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

Re: Agenda for 2014-11-11 telcon

From: Eric <ericphb@gmail.com>
Date: Tue, 11 Nov 2014 21:35:57 -0800
Cc: "public-csv-wg@w3.org" <public-csv-wg@w3.org>
Message-Id: <C6C15D0A-D3EE-4D7F-98A7-ABB55928C53C@gmail.com>
To: Juergen Umbrich <juergen.umbrich@wu.ac.at>
Regrets for tomorrow as well.

Eric

Sent from my iPhone

> On Nov 11, 2014, at 5:40 AM, Juergen Umbrich <juergen.umbrich@wu.ac.at> wrote:
> 
> Regrets also from my side, still one more lecture. 
> I will attend the next calls again and can provide until next week our analysis of around 80K CSV files harvested from CKAN Open Data portals. 
> The report will include basic statistics, such as,  header vs file encoding, used delimiters, and types of deviations compared to a canonical tabular form (e.g, empty rows, missing values, varying column numbers, etc…).
> 
> Best
>   Jürgen 
>> On 11 Nov 2014, at 14:36, Ivan Herman <ivan@w3.org> wrote:
>> 
>> Regrets this time, sorry. I have to travel to down under (ie, Australia) tomorrow morning. Will be back for the next call.
>> 
>> Ivan
>> 
>>> On 11 Nov 2014, at 14:15 , Dan Brickley <danbri@google.com> wrote:
>>> 
>>> Agenda for tomorrow's call:
>>> https://www.w3.org/2013/csvw/wiki/Meeting_Agenda_2014-11-12
>>> 
>>> As recently agreed, it leans heavily on our Github editorial issue
>>> lists and the "requires telecon discussion/decision' label, so please
>>> also review:
>>> 
>>> https://github.com/w3c/csvw/labels/Requires%20telcon%20discussion/decision
>>> 
>>> Editors, please make sure that the issue tracker is up to date. A
>>> snapshot of current issues (with labels) are copied below, but we'll
>>> go with the latest state of the github tracker tomorrow.
>>> 
>>> cheers,
>>> 
>>> Dan
>>> 
>>> Current issues flagged for discussion:
>>> 
>>> for Metadata vocabulary document:
>>> 
>>> Pattern string formats for parsing dates/numbers/durations
>>> 
>>> Using JSON-LD for the metadata document (" is it useful for CSV
>>> metadata to be interpretable as JSON-LD? ")
>>> 
>>> CSV Dialect Description ("Do we want a way to describe the "dialect"
>>> of the CSV in the Metadata document (e.g. separator is ';')")
>>> 
>>> 
>>> for Mappings:
>>> 
>>> Should the RDF/JSON transformation check the values?
>>> - CSV to JSON mapping, CSV to RDF mapping
>>> 
>>> Is row by row processing sufficient?
>>> - CSV to JSON mapping, CSV to RDF mapping
>>> 
>>> How should ``language`` be used in RDF mapping?
>>> - CSV to RDF mapping
>>> 
>>> What should be generated for a value with datatype in the case of JSON
>>> - CSV to JSON mapping
>>> 
>>> How to interpret fixed string type values ("Table", "Row",...)
>>> - CSV to JSON mapping
>>> 
>>> Suggested form for provenance data in RDF & JSON
>>> - CSV to JSON mapping, CSV to RDF mapping
>> 
>> 
>> ----
>> Ivan Herman, W3C 
>> Digital Publishing Activity Lead
>> Home: http://www.w3.org/People/Ivan/
>> mobile: +31-641044153
>> ORCID ID: http://orcid.org/0000-0003-0782-2704
> 
> --
> Dr. Jürgen Umbrich
> WU Vienna, Institute for Information Business
> 
> 
> 
> 
> 
> 
Received on Wednesday, 12 November 2014 05:36:28 UTC

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