- From: David Booth <david@dbooth.org>
- Date: Tue, 18 Jun 2013 00:47:16 -0400
- To: Phil Archer <phila@w3.org>
- CC: semantic-web@w3.org
On 06/17/2013 04:41 PM, Phil Archer wrote: > On 17/06/2013 06:26, David Booth wrote: > [..] >> For example, suppose the client application dereferences a URI and >> obtains a comma-separated-values (CSV) document. unless the client >> application knew how to interpret that file, it would not be able to >> make meaningful use of that data. > > Subject to W3C Member approval and other bits of process, we hope to > launch a WG to define exactly that in the near future (say Sept/Oct). > i.e. define a metadata format and association mechanisms with CSV so > that you can express row and column headings, data types and, I hope, > basic templating rules for turning string values into URIs but I'm not > sure that's in the charter (I'm thinking something like GREL > http://code.google.com/p/google-refine/wiki/GRELFunctions). That same > data could be used to generate other formats besides RDF (OData etc.) Excellent! If it allows CSV documents to be standards-based interpreted as RDF then it would be a perfect example of the fact that data does not have to *look* (overtly) like RDF to *be* RDF. David
Received on Tuesday, 18 June 2013 04:47:43 UTC