diff --git a/xep-0224.xml b/xep-0224.xml index f570cc5c..3e52d8f7 100644 --- a/xep-0224.xml +++ b/xep-0224.xml @@ -55,7 +55,7 @@

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.

+

It was discussed whether this feature belongs in &xep0085;. However, the semantics are inherently different, since Chat State Notifications 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.

@@ -94,7 +94,7 @@
  • The message stanza containing the attention extension MAY contain a body and/or other extensions, which is to be displayed along with executing the attention event.
  • In message stanzas containing either &xep0203; data, attention extensions MUST be ignored, since the attention request is an instant event which SHOULD NOT be replayed after a delay.
  • Messages containing an attention extension SHOULD use the headline message type to avoid offline storage.
  • -
  • Using the attention extension in &IQ; stanzas is not desirable, since use this feature is part of the conversation.
  • +
  • The attention extension MUST NOT be sent in &IQ; stanzas, since use of this feature is part of a messaging conversation.