- From: W3C Community Development Team <team-community-process@w3.org>
- Date: Sun, 22 Jan 2017 16:51:46 +0000
- To: public-skosowlinterop@w3.org
Some examples of how people use SKOS, beyond just filling in the scheme: A . subclass skos:Concept with a class that means the same, but has its name in the national language. Example: ex-de:Konzept rdfs:subClassOf skos:Concept . ex-nl:Begrip rdfs:subClassOf skos:Concept . The use case for this is merely that one wants to provide the user with a model that is in the national language. B: to subclass skos:Concept with a number of classes that describe the body of knowledge. Example: ex:Vehicle rdfs:subClassOf skos:Concept . The idea behind this is that the developer wants to use the skos semantic relation properties to build a simple hierarchy. C: to subclass skos:Concept with a number of classes with OWL restrictions that describe the body of knowledge. Example: ex:Vehicle rdfs:subClassOf skos:Concept ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty ex:hasColour ; owl:someValuesFrom ex:Colour ; ] ; The idea behind this is that the developer wants to use the skos properties to build a simple hierarchy, AND use the restrictions to further describe the Vehicle set. E. To extend SKOS with capabilities that are (more or less) available in OWL: http://www.ddialliance.org/Specification/RDF/XKOS ---------- This post sent on SKOS and OWL for Interoperabilty Community Group 'SKOS in the wild' https://www.w3.org/community/skosowlinterop/2017/01/22/skos-in-the-wild/ Learn more about the SKOS and OWL for Interoperabilty Community Group: https://www.w3.org/community/skosowlinterop
Received on Sunday, 22 January 2017 16:51:52 UTC