08:16:29 RRSAgent has joined #dxwgdcat 08:16:29 logging to https://www.w3.org/2018/05/24-dxwgdcat-irc 08:17:05 meeting: DCAT team meeting 2018-05-24 08:17:11 chair: SimonCox 08:17:22 regrets: Makx 08:17:53 Agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2018.05.24 08:18:01 present+ 08:27:42 roba has joined #dxwgdcat 08:30:12 * dang - trying to find password.. 08:32:31 DaveBrowning has joined #dxwgdcat 08:33:37 riccardoAlbertoni has joined #dxwgdcat 08:34:19 alejandra has joined #dxwgdcat 08:34:49 Stijn_Goedertier_AIV has joined #dxwgdcat 08:36:18 hi all! 08:39:05 present+ 08:39:17 present+ 08:39:50 scribenick: alejandra 08:39:55 present+ 08:39:58 Agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2018.05.24 08:40:12 present+ 08:40:27 present+ 08:40:28 topic: confirm agenda 08:40:36 chair: SimonCox 08:41:27 SimonCox: proposal at the end of the discussion to close the issue provisionally 08:41:39 ... moving on with some issues, considering that all solutions are provisional 08:42:16 ... I propose to continue the discussion on DCAT service catalogs 08:42:19 +q 08:42:32 ... I chose 3 issues almost in order of complexity 08:42:41 ack alejandra 08:43:52 alejandra: link to ttl in FPWD - needs to be to a dated version that corresponds to dcat.ttl at time of approval 08:44:33 +1 08:44:37 +1 08:44:42 +1 08:44:46 present+ 08:44:49 +1 08:44:56 +1 08:45:00 topic: approve minutes of last meeting 08:45:09 https://www.w3.org/2018/05/17-dxwgdcat-minutes 08:45:14 +1 08:45:15 +1 08:45:19 +1 08:45:28 about the ttl in FPWD, I'll continue the discussion via email 08:45:29 +1 08:45:31 +1 08:45:33 +1 08:45:44 resolved: approve minutes of last meeting 08:45:57 q+ 08:45:58 topic: Expanded scope of dcat:Catalog 08:46:20 related to issue: https://github.com/w3c/dxwg/issues/172 08:46:40 example from Andrea and SimonCox https://github.com/w3c/dxwg/issues/237 08:47:13 the discussions on the model are in the wiki here: https://github.com/w3c/dxwg/wiki/Cataloguing-data-services 08:47:21 AndreaPerego has joined #dxwgdcat 08:47:23 https://github.com/w3c/dxwg/issues/237#issuecomment-390098689 08:47:35 present+ AndreaPerego 08:48:38 SimonCox: in the example, what is new is that the :MyCatalog uses dcat:service to link to a service 08:48:42 ... let's ignore the URI for now 08:49:07 ... dcterms:type has two values from the inspire code list 08:49:22 ... and there is a link to a dcat:endpoint 08:49:31 ... that would be a new addition in DCAT to satisfy this requirement 08:49:38 ... the rest is insignificant 08:49:55 https://rawgit.com/w3c/dxwg/dcat-service-simon/dcat/index.html#vocabulary-overview 08:50:02 q? 08:51:08 ... probably the biggest issue is having DiscoveryService as a subclass of Catalog and DataService 08:51:49 ack roba 08:52:07 roba: 3 things, first the bigger picture 08:52:27 ... comment by Maxk description of a profile as a resource 08:52:45 ... question about extending dcat:Resource 08:53:00 ... dct:conformsTo part of a DataService 08:53:05 ... but also for Dataset 08:53:08 q+ to comment that subclasses shown are not exhaustive 08:53:16 ... so it probably belongs to the superclass 08:53:22 ... Resource 08:53:38 I would be in favour of considering a profile as one of the resources that can go into a catalogue - in particular, into an adms:AssetRepository. 08:53:39 ... every Resource potentially has a requirement for that 08:53:56 q+ cardinalities to be read like RDF not UML 08:54:20 ... dcat:Distribution property may need a super property 08:54:31 +q to ask about Distribution and DataServiceDistribution 08:54:50 s/dcat:Distribution/dcat:distribution 08:54:55 q+ to say that sub-property relationships not shown 08:55:35 roba: csw in the example is actually a skos:Collection 08:55:51 ack SimonCox 08:55:51 SimonCox, you wanted to comment that subclasses shown are not exhaustive and to say that sub-property relationships not shown 08:55:56 q+ to ask roba to explain the point about skos:Collection 08:55:59 ... I can probably fix that, would you like me to explicitly declare it as a dct:Standard 08:56:12 SimonCox: subclassing is not exhaustive 08:56:23 ... the diagram should be read as RDF not UML 08:56:44 ... some of the classes that we put before are things we haven't discussed fully yet (in gray) 08:57:04 ... set of subclasses of Resource is not exhaustive 08:57:22 ... superclass of Distribution is not yet defined 08:57:31 ... the subproperties relationships are not shown 08:57:50 q+ to ask what limits there are on catalogue-able dcat:Resources... 08:57:53 ... I'm interested in knowing if anything is broken 08:58:28 +1 to SimonCox ( about reading UML under the open assumption though i would consider to change the notation or put a big warning about it) 08:58:45 roba: there is one error on dct:conformsTo 08:58:59 q? 08:59:15 q- cardinalities 08:59:17 +1 to SimonCox about adding sub-classes/properties statement, and when really needed (we need to be careful not to add dependencies having negative impact on not foreseen use cases) 08:59:21 ack alejandra 08:59:21 alejandra, you wanted to ask about Distribution and DataServiceDistribution 08:59:46 s/properties statement, /properties statements later, / 08:59:55 RRSAgent, make logs world 09:00:02 RRSAgent, draft minutes v2 09:00:02 I have made the request to generate https://www.w3.org/2018/05/24-dxwgdcat-minutes.html AndreaPerego 09:00:07 q? 09:00:39 Not clear to me what the superclass of "distribution" is meant for. 09:00:53 ack AndreaPerego 09:00:53 AndreaPerego, you wanted to ask roba to explain the point about skos:Collection 09:00:54 alejandra: relationship between Distribution and DataDistributionService needs to be clarified in my view 09:01:06 alejandra: what is their difference and relationship with Dataset 09:01:34 dcat:Distribution is intended to be 'representation' of a dataset, like a file 09:01:35 AndreaPerego: I'd like to discuss further what roba mentioned about skos:Collection 09:01:54 ... but it can be at a later stage 09:01:58 http://www.opengis.net/def/serviceType/ogc/csw is currently resolving to a thing that is a skos:Collection - I am actually maintaining this - I can change it so that... 09:02:02 ... we should look at what other communities are doing 09:02:25 ... e.g OAI-PMH 09:02:36 http://www.opengis.net/def/serviceType/ogc/csw is a skos:Concept and a dct:Standard and http://www.opengis.net/def/serviceType/ogc/csw/ is the "collection of versions" 09:02:40 ... we don't have evidence to define precisely the scope of the catalogue 09:02:52 i.e. i can fix the data to make the example correct :-0 09:02:53 ... we should refer to existing standards for what the catalogue contains 09:02:54 alejandra: wants to think about the relationships between DataDistribultionService, DIstribution, Dataset 09:03:11 s/DataDistribultionService/DataDistributionService/ 09:03:13 q? 09:03:17 ... I don't understand the point of the superclass of Distribution 09:03:18 ack DaveBrowning 09:03:18 DaveBrowning, you wanted to ask what limits there are on catalogue-able dcat:Resources... 09:03:36 s/DIstribution/Distribution/ 09:03:47 q+ 09:03:57 DaveBrowning: what is the scope of those things that can be catalogued 09:04:05 ... what standards should be, do we have a boundary 09:04:17 ... we are calling it Data Catalogue 09:04:22 q+ to comment on DaveBrowning 's point 09:04:39 ... so what do we include data-related 09:04:41 Noting the example of https://joinup.ec.europa.eu/release/dcat-ap-v11 09:05:07 ... this could come up on e-publication 09:05:29 ack roba 09:06:03 roba: the link above showed a profile as a dataset 09:06:06 +1 to squinting.... 09:06:45 SimonCox: if one would consider adding profile in the diagram, would it be a subclass of Dataset or Resource? 09:07:10 roba: it is a Resource 09:07:46 roba: a guidelines document is not the same as a Distribution but it is a Resource 09:07:56 SimonCox: this is a core model, what is not stated can be added 09:08:06 q? 09:08:13 roba: there seems to be an equivalent to Distribution as a pattern 09:08:14 ack AndreaPerego 09:08:14 AndreaPerego, you wanted to comment on DaveBrowning 's point 09:08:44 AndreaPerego: about what to include into the catalogue, it is related to the work of ADMS 09:08:52 yes to roba - dct:conformsTo could be moved up to dcat:Resource 09:09:03 ... it was designed due to the need of implementing catalogues of ReusableAssets 09:09:09 (so that is on the record ;-) 09:09:12 ... ontologies, data models, data schemas, etc 09:09:18 ... it was specifically designed for that 09:09:37 ... ADMS includes what was considered relevant for documenting models 09:09:40 +q 09:09:45 ... profiles is in scope as an asset for ADMS 09:09:51 q+ to commend the ADMS designers for getting there first! 09:10:16 ... when ADMS was contributed in W3C, the gov linked data group, ended up considering ADMS as a specialiaation of DCAT 09:10:25 s/specialiaation/specialisation 09:10:30 so we can make profile a subclass of an ADMS class and transitively have it as a subclass? 09:10:57 AndreaPerego: I see loads of correspondences between profiles and their definition in SHACL and its relationship of ADMS 09:11:15 +1 to considering Profiles (and standards) in scope ... following the patterns already tested in ADMS! 09:11:19 ... we could consider the inclusion of a profile within a DCAT catalogue 09:11:27 q? 09:11:33 ... or a more specific catalogue, which is more in scope of ADMS 09:11:51 ... the implementation resource description is a type of distribution 09:12:02 ... I don't see the need of having a superclass of Distribution 09:12:07 q+ to reopen the point from alejandra 09:12:09 q? 09:12:13 +1 as a type of distribution - happy if no subclassing needed in dcat core 09:12:15 ack riccardoAlbertoni 09:12:47 riccardoAlbertoni: I agree about including the profiles in the catalogues 09:13:06 ... I wonder if we should refer to the profile description ontology that Nick and roba have proposed 09:13:11 q+ 09:13:18 ack SimonCox 09:13:18 SimonCox, you wanted to commend the ADMS designers for getting there first! and to reopen the point from alejandra 09:13:44 SimonCox: thanks AndreaPerego for reminder about ADMS 09:14:45 q+ 09:14:50 ... we should check ADMS details 09:15:43 SimonCox: going back to the point that alejandra made on the relationship between DataDistributionService, Distribution and Dataset 09:16:04 ... pattern of DataDistributionService often tightly bound to datasets that they serve 09:16:15 ... that's why the link to the abstract Datatset 09:16:23 s/Datatset/Dataset 09:16:32 ... Distributions are usuall at the end of the chain 09:16:45 +q 09:17:00 ... inverse properties maybe? although discussions were against them 09:17:00 ack roba 09:17:22 roba: I'm happy about considering ADMS and not clutter the discussion now and move forward 09:17:44 ... not worry much about the profiles specifics at this point 09:17:48 ack AndreaPerego 09:18:04 AndreaPerego: relation between Distribution and Service 09:18:33 ... in the diagrams Simon presented and considering how DCAT is used, there is an indirect relationship between the service and the distribution 09:19:25 ... we had discussed and it was brought up again about having a property pointing to the service description 09:19:47 ... in DCAT-AP people point from the Distribution to this service description document 09:20:00 q? 09:20:01 ... there is not necessarily a direct relationship 09:20:18 SimonCox: we are trying to acknowledge the requirements from what people have done 09:20:28 ... but also recognised that there have been some hacks 09:20:47 ack alejandra 09:21:48 alejandra: DataDistributionService should have a direct relationship to Distributions as well as Datasets 09:22:39 SimonCox: we used to conflate Distributions and DistributionServices 09:22:45 q+ 09:22:59 ... a single DistributionService could deliver multiple Distributions 09:23:14 ack AndreaPerego 09:23:45 AndreaPerego: relation between service and distribution is tricky 09:23:58 ... service can offer multiple datasets and the same distribution in different formats 09:24:07 isn't that a different distribution? 09:24:17 AndreaPerego: it is not easy to map a Distribution to a Service 09:25:07 +1 09:25:09 SimonCox: should I put a proposal and accept it provisionally to move forward? 09:25:12 +1 09:25:16 +1 09:25:21 Proposed: Adopt solution shown in https://raw.githubusercontent.com/w3c/dxwg/dcat-service-simon/dcat/UML/DCAT-summary.png (not including greyed elements) as the provisional solution to an enlarged catalog scope, to allow us to move on and consider other DCAT matters for a while. dct:conformsTo moved up to dcat:Resource N.B. The model may be revisited later. 09:25:33 +1 09:25:40 +1 09:25:44 +1 to the proposal 09:25:44 +1 09:25:47 +1 09:25:47 +1 09:26:09 +q about process 09:26:23 ack alejandra 09:26:58 alejandra: are we then closing issues about this? 09:27:17 SimonCox: I think so, with the provision that issues can be reopened 09:28:06 q+ to make a suggestion 09:28:17 ack 09:28:46 alejandra: we need to work out the defintions 09:29:00 +1 09:29:21 approved: accepting the proposal module fix of dct:conforms and definitions 09:29:36 definitions will be refined and resolved on the lists and GitHub 09:29:39 s/module/modulo 09:29:55 q? 09:29:59 ack 09:30:01 ack 09:30:05 ack AndreaPerego 09:30:05 AndreaPerego, you wanted to make a suggestion 09:30:11 q- about 09:30:16 q- process 09:30:36 AndreaPerego: it would be good to have the link to the example 09:30:47 +1 to andrea 09:30:53 also name of dcat:endPoint needs resolving 09:31:04 ... so if we close issues and there are things pending, let's open specific issues 09:31:11 +1 to AndreaPerego 09:31:19 RRSAgent, draft minutes v2 09:31:19 I have made the request to generate https://www.w3.org/2018/05/24-dxwgdcat-minutes.html AndreaPerego 09:31:25 s/andrea/AndreaPerego 09:31:36 +q 09:32:01 resolved: accepting the proposal module fix of dct:conforms and definitions 09:32:07 s/approved: accepting/resolved: accepting/ 09:32:09 RRSAgent, draft minutes v2 09:32:09 I have made the request to generate https://www.w3.org/2018/05/24-dxwgdcat-minutes.html AndreaPerego 09:32:33 alejandra: also reminding the need for query cases 09:32:44 Bye ! 09:32:54 bye