W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > April 2002

Re: rdfs-constraining-containers, rdfs-container-membership-superProperty

From: Graham Klyne <Graham.Klyne@MIMEsweeper.com>
Date: Thu, 11 Apr 2002 17:13:47 +0100
Message-Id: <5.1.0.14.2.20020411171325.04115c20@joy.songbird.com>
To: "Jeremy Carroll" <jjc@hplb.hpl.hp.com>
Cc: <w3c-rdfcore-wg@w3.org>
Looks good.

Does this mean that rdfs:contains would be a superproperty of rdf:_1, 
rdf:_2, etc.?

#g
--

At 03:42 PM 4/11/02 +0200, Jeremy Carroll wrote:

>I suggest we resolve the rdfs-container-membership-superProperty by defining
>one:
>e.g. rdfs:contains
>
>
>I suggest we then declare rdfs-constraining-containers as out of scope on
>the basis that it can be addressed by DAML+OIL. All indications are that OWL
>will contrinue to address this issue.
>
>The DAML+OIL mantra is:
>
>
>
><daml:Restriction rdf:ID="ConstrainedContainer">
>   <rdfs:comment>
>     This is the class of resources all of
>     whose rdfs:contains edges point to a
>     resource of type eg:ElementsConstrainedToThisClass.
>     To have a Bag, a Seq or an Alt with such a constrained
>     declare the resource to have both type Bag and type
>     ConstrainedContainer.
>     Alternatively construct a new class that subclasses both
>     this class and the desired container class.
>   </rdfs:comment>
>   <daml:onProperty
>rdf:resource="http://www.w3.org/2000/01/rdf-schema#contains"/>
>   <daml:toClass
>rdf:resource="http://example.org/ElementsConstrainedToThisClass"/>
></daml:Restriction>
>
>Reference:
>http://www.daml.org/2001/03/daml+oil-walkthru#restrictions
>
>
>Jeremy

-------------------
Graham Klyne
<GK@NineByNine.org>
Received on Thursday, 11 April 2002 12:12:45 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 3 September 2003 09:47:25 EDT