1
0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-05 00:45:05 -05:00
xeps/xep-0242.xml
Emmanuel Gil Peyrot 3c5f20a4ca Remove all trailing whitespace from every XEP.
sed -i 's/\s\+$//' xep-*.xml
2017-02-16 19:37:21 -06:00

97 lines
3.4 KiB
XML

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
%ents;
]>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep>
<header>
<title>XMPP Client Compliance 2009</title>
<abstract>This document defines XMPP client compliance levels for 2009.</abstract>
&LEGALNOTICE;
<number>0242</number>
<status>Obsolete</status>
<type>Standards Track</type>
<sig>Standards</sig>
<dependencies>
<spec>XMPP Core</spec>
<spec>XMPP IM</spec>
<spec>XEP-0016</spec>
<spec>XEP-0030</spec>
<spec>XEP-0045</spec>
<spec>XEP-0054</spec>
<spec>XEP-0085</spec>
<spec>XEP-0115</spec>
<spec>XEP-0191</spec>
</dependencies>
<supersedes>
<spec>XEP-0211</spec>
<spec>XEP-0213</spec>
</supersedes>
<supersededby>
<spec>XEP-0270</spec>
</supersededby>
<shortname>N/A</shortname>
&stpeter;
<revision>
<version>1.0</version>
<date>2008-09-08</date>
<initials>psa</initials>
<remark><p>Per a vote of the XMPP Council, advanced specification to Draft.</p></remark>
</revision>
<revision>
<version>0.2</version>
<date>2008-06-18</date>
<initials>psa</initials>
<remark><p>Changed compliance level names, updated required support per Council discussion.</p></remark>
</revision>
<revision>
<version>0.1</version>
<date>2008-05-28</date>
<initials>psa</initials>
<remark><p>Initial published version, incorporating Council feedback.</p></remark>
</revision>
<revision>
<version>0.0.1</version>
<date>2008-05-27</date>
<initials>psa</initials>
<remark><p>First draft, copied and modified from XEP-0211.</p></remark>
</revision>
</header>
<section1 topic='Introduction' anchor='intro'>
<p>The &XSF; defines protocol suites for the purpose of compliance testing and software certification. This document specifies the 2009 compliance levels for XMPP clients. Support for the listed specifications is REQUIRED for compliance purposes.</p>
</section1>
<section1 topic='XMPP Core Client 2009' anchor='core'>
<p>The XMPP Core Client 2009 certification level is defined as follows:</p>
<ul>
<li>&rfc3920;</li>
<li>&rfc3921;</li>
<li>&xep0030;</li>
<li>&xep0115;</li>
</ul>
</section1>
<section1 topic='XMPP Advanced Client 2009' anchor='advanced'>
<p>The XMPP Advanced Client 2009 certification level is defined as follows:</p>
<ul>
<li>XMPP Core Client 2009 (see above)</li>
<li>&xep0016; and &xep0191;</li>
<li>&xep0045; (Entity Use Cases and Occupant Use Cases)</li>
<li>&xep0054;</li>
<li>&xep0085;</li>
</ul>
</section1>
<section1 topic='Implementation Notes' anchor='impl'>
<p>Some of the protocol specifications referenced herein have their own dependencies; developers must refer to the relevant specifications for further information.</p>
<p>Developers are advised to refer to &xep0178; regarding proper implementation of the SASL EXTERNAL mechanism in XMPP.</p>
</section1>
<section1 topic='Security Considerations' anchor='security'>
<p>This document introduces no additional security considerations above and beyond those defined in the documents on which it depends.</p>
</section1>
<section1 topic='IANA Considerations' anchor='iana'>
<p>This document requires no interaction with &IANA;.</p>
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<p>This document requires no interaction with the &REGISTRAR;.</p>
</section1>
</xep>