moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

XEP-0053 title change 

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@294 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2006-12-21 21:33:39 +00:00
parent 2ec0619f89
commit b11b7522f7
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
xep-0053.xml
View File

@ -6,8 +6,8 @@
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep>
<header>
<title>XMPP Registrar</title>
<abstract>This document defines the roles and processes of the XMPP Registrar within the Jabber Software Foundation.</abstract>
<title>XMPP Registrar Function</title>
<abstract>This document defines the roles and processes of the XMPP Registrar function within the Jabber Software Foundation.</abstract>
&LEGALNOTICE;
<number>0053</number>
<status>Active</status>
@ -83,7 +83,7 @@
<section1 topic='Registry Creation and Maintenance' anchor='registries'>
<p>Every XMPP Extension Protocol specification (XEP) must contain a section devoted to "XMPP Registrar Considerations", detailing the namespaces and parameters to be registered with the XMPP Registrar, as well as any new registries to be created as a result of the XEP.</p>
<p>The registry additions or creations specified in an XMPP Extension Protocol specification shall not take effect until the document advances to a status of Draft (Standards-Track XEPs) or Active (Informational and Historical XEPs). Registration of namespaces shall be handled as described in the <link url='#namespaces'>Namespace Issuance</link> section of this document. Registration of particular parameters used within a specification shall be initiated by the XMPP Extensions Editor if specified in the XEP, and may also be initiated by implementors of the XMPP Extension Protocol document after it has advanced to Active, Draft, or Final. Creation of new registries shall be initiated by the XMPP Registrar; if a document specifies the creation of a new registry, the author is strongly encouraged to consult with the XMPP Registrar before seeking a Last Call on the XEP.</p>
<p>Requests for parameter assignments must be sent to the XMPP Registrar in accordance with the process specified in the document (usually a XEP) that defines the relevant registry, normally by sending an appropriately formatted email message to &lt;registrar@jabber.org&gt;. If, in the Registrar's judgment, discussion of a request is required, the Registrar shall initiate such discussion within the &SJIG;. The Registrar shall add registry items at its discretion based on discussion within the Standards JIG if necessary, but shall not unduly restrict registration of parameter values. If a document author or implementer thinks that a request was unfairly denied by the Registrar, an appeal of the decision may be directed to the XMPP Council.</p>
<p>Requests for parameter assignments must be sent to the XMPP Registrar in accordance with the process specified in the document (usually a XEP) that defines the relevant registry, normally by sending an appropriately formatted email message to &lt;<link url='mailto:registrar@jabber.org'>mailto:registrar@jabber.org</link>&gt;. If, in the Registrar's judgment, discussion of a request is required, the Registrar shall initiate such discussion within the &SJIG;. The Registrar shall add registry items at its discretion based on discussion within the Standards JIG if necessary, but shall not unduly restrict registration of parameter values. If a document author or implementor thinks that a request was unfairly denied by the Registrar, an appeal of the decision may be directed to the XMPP Council.</p>
<p>The XMPP Registrar shall maintain registries of assigned namespaces and parameters at &lt;<link url="http://www.xmpp.org/registrar/">http://www.xmpp.org/registrar/</link>&gt; and shall update those registries in a timely fashion. Changes to the registries shall be announced on the Standards-JIG mailing list.</p>
</section1>
<section1 topic='Namespace Issuance' anchor='namespaces'>
@ -96,7 +96,7 @@
<li>Each name shall adhere to the format defined in &xmppurn;.</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. All such strings should be relevant and memorable, and may be determined in consultation with the author(s) of the XEP.</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 assign 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>
</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>
@ -104,10 +104,10 @@
<p>Any namespaces defined after advancement of the relevant XEP to a status of Draft shall be handled in the same manner. 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 topic='Security Considerations' anchor='security'>
<p>Security considerations are primarily the responsibility of the protocols in which specific parameters are used. The XMPP Registrar shall respect the security considerations defined in JSF protocol specifications, and shall endeavor to ensure that registered parameter values do not compromise privacy or security in any way.</p>
<p>Security considerations are primarily the responsibility of the protocols in which specific parameters are used. The XMPP Registrar shall respect the security considerations defined in XMPP Extension Protocol specifications, and shall endeavor to ensure that registered parameter values do not compromise privacy or security in any way.</p>
</section1>
<section1 topic='IANA Considerations' anchor='iana'>
<p>The XMPP Registrar shall be responsible for interacting with the IANA on behalf of the Jabber Software Foundation and Jabber/XMPP developer community. If an XMPP Extension Protocol document requires interaction with the IANA, that fact shall be noted by the document author and discussed on the Standards-JIG mailing list along with normal discussion of the XEP. The XMPP Registrar shall collaborate with the author to present an appropriate request to the IANA.</p>
<p>The XMPP Registrar shall be responsible for interacting with the IANA on behalf of the Jabber Software Foundation and Jabber/XMPP developer community. If an XMPP Extension Protocol specification requires interaction with the IANA, that fact shall be noted by the document author and discussed on the Standards-JIG mailing list along with normal discussion of the XEP. The XMPP Registrar shall collaborate with the author to present an appropriate request to the IANA.</p>
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<p>This entire document defines the processes and procedures of the XMPP Registrar.</p>

2
xep.ent
View File

@ -626,7 +626,7 @@
<!ENTITY xep0050 "<span class='ref'>Ad-Hoc Commands</span> <note>XEP-0050: Ad-Hoc Commands &lt;<link url='http://www.xmpp.org/extensions/xep-0050.html'>http://www.xmpp.org/extensions/xep-0050.html</link>&gt;.</note>" >
<!ENTITY xep0051 "<span class='ref'>Redirect and Connection Transfer</span> <note>XEP-0051: Redirect and Connection Transfer &lt;<link url='http://www.xmpp.org/extensions/xep-0051.html'>http://www.xmpp.org/extensions/xep-0051.html</link>&gt;.</note>" >
<!ENTITY xep0052 "<span class='ref'>File Transfer</span> <note>XEP-0052: File Transfer &lt;<link url='http://www.xmpp.org/extensions/xep-0052.html'>http://www.xmpp.org/extensions/xep-0052.html</link>&gt;.</note>" >
<!ENTITY xep0053 "<span class='ref'>XMPP Registrar</span> <note>XEP-0053: XMPP Registrar &lt;<link url='http://www.xmpp.org/extensions/xep-0053.html'>http://www.xmpp.org/extensions/xep-0053.html</link>&gt;.</note>" >
<!ENTITY xep0053 "<span class='ref'>XMPP Registrar Function</span> <note>XEP-0053: XMPP Registrar Function &lt;<link url='http://www.xmpp.org/extensions/xep-0053.html'>http://www.xmpp.org/extensions/xep-0053.html</link>&gt;.</note>" >
<!ENTITY xep0054 "<span class='ref'>vcard-temp</span> <note>XEP-0054: vcard-temp &lt;<link url='http://www.xmpp.org/extensions/xep-0054.html'>http://www.xmpp.org/extensions/xep-0054.html</link>&gt;.</note>" >
<!ENTITY xep0055 "<span class='ref'>Jabber Search</span> <note>XEP-0055: Jabber Search &lt;<link url='http://www.xmpp.org/extensions/xep-0055.html'>http://www.xmpp.org/extensions/xep-0055.html</link>&gt;.</note>" >
<!ENTITY xep0056 "<span class='ref'>Business Data Interchange</span> <note>XEP-0056: Business Data Interchange &lt;<link url='http://www.xmpp.org/extensions/xep-0056.html'>http://www.xmpp.org/extensions/xep-0056.html</link>&gt;.</note>" >