- From: Tim Robertson [GBIF] <trobertson@gbif.org>
- Date: Wed, 7 May 2014 16:21:50 +0200
- To: Jeni Tennison <jeni@jenitennison.com>
- Cc: public-csv-wg@w3.org, "rufus.pollock@okfn.org" <rufus.pollock@okfn.org>
Hi Jeni, Looks nice - quick observations for your consideration / dismissal: - should it support the ability to offer a default value for fields where the value is missing? > if so, this impacts the constraints section - should it be possible to declare a NULL value to support e.g. \N from MySQL dumps. > if so, impacts constraints as well - should it support the ability to offer a fixed field applicable to all rows, but not present in the CSV to allow data enrichment? > probably outside current scope, but we find very useful to annotate data in the use case I proposed today HTH, Tim On 07 May 2014, at 14:00, Jeni Tennison <jeni@jenitennison.com> wrote: > A highly draft version of the spec for metadata vocabulary is available at > > http://w3c.github.io/csvw/metadata/ > > There’s lots of work still to do. Rufus and I are concentrating on the single CSV file, single metadata file case to start with, and trying to create a JSON format that can be interpreted as JSON-LD into RDF (rather than defining an RDF vocabulary which is then described as JSON). > > Jeni > -- > Jeni Tennison > http://www.jenitennison.com/
Received on Wednesday, 7 May 2014 14:22:18 UTC