- From: Dan Brickley <danbri@google.com>
- Date: Tue, 11 Nov 2014 13:15:28 +0000
- To: "public-csv-wg@w3.org" <public-csv-wg@w3.org>
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
Received on Tuesday, 11 November 2014 13:15:57 UTC