From a1dad80941c5f695e1979588450737ef59c784ee Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Thu, 7 Jun 2007 22:44:32 +0000 Subject: [PATCH] 1.4pre2 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@922 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0080.xml | 78 +++++++--------------------------------------------- 1 file changed, 10 insertions(+), 68 deletions(-) diff --git a/xep-0080.xml b/xep-0080.xml index eab9abc9..05f24991 100644 --- a/xep-0080.xml +++ b/xep-0080.xml @@ -6,7 +6,7 @@
- User Geolocation + User Location This document defines an XMPP protocol extension for communicating information about the current geographical location of an entity. &LEGALNOTICE; 0080 @@ -26,10 +26,10 @@ &hildjj; &stpeter; - 1.4pre1 - in progress, last updated 2007-05-30 + 1.4pre2 + in progress, last updated 2007-06-07 psa -

Corrected PEP examples; added uri element.

 +

Renamed to User Location; corrected pubsub examples; removed non-pubsub examples; added uri element.

 1.3 @@ -130,7 +130,7 @@ -

Information about the entity's location is provided by the entity and propagated on the network by the entity's associated application (usually a client). The information is structured by means of a <geoloc/> element that is qualified by the 'http://jabber.org/protocol/geoloc' namespace; the geolocation information itself is provided as the XML character data of the following child elements:

+

Information about the entity's location is provided by the entity and propagated on the network by the entity's associated application (usually a client). The information is structured by means of a <geoloc/> element that is qualified by the 'http://jabber.org/protocol/geoloc' namespace; the location information itself is provided as the XML character data of the following child elements:

@@ -255,8 +255,9 @@
Element Name

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

 - -

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;.

+ +

Location information SHOULD be communicated and transported by means of &xep0060; or the subset thereof specified in &xep0163; (the examples below assume that the user's XMPP server supports PEP, thus the publish request lacks a 'to' address and the notification message has a 'from' address of the user's bare JID).

+

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;.

@@ -276,7 +277,7 @@ ]]> + to='bassanio@merchantofvenice.lit'> @@ -295,65 +296,6 @@ . ]]> - -

If an entity wishes to request the location of another entity but the requestee does not publish that information via pubsub (including PEP), the requestor MAY send an IQ to the requestee:

- - -]]> -

The receiving entity SHOULD make a careful access control decision before returning the actual location.

- - - Italy - 45.44 - Venice - 12.33 - -]]> -

If the receiving entity decides not to return the actual location, it MUST return an IQ error, which SHOULD be &forbidden; but MAY be some other appropriate error, such as ¬allowed;:

- - - - - - - ]]> - - -

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.

- - - Elsinore - 56.033 - 12.618 - http://www.mapquest.com/maps/map.adp?latlongtype=decimal&latitude=56.033&longitude=12.618 - - -]]> - - -

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.

- - - balcony - -]]> - @@ -447,7 +389,7 @@ -- <Accuracy/> - This element provides accuracy in meters. The geolocation protocol defined in XEP-0080 specifies such an element for XMPP, which SHOULD be used when mapping from IMPS to XMPP. + This element provides accuracy in meters. The location protocol defined in XEP-0080 specifies such an element for XMPP, which SHOULD be used when mapping from IMPS to XMPP. -- --