- From: Andrea Perego <andrea.perego@uninsubria.it>
- Date: Thu, 06 Dec 2007 14:47:08 +0100
- CC: Public POWDER <public-powderwg@w3.org>
Hi, Kevin. >> It is not clear to me why you're using here rdf:ID as an attribute to > rdfs:subclassOf. > > Well spotted - I meant rdf:resource :) Thanks. So, the corrected version of your example should be: 1 <owl:Class rdf:ID="ResourceOnExampleDotOrg"> 4 <rdfs:subClassOf rdf:resource="#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> But where the AllResources class is defined? Moreover, you cannot use rdf:resource and then include the restriction - i.e., the rdf:resource attribute is used to denote the object of the statement, but here there is already an object, namely, owl:Restriction. What you can write is: <owl:Class rdf:ID="ResourceOnExampleDotOrg"> <rdfs:subClassOf rdf:resource="#AllResources"> </owl:Class> <owl:Restriction rdf:ID="AllResources"> <owl:onProperty rdf:resource="&wdr;includeHost" /> <owl:hasValue>example.org</owl:hasValue> </owl:Restriction> but I'm not sure whether this is what you meant. Andrea
Received on Thursday, 6 December 2007 13:42:50 UTC