In an email that was not reflected into this issue, @kcoyle pointed out that the SKOS editors explicitly declined to introduce a constraint that a `skos:Concept` may not also be a Class: "3.5.1. SKOS Concepts, OWL Classes and OWL Properties Other than the assertion that skos:Concept is an instance of owl:Class, this specification does not make any additional statement about the formal relationship between the class of SKOS concepts and the class of OWL classes. The decision not to make any such statement has been made to allow applications the freedom to explore different design patterns for working with SKOS in combination with OWL." https://www.w3.org/TR/2009/REC-skos-reference-20090818/#concepts So I'm inclined to accept their (the SKOS editors) invitation and go with the flow - i.e. no change required to DCAT or Dublin Core because of `dct:type` entailments. -- GitHub Notification of comment by dr-shorthair Please view or discuss this issue at https://github.com/w3c/dxwg/issues/314#issuecomment-414177633 using your GitHub accountReceived on Monday, 20 August 2018 02:04:45 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:24 UTC