Lots of DTD fixes

Only one minor content change that fixes some unescaped characters.
Detaysoft · Nov 27, 2016 · 522dc36 · 522dc36
1 parent 1e8b673
commit 522dc36
Show file tree

Hide file tree

Showing 8 changed files with 36 additions and 6 deletions.
diff --git a/xep-0006.xml b/xep-0006.xml
@@ -13,6 +13,11 @@
   <status>Obsolete</status>
   <type>SIG Formation</type>
   <sig>Forms, Security</sig>
+  <approver>Board</approver>
+  <dependencies/>
+  <supersedes/>
+  <supersededby/>
+  <shortname>N/A</shortname>
   <author>
     <firstname>Adam</firstname>
     <surname>Theo</surname>

diff --git a/xep-0007.xml b/xep-0007.xml
@@ -13,6 +13,11 @@
   <status>Obsolete</status>
   <type>SIG Proposal</type>
   <sig>Conferencing</sig>
+  <approver>Board</approver>
+  <dependencies/>
+  <supersedes/>
+  <supersededby/>
+  <shortname>N/A</shortname>
   <author>
     <firstname>David</firstname>
     <surname>Waite</surname>

diff --git a/xep-0008.xml b/xep-0008.xml
@@ -18,8 +18,8 @@
     <spec>XMPP Core</spec>
     <spec>XMPP IM</spec>
   </dependencies>
-  <supersedes>None</supersedes>
-  <supersededby>None</supersededby>
+  <supersedes/>
+  <supersededby/>
   <shortname>None</shortname>
   &temas;
   &xvirge;

diff --git a/xep-0009.xml b/xep-0009.xml
@@ -62,7 +62,7 @@
 </header>
 <section1 topic='Introduction'>
   <p>&xmlrpc; is a method of encoding RPC requests and responses in XML. The original specification defines HTTP (see &rfc2068;) as the only valid transport for XML-RPC payloads.</p>
-  <p>Various initiatives exist already to transport XML-RPC payloads over Jabber. These initiatives were independent of each other and used slightly differing methods (e.g. carrying the payload in a <message/> element as opposed to an &IQ; stanza), resulting in potential interoperability problems.</p>
+  <p>Various initiatives exist already to transport XML-RPC payloads over Jabber. These initiatives were independent of each other and used slightly differing methods (e.g. carrying the payload in a &lt;message/&gt; element as opposed to an &IQ; stanza), resulting in potential interoperability problems.</p>
   <p>A working session during JabberCon 2001 resulted in formalisation of a single method. This document describes that method, which is labelled as Jabber-RPC to differentiate it from XML-RPC itself.</p>
 </section1>
 <section1 topic='Jabber-RPC'>

diff --git a/xep-0010.xml b/xep-0010.xml
@@ -13,6 +13,11 @@
   <status>Obsolete</status>
   <type>SIG Formation</type>
   <sig>None</sig>
+  <approver>Board</approver>
+  <dependencies/>
+  <supersedes/>
+  <supersededby/>
+  <shortname>N/A</shortname>
   <author>
     <firstname>Niklas</firstname>
     <surname>Gustavsson</surname>

diff --git a/xep-0014.xml b/xep-0014.xml
@@ -13,6 +13,12 @@
   <status>Rejected</status>
   <type>Standards Track</type>
   <sig>Standards</sig>
+  <dependencies>
+    <spec>XMPP Core</spec>
+  </dependencies>
+  <supersedes/>
+  <supersededby/>
+  <shortname>N/A</shortname>
   <author>
     <firstname>Mike</firstname>
     <surname>Mintz</surname>

diff --git a/xep-0015.xml b/xep-0015.xml
@@ -13,6 +13,12 @@
     <status>Rejected</status>
     <type>Standards Track</type>
     <sig>Standards</sig>
+    <dependencies>
+      <spec>XMPP Core</spec>
+    </dependencies>
+    <supersedes/>
+    <supersededby/>
+    <shortname>N/A</shortname>
     <author>
       <firstname>Casey</firstname>
       <surname>Crabb</surname>

diff --git a/xep-0018.xml b/xep-0018.xml
@@ -13,9 +13,12 @@
   <status>Rejected</status>
   <type>Informational</type>
   <sig>Standards</sig>
-  <dependencies>XMPP Core, XMPP IM</dependencies>
-  <supersedes>None</supersedes>
-  <supersededby>None</supersededby>
+  <dependencies>
+    <spec>XMPP Core</spec>
+    <spec>XMPP IM</spec>
+  </dependencies>
+  <supersedes/>
+  <supersededby/>
   <shortname>N/A</shortname>
   <author>
     <firstname>Ben</firstname>