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

Re: Meeting minutes for the 19th of February...

From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Thu, 20 Feb 2014 10:40:08 -0800
Cc: W3C CSV on the Web Working Group <public-csv-wg@w3.org>
Message-Id: <800D3743-45B2-43BA-890E-DD7FC82D9108@greggkellogg.net>
To: Ivan Herman <ivan@w3.org>
andys: some json reprs e.g. gregg's could lose order

Regarding Andy's comment that JSON might loose order, that's not necessarily the case. For data in a single row, if the headers map to the same property, and we describe the container type of that property to be @list, that could keep the data in order. For example, the following context snippet:

  "@context": {
    "Value1": {"@id": "ex:value", "@container": "@list"},
    "Value2": {"@id": "ex:value", "@container": "@list"}

<TimFinin> maybe we cld have any number of header rows. One might give simple datatypes. another might give column names. another might gibe URIs to semantic types

In my view, this information comes from the JSON-LD frame/context. A type can be statically associated with an entity, or the type could be derived from some column value. Datatype of column values can be determined from the @type associated with the context mapping for that value, allthough I presume that native datatypes, such as integer, float and boolean, are handled as they are in JSON-LD.

Regarding use cases, I'll create some based on the examples from my proposal.

Again, sorry to not be on the calls, but I will make time if asked. Unfortunately, the agendas have been published pretty late.

Gregg Kellogg

On Feb 19, 2014, at 5:58 AM, Ivan Herman <ivan@w3.org> wrote:

> ... are on the Web:
> http://www.w3.org/2014/02/19-csvw-minutes.html
> Cheers
> Ivan
> -- 
> Ivan Herman, W3C
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> http://www.ivan-herman.net/foaf#me
Received on Thursday, 20 February 2014 18:40:39 UTC

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