From bdc37fbb0cc152cbc52acc946b57c1545f2d365d Mon Sep 17 00:00:00 2001 From: stpeter Date: Tue, 16 Aug 2011 15:15:34 -0600 Subject: [PATCH] 1.2rc1 --- xep-0249.xml | 29 ++++++++++++++++++++++++++++- 1 file changed, 28 insertions(+), 1 deletion(-) diff --git a/xep-0249.xml b/xep-0249.xml index 92ebe9a7..4cf938bf 100644 --- a/xep-0249.xml +++ b/xep-0249.xml @@ -25,6 +25,12 @@ http://xmpp.org/schemas/x-conference.xsd &stpeter; + + 1.2rc1 + 2011-08-16 + psa +

Added continue and thread attributes for feature parity with mediated invitations when converting a one-to-one chat to a groupchat.

 + 1.1 2009-12-07 @@ -88,7 +94,7 @@ -

&xep0045; defines a protocol for groupchat over XMPP. That specification includes a method for inviting a contact to a room, where the invitation is mediated by the room itself: the user sends the invitation to the room, which in turn sends it to the contact. Unfortunately, a mediated invitation might not be delivered to the contact, for example if the contact blocks communication with entities not in its roster as specified in &xep0016;. As privacy lists have become more common, MUC invitations have been increasingly blocked at the server side, resulting in an undesirable user experience. Therefore, this specification defines a method for sending an invitation directly from the user to the contact, which re-uses the original 'jabber:x:conference' namespace in use before XEP-0045 was written (with the addition of a 'reason' attribute for the sake of feature parity with XEP-0045).

+

&xep0045; defines a protocol for groupchat over XMPP. That specification includes a method for inviting a contact to a room, where the invitation is mediated by the room itself: the user sends the invitation to the room, which in turn sends it to the contact. Unfortunately, a mediated invitation might not be delivered to the contact, for example if the contact blocks communication with entities not in its roster as specified in &xep0016;. As privacy lists have become more common, MUC invitations have been increasingly blocked at the server side, resulting in an undesirable user experience. Therefore, this specification defines a method for sending an invitation directly from the user to the contact, which re-uses the original 'jabber:x:conference' namespace in use before XEP-0045 was written (with the addition of 'reason', 'continue', and 'thread' attributes for feature parity with mediated invitations).

 @@ -106,6 +112,19 @@

The 'jid' attribute, which is REQUIRED, specifies the address of the groupchat room to be joined.

The 'password' attribute, which is OPTIONAL, specifies a password needed for entry into a password-protected room and maps to the <password/> element in a mediated invitation.

The 'reason' attribute, which is OPTIONAL, specifies a human-readable purpose for the invitation and maps to the <reason/> element in a mediated invitation.

+

The 'continue' and 'thread' attributes, which are OPTIONAL, specify that the groupchat room continues a one-to-one chat having the designated thread; these map to the <continue/> element (with 'thread' attribute) in a mediated invitation. Note that the 'continue' attribute has a datatype of boolean. &BOOLEANNOTE;

+ + + + ]]>

Upon receiving a direct invitation, the contact's client SHOULD present the invitation to the contact so that the contact can accept it or decline it. If the contact accepts the invitation, the contact's client shall join the room as described in XEP-0045. If the contact declines the invitation, it shall silently discard the invitation.

 @@ -179,6 +198,10 @@ + +