- From: Andrea Perego <andrea.perego@uninsubria.it>
- Date: Thu, 06 Dec 2007 23:32:06 +0100
- To: Public POWDER <public-powderwg@w3.org>
Hi, Stasinos.
> [snip]
>
> Or s'thing like declaring an RDF meta-property that has owl:Class as
> it's domain:
>
> <rdf:Property rdf:ID="includesHost">
> <rdfs:domain owl:Class"/>
> <rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
> </rdf:Property>
>
> <owl:Class rdf:ID="FOSIchildSafe">
> <rdfs:subClassOf wdr:ChildSafe/>
> <wdr:includeHost>example.org^^xsd:string</includesHost>
> </owl:Class>
Well, this allows me to ask you a new question.
In the POWDER vocabulary [1], we have defined the equivalent of the new
wdr:includeHost:
<owl:DatatypeProperty rdf:about="&wdr;includeHosts">
<rdfs:isDefinedBy rdf:resource="&wdr;" />
<rdfs:label xml:lang="en">include hosts</rdfs:label>
<rdfs:comment xml:lang="en">This property ...</rdfs:comment>
<rdfs:range rdf:resource="&wdrd;uriHostList" />
<rdfs:subPropertyOf rdf:resource="&wdr;addressRestriction" />
<rdfs:seeAlso rdf:resource="&group;#byURIcomp" />
</owl:DatatypeProperty>
The new definition should then be something like what follows:
<owl:DatatypeProperty rdf:about="&wdr;includeHost">
...
<rdfs:domain rdf:resource="&owl;Class" />
<rdfs:range rdf:resource="&xsd;string" />
...
</owl:DatatypeProperty>
You then say that the DR scope definition can be:
<owl:Class rdf:ID="FOSIchildSafe">
<wdr:includeHost>example.org</wdr:includeHost>
</owl:Class>
My question is: given that the wdr:includeHost property is defined as
above, is this equivalent or not to writing:
<owl:Class rdf:ID="ResourceOnExampleDotOrg">
<owl:equivalentClass>
<owl:Restriction>
<owl:onProperty rdf:resource="&wdr;includeHost" />
<owl:hasValue>example.org</owl:hasValue>
</owl:Restriction>
</owl:equivalentClass>
</owl:Class>
In other words, do we really need to use owl:Restriction?
Andrea
[1]http://www.w3.org/TR/powder-voc/wdr.rdf#includeHosts
Received on Thursday, 6 December 2007 22:27:26 UTC