hi michael, you may want to have a look at the SKOS[1] stuff. SKOS allows you to model classifications which don't really fit in the very strict constructs that OWL and RDFS offer. IIRC, you can't use an e.g. "skos:related" property with an owl:Class, though. but with the ACM scheme being closer a "concept" than an "object" taxonomy, it'd perhaps be more appropriate to use skos:broader/narrower instead of rdfs:subClassOf anyway (i.e. it's somewhat complicated to imagine an owl:Thing of rdf:type "Performance and Reliability" ...) hth, benjamin -- Benjamin Nowack Kruppstr. 100 45145 Essen, Germany http://www.bnode.org/ [1]http://www.w3.org/2004/02/skos/ On 08.12.2004 11:09:52, Michael Engelhardt wrote: >Hello out there, >I am currently trying to perform my first steps in the OWL world. Since >searching for a simple and useful example I want to build up the ACM >classification index in OWL. My approach is to express each classification >entry as an owl:class concept, relating them via rdfs:subClassOf. That is >pretty simple. However the ACM classification index encodes references >between certain entries too (e.g. B.2.3 ["Reliability, Testing, and >Fault-Tolerance Reliability, Testing, and Fault-Tolerance"] is related to B.8 >["Performance and Reliability"]) . So my question here is how to model those >references in OWL. I believe using the equivalentClass construct is not >appropriate, because those classes have not same instances. >Could anybody give me an enlightening idea please? > >thanks in advance > >Michael Engelhardt > >.me >Received on Wednesday, 8 December 2004 12:20:26 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:52:12 GMT