Remove all trailing whitespace from every XEP.

sed -i 's/\s\+$//' xep-*.xml
Detaysoft · Feb 17, 2017 · 3c5f20a · 3c5f20a
1 parent 856c742
commit 3c5f20a
Show file tree

Hide file tree

Showing 239 changed files with 4,021 additions and 4,021 deletions.
diff --git a/xep-0001.xml b/xep-0001.xml
@@ -211,7 +211,7 @@
   <ol start='1'>
     <li>To produce practical, technically excellent solutions to important problems of real-time communication based on the set of streaming XML technologies known as XMPP.</li>
     <li>To document XMPP extensions in a clear, concise manner so that the task of implementing the protocols is straightforward.</li>
-    <li>To ensure interoperability among the disparate technologies used on XMPP networks.</li> 
+    <li>To ensure interoperability among the disparate technologies used on XMPP networks.</li>
     <li>To guarantee that any person or entity can implement the protocols without encumbrance.</li>
     <li>To work in an fair, open, objective manner.</li>
   </ol>
@@ -350,8 +350,8 @@ Experimental ----> Proposed ----> Active
                                              |
                                              +--> Obsolete
     </code>
-    <p>Because such XEPs do not seek to define standard protocols, in general they are less controversial and tend to proceed from Proposed to Active without controversy on a vote of the XMPP Council. However, some of these XEPs may be remanded from the Council to the XEP author and/or XMPP Extensions Editor for revision in order to be suitable for advancement from Proposed to Active (e.g., documentation of protocols in use must be accurate and describe any existing security concerns). As with Standards Track XEPs, the XEP author may retract such a XEP when it is Experimental, and the Council may reject such a XEP when it is Proposed.</p> 
-    <p>Once approved, Historical, Informational, and Procedural XEPs will have a status of Active. Such a XEP may be replaced by a new XEP on the same or a similar topic, thus rendering the earlier XEP out of date; in such cases, the earlier XEP shall be assigned a status of Deprecated (and eventually Obsolete) with a note specifying the superseding XEP.</p> 
+    <p>Because such XEPs do not seek to define standard protocols, in general they are less controversial and tend to proceed from Proposed to Active without controversy on a vote of the XMPP Council. However, some of these XEPs may be remanded from the Council to the XEP author and/or XMPP Extensions Editor for revision in order to be suitable for advancement from Proposed to Active (e.g., documentation of protocols in use must be accurate and describe any existing security concerns). As with Standards Track XEPs, the XEP author may retract such a XEP when it is Experimental, and the Council may reject such a XEP when it is Proposed.</p>
+    <p>Once approved, Historical, Informational, and Procedural XEPs will have a status of Active. Such a XEP may be replaced by a new XEP on the same or a similar topic, thus rendering the earlier XEP out of date; in such cases, the earlier XEP shall be assigned a status of Deprecated (and eventually Obsolete) with a note specifying the superseding XEP.</p>
     <p>The XMPP Council may, at its discretion, decide to convert an Historical XEP into a Standards Track XEP if the protocol defined in the XEP has been in long use, is deemed stable and uncontroversial, and is unlikely to be superseded by a newer protocol. The Historical XEP shall be treated in the same way as a Standards Track XEP that has a status of Experimental, beginning with the <link url="#proposal">Proposal Process</link>. If after the Last Call and voting by the XMPP Council the XEP is approved for advancement on the standards track, its type shall be changed to Standards Track and its status shall be changed to Draft.</p>
   </section2>
 </section1>
@@ -370,7 +370,7 @@ Experimental ----> Proposed ----> Active
   </section2>
   <section2 topic='Final' anchor='states-Final'>
     <p>A Standards Track XEP is in the Final state after it has been in the Draft state for at least six (6) months, has been implemented in at least two separate codebases, and has been voted forward on the standards track by the XMPP Council.</p>
-    <p><em>Note: Once an XMPP Extension Protocol has been advanced to a status of Final, every effort shall be made to limit the scope of modifications; in particular, backwards-incompatible changes shall not be made. However, limited modifications may be made as long as they are optional, backwards-compatible extensions rather than modifications to the core protocol itself. Therefore, a Final protocol is safe for deployment in mission-critical applications.</em></p> 
+    <p><em>Note: Once an XMPP Extension Protocol has been advanced to a status of Final, every effort shall be made to limit the scope of modifications; in particular, backwards-incompatible changes shall not be made. However, limited modifications may be made as long as they are optional, backwards-compatible extensions rather than modifications to the core protocol itself. Therefore, a Final protocol is safe for deployment in mission-critical applications.</em></p>
   </section2>
   <section2 topic='Active' anchor='states-Active'>
     <p>A XEP of any type other than Standards Track is advanced to a status of Active after it has been voted forward from Experimental by the XMPP Council.</p>
@@ -453,10 +453,10 @@ THE SOFTWARE.
     <xs:annotation>
       <xs:documentation>
 
-        This schema defines the document format for XMPP Extension 
+        This schema defines the document format for XMPP Extension
         Protocols (XEPs). For further information about XEPs, visit:
 
-           http://www.xmpp.org/extensions/ 
+           http://www.xmpp.org/extensions/
 
         The canonical URL for this schema is:
 
@@ -481,20 +481,20 @@ THE SOFTWARE.
         <xs:element name='number' type='xs:byte'/>
         <xs:element ref='status'/>
         <xs:element name='lastcall' minOccurs='0' type='xs:string'/>
-        <xs:element name='interim' minOccurs='0' type='empty'/> 
-        <xs:element ref='type'/> 
+        <xs:element name='interim' minOccurs='0' type='empty'/>
+        <xs:element ref='type'/>
         <xs:element name='sig' type='xs:string'/>
         <xs:element name='approver' type='xs:string'/>
         <xs:element ref='dependencies'/>
         <xs:element ref='supersedes'/>
         <xs:element ref='supersededby'/>
         <xs:element name='shortname' type='xs:NCName'/>
-        <xs:element ref='schemaloc' minOccurs='0' maxOccurs='unbounded'/> 
-        <xs:element name='registry' minOccurs='0' type='empty'/> 
+        <xs:element ref='schemaloc' minOccurs='0' maxOccurs='unbounded'/>
+        <xs:element name='registry' minOccurs='0' type='empty'/>
         <xs:element name='discuss' minOccurs='0' type='xs:string'/>
         <xs:element name='expires' minOccurs='0' type='xs:string'/>
-        <xs:element ref='author' minOccurs='1' maxOccurs='unbounded'/> 
-        <xs:element ref='revision' minOccurs='1' maxOccurs='unbounded'/> 
+        <xs:element ref='author' minOccurs='1' maxOccurs='unbounded'/>
+        <xs:element ref='revision' minOccurs='1' maxOccurs='unbounded'/>
       </xs:sequence>
     </xs:complexType>
   </xs:element>
@@ -744,7 +744,7 @@ THE SOFTWARE.
     <xs:complexType>
       <xs:simpleContent>
         <xs:extension base='empty'>
-          <xs:attribute name='source' use='required'/> 
+          <xs:attribute name='source' use='required'/>
         </xs:extension>
       </xs:simpleContent>
     </xs:complexType>
@@ -754,7 +754,7 @@ THE SOFTWARE.
     <xs:complexType>
       <xs:simpleContent>
         <xs:extension base='xs:string'>
-          <xs:attribute name='url' use='required'/> 
+          <xs:attribute name='url' use='required'/>
         </xs:extension>
       </xs:simpleContent>
     </xs:complexType>
@@ -766,7 +766,7 @@ THE SOFTWARE.
     <xs:complexType>
       <xs:simpleContent>
         <xs:extension base='xs:string'>
-          <xs:attribute name='caption' use='optional'/> 
+          <xs:attribute name='caption' use='optional'/>
         </xs:extension>
       </xs:simpleContent>
     </xs:complexType>
@@ -776,7 +776,7 @@ THE SOFTWARE.
     <xs:complexType>
       <xs:simpleContent>
         <xs:extension base='xs:string'>
-          <xs:attribute name='caption' use='optional'/> 
+          <xs:attribute name='caption' use='optional'/>
         </xs:extension>
       </xs:simpleContent>
     </xs:complexType>
@@ -804,8 +804,8 @@ THE SOFTWARE.
     <xs:complexType>
       <xs:simpleContent>
         <xs:extension base='xs:string'>
-          <xs:attribute name='colspan' use='optional'/> 
-          <xs:attribute name='rowspan' use='optional'/> 
+          <xs:attribute name='colspan' use='optional'/>
+          <xs:attribute name='rowspan' use='optional'/>
         </xs:extension>
       </xs:simpleContent>
     </xs:complexType>
@@ -815,8 +815,8 @@ THE SOFTWARE.
     <xs:complexType>
       <xs:simpleContent>
         <xs:extension base='xs:string'>
-          <xs:attribute name='colspan' use='optional'/> 
-          <xs:attribute name='rowspan' use='optional'/> 
+          <xs:attribute name='colspan' use='optional'/>
+          <xs:attribute name='rowspan' use='optional'/>
         </xs:extension>
       </xs:simpleContent>
     </xs:complexType>

diff --git a/xep-0004.xml b/xep-0004.xml
@@ -317,7 +317,7 @@
     type='get'
     xml:lang='en'
     id='create1'>
-  <command xmlns='http://jabber.org/protocol/commands' 
+  <command xmlns='http://jabber.org/protocol/commands'
            node='create'
            action='execute'/>
 </iq>
@@ -481,7 +481,7 @@
     type='get'
     xml:lang='en'
     id='search1'>
-  <command xmlns='http://jabber.org/protocol/commands' 
+  <command xmlns='http://jabber.org/protocol/commands'
            node='search'
            action='execute'/>
 </iq>
@@ -492,7 +492,7 @@
     type='result'
     xml:lang='en'
     id='search1'>
-  <command xmlns='http://jabber.org/protocol/commands' 
+  <command xmlns='http://jabber.org/protocol/commands'
            node='search'
            status='executing'>
     <x xmlns='jabber:x:data' type='form'>
@@ -512,7 +512,7 @@
     type='get'
     xml:lang='en'
     id='search2'>
-  <command xmlns='http://jabber.org/protocol/commands' 
+  <command xmlns='http://jabber.org/protocol/commands'
            node='search'>
     <x xmlns='jabber:x:data' type='submit'>
       <field type='text-single' var='search_request'>
@@ -528,7 +528,7 @@
     type='result'
     xml:lang='en'
     id='search2'>
-  <command xmlns='http://jabber.org/protocol/commands' 
+  <command xmlns='http://jabber.org/protocol/commands'
            node='search'
            status='completed'>
     <x xmlns='jabber:x:data' type='result'>
@@ -642,9 +642,9 @@
   <xs:element name='x'>
     <xs:complexType>
       <xs:sequence>
-        <xs:element name='instructions' 
-                    minOccurs='0' 
-                    maxOccurs='unbounded' 
+        <xs:element name='instructions'
+                    minOccurs='0'
+                    maxOccurs='unbounded'
                     type='xs:string'/>
         <xs:element name='title' minOccurs='0' type='xs:string'/>
         <xs:element ref='field' minOccurs='0' maxOccurs='unbounded'/>

diff --git a/xep-0007.xml b/xep-0007.xml
@@ -70,7 +70,7 @@
     <li>The "groupchat" protocol has no way of performing feature negotiation (e.g., specifying the additional protocol elements needed to participate in a room, or optionally allowed from participants within a room). If there were participants with clients sending custom data through the room (such as XHTML or whiteboarding), you would receive that information even without your client being able to support it, and have no way of distinguishing altered behavior due to additional features of a "groupchat" implementation.</li>
   </ul>
   <p>This new conferencing protocol will be designed to solve these problems.</p>
-  <p>Because of the prevalence of the existing "groupchat" specification for multi-user chats, a long conversion process is anticipated.  A server implementation which supports both protocols will simply not allow "groupchat"-only clients to participate in rooms with required features.</p> 
+  <p>Because of the prevalence of the existing "groupchat" specification for multi-user chats, a long conversion process is anticipated.  A server implementation which supports both protocols will simply not allow "groupchat"-only clients to participate in rooms with required features.</p>
 </section1>
 <section1 topic='Continuing Development'>
   <p>As listed above, there is a fairly large number of features that could be developed on top of a well-designed framework. The Conferencing SIG will first be established to develop a framework, with features mainly being compared against the framework for feasibility of implementation. After a proposal has been formalized as a specification, the SIG will become a group for discussing and proposing new features, and for formally specifying those features.</p>

diff --git a/xep-0009.xml b/xep-0009.xml
@@ -5,7 +5,7 @@
 ]>
 <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
 <xep>
-<header>	
+<header>
   <title>Jabber-RPC</title>
   <abstract>This specification defines an XMPP protocol extension for transporting XML-RPC encoded requests and responses between two XMPP entities. The protocol supports all syntax and semantics of XML-RPC except that it uses XMPP instead of HTTP as the underlying transport.</abstract>
   &LEGALNOTICE;
@@ -74,9 +74,9 @@
 </section1>
 <section1 topic='Examples'>
   <example caption='A typical request'><![CDATA[
-<iq type='set' 
-    from='[email protected]/jrpc-client' 
-    to='[email protected]/jrpc-server' 
+<iq type='set'
+    from='[email protected]/jrpc-client'
+    to='[email protected]/jrpc-server'
     id='rpc1'>
   <query xmlns='jabber:iq:rpc'>
     <methodCall>
@@ -91,9 +91,9 @@
 </iq>
   ]]></example>
   <example caption='A typical response'><![CDATA[
-<iq type='result' 
-    from='[email protected]/jrpc-server' 
-    to='[email protected]/jrpc-client' 
+<iq type='result'
+    from='[email protected]/jrpc-server'
+    to='[email protected]/jrpc-client'
     id='rpc1'>
   <query xmlns='jabber:iq:rpc'>
     <methodResponse>
@@ -108,9 +108,9 @@
   ]]></example>
   <p>If the requesting entity does not have sufficient permissions to perform remote procedure calls, the responding entity MUST return a &forbidden; error:</p>
   <example caption='Requesting entity is forbidden to perform remote procedure calls'><![CDATA[
-<iq type='error' 
-    from='[email protected]/jrpc-server' 
-    to='[email protected]/jrpc-client' 
+<iq type='error'
+    from='[email protected]/jrpc-server'
+    to='[email protected]/jrpc-client'
     id='rpc1'>
   <query xmlns='jabber:iq:rpc'>
     <methodCall>
@@ -131,17 +131,17 @@
 <section1 topic='Service Discovery' anchor='disco'>
   <p>If an entity supports the Jabber-RPC protocol, it SHOULD advertise that fact in response to &xep0030; information ("diso#info") requests by returning an identity of "automation/rpc" and a feature of "jabber:iq:rpc":</p>
   <example caption='A disco#info query'><![CDATA[
-<iq type='get' 
-    from='[email protected]/jrpc-client' 
-    to='[email protected]/jrpc-server' 
+<iq type='get'
+    from='[email protected]/jrpc-client'
+    to='[email protected]/jrpc-server'
     id='disco1'>
   <query xmlns='http://jabber.org/protocol/disco#info'/>
 </iq>
   ]]></example>
   <example caption='A disco#info response'><![CDATA[
-<iq type='result' 
-    to='[email protected]/jrpc-client' 
-    from='[email protected]/jrpc-server' 
+<iq type='result'
+    to='[email protected]/jrpc-client'
+    from='[email protected]/jrpc-server'
     id='disco1'>
   <query xmlns='http://jabber.org/protocol/disco#info'>
     <identity category='automation' type='rpc'/>
@@ -179,9 +179,9 @@
       The protocol documented by this schema is defined in
       XEP-0009: http://www.xmpp.org/extensions/xep-0009.html
 
-      There is no official XML schema for XML-RPC. The main body 
-      of this schema has been borrowed from an unofficial schema 
-      representation contained in the book "Processing XML With 
+      There is no official XML schema for XML-RPC. The main body
+      of this schema has been borrowed from an unofficial schema
+      representation contained in the book "Processing XML With
       Java" by Elliotte Rusty Harold, as located at:
 
       http://www.ibiblio.org/xml/books/xmljava/chapters/ch02s05.html
@@ -210,13 +210,13 @@
         <xs:element name="params" minOccurs="0" maxOccurs="1">
           <xs:complexType>
             <xs:sequence>
-              <xs:element name="param"  type="ParamType" 
+              <xs:element name="param"  type="ParamType"
                            minOccurs="0" maxOccurs="unbounded"/>
             </xs:sequence>
           </xs:complexType>
          </xs:element>
       </xs:all>
-    </xs:complexType>  
+    </xs:complexType>
   </xs:element>
 
   <xs:element name="methodResponse">
@@ -236,13 +236,13 @@
               <xs:element name="value">
                 <xs:complexType>
                   <xs:sequence>
-                    <xs:element name="struct"> 
-                      <xs:complexType> 
-                        <xs:sequence> 
-                          <xs:element name="member" 
+                    <xs:element name="struct">
+                      <xs:complexType>
+                        <xs:sequence>
+                          <xs:element name="member"
                                        type="MemberType">
                           </xs:element>
-                          <xs:element name="member" 
+                          <xs:element name="member"
                                        type="MemberType">
                           </xs:element>
                         </xs:sequence>
@@ -255,7 +255,7 @@
           </xs:complexType>
          </xs:element>
       </xs:choice>
-    </xs:complexType>  
+    </xs:complexType>
   </xs:element>
 
   <xs:complexType name="ParamType">
@@ -286,7 +286,7 @@
 
   <xs:complexType name="StructType">
     <xs:sequence>
-      <xs:element name="member" type="MemberType" 
+      <xs:element name="member" type="MemberType"
                    maxOccurs="unbounded"/>
     </xs:sequence>
   </xs:complexType>
@@ -303,7 +303,7 @@
       <xs:element name="data">
         <xs:complexType>
           <xs:sequence>
-            <xs:element name="value"  type="ValueType" 
+            <xs:element name="value"  type="ValueType"
                          minOccurs="0" maxOccurs="unbounded"/>
           </xs:sequence>
         </xs:complexType>