<?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE xep SYSTEM 'xep.dtd' [ <!ENTITY % ents SYSTEM 'xep.ent'> %ents; ]> <?xml-stylesheet type='text/xsl' href='xep.xsl'?> <xep> <header> <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> &LEGALNOTICE; <number>0090</number> <status>Obsolete</status> <type>Historical</type> <sig>Standards</sig> <dependencies> <spec>XMPP Core</spec> </dependencies> <supersedes/> <supersededby><spec>XEP-0202</spec></supersededby> <shortname>iq-time</shortname> <schemaloc> <url>http://www.xmpp.org/schemas/iq-time.xsd</url> </schemaloc> &stpeter; <revision> <version>1.2</version> <date>2009-05-27</date> <initials>psa</initials> <remark>Per a vote of the XMPP Council, changed status to Obsolete.</remark> </revision> <revision> <version>1.1</version> <date>2007-03-28</date> <initials>psa</initials> <remark>Per a vote of the XMPP Council, deprecated in favor of XEP-0202.</remark> </revision> <revision> <version>1.0</version> <date>2003-10-08</date> <initials>psa</initials> <remark>Per a vote of the Jabber Council, changed status to Active.</remark> </revision> <revision> <version>0.1</version> <date>2003-05-22</date> <initials>psa</initials> <remark>Initial version.</remark> </revision> </header> <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> <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> <ul> <li><utc/> -- 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><tz/> -- 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 <<link url='http://www.timeanddate.com/library/abbreviations/timezones/'>http://www.timeanddate.com/library/abbreviations/timezones/</link>>.</note> This element is OPTIONAL in an IQ result.</li> <li><display/> -- The time in a human-readable format. This element is OPTIONAL in an IQ result.</li> </ul> </section1> <section1 topic='Examples'> <example caption='Querying Another Entity for the Time'><![CDATA[ <iq type='get' from='romeo@montague.net/orchard' to='juliet@capulet.com/balcony' id='time_1'> <query xmlns='jabber:iq:time'/> </iq> ]]></example> <example caption='A Response to the Query'><![CDATA[ <iq type='result' from='juliet@capulet.com/balcony' to='romeo@montague.net/orchard' id='time_1'> <query xmlns='jabber:iq:time'> <utc>20020910T17:58:35</utc> <tz>MDT</tz> <display>Tue Sep 10 12:58:35 2002</display> </query> </iq> ]]></example> <p>The standard error conditions described in &xep0086; apply (e.g., service unavailable if the entity does not support the namespace).</p> </section1> <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 <utc/> element is explicitly UTC and therefore SHOULD NOT include the ending 'Z' character required by &iso8601;.</p> </section1> <section1 topic='Security Considerations'> <p>There are no security features or concerns related to this document.</p> </section1> <section1 topic='IANA Considerations'> <p>This document requires no interaction with &IANA;.</p> </section1> <section1 topic='XMPP Registrar Considerations'> <p>The 'jabber:iq:time' namespace is registered in the protocol namespaces registry maintained by the ®ISTRAR;.</p> </section1> <section1 topic='XML Schema'> <code><![CDATA[ <?xml version='1.0' encoding='UTF-8'?> <xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema' targetNamespace='jabber:iq:time' xmlns='jabber:iq:time' elementFormDefault='qualified'> <xs:annotation> <xs:documentation> The protocol documented by this schema is defined in XEP-0090: http://www.xmpp.org/extensions/xep-0090.html NOTE: This protocol has been deprecated in favor of the Entity Time protocol specified in XEP-0202: http://www.xmpp.org/extensions/xep-0202.html </xs:documentation> </xs:annotation> <xs:element name='query'> <xs:complexType> <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'/> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> ]]></code> </section1> </xep>