Per a vote of the XMPP Council, advanced specification from Experimental to Draft; also required inclusion of the creator attribute per list consensus.
Upon advancement of this specification from a status of Experimental to a status of Draft, the ®ISTRAR; shall add the foregoing namespaces to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.
+The ®ISTRAR; includes the foregoing namespaces in its registry at &NAMESPACES;, as governed by &xep0053;.
The XMPP Registrar shall maintain a registry of Jingle application formats. All application format registrations shall be defined in separate specifications (not in this document). Application types defined within the XEP series MUST be registered with the XMPP Registrar, resulting in protocol URNs of the form "urn:xmpp:jingle:app:name:X" (where "name" is the registered name of the application format and "X" is a non-negative integer).
+The XMPP Registrar maintains a registry of Jingle application formats at &JINGLEAPPS;. All application format registrations shall be defined in separate specifications (not in this document). Application types defined within the XEP series MUST be registered with the XMPP Registrar, resulting in protocol URNs of the form "urn:xmpp:jingle:app:name:X" (where "name" is the registered name of the application format and "X" is a non-negative integer).
®PROCESS;
@@ -1542,7 +1557,7 @@ PENDING o-----------------------+ |
]]>
The XMPP Registrar shall maintain a registry of Jingle transport methods. All transport method registrations shall be defined in separate specifications (not in this document). Transport methods defined within the XEP series MUST be registered with the XMPP Registrar, resulting in protocol URNs of the form "urn:xmpp:jingle:transport:name" (where "name" is the registered name of the transport method).
+The XMPP Registrar maintains a registry of Jingle transport methods at &JINGLETRANSPORTS;. All transport method registrations shall be defined in separate specifications (not in this document). Transport methods defined within the XEP series MUST be registered with the XMPP Registrar, resulting in protocol URNs of the form "urn:xmpp:jingle:transport:name" (where "name" is the registered name of the transport method).
®PROCESS;
@@ -1568,6 +1583,13 @@ PENDING o-----------------------+ |
xmlns='urn:xmpp:jingle:1'
elementFormDefault='qualified'>
+
+
+ The protocol documented by this schema is defined in
+ XEP-0166: http://www.xmpp.org/extensions/xep-0166.html
+
+
+
@@ -1622,8 +1644,7 @@ PENDING o-----------------------+ |
+ use='required'>
@@ -1698,6 +1719,13 @@ PENDING o-----------------------+ |
xmlns='urn:xmpp:jingle:errors:1'
elementFormDefault='qualified'>
+
+
+ The protocol documented by this schema is defined in
+ XEP-0166: http://www.xmpp.org/extensions/xep-0166.html
+
+
+