moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-22 01:02:17 -05:00
Code Issues Releases Wiki Activity

1.4rc1: modified namespace issuance and versioning rules

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2323 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2008-10-06 15:53:30 +00:00
parent a40e41a445
commit 572d228824
1 changed files with 12 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
xep-0053.xml
View File

@ -19,6 +19,12 @@
<supersededby/> <supersededby/>
<shortname>N/A</shortname> <shortname>N/A</shortname>
&stpeter; &stpeter;
<revision>
<version>1.4rc1</version>
<date>2008-10-06</date>
<initials>psa</initials>
<remark><p>Adjusted namespace issuance process to use namespace versioning.</p></remark>
</revision>
<revision> <revision>
<version>1.3</version> <version>1.3</version>
<date>2006-12-07</date> <date>2006-12-07</date>
@ -89,20 +95,21 @@
<section1 topic='Namespace Issuance' anchor='namespaces'> <section1 topic='Namespace Issuance' anchor='namespaces'>
<p>The XMPP Registrar shall be responsible for issuing namespaces to be used in XMPP Extension Protocols (XEPs) developed through the XMPP Standards Foundation's standards process as specified in <cite>XEP-0001</cite>. The policies and procedures for namespace issuance shall be as follows:</p> <p>The XMPP Registrar shall be responsible for issuing namespaces to be used in XMPP Extension Protocols (XEPs) developed through the XMPP Standards Foundation's standards process as specified in <cite>XEP-0001</cite>. The policies and procedures for namespace issuance shall be as follows:</p>
<ol start='1'> <ol start='1'>
<li><p>While a XEP is in the Experimental state, the namespaces specified therein shall be of the form "http://www.xmpp.org/extensions/xep-XXXX.html#ns" and "http://www.xmpp.org/extensions/xep-XXXX.html#ns-SubName", where "XXXX" is the XEP number and "SubName" is a sub-namespace (as is familiar from specifications such as &xep0045;).</p></li>
<li> <li>
<p>When the XMPP Council votes to advance the XEP to a status of Draft, the XMPP Registrar shall generate official names for all namespaces specified in the XEP. The following considerations apply:</p> <p>When a XEP is first published in the Experimental state, the XMPP Registrar shall work with the author(s) to generate an appropriate namespace name, which shall be of the form "urn:xmpp:ShortName:0" or, where appropriate, "urn:xmpp:ShortName:SubName:0". The following considerations apply:</p>
<ol> <ol style='list-style: lower-alpha'>
<li>Each name shall adhere to the format defined in &rfc4854;.</li> <li>Each name shall adhere to the format defined in &rfc4854;.</li>
<li>Each name shall be of the form "urn:xmpp:ShortName[:SubName]".</li> <li>Each name shall be of the form "urn:xmpp:ShortName[:SubName]".</li>
<li>The "ShortName" string shall be unique within the XMPP URN tree and any "SubName" strings shall be unique within the scope of the ShortName.</li> <li>The "ShortName" string shall be unique within the XMPP URN tree and any "SubName" strings shall be unique within the scope of the ShortName.</li>
<li>Each name should be relevant and memorable. Names may be determined in consultation with the author(s) of the XEP and may be requested by the author(s) in the XMPP Registrar Considerations section of the XEP; however, the official issuance of namespace names is the sole responsibility of the XMPP Registrar, which may modify or ignore any names requested.</li> <li>Each name should be relevant and memorable. Names may be determined in consultation with the author(s) of the XEP and may be requested by the author(s) in the XMPP Registrar Considerations section of the XEP; however, the issuance of namespace names is the sole responsibility of the XMPP Registrar, which may modify or ignore any names requested.</li>
<li>Each name shall be checked against the registry of existing names located at &NAMESPACES; to ensure that no duplicate names are issued.</li> <li>Each name shall be checked against the registry of existing names located at &NAMESPACES; to ensure that no duplicate names are issued.</li>
<li>The XMPP Registrar shall issue all XMPP URNs directly and shall not assign secondary responsibility for management of any sub-trees.</li> <li>The XMPP Registrar shall issue all XMPP URNs directly and shall not assign secondary responsibility for management of any sub-trees.</li>
</ol> </ol>
</li> </li>
<li><p>After generating the relevant namespace name(s), the XMPP Registrar shall modify the XEP to reflect the issued namespace names and shall update the namespace registry in accordance with the procedures specified in the <link url='#registries'>Registry Creation and Maintenance</link> section of this document.</p></li> <li><p>While the XEP is in the Experimental state, if appropriate and in consultation with the author(s), the XMPP Registrar shall update the namespace version number at the end of namespace (e.g., from "0" to "1"); the XMPP Registrar shall do so only if the protocol defined in the XEP has been modified in a way that is not backwards-compatible with an earlier version of the protocol, or if significant new features have been added to the protocol.</p></li>
<li><p>When the XMPP Council votes to advance the XEP to a status of Draft, the XMPP Registrar shall update the namespace registry in accordance with the procedures specified in the <link url='#registries'>Registry Creation and Maintenance</link> section of this document.</p></li>
<li><p>Any namespaces defined after advancement of the relevant XEP to a status of Draft shall be handled in the same manner.</p></li> <li><p>Any namespaces defined after advancement of the relevant XEP to a status of Draft shall be handled in the same manner.</p></li>
<li><p>While the XEP is in the Draft or Final state, if appropriate and in consultation with the author(s) and the XMPP Council, the XMPP Registrar shall update the namespace version number at the end of namespace (e.g., from "1" to "2"); the XMPP Registrar shall do so only if the protocol defined in the XEP has been modified in a way that is not backwards-compatible with an earlier version of the protocol, or if significant new features have been added to the protocol. The XMPP Council must approve any change to the namespace version while the XEP is in the Draft or Final state.</p></li>
</ol> </ol>
<p>The XMPP Registrar shall not issue XMPP URNs except as specified above (e.g., it shall not issue XMPP URNs to private parties or in relation to specifications that are not published in the XEP series). However, the XMPP Registrar may at its discretion add namespace names other than XMPP URNs to its namespace registry, e.g. to register "legacy" namespace names (of the form "jabber:iq:*", "jabber:x:*", and "http://jabber.org/protocol/*") as well as namespace names produced by recognized standards development organizations (such as names issued in the IETF URN tree).</p> <p>The XMPP Registrar shall not issue XMPP URNs except as specified above (e.g., it shall not issue XMPP URNs to private parties or in relation to specifications that are not published in the XEP series). However, the XMPP Registrar may at its discretion add namespace names other than XMPP URNs to its namespace registry, e.g. to register "legacy" namespace names (of the form "jabber:iq:*", "jabber:x:*", and "http://jabber.org/protocol/*") as well as namespace names produced by recognized standards development organizations (such as names issued in the IETF URN tree).</p>
</section1> </section1>