moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 15:18:51 -05:00
Code Issues Releases Wiki Activity

0.2

Browse Source
This commit is contained in:
Peter Saint-Andre 2013-09-05 10:28:13 -06:00
parent 4a0e5b86ad
commit 9d471ebe9a
1 changed files with 14 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
xep-0333.xml
View File

@ -27,6 +27,12 @@
<email>im@spencermacdonald.com</email>
<jid>im@spencermacdonald.com</jid>
</author>
<revision>
<version>0.2</version>
<date>2013-09-05</date>
<initials>sdm</initials>
<remark><p>Moved Thread outside of the Chat Marker.</p></remark>
</revision>
<revision>
<version>0.1</version>
<date>2013-07-11</date>
@ -141,7 +147,7 @@
<section1 topic='Protocol Format' anchor='format'>
<p>Chat Markers use a dedicated protocol extension qualified by the 'urn:xmpp:chat-markers:0' namespace.</p>
<p>There are 4 allowable elements in the namespace, the first 'markable' indicates that a message can be marked with a Chat Marker and is therefore a markable message.</p>
<p>There are 4 allowable elements in the namespace, the first 'markable' indicates that a message can be marked with a Chat Marker and is therefore a "markable message".</p>
<p>The 3 other allowable elements in this namespace are used to mark a message (in order of significance):</p>
<ul>
<li>received -- the message has been received by a client.</li>
@ -150,7 +156,7 @@
</ul>
<p>The Chat Marker MUST have an 'id' which is the 'id' of the message being marked.</p>
<p>The Chat Marker MUST have a 'thread' if the message has been received, displayed or acknowledged in the context of a thread.</p>
<p>The Chat Marker message stanza MUST have a 'thread' child element if the message has been received, displayed or acknowledged in the context of a thread.</p>
<p>A Chat Marker Indicates that all messages up to and including that message 'id' have been marked. If a thread is supplied, a Chat Marker is only valid in the context of that thread.</p>
<example caption='Example Content Message with a markable Chat Marker'>
@ -160,7 +166,7 @@
id='message-1'
to='ingrichard@royalty.england.lit/throne'>
<thread>sleeping</thread>
<body>>My lord, dispatch; read o'er these articles.</body>
<body>My lord, dispatch; read o'er these articles.</body>
<markable xmlns='urn:xmpp:chat-markers:0'/>
</message>
]]>
@ -176,18 +182,18 @@
from='kingrichard@royalty.england.lit/throne'
id='message-2'
to='northumberland@shakespeare.lit/westminster'>
<thread>sleeping</thread>
<received xmlns='urn:xmpp:chat-markers:0'
id='message-1'
thread='sleeping'/>
id='message-1'/>
</message>
]]>
</example>
<p>When the recipient sends a Chat Marker, it SHOULD ensure that the message stanza contains only the Chat Marker child element. Naturally, intermediate entities might add other extension elements to the message when routing or delivering the receipt message, e.g., a &lt;delay/&gt; element as specified in &xep0203;.</p>
<p>When the recipient sends a Chat Marker, it SHOULD ensure that the message stanza contains only the Chat Marker child element and optionally (when appropriate) a thread child element. Naturally, intermediate entities might add other extension elements to the message when routing or delivering the receipt message, e.g., a &lt;delay/&gt; element as specified in &xep0203;.</p>
</section1>
<section1 topic='Requirements' anchor='requirements'>
<p>Clients SHOULD use &xep0280; to support multiple online resources.</p>
<p>Clients SHOULD use &xep0136; or &xep0313; to support offline updating of Chat Markers. Chat Markers SHOULD be archived, so they can be fetched and set regardless of wether the other users in a chat are online.</p>
<p>Clients SHOULD use &xep0136; or &xep0313; to support offline updating of Chat Markers. Chat Markers SHOULD be archived, so they can be fetched and set regardless of whether the other users in a chat are online.</p>
<p>Messages MUST have an 'id' to use Chat Markers.</p>
<p>Messages MUST include the 'markable' element to use Chat Markers.</p>
<p>Chat Markers MUST only move forward. If a Chat Maker is received for an earlier message than the current Chat Marker, it MUST be ignored by the client.
@ -246,7 +252,7 @@
<xs:annotation>
<xs:documentation>
The protocol documented by this schema is defined in
XEP-XXXX: http://xmpp.org/extensions/xep-XXXX.html
XEP-0333: http://xmpp.org/extensions/xep-0333.html
</xs:documentation>
</xs:annotation>
@ -264,7 +270,6 @@
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute type="xs:string" name="id"/>
<xs:attribute type="xs:string" name="thread"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
@ -275,7 +280,6 @@
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute type="xs:string" name="id"/>
<xs:attribute type="xs:string" name="thread"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
@ -287,7 +291,6 @@
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute type="xs:string" name="id"/>
<xs:attribute type="xs:string" name="thread"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>