19:55:29 RRSAgent has joined #dxwgdcat 19:55:29 logging to https://www.w3.org/2018/04/18-dxwgdcat-irc 19:55:41 rrsagent: make logs public 19:56:07 meeting: DCAT team 2018-04-18 19:57:43 NicholasCar has joined #dxwgdcat 19:57:50 present+ 19:58:47 Morning, can hear but will limit speach - sleeping kids 19:59:33 PWinstanley has joined #dxwgdcat 19:59:51 present+ 19:59:55 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2018.04.18 20:01:17 regrets: Alejandra 20:01:21 present+ 20:01:53 regrets: Makx 20:03:18 DaveBrowning has joined #dxwgdcat 20:04:16 riccardoAlbertoni has joined #dxwgdcat 20:05:16 present+ 20:05:59 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2018.04.18 20:06:43 present+ 20:06:59 roba has joined #dxwgdcat 20:07:08 Problem with webex DaveBrowning ? 20:08:19 Will join soon 20:08:28 stijn_goedertier_AIV has joined #dxwgdcat 20:08:39 present+ 20:08:43 https://github.com/w3c/dxwg/issues/114 20:09:02 issue above is license/ODRL 20:09:02 Sorry, but no Tracker is associated with this channel. 20:09:45 present+ 20:10:05 scribe: PWinstanley 20:10:30 topic: confirm agenda 20:10:43 https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2018.04.18 20:11:49 AndreaPerego has joined #dxwgdcat 20:12:20 confirmed 20:12:35 Topic: approve minutes of last meeting 20:12:44 https://www.w3.org/2018/04/11-dxwgdcat-minutes 20:12:44 present+ AndreaPerego 20:12:48 +1 20:12:51 0 ( i was absent) 20:12:58 0 also absent 20:13:01 0 (absent) 20:13:06 +1 20:13:10 +1 20:13:11 +1 20:13:27 resolved: approve minutes of last meeting 20:13:36 topic: licenses and rights 20:13:48 https://github.com/w3c/dxwg/issues/114 20:14:12 https://github.com/w3c/dxwg/issues/114#issuecomment-382298577 20:14:40 SimonCox: drawing attention to this topic of discussion. Makx providing clarification as per comments 20:15:55 ... in earlier conversations best practice would be to refer to existing, but we need to have the possibility of coping with new options and other elements that ODRL allows. 20:16:10 q+ 20:16:18 ... An informal use case has been added. Other contributions are welcomed 20:16:19 ack NicholasCar 20:17:05 Should we add odrl:hasPolicy as an additional property recommended for use on a dcat:Distribution? 20:17:08 NicholasCar: is it sensible to have policy associations? Anything that retains flexibility is a good thing 20:17:55 SimonCox: OWL/RDFS constraints are not there, it is simply a recommendation 20:18:16 ... but do we formally include ODRL as a suggestion in the spec? 20:18:28 NicholasCar: I think that is helpful 20:18:34 q? 20:18:40 q+ 20:18:44 q+ 20:19:10 ack DaveBrowning 20:19:11 ... it is a useful pointer to developers/catalogue managers 20:20:27 q+ 20:20:31 DaveBrowning: I agree with NicholasCar . ODRL provides scope for wide coverage within the publishing industry and provides economies of scale - it is a one-stop shop 20:20:31 ack AndreaPerego 20:20:38 q? 20:22:02 if we need a machine readable validation around use of a recommended vocabulary then we have a formal profile.. 20:22:08 AndreaPerego: we need to clarify the use cases where ODRL is helpful. We already have dct:rights and others. I don't recall any use case not covered by the generic 20:22:49 SimonCox: we are aware that there is no documented use case and hence NicholasCar has added a full additional use case specifically using ODRL 20:22:57 q+ on licensing use case 20:23:03 ... there needs to be proper guidance in the doc 20:23:52 Andrea refers to the ODRS http://schema.theodi.org/odrs/ 20:24:04 AndreaPerego: We still need to discuss the the ODI vocabulary - ODRS 20:24:41 ... it is worth looking at this because they found a way to use a standard license and determine the text for the attribution. 20:24:54 ... this is dependent on the dataset that one is licensing 20:25:03 ack NicholasCar 20:25:10 SimonCox: AndreaPerego can you please add to #114 20:26:06 q- (also wanted to comment on attribution URL / attribution text) 20:26:15 q- 20:26:31 NicholasCar: Am aware of ODRS. Have used. Next question is do we need both, or will ODRL do everything? I'm implementing a license register in a project and will have an ODRL test case in Linked Data using real data 20:27:13 SimonCox: It is premature to consider the agenda proposal but that conversation provided issues that we add to the discussion 20:27:25 topic: Consequences of expanded scope of dcat:Catalog 20:28:18 SimonCox: 2-3 weeks ago we agreed that DCAT would explicitly cover data services, but we haven't considered specific proposals for new properties 20:28:21 specific or general property for catalog contents - https://github.com/w3c/dxwg/issues/116 20:28:44 ... a long thread on issue 116 is about the range of dcat:Dataset. 20:29:24 ... the dcat:dataset pred has been used to link to things that hitherto would not have been considered as datasets, 20:30:18 ... but we are proposing to extend the use of dcat:dataset so that one looks at the items to determine their class rather than inferring from the range 20:31:00 q? 20:31:04 ... Next step is to mint specific predicates for different catalogue contents 20:31:09 q+ 20:31:16 ack NicholasCar 20:31:43 we can hear you nick 20:32:16 NicholasCar: isn't this direct predicate minting against the qualified association pattern we are implementing elsewhere? 20:32:26 ... isnt' a generic approach better? 20:32:33 q? 20:32:38 present- 20:33:20 SimonCox: when modelling the tension between generic and specific is always there. No 'right' answer. specific preds are there for 'important' relationships 20:33:47 ... The qualified association pattern requires a sideways look to determine the class 20:34:19 q+ 20:34:21 q+ to say that the two approaches (generic vs specific properties) are not mutually exclusive 20:34:33 ack roba 20:34:42 ... in this situation the name of the predicate is unsuitable for classes that are not datasets. If we are expanding to include services it makes sense to have a service-specific pred 20:34:59 Please see https://github.com/w3c/dxwg/wiki/Cataloguing-data-services 20:35:28 q? 20:36:13 wonders if we are we talking about data sets exposed by services - or data-less transformation services? 20:36:29 SimonCox: the 2nd diagram in the above wiki page shows the most common use case and the relations between the service and the datasets 20:36:30 q? 20:36:34 ack AndreaPerego 20:36:34 AndreaPerego, you wanted to say that the two approaches (generic vs specific properties) are not mutually exclusive 20:38:06 the proposal does not change the scope of dcat:dataset - it adds finer grained semantics around distribution 20:38:37 AndreaPerego: we have an example taken from different context that include resources that are dcat:Dataset, but we also have events which can be either datasets or physical things like chemical samples. 20:38:54 q+ 20:39:10 ... we need to leave the door open for diverse classes, so a generic property can help with this 20:39:13 ack Si 20:39:16 ack SimonCox 20:39:20 but is a data access service a virtualised "set of datasets" ? 20:39:37 SimonCox: in some examples in the past AndreaPerego you used dc:terms? 20:39:49 dcterms:hasPart 20:39:53 AndreaPerego: yes, because no other was available/suitable 20:40:14 s\dc:terms\dcterms:hasPart 20:40:17 ... the point is that this predicate is overused and it has become ambiguous 20:40:40 SimonCox: it is from observiing that that the motivation for other predicates originated 20:41:19 ... we should allow ourselves to include other predicates than dcat:dataset 20:41:32 q? 20:41:36 ... and this means that we don't need to relax the range of this pred 20:41:48 Jaroslav_Pullmann has joined #dxwgdcat 20:42:06 ... the thinking originates from observing what AndreaPerego has done before 20:42:23 Hello everybody, I am travelling with no reliable connection. 20:43:04 ... this list of predicates will be small in number (<5) but will be specific to the class 20:43:21 PROPOSED: the range of dcat:dataset shall not be relaxed, and the DCAT backbone shall have specific properties for other types of resource included in a catalog (sub-properties of dct:hasPart) 20:43:25 q? 20:44:05 PROPOSED: the range of dcat:dataset shall not be relaxed, and the DCAT backbone shall have specific membership predicates for other types of resource included in a catalog (sub-properties of dct:hasPart) 20:44:11 * Hi Andrea! 20:44:22 q+ to ask is this includes a possible super-property for them 20:44:33 ack AndreaPerego 20:44:33 AndreaPerego, you wanted to ask is this includes a possible super-property for them 20:45:18 PROPOSED: the range of dcat:dataset shall not be relaxed 20:45:21 AndreaPerego: for clasrification - the proposal is for 5 props, or are these to be sub-props of a more generic super-prop? 20:45:22 issue #116 20:45:22 Sorry, but no Tracker is associated with this channel. 20:45:33 +1 20:45:40 s/clasrification /clarification / 20:45:59 +1 20:46:02 +1 20:46:04 +1 20:46:10 +1 20:46:11 +1 20:46:13 +1 20:46:29 dataservice as a subtype of dataset that has1+ service distributions and may have multiple other datasets exposed (finer grained semantics?) 20:46:50 RRSAgent, draft minutes v2 20:46:50 I have made the request to generate https://www.w3.org/2018/04/18-dxwgdcat-minutes.html AndreaPerego 20:46:54 so we can close https://github.com/w3c/dxwg/issues/116 20:47:26 RRSAgent, make logs world 20:48:17 roba: I think this comes down to finer grained semantics. I think services look like datasets 20:48:43 SimonCox: the boundary between serialised resources and services is blurred 20:49:23 +1 20:49:40 RESOLVED: the range of dcat:dataset shall not be relaxed, and the DCAT backbone shall have specific membership predicates for other types of resource included in a catalog (sub-properties of dct:hasPart) 20:49:46 RRSAgent, draft minutes v2 20:49:46 I have made the request to generate https://www.w3.org/2018/04/18-dxwgdcat-minutes.html AndreaPerego 20:50:17 q? 20:50:30 chair: SimonCox 20:50:31 RRSAgent, draft minutes v2 20:50:31 I have made the request to generate https://www.w3.org/2018/04/18-dxwgdcat-minutes.html AndreaPerego 20:50:35 class and property for data distribution service https://github.com/w3c/dxwg/issues/180 20:50:47 Topic: issue 180 20:50:52 so if a distribution was able to specify service type would this motivation still hold? 20:51:17 RESOLVED: the range of dcat:dataset shall not be relaxed 20:51:23 \me ok 20:51:51 s/RESOLVED: the range of dcat:dataset shall not be relaxed, and the DCAT backbone shall have specific membership predicates for other types of resource included in a catalog (sub-properties of dct:hasPart)/RESOLVED: the range of dcat:dataset shall not be relaxed/ 20:52:35 (note a subproperty of dcat:dataset where range is a subclass of Dataset meets the proposal) 20:52:55 ... that was my suggestion 20:53:07 SimonCox: roba please can you explain your vision in a diagram? 20:53:19 q? 20:53:20 q+ 20:53:21 ... then we can do a comparison 20:53:28 ack roba 20:53:41 RRSAgent, draft minutes v2 20:53:41 I have made the request to generate https://www.w3.org/2018/04/18-dxwgdcat-minutes.html AndreaPerego 20:54:14 roba: going back to the original proposal - the one on the wiki page -- 2 classes, almost identical. 20:55:08 ok 20:55:22 so if a distribution was able to specify service type would this motivation still hold? 20:55:26 ACTION: RobA to make more detailed counter-proposal 20:55:26 Sorry, but no Tracker is associated with this channel. 20:55:32 q? 20:56:10 especially if a sub-type of Dataset which is a collection of other datsets is also supported (i.e we have data set relationships) 20:56:24 otherwise we may have multiple ways of doing this when those facilities are available 20:56:32 SimonCox: This goes back to the earlier part of the discussion - many solutions and we decide to give names to some properties and not others depending on the way the model is going to be used 20:56:52 @roba, yes it holds for me. The service itself won't be "hidden" into a distribution, but a standalone entity. 20:57:06 ... frm the discussion coming from AndreaPerego services needed to be first class objects in a data catalogue. 20:57:25 ... there might appear to be an implicit super class, 20:57:26 @AndreaPerego - yes it still will be as a sube type of Dataset... 20:57:28 The distribution can be linked to the service, but it is the distribution itself. 20:57:43 s/but it is the distribution itself/but it is not the distribution itself/ 20:57:54 ... we might be mixing the abstractions in the background with requirements in the foreground. 20:58:08 q? 20:58:09 q+ 20:58:11 yes an implicit superclass would help but changes the range of dcat:dataset :-( 20:58:21 ... the diagram might be showing only a part view of the requirements, with some components not shown 20:59:15 Dear all, before this meeting ends - I started to include Øystein's proposals like here: https://github.com/w3c/dxwg/issues/56#issuecomment-382467602 20:59:33 I have lost audio 20:59:53 anyway - I'm pointing out what looks like an antipattern in the model, and missing consideration of the implications of service types in distribution semantics - i would rather see this discussed when those facilities are on the table 21:01:43 riccardoAlbertoni: the services are not only ones exposing data, they can be other types. In this case it is perhaps better not to use a subclass. It would be reasonable to have class specialisation if they are services exposing data, but a DCAT catalogue can include other kinds of services 21:02:18 ... it is not a matter of object orientation, it is a matter of what the classes represent 21:02:18 @riccardoAlbertoni I agree - but i would model it differently if thats the case... we perhaps need a superclass or "mix-in" for generic catalog entry metadata 21:02:20 SimonCox_ has joined #dxwgdcat 21:02:45 SimonCox: this discussion needs to be continued next week 21:02:48 RRSAgent, draft minutes v2 21:02:48 I have made the request to generate https://www.w3.org/2018/04/18-dxwgdcat-minutes.html AndreaPerego 21:03:09 +1 to riccardoAlbertoni 21:03:11 RRSAgent, draft minutes v2 21:03:11 I have made the request to generate https://www.w3.org/2018/04/18-dxwgdcat-minutes.html AndreaPerego 21:03:41 bye 21:03:41 bye 21:03:46 thanks all 21:03:47 bye!