XEP-0045: Presence sent to occupants of a destroyed room includes a `…

…<destroy/>` element

Even if no reason or alternate venue is provided, a `<destroy/>` element is needed to distinguish between other presence unavailable.

xep-0045.xml

@@ -48,7 +48,7 @@
   &stpeter;
   <revision>
     <version>1.34.7</version>
-    <date>2024-07-12</date>
+    <date>2024-07-13</date>
     <initials>gk</initials>
     <remark>
       <ul>
@@ -58,6 +58,7 @@
         <li>Improved 'Service Removes Non-Member' example.</li>
         <li>Clarify usage of presence stanzas when removing a non-member from a members-only room.</li>
         <li>Replace inappropriate RFC 2119 key word usage in §9.7.</li>
+        <li>Presence sent to occupants of a destroyed room includes a &lt;destroy/&gt; element.</li>
       </ul>
     </remark>
   </revision>
@@ -4902,7 +4903,8 @@
   </query>
 </iq>
 ]]></example>
-    <p>The service is responsible for removing all the occupants. It SHOULD NOT broadcast presence stanzas of type "unavailable" from all occupants, instead sending only one presence stanza of type "unavailable" to each occupant so that the user knows he or she has been removed from the room. If extended presence information specifying the JID of an alternate location and the reason for the room destruction was provided by the room owner, the presence stanza MUST include that information.</p>
+    <p>The service is responsible for removing all the occupants. It SHOULD NOT broadcast presence stanzas of type "unavailable" from all occupants, instead sending only one presence stanza of type "unavailable" to each occupant so that the user knows he or she has been removed from the room. The extended presence information of the stanza MUST include &lt;destroy/&gt; element. If extended information specifying the JID of an alternate location and/or the reason for the room destruction was provided by the room owner, the presence stanza MUST include that information.</p>
+    <p>Note: in older versions of this standard, the inclusion of a &lt;destroy/&gt; element was not explicitly defined to be mandatory (when no alternate location or reason are provided by the room owner). Implementations therefore cannot reliably depend on the existence of this element to identify a room destruction event.</p>
     <example caption='Service Removes Each Occupant'><![CDATA[
 <presence
     from='[email protected]/firstwitch'