Note: This specification has been deprecated in favor of Entity Time (XEP-0202)XEP-0202: Entity Time <https://xmpp.org/extensions/xep-0202.html>..
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 XEP-0202.
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:
<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.
<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. A list of time zone names and abbreviations is located at <http://www.timeanddate.com/library/abbreviations/timezones/>. This element is OPTIONAL in an IQ result.
<display/> -- The time in a human-readable format. This element is OPTIONAL in an IQ result.
The standard error conditions described in Error Condition Mappings (XEP-0086)XEP-0086: Error Condition Mappings <https://xmpp.org/extensions/xep-0086.html>. apply (e.g., service unavailable if the entity does not support the namespace).
XMPP Date and Time Profiles (XEP-0082)XEP-0082: XMPP Date and Time Profiles <https://xmpp.org/extensions/xep-0082.html>. 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 XML Schema Part 2XML Schema Part 2: Datatypes <http://www.w3.org/TR/xmlschema11-2/>.. 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 ISO 8601ISO 8601: Representation of Dates and Times (2000). This specification is not freely available; however, a good summary is located at <http://www.cl.cam.ac.uk/~mgk25/iso-time.html>..
There are no security features or concerns related to this document.
This document requires no interaction with the Internet Assigned Numbers Authority (IANA)The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>..
The 'jabber:iq:time' namespace is registered in the protocol namespaces registry maintained by the XMPP RegistrarThe XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <https://xmpp.org/registrar/>..
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
]]>