You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

132 lines
5.9 KiB

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<title>Legacy Entity Time</title>
<abstract>This specification provides historical documentation of the legacy jabber:iq:time namespace, which has been deprecated in favor the urn:xmpp:time namespace defined in XEP-0202.</abstract>
<spec>XMPP Core</spec>
<remark>Per a vote of the XMPP Council, changed status to Obsolete.</remark>
<remark>Per a vote of the XMPP Council, deprecated in favor of XEP-0202.</remark>
<remark>Per a vote of the Jabber Council, changed status to Active.</remark>
<remark>Initial version.</remark>
<section1 topic='Introduction'>
<p class='note'>Note: This specification has been deprecated in favor of &xep0202;.</p>
<p>This document provides canonical documentation of the 'jabber:iq:time' namespace, which was long used by Jabber applications to discover the time at another entity's location. This document is of historical importance only, since it has been deprecated in favor of <cite>XEP-0202</cite>.</p>
<section1 topic='Definition'>
<p>The 'jabber:iq:time' namespace provides a standard way for Jabber entities to exchange information about the local time (e.g., to "ping" another entity or check network latency). The information is communicated in a request/response pair using an &IQ; element that contains a &QUERY; scoped by the 'jabber:iq:time' namespace. The following children of the &QUERY; element are allowed in an IQ result:</p>
<li>&lt;utc/&gt; -- The time (in UTC) according to the responding entity. The format SHOULD be "CCYYMMDDThh:mm:ss" (see below). This element is REQUIRED in an IQ result.</li>
<li>&lt;tz/&gt; -- The time zone in which the responding entity is located. This can be either a three-letter acronym or the full natural-language name of the timezone. <note>A list of time zone names and abbreviations is located at &lt;<link url=''></link>&gt;.</note> This element is OPTIONAL in an IQ result.</li>
<li>&lt;display/&gt; -- The time in a human-readable format. This element is OPTIONAL in an IQ result.</li>
<section1 topic='Examples'>
<example caption='Querying Another Entity for the Time'><![CDATA[
<iq type='get'
<query xmlns='jabber:iq:time'/>
<example caption='A Response to the Query'><![CDATA[
<iq type='result'
<query xmlns='jabber:iq:time'>
<display>Tue Sep 10 12:58:35 2002</display>
<p>The standard error conditions described in &xep0086; apply (e.g., service unavailable if the entity does not support the namespace).</p>
<section1 topic='A Note on Time Formats'>
<p>&xep0082; defines the lexical representation of dates, times, and datetimes in Jabber protocols. Unfortunately, the 'jabber:iq:time' namespace predates that definition, and uses a datetime format ("CCYYMMDDThh:mm:ss") that is inconsistent with XEP-0082 and &w3xmlschema2;. Because a large base of deployed software uses the old format, this document specifies that applications using 'jabber:iq:time' SHOULD use the old format, not the format defined in XEP-0082. In addition, note well that the datetime provided in the &lt;utc/&gt; element is explicitly UTC and therefore SHOULD NOT include the ending 'Z' character required by &iso8601;.</p>
<section1 topic='Security Considerations'>
<p>There are no security features or concerns related to this document.</p>
<section1 topic='IANA Considerations'>
<p>This document requires no interaction with &IANA;.</p>
<section1 topic='XMPP Registrar Considerations'>
<p>The 'jabber:iq:time' namespace is registered in the protocol namespaces registry maintained by the &REGISTRAR;.</p>
<section1 topic='XML Schema'>
<?xml version='1.0' encoding='UTF-8'?>
The protocol documented by this schema is defined in
NOTE: This protocol has been deprecated in favor of the
Entity Time protocol specified in XEP-0202:
<xs:element name='query'>
<xs:sequence minOccurs='0'>
<xs:element name='utc' type='xs:string' minOccurs='1'/>
<xs:element name='tz' type='xs:string' minOccurs='0'/>
<xs:element name='display' type='xs:string' minOccurs='0'/>