19:54:10 RRSAgent has joined #dxwgdcat 19:54:10 logging to https://www.w3.org/2019/07/24-dxwgdcat-irc 19:54:12 RRSAgent, make logs public 19:54:12 Zakim has joined #dxwgdcat 19:54:14 Meeting: Dataset Exchange Working Group Teleconference 19:54:15 Date: 24 July 2019 19:54:41 Meeting: DXWG DCAT subgroup teleconference 24 July 2019 20:00 UTC 19:54:46 PWinstanley has joined #dxwgdcat 19:55:01 rrsagent, draft minutes v2 19:55:01 I have made the request to generate https://www.w3.org/2019/07/24-dxwgdcat-minutes.html DaveBrowning 19:55:17 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2019.07.24 19:55:20 present+ 19:55:43 chair: DaveBrowning 19:55:56 rrsagent, draft minutes v2 19:55:56 I have made the request to generate https://www.w3.org/2019/07/24-dxwgdcat-minutes.html DaveBrowning 19:56:33 AndreaPerego has joined #dxwgdcat 20:03:26 SimonCox has joined #dxwgdcat 20:03:46 present+ 20:05:26 riccardoAlbertoni has joined #dxwgdcat 20:05:57 present+ 20:06:40 RRSAgent, draft minutes v2 20:06:40 I have made the request to generate https://www.w3.org/2019/07/24-dxwgdcat-minutes.html AndreaPerego 20:09:34 present+ 20:10:03 agenda - https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2019.07.24 20:10:11 Makx has joined #dxwgdcat 20:10:18 scribenick: PWinstanley 20:10:27 Topic: Admin 20:10:31 s/agenda -/agenda:/ 20:10:43 proposed: accept minutes of last meeting 20:11:04 +1 20:11:12 Present+ Makx 20:11:13 +1 20:11:18 +1 20:11:24 +1 20:11:55 resolved: accept minutes of last meeting 20:12:11 RRSAgent, draft minutes v2 20:12:11 I have made the request to generate https://www.w3.org/2019/07/24-dxwgdcat-minutes.html AndreaPerego 20:12:36 DaveBrowning: No issues from the DCAT plenary for us 20:13:17 PWinstanley: there is a poll, everyone needs to answer ASAP 20:13:33 Issues as listed in the googel doc https://docs.google.com/spreadsheets/d/1biOFTFAlF6wd7nhi5MsSusMokfdbwWII9OXSyfAw2iQ/edit?usp=sharing 20:13:36 Done poll 20:13:37 Topic: issues as in Google Doc 20:13:58 Poll on DCAT2: https://lists.w3.org/Archives/Public/public-dxwg-wg/2019Jul/0495.html 20:14:36 DaveBrowning: There has been tidying up - the doc has all closed issues at the top, then future work , issues due for closing (lots) which I tend to close later in the week 20:14:48 ... issues under ColA are effectively still open 20:15:51 ... I made a unilateral colour coding decision - yellow = unclear about future course; green = PR fairly advanced; no colour = unclear as to what we're doing 20:16:12 ... If colleagues are OK, I'd like to suggest that we start with #725 20:16:16 https://github.com/w3c/dxwg/issues/725 20:16:25 https://github.com/w3c/dxwg/pull/1010 20:16:33 +q 20:16:40 ack riccardoAlbertoni 20:16:41 ... I want to make sure that this is sorted before holiday season 20:18:11 riccardoAlbertoni: re: 725 - a suggestion in the PR that can include SimonCox views 20:18:37 SimonCox: where is the short report of what is needed to be done? 20:18:45 riccardoAlbertoni: it is in the PR. 20:19:00 ... Please can others pick this up whilst I'm away 20:19:45 ... #725 and the related PR are affecting all the skos:scopeNote and I'm trying to avoid conflict by merging issues 20:20:06 SimonCox: Thanks riccardoAlbertoni - sorry it got so complicated 20:20:18 ... I think you've implemented accurately. well done 20:20:28 riccardoAlbertoni: your suggestions were very helpful 20:20:49 ... the solution might be repetitive, but at least we won't lose anything 20:21:52 SimonCox: I'm looking and accepting mostly the comments you made 20:22:47 ... the significant contribution we are making is the translations 20:22:50 alejandra has joined #dxwgdcat 20:23:26 present+ 20:24:51 +q 20:24:57 DaveBrowning: issue #983 - is this superceded? 20:24:58 ack ric 20:25:32 riccardoAlbertoni: no, because deleting the terms at the beginning that were duplicated gets rid of the link to the definitions, but we need to harmonise 20:25:52 q? 20:26:01 ... the previous version used rdfs:comment and the new version uses skos:definition. 20:26:16 ... we decided to use both for backward compatibility 20:26:52 DaveBrowning: sounds sensible - we don't want a mess 20:27:18 ... SimonCox are you ok taking on #1010 20:27:22 ...? 20:27:50 DaveBrowning: We have discussed #725 and #983 20:28:12 https://github.com/w3c/dxwg/issues/958 20:28:31 ... about languages and direction marker 20:29:20 ... the remaing 2 with yellow markers are #958 (coming from the internationalisation review, about language tags and direction markers) I'd like to acknowledge the point about direction metadata and that we respond by saying that we know about it and will incorporate later 20:30:02 ... so I've marked in the milestone for future work 20:30:10 ... Are people happy with that? 20:30:13 +1 20:30:13 +1 20:30:27 +1 20:30:27 +1 20:30:46 +0 20:30:50 +1 20:30:56 resolved: to add the direction metadata to a future milestone 20:31:07 I think this feature is more fit to https://www.w3.org/TR/Content-in-RDF10/ 20:31:36 DaveBrowning: so I've updated the google doc and will incorporate AndreaPerego suggestion 20:32:15 ... The remaining yellow (#972) 20:32:16 Next issue https://github.com/w3c/dxwg/issues/972 20:32:53 ... I cannot parse the thread to get the sense. Has it reached consensus. 20:33:08 SimonCox: I say Steve last week and should have discussed it with him. 20:33:28 ... the issue was that I thought he had missed the key point 20:34:07 ... he is concerned about the range of foaf:document and then wondered if accessURL should be accessPage 20:34:23 ... it might need some finessing to deal with foaf:document 20:34:25 q+ 20:34:29 ... I will attend to it 20:34:38 ack AndreaPerego 20:35:06 AndreaPerego: just a note about foaf:document - the point is that this class is more generic than the name of the class itself 20:35:12 ... it is very generic 20:35:28 s/foaf:document/foaf:Document/ 20:35:49 rrsagent, draft minutes v2 20:35:49 I have made the request to generate https://www.w3.org/2019/07/24-dxwgdcat-minutes.html DaveBrowning 20:36:04 SimonCox: I think this is from DCAT 2014 20:36:50 AndreaPerego: the semantics is broader than just 'document' 20:37:14 SimonCox: you are correct AndreaPerego but we are addressing backward compatibility 20:37:41 AndreaPerego: I don't see big issues here 20:38:21 ... the problem raised by Steve ended up in also in the wording of props such as accessURL etc 20:38:49 ... I don't know if it can be sorted by modifying the wording of the definition 20:39:33 ... in DCAT 2014 there was a relationship between landingPage and accessURL - a usage note indicating a soft relationship 20:40:03 DaveBrowning: So is this enough 20:40:19 SimonCox: I am adding a note to the issue capturing some of the discussion we have just had 20:41:03 AndreaPerego: from my side, when working around GeoDCAT-AP and DCAT-AP they were missing the broad notion of landingPage - they were thought to be more for usage with a service than with a dataset 20:41:31 ... in DCAT 2014 it was not possible to use landingPage because of a domain restriction 20:43:07 Stephen was referring to the user notes 20:43:17 so I imagine he will agree on tighten up the text 20:43:30 DaveBrowning: So we have covered the points I thought would be most significant or most simple to deal with, but there are still other open issues on the google doc 20:43:44 s/user notes/scope notes 20:43:58 ... #979 - I'm not sure what we want to do 20:44:15 ... DCAT 2014 didn't do anything, btw 20:44:54 q+ 20:44:56 ... A related topic is how we publish these things on the website. My assumption is that the dcat.ttl is a replacement for the one currently in place. Correct? 20:44:56 +q 20:44:59 SimonCox: Yes 20:45:07 DaveBrowning: Sure? 20:45:09 ack AndreaPerego 20:45:36 AndreaPerego: related topic - we had discussions about keeping the old version of dcat.ttl, but I don't know how to do this 20:45:50 ... it is about versioning 20:47:02 DaveBrowning: I thought it might work by having the ttl file at /ns/dcat replaced by the new one. we can also use the latitude afforeded by the namespace file to point to the old dcat.ttl and state that we are publishing a backwardly-compatible file 20:47:12 ... the old version will therefore be available 20:47:12 q? 20:47:33 AndreaPerego: W3C has a policy for latest and previous versions - perhaps we could use that 20:48:02 PWinstanley: Perhaps we could couch it in an HTML file and use the W3C 'latest' version 20:48:03 ack ric 20:48:05 q+ 20:48:15 riccardoAlbertoni: I was making the same point as AndreaPerego 20:48:31 ... we could add a prov statement 20:48:48 ack DaveBrowning 20:49:17 q+ to note there are some properties from DCTERMS and ADMS that can be used for linking versions of a vocabulary. 20:49:50 ack AndreaPerego 20:49:50 AndreaPerego, you wanted to note there are some properties from DCTERMS and ADMS that can be used for linking versions of a vocabulary. 20:49:57 DaveBrowning: can this be covered with phillipe? 20:50:09 PWinstanley: yes - I will prime him with this question 20:50:21 AndreaPerego: There is prior art with ADMS 20:50:29 ... we can use this approach 20:51:01 Last version https://www.w3.org/TR/vocab-adms/#adms-last 20:51:18 Next version version https://www.w3.org/TR/vocab-adms/#adms-next 20:51:29 Previous version version https://www.w3.org/TR/vocab-adms/#adms-prev 20:51:55 +1 to andrea 20:52:19 DaveBrowning: I think we need to be careful not to gold plate this. 20:52:33 +q 20:52:38 ack riccardoAlbertoni 20:53:23 riccardoAlbertoni: I don't think we can change the old spec, so the warning that is seen on the page should be enough 20:55:24 q+ 20:55:29 ack AndreaPerego 20:55:41 SimonCox: I will do the conversion to different formats when the time is right 20:55:58 AndreaPerego: I wonder if the server is supporting content negotiation 20:56:44 ... we need to clarify what is happening so that we don't add a fudge that then results in inappropriate returns 20:57:15 for DQV we had to explicitly ask for content negotiation 20:57:22 DaveBrowning: The conneg seems to support this, and there is the scope for issues with the version perhaps 20:57:56 DaveBrowning: I think we've concluded 20:58:00 s/version version/version/ 20:58:03 s/version version/version/ 20:58:10 RRSAgent, draft minutes v2 20:58:10 I have made the request to generate https://www.w3.org/2019/07/24-dxwgdcat-minutes.html AndreaPerego 20:59:10 Thanks, and bye! 20:59:14 Bye 20:59:15 bye! 20:59:33 RRSAgent, draft minutes v2 20:59:33 I have made the request to generate https://www.w3.org/2019/07/24-dxwgdcat-minutes.html AndreaPerego