19:44:02 RRSAgent has joined #dxwg 19:44:02 logging to https://www.w3.org/2019/09/03-dxwg-irc 19:44:12 rrsagent, make logs public 19:44:18 chair: PWinstanley 19:44:48 regrets+ Annette; DaveBrowning (likely), Alejandra, Dave Raggett 19:44:55 meeting: DXWG Plenary 19:45:21 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2019.09.03 19:45:42 present+ 19:45:43 rrsagent, create minutes v2 19:45:43 I have made the request to generate https://www.w3.org/2019/09/03-dxwg-minutes.html PWinstanley 19:57:08 TomB has joined #dxwg 19:59:16 kcoyle has joined #dxwg 20:01:03 present+ TomB 20:03:22 ncar has joined #dxwg 20:03:45 present+ 20:05:18 antoine has joined #dxwg 20:05:32 present+ antoine 20:05:39 rrsagent, please draft minutes 20:05:39 I have made the request to generate https://www.w3.org/2019/09/03-dxwg-minutes.html antoine 20:05:45 scribenick: antoine 20:05:49 AndreaPerego has joined #dxwg 20:05:53 present+ 20:05:54 present+ 20:06:46 q+ 20:06:46 q+ 20:06:48 Topic: admin 20:06:56 https://www.w3.org/2019/08/27-dxwg-minutes 20:07:02 proposal: to accept minutes of last meeting 20:07:17 ack TomB 20:07:45 antoine has joined #dxwg 20:07:53 TomB: topic 4 should be topic 5 20:08:19 ack kcoyle 20:08:25 ... I've typed the wrong topic. Topic 4 should be deleted/merged with next topic 20:09:11 Makx has joined #dxwg 20:09:14 +1 20:09:17 0 (was not there) 20:09:18 0 - not there 20:09:18 +1 20:09:20 +1 20:09:36 present+ Makx 20:09:47 0 - not there 20:09:49 resolved: to accept the minutes of last week 20:10:10 RRSAgent, draft minutes v2 20:10:10 I have made the request to generate https://www.w3.org/2019/09/03-dxwg-minutes.html AndreaPerego 20:10:18 Topic: Review of deadlines 20:10:23 q- 20:11:14 PWinstanley: kcoyle will you put something on the main page of the wiki? 20:11:19 kcoyle: I'm working on it 20:11:40 ... we need something to present versions to the group and group decisions 20:12:14 ... the date for final move to DCAT CR was in Oct I think 20:12:43 ... there are some deadlines mid-September (I think) for making decisions on Conneg and PROF 20:13:04 Action: kcoyle to put a table of deadlines on wiki 20:13:04 Created ACTION-363 - Put a table of deadlines on wiki [on Karen Coyle - due 2019-09-10]. 20:13:34 RiccardoAlbertoni has joined #dxwg 20:13:42 Topic: DCAT update 20:13:49 RRSAgent, draft minutes v2 20:13:49 I have made the request to generate https://www.w3.org/2019/09/03-dxwg-minutes.html AndreaPerego 20:14:07 present+ 20:14:16 PWinstanley: for DCAT there have not been meetings on the past two weeks. 20:14:26 yes we have a meeting tomorrow 20:15:00 PWinstanley: I expect tomorrow's meeting will discuss deadlines we've just mentioned. 20:15:09 Not from my side. 20:15:27 Topic: Conneg update 20:15:29 RRSAgent, draft minutes v2 20:15:29 I have made the request to generate https://www.w3.org/2019/09/03-dxwg-minutes.html AndreaPerego 20:15:30 Conneg is 3PWD candidate: https://w3c.github.io/dxwg/conneg-by-ap/ 20:16:00 ncar: I've got access to github now and could merge the PRs 20:16:16 ... we're meeting tomorrow 20:16:39 Just to note respec reports errors/warnings. 20:17:09 PWinstanley, ncar: we need to coordinate on a poll for 3PWD 20:17:16 Yes, we know! A link we expect to fix 20:17:21 ack kcoyle 20:17:44 kcoyle: there is a discussion about including tokens in Conneg 20:17:54 ... how would a decision on this affect the timetable? 20:18:13 ncar: like anything, if there's a serious case for change 20:18:25 ... there is a whole section there, motivated by use case 20:18:38 ... there is a discussion on whether these cases are important 20:18:52 ... the question is the positioning of the IETF about this. 20:19:16 ... it could be about not disallowing tokens. 20:19:35 kcoyle: we need a drop-dead date for making a decision on this, for passing to next WD 20:19:54 Or mark it as a feature at risk? 20:20:19 PWinstanley: we've got experience about marking features at risk in DCAT 20:21:08 ... this could allows to avoid the full circle of validations 20:21:31 RRSAgent, please draft minutes 20:21:31 I have made the request to generate https://www.w3.org/2019/09/03-dxwg-minutes.html antoine 20:21:44 Yes, this is what I meant. 20:21:50 rrsagent, create minutes v2 20:21:50 I have made the request to generate https://www.w3.org/2019/09/03-dxwg-minutes.html antoine 20:22:51 plh has joined #dxwg 20:23:34 https://github.com/w3c/dxwg/wiki/Steps-to-Recommendation-2019 20:23:38 plh: drop-dead dates are on the wiki page 20:24:37 ... features at risk is features that can be removed, or made informative, without affecting the structure of the rec 20:24:56 ... this allows experimenting with the feature until the end of the CR 20:25:19 without this, if you want to remove the feature you have to create a new CR and wait for 60 days for doing so. 20:25:26 kcoyle has joined #dxwg 20:25:52 ... usually the price is feelings. But in doubt, it's wiser to declare features at risk. 20:26:05 s/feelings/possible hurt feelings/ 20:26:26 s/structure of the spec/consistency of the spec/ 20:26:39 rrsagent, create minutes v2 20:26:39 I have made the request to generate https://www.w3.org/2019/09/03-dxwg-minutes.html antoine 20:28:47 Topic: Pull requests and closing of issues 20:29:24 PWinstanley: the past process (based on informative flagging) was not satisfactory 20:29:48 q+ 20:30:00 ... some issues were re-opened because there was no clear evidence that the issue was resolved 20:30:14 ... I'd like a formalized procedure for closing issues 20:30:32 q- 20:30:45 ... We have a table each week, and the opportunity for the plenary to make a formal statement that the issues can be closed. 20:30:53 q+ 20:30:59 q+ 20:30:59 ack plh 20:31:16 plh: you're running out of time 20:31:43 ... you're supposed to make a decision on moving to CR in two weeks 20:32:02 ... are you suggesting to go through all these issues? 20:32:21 PWinstanley: no, what we want to avoid enthusiastic closing of issues 20:32:25 q+ to ask who is responsible for tracking issues 20:32:31 ack antoine 20:32:38 q+ 20:32:50 antoine: I'm not sure what you're suggesting? 20:33:43 q+ 20:33:45 ... we want to give people an opportunity to jump in 20:33:54 q+ 20:34:00 ack TomB 20:34:00 TomB, you wanted to ask who is responsible for tracking issues 20:34:05 Antoine: what precisely will happen? 20:34:19 PWinstanley: we would discuss issues in plenary 20:35:08 TomB: the list is overwhelming 20:35:35 ... the deadline is next Friday (the 13th?) and some of the issues have been opened for one year 20:35:54 ... Whose responsibility is it to track this? 20:36:02 q? 20:36:13 ... Should responders track the issues that correspond to their feedback? 20:36:40 Which issue Tom? 20:37:10 q- 20:37:20 ... I was involved in an issue and it's not clear why it would be closed 20:37:22 q+ 20:37:24 ack ncar 20:38:21 ncar: now I'm replying to people, detailing what has been done and this happens every week. 20:38:49 ... all issues were re-opened 20:39:57 PWinstanley: it's not you ncar . there needs to be a ping-pong 20:40:29 ... we need to sort things out. 20:40:47 q? 20:40:56 ncar: we try to do this every week. 20:41:17 plh: can we get into the specifics? 20:42:28 q+ to point out https://lists.w3.org/Archives/Public/public-dxwg-comments/2019Feb/0001.html 20:42:53 ack plh 20:42:58 ack antoine 20:43:34 https://github.com/w3c/dxwg/issues/698 20:44:11 https://github.com/w3c/dxwg/issues/402 20:44:20 antoine: My approach is that I've seen and contributed to this list of issues and there is an issue proposed for closing, if I have an objection or make a minor comment then this is OK, 20:44:41 https://github.com/w3c/dxwg/issues/467 20:46:00 ... It is completely OK for people to look at these issues and make comments - this doesn't need to have plenary activity, it can be done bilaterally between the author and the person raising the issue 20:46:54 plh: Can I suggest that use of thumbs up icons will help show that the proposal is agreeable 20:47:21 +1 to antoine ( asking for objections is enough in my opinion) 20:47:59 q+ 20:48:04 +1 to antoine 20:48:12 ack TomB 20:48:12 TomB, you wanted to point out https://lists.w3.org/Archives/Public/public-dxwg-comments/2019Feb/0001.html 20:48:19 +1 to thumps up 20:50:16 TomB: I understand the process is stressful 20:50:40 ... is it the responsibility of commenters to keep track of whether their comments have been answered? 20:51:03 plh: from a W3C process we expect answers to comments 20:51:43 TomB: if the comments are made on the public list, shouldn't the answer go there? 20:51:55 plh: it could be on github, or on the list 20:52:25 ncar: I saw the email, I don't think it has gone through issues 20:52:32 ... I would still like to do this 20:52:46 ... and answer both on the list and github 20:52:58 ... I've done this today for 3 commenters 20:53:15 ... I haven't got to TomB's one yet 20:53:31 q+ 20:53:36 ack antoine 20:54:13 RRSAgent, draft minutes v2 20:54:13 I have made the request to generate https://www.w3.org/2019/09/03-dxwg-minutes.html AndreaPerego 20:54:23 antoine: I've several points: - I've seen public comments and answers and this is what TomB was thinking about, it is the right direction 20:55:21 ... - the process of creating issues is important. The public comment list is not so crowded and it is easy to identify emails that haven't been commented, so we can clear these up quite quickly 20:55:25 q+ to ask whether today's comments to https://github.com/w3c/dxwg/issues/792 will be turned into an issue (as an example) 20:56:44 ... The issues that have been closed - I've been working with Nick to make the list. It is not intended for closing really hard issues, but for the simple cases. We don't want to have unresolved questions, just to have some good housekeeping 20:56:48 ack TomB 20:56:48 TomB, you wanted to ask whether today's comments to https://github.com/w3c/dxwg/issues/792 will be turned into an issue (as an example) 20:57:33 TomB: there is a comment today in https://github.com/w3c/dxwg/issues/792 20:57:54 ... issues about the design of the spec 20:58:00 q+ PWinstanley 20:58:06 ... issues can be used to explained the rationale 20:58:19 ... it's hard to see the fundamental issues 20:58:43 q+ 20:58:52 ... they're getting snowed under 20:58:54 q+ 20:59:56 ack PWinstanley 21:00:38 PWinstanley: for DCAT we decided to shelve issues for the next version 21:01:07 ... we could this, ensure we've got documentation and point to the fact that a subsequent team would update 21:01:16 ... plh would this idea of backlog work? 21:01:43 plh: it could, assuming that the issues can be fixed. 21:02:08 PWinstanley: there were fundamental issues on DCAT like versioning, that we left 21:02:25 plh: the editors need to triage 21:02:28 q? 21:03:14 plh: we cannot change the architecture between v1 and v2. 21:03:24 ack antoine 21:04:19 antoine: I was at the call discussing this process previously, and getting issues on the list was part of the triage, to remove the small items and raise the profile of the larger issues 21:04:24 ack plh 21:05:06 plh: I understand that TomB and ncar are stressed, but a decision needs to be made in two weeks 21:05:24 ... if we don't have the time, we don't have the time 21:06:10 q+ to say that WG Note is a perfectly good outcome 21:06:16 TomB: this is too much work 21:06:40 PWinstanley: yes but we need to try, give each other feedback 21:06:54 rrsagent, create minutes v2 21:06:54 I have made the request to generate https://www.w3.org/2019/09/03-dxwg-minutes.html antoine 21:07:33 TomB: I think a WG Note would be a good outcome 21:07:52 PWinstanley: if we miss the drop-dead dates we'll move from CR to Note 21:08:31 rrsagent, create minutes v2 21:08:31 I have made the request to generate https://www.w3.org/2019/09/03-dxwg-minutes.html PWinstanley 21:08:35 plh: and the priority is to update DCAT 21:08:38 Thank you, Bye ! 21:08:39 rrsagent, create minutes v2 21:08:39 I have made the request to generate https://www.w3.org/2019/09/03-dxwg-minutes.html antoine 21:08:50 bye