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

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

From: Andrea Perego <andrea.perego@jrc.ec.europa.eu>
Date: Wed, 20 May 2015 17:24:01 +0200
Message-id: <CAHzfgWC=7FGF0QDi=FGByO5PeeVqgW6YHYNVwyrrbjvQiEDcFw@mail.gmail.com>
To: "Svensson, Lars" <L.Svensson@dnb.de>
Cc: Raphaël Troncy <raphael.troncy@eurecom.fr>, "Simon.Cox@csiro.au" <Simon.Cox@csiro.au>, "Kerry.Taylor@csiro.au" <Kerry.Taylor@csiro.au>, "eparsons@google.com" <eparsons@google.com>, "janowicz@ucsb.edu" <janowicz@ucsb.edu>, "public-sdw-wg@w3.org" <public-sdw-wg@w3.org>
On Tue, May 19, 2015 at 1:50 PM, Svensson, Lars <L.Svensson@dnb.de> wrote:
> 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 15:24:47 UTC

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