W3C home > Mailing lists > Public > www-rdf-interest@w3.org > September 2004

RE: Modelling rdfs:range(s) in PRISM

From: Victor Lindesay <victor@schemaweb.info>
Date: Thu, 2 Sep 2004 10:03:23 +0100
To: <www-rdf-interest@w3.org>
Message-ID: <000001c490cb$b498f360$1c497ad5@vicsoft.co.uk>

Tony Hammond wrote regarding the new PRISM schema:

> Hi Richard:
> 
> So you would suggest having (scuse any text wrapping)

> <!-- "AuthorityReferenceConstraint" class -->
> <owl:Class rdf:ID="AuthorityReferenceConstraint">
>   <owl:unionOf rdf:parseType="Collection">
>     <owl:Class rdf:about="#AuthorityReference" />
>     <owl:Class 
> rdf:about="http://www.w3.org/2000/01/rdf-schema#Literal" />
>   </owl:unionOf>
> </owl:Class>
> 
> <!-- prism:category -->
> <rdf:Property rdf:about="category">
> <rdfs:label xml:lang="en-US">category</rdfs:label>
> <rdfs:comment xml:lang="en-US">The nature or genre of a 
> resources intellectual content.</rdfs:comment> 
> <rdfs:isDefinedBy rdf:resource=""/> <rdfs:range 
> rdf:resource="#AuthorityReferenceConstraint"/>
> </rdf:Property>

Or maybe embed an anonymous class within the rdfs:range. This would
avoid explicitly defining the constraint class.

<rdf:Property rdf:about="category">
<rdfs:range>
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<owl:Class rdf:about="#AuthorityReference" />
<owl:Class rdf:about="http://www.w3.org/2000/01/rdf-schema#Literal" />
</owl:unionOf>
</owl:Class>
</rdfs:range>
</rdf:Property>

An example using rdfs:domain is in the Language Ref.
http://www.w3.org/TR/owl-ref/#domain-def
Received on Thursday, 2 September 2004 09:10:52 GMT

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