%ents; ]>
Message Attaching This specification defines a method for indicating that a message contains content which describes an earlier message in the conversation and should be grouped with the earlier message. &LEGALNOTICE; 0367 Experimental Standards Track Standards Council XMPP Core XEP-0359 message-attaching &sam; Craig Petchell cpetchell@atlassian.com &mwild; 0.3 2018-08-18 mw Update to use unique stanza ids. 0.2 2017-09-11 XEP Editor (jwi) Defer due to lack of activity. 0.1 2015-12-15 XEP Editor (asw)

Initial published version approved by the XMPP Council.

 0.0.1 2015-10-16 ssw

First draft.

Many messaging applications send special messages which include more information about a previous message. For example, when sending a link the service may display the description or an image off the page, or users may respond to a message with a "sticker" or an "emotion" which they wish to display alongside the message, even though the conversation has moved on.

This specification defines a way by which one can indicate that a message is logically (and visibly) "attached" to an earlier message in the conversation.

If a client implements message attaching, it MUST specify the 'urn:xmpp:message-attaching:1' feature in its service discovery information features as specified in &xep0030; and the Entity Capabilities profile specified in &xep0115;.

]]> … … ]]>

Messages that are attached to other messages MUST contain an <attach-to/> element qualified by the 'urn:xmpp:message-attaching:1' namespace and with an 'id' attribute set to the ID of the message that we want to attach to (important note: the correct ID to use depends on the context, see the business rules below). Messages MAY be attached to any other message, including those sent by other clients, but clients MAY choose to ignore the attach-to directive and display the message normally.

storm.png ]]>

Note that indicating that a message should be "attached" to an earlier message in the conversation is merely a suggestion to the client to display the message next to or below the old message.

For messages of type 'groupchat', the stanza's 'id' attribute MUST NOT be used for attachments. Instead, in group chat situations, the ID assigned to the stanza by the group chat itself must be used. This is discovered in a <stanza-id> element with a 'by' attribute that matches the bare JID of the group chat, as defined in &xep0359;.

This implies that group chat messages without a &xep0359; stanza-id cannot be attached-to.

For other message types the attacher should use the 'id' from a XEP-0359 <origin-id> if present, or the value of the 'id' attribute on the <message> otherwise.

A receiving client MAY choose to show the attached message next to or below the indicated message in whatever display is used for messages or can choose to display the attachment in another way (including as a normal message, completely ignoring the attach-to element).

A receiving client SHOULD indicate that the message is an attachment, and not a part of the original message to prevent confusion.

<attach-to/> elements MUST NOT be put on any stanza type other than messages.

A server may choose to strip some <attach-to/> messages based on local policy (eg. a server might have a policy that only it can create message attachments).

Clients MUST send ids on messages if they support attachments.

Messages MUST NOT contain more than one <attach-to/> element.

Clients and servers MUST NOT include an <attach-to/> element on messages with a non-messaging payload unless they are including it on an error which may be attached to the message that caused the error to be generated.

Clients that implement message attachments MUST display the attachments in such a way that they could not be confused with the original message and cause someone viewing the conversation to assume they were sent by the sender of the message being attached to.

When matching a received attachment to the original message, clients must ensure they match using the correct ID, as described in the business rules section, e.g. within a group chat only the XEP-0359 stanza-id should be matched against. If this is not available, the message SHOULD be displayed as a normal unattached message.

This document requires no interaction with &IANA;.

This specification defines the following XML namespaces:

The ®ISTRAR; shall include the foregoing namespaces in its disco features registry as defined in &xep0030;.

urn:xmpp:message-attaching:1 Indicates support for attaching one message to another. XEP-xxxx ]]> ]]>