From 08dc26aa6a1e90fcd155ddb6235b2097304269ee Mon Sep 17 00:00:00 2001 From: nicoco Date: Fri, 9 Dec 2022 05:23:46 +0100 Subject: [PATCH] XEP-0461: fix example char count, disco feature, allow missing 'to' attr --- xep-0461.xml | 42 +++++++++++++++++++++++++++++++++++++++--- 1 file changed, 39 insertions(+), 3 deletions(-) diff --git a/xep-0461.xml b/xep-0461.xml index 205fba35..539c18d2 100644 --- a/xep-0461.xml +++ b/xep-0461.xml @@ -15,6 +15,7 @@ Experimental Standards Track Standards + Council @@ -30,6 +31,12 @@ xsf@larma.de jabber@larma.de + + 0.2.0 + 2022-12-09 + nc + Fix example character counting. Add disco feature. Relax the 'to' attribute constraints. + 0.1.0 2022-01-25 @@ -58,11 +65,38 @@

+ +

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

+ + + ]]> + + + ... + + ... + + ]]> + +

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. + message stanza. The <reply> element SHOULD have a 'to' attribute containing the full jid of the author of the + referenced message and MUST have an 'id' attribute containing the id of the referenced message. + In a 1:1 chat context, a bare jid MAY be used instead of a full jid.

@@ -78,6 +112,8 @@

To provide a fallback for non-supporting clients, the sending client MAY include fallback text in the body and indicate it via Compatibility Fallback. + Note that the following example is formatted for readability and that the indentation, leading and trailing new lines + of the example body element should not be taken into account.

@@ -88,7 +124,7 @@ - + ]]>