moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 23:28:51 -05:00
Code Issues Releases Wiki Activity

1.0

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2497 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2008-11-13 20:24:24 +00:00
parent 0879be4098
commit bac2314db6
1 changed files with 35 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
xep-0224.xml
View File

@ -10,12 +10,13 @@
<abstract>This document defines an XMPP protocol extension for getting the attention of another user.</abstract>
&LEGALNOTICE;
<number>0224</number>
<status>Proposed</status>
<status>Draft</status>
<type>Standards Track</type>
<sig>Standards</sig>
<approver>Council</approver>
<dependencies>
<spec>XMPP Core</spec>
<spec>XMPP IM</spec>
<spec>XEP-0030</spec>
</dependencies>
<supersedes/>
@ -27,6 +28,12 @@
<email>andy@monitzer.com</email>
<jid>andy@monitzer.com</jid>
</author>
<revision>
<version>1.0</version>
<date>2008-11-13</date>
<initials>psa</initials>
<remark><p>Per a vote of the XMPP Council, advanced specification to Draft.</p></remark>
</revision>
<revision>
<version>0.2</version>
<date>2008-10-01</date>
@ -47,8 +54,8 @@
</revision>
</header>
<section1 topic='Introduction' anchor='intro'>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
</section1>
<section1 topic='Requirements' anchor='reqs'>
<p>The specification addresses remotely getting the user's attention in a more assertive way than simple text messages.</p>
@ -56,20 +63,26 @@
<section1 topic='Protocol' anchor='protocol'>
<p>In the following conversation, a user talks to somebody, but this user doesn't respond. The second inquiry includes an attention extension.</p>
<example caption="User sends a regular message"><![CDATA[
<message from='calvin@usrobots.lit/lab' to='herbie@usrobots.lit/home' type='chat'>
<message from='calvin@usrobots.lit/lab'
to='herbie@usrobots.lit/home'
type='chat'>
<body>All right, then, Herbie, give! We're waiting.</body>
</message>
]]></example>
<p>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 &lt;attention/&gt; element qualified by the 'urn:xmpp:attention:0' namespace &VNOTE;. Note: The message may or may not include a &BODY; element.</p>
<p>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 &lt;attention/&gt; element qualified by the 'urn:xmpp:attention:0' namespace &VNOTE;. Note: The message MAY include a &BODY; element.</p>
<example caption="User tries to capture the other's attention"><![CDATA[
<message from='calvin@usrobots.lit/lab' to='herbie@usrobots.lit/home' type='headline'>
<message from='calvin@usrobots.lit/lab'
to='herbie@usrobots.lit/home'
type='headline'>
<attention xmlns='urn:xmpp:attention:0'/>
<body>Why don't you answer, Herbie?</body>
</message>
]]></example>
<p>Finally, the receiving user notices the urgency of the message and responds.</p>
<example caption="The user whose attention has been captured responds."><![CDATA[
<message from='herbie@usrobots.lit/home' to='calvin@usrobots.lit/lab' type='chat'>
<message from='herbie@usrobots.lit/home'
to='calvin@usrobots.lit/lab'
type='chat'>
<body>I cannot. You know I cannot! Dr. Bogert and Dr. Lanning don't want me to.</body>
</message>
]]></example>
@ -79,14 +92,14 @@
<ol>
<li>Before sending an attention message stanza, the client SHOULD confirm support for it in the other client as described under <link url='#disco'>Determining Support</link>.</li>
<li>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.</li>
<li>In message stanzas containing either &xep0203; data, attention extensions MUST be ignored, since this is an instant event which should not be replayed after a delay.</li>
<li>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.</li>
<li>Messages containing an attention extension SHOULD use the headline message type to avoid offline storage.</li>
<li>Using the attention extension in &IQ; stanzas is not desirable, since this is part of the conversation.</li>
<li>Using the attention extension in &IQ; stanzas is not desirable, since use this feature is part of the conversation.</li>
</ol>
</p>
</section1>
<section1 topic='Determining Support' anchor='disco'>
<p>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":</p>
<p>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":</p>
<example caption='A disco#info query'><![CDATA[
<iq type='get'
from='calvin@usrobots.lit/lab'
@ -101,29 +114,27 @@
to='calvin@usrobots.lit/lab'
id='disco1'>
<query xmlns='http://jabber.org/protocol/disco#info'>
...
<feature var='urn:xmpp:attention:0'/>
...
</query>
</iq>
]]></example>
<p>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.</p>
</section1>
<section1 topic='Implementation Notes' anchor='impl'>
<p>The implementation of the alert is up to the developer. Possible behavior is:</p>
<p>The implementation of the alert is up to the developer. Possible behavior includes:</p>
<ul>
<li>Shaking the window.</li>
<li>Playing a specific sound not used for any other event.</li>
<li>Flashing the screen.</li>
<li>Enabling external hardware such as flashlights.</li>
<li>Enabling external hardware such as flashing lights.</li>
<li>Let it be user customizable.</li>
</ul>
<p>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.</p>
<p>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.</p>
<p>Rate-limiting might be desirable in some implementations.</p>
<p>Formal feedback in response to the attention request to the requesting user is not specified, and so the request might be silently dropped.</p>
</section1>
<section1 topic='Security Considerations' anchor='security'>
<p>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.</p>
<p>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).</p>
</section1>
<section1 topic='IANA Considerations' anchor='iana'>
<p>This document requires no interaction with &IANA;.</p>
@ -134,7 +145,7 @@
<ul>
<li>urn:xmpp:attention:0</li>
</ul>
<p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
<p>The &REGISTRAR; includes this namespace in the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
</section2>
<section2 topic='Protocol Versioning' anchor='registrar-versioning'>
<p>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 <cite>XEP-0053</cite>.</p>
@ -150,6 +161,13 @@
xmlns='urn:xmpp:attention:0'
elementFormDefault='qualified'>
<xs:annotation>
<xs:documentation>
The protocol documented by this schema is defined in
XEP-0224: http://www.xmpp.org/extensions/xep-0224.html
</xs:documentation>
</xs:annotation>
<xs:element name='attention' type='empty'/>
<xs:simpleType name='empty'>