- From: Gregg Kellogg <gregg@greggkellogg.net>
- Date: Wed, 2 Apr 2014 08:37:03 -0700
- To: Phil Archer <phila@w3.org>
- Cc: "Tandy, Jeremy" <jeremy.tandy@metoffice.gov.uk>, public-csv-wg@w3.org
On Apr 2, 2014, at 7:43 AM, Phil Archer <phila@w3.org> wrote: > Jeremy, > > Picking up on your +1 to my mention of a use case where person B creates metadata about data published by person A, I'm happy to write the use case(s) but do you have one in mind that you can point me to? As well as this general case, it should also cover metadata for a query to an API (potentially including OData), i.e. anything that comes back from a URL that looks a bit like a table. It's the link *from* the metadata *to* the data that I'm most anxious to see covered. It seems to me that allowing the metadata to reference the data source should be fairly straightforward. The case where this is a URL would seem to cover this, and we would want to provide guidance on content-negotiation for this. We also need to provide some enumeration of specific supported types (text/csv, text/tsv). It might be interesting to consider extracting data from an HTML table identified by a fragment of an HTML document as another supported format. Gregg > Phil. > > -- > > > Phil Archer > W3C Data Activity Lead > http://www.w3.org/2013/data/ > > http://philarcher.org > +44 (0)7887 767755 > @philarcher1 >
Received on Wednesday, 2 April 2014 15:37:34 UTC