moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-25 10:42:19 -05:00
Code Issues Releases Wiki Activity

XEP-0389: expand Registrar Considerations

Browse Source 
This cleans up existing registrations, tweaks how the new registry works
to better match existing registries, and also adds registrations for the
namespaces registry and feature discovery registries.
This commit is contained in:
Sam Whited 2020-04-21 12:50:11 -04:00
parent e0694f28bd
commit 4850b2f5a7
1 changed files with 36 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
xep-0389.xml
View File

@ -407,9 +407,36 @@
<p> <p>
Upon advancement of this specification from a status of Experimental to a Upon advancement of this specification from a status of Experimental to a
status of Draft, the &REGISTRAR; shall add the foregoing namespace to the status of Draft, the &REGISTRAR; shall add the foregoing namespace to the
registry located at &STREAMFEATURES;, as described in Section 4 of registries located at &STREAMFEATURES;, and &DISCOFEATURES; as described
&xep0053;. in Section 4 of &xep0053;.
</p> </p>
<code caption='Service Discovery Features Registry Submission'><![CDATA[
<var>
<name>urn:xmpp:register:0</name>
<desc>Support for in band registration and password reset.</desc>
<doc>&xep0389;</doc>
</var>]]></code>
<code caption='Stream Features Registry Submission'><![CDATA[
<feature>
<ns>urn:xmpp:register:0</ns>
<name>Extensible In-Band Registration</name>
<element>register</element>
<desc>Support for in band registration and password reset.</desc>
<doc>&xep0389;</doc>
</feature>]]></code>
<p>
The &REGISTRAR; shall also add the foregoing namespace to the Jabber/XMPP
Protocol Namespaces Registry located at &NAMESPACES;.
Upon advancement of this specification from a status of Experimental to a
status of Draft, the &REGISTRAR; shall remove the provisional status from
this registry entry.
</p>
<code caption='Jabber/XMPP Protocol Namespaces Registry Submission'><![CDATA[
<ns>
<name>urn:xmpp:register:0</name>
<doc>&xep0389;</doc>
<status>provisional</status>
</ns>]]></code>
</section2> </section2>
<section2 topic='IBR Challenge Types Registry' anchor='registrar-challenges'> <section2 topic='IBR Challenge Types Registry' anchor='registrar-challenges'>
<p> <p>
@ -420,14 +447,11 @@
&REGPROCESS; &REGPROCESS;
<code><![CDATA[ <code><![CDATA[
<challenge> <challenge>
<name>The name of the challenge type.</name> <name>The name of the challenge (from the initial <challenge/> listing).</name>
<desc>A natural-language summary of the challenge.</desc> <desc>A natural-language summary of the challenge.</desc>
<payloaddoc>
The document in which the IBR challenge payload is specified.
</payloaddoc>
<doc> <doc>
The doucment in which the IBR challenge itself is specified (may be the same The doucment (or documents) in which the IBR challenge and its paylaod are
as <payloaddoc/>). defined.
</doc> </doc>
</challenge>]]></code> </challenge>]]></code>
<p> <p>
@ -444,13 +468,12 @@
status of Draft, the &REGISTRAR; shall add the following definition to the status of Draft, the &REGISTRAR; shall add the following definition to the
IBR challenge types registry, as described in this document: IBR challenge types registry, as described in this document:
</p> </p>
<code><![CDATA[ <code caption='Challenge Type Registry Submission for Data Forms'><![CDATA[
<challenge> <challenge>
<name>Data Forms Challenge</name> <name>jabber:x:data</name>
<desc>Requests that the client fill out an XEP-0004 data form.</desc> <desc>Requests that the client fill out an XEP-0004 data form.</desc>
<payloaddoc>XEP-0004</payloaddoc> <doc>&xep0389;, &xep0004;</doc>
<doc>TODO: Insert this document once it is assigned a number</doc> </challenge>]]></code>
</profile>]]></code>
</section2> </section2>
<section2 topic='Namespace Versioning' anchor='registrar-versioning'> <section2 topic='Namespace Versioning' anchor='registrar-versioning'>
&NSVER; &NSVER;