W3C home > Mailing lists > Public > semantic-web@w3.org > March 2005

Re: Announcement: RDF Content Labels

From: Phil Archer <phil.archer@icra.org>
Date: Thu, 31 Mar 2005 15:59:13 +0100
Message-ID: <007c01c53602$d6518b70$63601052@PHILXP>
To: "Benjamin Nowack" <bnowack@appmosphere.com>
Cc: <semantic-web@w3.org>

Hi Benjamin,

Thanks for looking at this and yes, you're right, unionOf and intersectionOf 
are classes, not properties - I'll amend the documentation accordingly. 
Also, it is easier on the eye and brain to call the classes unionRules and 
intersectionRules. Ditto "applyLabel" rather than hasLabel. Hmmm... but, as 
you say, this is only easier of you're not a machine.

hasLabel makes more sense to the wetware perhaps when we have a simple 
"rule" that doesn't include any unions or intersections. In this case we get

  <label:rules rdf:parseType="Collection">
      <label:hasLabel rdf:resource="#label2" />

i.e. the guestbook gets label 2 - nice and easy and, to be honest, a more 
likely rule in the real world.

Incidentally, I was pleased to see one of our beta testers easily 
incorporated a content label into his existing RDF. See 
http://www.six27.com/sitewide.rdf. Dublin Core, Creative Commons and ICRA 
all in one little file. Nice.


----- Original Message ----- 
From: "Benjamin Nowack" <bnowack@appmosphere.com>
To: "Phil Archer" <phil.archer@icra.org>
Cc: <semantic-web@w3.org>
Sent: Saturday, March 26, 2005 5:17 PM
Subject: Re: Announcement: RDF Content Labels

Hi Phil,

just had a quick glance at the content labels docs,
looks very interesting. I may be able to send more
detailed comments when I find the time to read the
whole stuff, just one thing I spotted:

- label:unionOf/intersectionOf are described as
  properties, but I think the way they are used
  inside an rdf collection makes them a class,
      <label:rules rdf:parseType="Collection">
         <label:unionOf rdf:ID="rule1">
            <label:hasLabel rdf:resource="#label_2" />
         <label:intersectionOf rdf:ID="rule2">
            <label:hasLabel rdf:resource="#label_2" />
would ceate the (pseudo-)triples
   label:Ruleset label:rules _:list1
   _:list1 rdf:first #rule1
   #rule1 rdf:type label:unionOf
   _:list1 rdf:rest _:list2
   _:list2 rdf:first #rule2
   #rule2 rdf:type label:intersectionOf
   _:list2 rdf:rest rdf:nil

not sure how to model this though, maybe just
      <label:rules rdf:parseType="Collection">
         <label:UnionRule rdf:ID="rule1">
            <label:hasLabel rdf:resource="#label_2" />
         <label:IntersectionRule rdf:ID="rule2">
            <label:hasLabel rdf:resource="#label_2" />
to say that rule1 needs one condition to match,
and rule2 all conditions in order to apply another

(Maybe changing "hasLabel" to "applyLabel" could
make the difference between conditions (matching URI)
and effects (change label) more obvious, but of course
that's only what a non-machine would say.. ;)


Benjamin Nowack

Kruppstr. 100
45145 Essen, Germany

On 23.03.2005 16:35:39, Phil Archer wrote:
>Dear all,
>Those at the second day of the SWIG meeting in Boston recently have had a
>preview of this. Various people and organisations have been working on a
>method of grouping URIs together and linking them to a common description,
>what we call a content label. This is, I know, potentially confusing since
>we're not talking about rdfs:label.
>ICRA's use case is that this can supersede PICS in offering a way for
>content providers to label their content in terms of the various things
>parents in different parts of the world don't want their children to see
>(types of nudity, sexual material, violence, language, racism etc.). There
>are others however - DC and Creative Commons information, for instance, 
>generally apply to more than one of your resources. The mobile industry is
>looking at a "Mobile OK" label for resources that work well on mobile
>The recent thread on this interest group between Benjamin Nowak and Stephen
>Rhoads (SemWeb Non-Starter -- Distributed URI Discovery) might perhaps be
>relevant here too since our aim is to make it possible to parse an RDF
>instance that contains descriptions for a whole bunch of URIs. Our solution
>is to create a simple ruleset that takes a URI as an input and gives a
>description as output. In essence, the system amounts to:
>1. If you're on any of the following hosts, the default content label is
>2. There now follows an ordered sequence of regular expressions for you to
>match against your target URI. As soon as you get a match, take the
>associated label.
>3. If no match, thre default description applies.
>We offer machanisms that distinguish between a content label as a class 
>has descriptive properties, a content label that delivers management
>information (like DC and CC stuff), and a class that serves a description 
>itself, such as "PG-13".
>Use cases and general information is at [1] with a description of the 
>itself at [2]. I have applied the system to ICRA's use case and created 
>this group might call an RDF generator at [3] that allows you to "label 
>website" and a basic tool to test those labels at [4]. The latter is very
>much under development and will make full use of SPARQL in due course and
>may do other fancy things - as ever, it's all about time and priorities!
>Incidentally, Piggy Bank [5] shows up the content labels nicely, but, being
>unaware of the rule methods we've proposed, shows all available labels
>without knowing which label applies to the particular page you're on.
>Comments more than welcome.
>Thank you
>Phil Archer
>[1} http://www.w3.org/2004/12/q/doc/rdf-contentlabels.html
>[2] http://www.w3.org/2004/12/q/doc/content-labels-schema.htm
>[3] http://www.icra.org/RDF/label/
>[4] http://www.icra.org/RDF/label/tester/
>[5] http://simile.mit.edu/piggy-bank/
Received on Thursday, 31 March 2005 15:03:43 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:44:52 UTC