NSVER

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2763 4b5297f7-1745-476d-ba37-a9c6900126ab

xep-0152.xml

@@ -210,14 +210,14 @@
 
 <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
   <section2 topic='Protocol Namespaces' anchor='registrar-ns'>
-    <p>This specification defines the following XML namespaces:</p>
+    <p>This specification defines the following XML namespace:</p>
     <ul>
       <li>urn:xmpp:reach:0</li>
     </ul>
-    <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespaces to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
+    <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
   </section2>
   <section2 topic='Namespace Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+    &NSVER;
   </section2>
 </section1>
 

xep-0168.xml

@@ -380,7 +380,7 @@
     <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespaces to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
   </section2>
   <section2 topic='Namespace Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+    &NSVER;
   </section2>
 </section1>
 

xep-0181.xml

@@ -215,10 +215,10 @@
     <ul>
       <li>urn:xmpp:jingle:dtmf:0</li>
     </ul>
-    <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespaces to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
+    <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
   </section2>
   <section2 topic='Protocol Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+    &NSVER;
   </section2>
 </section1>
 

xep-0186.xml

@@ -226,7 +226,7 @@
     <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
   </section2>
   <section2 topic='Protocol Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+    &NSVER;
   </section2>
 </section1>
 

xep-0194.xml

@@ -150,14 +150,14 @@
 </section1>
 <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
   <section2 topic='Protocol Namespaces' anchor='registrar-ns'>
-    <p>This specification defines the following XML namespaces:</p>
+    <p>This specification defines the following XML namespace:</p>
     <ul>
       <li>urn:xmpp:chatting:0</li>
     </ul>
-    <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespaces to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
+    <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
   </section2>
   <section2 topic='Namespace Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+    &NSVER;
   </section2>
 </section1>
 <section1 topic='XML Schema' anchor='schema'>

xep-0195.xml

@@ -159,10 +159,10 @@
     <ul>
       <li>urn:xmpp:browsing:0</li>
     </ul>
-    <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespaces to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
+    <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
   </section2>
   <section2 topic='Namespace Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+    &NSVER;
   </section2>
 </section1>
 <section1 topic='XML Schema' anchor='schema'>

xep-0196.xml

@@ -182,10 +182,10 @@
     <ul>
       <li>urn:xmpp:gaming:0</li>
     </ul>
-    <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespaces to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
+    <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
   </section2>
   <section2 topic='Namespace Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+    &NSVER;
   </section2>
 </section1>
 <section1 topic='XML Schema' anchor='schema'>

xep-0197.xml

@@ -227,10 +227,10 @@
     <ul>
       <li>urn:xmpp:viewing:0</li>
     </ul>
-    <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespaces to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
+    <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
   </section2>
   <section2 topic='Namespace Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+    &NSVER;
   </section2>
 </section1>
 <section1 topic='XML Schema' anchor='schema'>

xep-0198.xml

@@ -233,7 +233,7 @@ C: <enable xmlns='urn:xmpp:sm:0' resume='true'/>
     <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespaces to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
   </section2>
   <section2 topic='Protocol Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+    &NSVER;
   </section2>
   <section2 topic='Stream Features' anchor='registrar-stream'>
     <p>Upon approval of this specification, the XMPP Registrar shall add 'urn:xmpp:sm:0:feature' to its registry of stream features.</p>

xep-0224.xml

@@ -148,7 +148,7 @@
     <p>The &REGISTRAR; includes this namespace in the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
   </section2>
   <section2 topic='Protocol Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+    &NSVER;
   </section2>
 </section1>
 <section1 topic='XML Schema' anchor='schema'>

xep-0225.xml

@@ -141,7 +141,7 @@ S: <iq id='unbind_1' type='result'/>
     <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
   </section2>
   <section2 topic='Protocol Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+    &NSVER;
   </section2>
 </section1>
 <section1 topic='XML Schema' anchor='schema'>

xep-0234.xml

@@ -277,7 +277,7 @@ Initiator                    Responder
     <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespaces to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
   </section2>
   <section2 topic='Namespace Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+    &NSVER;
   </section2>
   <section2 topic='Jingle Application Formats' anchor='registrar-content'>
     <p>The XMPP Registrar shall include "file-transfer" in its registry of Jingle application formats. The registry submission is as follows:</p>

xep-0251.xml

@@ -520,7 +520,7 @@ Caller                 Attendant                 Callee
     <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespaces to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
   </section2>
   <section2 topic='Protocol Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+    &NSVER;
   </section2>
 </section1>
 

xep-0255.xml

@@ -694,7 +694,7 @@
     <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespaces to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
   </section2>
   <section2 topic='Protocol Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+    &NSVER;
   </section2>
 
 </section1>

xep-0260.xml

@@ -418,7 +418,7 @@ Romeo                               Juliet
 
 <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
   <section2 topic='Jingle Transport Methods' anchor='registrar-transports'>
-    <p>The XMPP Registrar shall add to its registry of Jingle transport methods a definition for the "jingle-s5b" transport method. The registry submission is as follows:</p>
+    <p>The &REGISTRAR; shall add to its registry of Jingle transport methods a definition for the "jingle-s5b" transport method. The registry submission is as follows:</p>
     <code><![CDATA[
 <transport>
   <name>s5b</name>