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

Agenda for 2014-11-11 telcon

From: Dan Brickley <danbri@google.com>
Date: Tue, 11 Nov 2014 13:15:28 +0000
Message-ID: <CAK-qy=5Egm_QxOCYG09w0tzJ_uDVGhh8TNdL4rgfK9kCaxOdkA@mail.gmail.com>
To: "public-csv-wg@w3.org" <public-csv-wg@w3.org>
Agenda for tomorrow's call:

As recently agreed, it leans heavily on our Github editorial issue
lists and the "requires telecon discussion/decision' label, so please
also review:


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.



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
Received on Tuesday, 11 November 2014 13:15:57 UTC

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