GUID: a Globally Unique Indentifier, used as the identifier for a shared editing session.
-Host: The JID to which the SXE messages are sent for relaying to other members of the session; this can be the initiator of the session (e.g., in a one-to-one session or small multi-user session) or a multi-user chat room or specialized shared editing component.
-RID: the Record ID given to a record when it is created.
-State: In the context of a new user joining, the state refers to the set of records that describes the edited object, including all previous versions of each record. All entities involved in the session are REQUIRED to keep this state unless a specialized component handles user joins.
-Weight: Primarily, the weight of a node is represented by the 'primary-weight' field of the corresponding record. Secondarily, if the values of the 'primary-weight' of two records are equal, the first differing characters of the rids are compared by their Unicode values. The higher the character the higher the weight of the node is.
+The responder indiciates the reason for refusing the session by including a "reason" element. The following reasons are suggested (see also XEP-0166):
+The responder indiciates the reason for refusing the session by including a "reason" element. The following reasons are suggested (see also &xep0166;):
Such presence can be broadcast or can be sent in the context of a multi-user chat room (see XEP-0045).
-However, presence is not sent when operating in a serverless messaging environment (see XEP-0174). Instead, DNS TXT records are published. Two new key-value pairs are used to advertise a session id ("sxe_id") and session name ("sxe_name") when using serverless messaging.
+Such presence can be broadcast or can be sent in the context of a multi-user chat room (see &xep0045;).
+However, presence is not sent when operating in a serverless messaging environment (see &xep0174;). Instead, DNS TXT records are published. Two new key-value pairs are used to advertise a session id ("sxe_id") and session name ("sxe_name") when using serverless messaging.
The ®ISTRAR; shall add the type of "sxe" to the "collaboration" category in its registry of service discovery identities.
+The ®ISTRAR; shall add the type of "sxe" to the "collaboration" category in its registry of service discovery identities.
The XMPP Registrar shall include "sxe" in its registry of Jingle transport methods. The registry submission is as follows:
@@ -1047,14 +1086,143 @@ PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"To follow.
+
+
+
+
+
+
+ The protocol documented by this schema is defined in
+ XEP-0284: http://xmpp.org/extensions/xep-0284.html
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ]]>