XEP-0313: Add anchor IDs

xep-0313.xml

@@ -525,16 +525,16 @@
 </section1>
 
 <section1 topic='Business Rules' anchor='business_rules'>
-  <section2 topic='Storage and Retrieval Rules'>
+  <section2 topic='Storage and Retrieval Rules' anchor='business-storeret'>
   	<p>Different entities will have different requirements for which data are stored, as might different deployments. This section provides general rules within which a server will act. While there may be local policy restrictions that prevent archiving of some aspects discussed here, this is a RECOMMENDED baseline. A server MAY implement any subset of possible archives for JIDs it controls (although it MUST advertise support only for those JIDs that support it).</p>
 	<p>No requirements are placed on how a server implements its storage beyond that it has to store data sufficient to be able to comply with this document. When this document describes storage requirements (e.g. MUST NOT store more than one copy...), it refers to what would appear to have been stored in order to satisfy the query.</p>
     <p>If an entity (user's server, MUC room, pubsub node, ...) rejects an incoming message (such as from an occupant not allowed to send messages to the room, a user not authorized to publish to a pubsub node, a contact blocked by the user etc.) that message should not appear in the archive for the entity that rejected it - the archive should represent what logical entities (MUC occupants, users, pubsub subscribers...) would have received, and so only contain messages accepted for delivery to such entities.</p>
-  	<section3 topic="User Archives">
+  	<section3 topic="User Archives" anchor='business-storeret-user-archives'>
   		<p>A user archive is anticipated to provide the user with the ability to access their prior conversations. To this end, a server SHOULD include in a user archive all of the messages a user sends or receives of type 'normal' or 'chat' that contain a &lt;body&gt; element. A server SHOULD also include messages of type 'groupchat' that have a &lt;body&gt;, but where such history is accessible through another method (e.g. through an archive on the MUC JID), a server MAY exclude these from the archive. A server MAY include additional non-conversation messages. A server MAY include messages of type 'headline', but this is not generally suggested.</p>
   		<p>At a minimum, the server MUST store the &lt;body&gt; elements of a stanza. It is suggested that other elements that are used in a given deployment to supplement conversations (e.g. XHTML-IM payloads) are also stored. Other elements MAY be stored.</p>
   		<p>If a server supports mechanisms that multiply copies of a stanza (e.g. Carbons, or forking a stanza to a bare JID), it MUST store such a staza within a given archive only once, irrespective of multiple connected clients receiving copies</p>
   	</section3>
-  	<section3 topic="MUC Archives">
+  	<section3 topic="MUC Archives" anchor='business-storeret-muc-archives'>
   		<p>A MUC archives allows a user to view the conversation within a room. All messages sent to the room that contain a &lt;body&gt; element SHOULD be stored, as should subject change stanzas, apart from those messages that the room rejects.</p>
   		<p>A MUC archive MUST store each message only once (not, for example, every copy sent out to an occupant).</p>
                 <p>A MUC archive MUST NOT include 'private message' results (those sent directly between occupants, not shared in the room) in the results</p>
@@ -581,7 +581,7 @@
 </message>
                 ]]></example>
   	</section3>
-  	<section3 topic="Pubsub Archives">
+  	<section3 topic="Pubsub Archives" anchor='business-storeret-pubsub-archives'>
   		<p>A PubSub service offering MAM SHOULD store each of the items published to each node. When responding to MAM requests it MUST construct the message stanza within the &lt;forwarded&gt; element in the same manner as the notifications sent to subscribers for the item, except that specifying the 'from' 'to' and 'id' attributes are OPTIONAL. Pubsub items must be returned one per message stanza (i.e. there MUST NOT be multiple &lt;item&gt; elements within the &lt;items&gt; element).</p>
   		<example caption='Server returns a pubsub messages'><![CDATA[
 <message id='iasd208' to='juliet@capulet.lit/chamber'>
@@ -617,7 +617,7 @@
   </section3>
 
   </section2>
-  <section2 topic='IDs'>
+  <section2 topic='IDs' anchor='business-ids'>
         <p>The IDs used within an archive MUST be unique per item stored and MUST NOT be reused, even if the original item with a given ID has since been removed from the archive. If a server provides multiple archives (e.g. many user archives, or many MUC archives), the IDs do not need to be unique across all of these archives unless the server also allows a single query to be run across multiple archives (e.g. searching of all MUC rooms), discussion of which is beyond the scope of this document. These IDs are strings that servers may construct in any manner, and clients must treat as opaque strings (e.g. there is no requirement for them to be numeric, sequenced or GUIDs).</p>
   </section2>
   <section2 topic='Client synchronization' anchor='sync'>
@@ -821,7 +821,7 @@
   <section2 topic='Stanza IDs' anchor='security-stanza-ids'>
     <p>Entities that implement this specification must also adhere to the security requirements of XEP-0359.</p>
   </section2>
-  <section2 topic='MUC message spoofing'>
+  <section2 topic='MUC message spoofing' anchor='security-muc-spoofing'>
     <p>This specification re-uses the &lt;x&gt; element from the 'http://jabber.org/protocol/muc#user' namespace to convey information about the sender of a message in a MUC room. However this element is not sanitized by MUC services, so the archiving entity MUST strip any existing &lt;x&gt; element in the 'http://jabber.org/protocol/muc#user' namespace from messages before archiving them (regardless of whether it adds in its own &lt;x&gt; element).</p>
   </section2>
 </section1>