From 95a07d32c699fcdebc3f24efcee511ddcc38cd6e Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 22 Oct 2008 15:28:19 +0000 Subject: [PATCH] 1.4rc2: clarified uniqueness checking and version incrementing for namespaces git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2422 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0053.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/xep-0053.xml b/xep-0053.xml index 705197d3..4801d62e 100644 --- a/xep-0053.xml +++ b/xep-0053.xml @@ -20,10 +20,10 @@ N/A &stpeter; - 1.4rc1 - 2008-10-06 + 1.4rc2 + in progress, last updated 2008-10-21 psa -

Adjusted namespace issuance process to use namespace versioning.

 +

Adjusted namespace issuance process to employ namespace versioning.

 1.3 @@ -96,17 +96,17 @@

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 XEP-0001. The policies and procedures for namespace issuance shall be as follows:

  1. -

    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:

    +

    When a XEP is first published in the Experimental state, the XMPP Registrar shall work with the author(s) to mint 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:

    1. Each name shall adhere to the format defined in &rfc4854;.
    2. Each name shall be of the form "urn:xmpp:ShortName[:SubName]".
    3. The "ShortName" string shall be unique within the XMPP URN tree and any "SubName" strings shall be unique within the scope of the ShortName.
    4. 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.
      5. -
    5. Each name shall be checked against the registry of existing names located at &NAMESPACES; to ensure that no duplicate names are issued.
      6. +
    6. To ensure that no duplicate names are issued, each name to be minted shall be checked against the registry of registered names issued in relation to Draft and Final XEPs (see &NAMESPACES;) and against the list of minted but not yet registered names issued in relation to Experimental XEPs.
    7. The XMPP Registrar shall issue all XMPP URNs directly and shall not assign secondary responsibility for management of any sub-trees.
    2. -

  2. 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.

    3. +

  3. 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.

  4. 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 Registry Creation and Maintenance section of this document.

  5. Any namespaces defined after advancement of the relevant XEP to a status of Draft shall be handled in the same manner.

  6. 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.