Re: [dxwg] license and rights apply to Dataset as well as Distribution

However, from the discussion here https://github.com/ckan/ckanext-dcat/issues/42 it looks like the DCAT is out of tune with CKAN and Open Data Hub, and that this is causing difficulties for these major metadata platforms. 

@aisaac you correctly point out that there is nothing prohibiting the use of `dct:license` and `dct:rights` on a `dcat:Dataset`, but clearly from the discussion in these user communities there is uncertainty about how this works, and probably a reluctance to use properties out of the context described in the recommendation. To resolve this I don't think leaving the documentation as is would be satisfactory. Can we allow for use of licensing and rights information at both the Dataset and Distribution level, and then leave it up to profiles or repositories to recommend their best practice? 

@makxdekkers you asserted that there is "no formal way to impose inheritance" - well, in the OWA there is no formal way to impose much! But it is relatively easy to write rules for this kind of inheritance, which can be implemented in SPARQL and embedded in an RDF representation using SPIN. For example, I recently proposed something along these lines for part of an extension to SSN - see https://w3c.github.io/sdw/proposals/ssn-extensions/#container-property-rule 
The presumption there is that the local value will always override the value 'inherited' from a container. 
The same pattern would apply on a `dcat:Distribution` inheriting values from the associated `dcat:Dataset`.  

Of course, running the other way is more tricky in the case where different licenses apply to different distributions of the same dataset, without some kind of license/rights algebra! 


-- 
GitHub Notification of comment by dr-shorthair
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/104#issuecomment-376764347 using your GitHub account

Received on Wednesday, 28 March 2018 05:17:27 UTC