W3C home > Mailing lists > Public > public-wai-ert@w3.org > March 2006

rdf-cl and wcl xg

From: <drooks@segala.com>
Date: Wed, 15 Mar 2006 14:46:08 +0000
Message-ID: <1142433968.441828b03d9d5@>
To: public-wai-ert@w3.org

Hi all,

Here is my long overdue action to let you all know about content labels (rdf-cl)
and to let you know whats happening over in the content label incubator group

For a quick summary of rdf-cl and its use cases check out the wclxg charter -

That should give you a good idea of the purpose of rdf-cl. Basically, it is an
rdf replacement for PICS.

The main similarity between RDF-CL and EARL is that both languages can be used
to make statements it is how these statements are implemented that the
differences lie...

In order to create a content label a vocabulary first needs to be defined. This
vocabulary contains all the statements that a content provider may want to make
on a specific topic. So, for example the vocabulary would define statement A as
being 'all images contain meaningful alternative text' and its value as being
boolean. The vocabulary (lets call is WCAG) can also define classifications
such a "A", "AA" & "AAA". This vocabulary would typically sit somewhere on its
creators web server so that it is publicly available.

Once the vocabulary is defined a content label can be created. Basically, what
happens is that you create file which declares a WCAG namespace (amongst
others) and then makes some statements. e.g. <WCAG:A>1</WCAG:A> states that
'all images contain meaningful alternative text' is true. If you fulfilled all
WCAG 1 checkpoints then you could also classify the label as being 'A'
compliant .

RDF-CL also provides the ability to apply different labels to different URLs. So
you can apply label#1 to all pages in www.somewhere.org excluding those in
www.somewhere.org/elsewhere and apply label#2 to www.somewhere.org/elsewhere.

For a more technical summary of rdf-cl QUATRO provides an excellent example -

In terms of what the xg group are doing at the moment we are fleshing out our
use cases and starting work on the requirements. Our aim is to have the
majority of work completed by the end of may in time for www2006 in edinburgh.

Received on Wednesday, 15 March 2006 14:47:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:53 UTC