W3C home > Mailing lists > Public > public-powderwg@w3.org > June 2008

Re: PROPOSAL to allow multiple descriptor sets in DRs

From: Phil Archer <parcher@icra.org>
Date: Wed, 11 Jun 2008 11:08:54 +0100
Message-ID: <484FA436.2040704@icra.org>
To: Public POWDER <public-powderwg@w3.org>



Smith, Kevin, (R&D) VF-Group wrote:
> HI Phil,
> 
> +1 from me - isn't this another way of doing packages, as we used to
> call them? 

Exactement monsieur.

Not only that, you know POWDER looks more and more like RDF-CL every 
day... ;-)

P


> -----Original Message-----
> From: public-powderwg-request@w3.org
> [mailto:public-powderwg-request@w3.org] On Behalf Of Phil Archer
> Sent: 11 June 2008 10:14
> To: Public POWDER
> Subject: PROPOSAL to allow multiple descriptor sets in DRs
> 
> 
> I've been looking at the implications of allowing more than one
> descriptor set (and tagset) within a DR and can't find a reason to limit
> their cardinality to one - which is probably good.
> 
> The use case for this would be where one organisation is creating DRs
> from different (knowledge) domains. To give a real world example, FOSI
> is likely to be launching its own trustmark later this year,
> independently of the usual ICRA stuff so we might well have a Web site
> that needed, say, a different ICRA label for different sections but the
> same FOSI trustmark across the whole site - hang on - er, that would
> apply to our own site, so how's this (note the use of the ordered list):
> 
> <ol>
>    <dr>
>      <iriset>
>        <includehosts>fosi.org</includehosts>
>        <pathstartswith>/associates</pathstartswith>
>      </iriset>
> 
>      <descriptorset src="#someNudity" />
>      <descriptorset src="#FOSItrustmark" />
>    </dr>
> 
>    <dr>
>      <iriset>
>        <includehosts>fosi.org</includehosts>
>      </iriset>
> 
>      <descriptorset src="#noNudity" />
>      <descriptorset src="#FOSItrustmark" />
>    </dr>
> </ol>
> 
> To process either DR you'd fetch the two descriptor sets identified in
> the src attributes and apply them all to whatever your candidate
> resource was. So allowing multiple descriptor sets allows you to mix and
> match them within a DR - something I recall talking to Dave/Segala about
> in the past as being something that would be useful.
> 
> It works in POWDER-S too.
> 
> Each of those descriptor sets would create an OWL class with an nodeID
> of descriptorset_x and the sub class relationship would be
> 
> <owl:Class rdf:about="#iriset_1">
>    <rdfs:subClassOf rdf:resource="#descriptorset_1"/>
>    <rdfs:subClassOf rdf:resource="#descriptorset_2"/> </owl:Class>
> 
> Look OK to everyone?
> 
> Phil.
Received on Wednesday, 11 June 2008 10:09:40 GMT

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