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

RE: CSV-LD proposal

From: Tandy, Jeremy <jeremy.tandy@metoffice.gov.uk>
Date: Fri, 14 Feb 2014 09:18:35 +0000
To: Gregg Kellogg <gregg@greggkellogg.net>, Alf Eaton <eaton.alf@gmail.com>
CC: "public-csv-wg@w3.org" <public-csv-wg@w3.org>
Message-ID: <2624871D9A05174691BD59F8EFD68AE2B32455@EXXCMPD1DAG3.cmpd1.metoffice.gov.uk>
<snip>
I hadn't considered the need for a format description, and I question if it's always needed, but I could see something like that being added to a spec.

Describing column micro-syntaxes might also be useful, and is another motivation for a format description.
</snip>

Currently, none of the use cases mention this aspect, so it's difficult to establish a requirement for it.

Alf, at this week's teleconf you said that you planned to update some use cases (perhaps in collaboration with Davide?). Perhaps you could incorporate this aspect?

Regards, Jeremy

-----Original Message-----
From: Gregg Kellogg [mailto:gregg@greggkellogg.net] 
Sent: 13 February 2014 19:28
To: Alf Eaton
Cc: public-csv-wg@w3.org
Subject: Re: CSV-LD proposal


On Feb 12, 2014, at 9:28 AM, Alf Eaton <eaton.alf@gmail.com> wrote:

> I've been having a go at writing a PHP class that will read a JSON 
> description file and use it to extract linked data from a CSV file.
> 
> The JSON description file a) describes how to parse the CSV file, and
> b) links to a JSON-LD context document that describes how to map the 
> column names to URIs.
> 
> Repo:
>  https://github.com/hubgit/csvfile-php
> Example description file:
>  
> https://github.com/hubgit/csvfile-php/blob/master/demo/description.jso
> n
> Example context document:
>  https://github.com/hubgit/csvfile-php/blob/master/demo/context.json
> 
> It's not finished yet (or documented), but has been useful for 
> experimenting with ideas for the description file, so I thought I'd 
> post it to the list.
> 
> The idea is to get to the point where any CSV file can be parsed 
> successfully using just the declarative information in the description 
> file. Perhaps the conversion of field names to URIs using the context 
> document should be moved out into a separate step with a dedicated 
> JSON-LD parser, I'm not sure.

Great Alf, this is fairly close to my CSV-LD proposal without the use of framing a framing document, which is fine for simple cases.

I hadn't considered the need for a format description, and I question if it's always needed, but I could see something like that being added to a spec.

Describing column micro-syntaxes might also be useful, and is another motivation for a format description.

Thanks,

Gregg

> It's similar to the Simple Data Format, except that SDF has its own 
> schema/fields definition section rather than pointing to a separate 
> JSON-LD context document. It might be possible to merge the two 
> together, and maybe in fact there will still be some field-specific 
> parsing instructions (e.g. the format of date fields) that need a 
> separate schema definition...
> 
> Alf
> 
> On 1 February 2014 01:52, Gregg Kellogg <gregg@greggkellogg.net> wrote:
>> I added a proposal for something I call CSV-LD to the wiki [1]. As the name might suggest, this is strongly tied to JSON-LD, and uses JSON-LD context and frame definitions to both provide meaning to CSV, allowing it to be losslessly transformed to JSON-LD, or to create CSV from JSON-LD (with or without embedding).
>> 
>> Consider this a straw-man proposal. It does lay out some use cases that are generally useful (and perhaps should be copied to other pages on the wiki), but there may be more use cases to consider. IMO, creating a specification for this, and extending an existing JSON-LD implementation to support this would not be too difficult.
>> 
>> Gregg Kellogg
>> gregg@greggkellogg.net
>> 
>> [1] https://www.w3.org/2013/csvw/wiki/CSV-LD
>> 
>> 
> 
Received on Friday, 14 February 2014 09:19:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:21:38 UTC