W3C home > Mailing lists > Public > public-egov-ig@w3.org > November 2010

Re: Geo in RDF (was Re: Censorship?)

From: William Waites <ww@styx.org>
Date: Tue, 16 Nov 2010 15:08:26 +0100
To: Stuart Williams <skw@epimorphics.com>
Cc: bvillazon@fi.upm.es, public-egov-ig@w3.org
Message-ID: <20101116140826.GO44680@styx.org>
* [2010-11-16 11:21:34 +0000] Stuart Williams <skw@epimorphics.com> écrit:
] Maybe that's intentional, its just that order within a linestring doesn't 
] seem to me to be an invariant property of a point, more of its 'use' in 
] defining a curve.

Somehow it seems like we want to do a linked-list pattern like
rdf:value, rdf:next as in rdf:List...

Unless we have stores that natively understand compound shapes
expressed in RDF or *ML (I think the answer is "not really") the
simplest thing that could possibly work still seems to me to be to
just use WKT which is understood by pretty much every spatial query

What is the compelling argument for expressing this type of data
directly in RDF?

Even the case of annotating, e.g. a segment of a LINESTRING can be
done easily enough by just writing down the segment as WTK and
annotating that...

William Waites
9C7E F636 52F6 1004 E40A  E565 98E3 BBF3 8320 7664
Received on Tuesday, 16 November 2010 14:08:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:00:44 UTC