11:27:37 RRSAgent has joined #csvw 11:27:37 logging to http://www.w3.org/2014/05/07-csvw-irc 11:27:39 RRSAgent, make logs public 11:27:39 Zakim has joined #csvw 11:27:41 Zakim, this will be CSVW 11:27:41 ok, trackbot; I see DATA_CSVWG()8:00AM scheduled to start in 33 minutes 11:27:42 Meeting: CSV on the Web Working Group Teleconference 11:27:42 Date: 07 May 2014 11:28:15 ivan has changed the topic to: 2014-05-07 Meeting agenda: https://www.w3.org/2013/csvw/wiki/Meeting_Agenda_2014-05-07 11:28:26 Chair: Dan Brickley 11:31:26 AndyS has joined #csvw 11:43:41 danbri has joined #csvw 11:52:13 JeniT has joined #csvw 11:52:40 hello comma separation fans 11:52:44 any scribe volunteers? 11:53:03 phila has joined #csvw 11:53:19 zakim, pick phila as a victim 11:53:19 I don't understand 'pick phila as a victim', danbri 11:53:45 you scribed recently 11:55:21 i have an lrmi call at 2.30pm :( 11:55:24 let me try move that 11:57:03 otherwise can do 1st 30m 11:58:51 jtandy has joined #csvw 11:59:36 DATA_CSVWG()8:00AM has now started 11:59:44 + +44.207.800.aaaa 11:59:55 zakim, aaaa is me 11:59:55 +jtandy; got it 12:00:39 zakim, code? 12:00:39 the conference code is 2789 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), phila 12:00:47 agenda: https://www.w3.org/2013/csvw/wiki/Meeting_Agenda_2014-05-07 12:00:51 +[IPcaller] 12:00:55 zakim, ipcaller is me 12:00:55 +phila; got it 12:01:14 + +1.410.764.aabb 12:01:32 +[IPcaller] 12:01:40 zakim, IPCaller is me 12:01:40 +AndyS; got it 12:01:49 +??P7 12:01:52 zakim, ??P7 is danbri 12:01:52 +danbri; got it 12:02:04 zakim, who is on the phone? 12:02:04 On the phone I see jtandy, phila, +1.410.764.aabb, AndyS, danbri 12:02:18 zakim, mute me 12:02:20 jtandy should now be muted 12:02:38 zakim, aabb is Yakov 12:02:38 +Yakov; got it 12:02:49 yakovsh has joined #csvw 12:02:57 zakim, dial ivan-voip 12:02:57 ok, ivan; the call is being made 12:02:58 +Ivan 12:03:44 last week's meeting record: http://lists.w3.org/Archives/Public/public-csv-wg/2014Apr/0123.html 12:03:44 DavideCeolin has joined #csvw 12:04:23 http://www.w3.org/2014/04/23-csvw-minutes.html 12:04:23 zakim, who is on the phone? 12:04:23 On the phone I see jtandy (muted), phila, Yakov, AndyS, danbri, Ivan 12:04:30 30th april minutes: http://lists.w3.org/Archives/Public/public-csv-wg/2014Apr/0123.html 12:04:38 zakim, yakov is yakovsh 12:04:38 +yakovsh; got it 12:04:46 +ericstephan 12:05:00 +??P15 12:05:07 ericstephan has joined #csvw 12:05:11 zakim, ??P15 is me 12:05:11 +DavideCeolin; got it 12:05:19 jumbrich has joined #csvw 12:05:21 Previous week's minutes are at http://www.w3.org/2014/04/23-csvw-minutes.html 12:05:23 zakim, mute me 12:05:23 DavideCeolin should now be muted 12:05:35 i.e. it was on the 23rd, not the 24th 12:05:42 +1 to both 12:05:46 +??P17 12:05:56 zakim, ??P17 is me 12:05:56 +jumbrich; got it 12:05:56 PROPOSED: Accept previous two week's minutes 12:06:00 +1 12:06:04 + +44.797.442.aacc 12:06:18 zakim, aacc is JeniT 12:06:18 +JeniT; got it 12:06:32 RESOLVED: Accept previous two week's minutes http://lists.w3.org/Archives/Public/public-csv-wg/2014Apr/0123.html and http://www.w3.org/2014/04/23-csvw-minutes.html 12:06:42 chair: danbri 12:06:51 scribe: phila 12:06:55 fonso has joined #csvw 12:06:56 scribeNick: phila 12:07:08 danbri: Introduces agenda 12:07:19 topic: Use Cases and Requirements doc 12:07:19 zakim, unmute me 12:07:19 DavideCeolin should no longer be muted 12:07:24 danbri: Where are we? 12:07:57 -> http://w3c.github.io/csvw/use-cases-and-requirements/index.html UCR Editors' draft 12:08:00 ericstephan: Folks have been pretty swamped but we've managed to add a few more use cases 12:08:12 ... one came from Tim Robinson this morning 12:08:17 ... and one to come from Phil 12:08:23 phila: (I added it this morning too) 12:08:36 ericstephan: We have to firm up the categorisation 12:08:39 q+ 12:08:40 q+ 12:08:43 q+ 12:08:52 do we need to flesh out the requirements themselves? 12:08:55 q? 12:08:55 danbri: So do you have what you need for a next publication? 12:09:01 ericstephan: It depends on the time all of us have this week 12:09:11 zakim, unmute me 12:09:11 jtandy should no longer be muted 12:09:11 ... I'm going to be fairly busy but I can spend some time on it 12:09:23 +??P20 12:09:26 [let's do editors comments, then the zakim queue] 12:09:30 zakim, I am ??P20 12:09:30 +fonso; got it 12:09:33 jtandy: I've not been able to pay much attention so far this week but I should be able to support Wereic this week 12:09:38 zakim, mute me 12:09:38 jtandy should now be muted 12:09:47 DavideCeolin: There are a few things to discuss. I sent an e-mail about that 12:10:09 ... I have tried to classify the requirements following the last meeting. I don't know if the classification is OK or not 12:10:32 ... also I was doubtful about the annotation req. Some reqs could be sub-reqs of that 12:10:37 q+ to discuss annotation requirement 12:10:44 http://lists.w3.org/Archives/Public/public-csv-wg/2014May/0003.html 12:10:46 s /Wereic/ericstephan/ 12:10:53 thx 12:10:58 ack me 12:11:02 https://www.w3.org/2013/csvw/wiki/Use_Cases#Making_Sense_of_Other_People.27s_Data 12:11:05 q- 12:11:26 ack ivan 12:11:34 ack ivan 12:11:44 phila: I added my use case. I'm now checking with the people it talks about that it is accurate 12:11:56 ivan: I think the new use cases lack requirements 12:12:11 ivan: Publishing in 2 weeks is not sacrosanct 12:12:26 ... I'd rather that the requirement table and put it in the doc. If that takes > 2 weeks, so be it 12:12:40 ... what's on the wiki is a significant step forwards 12:12:45 q? 12:12:49 ericstephan: I would prefer moving without doing what Ivan just suggested 12:12:55 +1 to taking more time to get the requirements correct 12:13:05 +1 12:13:06 ... and taking more time as necesssary 12:13:21 ericstephan: I think we can try to get things done... I'd prefer if we had a bit more time (Scribe correct, i.e. Eric agreed with Ivan) 12:13:42 [ah, 'moving out' was wrt to timescale, not location of text] 12:13:42 ivan: There is no requirement to publish on 2 - 3 weeks 12:13:42 q? 12:13:53 ack JeniT 12:13:53 JeniT, you wanted to discuss annotation requirement 12:13:53 ack JeniT 12:14:24 JeniT: I think this doc is really good, the classification is excellent the reqs (section 4) ... 12:14:55 ... section 4.2... I suggest putting all the reqs into accepted for what we want to publish next 12:15:14 JeniT: The 2 - 3 weeks deadline was arbitrary because I think deadlines help to motivate people 12:15:20 ... if it takes longer, then OK 12:15:34 ... but it's also good to publish heartbeat docs so people can track even small changes 12:15:54 JeniT: Re the issue of annotation and supplementary info reqs... 12:16:12 ... There were lots of sub reqs and it's not clear whether we need some of the high level reqs 12:16:17 [loud typing noises] 12:16:34 ... I think we're looking at human-readable annotations 12:16:49 +1 12:16:52 q? 12:17:11 http://w3c.github.io/csvw/use-cases-and-requirements/index.html#R-AnnotationAndSupplementaryInfo 12:17:25 q+ 12:17:29 ^^ That's the specific req under discussion 12:17:42 JeniT: There are lots of reqs, sub reqs around that 12:17:53 I agree that the "annotation and supplementary info" requirement should not overlap with the scope of the other requirements - therefore focus on the human readable annotation 12:17:54 q- 12:17:55 topic: RDF Proc 12:18:00 zakim, who is on the phone? 12:18:00 On the phone I see jtandy (muted), phila, yakovsh, AndyS, danbri, Ivan, ericstephan, DavideCeolin, jumbrich, JeniT, fonso 12:18:26 danbri: This will be a FPWD of the RDF Mapping? 12:18:31 -> http://w3c.github.io/csvw/csv2rdf/ Generating RDF from Tabular Data on the Web 12:18:33 AndyS: Only if you want a very rough and ready document 12:18:43 s/RDF Proc/RDF Mapping/ 12:18:53 q+ 12:18:55 AndyS: There's a lot to be thought through to align the docs 12:19:02 danbri: How would an extra week help? 12:19:11 AndyS: I don't think it will make a stunning difference 12:19:31 danbri: Any particular reason for publishing everything in coordinated waves? 12:19:36 q? 12:19:39 ivan: No, we can do what we like oin that regard 12:19:40 ack ivan 12:19:41 ack ivan 12:20:08 ivan: What bothers me about publishing this doc now... we had a discussion a few weeks ago on the general principles of conversaion of CSV 12:20:27 ... I think what the doc has is more or less in line with that. But I would like those discussions documented and published somewhere 12:20:34 ... just for the public view of things 12:20:42 JeniT: Which doc would that fit in best? 12:20:55 ivan: I was thinking the same thing but don't have an answer 12:21:04 JeniT: There might need to be a general conversion doc? 12:21:05 -jumbrich 12:21:21 ivan: Might it fit in the structure of the model doc? 12:21:25 +??P16 12:21:27 JeniT: I can look 12:21:34 zakim, ??P16 is me 12:21:34 +jumbrich; got it 12:21:39 ivan: I don't mind. I just think the principles should be included somewhere 12:21:42 q? 12:22:10 AndyS: Could you take a go at writing a couple of paras in an e-mail then it can at least go in the RDF doc. It might get moved later 12:22:27 q+ suggest parag re json-ld in http://lists.w3.org/Archives/Public/public-csv-wg/2014May/0017.html 12:22:28 ivan: It's a possibility, but if we do a JSON doc at some point then we'll have to sync those texts 12:22:38 AndyS: That might be the triggerto get it out of the RDf doc 12:22:40 q+ to suggest parag re json-ld in http://lists.w3.org/Archives/Public/public-csv-wg/2014May/0017.html 12:22:49 AndyS: Let's get the text out now and worry about where it ends up later 12:22:51 +1 12:23:04 danbri: Jeni just circulated a draft 12:23:27 zakim, who is noisy? 12:23:41 ivan, listening for 12 seconds I heard sound from the following: danbri (31%) 12:23:51 zakim, who is talking? 12:24:03 danbri, listening for 12 seconds I heard sound from the following: danbri (12%) 12:24:07 action: danbri supply a json-ld sentence for csv2rdf doc 12:24:07 Created ACTION-14 - Supply a json-ld sentence for csv2rdf doc [on Dan Brickley - due 2014-05-14]. 12:24:45 AndyS: I thought Jeni's message is about an RDF form of the metadata doc 12:24:57 danbri: The idea was to take Jeni's sentiment and add it to the doc 12:25:10 JeniT: Not sure how that's relevant? 12:25:34 danbri: I'm just thinking about someone coming in to this and seeing RDF in 2 places 12:25:46 ivan: There is the issue of how the three docs work together 12:26:08 The CSV2RDF doc will refer to metadat doc and (eventually) align. 12:26:15 ivan: When I first saw the metadata doc I was a bit confused about the relationships. It needs clarity, that's all 12:26:23 q? 12:26:30 danbri: Any more to say on RDF generation? 12:27:25 AndyS: If you can send the mail, Ivan, I'll add it to the doc 12:28:14 action: Ivan to send 2 paras on format conversion in an e-mail that Andy will incorporate in the mapping Doc 12:28:14 Created ACTION-15 - Send 2 paras on format conversion in an e-mail that andy will incorporate in the mapping doc [on Ivan Herman - due 2014-05-14]. 12:28:25 ivan: We haven't got any use cases for the XML conversion? 12:28:35 JeniT: No, but we did just have a use case with XML metadata 12:28:40 ivan: It would be good to track that 12:28:43 q? 12:28:45 JeniT: I agree 12:29:21 JeniT: I have taken CSV files and converted them to XML but there was more to it than that 12:29:34 Topic: Model for Tabular Data 12:29:47 danbri: You had a proposal, Jeni that everyone agreed with 12:29:54 -> http://w3c.github.io/csvw/syntax/index.html editor's copy 12:30:09 JeniT: Yes, the proposal was to not worry about embedding any metadata in the CSV other than the column headings 12:30:18 ... lots of +1s to that 12:30:24 +1 12:30:27 +1 12:30:27 danbri: So we're saying nothing, not that you can't do it? 12:31:00 JeniT: We're saying for our WG that, at least for now, we're focussing on CSV with no extra header lines with reserved character starts 12:31:18 danbri: Yes but people *are* putting extra headers in 12:31:36 JeniT: Yes, lots of examples of that - random ways - we need to scope that out for now I think 12:31:59 danbri: But we still need to point to the metadata file 12:32:01 JeniT: Yes 12:32:36 JeniT: We have resolved to defer any consideration of embedding metadata in CSV docs with the exception of column headings 12:32:46 RESOLVED: See above 12:33:15 q+ 12:33:21 JeniT: There are a few other issues... but I'm generally happy for them to stay in the file and for us just to have a heartbeat publication, prob in line with otehr docs 12:33:25 q- 12:33:27 danbri: Any more on this doc? 12:33:48 ivan: I want to make sure that this is reflectied - the RtL issue? We have the use case 12:34:01 ... that's a new req that should be documented that may have an effect on the parsing algorithm 12:34:08 JeniT: I'm happy to add something about that 12:34:17 ... prob in the parsing bit which is informative 12:34:44 ivan: I tried to get some feedback from CN and JP folks to see if vertical writing might be relevant too 12:34:55 ... it seems that no, they tend to work in rows (LtR) 12:35:05 q? 12:35:07 q- 12:35:11 re JP and CN - that's good to hear 12:35:12 ...but Arabic and Hebrew def go RtL 12:35:14 q- 12:35:19 ack ivan 12:35:21 danbri: Do you have all you need? 12:35:23 JeniT: Yep 12:35:32 topic: metadata document 12:35:33 http://lists.w3.org/Archives/Public/public-csv-wg/2014May/0017.html 12:35:37 -> http://w3c.github.io/csvw/metadata/ 12:35:46 JeniT: Last week we had a rough version. This week's is slightly less rough 12:35:46 "Validation and conversion of tabular data on the web requires additional metadata that describes how the data should be interpreted. This document defines a vocabulary for metadata that annotates tabular data. This can be used to provide metadata at various levels, from collections of data from CSV documents and how they relate to each other down to individual cells within a table." 12:35:57 ... I have discussed with Rufus how to structure this 12:36:17 JeniT: One was whether to take it vocab first and then to JSON or from format to vocab - Rufus said the latter 12:36:33 ... the other things was orienting it around using JSON-LD to map the data format 12:36:50 ... also decided to scope the simplest possible case which is a single CSV file described by a single metadata file 12:36:52 -jumbrich 12:36:57 ... that leaves out packages of CSV files 12:37:07 ... and several CSV failes that share the same schema 12:37:21 +??P16 12:37:30 ... what I've done today is to see those divisions in the format of the doc 12:37:32 zakim, ??P16 is me 12:37:32 +jumbrich; got it 12:37:36 http://w3c.github.io/csvw/metadata/#tables 12:37:38 q? 12:37:46 ... looking at aligning that with existing RDF vocabs using JSON-LD 12:38:00 ... using @ to point to the CSV file 12:38:13 zakim, mute me 12:38:13 jumbrich should now be muted 12:38:19 ... we can probably guess a rough version together over the next couple of weeks or a more formed version in 4 weeks 12:38:40 JeniT: So I'd welcome any comments on approach and direction. It means that we depart quite a bit from teh original data package format 12:38:59 ivan: So do we want at some point to go through the various issues before publication? 12:39:04 q+ 12:39:18 JeniT: I think it's OK to have some issues in teh doc but it would be good to go through them 12:39:25 ... anything up to section 2,2 bascially 12:39:28 q? 12:39:30 ack phila 12:39:31 ack me 12:40:08 q? 12:40:13 q+ 12:40:38 ack ivan 12:41:02 ivan: I think it would be good if this doc included a reference/example to the RDF conversion doc 12:41:28 ... AIUI if we use some sort of template for the RDF conversion then it should be clear where it goes in this metadata doc 12:41:33 agreed - it's not clear how the RDF conversion templates fit into the metadata doc 12:41:34 ... but it's not clear to me yet 12:41:37 JeniT: Noted 12:41:50 q+ 12:42:15 JeniT: The format is very much taken from the data packages spec which doesn't include anything about conversion. I think that's a feature of the doc being young 12:42:30 danbri: Does it have any relationship to the UCR (explicitly) 12:43:02 JeniT: Not explicitly. Reqs are quite high level. e.g. 'Validation' - meaning what kind of validation? 12:43:08 q+ 12:43:17 q+ to talk avout validation 12:43:32 zakim, unmute me 12:43:32 jtandy should no longer be muted 12:44:04 q? 12:44:06 jtandy: I just wanted to say... following on from the weather obs example I put on github, I'll try and apply the metadata doc and if broken will feed back 12:44:07 ack jtandy 12:44:19 JeniT: That would be v helkpful - but give it a week first 12:44:51 (phil/ivan, where are we w.r.t. idea of rdf validation wg at w3c?) 12:45:02 ack phila 12:45:02 phila, you wanted to talk avout validation 12:45:05 zakim, mute me 12:45:05 jtandy should now be muted 12:45:48 q? 12:46:19 q+ 12:46:51 discussion of poss usefulness of proposed RDF validation 12:47:52 JeniT: validation of the JSON might be useful for people wanting to use a JSON schema 12:48:15 q? 12:48:18 ack me? 12:48:21 danbri: The RDF validation might take some pressure off us but we can't get wawy without any validation 12:48:24 ack danbri 12:48:33 danbri: Anymore on the metadata vocab doc jeni? 12:48:38 topic: AOB 12:48:45 danbri: Any upcoming events? 12:48:51 +q 12:48:55 http://2014.eswc-conferences.org/ 12:49:18 http://www.thinkingdigital.co.uk/ 12:49:30 http://csvconf.com/ !!!!! 12:49:35 possibly, but not 100% sure I'll be at ESWC 12:49:36 ericstephan: I'll be at hte data Reproducabilty workhop in Seattle tomorrow. Focussed on the biomedical community. Very spreadsheet-centric. Lots of discussion there on tools and standards 12:49:48 this? http://escience.washington.edu/event/first-reproducibility-workshop 12:49:54 ESWC? seems not. 12:49:55 yes 12:50:03 JeniT: There's a CSV Conf! 12:50:11 ... the first international CSV conference in berlin 12:50:43 phila: notes "A conference for data makers. Part of the week long OKFestival" 12:50:47 part of http://2014.okfestival.org/ (so Rufus might know more) 12:50:55 ivan: Is it important for us to be there and for them to know about our work 12:50:56 jeni planning to go 12:51:05 JeniT: I'm planning on going and hoping to give a presentation 12:51:08 ivan: Great 12:51:20 danbri: I'd like to go if I can 12:51:39 Thats our slogan CSV is relaxing 12:51:43 there is going to be an ietf meeting in canada in july but its probably not relevant for our work : http://www.ietf.org/meeting/90/index.html 12:52:04 bye everyone 12:52:07 bye! 12:52:09 bye 12:52:10 bye 12:52:10 -JeniT 12:52:12 -DavideCeolin 12:52:13 -AndyS 12:52:13 -ericstephan 12:52:14 -Ivan 12:52:14 -danbri 12:52:15 -phila 12:52:15 -jtandy 12:52:16 -yakovsh 12:52:16 -jumbrich 12:52:18 meeting adjourned 12:52:18 -fonso 12:52:20 DATA_CSVWG()8:00AM has ended 12:52:20 Attendees were +44.207.800.aaaa, jtandy, phila, +1.410.764.aabb, AndyS, danbri, Ivan, yakovsh, ericstephan, DavideCeolin, jumbrich, +44.797.442.aacc, JeniT, fonso 12:52:20 jumbrich has left #csvw 12:52:23 rrsagent, make logs public 12:52:27 rrsagent, draft minutes 12:52:27 I have made the request to generate http://www.w3.org/2014/05/07-csvw-minutes.html ivan 12:52:33 trackbot, close meeting 12:52:33 Sorry, phila, I don't understand 'trackbot, close meeting'. Please refer to for help. 12:52:43 jenit, http://w3c.github.io/csvw/metadata/ looks pretty good so far :) 12:54:35 andys, re http://w3c.github.io/csvw/csv2rdf/ and field refs, a la schema:homepage <{+homepage}>; … there is a similar construct in the schema.org Actions spec. Except we used parallel property names, 'foo' becomes '-foo' to indicate that its value is a sorta variable 12:54:41 trackbot, end meeting 12:54:41 Zakim, list attendees 12:54:41 sorry, trackbot, I don't know what conference this is 12:54:49 RRSAgent, please draft minutes 12:54:49 I have made the request to generate http://www.w3.org/2014/05/07-csvw-minutes.html trackbot 12:54:50 RRSAgent, bye 12:54:50 I see 2 open action items saved in http://www.w3.org/2014/05/07-csvw-actions.rdf : 12:54:50 ACTION: danbri supply a json-ld sentence for csv2rdf doc [1] 12:54:50 recorded in http://www.w3.org/2014/05/07-csvw-irc#T12-24-07 12:54:50 ACTION: Ivan to send 2 paras on format conversion in an e-mail that Andy will incorporate in the mapping Doc [2] 12:54:50 recorded in http://www.w3.org/2014/05/07-csvw-irc#T12-28-14