Re: Metadata document v0.0.1

Hi Tim,

IIRC, we don’t have, in our use cases document, use cases for a couple of these requirements. It would be great if you could put some together. Specifically examples where it’s useful to have:

  * default values for a column
  * fixed-value fields applicable to all rows

(This is just so that we have it all justified, and are able to cull the use cases document for examples; I’m not at all questioning whether these are real requirements.)

We do have a requirement to support missing values: R-MissingValueDefinition [1], so we will get around to making sure that’s included in the metadata definition :)

What format are you converting your CSVs to?

Thanks,

Jeni

[1] http://w3c.github.io/csvw/use-cases-and-requirements/#R-MissingValueDefinition

------------------------------------------------------
From: Tim Robertson [GBIF] trobertson@gbif.org
Reply: Tim Robertson [GBIF] trobertson@gbif.org
Date: 7 May 2014 at 15:23:03
To: Jeni Tennison jeni@jenitennison.com
Cc: public-csv-wg@w3.org public-csv-wg@w3.org, rufus.pollock@okfn.org rufus.pollock@okfn.org
Subject:  Re: Metadata document v0.0.1

> 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 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/
>  
>  
>  
>  

--  
Jeni Tennison
http://www.jenitennison.com/

Received on Wednesday, 7 May 2014 15:32:12 UTC