Monday, July 27, 2009

[Geopriv] geo: URI: what about uncertainty?

Any particular reason not to allow for an uncertainty
information to be specified in the URI?

Speaking of practical significance, consider, e. g.:

--cut: http://www.ietf.org/id/draft-ietf-geopriv-geo-uri-01.txt --
<p>one of Vienna's popular sights is the <a href='geo:
48.198634,16.371648;crs=wgs84'>Karlskirche</a>.

A web brower could extract the coordinates from the HTML snippet, and
offer the user various options (based on configuration, context), for
example:

o display a small map thumbnail when the mouse pointer hovers over
the link

o switch to a mapping service of the user's choice once the link is
selected
--cut: http://www.ietf.org/id/draft-ietf-geopriv-geo-uri-01.txt --

There, the uncertainty information embedded into the URI would
allow for the ``small map thumbnail'' or the ``mapping service''
resolution (or scale) to be determined automagically. Say, the
mapping service could select a map resolution so that the given
uncertainty will be of a few pixels on the screen.

Examples:

* geo:53:83;uncertainty=1 -- Barnaul on a global-scale map;

* geo:53.36:83.75;uncertainty=0.05 -- Barnaul on a
regional-scale map;

* geo:53....:83....;uncertainty=0.0001 -- a street map around a
specific location in or near Barnaul.

(Though note that it should be allowed for the uncertainties on
different axes to be different.)

... Finally, following the ``confidence trend'', the comment
like the one below may come handy.

--cut: www.rfc-editor.org/rfc/rfc5491.txt --
It is RECOMMENDED that uncertainty is expressed at a confidence of
95% or higher. Specifying a convention for confidence enables better
use of uncertainty values.
--cut: www.rfc-editor.org/rfc/rfc5491.txt --

--
FSF associate member #7257
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv