W3C home > Mailing lists > Public > public-sdw-comments@w3.org > December 2015

Subsetting data

From: Phil Archer <phila@w3.org>
Date: Wed, 30 Dec 2015 18:31:16 +0000
To: Manolis Koubarakis <koubarak@di.uoa.gr>, "'public-sdw-comments@w3.org'" <public-sdw-comments@w3.org>, Annette Greiner <amgreiner@lbl.gov>, Eric Stephan <ericphb@gmail.com>, "Tandy, Jeremy" <jeremy.tandy@metoffice.gov.uk>, public-dwbp-comments@w3.org
Message-ID: <568422F4.5080405@w3.org>
At various times in recent months I have promised to look into the topic 
of persistent identifiers for subsets of data. This came up at the SDW 
F2F in Sapporo but has also been raised by Annette in DWBP. In between 
festive activities I've been giving this some thought and have tried to 
begin to commit some ideas to a page [1].

During the CEO-LD meeting, Jeremy pointed to OpenSearch as a possible 
way forward, including its geo-temporal extensions defined by the OGC. 
There is also the Linked Data API as a means of doing this, and what 
they both have in common is that they offer an intermediate layer that 
turns a URL into a query.

How do you define a persistent identifier for a subset of a dataset? IMO 
you mint a URI and say "this identifies a subset of a dataset" - and 
then provide a means of programmatically going from the URI to a query 
that returns the subset. As long as you can replace the intermediate 
layer with another one that also returns the same subset, we're done.

The UK Government Linked Data examples tend to be along the lines of:

returns a list of all stations in Britain.

returns a list of stations in Manchester

identifies Manchester Piccadilly station.

All of that data of course comes from a single dataset.

Does this work in the real worlds of meteorology and UBL/PNNL?


[1] https://github.com/w3c/sdw/blob/gh-pages/subsetting/index.md


Phil Archer
W3C Data Activity Lead

+44 (0)7887 767755
Received on Wednesday, 30 December 2015 18:30:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:36 UTC