No Description
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.

xep-0090.xml 5.9KB

  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE xep SYSTEM 'xep.dtd' [
  3. <!ENTITY % ents SYSTEM 'xep.ent'>
  4. %ents;
  5. ]>
  6. <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
  7. <xep>
  8. <header>
  9. <title>Legacy Entity Time</title>
  10. <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>
  12. <number>0090</number>
  13. <status>Obsolete</status>
  14. <type>Historical</type>
  15. <sig>Standards</sig>
  16. <dependencies>
  17. <spec>XMPP Core</spec>
  18. </dependencies>
  19. <supersedes/>
  20. <supersededby><spec>XEP-0202</spec></supersededby>
  21. <shortname>iq-time</shortname>
  22. <schemaloc>
  23. <url></url>
  24. </schemaloc>
  25. &stpeter;
  26. <revision>
  27. <version>1.2</version>
  28. <date>2009-05-27</date>
  29. <initials>psa</initials>
  30. <remark>Per a vote of the XMPP Council, changed status to Obsolete.</remark>
  31. </revision>
  32. <revision>
  33. <version>1.1</version>
  34. <date>2007-03-28</date>
  35. <initials>psa</initials>
  36. <remark>Per a vote of the XMPP Council, deprecated in favor of XEP-0202.</remark>
  37. </revision>
  38. <revision>
  39. <version>1.0</version>
  40. <date>2003-10-08</date>
  41. <initials>psa</initials>
  42. <remark>Per a vote of the Jabber Council, changed status to Active.</remark>
  43. </revision>
  44. <revision>
  45. <version>0.1</version>
  46. <date>2003-05-22</date>
  47. <initials>psa</initials>
  48. <remark>Initial version.</remark>
  49. </revision>
  50. </header>
  51. <section1 topic='Introduction'>
  52. <p class='note'>Note: This specification has been deprecated in favor of &xep0202;.</p>
  53. <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>
  54. </section1>
  55. <section1 topic='Definition'>
  56. <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>
  57. <ul>
  58. <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>
  59. <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>
  60. <li>&lt;display/&gt; -- The time in a human-readable format. This element is OPTIONAL in an IQ result.</li>
  61. </ul>
  62. </section1>
  63. <section1 topic='Examples'>
  64. <example caption='Querying Another Entity for the Time'><![CDATA[
  65. <iq type='get'
  66. from=''
  67. to=''
  68. id='time_1'>
  69. <query xmlns='jabber:iq:time'/>
  70. </iq>
  71. ]]></example>
  72. <example caption='A Response to the Query'><![CDATA[
  73. <iq type='result'
  74. from=''
  75. to=''
  76. id='time_1'>
  77. <query xmlns='jabber:iq:time'>
  78. <utc>20020910T17:58:35</utc>
  79. <tz>MDT</tz>
  80. <display>Tue Sep 10 12:58:35 2002</display>
  81. </query>
  82. </iq>
  83. ]]></example>
  84. <p>The standard error conditions described in &xep0086; apply (e.g., service unavailable if the entity does not support the namespace).</p>
  85. </section1>
  86. <section1 topic='A Note on Time Formats'>
  87. <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>
  88. </section1>
  89. <section1 topic='Security Considerations'>
  90. <p>There are no security features or concerns related to this document.</p>
  91. </section1>
  92. <section1 topic='IANA Considerations'>
  93. <p>This document requires no interaction with &IANA;.</p>
  94. </section1>
  95. <section1 topic='XMPP Registrar Considerations'>
  96. <p>The 'jabber:iq:time' namespace is registered in the protocol namespaces registry maintained by the &REGISTRAR;.</p>
  97. </section1>
  98. <section1 topic='XML Schema'>
  99. <code><![CDATA[
  100. <?xml version='1.0' encoding='UTF-8'?>
  101. <xs:schema
  102. xmlns:xs=''
  103. targetNamespace='jabber:iq:time'
  104. xmlns='jabber:iq:time'
  105. elementFormDefault='qualified'>
  106. <xs:annotation>
  107. <xs:documentation>
  108. The protocol documented by this schema is defined in
  109. XEP-0090:
  110. NOTE: This protocol has been deprecated in favor of the
  111. Entity Time protocol specified in XEP-0202:
  113. </xs:documentation>
  114. </xs:annotation>
  115. <xs:element name='query'>
  116. <xs:complexType>
  117. <xs:sequence minOccurs='0'>
  118. <xs:element name='utc' type='xs:string' minOccurs='1'/>
  119. <xs:element name='tz' type='xs:string' minOccurs='0'/>
  120. <xs:element name='display' type='xs:string' minOccurs='0'/>
  121. </xs:sequence>
  122. </xs:complexType>
  123. </xs:element>
  124. </xs:schema>
  125. ]]></code>
  126. </section1>
  127. </xep>