W3C home > Mailing lists > Public > public-powderwg@w3.org > December 2007

Re: Open Issues: DR scope

From: Andrea Perego <andrea.perego@uninsubria.it>
Date: Thu, 06 Dec 2007 14:47:08 +0100
Message-ID: <4757FD5C.5080006@uninsubria.it>
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:Restriction rdf:ID="AllResources">
  <owl:onProperty rdf:resource="&wdr;includeHost" />

but I'm not sure whether this is what you meant.

Received on Thursday, 6 December 2007 13:42:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:06:03 UTC