12:58:55 RRSAgent has joined #dxwg 12:58:55 logging to http://www.w3.org/2017/05/25-dxwg-irc 12:58:57 RRSAgent, make logs public 12:58:57 Zakim has joined #dxwg 12:58:59 Zakim, this will be 12:58:59 I don't understand 'this will be', trackbot 12:59:00 Meeting: Dataset Exchange Working Group Teleconference 12:59:00 Date: 25 May 2017 13:00:01 regrets+ Kate, Antoine, Colleen, Luiz, Jacco, Ruben, Lars 13:00:10 RRSAgent, make logs public 13:00:26 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2017.05.25 13:44:34 Caroline has joined #DXWG 13:44:48 kcoyle has joined #dxwg 13:47:27 fanieli has joined #dxwg 13:47:56 fanieli has joined #dxwg 13:48:04 present+ fanieli 13:49:05 roba has joined #dxwg 13:49:50 newton has joined #dxwg 13:53:53 Jaroslav_Pullmann has joined #dxwg 13:54:04 present+ Jaroslav_Pullmann 13:55:51 RubenVerborgh has joined #dxwg 13:56:21 present+ 13:56:46 Present+ Caroline 13:56:50 I'm not getting on to webex - says host has not joined..... I'll try to ping Phil 13:56:57 present+ Rob Atkinson 13:57:24 Jean_ has joined #dxwg 13:58:22 present+ newton 13:58:47 present+ Jean 13:59:09 present+ 13:59:26 Alejandra has joined #dxwg 13:59:50 Present_Thomas has joined #dxwg 14:00:20 present+ 14:00:23 ByronCinNZ has joined #dxwg 14:00:56 present+ ByronCinNZ 14:01:01 LarsG has joined #dxwg 14:01:05 SimonCox has joined #dxwg 14:01:08 present+ alejandra 14:01:10 present+ 14:01:12 erics has joined #dxwg 14:01:19 present+ 14:01:37 regrets- Ruben 14:01:51 zakim, pic a victim 14:01:52 I don't understand 'pic a victim', Caroline 14:01:52 RiccardoAlbertoni has joined #DXWG 14:02:05 zakim, pick a victim 14:02:05 Not knowing who is chairing or who scribed recently, I propose RubenVerborgh 14:02:13 chair: Caroline 14:02:23 scribe: Ruben 14:02:25 does it need to be your nick on present+ - it already knows your nick so I tried putting my real name to add info - will that work? 14:02:29 scribeNick: RubenVerborgh 14:02:41 PWinstanley has joined #dxwg 14:02:42 present+ 14:02:48 https://www.w3.org/2017/05/18-dxwg-minutes 14:02:56 present+ PWinstanley 14:02:58 annette_g has joined #dxwg 14:03:05 s/does it need to be your nick on present+ - it already knows your nick so I tried putting my real name to add info - will that work?// 14:03:20 Topic: Approving Minutes 14:03:22 Anyone knows the webex password? 14:03:50 RESOLUTION: Last week's minutes approved 14:04:00 present+ RiccardoAlbertoni 14:04:31 Alejandra asks for what appears in the minutes 14:04:44 https://www.w3.org/wiki/IRC 14:05:11 q+ 14:05:12 phil: the queue system: if you want to speak, just type q+ 14:05:20 q? 14:05:24 ack p 14:05:34 thanks! 14:05:46 see https://www.w3.org/2001/12/zakim-irc-bot.html 14:06:01 and https://www.w3.org/2002/03/RRSAgent 14:06:36 Topic: Introductions 14:06:40 achille_zappa has joined #dxwg 14:07:16 Jean: works at XXX, PhD student on topic of open data 14:07:29 s/XXX/NIC.br 14:08:03 https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2017.05.25 14:08:05 q+ to ask about other new folks 14:08:22 III. Use case task: Use Case Working Space: discussing the Use Cases addressed and defining the editors 14:08:24 Topic: Use cases 14:08:25 q+ 14:08:44 q- 14:09:02 ack Alejandra 14:09:23 Alejandra: will there be a deadline for use cases? 14:09:52 Caroline: it is flexible, but would be nice to have a deadline, so we can move on with the requirements 14:09:54 q+ 14:10:00 ack q 14:10:03 ack kcoyle 14:10:09 AndreaPerego has joined #dxwg 14:10:21 Karen: let's not wait too long for use cases 14:10:26 +1 to the idea of a month 14:10:28 Let's set a deadline of a month? 14:10:33 +1 for a month 14:10:37 +1 for me (a month) 14:10:39 present+ AndreaPerego 14:10:41 +1 for a month 14:10:42 +1 to setting a deadline in one month 14:10:45 q+ to talk about iterations 14:10:47 +1 for 1 month 14:10:48 +1 for a month 14:10:52 +1 14:11:00 ack phila 14:11:00 phila, you wanted to talk about iterations 14:11:02 Karen: also, other work can go on in the background 14:11:32 Phil: we could then have a first public working draft with use cases 14:11:39 present+ annette_g 14:11:41 q+ 14:11:50 ack kcoyle 14:11:54 can still have updates then 14:12:13 Karen: this also means we'd have complete use cases before the first F2F 14:12:18 +1 14:12:32 +1 14:12:37 Proposal: establish deadline for use cases 14:12:42 +1 14:13:10 PROPOSED: Use Cases to be collected by the end of June 14:13:18 +1 14:13:18 +1 14:13:20 +1 14:13:20 +1 14:13:21 +1 14:13:22 +1 14:13:24 +1 14:13:24 +1 14:13:24 s/Karen/kcoyle/ 14:13:26 +1 14:13:27 +1 14:13:27 +1 14:13:28 +1 14:13:29 +1 14:13:31 +1 14:13:34 RESOLUTION: Use Cases to be collected by the end of June 14:13:36 +1 14:13:49 RRSAgent, draft minutes v2 14:13:49 I have made the request to generate http://www.w3.org/2017/05/25-dxwg-minutes.html phila 14:13:51 +1 14:14:03 phila: is explaining how the process works 14:14:28 RubenVerborgh1 has joined #dxwg 14:14:32 ... showing the minutes and explaining how the resolutions are recorded 14:14:58 Present+ annette_g 14:15:03 Caroline: suggest to define the editors of Use Cases 14:15:04 q+ 14:15:16 present+ achille_zappa 14:15:18 ack fanieli 14:15:41 fanieli: can be one of the editor of the UC doc 14:15:48 q? 14:16:04 q+ 14:16:07 q+ 14:16:07 q+ 14:16:10 ack phila 14:16:21 Caroline: anyone else would like to be an editor with fanieli? 14:16:27 Phil: whichever document we're talking about, editing a document is a scary thing 14:16:38 I will help in this 14:16:40 you may be put off by HTML and GitHub 14:16:42 but you will be helped 14:17:13 q? 14:17:13 these technical things shouldn't stop you from being an editor 14:17:14 q+ availability to help with github and html stuff 14:17:17 ack Alejandra 14:17:22 mdaquin has joined #dxwg 14:17:39 q- availability 14:17:44 Alejandra: I want to edit one of the other documents 14:17:50 but how much time should I consider for that? 14:17:50 q+ 14:18:02 How long is a piece of string? 14:18:14 present+ mathieu 14:18:23 q+ 14:18:36 q? 14:18:46 Phil: use cases document is probably one of the simplest 14:18:52 difficult thing is keeping track 14:18:58 but not a huge job 14:19:04 thanks :-) 14:19:07 q? 14:19:10 time is hard to say, half a day a week until it is done maybe 14:19:11 ack erics 14:19:36 q+ 14:19:42 q+ 14:19:44 Editing UC document: Largely about being organized in keeping lists and cross-references, and making things look a bit uniform 14:20:02 Eric: Should we have sample data for use cases? 14:20:04 q+ to pick up on Eric's question 14:20:26 ack phila 14:20:26 phila, you wanted to pick up on Eric's question 14:20:53 Phil: yes, having real data in the use cases makes them much stronger, definitely encouraged 14:21:17 s/Phil/phila/ 14:21:42 phila: definite +1 for real data 14:21:59 q+ 14:22:07 q- 14:22:17 ack newton 14:22:42 ack roba 14:22:42 newton: Happy to help and contribute with GitHub and HTML 14:23:33 roba: Comment on the use cases: it's useful to distinguish between use cases and example scenarios differently 14:24:33 q? 14:24:40 I agree with roba that we need a canonical model for use cases 14:24:43 ack Jaroslav_Pullmann 14:25:21 Jaroslav_Pullmann: documents important to know how current standards have to be changed 14:25:21 more than 20 use cases, very impressive 14:25:28 if more editors are needed, I can help 14:25:42 helps extract requirements 14:25:46 for new version of DCAT 14:25:55 ack Alejandra 14:26:07 q+ 14:26:44 Alejandra: In terms of documents, if we are working in parallel tracks? 14:26:57 …role of editors: are they the only ones modifying? 14:27:04 …others just make issues? 14:27:26 q+ 14:27:53 Caroline: everything we approve as group must be in the document 14:27:55 ack kcoyle 14:27:59 …that's the main role of the editor 14:28:20 q? 14:28:41 kcoyle: I would suggest that XXX and YYY edit the document 14:28:48 you can distinguish between editors and contributors 14:28:59 s/XXX/Jaroslav_Pullmann/ 14:29:15 s/YYY/fanieli/ 14:29:24 ack roba 14:29:27 Caroline: we can have 3 editors as well 14:29:43 +1 for pull requests 14:29:49 roba: contributions can also be done through pull requests for editors 14:29:52 +1 to erics about distinguishing between editors and contributors as we did in other group 14:30:29 Caroline: other editors? 14:30:29 q? 14:30:35 will be happy to join as editor - can help with git 14:30:39 PROPOSED: Have Jaroslav_Pullmann and fanieli as editors 14:30:58 +1 14:31:07 +1 14:31:08 +1 14:31:10 should probably say what they are editing 14:31:19 +1 14:31:27 +1 14:31:41 Three, I thought 14:31:48 PROPOSED: Have Jaroslav_Pullmann, fanieli and roba as editors of the Use Cases document 14:31:53 +1 14:31:55 +1 14:31:55 t+1 14:31:58 +1 14:31:59 +1 14:32:00 +1 14:32:00 +1 14:32:01 +1 14:32:01 +1 14:32:03 +1 14:32:03 +1 14:32:05 +1 14:32:05 +1 14:32:06 +1 14:32:11 s/t+1/+1/ 14:32:13 s\t+1\+1 14:32:17 +1 14:32:24 +1 14:32:53 roba: no need to vote on GitHub 14:33:10 RESOVED: Have Jaroslav_Pullmann, fanieli and roba as editors of the Use Cases document 14:33:23 RESOLVED: Have Jaroslav_Pullmann, fanieli and roba as editors of the Use Cases document 14:33:50 IV. Starting discussing DCAT and defining the editors 14:33:56 TOPIC: start discussing DCAT 14:33:58 q? 14:34:39 q+ 14:34:45 ack Alejandra 14:35:01 Alejandra: I volunteer 14:35:02 I will help 14:35:05 q 14:35:14 I will assist too 14:35:14 I can help also 14:35:16 I can help too 14:35:20 ack SimonCox 14:35:28 i will help as contributor.. 14:36:05 q? 14:36:05 q+ 14:36:09 ack kcoyle 14:36:28 kcoyle: Given that a number of people couldn't attend, maybe we shouldn't finalize this. 14:36:31 oooh good point 14:36:36 i think it would be better wait for missing people 14:36:51 that's a good point 14:36:54 yeah, the short notice and the holiday are a bit unfortunate for major decisions 14:36:55 - good point Karen - though there will always be missing members (e.g. next week I will not be in the meeting) 14:36:56 I think our charter says we have to do that 14:37:15 +1 to kcoyle about not finalising the list of editors.. 14:37:37 ok by me 14:37:39 Caroline: shall we leave the decision open about use cases as well then? 14:37:45 q? 14:37:50 q+ 14:37:52 +1 14:37:55 ack LarsG 14:38:02 regrets- Lars 14:38:16 wait at least for DCAT 14:38:18 +1 14:38:24 LarsG: let's set editors now for use cases, given short amount of time 14:38:36 +1 to wait for DCAT 14:38:38 + 14:38:38 q? 14:38:39 +1 on waiting 14:38:40 PROPOSED: waiting a week for DCAT 14:38:41 +1 14:38:42 +1 14:38:42 +1 to wait a wewek 14:38:44 +1 14:38:44 +1 14:38:46 +1 14:38:47 +1 14:38:47 +1 14:38:48 +1 14:38:50 +1 14:38:52 +1 14:38:53 +1 14:38:53 +1 or waiting 14:38:55 RESOLVED: let's wait a week for DCAT 14:38:56 Is 'next week' monday? 14:39:02 q+ 14:39:04 +1 it should be noted that this is for the editor vote 14:39:08 V. Announcing the F2F at the University of Oxford on July 17-18 (see Oxford Attendance and logistics) 14:39:11 I think it is actually Monday 14:39:18 Topic: F2F in Oxford, July 14:39:32 q? 14:39:37 ack SimonCox 14:39:51 SimonCox: when are the next decisions made? next meeting is Monday, right? 14:40:03 next Monday is too soon 14:40:08 SimonCox: tripping over ourselves with short notice and deadlines 14:40:20 q+ 14:40:22 next monday is also bank holiday in England 14:40:26 Caroline: next Monday is too soon, let's decide not next Monday, but the one after that 14:40:30 q- 14:40:42 Monday June 5 14:40:51 +1 on 5/6 14:40:52 Is there a point in having a meeting at all next Monday? given short time in between 14:41:01 +1 to 5/6 14:41:17 However - we have to be a bit careful about everyone's holidays ... THere will be a holiday most weeks in one place? 14:41:18 +1 for June 6th 14:41:23 PROPOSED: deciding on editors on June 6th 14:41:35 Monday/Tuesday 14:41:37 PROPOSED: deciding on editors of DCAT on June 6th 14:41:46 6th is Tuesday? totally confused… 14:41:46 q? 14:41:47 +1 14:41:47 June, 6th, is Tuesday. 14:41:55 June 5th 14:41:57 June 5th is Monday 14:42:11 +1 14:42:19 GMT 14:42:19 PROPOSED: deciding on editors of DCAT on June 5th 4PM UTC 14:42:25 aargh 14:42:29 s/4PM/2PM/ 14:42:35 +1 14:42:36 +1 14:42:38 +1 14:42:38 +1 14:42:39 +1 14:42:40 +1 14:42:42 +1 14:42:44 +1 14:42:49 +1 14:42:49 +1 14:42:53 +1 14:42:54 +1 14:42:56 0 (but as said it's a holiday) 14:42:58 Lets stick to date and time in UTC 14:43:04 +1 14:43:16 RESOLVED: deciding on editors of DCAT on June 5th 2PM UTC 14:43:28 Caroline: back to F2F now 14:43:28 +1 to SimonCox 14:43:31 q+ 14:43:41 q+ 14:43:46 ack Caroline 14:43:50 ack Alejandra 14:44:04 q+ 14:44:06 Alejandra: could be good to know ASAP how many people tend to attend, for size of room (25) 14:44:15 I plan to attend 14:44:25 Will remote attendees be supported? 14:44:28 I plan to attend :) 14:44:31 Alejandra: sent around hotels 14:44:37 attendance doc: https://www.w3.org/2017/dxwg/wiki/Oxford_Attendance_and_logistics 14:44:53 q- 14:45:00 q+ 14:45:02 would love to - but its a bit short notice for funding options. 14:45:03 q+ 14:45:20 Phil: remote attendees will be supported 14:45:21 ack fanieli 14:45:25 great, thank you! 14:45:40 fanieli: how will F2F be different then what we're doing from week to week? 14:45:58 Caroline: I see it as a marathon 14:46:06 …2 days, very intense, lot of work, great work 14:46:10 …still use IRC to document 14:46:22 …also hands-on, write down ideas 14:46:30 …discuss them, have as many resolutions as possible 14:46:38 …go deeper, profound about things 14:47:10 RRSAgent, draft minutes v2 14:47:10 I have made the request to generate http://www.w3.org/2017/05/25-dxwg-minutes.html AndreaPerego 14:47:25 q? 14:47:28 ack phila 14:47:49 phila: meeting online is baffling until you get used to it 14:47:53 …in a F2F, two important things happen 14:48:02 …we get through a lot, intense discussion 14:48:12 …but also, "there's no such thing as a virtual beer" 14:48:16 ;o) 14:48:28 +1 to "there's no such thing as a virtual beer" :) 14:48:28 Lol 14:48:34 …when you get together, you interact socially as well as professionally 14:48:44 …group comes together much better after F2F 14:49:12 It is well worth it if you can attend! I'd rather visit Oxford :-) 14:49:13 not just budget, also travel *time* which is large for some ... 14:49:21 thanks, yes, Caroline told me about this - I hope it should be fine 14:49:25 …satisfying and lot of fun 14:49:26 q? 14:49:40 Caroline: we can always have F2F in other places 14:50:06 q? 14:50:25 Topic: setting the meeting time 14:50:48 VI. Setting regular meeting time 14:50:53 Caroline: is always difficult 14:51:02 …but let's discuss with group, we can change 14:51:11 …It's a group discussion 14:51:40 …we'll now follow the Doodle 14:51:44 Doodle poll was clear. Monday 1400 14:52:08 …if we decide in task forces, they can adjust 14:52:16 RRSAgent, draft minutes v2 14:52:16 I have made the request to generate http://www.w3.org/2017/05/25-dxwg-minutes.html phila 14:52:17 q? 14:52:19 s/decide in/decide to split in/ 14:52:38 q+ 14:52:42 ack phila 14:53:04 phila: if the group splits, which is likely, those subgroups can have their own times 14:53:08 q+ 14:53:11 -> https://w3c.github.io/dxwg/ucr/ UCR 14:53:13 q+ 14:53:28 q? 14:53:38 Phil: set up the skeleton 14:54:01 ack RubenVerborgh1 14:54:19 RubenVerborgh1: Should the next meeting be on Monday on the week after that? 14:54:22 q+ 14:54:26 q? 14:54:28 ... Its' very short notice if it's this coming Monday 14:54:28 didn't we just vote to wait a week? 14:54:29 ack RubenVerborgh1 14:54:35 ack Jaroslav_Pullmann 14:54:39 q- 14:54:56 Jaroslav_Pullmann: should agree on some progress 14:55:04 q? 14:55:15 …are we going to merge the use cases out there? 14:55:16 ack kcoyle 14:55:41 kcoyle: yes, you end up editing them into a coherent document 14:55:54 merge and group 14:56:09 …let's use Monday to actually talk about use cases 14:56:11 q+ 14:56:16 q? 14:56:43 …possible that not every use case will end up there, because of duplication 14:57:05 ack AndreaPerego 14:57:38 Current use-cases - https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space 14:58:17 q+ 14:58:23 AndreaPerego: even though there is overlap, you may want to keep most of them, and group them by categories 14:58:25 ack Jaroslav_Pullmann 14:58:43 Jaroslav_Pullmann: we should pertain the different areas that they are covering 14:58:48 q+ 14:58:50 q? 14:59:43 andrea: contributors maybe should indicate which of their use cases overlap or relate to other use cases 14:59:46 ok 14:59:49 ack phila 15:00:15 phila: I would recommend to work out early on criteria for relevance of use cases 15:00:27 …will be edge cases, people will want this or that in 15:00:34 +1 to work out early on criteria for relevance of use cases 15:00:34 it is probably useful to take a look to use cases document prepared in previous w3c working group just to get inspired. 15:00:42 …document criteria, can save a lot of hassle 15:01:00 s/document criteria/document those criteria/ 15:01:55 Next Meeting Monday 5 June 15:02:02 fine! 15:02:03 RRSAgent, pointer? 15:02:03 See http://www.w3.org/2017/05/25-dxwg-irc#T15-02-03 15:02:05 +1 15:02:09 bye bye 15:02:13 Caroline: keep discussions on e-mail by now 15:02:17 Bye 15:02:17 bye 15:02:18 bye bye 15:02:18 bye all! 15:02:19 Bye bye 15:02:20 bye 15:02:21 Thank you Caroline, By 15:02:21 Bye 15:02:22 thank you! 15:02:23 bye 15:02:24 bye 15:02:25 bye 15:02:25 Thanks and bye! 15:02:29 bye 15:02:30 RRSAgent, draft minutes 15:02:30 I have made the request to generate http://www.w3.org/2017/05/25-dxwg-minutes.html phila 15:02:45 RRSAgent, draft minutes v2 15:02:45 I have made the request to generate http://www.w3.org/2017/05/25-dxwg-minutes.html phila 15:04:21 RRSAgent, draft minutes v2 15:04:21 I have made the request to generate http://www.w3.org/2017/05/25-dxwg-minutes.html phila 15:13:27 annette_g has left #dxwg 15:24:35 present- 15:26:31 newton has joined #dxwg 16:27:31 newton has joined #dxwg 16:35:52 newton has joined #dxwg 16:37:28 phila has joined #dxwg 17:33:02 Zakim has left #dxwg