Per a vote of the XMPP Council, advanced specification to Draft.
Even though a client might be available (as stated in the most recent presence stanza), the user this client belongs to might not be focused on the client currently. &xep0132; defines a method for a physical test of user presence. Since this requires special hardware that can not be assumed to be available, this XEP defines a software-only implementation where no direct feedback is expected. This is known as 'nudge' or 'buzz' in some legacy IM protocols.
-It was discussed whether this should be part of &xep0085;. However, the semantics are inherently different, since it describes the sender's state, not a request to change the receiver's. Thus, a separate extension is desirable.
+Even though a client might be available (as stated in the most recent presence stanza), the user this client belongs to might not be focused on the client currently. &xep0132; defines a method for a physical test of user presence. Since this requires special hardware that cannot be assumed to be available, this XEP defines a software-only implementation where no direct feedback is expected. This feature is known as 'nudge' or 'buzz' in some non-XMPP IM protocols.
+It was discussed whether this feature belongs in &xep0085;. However, the semantics are inherently different, since Chat State Notificaitons describe the sender's state, not a request to change the receiver's. Thus, a separate extension is desirable.
The specification addresses remotely getting the user's attention in a more assertive way than simple text messages.
@@ -56,20 +63,26 @@In the following conversation, a user talks to somebody, but this user doesn't respond. The second inquiry includes an attention extension.
When no reply is received, the sending user might want to grab the other's attention. This is done by sending a message that includes an <attention/> element qualified by the 'urn:xmpp:attention:0' namespace &VNOTE;. Note: The message may or may not include a &BODY; element.
+When no reply is received, the sending user might want to grab the other's attention. This is done by sending a message that includes an <attention/> element qualified by the 'urn:xmpp:attention:0' namespace &VNOTE;. Note: The message MAY include a &BODY; element.
Finally, the receiving user notices the urgency of the message and responds.
If an entity supports receiving the attention extension, it MUST advertise that fact in its responses to &xep0030; information ("disco#info") requests by returning a feature of "urn:xmpp:attention:0":
+If an entity wishes to receive the attention extension, it MUST advertise that fact in its responses to &xep0030; information ("disco#info") requests by returning a feature of "urn:xmpp:attention:0":
In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in &xep0115;. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.
The implementation of the alert is up to the developer. Possible behavior is:
+The implementation of the alert is up to the developer. Possible behavior includes:
However, since some users might not want this feature to disturb them, a client SHOULD allow the user to disable support. When the feature is disabled, it MUST NOT be advertised in disco#info.
+Because some users might not want this feature to disturb them, a client MUST either (1) allow the user to disable support or (2) disable the feature by default and process attention requests only if the user has explicitly enabled support. When the feature is disabled, it MUST NOT be advertised in disco#info.
Rate-limiting might be desirable in some implementations.
Formal feedback in response to the attention request to the requesting user is not specified, and so the request might be silently dropped.
It is RECOMMENDED that only message stanzas containing attention extensions from peers on the user's roster are accepted. Finer grained control might be implemented.
+It is RECOMMENDED that a client accept message stanzas containing the attention extension only contacts that are in the user's roster or with whome the user's client is currently sharing directed presence, mainly to prevent the user from being annoyed by attention requests from random entities on the network. A client could implement finer-grained control if desired (e.g., allow attention requests only from entities in a particular roster group).
This document requires no interaction with &IANA;.
@@ -134,7 +145,7 @@Upon advancement of this specification from a status of Experimental to a status of Draft, the ®ISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.
+The ®ISTRAR; includes this namespace in the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.
If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of XEP-0053.
@@ -150,6 +161,13 @@ xmlns='urn:xmpp:attention:0' elementFormDefault='qualified'> +