20:49:42 <RRSAgent> RRSAgent has joined #dxwgdcat
20:49:42 <RRSAgent> logging to https://www.w3.org/2019/03/27-dxwgdcat-irc
20:49:44 <trackbot> RRSAgent, make logs public
20:49:44 <Zakim> Zakim has joined #dxwgdcat
20:49:46 <trackbot> Meeting: Dataset Exchange Working Group Teleconference
20:49:46 <trackbot> Date: 27 March 2019
20:50:26 <DaveBrowning> meeting: DXWG DCAT subgroup teleconference 27 March 2019 21:00 UTC
20:51:11 <DaveBrowning> regrets: Alasdair Gray, Erik Mannens, Thomas D'Haenens, Lars Svensson
20:51:30 <DaveBrowning> rrsagent, draft minutes v2
20:51:30 <RRSAgent> I have made the request to generate https://www.w3.org/2019/03/27-dxwgdcat-minutes.html DaveBrowning
20:56:41 <PWinstanley> PWinstanley has joined #dxwgdcat
20:58:45 <AndreaPerego> AndreaPerego has joined #dxwgdcat
20:59:19 <AndreaPerego> present+
20:59:27 <PWinstanley> present+
20:59:48 <AndreaPerego> agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2019.03.27
20:59:56 <AndreaPerego> RRSAgent, draft minutes v2
20:59:56 <RRSAgent> I have made the request to generate https://www.w3.org/2019/03/27-dxwgdcat-minutes.html AndreaPerego
21:03:10 <riccardoAlbertoni> riccardoAlbertoni has joined #dxwgdcat
21:03:42 <SimonCox> SimonCox has joined #dxwgdcat
21:04:28 <Makx> Makx has joined #dxwgdcat
21:04:58 <alejandra> alejandra has joined #dxwgdcat
21:05:09 <alejandra> present+
21:05:15 <riccardoAlbertoni> present+
21:05:20 <Makx> present+
21:05:21 <DaveBrowning> present+
21:05:32 <AndreaPerego> RRSAgent, draft minutes v2
21:05:32 <RRSAgent> I have made the request to generate https://www.w3.org/2019/03/27-dxwgdcat-minutes.html AndreaPerego
21:06:22 <SimonCox> present+
21:06:34 <PWinstanley> present+
21:06:44 <riccardoAlbertoni> present+
21:07:09 <DaveBrowning> chair: DaveBrowning
21:07:19 <SimonCox> scribe: SimonCox
21:07:27 <SimonCox> scribenick: Si
21:07:37 <SimonCox> scribenick: SimonCox
21:07:50 <SimonCox> Topic: agenda
21:07:58 <SimonCox> https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2019.03.27
21:08:27 <SimonCox> +1
21:08:29 <AndreaPerego> +1
21:08:33 <alejandra> +1
21:08:36 <PWinstanley> +1
21:08:49 <riccardoAlbertoni> +1
21:08:55 <Makx> +1
21:09:02 <SimonCox> topic: approve minutes of last meeting
21:09:04 <SimonCox> https://www.w3.org/2019/03/20-dxwgdcat-minutes
21:09:08 <PWinstanley> +1
21:09:10 <AndreaPerego> +1
21:09:18 <Makx> +1
21:09:22 <SimonCox> +1
21:09:23 <riccardoAlbertoni> +1
21:09:24 <DaveBrowning> +1
21:09:25 <alejandra> +0 (was absent)
21:09:36 <SimonCox> resolved: approve minutes of last meeting
21:09:41 <AndreaPerego> RRSAgent, draft minutes v2
21:09:41 <RRSAgent> I have made the request to generate https://www.w3.org/2019/03/27-dxwgdcat-minutes.html AndreaPerego
21:09:53 <SimonCox> topic: timing of future meetings
21:10:17 <PWinstanley> 20:00 UTC suits me
21:10:23 <AndreaPerego> +1 to shifting 1h
21:10:29 <alejandra> +1 to 20:00 UTC
21:10:45 <SimonCox> invitation sent for 20:00 UTC on Wednesdays starting 2019-04-03
21:11:05 <Makx> +1
21:11:06 <DaveBrowning> +1
21:11:10 <SimonCox> +1
21:11:10 <AndreaPerego> +1
21:11:12 <riccardoAlbertoni> +1
21:11:28 <SimonCox> topic: General release points
21:11:33 <AndreaPerego> RRSAgent, draft minutes v2
21:11:33 <RRSAgent> I have made the request to generate https://www.w3.org/2019/03/27-dxwgdcat-minutes.html AndreaPerego
21:12:01 <SimonCox> verify that we agree with announced release points
21:12:38 <PWinstanley> there is a 1.1 of DCAT-AP and there might be confusion with that
21:12:41 <SimonCox> DaveBrowning: what is the release number? charter says 1.1, else 2.0?
21:12:44 <SimonCox> q+
21:12:51 <DaveBrowning> ack SimonCox
21:13:06 <alejandra> https://www.w3.org/TR/vocab-dcat-2/
21:13:10 <alejandra> +q
21:13:11 <PWinstanley> SimonCox: the version number is only what is in the header of the recommendation - it is just a designation
21:13:19 <alejandra> the URL already says 2
21:13:40 <PWinstanley> ... so my sense is that we shouldn't be shy.  it is not just a few corrections.  it is a significant change, so why not go to 2
21:13:46 <PWinstanley> +1 to SimonCox
21:13:59 <DaveBrowning> ack alejandra
21:14:11 <riccardoAlbertoni> +1  to SimonCox and alejandra
21:14:14 <Makx> +1
21:14:18 <AndreaPerego> q+
21:14:22 <SimonCox> alejandra: match the version number with the URI
21:14:39 <SimonCox> DaveBrowning: we need to communicate this to Phillipe
21:14:43 <DaveBrowning> q?
21:14:47 <alejandra> there are significant changes so it merits version 2.0
21:15:19 <SimonCox> PWinstanley: should not confuse with minor tweaking e.g. DCAT-AP 1.1
21:15:21 <DaveBrowning> ack AndreaPerego
21:16:23 <SimonCox> AndreaPerego: 1.1 would not reflect the substantial changes; the thing that needs to be clarified to readers is that even though it is v2 it is backward compatible with v1
21:16:31 <SimonCox> ... in the text
21:16:58 <SimonCox> ... but what about the evergreen-standards ideas? 1.1 makes it easier to move to 1.2?
21:16:59 <SimonCox> q+
21:17:14 <SimonCox> q+ to point out that v3 would be the next version!
21:17:38 <alejandra> +q
21:18:24 <SimonCox> PWinstanley: evergreen standards is high priority for W3C; expected to deal with the backlog soon
21:18:30 <Makx> q+
21:18:46 <DaveBrowning> ack SimonCox
21:18:46 <Zakim> SimonCox, you wanted to point out that v3 would be the next version!
21:18:48 <SimonCox> ... would that be another major version shift?
21:18:51 <DaveBrowning> q?
21:18:56 <DaveBrowning> q+
21:19:02 <PWinstanley> SimonCox: I think all this numbering gets tangled up
21:19:17 <PWinstanley> ... practices are different in different products
21:19:30 <DaveBrowning> q?
21:19:32 <PWinstanley> ... getting up to version 30 isn't as scary as it once was
21:19:47 <DaveBrowning> ack alejandra
21:19:49 <PWinstanley> ... so just restricting to cardinal numbers is ok
21:20:03 <SimonCox> we shouldn't be scared about incrementing version numbers
21:20:52 <DaveBrowning> ack Makx
21:20:52 <SimonCox> alejandra: designation of future version is a discussion for the future
21:20:58 <DaveBrowning> q-
21:21:14 <SimonCox> Makx: how about DCAT 2019?
21:22:07 <SimonCox> ... Firefox is now version 65 now, and no-one worries much, lets just use integers
21:22:13 <alejandra> to me the decision is taken considering if the changes are major or not
21:22:13 <SimonCox> q?
21:22:19 <riccardoAlbertoni> +q
21:22:29 <PWinstanley> let's make a resolution
21:22:34 <SimonCox> DaveBrowning: we agree that this is version 2, worry about the future later
21:22:43 <DaveBrowning> ack riccardoAlbertoni
21:23:11 <DaveBrowning> proposed: This version of the rec will be version 2.0,  subsequent versioning tbd
21:23:18 <SimonCox> q+
21:23:22 <Makx> q+
21:23:32 <Makx> +1 to drop .0
21:23:35 <Makx> q-
21:23:39 <DaveBrowning> proposed: This version of the rec will be version 2,  subsequent versioning tbd
21:23:44 <PWinstanley> +1
21:23:45 <alejandra> +1
21:23:46 <riccardoAlbertoni> +1
21:23:47 <Makx> +1
21:23:47 <SimonCox> amendment = drop the .0
21:23:48 <AndreaPerego> 0
21:23:48 <DaveBrowning> +1
21:23:50 <SimonCox> +1
21:24:02 <SimonCox> resolved: This version of the rec will be version 2,  subsequent versioning tbd
21:24:32 <AndreaPerego> RRSAgent, draft minutes v2
21:24:32 <RRSAgent> I have made the request to generate https://www.w3.org/2019/03/27-dxwgdcat-minutes.html AndreaPerego
21:24:42 <SimonCox> Should all notes persist in CR?
21:25:19 <AndreaPerego> s/Should all notes persist in CR?/DaveBrowning: Should all notes persist in CR?/
21:25:23 <SimonCox> DaveBrowning: ednotes will be dropped from the CR; should all others remain?
21:25:25 <alejandra> +q
21:25:28 <AndreaPerego> q+
21:25:34 <DaveBrowning> ack SimonCox
21:25:40 <DaveBrowning> ack alejandra
21:25:51 <SimonCox> ... in particular do we leave the NOTES that point out new features in the text?
21:26:10 <SimonCox> alejandra: leave them in; important for people upgrading
21:26:26 <DaveBrowning> ack AndreaPerego
21:26:35 <Makx> +1 to alejandra
21:26:37 <PWinstanley> +1 to alejandra - we can use styling to put them into a reduced size font or a box or similar
21:27:21 <SimonCox> AndreaPerego: +1 to alejandra; need sanity check if some notes are really editor's notes
21:27:47 <SimonCox> +1 to Peter - style new-feature notes different?
21:28:07 <AndreaPerego> RRSAgent, draft minutes v2
21:28:07 <RRSAgent> I have made the request to generate https://www.w3.org/2019/03/27-dxwgdcat-minutes.html AndreaPerego
21:28:51 <AndreaPerego> q+
21:28:53 <SimonCox> DaveBrowning: Code samples? where should they persist? Frozen GitHub branch used for FPWD. Same mechanism for CR?
21:28:56 <SimonCox> +1
21:29:00 <DaveBrowning> ack AndreaPerego
21:30:13 <SimonCox> AndreaPerego: is there an issue related to generation of static HTML in pub process?
21:30:17 <DaveBrowning> https://www.w3.org/TR/vocab-dcat-2/#data-service-examples
21:30:54 <SimonCox> DaveBrowning: this example shows link to 'DXWG code repository' which is live link to GitHub branch
21:31:51 <SimonCox> ... was not sure about it, but seemed to work well, and is consistent with mention of GitHub issue
21:32:17 <SimonCox> AndreaPerego: is there a W3C requirement around this?
21:32:44 <SimonCox> DaveBrowning: lets us assert this is how we want to do it, and wait for W3C to complain.
21:33:21 <AndreaPerego> q+
21:33:38 <DaveBrowning> ack AndreaPerego
21:35:31 <SimonCox> evergreen delivery would be assisted by retaining the same repository
21:35:40 <AndreaPerego> RRSAgent, draft minutes v2
21:35:40 <RRSAgent> I have made the request to generate https://www.w3.org/2019/03/27-dxwgdcat-minutes.html AndreaPerego
21:35:59 <SimonCox> DaveBrowning: alignment sections?
21:36:13 <SimonCox> ... 16, ApA, ApB
21:36:43 <DaveBrowning> https://w3c.github.io/dxwg/dcat/#other-w3c-recommendations
21:36:57 <SimonCox> q+
21:37:04 <riccardoAlbertoni> +q
21:37:13 <riccardoAlbertoni> q-
21:37:21 <riccardoAlbertoni> +1 to simonCox
21:37:39 <alejandra> +1, we did agree on dropping Annex B
21:37:49 <Makx> +1 to drop annex B
21:37:50 <PWinstanley> SimonCox: I think we agreed in a previous call that we would be dropping the alignment with other vocabularies (annexes A and B).  there are partial alignments in other places
21:38:07 <riccardoAlbertoni> +1 to delete annex B and have the issues in the backlog
21:38:14 <PWinstanley> ... I think Annex B is straightforward.  There certainly is a potential for joining 16 with A
21:38:15 <AndreaPerego> +1 to drop Annex B
21:39:07 <PWinstanley> ... I did some work, not very substantial. There was discussion about entailment and qualified relations
21:39:37 <PWinstanley> DaveBrowning: it is there for people with an interest
21:40:16 <PWinstanley> SimonCox: it is not said explicitly - but there is a consistent story, if not a good one.  We can then drop A.2 if we add a little narrative here
21:40:19 <AndreaPerego> +1 to drop Annex A.2
21:40:36 <Makx> +1 to drop annex A2
21:40:59 <SimonCox> suggest adding a mention in 9.1 noting that use of prov:qualifiedAttribution entails that dcat:Dataset is a subclass of prov:Entity (the afficionados woudl have spotted that already)
21:41:09 <SimonCox> ... otherwise we can drop A.2
21:41:56 <Makx> +1 to drop section 16
21:42:45 <AndreaPerego> +1 to drop Section 16
21:42:49 <alejandra> +1 to raising an issue
21:42:53 <AndreaPerego> q+
21:42:55 <alejandra> so that we can have discussion there
21:43:02 <DaveBrowning> ack SimonCox
21:43:06 <DaveBrowning> ack AndreaPerego
21:43:10 <SimonCox> DaveBrowning: section 16 needs inspection, and discussion in an issue
21:43:39 <SimonCox> AndreaPerego: was from an external contributor, we don't have time to check it, so maybe drop it
21:44:03 <SimonCox> DaveBrowning: formal issue will allow us to engage with it and resolve it transparently
21:44:42 <SimonCox> ... specific problem is that it proposes new RDF properties in dcat: namespace
21:44:59 <DaveBrowning> proposed: raise issue to determine status of sect 16
21:45:02 <SimonCox> ... e.g. dcat:records, dcat:datasets, dcat:services
21:45:06 <AndreaPerego> +1
21:45:07 <SimonCox> +1
21:45:08 <DaveBrowning> +1
21:45:08 <PWinstanley> +1
21:45:16 <riccardoAlbertoni> +1
21:45:20 <Makx> +1
21:45:23 <SimonCox> resolved: raise issue to determine status of sect 16
21:45:33 <AndreaPerego> RRSAgent, draft minutes v2
21:45:33 <RRSAgent> I have made the request to generate https://www.w3.org/2019/03/27-dxwgdcat-minutes.html AndreaPerego
21:45:50 <SimonCox> also raise issue to remove annex B
21:46:07 <DaveBrowning> https://github.com/w3c/dxwg/issues/838
21:46:15 <SimonCox> DaveBrowning: props to riccardoAlbertoni for sterling work on backlog
21:46:59 <riccardoAlbertoni> +q
21:47:06 <DaveBrowning> ack riccardoAlbertoni
21:48:01 <SimonCox> riccardoAlbertoni: we are accumulating a backlog, so need to make this transparent and orderly by putting explicit link to them
21:48:10 <riccardoAlbertoni> https://github.com/w3c/dxwg/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Adcat+no%3Amilestone%09
21:48:51 <SimonCox> ... but many issues label:dcat are not in the backlog, or should we close a lot with 'won't fix'
21:49:32 <alejandra> +1
21:49:33 <SimonCox> DaveBrowning: need a clear story about which are in backlog, and which are not
21:49:38 <alejandra> +q
21:49:47 <DaveBrowning> ack alejandra
21:49:51 <AndreaPerego> q+
21:50:30 <SimonCox> alejandra: 'backlog' milestone is a hack ...
21:51:02 <SimonCox> ... from when we stopped such frequent releases, when an existing milestone was renamed
21:51:04 <DaveBrowning> q?
21:51:10 <DaveBrowning> ack AndreaPerego
21:51:23 <SimonCox> ... it is actually easy - any unresolved issue is automatically in the backlog!
21:51:25 <PWinstanley> +1 to prioritising for next version (we need to log our thinking somewhere)
21:51:26 <riccardoAlbertoni> +q
21:51:43 <DaveBrowning> q?
21:51:47 <SimonCox> AndreaPerego: but still need to prioritize the next ones that we will deal with
21:51:52 <alejandra> +q
21:51:57 <DaveBrowning> q?
21:52:22 <SimonCox> ... will help people understand how the WG sees next priorities
21:52:24 <DaveBrowning> ack riccardoAlbertoni
21:53:32 <SimonCox> riccardoAlbertoni: backlog milestone is useful - it allows us to show where discussion has been happening
21:53:37 <DaveBrowning> q?
21:53:44 <DaveBrowning> acl alejandra
21:53:49 <DaveBrowning> ack alejandra
21:54:31 <SimonCox> alejandra: to AndreaPerego there is a prioritization, 3rd and 4th WD milestones; 4th WD was then renamed 'backlog'
21:54:53 <SimonCox> ... but what we are relaly talking about is a 'roadmap' which would be useful to get external feedback
21:55:02 <SimonCox> ... now we need to focus on issues at hand!
21:55:02 <DaveBrowning> rrsagent, draft minutes v2
21:55:02 <RRSAgent> I have made the request to generate https://www.w3.org/2019/03/27-dxwgdcat-minutes.html DaveBrowning
21:55:06 <AndreaPerego> q+
21:55:15 <DaveBrowning> ack AndreaPerego
21:55:16 <SimonCox> s/relaly/really/
21:55:38 <SimonCox> AndreaPerego: what is purpose of backlog? to inform readers about what will be addressed in the next release
21:56:00 <SimonCox> ... there are 42 issues not in the backlog milestone - too many to give direction to readers
21:57:31 <alejandra> I would change the name 'backlog'
21:57:44 <alejandra> maybe for 'roadmap'
21:58:03 <SimonCox> or 'priority'
21:58:22 <PWinstanley> 'next steps'
21:58:26 <alejandra> yes, 'priority' is good
21:58:27 <riccardoAlbertoni> +1 to change the name of backlog
21:58:28 <SimonCox> (a roadmap is a more discursive plan?)
21:59:09 <SimonCox> resolved: keep a milestone for 'priority' issues
21:59:14 <PWinstanley> I think it is important not to lose discussions
21:59:24 <PWinstanley> what we avoided is important to know
22:01:03 <riccardoAlbertoni> +1 to merge I agree with SimonCox
22:01:11 <AndreaPerego> q+
22:01:18 <DaveBrowning> ack AndreaPerego
22:03:29 <AndreaPerego> RRSAgent, draft minutes v2
22:03:29 <RRSAgent> I have made the request to generate https://www.w3.org/2019/03/27-dxwgdcat-minutes.html AndreaPerego
22:03:37 <riccardoAlbertoni> thanks  a lot , bye
22:03:38 <Makx> bye now
22:03:39 <SimonCox> it is important to do the merge so that classes that we know will go away no longer are visible in the ED
22:03:44 <AndreaPerego> RRSAgent, draft minutes v2
22:03:44 <RRSAgent> I have made the request to generate https://www.w3.org/2019/03/27-dxwgdcat-minutes.html AndreaPerego