XEP-0461: Message Replies

Abstract
This document defines a way to indicate that a message is a reply to a previous message.
Authors
  • Natalie Wirth
  • Marvin Wissfeld
Copyright
© 1999 – 2021 XMPP Standards Foundation. SEE LEGAL NOTICES.
Status

Experimental

WARNING: This Standards-Track document is Experimental. Publication as an XMPP Extension Protocol does not imply approval of this proposal by the XMPP Standards Foundation. Implementation of the protocol described herein is encouraged in exploratory implementations, but production systems are advised to carefully consider whether it is appropriate to deploy implementations of this protocol before it advances to a status of Draft.
Type
Standards Track
Version
0.1.0 (2022-01-25)
Document Lifecycle
  1. Experimental
  2. Proposed
  3. Stable
  4. Final

1. Introduction

When commenting on a previous message, it is sometimes desired to clarify which message the comment refers to. Currently, Message Styling (XEP-0393) [1] quotes are commonly used for that purpose. However, this format does not allow receiving clients to properly identify the referenced message or to adjust the user interface accordingly.

This specification defines a way to indicate that a message is a reply to a previous message. It does not intend to provide means to create sub-threads for a message.

2. Use Cases

To indicate that a message is a reply, a <reply> element in the urn:xmpp:reply:0 namespace is placed in the message stanza. The <reply> element has a 'to' attribute containing the full jid of the author of the referenced message and an 'id' attribute containing the id of the referenced message.

Example 1. Max replies to Anna's message
<message to='max@example.com' from='anna@example.com/tablet' id='message-id1' type='chat'>
  <body>We should bake a cake</body>
</message>

<message to='anna@example.com' id='message-id2' type='chat'>
  <body>Great idea!</body>
  <reply to='anna@example.com/tablet' id='message-id1' xmlns='urn:xmpp:reply:0' />
</message>

2.1 Compatibility Fallback

To provide a fallback for non-supporting clients, the sending client MAY include fallback text in the body and indicate it via Compatibility Fallback.

Example 2. Anna replies to a message and includes a fallback
<message to='anna@example.com' id='message-id3' type='chat'>
  <body>
    > Anna wrote:
    > We should bake a cake
    Great idea!
  </body>
  <reply to='anna@example.com/laptop' id='message-id1' xmlns='urn:xmpp:reply:0' />
  <fallback xmlns='urn:xmpp:feature-fallback:0' for='urn:xmpp:reply:0'>
    <body start="0" end="36" />
  </fallback>
</message>

The receiving client SHOULD NOT display the compatibility fallback if it renders the referenced message alongside the reply in some way. However, if the receiving client does not display the referenced message, for example because it doesn't know the referenced id, it MAY display the compatibility fallback instead.

3. Business Rules

Answers MUST NOT be be assumed to relate to any other messages than the referenced one.

3.1 Using the correct ID

For messages of type 'groupchat', the stanza's 'id' attribute MUST NOT be used for replies. 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 Unique and Stable Stanza IDs (XEP-0359) [2].

This implies that group chat messages without a Unique and Stable Stanza IDs (XEP-0359) [2] stanza-id cannot be replied to.

For other message types the sender should use the 'id' from a Unique and Stable Stanza IDs (XEP-0359) [2] <origin-id> if present, or the value of the 'id' attribute on the <message> otherwise.

4. IANA Considerations

This document requires no interaction with the Internet Assigned Numbers Authority (IANA) [3].

5. XMPP Registrar Considerations

This document requires no interaction with XMPP Registrar [4].


Appendices

Appendix A: Document Information

Series
XEP
Number
0461
Publisher
XMPP Standards Foundation
Status
Experimental
Type
Standards Track
Version
0.1.0
Last Updated
2022-01-25
Approving Body
XMPP Council
Dependencies
None
Supersedes
None
Superseded By
None
Short Name
reply
Source Control
HTML

This document in other formats: XML  PDF

Appendix B: Author Information

Natalie Wirth
Email
nataliew@laposte.net
Marvin Wissfeld
Email
xsf@larma.de
JabberID
jabber@larma.de

Copyright

This XMPP Extension Protocol is copyright © 1999 – 2020 by the XMPP Standards Foundation (XSF).

Permissions

Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.

Disclaimer of Warranty

## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ##

Limitation of Liability

In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.

IPR Conformance

This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <https://xmpp.org/about/xsf/ipr-policy> or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO 80134 USA).

Visual Presentation

The HTML representation (you are looking at) is maintained by the XSF. It is based on the YAML CSS Framework, which is licensed under the terms of the CC-BY-SA 2.0 license.

Appendix D: Relation to XMPP

The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.

Appendix E: Discussion Venue

The primary venue for discussion of XMPP Extension Protocols is the <standards@xmpp.org> discussion list.

Discussion on other xmpp.org discussion lists might also be appropriate; see <https://xmpp.org/about/discuss.shtml> for a complete list.

Errata can be sent to <editor@xmpp.org>.

Appendix F: Requirements Conformance

The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".

Appendix G: Notes

1. XEP-0393: Message Styling <https://xmpp.org/extensions/xep-0393.html>.

2. XEP-0359: Unique and Stable Stanza IDs <https://xmpp.org/extensions/xep-0359.html>.

3. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.

4. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <https://xmpp.org/registrar/>.

Appendix H: Revision History

Note: Older versions of this specification might be available at https://xmpp.org/extensions/attic/

  1. Version 0.1.0 (2022-01-25)
    Accepted by vote of Council on 2022-01-05.
    XEP Editor (jsc)
  2. Version 0.0.1 (2022-01-01)

    First draft.

    nw/mw

Appendix I: Bib(La)TeX Entry

@report{wirth2022reply,
  title = {Message Replies},
  author = {Wirth, Natalie and Wissfeld, Marvin},
  type = {XEP},
  number = {0461},
  version = {0.1.0},
  institution = {XMPP Standards Foundation},
  url = {https://xmpp.org/extensions/xep-0461.html},
  date = {2022-01-01/2022-01-25},
}

END