[Standards] NEW: XEP-0308 (Last Message Correction)- Interop with XEP 0301 RTT
markybox at gmail.com
Thu Jul 19 22:12:58 UTC 2012
Here is a proposed amendment to XEP-0301 for full compatibility between
XEP-0301 and XEP-0308, to accommodate agreement between myself, Lance,
Peter, and Kevin.
This OPTIONAL attribute is used only if *Last Message Correction 
is implemented. Sender clients MAY use this attribute to allow recipient
clients to have improved presentation of real-time text during message
correction (e.g. shown as in-place editing of previous message).
This *id *attribute refers to the <message/> stanza containing the <body/>
that is being edited (See 'Business Rules' in XEP-0308). If used at all,
then *id* MUST be included in all <rtt/> elements transmitted during
message correction of the previous message. When switching messages being
edited (i.e. editing the current message versus editing the previous
message), the first <rtt/> element MUST contain an
value, such as 'reset'. See *Message
(This will be a new section 4.2.3 in RTT Attributes
Is this amendment sufficently clear? It is basic, and doesn't provide an
example, and doesn't provide an Implementation Note, but it provides
necessary minimum protocol for syncing up XEP-0301 and XEP-0308.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Standards