mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-21 16:55:07 -05:00
0.2
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@680 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
parent
1badb5fb65
commit
8859c55ab0
29
xep-0202.xml
29
xep-0202.xml
@ -30,6 +30,12 @@
|
||||
<email>machekku@uaznia.net</email>
|
||||
<jid>machekku@uaznia.net</jid>
|
||||
</author>
|
||||
<revision>
|
||||
<version>0.2</version>
|
||||
<date>2007-03-19</date>
|
||||
<initials>psa</initials>
|
||||
<remark><p>Added service discovery section.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.1</version>
|
||||
<date>2006-12-20</date>
|
||||
@ -101,6 +107,29 @@
|
||||
]]></example>
|
||||
<p>The standard error conditions described in &xep0086; apply (e.g., &unavailable; if the entity does not support the namespace).</p>
|
||||
</section1>
|
||||
<section1 topic='Service Discovery' anchor='disco'>
|
||||
<p>If an entity supports the Entity Time protocol, it MUST report that by including a service discovery feature of "http://www.xmpp.org/extensions/xep-0202.html#ns" &NSNOTE; in response to a &xep0030; information request:</p>
|
||||
<example caption="Service Discovery information request"><![CDATA[
|
||||
<iq type='get'
|
||||
from='romeo@montague.net/orchard'
|
||||
to='juliet@capulet.com/balcony'
|
||||
id='disco1'>
|
||||
<query xmlns='http://jabber.org/protocol/disco#info'/>
|
||||
</iq>
|
||||
]]></example>
|
||||
<example caption="Service Discovery information response"><![CDATA[
|
||||
<iq type='result'
|
||||
from='juliet@capulet.com/balcony'
|
||||
to='romeo@montague.net/orchard'
|
||||
id='disco1'>
|
||||
<query xmlns='http://jabber.org/protocol/disco#info'>
|
||||
...
|
||||
<feature var='http://www.xmpp.org/extensions/xep-0202.html#ns'/>
|
||||
...
|
||||
</query>
|
||||
</iq>
|
||||
]]></example>
|
||||
</section1>
|
||||
<section1 topic='Implementation Notes' anchor='impl'>
|
||||
<p>This protocol was designed in a way that makes migration from <cite>XEP-0090</cite> straightforward. This document specifies a different format for the XML character data of the <utc> element (compliant with <cite>XEP-0082</cite>) and specifies a new <tzo> element for the numeric offset from UTC, while removing the formerly optional and effectively useless <display/> and <tz/> elements.</p>
|
||||
<p>Implementations that support <cite>XEP-0090</cite> should support the protocol defined herein as soon as possible, but should continue to support the protocol defined in <cite>XEP-0090</cite> for backwards compatibility until the status of that specification is changed to Obsolete.</p>
|
||||
|
35
xep-0203.xml
35
xep-0203.xml
@ -22,8 +22,14 @@
|
||||
<spec>XEP-0091</spec>
|
||||
</supersedes>
|
||||
<supersededby/>
|
||||
<shortname>Not yet assigned</shortname>
|
||||
<shortname>NOT YET ASSIGNED</shortname>
|
||||
&stpeter;
|
||||
<revision>
|
||||
<version>0.2</version>
|
||||
<date>2007-03-19</date>
|
||||
<initials>psa</initials>
|
||||
<remark><p>Added service discovery section.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.1</version>
|
||||
<date>2006-12-20</date>
|
||||
@ -55,12 +61,12 @@
|
||||
<th>Inclusion</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><from/></td>
|
||||
<td>from</td>
|
||||
<td>The Jabber ID of the entity that originally sent the XML stanza or that delayed the delivery of the stanza (e.g., the address of a multi-user chat room).</td>
|
||||
<td>RECOMMENDED</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><stamp/></td>
|
||||
<td>stamp</td>
|
||||
<td>The time when the XML stanza was originally sent. The format MUST adhere to the dateTime format specified in <cite>XEP-0082</cite> and MUST be expressed in UTC.</td>
|
||||
<td>REQUIRED</td>
|
||||
</tr>
|
||||
@ -112,6 +118,29 @@
|
||||
</message>
|
||||
]]></example>
|
||||
</section1>
|
||||
<section1 topic='Service Discovery' anchor='disco'>
|
||||
<p>If an entity supports the Delayed Delivery protocol, it MUST report that by including a service discovery feature of "http://www.xmpp.org/extensions/xep-0203.html#ns" &NSNOTE; in response to a &xep0030; information request:</p>
|
||||
<example caption="Service Discovery information request"><![CDATA[
|
||||
<iq type='get'
|
||||
from='romeo@montague.net/orchard'
|
||||
to='juliet@capulet.com/balcony'
|
||||
id='disco1'>
|
||||
<query xmlns='http://jabber.org/protocol/disco#info'/>
|
||||
</iq>
|
||||
]]></example>
|
||||
<example caption="Service Discovery information response"><![CDATA[
|
||||
<iq type='result'
|
||||
from='juliet@capulet.com/balcony'
|
||||
to='romeo@montague.net/orchard'
|
||||
id='disco1'>
|
||||
<query xmlns='http://jabber.org/protocol/disco#info'>
|
||||
...
|
||||
<feature var='http://www.xmpp.org/extensions/xep-0203.html#ns'/>
|
||||
...
|
||||
</query>
|
||||
</iq>
|
||||
]]></example>
|
||||
</section1>
|
||||
<section1 topic='Implementation Notes' anchor='impl'>
|
||||
<p>This protocol was designed in a way that makes migration from <cite>XEP-0091</cite> straightforward. All attributes present in the 'jabber:x:delay' namespace are present in the namespace defined herein. However, this document specifies a different format for the value of the <stamp> attribute (compliant with <cite>XEP-0082</cite>).</p>
|
||||
<p>Implementations that support <cite>XEP-0091</cite> should support the protocol defined herein as soon as possible, but should continue to support the protocol defined in <cite>XEP-0091</cite> for backwards compatibility until the status of that specification is changed to Obsolete.</p>
|
||||
|
Loading…
Reference in New Issue
Block a user