There is a related ISO TC 211 activity similar to this proposal - but more
broad reaching (19151 - Geographic information - Logical position
identification scheme). They already have a level 0 document (first step on
the ISO standards track). I have to find out if I can share the draft
document. At a TC 211 meeting last week, I suggested they consider the work
of the GeoPRIV community. FYI, the submission team has working
implementations.
Regards
Carl
PS: From the document
1 u-position naming scheme(u-position URI)
The u-position is a logical and seamless spatial reference in the form of a
label or a code that identifies a location. Naming scheme of the
u-position(called u-position URI) is defined based on URI syntax and ABNF
notation, as described in IETF RFC 3986(Uniform Resource Identifier (URI) :
Generic Syntax) and RFC2234(ABNF: the Augmented Backus-Naur Form). The
u-Position URI is used to indicate or access spatial information. The
u-Position URI syntax consists of a hierarchical sequence of four components
referred to as the scheme, host, port, and path_upos. The scheme, host,
path_upos are required, and the port is optional. 'path_upos' must begin
with a slash ("/").
u-Position URI = "upos" ":" "//" host [ ":" port ] path-upos
EXAMPLE: upos://scientists.org:1028/charles_darwin
EXAMPLE: upos://scientists.org/uk1_scientist/charles_darwin
EXAMPLE: upos://164.125.2.5:1028/uk1_scientist/charles_darwin
----- Original Message -----
From: "Andy Mabbett" <andy@pigsonthewing.org.uk>
To: <vcarddav@ietf.org>; "GEOPRIV" <geopriv@ietf.org>
Sent: Tuesday, June 02, 2009 3:02 PM
Subject: [Geopriv] [VCARDDAV] The "geo" URI draft
> In message <gYD9ryGv3YJKFw$f@pigsonthewing.org.uk>, Andy Mabbett
> <andy@pigsonthewing.org.uk> writes
>
>>In message <4A25272B.1040808@danbri.org>, Dan Brickley
>><danbri@danbri.org> writes
>>
>>>GeoNames is using 303 (See Other) redirection to distinguish the
>>>Concept (thing as is) from the Document about it.
>>>
>>>For the town Embrun in France we have these two URIs :
>>>[1] http://sws.geonames.org/3020251/
>>>[2] http://sws.geonames.org/3020251/about.rdf
>>
>>That's interesting; but some (notably proponents of RESTful URLs)
>>advise against using file-type extensions.
>>
>>Perhaps:
>>
>> http://sws.geonames.org/3020251/
>>
>> http://sws.geonames.org/3020251/about
>>
>>would suffice?
>
> On reflection:
>
> http://sws.geonames.org/3020251/
>
> http://sws.geonames.org/about/3020251/
>
> or even:
>
> http://sws.geonames.org/place/3020251/
>
> http://sws.geonames.org/about/3020251/
>
> may be better.
>
> --
> Andy Mabbett
> Says "NO! to compulsory UK ID Cards": <http://www.no2id.net/>
> and: "Free Our Data": <http://www.freeourdata.org.uk>
> (both also on Facebook)
> _______________________________________________
> Geopriv mailing list
> Geopriv@ietf.org
> https://www.ietf.org/mailman/listinfo/geopriv
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
