20:40:36 RRSAgent has joined #dxwg 20:40:36 logging to https://www.w3.org/2020/02/25-dxwg-irc 20:40:43 rrsagent, make logs public 20:40:54 chair: PWinstanley 20:41:25 meeting: DXWG Plenary 20:41:28 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2020.02.25 20:42:17 regrets+ SimonCox, Makx, RiccardoAlbertoni, DaveBrowning, RobA 20:42:29 rrsagent, create minutes v2 20:42:29 I have made the request to generate https://www.w3.org/2020/02/25-dxwg-minutes.html PWinstanley 20:58:35 antoine has joined #dxwg 21:02:02 ncar has joined #dxwg 21:02:12 present+ 21:02:19 present+ 21:02:57 present+ 21:03:22 Scribenick: antoine 21:03:32 rrsagent, please draft minutes v2 21:03:32 I have made the request to generate https://www.w3.org/2020/02/25-dxwg-minutes.html antoine 21:05:51 Topic: admin 21:06:24 proposal: accept minutes of last call https://www.w3.org/2020/02/18-dxwg-minutes 21:06:34 annette_g: they were mixed up 21:06:52 philippe: I've cleaned it 21:07:24 PWinstanley: there are some warning 21:07:39 ... in the diagnostics 21:07:48 philippe: I'll fix that as well. 21:08:04 AndreaPerego has joined #dxwg 21:08:23 +1 21:08:23 +1 21:08:23 +1 21:08:26 +1 21:08:30 oops no 0 I was not here 21:08:45 present+ 21:08:46 but it seems there's been some attention to the minutes :-) 21:09:05 resolved: accept minutes https://www.w3.org/2020/02/18-dxwg-minutes 21:09:16 Topic: DCAT V3 21:09:51 PWinstanley: we agreed to split the repos 21:10:00 ... open two new ones for Conneg and PROV 21:10:19 plh has joined #dxwg 21:10:25 and do a bulk closure of Conneg and PROV in the current repo 21:10:37 dxwg, dx-prof-conneg 21:11:02 philippe: not done yet. You want dxwg, dxwg-conneg and dxwg-prof ? 21:11:05 dxwg, dx-prof-conneg, dx-prof 21:11:18 yes please! 21:11:36 alejandra has joined #dxwg 21:11:43 did we make a call about UCR & Guidance? 21:12:03 q+ 21:12:22 https://github.com/w3c/dx-prof-conneg 21:12:30 yes 21:12:48 PWinstanley: the current one would be for DCAT 21:12:49 q+ 21:13:19 dx-connegp 21:13:21 dx-prof 21:13:34 dx-prof-conneg is fine 21:13:47 nooo! 21:14:07 q? 21:14:08 copnnegp is my personal preferred term 21:14:11 ack ncar 21:14:12 make that connegp 21:14:39 ncar: did we discuss UCR and Guidance 21:14:45 PWinstanley: no we didn't have time 21:14:47 ack antoine 21:15:25 preferred dx-prof & dx-connegp 21:15:57 antoine: I am arguing against dx-prof-conneg 21:16:15 https://github.com/w3c/dx-connegp 21:16:16 ncar: would it be possible to change the short name of prof-conneg? 21:16:25 philippe: open an issue in the new repo! 21:16:35 ... and assign the issue to me. 21:17:33 PWinstanley: do you see issues for expedite the new github repo arrangement? 21:17:54 philippe: connegp is created and I gave you access. 21:18:01 ... do you want me to transfer issues? 21:18:11 PWinstanley: pretty certain that yes 21:18:42 ncar: for connegp and prof, yes, and we'll tidy them up 21:19:05 q+ 21:19:11 ack antoine 21:19:21 https://github.com/w3c/dxwg/issues/1211 21:20:03 q+ 21:20:06 antoine: question about shared issues, esp 1211. It was originally about DCAT but spans two topics 21:20:13 ack ncar 21:20:42 ncar: we'll have to do what we do with other work. Maybe create copy issues. 21:20:44 I think we just do as in other projects and make reference across repos. Perhaps create peer issues if necessary 21:20:47 https://github.com/w3c/dx-prof now exists 21:20:47 q+ 21:20:48 present+ 21:20:55 ack antoine 21:21:17 ncar: we'll lose neatness but I think it's fine. 21:21:21 antoine: I can live with that, but if done automatically, which repo does it end up in? 21:21:32 ncar: in this case leave in DCAT 21:21:35 ncar: in this one we can leave it with DCAT 21:21:38 q+ 21:21:45 question: should the prefix be dxwg rather than dx? 21:21:46 ack antoine 21:22:02 due to the existing repo: https://github.com/w3c/dxwg 21:22:05 antoine: good - so can we take a note of the shared issues? 21:22:38 ... I'm concerned that we lose info if this is done automatically 21:23:05 PWinstanley: this is something we can identify by queries 21:23:37 ncar: the tags are free-floating so they would retain the original labels 21:24:58 alejandra: so we would create mirror issues? My concern is that we would still have to go back to original issues. 21:25:18 PWinstanley: there may not be many, but there could be the important ones 21:25:30 https://github.com/w3c/dxwg/issues/1216#issuecomment-587788504 21:26:03 alejandra: also shouldn't we keep the same prefix, i.e. dxwg? 21:26:09 ... for consistency 21:26:34 q+ 21:26:38 PWinstanley: yes we probably should want to do this 21:26:51 alejandra: especially if DCAT remains in the original repo 21:27:02 ack annette_g 21:27:10 annette_g: wouldn't it create inconsistencies with the W3C websites? 21:27:24 philippe: we track repos based on their configuration not their name 21:27:45 ... what we recommend is that the name of the repo is the one of the short name of the spec 21:27:57 about the overlap of issues... there is now only 1 issue that shares the labels dcat and profiles-vocabulary: https://github.com/w3c/dxwg/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Aprofiles-vocabulary+label%3Adcat 21:27:57 ... if one changes then the other should change 21:28:16 q+ 21:28:41 PWinstanley: maybe we should do this once we start working with these new repos 21:28:46 ack antoine 21:28:52 ... and the UCR 21:29:30 +q 21:29:41 and no issues between dcat and profiles-negotiation 21:29:47 -q 21:29:47 antoine: I wanted to point to the statistics on the shared issues that Riccardo / Karen were pointing out were not overlapping, but there is 1211 21:30:07 +q 21:31:26 ack alejandra 21:32:02 alejandra: I agree that it falls into profile guidance but are we sure we don't want to add something in DCAT? 21:32:13 ... the original post was about the description in DCAT 21:32:48 Create a peer Issue Alejandra? 21:32:53 ... there could be an issue created for the original spec 21:33:07 philippe: we can create a peer issue if needed 21:33:18 https://github.com/w3c/dxwg/issues/389 21:33:34 sure - I will comment on the issue later - I think it has to stay in DCAT and we can create a peer issue in the guidance doc 21:33:36 nice! 21:33:52 PWinstanley: alejandra is it something that you want to track? 21:34:08 q+ 21:34:53 action: alejandra to keep an eye on #1211 as a shared issue 21:34:53 Created ACTION-398 - Keep an eye on #1211 as a shared issue [on Alejandra Gonzalez Beltran - due 2020-03-03]. 21:34:59 q- 21:35:01 ack antoine 21:35:58 PWinstanley: next topic is future work and UCR 21:36:04 RRSAgent, draft minutes v2 21:36:04 I have made the request to generate https://www.w3.org/2020/02/25-dxwg-minutes.html AndreaPerego 21:36:24 q+ 21:36:29 ack antoine 21:36:49 antoine: what needs to be done? 21:37:32 PWinstanley: at the moment we have a list of future work and things in UCR that haven't be dealt with 21:37:43 ... we need to check they are in line, and in scope 21:37:54 q+ 21:38:01 ... we need to do some triage 21:38:03 ack antoine 21:38:25 +q 21:38:42 antoine: I was concerned that we would be re-doing UCR 21:38:44 antoine: I thought this would be about doing a new UCR 21:38:45 PWinstanley: NO 21:38:48 ack alejandra 21:39:07 alejandra: we don't even need to look at the UCR again, I believe 21:39:19 q+ 21:39:39 ack annette_g 21:39:49 ... in principle we've handled them, either solved them or they are open as github issues 21:40:03 ... so we shouldn't have to look again at the original UCR 21:40:15 also note that we do have new use cases from those written in the UCR, but they are in github issues 21:40:20 annette_g: do we have new people coming as per the re-chatering? 21:40:49 PWinstanley: there should be people around, whom we could ask 21:41:10 ... do you see anything appropriate for inclusion? 21:41:17 s/chatering/chartering/ 21:41:26 annette_g: I think I might have seen something, but it was late in the process 21:41:42 ... it was about the need to streamline things 21:41:52 ... I would need to write it in a coherent way 21:42:22 ... We should consider how people put things into practice 21:42:40 ... For example what we're asking in Conneg can be burdensome 21:42:52 PW: user experience - user research? 21:42:56 annette_g: yes 21:43:06 PW: there are groups to which we could throw things 21:43:27 ... a number of them from W3C members 21:43:40 ... We tend to look at accessibility but there are other aspects of usability 21:44:14 ... Anything else, e.g. on FAIR? 21:44:20 q+ 21:44:28 ack antoine 21:45:23 antoine: alejandra said that there are some use cases that are new (not in the UCR, but are in github issues). Do these need to be put into the UCR? 21:45:51 PWinstanley: I'm going to ask philippe where we're going in terms of agile method 21:46:01 ... the UCR was waterfall-y. 21:46:26 ... How should we think of our compentency questions? 21:46:39 ... the UCR is not complete 21:46:52 ... wrt competency questions 21:47:07 s/compentency/competency 21:47:17 philippe: UCR is not a REC, it's a NOTE 21:48:33 PWinstanley: at this stage do we need to update the UCR doc with things in the github issues? 21:48:46 philippe: no it's not needed 21:49:10 ... I would recommend that before moving to CR that you mention where the requirements are 21:49:29 ... because you'll need to prove you've met there. 21:49:32 Good! To be more agile is good to keep the use cases in github only 21:49:51 PWinstanley: ok so as long as we're explicit on where the requirements came from and that we've handled them then we're good to go. 21:50:26 https://github.com/w3c/dxwg/issues?page=1&q=is%3Aissue+is%3Aopen+label%3Aprofiles-vocabulary 21:50:37 philippe: I've moved all the open issues for the two deliverable except these which had dual labels 21:50:52 +1! 21:51:14 PWinstanley: alejandra and ncar can look at them and mirror them if needed 21:51:18 +1 21:51:24 +1 to moving them 21:51:27 philippe: do you want me to migrate the closed issues? 21:51:43 =1 21:51:44 +1 21:51:45 ncar: I don't think it's a good idea but I won't object 21:52:08 philippe: ok I'll do them one by one 21:52:09 q+ 21:52:28 ack antoine 21:53:08 antoine: asking plh - will the closed issues be moved with the same criteria as the live one - esp relating to issues spanning deliverables? 21:53:13 plh: yes 21:53:41 philippe: something else: for the moment I've cloned the repo, keeping the structure and milestones 21:54:01 ... for DCAT there could still be links to editor's drafts 21:54:21 ... I can update the REC to point to the right place but it needs some coordination. 21:54:27 Topic: Conneg 21:54:51 ncar: Rob are going to check the test suite in the next day or two 21:55:33 ... we don't think there will be a lot of change but will check 21:55:48 ... the main change will be adding a list of requirements 21:55:53 Topic: PROF 21:56:18 ncar: I've made a profile hierarchy-based validation tool 21:56:52 ... the tool is fed with a data graph and a profile hierarchy and hunts for the SHACL files available for the hierarchy. 21:57:07 ... it implements one of our use cases. 21:57:34 ... I've implemented this tool because we need to validate data for another project [???] 21:57:48 ... which will make conformance claims based on the outcome 21:58:53 PWinstanley: maybe you can check and move the drafts to the new repo 21:58:56 q+ 21:59:20 ncar: ok but how about the issues? 21:59:28 PWinstanley: they are moved 21:59:36 q- 21:59:56 ... it would be good to have visibility for the group, with links 22:00:25 action: ncar to mail the group with a proposal to move the prof and connegp drafts from the original repo to the new ones 22:00:25 Created ACTION-399 - Mail the group with a proposal to move the prof and connegp drafts from the original repo to the new ones [on Nicholas Car - due 2020-03-03]. 22:01:01 rrsagent, please draft minutes v2 22:01:01 I have made the request to generate https://www.w3.org/2020/02/25-dxwg-minutes.html antoine 22:01:02 thanks all, and bye! 22:01:15 Thanks, bye! 22:01:29 rrsagent, create minutes v2 22:01:29 I have made the request to generate https://www.w3.org/2020/02/25-dxwg-minutes.html PWinstanley 23:18:31 plh has joined #dxwg