diff --git a/xep-0080.xml b/xep-0080.xml index eb4ad2f5..eab9abc9 100644 --- a/xep-0080.xml +++ b/xep-0080.xml @@ -15,7 +15,7 @@ Standards XMPP Core - XEP-0060 + XEP-0163 @@ -25,6 +25,12 @@ &hildjj; &stpeter; + + 1.4pre1 + in progress, last updated 2007-05-30 + psa +

Corrected PEP examples; added uri element.

 + 1.3 2006-08-21 @@ -240,18 +246,23 @@ UTC timestamp specifying the moment when the reading was taken (MUST conform to the DateTime profile of &xep0082;) 2004-02-19T21:12Z + + uri + A URI or URL pointing to information about the location + http://beta.plazes.com/plazes/1940:jabber_inc + xs:anyURI +

NOTE: The datatypes specified above are defined in &w3xmlschema2;.

-

The location information SHOULD be communicated by means of &xep0060; or the subset of publish-subscribe specified in &xep0163;. Because 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;, although an application MAY do so if necessary.

- -

In order to provide information about one's location, the publishing entity should use the pubsub protocol (the following examples show use of the publish-subscribe subset specified in XEP-0163).

+

Location information SHOULD be communicated and transported by means of the &xep0060; subset specified in &xep0163;. Because 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;.

+ - + Italy 45.44 @@ -268,7 +279,7 @@ to='bassanio@merchantofvenice.lit/home'> - + Italy 45.44 @@ -279,6 +290,9 @@ +. +. +. ]]> @@ -317,35 +331,26 @@ ]]> -

If an entity wants to send another entity its postition but it does not publish that information via pubsub, it MAY do so in a message. There SHOULD be a body element so that receiving entities that do not support the geolocation protocol can present a message to the recipient.

+

If an entity wants to send another entity its postition but it does not publish that information via pubsub, it MAY do so in a message. The message SHOULD NOT include an XMPP body element.

- This message contains a location. Elsinore 56.033 12.618 + http://www.mapquest.com/maps/map.adp?latlongtype=decimal&latitude=56.033&longitude=12.618 - - - http://www.mapquest.com/maps/map.adp?latlongtype=decimal&latitude=56.033&longitude=12.618 - ]]> -

If an entity wishes all of the entities on its roster to be informed of a new location, the entity MAY publish a presence stanza that includes a location, although this is NOT RECOMMENDED (since location SHOULD be published using pubsub instead in order to ensure appropriate access control):

+

If an entity has generated or been issued a random resource identifier but it wishes to inform all of the entities on its roster about its location, the entity MAY publish a presence stanza that includes a location. It is RECOMMENDED to include only the <description/> element, since full locations SHOULD be published using PEP in order to save bandwidth and ensure appropriate access control.

+ - 1609 - Jabber, Inc. - 10 - 39.75477 - -104.99768 - 2004-02-19T21:12Z + balcony ]]> @@ -514,6 +519,7 @@ +