XEP-0136: advance status to Deprecated.

xep-0136.xml

@@ -10,7 +10,7 @@
   <abstract>This document defines mechanisms and preferences for the server-side archiving and retrieval of XMPP messages.</abstract>
   &LEGALNOTICE;
   <number>0136</number>
-  <status>Draft</status>
+  <status>Deprecated</status>
   <type>Standards Track</type>
   <sig>Standards</sig>
   <dependencies>
@@ -21,7 +21,7 @@
     <spec>XEP-0060</spec>
   </dependencies>
   <supersedes/>
-  <supersededby/>
+  <supersededby><spec>XEP-0313</spec></supersededby>
   <shortname>archive</shortname>
   <schemaloc>
     <url>http://www.xmpp.org/schemas/archive.xsd</url>
@@ -45,6 +45,12 @@
     <surname>Leboulanger</surname>
     <email>asterix@lagaule.org</email>
   </author>
+  <revision>
+    <version>1.3</version>
+    <date>2017-11-15</date>
+    <initials>XEP Editor (ssw)</initials>
+    <remark><p>Per a vote of the XMPP Council, advanced status to Deprecated.</p></remark>
+  </revision>
   <revision>
     <version>1.2</version>
     <date>2010-06-21</date>
@@ -299,7 +305,7 @@
       <section4 topic='timeout Attribute' anchor='pref-syntax-timeout'>
         <p>The 'timeout' attribute indicates how long this rule will stay in server after the latest message in this thread is exchanged. Server MUST NOT forget this rule before 'timeout' seconds after latest message in this thread is exchanged but MAY keep this rule longer than 'timeout' value specifies.</p>
         <p>Client MUST NOT set this attribute, but wait for server's answer to know this value.</p>
-	<p>If the client wants to keep this rule longer, it must send a new &lt;session/&gt; element to the server before this timeout expires.</p>
+        <p>If the client wants to keep this rule longer, it must send a new &lt;session/&gt; element to the server before this timeout expires.</p>
       </section4>
       <section4 topic='thread Attribute' anchor='pref-syntax-thread'>
         <p>The 'thread' attribute specifies the ThreadID of the chat session (in the sense of &xep0201;) to which the preferences specified in this &lt;session/&gt; element apply.</p>
@@ -450,7 +456,7 @@
 ]]></example>
   </section2>
   <section2 topic='Setting Modes for a Chat Session' anchor='pref-session'>
-	  <p>A client may use a similar protocol to set the Modes for a particular chat session. A chat session is identified by its unique 'thread' attributes in &lt;message&gt; stanza (see &xep0155;).</p>
+    <p>A client may use a similar protocol to set the Modes for a particular chat session. A chat session is identified by its unique 'thread' attributes in &lt;message&gt; stanza (see &xep0155;).</p>
     <example caption='Client Sets Modes for a Chat Session'><![CDATA[
 <iq type='set' id='pref4'>
   <pref xmlns='urn:xmpp:archive'>
@@ -878,7 +884,7 @@
 ]]></example>
   <p>Otherwise:</p>
   <ul>
-	  <li>Automatic archiving MUST default to enabled or disabled when each stream is opened according to the last value of &lt;auto/&gt; element if 'scope' was set to 'global' (see <link url='#pref-syntax-auto'>Auto element</link>), else Automatic archiving MUST default disabled.</li>
+    <li>Automatic archiving MUST default to enabled or disabled when each stream is opened according to the last value of &lt;auto/&gt; element if 'scope' was set to 'global' (see <link url='#pref-syntax-auto'>Auto element</link>), else Automatic archiving MUST default disabled.</li>
     <li>A client MAY enable or disable automatic archiving for messages sent over its stream at any time. Note: If the client switches off all auto-archiving then the server MUST close and archive all active collections.</li>
     <li>Once automatic archiving is switched on then the server MUST automatically archive messages only according to the user's <link url='#pref'>Archiving Preferences</link>.</li>
     <li>Note: Both parties to an ESession (see &xep0116;) SHOULD either disable archiving or use an archiving method other than automatic, since ESession decryption keys are short-lived -- making it impossible to decrypt automatically archived messages.</li>