W3C home > Mailing lists > Public > public-csv-wg@w3.org > November 2014

Re: Could primaryKey be specified directly as a column name?

From: Jeni Tennison <jeni@jenitennison.com>
Date: Mon, 3 Nov 2014 10:53:08 +0000
To: David Booth <david@dbooth.org>, public-csv-wg@w3.org
Message-ID: <etPan.54575e94.74b0dc51.34c@jenit-2>
Hi David,

This was an attempt to make the metadata JSON be good JSON-LD. The draft now just uses the “name” property and references those names within “primaryKey", which makes it easier to write but requires a bit more application logic.

Jeni

-----Original Message-----
From: David Booth <david@dbooth.org>
Reply: David Booth <david@dbooth.org>>
Date: 1 November 2014 at 20:36:05
To: public-csv-wg@w3.org <public-csv-wg@w3.org>>
Subject:  Could primaryKey be specified directly as a column name?

> In the 30-Oct-2014 draft at
> http://w3c.github.io/csvw/csv2rdf/
> there is a very nice, simple example in Sec 4. (Thanks for that!) But
> I'm wondering about one detail.
>  
> Example 3 shows CSV metadata, which includes:
>  
> . . .
> "columns": [{
> "@id": "_:GID",
> "name": "GID",
> "datatype": "integer"
> }, {
> . . .
> "primaryKey": "_:GID"
> }]
> . . .
>  
> I notice that the value provided for "primaryKey" above is specified as
> an indirect identifier ("_:GID") for the primary key column, instead of
> being directly specified as the column name "GID". I assume that there
> is some rationale for doing it this way -- perhaps so that the metadata
> can specify duplicate column names, though wouldn't that be a bad use
> case to support? -- but it seems cumbersome and error prone. Can this
> be simplified to allow the "primaryKey" to be specified directly as the
> column name?
>  
> Thanks,
> David
>  
>  
>  

--  
Jeni Tennison
http://www.jenitennison.com/
Received on Monday, 3 November 2014 10:53:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:27:45 UTC