[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Uri-review] early draft of a "geo:" URI scheme.
Hello Alex,
Some comments:
The query part is heavily underspecified. A particular concern
is internationalization. You should say that any textual data
has to be encoded using UTF-8 and %-encoding, in order to work
well with IRIs (RFC 3987).
Also, you say that the query component is specified in secion
3.4 of RFC 3986, and later assume a key/value syntax, but RFC
3986 does not define such syntax. You have to either specify
it yourself (preferably using ';' as a separator rather than '&'),
or not use it.
In 4.7., Interopability Considerations, you say:
authors of 'geo' URIs SHOULD only use well known parameters
in the 'query' component, but you give no clues at all how
such 'well known' parameters will be defined.
The site at http://geouri.org/ (in the entry
Firefox extension handles “geo:” URI) provides some good arguments
for your proposal; it may make sense to include some of the points in
the draft (clearly separated from the normative provisions).
I suggest reducing Section 6.1 (typing bits and pieces from
an URI into an application is definitely NOT what URIs are
for) and expanding Section 6.2 a bit.
In the security section, I don't really see the point of
section 8.3., Malicious Locations. How would a browser
validate and protect a geo: URI? Would that mean that geo:
URIs sohuld only be used over https, not http? What's the
difference to any other kind of link that might be wrong?
In 4.4.2, I would word the second paragraph with MAY, rather
than MUST, because some applications may consider geo: URIs
equal for their purposes even e.g. if altitude doesn't match
(simply consider a map application).
It would also be nice if you could give some RDF/Semantic
Web example.
Regards, Martin.
At 23:01 07/03/01, Alexander Mayrhofer wrote:
>Hi,
>
>we have been working on a first draft of a "geo:" URI to identify geographic
>locations (see draft announcement below). A supplemental website for the
>development of the URI scheme is available at http://geouri.org/, and the
>draft will be on the agenda of the IETF68 GEOPRIV session.
>
>Comments & reviews about the document as well as the URI scheme itself are
>of course strongly appreciated (please ignore the typos in the draft for now..)
>
>thanks,
>
>Alex Mayrhofer / Christian Spanring
>
>---------
>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
>
>
> Title : A Uniform Resource Identifier for Geographic Locations ('geo' URI)
> Author(s) : A. Mayrhofer, C. Spanring
> Filename : draft-mayrhofer-geo-uri-00.txt
> Pages : 13
> Date : 2007-2-23
>
> This document specifies an Uniform Resource Identifier (URI) for
> geographic locations using the 'geo' scheme name. A 'geo' URI
> provides latitude, longitude and optionally altitude of a location in
> a simple, human-readable form. The 'geo' URI is not tied to a
> specific application or protocol.
>
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-mayrhofer-geo-uri-00.txt
>
>_______________________________________________
>Uri-review mailing list
>Uri-review at ietf.org
>https://www1.ietf.org/mailman/listinfo/uri-review
#-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-# http://www.sw.it.aoyama.ac.jp mailto:duerst at it.aoyama.ac.jp
_______________________________________________
Uri-review mailing list
Uri-review at ietf.org
https://www1.ietf.org/mailman/listinfo/uri-review