W3C home > Mailing lists > Public > public-linked-json@w3.org > February 2014

Fwd: CSV-LD proposal

From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Fri, 31 Jan 2014 18:03:59 -0800
To: Linked JSON <public-linked-json@w3.org>
Message-Id: <B68B9BF4-BB8F-4F84-A187-F7E4F4CA0F88@greggkellogg.net>
FYI, the CSV on the Web working group is essentially trying to do for CSV (and other tabular formats) what JSON-LD did for JSON. I've put forward a CSV-LD proposal [1].

Doing this would require standardizing framing, with some extensions to the existing algorithms, as I note within the document, this could mean using embedded context definitions within a frame to compact embedded nodes using the most specific context definition; I created issue 315 [2] to describe this further.

Gregg Kellogg
gregg@greggkellogg.net

[2] https://github.com/json-ld/json-ld.org/issues/315

Begin forwarded message:

> From: Gregg Kellogg <gregg@greggkellogg.net>
> Subject: CSV-LD proposal
> Date: January 31, 2014 at 5:52:09 PM PST
> To: public-csv-wg@w3.org
> 
> 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 Saturday, 1 February 2014 02:04:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:41 UTC