From 084bc5c31b6d53662902c5ff95be0d0c8575abb4 Mon Sep 17 00:00:00 2001
From: Sam Whited <sam@samwhited.com>
Date: Wed, 7 Dec 2016 10:36:02 -0600
Subject: [PATCH] Publish spoilers as XEP-0382

---
 inbox/spoiler.xml => xep-0382.xml | 36 +++++++++++++++++--------------
 1 file changed, 20 insertions(+), 16 deletions(-)
 rename inbox/spoiler.xml => xep-0382.xml (87%)

diff --git a/inbox/spoiler.xml b/xep-0382.xml
similarity index 87%
rename from inbox/spoiler.xml
rename to xep-0382.xml
index 5b8c5c8d..f3bcc227 100644
--- a/inbox/spoiler.xml
+++ b/xep-0382.xml
@@ -13,8 +13,8 @@
       such.
     </abstract>
     &LEGALNOTICE;
-    <number>xxxx</number>
-    <status>ProtoXEP</status>
+    <number>0382</number>
+    <status>Experimental</status>
     <type>Standards Track</type>
     <sig>Standards</sig>
     <approver>Council</approver>
@@ -23,7 +23,7 @@
     </dependencies>
     <supersedes/>
     <supersededby/>
-    <shortname>NOT_YET_ASSIGNED</shortname>
+    <shortname>spoilers</shortname>
     <author>
       <firstname>Severino</firstname>
       <surname>Ferrer de la Peñita</surname>
@@ -36,6 +36,12 @@
       <email>vaulor@openmailbox.org</email>
       <jid>vaulor@blastersklan.com</jid>
     </author>
+    <revision>
+      <version>0.1</version>
+      <date>2016-12-07</date>
+      <initials>XEP Editor: ssw</initials>
+      <remark><p>Initial version approved by the council.</p></remark>
+    </revision>
     <revision>
       <version>0.0.2</version>
       <date>2016-10-31</date>
@@ -123,18 +129,16 @@
 ]]></example>
     </section1>
   <section1 topic='Business Rules' anchor='rules'>
-    <p>
-      <ol>
-        <li>It MUST be clear that a message is in fact a spoiler and its content MUST only be displayed upon
-            user's request.</li>
-        <li>Clients MAY provide a way to display spoilers always uncovered, without the need of interaction
-            by the user (e.g. in the client's settings).</li>
-        <li>Clients SHOULD display spoiler's hint, if any, before showing message's content.</li>
-        <li>Clients MAY display spoiler's hint even after showing message's content (e.g. as a header or
-            title of the message).</li>
-        <li>Users SHOULD uncover or hide a spoiler message at will, anytime.</li>
-     </ol>
-    </p>
+    <ol>
+      <li>It MUST be clear that a message is in fact a spoiler and its content MUST only be displayed upon
+        user's request.</li>
+      <li>Clients MAY provide a way to display spoilers always uncovered, without the need of interaction
+        by the user (e.g. in the client's settings).</li>
+      <li>Clients SHOULD display spoiler's hint, if any, before showing message's content.</li>
+      <li>Clients MAY display spoiler's hint even after showing message's content (e.g. as a header or
+        title of the message).</li>
+      <li>Users SHOULD uncover or hide a spoiler message at will, anytime.</li>
+    </ol>
   </section1>
   <section1 topic='Security Considerations' anchor='security'>
     <p>
@@ -161,7 +165,7 @@
 <var>
   <name>urn:xmpp:spoiler:0</name>
   <desc>Indicates that a message's content should not be displayed by default.</desc>
-  <doc>xxxx</doc>
+  <doc>0382</doc>
 </var>
 ]]></code>
     </section2>