20:52:19 RRSAgent has joined #dxwg 20:52:24 logging to https://www.w3.org/2023/11/07-dxwg-irc 20:52:31 rsagent, make logs public 20:53:24 RiccardoAlbertoni has joined #dxwg 20:59:03 present+ 20:59:08 scribe pwinstanley 20:59:25 present+ 21:01:48 AndreaPerego has joined #dxwg 21:02:15 present+ 21:02:29 chair: pchampin 21:02:38 present+ 21:06:54 pchampin: The meeting - before going to CR, we need to check that everything is in order to avoid future problems. 2 things: close any issues in github that we can; the wider review, the standard one and the one relating to groups specifically mentioned in the charter, have to be dealt with. 21:07:06 https://github.com/w3c/dxwg/issues?q=is%3Aissue+is%3Aopen+label%3Adcat+-label%3Afuture-work 21:07:17 alejandra has joined #dxwg 21:07:30 DaveBrowning has joined #dxwg 21:07:51 q+ 21:07:57 ... Issues: see the link above. 21:08:05 present+ 21:08:39 q+ 21:08:39 ... Issue #1561 - is probably out of date. 21:08:49 ack RiccardoAlbertoni 21:09:30 present+ 21:09:42 RiccardoAlbertoni: yes, it is. I was trying to make a proposal 21:09:54 https://www.w3.org/2017/dxwg/wiki/Main_Page 21:10:20 roba has joined #dxwg 21:10:35 present+ 21:10:53 RRSAgent, draft minutes 21:10:55 I have made the request to generate https://www.w3.org/2023/11/07-dxwg-minutes.html AndreaPerego 21:11:24 pchampin: the last 2 lines say '2023', but should be '2024' 21:11:48 ... I think we can go with that proposal 21:12:59 ... Once the issue is updated, then we can close. But it is like a noticeboard and so is OK to leave open too 21:13:28 ... Just add a pointer to the timetable in the wiki 21:14:59 ... We need 28 days between CR publication and transition - we should exclude holidays around Christmas etc - but as long as the timetable proposal is realistic we are OK 21:15:14 RRSAgent, make logs world 21:15:17 RRSAgent, draft minutes 21:15:18 I have made the request to generate https://www.w3.org/2023/11/07-dxwg-minutes.html AndreaPerego 21:15:25 q? 21:15:43 ... The issue should probably stay open until the completion of the timetable 21:15:54 action: RiccardoAlbertoni to update the issue 21:16:03 action: RiccardoAlbertoni to update issue 1561 with the latest schedule (link above) 21:16:31 meeting: DXWG DCAT subgroup meeting 21:16:39 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2023.11.07 21:16:42 RRSAgent, draft minutes 21:16:43 I have made the request to generate https://www.w3.org/2023/11/07-dxwg-minutes.html AndreaPerego 21:16:49 pchampin: The next issue is 1509. This is a checklist. Most are checked apart from a small number. 21:17:10 q+ 21:17:13 ... The only unchecked boxes are in our list, so we can also keep this until the end of the schedule 21:17:17 ack AndreaPerego 21:18:04 AndreaPerego: This issue has been open since 2019. The problem is that when we get references from the W3 software there is inconsistency in the results 21:18:25 ... unless it is fixed centrally, we need to make a local fix 21:19:06 pchampin: I am not sure that this is a bug - it might be a feature. 21:20:17 AndreaPerego: I think it is a bug because the editors are given as those for version 1 21:21:39 ... the link points to DCAT 2, not DCAT 1. So there is an inconsistency between the short name without the version number in SpecRef and the TR link 21:22:44 pchampin: we should fix our problem at our level, and close this issue 21:23:14 ... but, this is mainly editorial, so we can keep the issue open and fix at PR time 21:23:23 q? 21:23:42 pchampin: Are we happy about having the local fix? 21:24:08 ... looks like there is no objection to this approach 21:24:21 +q 21:24:24 pchampin: Next issue -1352 21:24:39 ack RiccardoAlbertoni 21:25:03 https://github.com/w3c/dxwg/issues/1352 21:25:05 RiccardoAlbertoni: a reminder that at some point we need to provide translations to other languages 21:26:03 ... we need to consider this within our schedule because it will take time 21:27:02 pchampin: What are the specific success criteria? It seems like a 'nice to have' and not essential for moving through to CR etc 21:27:18 RiccardoAlbertoni: It is something that matters to the group 21:27:28 s/rsagent, make logs public// 21:27:39 s/scribe pwinstanley// 21:27:39 q? 21:27:46 RRSAgent, draft minutes 21:27:47 I have made the request to generate https://www.w3.org/2023/11/07-dxwg-minutes.html AndreaPerego 21:27:53 pchampin: Agreed, but it isn't essential - we keep the issue open but it is not an obstacle 21:28:26 ... Issue 1352 is an unticked box in 1509. 21:29:12 ... So we should be consistent - I don't think keeping this issue open (1352) isn't blocking the closure of 1509 21:29:48 ... so I propose to remove them from the list - 21:30:24 PROPOSED: remove issues 1223 and 1352 from the meta-issue 1509 ("to be adressed for CR") 21:30:28 rrsagent, create minutes v2 21:30:30 I have made the request to generate https://www.w3.org/2023/11/07-dxwg-minutes.html pwinstanley 21:30:36 +1 from me 21:30:36 +1 21:30:36 +1 21:30:36 +1 21:30:45 RESOLVED: remove issues 1223 and 1352 from the meta-issue 1509 ("to be adressed for CR") 21:31:21 +1 21:31:22 +1 21:32:55 pchampin: Issue 1507 21:33:01 https://github.com/w3c/dxwg/issues/1507 21:33:17 ... This is one of the horizontal reviews. 21:33:47 RiccardoAlbertoni: I think we can close this 21:33:52 +1 21:34:13 pchampin: agreed because we have had correspondence with reviewers. Any objection to closing? 21:34:23 +1 21:34:30 ... I think we can proceed 21:34:30 q? 21:35:30 pchampin: The remaining issue is 1502 - about the wide review. Only open because of the need to cover reaching out to all groups in our charter 21:35:34 https://github.com/w3c/dxwg/issues/1502 21:36:07 https://www.w3.org/2020/02/dx-wg-charter.html#coordination 21:36:43 RiccardoAlbertoni: there is a newer version of the charter 21:36:52 https://www.w3.org/2022/06/dx-wg-charter.html 21:37:00 https://www.w3.org/2022/06/dx-wg-charter.html#coordination 21:37:45 The Working Group is advised to seek a review at least 3 months before first entering CR and is encouraged to proactively notify the horizontal review groups when major changes occur in a specification following a review. 21:39:07 q+ 21:39:08 https://docs.google.com/document/d/1EPQKTLXHlJUTDWqGrK3tRbfLC3mKHjEu_E26veTcC-U/edit?usp=sharing 21:40:00 pchampin: we just need to understand that some interaction has taken place 21:40:38 q+ 21:40:48 ... and also, this is 'advisory'. 21:41:01 ack AndreaPerego 21:41:34 ack alejandra 21:41:37 AndreaPerego: we have some users who have already made preparations to move to v3 21:42:46 alejandra: if it is only awareness then we have been promoting this 21:43:03 s/ to move to v3/ to move to v3 (e.g., DCAT-AP). 21:43:09 RRSAgent, draft minutes 21:43:10 I have made the request to generate https://www.w3.org/2023/11/07-dxwg-minutes.html AndreaPerego 21:43:46 RiccardoAlbertoni: we just need to write this down 21:43:46 alejandra: we need to advertise widely. what is the 'official' requirement 21:45:17 pchampin: The lists in the charter and in the google doc aren't the same? They seem close 21:46:42 +q 21:46:58 pchampin: Thanks RiccardoAlbertoni - that is exactly what I need. I think that we have something for all the groups. Can I include a pointer in the transition request? If so then if there are additions following this meeting they will be available to people 21:47:12 ack RiccardoAlbertoni 21:47:39 RiccardoAlbertoni: my impression is that the community group isn't that active 21:49:00 pchampin: obviously there are registered participants who are not very active, and if community groups aren't active then we cannot expect feedback. 21:51:28 ... Given that there is no objection to using the google doc as part of the justification of wide review, and that we have no github issues that might block moving to CR, then I will take the snapshot from 3 weeks ago and will proceed with that. The SpecRef bug can be handled later. I will proceed with the transition request on this basis 21:51:28 q? 21:51:34 +q 21:51:38 ack RiccardoAlbertoni 21:52:23 q+ 21:52:31 RiccardoAlbertoni: in January we are expected to prove implementation. Do we need to provide a proper document for this? 21:53:12 pchampin: I don't know how formalised this is - my understanding is that implementation evidence isn't a tick-box situation. I will check 21:54:16 rrsagent, create minutes v2 21:54:18 I have made the request to generate https://www.w3.org/2023/11/07-dxwg-minutes.html pwinstanley 21:54:51 pchampin: features at risk can be removed from the CR before going to PR 21:55:04 q? 21:55:08 ack roba 21:56:07 roba: during December I will be working on the geoDCAT profile and will be needing help with testing 21:56:15 q? 21:56:48 pchampin: I will send the CR in the morning and keep everyone posted 21:56:57 rrsagent, create minutes v2 21:56:59 I have made the request to generate https://www.w3.org/2023/11/07-dxwg-minutes.html DaveBrowning 21:57:24 pchampin: bye, and meet up after the CR period 21:57:31 RRSAgent, draft minutes 21:57:32 I have made the request to generate https://www.w3.org/2023/11/07-dxwg-minutes.html AndreaPerego 21:58:28 present-