>
>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
Well, this may be obvious when or if you can share
the document, but this syntax and example set seems
to be a pointer mechanism for grabbing spatial information,
rather than a mechanism for including it. The geo
URI that's been discussed here seems to be for URI-format
geo information, rather than a protocol that tells
you where to go get it.
Am I misunderstanding this?
regards,
Ted
>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
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
