-
Notifications
You must be signed in to change notification settings - Fork 122
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
XEP-0333: bring back disco feature. rename xep
- Loading branch information
Showing
2 changed files
with
38 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,7 +6,7 @@ | |
| <?xml-stylesheet type='text/xsl' href='xep.xsl'?> | ||
| <xep> | ||
| <header> | ||
| <title>Displayed Markers (was: Chat Markers)</title> | ||
| <title>Displayed Markers</title> | ||
| <abstract>This specification introduces a method to let the sender, or multiple participants in a group chat, know that a client has displayed messages up to a certain point.</abstract> | ||
| &LEGALNOTICE; | ||
| <number>0333</number> | ||
|
|
@@ -37,6 +37,17 @@ | |
| <email>[email protected]</email> | ||
| <jid>[email protected]</jid> | ||
| </author> | ||
| <revision> | ||
| <version>0.7.0</version> | ||
| <date>2024-04-04</date> | ||
| <initials>dg</initials> | ||
| <remark> | ||
| <ul> | ||
| <li>Change title to "Displayed Markers"</li> | ||
| <li>Bring back Service Discovery feature</li> | ||
| </ul> | ||
| </remark> | ||
| </revision> | ||
| <revision> | ||
| <version>0.6.0</version> | ||
| <date>2024-03-21</date> | ||
|
|
@@ -145,6 +156,31 @@ | |
| </ul> | ||
| </section1> | ||
|
|
||
| <section1 topic='Determining support' anchor='disco'> | ||
| <p>If an entity supports the Displayed Markers protocol, it MUST report that by including a &xep0030; | ||
| feature of "urn:xmpp:chat-markers:0" in response to disco#info requests:</p> | ||
| <example caption='Client queries for features'> | ||
| <![CDATA[ | ||
| <iq type='get' id='disco1' to='[email protected]/mobile' from='[email protected]/balcony'> | ||
| <query xmlns='http://jabber.org/protocol/disco#info'/> | ||
| </iq> | ||
| ]]> | ||
| </example> | ||
|
|
||
| <example caption='Entity responds with features'> | ||
| <![CDATA[ | ||
| <iq type='result' id='disco1' from='[email protected]/mobile' to='[email protected]/balcony'> | ||
| <query xmlns='http://jabber.org/protocol/disco#info'> | ||
| ... | ||
| <feature var='urn:xmpp:chat-markers:0'/> | ||
| ... | ||
| </query> | ||
| </iq> | ||
| ]]> | ||
| </example> | ||
| <p>Support can also be determined via &xep0115; or &xep0390;.</p> | ||
| </section1> | ||
|
|
||
| <section1 topic='Use Cases' anchor='usecases'> | ||
| <section2 topic='Requesting Displayed Markers' anchor='request'> | ||
| <p>An entity interested to know if the recipient has displayed a message attaches a <markable/> element qualified by the 'urn:xmpp:chat-markers:0' namespace to the message. The message MUST possess an 'id' attribute for traceability.</p> | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters