moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 16:55:07 -05:00
Code Issues Releases Wiki Activity

added new XEPs, removed bis notes

Browse Source
This commit is contained in:
stpeter 2011-04-11 16:27:01 -06:00
parent 520e958af4
commit e5e1a3b991
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
xep.ent
View File

@ -230,9 +230,6 @@ THE SOFTWARE.
<!-- other XSF-related text shortcuts --> <!-- other XSF-related text shortcuts -->
<!ENTITY RFC3920BISNOTE "<p><em>Note: This document describes a protocol or best practice that is intended for incorporation into the specification that will supersede &rfc3920; within the Internet Standards Process, i.e., &rfc3920bis;. This document is provided only for the purpose of open community discussion of the potential modification and will be obsoleted as soon as the relevant RFC is published.</em></p>" >
<!ENTITY RFC3921BISNOTE "<p><em>Note: This document describes a protocol or best practice that is intended for incorporation into the specification that will supersede &rfc3921; within the Internet Standards Process, i.e., &rfc3921bis;. This document is provided only for the purpose of open community discussion of the potential modification and will be obsoleted as soon as the relevant RFC is published.</em></p>" >
<!ENTITY BOOLEANNOTE "<note>In accordance with Section 3.2.2.1 of <cite>XML Schema Part 2: Datatypes</cite>, the allowable lexical representations for the xs:boolean datatype are the strings &quot;0&quot; and &quot;false&quot; for the concept 'false' and the strings &quot;1&quot; and &quot;true&quot; for the concept 'true'; implementations MUST support both styles of lexical representation.</note>" > <!ENTITY BOOLEANNOTE "<note>In accordance with Section 3.2.2.1 of <cite>XML Schema Part 2: Datatypes</cite>, the allowable lexical representations for the xs:boolean datatype are the strings &quot;0&quot; and &quot;false&quot; for the concept 'false' and the strings &quot;1&quot; and &quot;true&quot; for the concept 'true'; implementations MUST support both styles of lexical representation.</note>" >
<!ENTITY REGPROCESS "<p>In order to submit new values to this registry, the registrant shall define an XML fragment of the following form and either include it in the relevant XMPP Extension Protocol or send it to the email address &lt;registrar@xmpp.org&gt;:</p>" > <!ENTITY REGPROCESS "<p>In order to submit new values to this registry, the registrant shall define an XML fragment of the following form and either include it in the relevant XMPP Extension Protocol or send it to the email address &lt;registrar@xmpp.org&gt;:</p>" >
@ -1198,3 +1195,6 @@ IANA Service Location Protocol, Version 2 (SLPv2) Templates</link></span> <note>
<!ENTITY xep0292 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0292.html'>vCard4 over XMPP</link></span> <note>XEP-0292: vCard4 over XMPP &lt;<link url='http://xmpp.org/extensions/xep-0292.html'>http://xmpp.org/extensions/xep-0292.html</link>&gt;.</note>" > <!ENTITY xep0292 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0292.html'>vCard4 over XMPP</link></span> <note>XEP-0292: vCard4 over XMPP &lt;<link url='http://xmpp.org/extensions/xep-0292.html'>http://xmpp.org/extensions/xep-0292.html</link>&gt;.</note>" >
<!ENTITY xep0293 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0293.html'>Jingle RTP Feedback Negotiation</link></span> <note>XEP-0293: Jingle RTP Feedback Negotiation&lt;<link url='http://xmpp.org/extensions/xep-0293.html'>http://xmpp.org/extensions/xep-0293.html</link>&gt;.</note>" > <!ENTITY xep0293 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0293.html'>Jingle RTP Feedback Negotiation</link></span> <note>XEP-0293: Jingle RTP Feedback Negotiation&lt;<link url='http://xmpp.org/extensions/xep-0293.html'>http://xmpp.org/extensions/xep-0293.html</link>&gt;.</note>" >
<!ENTITY xep0294 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0294.html'>Jingle RTP Header Extensions Negotiation</link></span> <note>XEP-0294: Jingle RTP Header Extensions Negotiation &lt;<link url='http://xmpp.org/extensions/xep-0294.html'>http://xmpp.org/extensions/xep-0294.html</link>&gt;.</note>" > <!ENTITY xep0294 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0294.html'>Jingle RTP Header Extensions Negotiation</link></span> <note>XEP-0294: Jingle RTP Header Extensions Negotiation &lt;<link url='http://xmpp.org/extensions/xep-0294.html'>http://xmpp.org/extensions/xep-0294.html</link>&gt;.</note>" >
<!ENTITY xep0295 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0295.html'>JSON Encodings for XMPP</link></span> <note>XEP-0295: JSON Encodings for XMPP &lt;<link url='http://xmpp.org/extensions/xep-0295.html'>http://xmpp.org/extensions/xep-0295.html</link>&gt;.</note>" >
<!ENTITY xep0296 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0296.html'>Best Practices for Resource Locking</link></span> <note>XEP-0296: Best Practices for Resource Locking &lt;<link url='http://xmpp.org/extensions/xep-0296.html'>http://xmpp.org/extensions/xep-0296.html</link>&gt;.</note>" >
<!ENTITY xep0297 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0297.html'>Message Forwarding</link></span> <note>XEP-0297: Message Forwarding &lt;<link url='http://xmpp.org/extensions/xep-0297.html'>http://xmpp.org/extensions/xep-0297.html</link>&gt;.</note>" >