W3C home > Mailing lists > Public > public-sdw-wg@w3.org > May 2015

RE: UCR issue: phrasing of CRS requirement(s)

From: <Simon.Cox@csiro.au>
Date: Wed, 20 May 2015 05:30:47 +0000
To: <L.Svensson@dnb.de>, <raphael.troncy@eurecom.fr>, <Kerry.Taylor@csiro.au>, <eparsons@google.com>, <janowicz@ucsb.edu>
CC: <public-sdw-wg@w3.org>
Message-ID: <2A7346E8D9F62D4CA8D78387173A054A601742F1@exmbx04-cdc.nexus.csiro.au>
Raphaël: how is 'semanticizing' the description of CRS helpful? As Peter and I have shown there are existing XML-based services that deliver the entire EPSG CRS dataset in fully structured form (which covers the lat/lon vs lon/lat issue Lars). Given that these services have reliable URIs (based on the EPSG identifiers), contain links (to the component elements like CS, Datum, Axis, etc), and are in an open format (GML/XML), we are already up to about 4 1/2-star linked data. 

I'm a big fan of RDF and OWL, partly because of the scalability and flexibility, and tool support. But there are some boundaries over which the value add of RDF is vanishingly small, particularly if some 'linked data' that is already available. I question whether effort is wisely spent here, compared with some other parts of the puzzle which are much less evolved right now.  

Kerry raised the issue of scope, and suggested that the goal should be n-star linked spatial data. I agree, but we need to be clear that "linked data" != "semantic web with full reasoning", so need to be careful about balance here. 

-----Original Message-----
From: Svensson, Lars [mailto:L.Svensson@dnb.de] 
Sent: Tuesday, 19 May 2015 9:51 PM
To: Raphaël Troncy; Cox, Simon (L&W, Highett); Taylor, Kerry (Digital, Acton); eparsons@google.com; janowicz@ucsb.edu
Cc: public-sdw-wg@w3.org
Subject: RE: UCR issue: phrasing of CRS requirement(s)

On Tuesday, May 19, 2015 10:09 AM Raphaël Troncy wrote:

> >  Thanks Kerry - that's essentially the way I see it, if by "linked 
> > data representation" you are implying RDF. I would like to ask those 
> > people advocating a new CRS encoding in RDF, what this would be 
> > useful for?
> Well of course, this is a very "niche" usage, but typical use cases 
> are for getting an explicit semantic description of how a CRS has been 
> built so that you can, for example, query for all CRSs that use a 
> specific Datum, or, more simply, ask for the EPSG identifier 
> corresponding to the URI of a CRS, etc.

Another case would be to get information about lat/long vs. long/lat.


Received on Wednesday, 20 May 2015 05:32:08 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:16 UTC