20:53:09 RRSAgent has joined #dxwgdcat 20:53:09 logging to https://www.w3.org/2018/02/14-dxwgdcat-irc 20:53:27 Zakim has joined #dxwgdcat 20:53:36 chair SimonCox 20:53:40 present+ 20:56:19 PWinstanley has joined #dxwgdcat 20:56:31 present+ 20:57:33 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2018.02.14 20:57:47 arminhaller has joined #dxwgdcat 20:58:13 minutes of last meeting: https://www.w3.org/2018/02/07-dxwgdcat-minutes 20:58:51 chair: SimonCox 20:59:05 meeting: DXWG DCAT team 20:59:45 scribenick: arminhaller 21:00:11 audio PWinstanley ?? 21:02:04 Stijn_Goedertier_AIV has joined #dxwgdcat 21:02:39 DaveBrowning has joined #dxwgdcat 21:03:23 NicholasCar has joined #dxwgdcat 21:03:37 present+ 21:04:10 present+ 21:04:15 present + 21:04:27 present+ 21:04:31 Jaroslav_Pullmann has joined #dxwgdcat 21:05:13 topic: Confirm agenda 21:05:13 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2018.02.14 21:05:31 topic: Approve minutes from last meeting – https://www.w3.org/2018/02/07-dxwgdcat-minutes 21:06:34 +1 21:06:35 +1 21:06:36 0 - wasn't there 21:06:40 0 21:06:48 0 not there 21:06:49 +1 21:07:08 Resolved: Minutes approved 21:07:18 topic: Actions from last meeting 21:07:28 topic: - Review of Requirements in GitHub issue tracker - https://github.com/w3c/dxwg/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Adcat+label%3Arequirement 21:08:03 alejandra has joined #dxwgdcat 21:08:10 present+ 21:08:12 AndreaPerego has joined #dxwgdcat 21:08:19 https://github.com/w3c/dxwg/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3Adcat+is%3Aclosed+ 21:08:21 present+ AndreaPerego 21:08:54 https://github.com/w3c/dxwg/pulls?q=is%3Apr+is%3Aclosed 21:09:31 s/waives/waves/ 21:09:52 q+ 21:09:54 SimonCox: points to closed issues and pull requests 21:10:01 q- 21:10:03 RiccardoAlbertoni has joined #dxwgdcat 21:10:14 topic: Global constraints - Relax global domain axioms on many dcat properties https://github.com/w3c/dxwg/issues/110 21:10:14 topic: Pull requests resulting from last meeting’s resolutions - https://github.com/w3c/dxwg/pulls 21:10:29 Makx has joined #dxwgdcat 21:10:46 presnt+ Makx 21:10:52 present+ Makx 21:11:09 present+ RiccardoAlbertoni 21:13:58 q? 21:14:10 q+ 21:14:13 q+ 21:14:14 q+ 21:14:17 ack Jaroslav_Pullmann 21:14:27 SimonCox: Comments on the proposal from Max on global constraints 21:15:02 Jaroslav_Pullmann: Will tooling support be hindered by removal of global axioms? 21:15:02 q+ 21:15:19 ack DaveBrowning 21:15:23 Jaroslav_Pullmann: Autocomplete in WebProtege may not work? 21:16:19 DaveBrowning: Agree with the approach. More explanatory text is needed. Having the domains there helps to give context, so if we remove them, we need to be more explicit in the descriptions. 21:16:23 ack alejandra 21:16:31 +1 on better annotations 21:16:42 +1 for annotations 21:17:44 +1 for usage of profiles instead 21:17:51 alejandra: Agree with removing global constraints. 2 Questions? Do we need to link to this to a requirement? Any of those restrictions could potentially be added for profiles. 21:18:07 q? 21:18:10 ack SimonCox 21:18:51 Adding a use case + req makes perfect sense to me. 21:19:14 SimonCox: Comment around Protege. Protege and the RDF editors are to be used at the design phase. When people create records, they most likely don't use Protege. 21:19:29 Agree with SimonCox 21:19:34 q+ 21:19:52 ... I would downplay the importance of editors for these users. 21:19:53 ack jar 21:19:55 q+ 21:19:58 ack jaro 21:20:03 ack Jaroslav_Pullmann 21:20:10 +1 to SimonCox 21:20:34 q? 21:20:49 Jaroslav_Pullmann: I am convinced now that users will not use editors to create instances. 21:21:15 ... profiles are auxiliary documents for documenting if we remove global constraints 21:21:16 My colleagues use DCAT for query to get data. http://data.sepa.org.uk/metadata/datacatalog.html - these sort of applications might involve reasoning 21:21:23 ack arminhaller 21:22:00 arminhaller: there are tools that use domain and range - form generation tools, but also use guarded restrictions, could use both of those; 21:22:22 ... if remove domain/ange, replace with guarded restrictions 21:22:43 q? 21:23:44 SimonCox: Let's address alejandra's question around the requirements 21:23:55 +1 to add use case + req as suggested by alejandra 21:24:16 plus we need an analysis of the impact this change would have: in terms of tooling and reasoning 21:24:17 +1 to AndreaPerego 21:24:57 +1 to AndreaPerego, adding a use case with the issue on dcat:contactPoint 21:25:22 alejandra: Removing it from the main vocabulary, but add it as a profile, for example. 21:26:20 q+ 21:26:25 q+ 21:26:26 ack arminhaller 21:26:57 +q 21:27:05 q+ 21:27:11 ack AndreaPerego 21:27:13 q- 21:27:30 In the case of contactPoint, Andrea did present a specific use case: https://github.com/w3c/dxwg/issues/95 21:27:50 Makx proposes retain domain restriction on For dcat:Catalog: dcat:dataset, dcat:record For dcat:Dataset: dcat:distribution For dcat:Distribution: dcat:accessURL, dcat:downloadURL 21:28:06 see https://github.com/w3c/dxwg/issues/110#issuecomment-365526268 21:28:12 ArminHaller: Maybe replace all global constraints and replace it with local restrictions that capture the intent of the original authors of DCAT and then move forward from there. 21:29:05 +1 to reviewing one by one 21:29:06 AndreaPerego: Look at the use cases and see which properties we need to remove global constraints. 21:30:04 ... tools that use domain and range restrictions use it in hard-coded way. They may not work any longer. 21:30:29 +1 to consider the dropping following a case by case approach as andrea is suggesting.. 21:30:36 q? 21:30:37 ... it is worth asking people who use tools if the removal would impact their implementation. 21:30:42 ack SimonCox 21:30:45 ack SimonCox 21:31:39 SimonCox: back off from having a resolution today on that issue. There needs to be a use case contributed (although that is a modelling issue). 21:31:51 we have some meta-use cases within the UCR document, so a new UC would be fine 21:32:08 ... we have a need to give people the ability to respond to a potential removal of domain/range restrictions 21:32:23 ... create an issue per property and have a discussion on a case by case basis 21:32:37 +1 21:32:42 +1 21:32:45 +1 21:32:46 q+ 21:32:54 +1 21:33:03 q? 21:33:08 ack Jaroslav_Pullmann 21:33:36 Jaroslav_Pullmann: the process you suggested makes sense. We have examples of meta modelling use cases already. 21:33:48 ... provide a motivation out of the arguments you have provided 21:33:56 q? 21:34:56 ... add guidance on the usage on properties where we remove global restrictions 21:35:50 ACTION: SimonCox to include issues for each property that uses global domain/range restrictions 21:35:50 Sorry, but no Tracker is associated with this channel. 21:36:08 Action: SimonCox and Jaroslav_Pullmann to create meta-use-case 21:36:08 Sorry, but no Tracker is associated with this channel. 21:36:10 For contactPoint there was a specific example from GeoDCAT-AP that Andrea discussed in the issue: https://github.com/w3c/dxwg/issues/95 21:36:22 trackbot, associate this channel with #dxwg 21:36:26 it would be good to find similar motivation for further changes in other properties 21:36:28 Action: SimonCox to create set of issues per dcat:property 21:36:28 Sorry, but no Tracker is associated with this channel. 21:36:50 ACTION: Jaroslav_Pullmann to create a use case that explains the meta modelling requirement for domain/range restrictions on the dcat:ContacPoint 21:36:50 Sorry, but no Tracker is associated with this channel. 21:37:16 see Local constraints - Use owl:Restriction constraints to bind DC properties to DCAT classes https://github.com/w3c/dxwg/issues/105 21:37:19 for related issue 21:37:33 topic: Local constraints - Use owl:Restriction constraints to bind DC properties to DCAT classes https://github.com/w3c/dxwg/issues/105 21:37:50 we discussed this in the context of the above 21:37:59 topic: Dependencies – continue discussion from https://www.w3.org/2018/01/31-dxwgdcat-minutes#x06 and https://github.com/w3c/dxwg/issues/111 21:38:02 topic: Dependencies – continue discussion from https://www.w3.org/2018/01/31-dxwgdcat-minutes#x06 and https://github.com/w3c/dxwg/issues/111 21:38:50 RRSAgent, make logs public 21:39:57 SimonCox: DCAT has dependencies on several ontologies, e.g. DC-Terms, SKOS, FOAF, potentially PROV in the future 21:40:24 ... only SKOS and vCard are W3C standards 21:40:45 ... and PROV, if we add it, but the others are popular vocabularies on the Web 21:41:01 ... including them introduces risks, but also efficiencies if they are used 21:41:47 q? 21:42:03 ... NickCar and Makx have asked if there are more opinions on that issues 21:42:20 s/NickCar/NicholasCar 21:42:20 +q 21:42:48 ... another questions was around the ORG ontology and a Person ontology (which I am not familiar with) 21:42:54 https://joinup.ec.europa.eu/page/core-vocabularies 21:43:22 ... if we adopt PROV, the agent class is potentially replicated 21:43:31 Nicholas, what is the rationale of including org-ontology? 21:43:33 ISA Core Person Vocabulary: https://www.w3.org/ns/person 21:43:35 q? 21:43:40 ack NicholasCar 21:43:41 ... we may end up with some axiomatization that is not intended 21:44:08 Yes it's the W3C one https://www.w3.org/ns/person 21:44:51 NicholasCar: reusing old ontologies may be a problem in regards to what happened in the meantime. Dublin Core, in particular. 21:45:00 org, prov, person, foaf all have agent-ish classes and do not necessarily have clear relationships 21:45:06 also vCard implicitly 21:45:20 NicholasCar: For ORG, we may want a better handling of groups which is not done in FOAF 21:45:37 q+ 21:45:42 q+ 21:45:48 ... broader set of metadata available if we allow a more sophisticated agent handling 21:45:59 +1 for NicholasCar for a better agent handling allowing groups 21:46:36 No need for change in DCAT I think. org:Organization is a subclass of foaf:Agent anyway. 21:46:50 SimonCox: One of the modelling solutions is to define a local agent class and describe its relations to external vocabularies 21:47:09 q? 21:47:14 ack SimonCox 21:47:15 ack SimonCox 21:47:16 q+ 21:47:19 ack AndreaPerego 21:47:22 +q 21:47:51 It seems to me that foaf:Agent/dct:Agent are broad enough. 21:48:19 AndreaPerego: In our case we associate the authors to the Dataset. We need to assign the affiliations of the authors. We can't do that in FOAF, so we use the ORG ontology. 21:48:31 q+ 21:49:24 ... metadata coming from CrossRef, for example, we add this metadata using the external vocabularies 21:49:54 I think it is perfectly fine to describe a foaf:Agent with properties from ORG 21:50:00 ... if we have a tool that only understands FOAF, for example, everything that is related to ORG, it will be ignored 21:50:02 ack Jaroslav_Pullmann 21:50:44 Jaroslav_Pullmann: We looked at the ORG ontology, but we had a hard time to see the extra benefit of the ORG ontology. 21:51:07 ack alejandra 21:51:13 ... we don't need to import 21:51:26 The ORG property I mentioned to specify affiliation is https://www.w3.org/TR/vocab-org/#property-memberof 21:51:29 alejandra: Agree to not importing the whole ontology. 21:51:31 q+ 21:52:27 alejandra: we should use what we need from ontologies, but be minimal and not use a local class. 21:52:41 ack SimonCox 21:53:33 I fail to see the problem here. DCAT only declares the range of one of its properties to be a foaf:Agent. Nowhere is it said that you can only use FOAF properties to describe a foaf:Agent. 21:53:35 SimonCox: the ORG ontology's primary functions are organisational history and structure 21:53:55 ... the tricky one will be PROV-O. with the agent class 21:54:02 Agree with just using ORG where needed if foaf:Agent already used 21:54:14 ack arminhaller 21:54:17 q? 21:54:18 DCAT actually says nothing about how to describe agents. 21:54:23 Agree too that PROV Agent more difficult 21:55:10 arminhaller: need to make clear that dcat classes and properties are consistent with the other W3C ontologies 21:55:16 q? 21:56:13 PROPOSED: The preference as a general rule will be not to import ontologies 21:56:21 +1 21:56:22 +1 21:56:22 +1 21:56:22 +1 21:56:23 +1 21:56:29 +1 21:56:30 +1 21:56:32 +1 21:56:32 +1 21:56:36 RESOLVED: The preference as a general rule will be not to import ontologies 21:56:39 +1 21:56:55 +1 21:57:28 I import in Protege for dev then delete imports before publication! 21:57:31 https://github.com/w3c/dxwg/issues/53 21:59:07 q+ 21:59:30 SimonCox: I have dominated the agenda so far, I am inviting members to use the mailing list to propose topics 22:00:15 q+ 22:00:29 ack AndreaPerego 22:00:35 ... there was a lot of discussion on versioning earlier, maybe someone from that set of people can propose an agenda item 22:01:43 AndreaPerego: Another issue, I want to raise an issue if we can use DCAT terms also for Catalogs or other data sources, not only dcat:Dataset 22:01:51 q+ 22:02:07 ack Jaroslav_Pullmann 22:02:11 ... other type of resources should be supported other than datasets 22:02:14 q? 22:02:54 Jaroslav_Pullmann: There are comments on the UCR document, the dynamic access to data, paramaterialised arrays. we need to look at those. 22:03:08 q? 22:03:12 s/arrays/URIs/ 22:03:13 RRSAgent, make logs public 22:03:19 RRSAgent, draft minutes 22:03:19 I have made the request to generate https://www.w3.org/2018/02/14-dxwgdcat-minutes.html arminhaller 22:03:36 bye 22:03:39 thanks, and bye! 22:03:39 Thanks, and bye! 22:03:40 present- 22:03:40 Thanks for the interesting discussion, bye 22:03:48 bye 22:03:51 bye 22:21:56 AndreaPerego has joined #dxwgdcat 22:22:15 RRSAgent, draft minutes v2 22:22:15 I have made the request to generate https://www.w3.org/2018/02/14-dxwgdcat-minutes.html AndreaPerego 22:22:40 RRSAgent, make logs world 22:22:42 RRSAgent, draft minutes v2 22:22:42 I have made the request to generate https://www.w3.org/2018/02/14-dxwgdcat-minutes.html AndreaPerego 22:24:29 RRSAgent, draft minutes v2 22:24:29 I have made the request to generate https://www.w3.org/2018/02/14-dxwgdcat-minutes.html AndreaPerego 22:24:56 RRSAgent, make logs world