From a9da7f313bc089b59468f24072a3fcadb765551e Mon Sep 17 00:00:00 2001 From: "Matthew A. Miller" Date: Mon, 23 Jun 2014 13:32:41 -0600 Subject: [PATCH] ProtoXEP geoloc-dataform v0.0.2: updates per council requests --- inbox/geoloc-dataform.xml | 61 +++++++++++++++++++++++++++++---------- 1 file changed, 46 insertions(+), 15 deletions(-) diff --git a/inbox/geoloc-dataform.xml b/inbox/geoloc-dataform.xml index 93d8e2cc..7ea3c17e 100644 --- a/inbox/geoloc-dataform.xml +++ b/inbox/geoloc-dataform.xml @@ -7,7 +7,7 @@
Data Forms Geolocation Element - This specification defines an XMPP protocol extension for including geolocation data in XEP-0004 data forms. + This specification defines an XMPP protocol extension for including geolocation data in XEP-0004 Data Forms. &LEGALNOTICE; xxxx ProtoXEP @@ -17,6 +17,7 @@ XMPP Core XEP-0004 XEP-0080 + XEP-0122 None None @@ -30,6 +31,14 @@ laukner@gmail.com laukner@jabber.org + + 0.0.2 + 2014-06-21 + ml + +

Initial version, borrowing from XEP-0221 and XEP-0137.

+ + 0.0.1 2014-06-11 @@ -40,25 +49,44 @@
-

In certain protocols that make use of &xep0004;, it can be helpful to include geolocation data. One example of such a "using protocol" is &xep0346;. This document defines a method for including geolocation data in a data form for something you manage and want to publish. This XEP leaves it open to developers how such a <geoloc/> form element will be rendered; possibilities might include editing Latitude and Longitude manually or through a rendered map.

+

In certain protocols that make use of &xep0004;, it can be helpful to include geolocation data. One example of such a "using protocol" is &xep0346;. This document defines a method for including geolocation data in a Data Form for something you manage and want to publish. This XEP leaves it open to developers how such a <geoloc/> form element will be rendered; possibilities might include editing Latitude and Longitude manually or through a rendered map.

 - + +

This proposal addresses the following requirements:

+
    +
  • Integrate geolocation data with &xep0004;.
    • +
  • Allow a potential receiver (rather than the sender) to validate geolocation data.
    • +
+ +

The root element for geolocation data is <geoloc/> as defined in &xep0080;. The information is structured by means of a <geoloc /> element that is qualified by the 'http://jabber.org/protocol/geoloc' namespace. The <geoloc/> element MUST be contained within a <field/> element qualified by the 'jabber:x:data' namespace.

The following example is provided only for the purpose of illustration; consult the specifications for using protocols (e.g., &xep0080;) to see canonical examples.

- - [ ... ] - - - Venice, Italy - Venice - Italy - 45.44 - 12.33 - - - [ ... ] + + [ ... ] + + + Venice, Italy + Venice + Italy + 45.44 + 12.33 + + + [ ... ] ]]> + +

To indicate that a 'geoloc' datatype is expected to be displayed by a receiving entity, the sender MUST use the 'geoloc' datatype as specified in &xep0122;.

+

When submitting a form, a field's value(s) MUST be validated by the receiving entity based on the 'geoloc' datatype identifier(s).

+

Also, the submitter MUST provide a 'geoloc' element for each element within the data form.

+ + + + + ]]> +

If a form-submitting entity receives a field type it does not understand, the 'text-single' field type from &xep0004; MUST be assumed.

+

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. If an error is deliberately added to a location, the error SHOULD be the same for all receivers, to minimize the likelihood of triangulation. In the case of deliberate error, the <accuracy /> element SHOULD NOT be included.

 @@ -71,6 +99,9 @@ The ®ISTRAR; already includes 'http://jabber.org/protocol/geoloc' in its registry of protocol namespaces (see &NAMESPACES;).

+ +

The XMPP Registrar includes 'http://jabber.org/protocol/geoloc' in its registry of Data Forms Validation Datatype Prefixes.

+

As this document only defines semantics for existing protocol, additional schemas are not required.