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

Re: CSV-LD proposal

From: Ivan Herman <ivan@w3.org>
Date: Wed, 5 Feb 2014 12:47:35 +0100
Cc: W3C CSV on the Web Working Group <public-csv-wg@w3.org>
Message-Id: <F112E546-EBBB-49AB-8208-3C33B922188D@w3.org>
To: Gregg Kellogg <gregg@greggkellogg.net>

On 05 Feb 2014, at 12:34 , Gregg Kellogg <gregg@greggkellogg.net> wrote:

> On Feb 5, 2014, at 2:59 AM, Ivan Herman <ivan@w3.org> wrote:
>> 
>> Hi Gregg,
>> 
>>> On 04 Feb 2014, at 19:36 , Gregg Kellogg <gregg@greggkellogg.net> wrote:
>> 
>> <snip/>
>> 
>>>> 3. We have a mapping of the metadata to a JSON-LD @context file
>>>> 
>>>> I *think* that this covers your example, too. If the metadata correctly identifies
>>>>   - doap_id as a primary key
>>>>   - doap_id and foaf_id as @id-s in the JSON-LD sense (note that this is not the same as primary key!)
>>>>   - foaf_name and doap_name as strings
>>> 
>>> Yes, but this can't be done entirely using a JSON-LD context file, which is why my example used a frame. A frame is basically a context plus entity linking. This is what allows me to allocate doap_id to the outer object, and foaf_id to the inner object.
>>> 
>>> For example, if I have the following:
>>> 
>>> doap_id doap_name foaf_id foaf_name
>>> <rdf> "RDF" <gk> "Gregg"
>>> <rdf> "RDF" <arto> "Arto"
>>> 
>>> I probably have in mind something like
>>> 
>>> <rdf> doap:name "RDF"; doap:developer <gregg>, <arto> .
>>> <gregg> foaf:name "Gregg" .
>>> <arto> foaf:name "Arto" .
>>> 
>>> It's the framing which allows me to do this (and insert the inferred doap:developer property).
>> 
>> I *think* I understand what you mean but... is this something we need to handle it this WG? What strikes me is that
>> 
>> - one can generate JSON-LD and/or RDF with the mechanisms we describe without any further ado
> 
> For CSV to JSON-LD, nothing should be required beyond what already exists.
> 
>> - there are tools that can transform JSON-LD into a more elaborate one (ie, framing), or transform RDF into a more elaborate one (SPIN, SPARQL Constructs, RDF/OWL reasoning engined). Jolly good, as the British say:-), good for us that we have those facilities, but do we have to specify those in this Working Group?
> 
> RDF to CSV through JSON-LD does require framing. The work is quite maturer, but some WG will need to bring to REC. If we go this way, then it may make sense for that to be this group.
> 

The charter only talks about CSV -> RDF/JSON/XML; not the other way round!

Ivan


> Gregg
> 
>> Ivan
>> 
>> 
>> ----
>> Ivan Herman, W3C 
>> Digital Publishing Activity Lead
>> Home: http://www.w3.org/People/Ivan/
>> mobile: +31-641044153
>> GPG: 0x343F1A3D
>> FOAF: http://www.ivan-herman.net/foaf


----
Ivan Herman, W3C 
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
GPG: 0x343F1A3D
FOAF: http://www.ivan-herman.net/foaf






Received on Wednesday, 5 February 2014 11:48:09 UTC

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