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-0112.xml 15KB

  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>User Physical Location</title>
  10. <abstract>This document defines a protocol for communicating information about the current physical location of a Jabber entity. NOTE WELL: The protocol defined herein has been folded into XEP-0080.</abstract>
  12. <number>0112</number>
  13. <status>Obsolete</status>
  14. <type>Standards Track</type>
  15. <sig>Standards</sig>
  16. <dependencies>
  17. <spec>XMPP Core</spec>
  18. <spec>XEP-0060</spec>
  19. </dependencies>
  20. <supersedes/>
  21. <supersededby>
  22. <spec>XEP-0080</spec>
  23. </supersededby>
  24. <shortname>physloc</shortname>
  25. &stpeter;
  26. <revision>
  27. <version>1.0</version>
  28. <date>2004-10-12</date>
  29. <initials>psa</initials>
  30. <remark>Per a vote of the Jabber Council, advanced status to Draft.</remark>
  31. </revision>
  32. <revision>
  33. <version>0.8</version>
  34. <date>2004-10-12</date>
  35. <initials>psa</initials>
  36. <remark>Added internationalization considerations.</remark>
  37. </revision>
  38. <revision>
  39. <version>0.7</version>
  40. <date>2004-10-10</date>
  41. <initials>psa</initials>
  42. <remark>Added &lt;postalcode/&gt; element; removed &lt;url/&gt; element (unnecessary given the existence of jabber:x:oob); defined mapping to vCard.</remark>
  43. </revision>
  44. <revision>
  45. <version>0.6</version>
  46. <date>2004-10-05</date>
  47. <initials>psa</initials>
  48. <remark>Defined mappings to Wireless Village and SIMPLE.</remark>
  49. </revision>
  50. <revision>
  51. <version>0.5</version>
  52. <date>2004-05-11</date>
  53. <initials>psa</initials>
  54. <remark>Changed root element, namespace, and shortname to physloc to prevent conflict with XEP-0033.</remark>
  55. </revision>
  56. <revision>
  57. <version>0.4</version>
  58. <date>2004-04-25</date>
  59. <initials>psa</initials>
  60. <remark>Corrected several errors; added reference to XEP-0033.</remark>
  61. </revision>
  62. <revision>
  63. <version>0.3</version>
  64. <date>2004-02-19</date>
  65. <initials>psa</initials>
  66. <remark>Revived document upon modifications to XEP-0080; changed root element, namespace, and shortname to 'address'.</remark>
  67. </revision>
  68. <revision>
  69. <version>0.2</version>
  70. <date>2003-08-21</date>
  71. <initials>psa</initials>
  72. <remark>Removed 'current' from title; changed shortname to 'location'; changed 'freetext' to 'text'; made several other small fixes.</remark>
  73. </revision>
  74. <revision>
  75. <version>0.1</version>
  76. <date>2003-08-20</date>
  77. <initials>psa</initials>
  78. <remark>Initial version.</remark>
  79. </revision>
  80. </header>
  81. <section1 topic='Introduction' anchor='intro'>
  82. <p><em>NOTE WELL: The protocol defined herein has been folded into &xep0080;.</em></p>
  83. <p>This document defines an extension mechanism for capturing "extended presence" information about a user's current physical location. The information structures defined herein are intended to provide a format for describing a location or address that may change fairly frequently (e.g., one's location on a campus or in a large building) in situations where the user or application does not possess, or does not wish to communicate, detailed latitude/longitude data of the type defined in <cite>XEP-0080</cite>.</p>
  84. </section1>
  85. <section1 topic='Protocol' anchor='protocol'>
  86. <p>Information about the user's location is provided by the user and propagated on the network by the user's client. The information is structured by means of an &lt;physloc/&gt; element that is qualified by the '' namespace. The location information itself is provided as the XML character data of the following children of the &lt;physloc/&gt; element:</p>
  87. <table caption='Child Elements'>
  88. <tr><th>Element</th><th>Description</th><th>Example</th></tr>
  89. <tr><td>&lt;country/&gt;</td><td>The nation where the user is located</td><td>USA</td></tr>
  90. <tr><td>&lt;region/&gt;</td><td>An administrative region of the nation, such as a state or province</td><td>New York</td></tr>
  91. <tr><td>&lt;locality/&gt;</td><td>A locality within the administrative region, such as a town or city</td><td>New York City</td></tr>
  92. <tr><td>&lt;area/&gt;</td><td>A named area such as a campus or neighborhood</td><td>Central Park</td></tr>
  93. <tr><td>&lt;street/&gt;</td><td>A thoroughfare within the locality, or a crossing of two thoroughfares</td><td>34th and Broadway</td></tr>
  94. <tr><td>&lt;building/&gt;</td><td>A specific building on a street or in an area</td><td>The Empire State Building</td></tr>
  95. <tr><td>&lt;floor/&gt;</td><td>A particular floor in a building</td><td>102</td></tr>
  96. <tr><td>&lt;room/&gt;</td><td>A particular room in a building</td><td>Observatory</td></tr>
  97. <tr><td>&lt;postalcode/&gt;</td><td>A code used for postal delivery</td><td>10027</td></tr>
  98. <tr><td>&lt;text/&gt;</td><td>A catch-all element that captures any other information about the user's location</td><td>Northwest corner of the lobby</td></tr>
  99. </table>
  100. </section1>
  101. <section1 topic='Usage' anchor='usage'>
  102. <p>The &lt;physloc/&gt; information SHOULD be communicated by means of &xep0060;. Because physical location information is not pure presence information and can change independently of the user's availability, it SHOULD NOT be provided as an extension to &PRESENCE;.</p>
  103. <example caption='User Publishes Address'><![CDATA[
  104. <iq type='set'
  105. from=''
  106. to=''
  107. id='publish1'>
  108. <pubsub xmlns=''>
  109. <publish node='generic/stpeter-loc'>
  110. <item id='current'>
  111. <physloc xmlns=''
  112. xml:lang='en'>
  113. <country>Austria</country>
  114. <locality>Vienna</locality>
  115. <building>Vienna International Centre</building>
  116. <text>At IETF 57</text>
  117. </physloc>
  118. </item>
  119. </publish>
  120. </pubsub>
  121. </iq>
  122. ]]></example>
  123. <p>The location information is then delivered to all subscribers:</p>
  124. <example caption='Address is Delivered to All Subscribers'><![CDATA[
  125. <message
  126. from=''
  127. to=''>
  128. <event xmlns=''>
  129. <items node='generic/stpeter-physloc'>
  130. <item id='current'>
  131. <physloc xmlns=''
  132. xml:lang='en'>
  133. <country>Austria</country>
  134. <locality>Vienna</locality>
  135. <building>Vienna International Centre</building>
  136. <text>At IETF 57</text>
  137. </physloc>
  138. </item>
  139. </items>
  140. </event>
  141. </message>
  142. .
  143. .
  144. .
  145. ]]></example>
  146. <p>As mentioned in XEP-0060, the stanza containing the event notification or payload MAY also include 'replyto' data (as specified by the &xep0033; protocol) to provide an explicit association between the published data and the user:</p>
  147. <example caption='Event notification with extended stanza addressing'><![CDATA[
  148. <message
  149. from=''
  150. to=''>
  151. <event xmlns=''>
  152. <items node='generic/stpeter-physloc'>
  153. <item id='current'>
  154. <physloc xmlns=''
  155. xml:lang='en'>
  156. <country>Austria</country>
  157. <locality>Vienna</locality>
  158. <building>Vienna International Centre</building>
  159. <text>At IETF 57</text>
  160. </physloc>
  161. </item>
  162. </items>
  163. </event>
  164. <addresses xmlns=''>
  165. <address type='replyto' jid=''/>
  166. </addresses>
  167. </message>
  168. ]]></example>
  169. </section1>
  170. <section1 topic='Mapping to Other Formats' anchor='mapping'>
  171. <p>There are many XML data formats for physical location or address information. It is beyond the scope of this document to provide a mapping from the extension defined herein to every such format. However, it would be valuable to provide a mapping from the Jabber/XMPP format to the formats used in other presence or extended presence protocols. The two main protocols of interest are:</p>
  172. <ol>
  173. <li><p>The Wireless Village (now "IMPS") specifications for mobile instant messaging; these specifications define a presence attribute for address information as encapsulated in the IMPS "Address" element <note>The Wireless Village Initiative: Presence Attributes v1.1 (WV-029); for further information, visit &lt;<link url=''></link>&gt;.</note>.</p></li>
  174. <li><p>The SIP-based SIMPLE specifications; in particular, the IETF's GEOPRIV Working Group has defined an extension to the IETF's &pidf; for location information, as specified in &rfc4119; (also known as "PIDF-LO").</p></li>
  175. </ol>
  176. <p>The following table also maps the format defined herein to the vCard XML format specified in &xep0054;.</p>
  177. <table caption='Mapping Jabber Physical Location to IMPS, PIDF-LO, and vCard'>
  178. <tr>
  179. <th>Jabber/XMPP</th>
  180. <th>Wireless Village / IMPS</th>
  181. <th>SIMPLE (PIDF-LO)</th>
  182. <th>vCard XML</th>
  183. </tr>
  184. <tr>
  185. <td align='center'>&lt;country/&gt;</td>
  186. <td align='center'>&lt;Country/&gt;</td>
  187. <td align='center'>&lt;country/&gt;</td>
  188. <td align='center'>&lt;CTRY/&gt;
  189. <note>As noted in XEP-0054, the XML vCard format defined in draft-dawson-vcard-xml-dtd-01 specified a &lt;COUNTRY/&gt; element rather than a &lt;CTRY/&gt; element; refer to XEP-0054 for details.</note>
  190. </td>
  191. </tr>
  192. <tr>
  193. <td align='center'>&lt;region/&gt;</td>
  194. <td align='center'>--</td>
  195. <td align='center'>&lt;A1/&gt; and/or &lt;A2/&gt;</td>
  196. <td align='center'>&lt;REGION/&gt;</td>
  197. </tr>
  198. <tr>
  199. <td align='center'>&lt;locality/&gt;</td>
  200. <td align='center'>&lt;City/&gt;</td>
  201. <td align='center'>&lt;A3/&gt;</td>
  202. <td align='center'>&lt;LOCALITY/&gt;</td>
  203. </tr>
  204. <tr>
  205. <td align='center'>&lt;area/&gt;</td>
  206. <td align='center'>&lt;NamedArea/&gt;</td>
  207. <td align='center'>&lt;A4/&gt; and/or &lt;A5/&gt;</td>
  208. <td align='center'>--</td>
  209. </tr>
  210. <tr>
  211. <td align='center'>&lt;street/&gt;</td>
  212. <td align='center'>&lt;Street/&gt;
  213. <note>The IMPS specification also enables one to define an intersection (e.g., "Broadway and 34th Street") as the combination of a &lt;Crossing1/&gt; element (e.g., "Broadway") and a &lt;Crossing2/&gt; element (e.g., "34th Street"). To map from IMPS to Jabber, an application SHOULD map such a combination to one Jabber/XMPP &lt;street/&gt; element.</note>
  214. </td>
  215. <td align='center'>&lt;A6/&gt;
  216. <note>The PIDF-LO format provides information elements for much more granular control over a traditional street address; in PIDF-LO the &lt;A6/&gt; element is the street name only, and further information is provided in distinct elements for a leading street direction (e.g., "N"), trailing street suffix (e.g., "SW"), street suffix (e.g., "Avenue"), house number (e.g., "909"), and house number suffix (e.g., "1/2"). To map from PIDF-LO to Jabber, an application SHOULD construct the complete street address from the PIDF-LO elements (&lt;A6/&gt;, &lt;PRD/&gt;, &lt;POD/&gt;, &lt;STS/&gt;, &lt;HNO/&gt;, and &lt;HNS/&gt;) and map the result to one Jabber/XMPP &lt;street/&gt; element.</note>
  217. </td>
  218. <td align='center'>&lt;STREET/&gt;</td>
  219. </tr>
  220. <tr>
  221. <td align='center'>&lt;building/&gt;</td>
  222. <td align='center'>&lt;Building/&gt;</td>
  223. <td align='center'>&lt;LMK/&gt;</td>
  224. <td align='center'>--</td>
  225. </tr>
  226. <tr>
  227. <td align='center'>&lt;floor/&gt;</td>
  228. <td align='center'>--</td>
  229. <td align='center'>&lt;FLR/&gt;</td>
  230. <td align='center'>--</td>
  231. </tr>
  232. <tr>
  233. <td align='center'>&lt;room/&gt;</td>
  234. <td align='center'>--</td>
  235. <td align='center'>--</td>
  236. <td align='center'>--</td>
  237. </tr>
  238. <tr>
  239. <td align='center'>&lt;postalcode/&gt;</td>
  240. <td align='center'>--</td>
  241. <td align='center'>&lt;PC/&gt;</td>
  242. <td align='center'>&lt;PCODE/&gt;</td>
  243. </tr>
  244. <tr>
  245. <td align='center'>&lt;text/&gt;</td>
  246. <td align='center'>&lt;FreeTextLocation/&gt;</td>
  247. <td align='center'>&lt;LOC/&gt;</td>
  248. <td align='center'>&lt;EXTADR/&gt;</td>
  249. </tr>
  250. <tr>
  251. <td align='center'>--</td>
  252. <td align='center'>&lt;Accuracy/&gt;
  253. <note>This element provides accuracy in meters. The geolocation protocol defined in XEP-0080 specifies such an element for Jabber/XMPP, which SHOULD be used when mapping from IMPS to Jabber.</note>
  254. </td>
  255. <td align='center'>--</td>
  256. <td align='center'>--</td>
  257. </tr>
  258. <tr>
  259. <td align='center'>--</td>
  260. <td align='center'>--</td>
  261. <td align='center'>&lt;NAM/&gt;
  262. <note>This element provides a name for the location, e.g., a certain store in a building. This SHOULD be mapped to the Jabber/XMPP &lt;text/&gt; element.</note>
  263. </td>
  264. <td align='center'>--</td>
  265. </tr>
  266. </table>
  267. </section1>
  268. <section1 topic='Internationalization Considerations' anchor='i18n'>
  269. <p>Because the character data contained in most &lt;physloc/&gt; child elements is intended to be readable by humans, the &lt;physloc/&gt; element SHOULD possess an 'xml:lang' attribute specifying the natural language of such character data.</p>
  270. </section1>
  271. <section1 topic='Security Considerations' anchor='security'>
  272. <p>It is imperative to control access to location information, at least by default. Imagine that a stalker got unauthorized access to this information, with enough accuracy and timeliness to be able to find the target person. This scenario could lead to loss of life, so please take access control checks seriously. A user SHOULD take care in approving subscribers and in characterizing his or her current physical location.</p>
  273. </section1>
  274. <section1 topic='IANA Considerations' anchor='iana'>
  275. <p>This document requires no interaction with &IANA;.</p>
  276. </section1>
  277. <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  278. <section2 topic='Protocol Namespaces' anchor='registrar-ns'>
  279. <p>The &REGISTRAR; includes '' in its registry of protocol namespaces, but the namespace is deprecated.</p>
  280. </section2>
  281. </section1>
  282. <section1 topic='XML Schema' anchor='schema'>
  283. <code><![CDATA[
  284. <?xml version='1.0' encoding='UTF-8'?>
  285. <xs:schema
  286. xmlns:xs=''
  287. targetNamespace=''
  288. xmlns=''
  289. elementFormDefault='qualified'>
  290. <xs:element name='physloc'>
  291. <xs:complexType>
  292. <xs:sequence>
  293. <xs:element name='country' minOccurs='0' type='xs:string'/>
  294. <xs:element name='region' minOccurs='0' type='xs:string'/>
  295. <xs:element name='locality' minOccurs='0' type='xs:string'/>
  296. <xs:element name='area' minOccurs='0' type='xs:string'/>
  297. <xs:element name='street' minOccurs='0' type='xs:string'/>
  298. <xs:element name='building' minOccurs='0' type='xs:string'/>
  299. <xs:element name='floor' minOccurs='0' type='xs:string'/>
  300. <xs:element name='room' minOccurs='0' type='xs:string'/>
  301. <xs:element name='postalcode' minOccurs='0' type='xs:string'/>
  302. <xs:element name='text' minOccurs='0' type='xs:string'/>
  303. </xs:sequence>
  304. </xs:complexType>
  305. </xs:element>
  306. </xs:schema>
  307. ]]></code>
  308. </section1>
  309. </xep>