20:51:00 RRSAgent has joined #dxwg 20:51:00 logging to https://www.w3.org/2019/02/12-dxwg-irc 20:51:07 Zakim has joined #dxwg 20:51:16 rrsagent, make logs public 20:52:54 regrets+ Andrea Perego, Makx, Antoine, Jaroslav Pullmann 20:53:01 present+ 20:53:09 rrsagent, create minutes v2 20:53:09 I have made the request to generate https://www.w3.org/2019/02/12-dxwg-minutes.html kcoyle 20:55:31 PWinstanley has joined #dxwg 20:59:07 AndreaPerego has joined #dxwg 20:59:18 regrets- Andrea Perego 20:59:23 present+ AndreaPerego 20:59:38 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2019.02.12 20:59:42 ncar has joined #dxwg 20:59:49 present+ 20:59:57 meeting: DXWG Plenary 20:59:57 meeting: Dataset Exchange Working Group Plenary 21:00:01 dsr has joined #dxwg 21:00:03 RRSAgent, draft minutes v2 21:00:03 I have made the request to generate https://www.w3.org/2019/02/12-dxwg-minutes.html AndreaPerego 21:00:14 present+ 21:00:39 meeting: DXWG Plenary 21:00:42 RRSAgent, draft minutes v2 21:00:42 I have made the request to generate https://www.w3.org/2019/02/12-dxwg-minutes.html AndreaPerego 21:01:13 chair: PWinstanley 21:01:14 RRSAgent, draft minutes v2 21:01:14 I have made the request to generate https://www.w3.org/2019/02/12-dxwg-minutes.html AndreaPerego 21:02:22 roba has joined #dxwg 21:02:52 scribe: ncar 21:03:22 present+ 21:03:39 annette_g has joined #dxwg 21:03:41 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2019.02.12 21:04:20 RRSAgent, draft minutes v2 21:04:20 I have made the request to generate https://www.w3.org/2019/02/12-dxwg-minutes.html AndreaPerego 21:05:38 topic: confirm agenda 21:05:49 +1 21:05:59 present+ 21:06:03 present+ 21:06:14 present+ 21:06:18 +1 21:06:19 proposed: approval of minutes Feb 5th 21:06:28 DaveBrowning has joined #dxwg 21:06:28 0 (was not there) 21:06:40 https://www.w3.org/2019/02/05-dxwg-minutes 21:06:40 https://www.w3.org/2019/02/05-dxwg-minutes 21:07:00 0 (not there) 21:07:03 +1 21:07:09 +1 21:07:18 present+ 21:07:25 +1 21:07:46 0 (not there) 21:08:08 resolution: approval of minutes Feb 5th 21:08:53 RRSAgent, draft minutes v2 21:08:53 I have made the request to generate https://www.w3.org/2019/02/12-dxwg-minutes.html kcoyle 21:08:55 topic: Open Action Items 21:09:08 https://www.w3.org/2017/dxwg/track/actions/open 21:10:18 About action-282: https://lists.w3.org/Archives/Public/public-dxwg-wg/2019Jan/0562.html 21:10:31 resolution: action-289 21:10:54 resolution: issue-289 21:11:01 close action-282 21:11:01 Closed action-282. 21:11:14 close action-289 21:11:15 Closed action-289. 21:11:19 rrsagent, draft minutes v2 21:11:19 I have made the request to generate https://www.w3.org/2019/02/12-dxwg-minutes.html DaveBrowning 21:11:45 topic: Discussion about sprints 21:12:12 PWinstanley: we have had a couple of DCAT and one on Guidance coming 21:12:32 PWinstanley: DaveBrowning & kcolye to describe 21:13:09 s/kcolye/kcoyle/ 21:13:36 DaveBrowning: thinks last DCAT sprint successful, not so much authoring but lots of agreements on next actions, second sprint tomorrow, focussing on versioning, haven't thought too far beyond that but thinks that they have covered major issues 21:13:59 PWinstanley: we must decide when to call a halt to everything 21:14:15 PWinstanley: sprints seem to be well received & make progress 21:14:44 PWinstanley: should we get position on halting after next sprint? 21:15:51 DaveBrowning: yes, after tomorrow's sprint, we should be in a good position to determine next stage of the DCAT doc, e.g. what to do about Reqs about alignment so far unaddressed - are these for the WG or other, non-normative groups? 21:16:16 DaveBrowning: critical aspects of the DCAT spec all done 21:16:32 alejandra has joined #dxwg 21:16:39 present+ 21:17:17 PWinstanley: are working procedures appropriate? 21:17:36 DaveBrowning: based on one workshop, yes, it went well 21:18:03 DaveBrowning: good to dedicate time to a specific set of issues 21:18:43 RRSAgent, draft minutes v2 21:18:43 I have made the request to generate https://www.w3.org/2019/02/12-dxwg-minutes.html AndreaPerego 21:18:56 https://w3c.github.io/dxwg/profiles/ 21:19:29 kcoyle: we've done a 1 hr sprint and have revised Sec 1 of Guidance doc and have requested another 2 hr session this week 21:19:53 kcoyle: we will be looking at Sec 2 21:19:57 https://docs.google.com/document/d/1Y4jP4SGZMnt63EpjTX11-hW6-3mxlaq1i-Lbiw4tx1M/edit#heading=h.xsyg95spoofu 21:20:27 alejandra_ has joined #dxwg 21:20:44 kcoyle: anyone can make Google Doc suggestions on that doc 21:21:12 kcoyle: we are trying to get as many edits as possible into the doc and are so far happy with the approach 21:21:30 q+ 21:21:47 PWinstanley: any lessons learned? 21:22:05 kcoyle: get lots of content into Google Doc 21:22:12 PWinstanley: coverage rather than depth 21:22:17 ack ncar 21:22:32 ncar: if there is a problem with webex CSIRO can provide 21:23:42 topic: Karen's email for proceedure for replying to comments 21:24:01 https://lists.w3.org/Archives/Public/public-dxwg-wg/2019Feb/0218.html 21:24:47 yes, that's what we've done in DCAT 21:24:52 kcoyle: we have a proceedure here, thank the commenter, return to (sub)group to discuss before formulating a reply 21:25:09 DaveBrowning: we have mostly done this in DCAT 21:25:22 s/proceedure/procedure/ 21:25:36 kcoyle: we recognised mailing list v. GitHub Issues 21:26:20 kcoyle: when we reach concensus in Issues' discussion, we have something to point to for following up comments 21:26:48 there is a label called 'feedback' 21:26:56 kcoyle: we should keep a list of the comments we've gotten - create a GitHub label to indicate outside input 21:26:57 q? 21:27:05 +q 21:27:18 q+ 21:28:02 PWinstanley: we need to ensure we aren't open to collusive behaviour, this is important for EU and similar org adoption 21:28:08 q? 21:28:29 PWinstanley: wide discussion & propper procedure are important 21:28:51 PWinstanley: there is also a rewuired W3C agreement about not holding on to patents 21:29:05 PWinstanley: important if secondary to core standards work 21:29:12 ? 21:29:15 ack alejandra 21:29:32 s/propper/proper/ 21:29:46 s/rewuired/required/ 21:29:48 alejandra_: we have a 'feedback label for GitHub 21:30:00 s/'feedback/'feedback' 21:30:07 ack ncar 21:30:35 ncar: I created a feedback label and things I've dealt with are tagged in that way 21:30:50 Q+ 21:30:52 SimonCox has joined #dxwg 21:30:55 ack o 21:31:06 PWinstanley: any further comments on this SOP? 21:31:17 kcoyle: dsr, is this in line with other groups? 21:31:35 dsr: haven't seen sprints much elsewhere 21:31:45 kcoyle: meant proceedures for responses more 21:31:56 rrsagent, draft minutes v2 21:31:56 I have made the request to generate https://www.w3.org/2019/02/12-dxwg-minutes.html DaveBrowning 21:32:00 s/proceedures/procedures/ 21:32:15 present+ 21:32:20 dsr: normally, proceedure is to invite people within the group to come up with comments, position established and presented back to group 21:32:29 apologies for joining late - network was down 21:32:51 kcoyle: are you, dsr, aware of what needs to be presented to prove feedback for document next stages? 21:33:15 dsr: you need to indicate how you've handled comments and the means, email, GitHub, may vary 21:33:53 dsr: you want to make sure all important comments have been addressed to the satisfaction of the commentor, not necissarily by agreement 21:34:17 kcoyle: we have asked commentors, have we satisfied you 21:34:22 dsr: seems sensible 21:34:24 ack roba 21:35:16 roba: can we filter GitHub issues to reveal all those not from WG meetings 21:35:37 https://github.com/w3c/dxwg/pull/750 21:36:09 alejandra_: new W3C check for WG users is applied to all PRs and fails if person not registered in WG 21:36:23 q+ 21:36:30 ack ncar 21:36:30 q+ 21:36:54 I don't think the list of contributors is so long that we can't manually cross check against WG members 21:36:59 we could use the github API and write some code to do that 21:37:18 q+ 21:37:24 ack annette_g 21:37:26 yeah, maybe manually cross checking is easier as SimonCox says 21:37:54 ncar: we can filter for WG Isseus using GitHub filter 21:37:57 ack roba 21:39:12 roba: how do we handle private comments on items which are then agreed to be forwarded to the Comments list? Assumption is it goes to Comments and then we respond formally, even if we've informally responded before 21:39:25 s/Isseus/Issues 21:39:57 q+ 21:40:03 ack ncar 21:41:01 would it help to send the emails also to the comments list? 21:41:23 ncar: some comments come in privately, even if people are directed to public Comments list 21:41:41 PWinstanley: chairs responsibility to ensure probity of responses 21:42:16 topic: continued discussion about 5FTF 21:42:31 PWinstanley: is 5FTF sensible? 21:42:39 PWinstanley: how do we coordinate deliverables 21:42:41 q+ 21:42:49 ack ncar 21:44:06 q+ 21:44:10 ncar: there are many places where coordination is needed, but as the document on profiles guidance matures this will be clearer 21:44:13 ack DaveBrowning 21:45:01 DaveBrowning: there are un-touched issues touching on DCAT profiles or profiles of DCAT. Haven't assessed what we need from Prof Guide here 21:45:43 PWinstanley: subgroups & sprints should bear coordination in mind. Perhaps logging them in GitHub or Google Docs for drafts 21:46:09 q+ 21:46:13 ack kcoyle 21:46:14 PWinstanley: 5FTF, are people interested in making a plan for something in a couple of months? 21:46:56 kcoyle: complication is that it is almost at the end of the charter, will the charter be extended, if so a meeting would perhaps make more sense 21:47:48 PWinstanley: should we pensil an FTF in, rather than making a committment? Or are multiple sprints the way to go? 21:47:56 q+ 21:48:01 ack ncar 21:48:35 ncar: We have a lot of potential to extract from sprints before we consider a F2F 21:50:07 PWinstanley: 10min to go, there is merit in ending early, thanks everyone, we have sprints and meetings tomorrow and sprints the next day 21:51:06 bigbluehat: people who have logged on from the Lyon meeting and seem to be on permanently 21:51:29 SimonCox: can we kick bigbluehat off? 21:52:14 ncar: we have had other permalogons before e.g. Hadley Beeman 21:52:58 dsr: I can ask W3C if people can be evicted from IRC 21:53:29 PWinstanley: potentially remove bigbluehat sandro @rhiaro 21:53:46 PWinstanley: if we can boot them off, they can come back if the want 21:54:05 ncar: I suspect a stray browser tab is open somewhere and hidden 21:54:07 In my client, I can see when each person's last activity was. 21:54:35 dsr: present plus is the basis for meeting presence 21:54:53 rrsagent, draft minutes v2 21:54:53 I have made the request to generate https://www.w3.org/2019/02/12-dxwg-minutes.html SimonCox 21:55:33 PWinstanley: dsr, please do have a chat about policy on this and if people can be cleared 21:55:50 they have recent activity 21:55:59 but I don't think it's in this channel 21:56:18 PWinstanley: enjoy Valentine's day 21:56:24 RRSAgent, draft minutes v2 21:56:24 I have made the request to generate https://www.w3.org/2019/02/12-dxwg-minutes.html AndreaPerego 21:56:28 bye, thanks 21:56:34 bye