Browse Source

Lots of DTD fixes

Only one minor content change that fixes some unescaped characters.
master
Sam Whited 3 years ago
parent
commit
522dc3671e
8 changed files with 36 additions and 6 deletions
  1. 5
    0
      xep-0006.xml
  2. 5
    0
      xep-0007.xml
  3. 2
    2
      xep-0008.xml
  4. 1
    1
      xep-0009.xml
  5. 5
    0
      xep-0010.xml
  6. 6
    0
      xep-0014.xml
  7. 6
    0
      xep-0015.xml
  8. 6
    3
      xep-0018.xml

+ 5
- 0
xep-0006.xml View File

@@ -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>

+ 5
- 0
xep-0007.xml View File

@@ -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>

+ 2
- 2
xep-0008.xml View File

@@ -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;

+ 1
- 1
xep-0009.xml View File

@@ -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'>

+ 5
- 0
xep-0010.xml View File

@@ -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>

+ 6
- 0
xep-0014.xml View File

@@ -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>

+ 6
- 0
xep-0015.xml View File

@@ -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>

+ 6
- 3
xep-0018.xml View File

@@ -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>

Loading…
Cancel
Save