- From: Andrea Perego <andrea.perego@uninsubria.it>
- Date: Thu, 06 Dec 2007 14:22:43 +0100
- To: Public POWDER <public-powderwg@w3.org>
Hi, Kevin. > What puzzles me is the need for owl:equivalentClass, and rdfs:subClassOf > (without an rdf:resource). My (admittedly poor) understanding was that > using equivalentClass you would have: > > 1 <owl:Class rdf:ID="ResourceOnExampleDotOrg"> > 2 <owl:equivalentClass> > 3 <owl:Restriction> > 4 <owl:onProperty rdf:resource="&wdr;includeHost" /> > 5 <owl:hasValue>example.org</owl:hasValue> > 6 </owl:Restriction> > 7 </owl:equivalentClass> > 8 </owl:Class> > > (ref [1]) Thanks for pointing this out. I've just "indirectly" replied to your mail by answering to Stasinos's one. > ...and that if you used subClassOf you would do something like (note > insertion of rdf:ID="AllResources"): > > 1 <owl:Class rdf:ID="ResourceOnExampleDotOrg"> > 4 <rdfs:subClassOf rdf:ID="AllResources"> > 5 <owl:Restriction> > 6 <owl:onProperty rdf:resource="&wdr;includeHost" /> > 7 <owl:hasValue>example.org</owl:hasValue> > 8 </owl:Restriction> > 9 </rdfs:subClassOf> > 12 </owl:Class> > > (ref [2]) It is not clear to me why you're using here rdf:ID as an attribute to rdfs:subclassOf. Thanks Andrea
Received on Thursday, 6 December 2007 13:18:13 UTC