moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-24 02:02:16 -05:00
Code Issues Releases Wiki Activity

XEP-0184: Require the 'id' attribute in <received/>.

Browse Source 
There was no way to implement this specification while not using the
'id' attribute, this makes it explicit in both the text and the schema.
This commit is contained in:
Emmanuel Gil Peyrot 2018-08-02 19:20:54 +02:00
parent 12eb7de93a
commit fd92e36127
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
xep-0184.xml
View File

@ -27,6 +27,12 @@
</schemaloc> </schemaloc>
&stpeter; &stpeter;
&hildjj; &hildjj;
<revision>
<version>1.4.0</version>
<date>2018-08-02</date>
<initials>egp</initials>
<remark><p>Make the 'id' attribute required, this extension makes no sense otherwise.</p></remark>
</revision>
<revision> <revision>
<version>1.3.0</version> <version>1.3.0</version>
<date>2019-05-15</date> <date>2019-05-15</date>
@ -209,7 +215,7 @@
<received xmlns='urn:xmpp:receipts' id='richard2-4.1.247'/> <received xmlns='urn:xmpp:receipts' id='richard2-4.1.247'/>
</message> </message>
]]></example> ]]></example>
<p>When the recipient sends an ack message, it SHOULD ensure that the message stanza contains only one child element, namely the &lt;received/&gt; element qualified by the 'urn:xmpp:receipts' namespace. In addition, it SHOULD include an 'id' attribute that echoes the 'id' attribute of the content message. 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 an ack message, it SHOULD ensure that the message stanza contains only one child element, namely the &lt;received/&gt; element qualified by the 'urn:xmpp:receipts' namespace, which MUST include an 'id' attribute that echoes the 'id' attribute of the content message. 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 class='box'>Note: It is a good practice to use the same message type as the message that requested the receipt, however a client SHOULD also accept receipts with a different message type. When sending a Receipt for a type='groupchat' message (which is NOT RECOMMENDED), the Receipt must be sent to the bare JID of the room and not to the full JID of the sender.</p> <p class='box'>Note: It is a good practice to use the same message type as the message that requested the receipt, however a client SHOULD also accept receipts with a different message type. When sending a Receipt for a type='groupchat' message (which is NOT RECOMMENDED), the Receipt must be sent to the bare JID of the room and not to the full JID of the sender.</p>
</section1> </section1>
@ -248,7 +254,7 @@
<xs:complexType> <xs:complexType>
<xs:simpleContent> <xs:simpleContent>
<xs:extension base='empty'> <xs:extension base='empty'>
<xs:attribute name='id' type='xs:string' use='optional'/> <xs:attribute name='id' type='xs:string' use='required'/>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>