CSV on the Web Working Group Teleconference

<trackbot> Date: 17 December 2014

<danbri> hi

<danbri> agenda: http://lists.w3.org/Archives/Public/public-csv-wg/2014Dec/0046.html

<danbri> any scribe volunteers?

<jtandy_> waiting for the wednesday afternoon fire alarm to complete :-)

FPWD Publishing

<danbri> +1 from AndyS, http://lists.w3.org/Archives/Public/public-csv-wg/2014Dec/0047.html

<danbri> scribenick: bill-ingram

<danbri> +1 and regrets from Eric, http://lists.w3.org/Archives/Public/public-csv-wg/2014Dec/0051.html

agenda — can we ship our first working draft?

<danbri> Proposal: That our CSV2JSON and CSV2RDF docs be published as First Public Working Drafts, accompanied by refreshed drafts of metadata and syntax documents (all based on current editor drafts).

<ivan> +1

+1

<jtandy_> +101

<danbri> +1

<jtandy_> (OK , +1)

<ivan> Resolved: That our CSV2JSON and CSV2RDF docs be published as First Public Working Drafts, accompanied by refreshed drafts of metadata and syntax documents (all based on current editor drafts).

considering this plus the mailing list +1s

<danbri> practicalia:

ivan: we should soon have a solid version, which will be the one that will be published

…need to freeze a draft

jtandy_: ask that someone else do the prep for working draft pub

ivan: happy to do that, but need a separate branch that is to be published

…there is a document for how to publish

<danbri> https://github.com/w3c/csvw/tree/gh-pages/publishing-snapshots

…all I need is for jtandy_ to say 'go'

jtandy_: leaving for xmas soon

ivan: should have enough time to put it through pub rules

…we also have to get a plea to jeni to finish her doc and make a snapshot herself

…i can start working around 5th jan, and that week it should be done

…i'm not around after that

danbri: let's shoot for the 8th

ivan: problem with issues not sync b/w the two

…minor things

danbri: are there issues in you heads not in github?

jtandy_: may be one or two that are mentioned in the document

danbri: github working ?

others: yes

ivan: we can send every github event to the mailing list; now we're using two lists; not sure it's necessary

<danbri> bill-ingram: are we using Git tag for releases?

<danbri> danbri: sounds right, but i'm not aware of us using it

<danbri> ivan: i use it personally, will try to remember for mon/tues. a good idea

<danbri> jtandy: we should probably stick with existing practice, a publishing snapshot dir, ... as we've done that so far.

<danbri> jtandy_ ... we lost you in audio

<jtandy_> I have lost audio too ...

<danbri> ack me?

<Zakim> danbri, you wanted to note from ivan ns URL / doc, http://lists.w3.org/Archives/Public/public-csv-wg/2014Dec/0052.html

<jtandy_> will dial back in :-(

ivan: namespace document summary

…it would be good idea to defreference namespace properly, i.e., no 404

…not saying we need something abs. complete there, just something at /ns/csvw

…simple html file is ok

…remember that existing jsonld document can serve as target

…either way, both are fine, need something earlier than the 8th

danbri: creating issue

jtandy_: there are some things we will need to talk about once we tick off the issues in the document

…but the docs stand on their own

ivan: maybe one thing would be to document somewhere that there are some terms, property terms, that are not yet in the metadata document

jtandy_: i think they are now in jeni's document

<danbri> I filed an issue to track ns doc point raised by ivan, https://github.com/w3c/csvw/issues/127

ivan: except the url templates

jtandy_: that's what the metadata document tells me to do

…nonetheless now i am synchronized with jeni's document

…obviously, if she makes changes, the mapping doc will need changes as well

…i doubt changes will come before new year

danbri: issue assigned to ivan

ivan: i can put together something simple
... anything else to discuss?

ISSUE 113: usage of @type

jtandy_: issue 113?

<danbri> https://github.com/w3c/csvw/issues/113

jtandy_: @type 'table' is about the resource or about a table description ?

…i'd suggest the @graph is about the description

…magic question is 'what's the subject?'

ivan: it uses the @type table in the metadata, which is rdf, and clearly assigns table as the subject of the metadata

…typing is on the data, not the metadata, both are rdf

<jtandy_> http://w3c.github.io/csvw/metadata/index.html

jtandy_: if you look at metadata editor's draft example #2

…the resource we're talking about is the csv file

…the dc.title is about the data

ivan: right, there is an inconsistency

…rows, cols, etc are about structures in the metadata

jtandy_: we've agreed that we're not going to make statements about rows, cells, right?

ivan: in the document, it still uses @type for column, template, now

jtandy_: that much is ok

ivan: are they not mapped into rdf as well?

jtandy_: when i map, i have chosen not to @type anything but the table

…my intention is to make the inconsistency visible now

…we don't need to buffer it out before first public working draft

ivan: would it be possible to articulate what you just describe, or put a reference to the minutes here, in the issue

…actually I will clean up the minutes and do it myself

danbri: shall we consider when our next meeting will be?

<danbri> next meeting?

<danbri> January 2015 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

<jtandy_> call broke again ... dialing back in

danbri: call on the 7th?

all: yes

<danbri> (I may be flying on 7th)

<jtandy_> I can do 7th

<danbri> Adjourned!

<danbri> jtandy, don't need to dial in :)

<jtandy_> ok. MERRY CHRISTMAS TO ALL

<danbri> thanks for scribing, bill :)

<ivan> trackbot, end telcon