<abstract>This document specifies an XMPP extension for use of the vCard4 XML format in XMPP systems, with the intent of obsoleting the vcard-temp format.</abstract>
<remark><p>Reword note about how to handle LMC in cases where it is not clear that all recipients support it.</p></remark>
</revision>
<revision>
<version>1.1.0</version>
<date>2019-05-15</date>
@ -80,7 +86,7 @@
...
</query>
</iq>]]></example>
<p>It is expected that clients will not send message corrections to clients that do not support them, as non-supporting clients will render these as duplicate (corrected) messages. There may be environments (particularly within a &xep0045; MUC room) where it is unknown whether some or all recipients support this extension, and implementors could choose to allow or disallow sending in such cases, as is appropriate for the intended deployments. It is suggested that when the support of recipients is not known a sending client will make the user aware of the potential for duplicate messages to be interpreted by the recipients.</p>
<p>Message corrections sent to clients that do not support them will be rendered as duplicate (corrected) messages. In most Instant Messaging environments (particularly within a &xep0045; room, but also with a recipient having multiple clients using &xep0280; and &xep0313;) it is unknown whether some or all receiving devices support this extension. It is suggested that a client should always allow sending corrections, but may make the user aware of the potential for duplicate messages to be interpreted by the recipients. In restricted environments, implementors could choose to allow or disallow sending in such cases, as is appropriate for the intended deployments.</p>
</section1>
<section1topic='Use Case'anchor='usecase'>
<p>When a user indicates to the client that he wants to correct the most recently sent message to a contact, the client will resend the corrected message with a new id, and with the replace payload refering to the previous message by id. The receiving client then treats the newly received payloads as completely replacing all payloads of the original message.</p>
<abstract>This specification provides a way for the initiator of a Jingle session to propose sending an invitation in an XMPP message stanza, thus taking advantage of message delivery semantics instead of sending IQ stanzas to all of the responder's online resources or choosing a particular online resource.</abstract>
<abstract>This specification describes a method to migrate to PEP based bookmarks without loosing compatibility with client that still use Private XML.</abstract>
&LEGALNOTICE;
<number>0411</number>
<status>Proposed</status>
<status>Draft</status>
<lastcall>2020-10-14</lastcall>
<type>Standards Track</type>
<sig>Standards</sig>
@ -29,6 +29,12 @@
<email>daniel@gultsch.de</email>
<jid>daniel@gultsch.de</jid>
</author>
<revision>
<version>1.0.0</version>
<date>2020-10-20</date>
<initials>XEP Editor (jsc)</initials>
<remark>Accepted as Draft by vote of Council on 2020-10-14.</remark>
Jonas Schäfer
3 years ago