Formal resolutions and actions from the F2F

I have collected the formal resolutions and actions we took at the F2F, see the list below.

Interestingly, we did not take a formal resolution that the CSV->RDF/JSON conversions will be the 'simple' conversions, and that the mustache/R2RML experiments are not work items any more (and that there will be a separate CG for those); however, that was pretty clearly stated in the second day's discussion. 

So here are the lists. For details and contexts, see the two minutes:

http://www.w3.org/2014/10/27-csvw-minutes.html
http://www.w3.org/2014/10/28-csvw-minutes.html

One particular resolution that has an immediate consequence: we decided to move the weekly telco's time by two hours, ie, to 11am Boston time; this facilitates the participation of our US West Coast friends. (I have asked the admin team to move the zakim timing for next week already.)


# Formal Resolutions #

- We will define the terms ‘title’ and ‘language’ (for columns) and ‘language’ (for table groups down), provide examples using qualified terms for other metadata vocabularies, and be guided by DWBP wrt recommending other particular metadata terms to recommend
- We should not support ‘geopoint’ as a datatype
- We should not support ‘object’, ‘array’ or ‘geojson’ as datatypes
- We will add ‘xml’ and ‘html’ datatypes as defined in RDF
- We have no difference between an empty string with quotes around it and one without quotes around it
- We do not support annotations on regions (for now)
- We use an ‘import’ property in the first metadata document found through the precedence hierarchy described in section 3 (but with inclusion of user-defined metadata); the merge is a depth first recursive inclusion
- We will use ‘describedby’ as the relevant link relation
- We find a metadata file by adding ‘-metadata.json’ to the end of the URL of the CSV file, but only if the URL doesn’t contain a query component
- We do not traverse path hierarchies to locate metadata files
- For now, and without limiting our future work, that we scope to the simplest possible thing that might work and therefore do not have multi-object per line or multiple columns per value
- The simple JSON mapping is a mapping for web developers who need not care about RDF; to generate an RDF serialisation such as JSON-LD, use the RDF mapping and serialise as JSON-LD informed by the metadata file to make a more asthetic result
- We drop the ability in the schema to specify metadata at the row or cell level: schemas are only used to define columns
- We will use URI templates for generating URLs for objects created from rows, for mapping of cell values, and for predicate URIs
- We remove referencing packaging (except as a note) in the Data Model WD
- We will label conversion of CSV to XML as an at risk feature
- We reserve 1 hour at 15:00 UK time on Wednesdays
- We continue on with the calls and review this in a couple of months
- Create github issues for every issue in a document. That we use tracker for actions outside documents that are administrative
- We mirror all the CSV parsing configuration specified in the model document as properties within an object in the metadata document

# Actions #

- danbri propose a sentence informative-referencing sitemaps.org xml format [recorded in http://www.w3.org/2014/10/27-csvw-minutes.html#action02] 
- JeniT to split out section 3.4 to discriminiate between different paths to metadata files [recorded in http://www.w3.org/2014/10/27-csvw-minutes.html#action01] 
- AxelPolleres to follow up on round-tripping metadata.json into RDF and out again [recorded in http://www.w3.org/2014/10/28-csvw-minutes.html#action07]
- AxelPolleres to reach out to other open data portals to join the group [recorded in http://www.w3.org/2014/10/28-csvw-minutes.html#action10]
- danbri and JeniT to talk to members of the group about being more active [recorded in http://www.w3.org/2014/10/28-csvw-minutes.html#action13]
- danbri propose a sentence informative-referencing sitemaps.org xml format [recorded in http://www.w3.org/2014/10/28-csvw-minutes.html#action01]
- Danbri to set up a community group around template mapping syntaxes [recorded in http://www.w3.org/2014/10/28-csvw-minutes.html#action14]
- ericstephan to talk to Bernadette about getting students to do some stuff [recorded in http://www.w3.org/2014/10/28-csvw-minutes.html#action12]
- gkellogg to investigate GitHub/ReSpec issue linkage [recorded in http://www.w3.org/2014/10/28-csvw-minutes.html#action08]
- ivan to create a worked through example for why predicate URLs need to be URL templates, for the simple mapping spec [recorded in http://www.w3.org/2014/10/28-csvw-minutes.html#action03]
- JeniT to amend uc-4 example to use the foreignKey pattern from json table schema [recorded in http://www.w3.org/2014/10/28-csvw-minutes.html#action04]
- JeniT to propose 12/13th Feb for CSV F2F on mailing list [recorded in http://www.w3.org/2014/10/28-csvw-minutes.html#action09]
- JeniT to put foreignKey stuff into metadata document [recorded in http://www.w3.org/2014/10/28-csvw-minutes.html#action05]
- jtandy and ivan to add some text in the mapping spec(s) to indicate the limit in scope and the other features that could be added given more capacity [recorded in http://www.w3.org/2014/10/28-csvw-minutes.html#action02]
- jtandy and ivan to work out how foreign keys get applied when mapping into RDF / JSON [recorded in http://www.w3.org/2014/10/28-csvw-minutes.html#action06]
- jtandy to reach out to UKGovLD Group to join the group [recorded in http://www.w3.org/2014/10/28-csvw-minutes.html#action11]
  

----
Ivan Herman, W3C 
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
GPG: 0x343F1A3D
WebID: http://www.ivan-herman.net/foaf#me