W3C home > Mailing lists > Public > www-rdf-interest@w3.org > July 2003

RE: rdfs:domain for OO class properties

From: Leo Sauermann <leo@gnowsis.com>
Date: Tue, 15 Jul 2003 11:22:57 +0200
To: <www-rdf-interest@w3.org>
Message-ID: <000001c34ab2$ae1d8470$0501a8c0@ZION>

I had the same problem with dc:title and dc:creator like predicates.
(dc = dublincore)

musicbrainz used the dc: namespace to define its author relation. when I
did a RDF scheme out of this, I did a domain definition that caused

<rdf:Property rdf:about="&dc;creator"
	<rdfs:domain rdf:resource="&mm;Album"/>
	<rdfs:domain rdf:resource="&mm;Track"/>
	<rdfs:range rdf:resource="&mm;Artist"/>

Dave Reynolds read it and suggested the following solution in
"Second, your declaration of DC:title is saying that it applies to
objects which
are type mm:Album AND type mm:Artist AND type mm:Track - whereas I
assume you
really mean OR. That effect could be achieved in RDFS by creating a new
mm:HasTitle and saying that mm:Album etc are sub-classes of it."

RDF Schema Validator - Validate RDF triples

> -----Original Message-----
> From: www-rdf-interest-request@w3.org 
> [mailto:www-rdf-interest-request@w3.org] On Behalf Of 
> Francesco CannistrÓ
> Sent: Tuesday, July 15, 2003 10:54 AM
> To: Pedro Assis in Oporto; www-rdf-interest@w3.org
> Subject: Re: rdfs:domain for OO class properties
> Hi
> > Assuming that the following interpretation of the property domain is
> > correct, what should be the right procedure (formally!?) to 
> describe in
> > RDF a property which can be applied to several distinct classes?
> >
> > The context is: The RDF properties domain (rdfs:domain) are globally
> > defined and the conjunction of domains, i.e. more than one 
> statement for a
> > property domain, leads to the class domain that is of both, (in the
> > case of 2 domain statements) types.
> >
> > Well, one solution is to create different properties, i.e. 
> with different
> > names, to describe the same behavior (hum, don't like 
> that). Another one
> > is to declare the domain as a collection of alternate 
> classes, i.e. all
> > the members of such collection (not sure about this one). 
> But, necessarily
> > this issue has arise many times before, so it must have a 
> proper solution.
> Another one (the rignt one I think) is to use OWL that is 
> going to be born
> just to let do things like this.
> Regards
Received on Tuesday, 15 July 2003 05:21:03 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:07:46 UTC