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

added clearer note about superseding

Browse Source
This commit is contained in:
stpeter 2012-03-13 12:23:23 -06:00
parent 543f555af0
commit e51305b312
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
xep-0029.xml
View File

@ -7,7 +7,7 @@
<xep>
<header>
<title>Definition of Jabber Identifiers (JIDs)</title>
<abstract>This document defines the exact nature of a Jabber Identifier (JID). <em>Note well: this document is superseded by the XMPP Core memo defined by the IETF's XMPP Working Group.</em></abstract>
<abstract>This document defines the exact nature of a Jabber Identifier (JID). <em>Note well: this document was superseded by RFC 3920, which in turn has been superseded by RFC 6122.</em></abstract>
&LEGALNOTICE;
<number>0029</number>
<status>Retracted</status>
@ -51,6 +51,7 @@
</revision>
</header>
<section1 topic='Introduction'>
<p class='box'>Note: This document was superseded by &rfc3920;, which in turn has been superseded by &rfc6122;.</p>
<p>Jabber Identifiers (JIDs) uniquely identify individual entities in the Jabber network. To date, their syntax has been defined by convention, existing implementations, and available documentation. As it exists, certain characters that are allowed in JIDs cause ambiguity, and the lack of a size limit on resources defies database schemas and causes some trivial JID operations to require dynamic memory allocation. This document seeks to both define and improve the existing JID syntax. This document will not explain the general usage or nature of JIDs, instead focusing on syntax.</p>
</section1>
<section1 topic='JIDs'>