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

Re: DR structure debate: summary and conclusion

From: Andrea Perego <andrea.perego@uninsubria.it>
Date: Fri, 30 Nov 2007 11:32:22 +0100
Message-ID: <474FE6B6.2080200@uninsubria.it>
To: Public POWDER <public-powderwg@w3.org>

A correction to my previous mail [1], about my comment on how we can use
reification to specify the author of the Resource Set and Descriptive
classes:

> [snip]
>
> So, if the following is the class description:
> 
> 1  <owl:Class rdf:ID="ResourceOnExampleDotOrg">
> 2    <owl:equivalentClass>
> 3      <owl:Class>
> 4        <rdfs:subClassOf>
> 5          <owl:Restriction>
> 6            <owl:onProperty rdf:resource="&wdr;includeHost" />
> 7            <owl:hasValue>example.org</owl:hasValue>
> 8          </owl:Restriction>
> 9        </rdfs:subClassOf>
> 10     </owl:Class>
> 11   </owl:equivalentClass>
> 12 </owl:Class>
> 
> we have first to associate an rdf:ID to each property used in the class
> description:
> 
> 1  <owl:Class rdf:ID="ResourceOnExampleDotOrg">
> 2    <owl:equivalentClass rdf:ID="p1">
> 3      <owl:Class>
> 4        <rdfs:subClassOf rdf:ID="p2">
> 5          <owl:Restriction>
> 6            <owl:onProperty  rdf:ID="p3" &wdr;includeHost" />
> 7            <owl:hasValue rdf:ID="p3">example.org</owl:hasValue>
> 8          </owl:Restriction>
> 9        </rdfs:subClassOf>
> 10     </owl:Class>
> 11   </owl:equivalentClass>
> 12 </owl:Class>
> 
> and then specify what follows:
> 
> <rdf:Description rdf:about="#p1">
>   <foaf:maker rdf:resource="http://www.example.com/foaf.rdf#david">
> </rdf:Description>
> 
> <rdf:Description rdf:about="#p2">
>   <foaf:maker rdf:resource="http://www.example.com/foaf.rdf#david">
> </rdf:Description>
> 
> <rdf:Description rdf:about="#p3">
>   <foaf:maker rdf:resource="http://www.example.com/foaf.rdf#david">
> </rdf:Description>
>
> [snip]

The correct version of it is the following:

> [snip]
>
> 1  <owl:Class rdf:ID="ResourceOnExampleDotOrg">
> 2    <owl:equivalentClass rdf:ID="p1">
> 3      <owl:Class>
> 4        <rdfs:subClassOf rdf:ID="p2">
> 5          <owl:Restriction>
> 6            <owl:onProperty  rdf:ID="p3" &wdr;includeHost" />
> 7            <owl:hasValue rdf:ID="p4">example.org</owl:hasValue>
> 8          </owl:Restriction>
> 9        </rdfs:subClassOf>
> 10     </owl:Class>
> 11   </owl:equivalentClass>
> 12 </owl:Class>
>
> [snip]
>
> <rdf:Description rdf:about="#p1">
>   <foaf:maker rdf:resource="http://www.example.com/foaf.rdf#david">
> </rdf:Description>
>
> <rdf:Description rdf:about="#p2">
>   <foaf:maker rdf:resource="http://www.example.com/foaf.rdf#david">
> </rdf:Description>
>
> <rdf:Description rdf:about="#p3">
>   <foaf:maker rdf:resource="http://www.example.com/foaf.rdf#david">
> </rdf:Description>
>
> <rdf:Description rdf:about="#p4">
>   <foaf:maker rdf:resource="http://www.example.com/foaf.rdf#david">
> </rdf:Description>
>
> [snip]

In other words, the owl:hasValue property has a rdf:ID "p4", and not
"p3" (this is the rdf:ID of owl:onProperty). Consequently, we need an
additional rdf:Description about "p4".

Sorry for the typo.

Andrea

[1]http://lists.w3.org/Archives/Public/public-powderwg/2007Nov/0034.html
Received on Friday, 30 November 2007 10:27:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:42:12 GMT