search

w3c / dxwg

Data Catalog Vocabulary (DCAT)
https://w3c.github.io/dxwg/dcat/
Other
144 stars 46 forks source link

Dcat issue 1364 second solution #1379

Closed riccardoAlbertoni closed 3 years ago

riccardoAlbertoni commented 3 years ago

An alternative solution to PR #1380

This PR drops the range for dcat:theme, but explicitly defining it as owl:ObjectProperty as suggested by @dr-shorthair in https://github.com/w3c/dxwg/issues/1364#issuecomment-843616224

Considering that dcterm:subject has been recently changed to let both literals and URI, by defining dcat:themes as an owl:ObjectProperty and dropping the dcat:theme's range, dcat:theme would still restrict dcterms:subject to URIs, while dcat:keyword might restrict dcterms:subject to literals.

This would also limit the automatic inference of skos:Concept, which could be potentially problematic when applied to instances whose classes are defined disjoint from skos:Concept.

dr-shorthair commented 3 years ago

This looks clean and sensible to me

riccardoAlbertoni commented 3 years ago

@andrea-perego can you check the rephasing of the note before definingdcat:theme meets the expectation you have expressed in the last DCAT teleconference? Feel free to rephrase it, otherwise. Thanks.

riccardoAlbertoni commented 3 years ago

Thanks, @riccardoAlbertoni .

+1 from me. I just suggested an editorial change.

Thanks, Andrea. I have accepted your suggestion.

riccardoAlbertoni commented 3 years ago

@davebrowning , @pwin , @agbeltran , Is this PR ok for you?