- From: Eric van der Vlist <vdv@dyomedea.com>
- Date: Fri, 23 Jan 2004 18:19:57 +0100
- To: www-tag@w3.org
On Fri, 2004-01-23 at 18:08, Jonathan Borden wrote:
>
> This is how we could do this in RDDL2:
> (assume namespace = http://example.org/namespace#)
> <div id="foo">
> <a rddl:nature="http://example.org/n1"
> rddl:purpose="http://example.org/p1" href="..."> ...</a>
> <a rddl:nature="http://example.org/n2"
> rddl:purpose="http://example.org/p2" href="..."> ... </a>
> <a rddl:nature="http://example.org/n3"
> rddl:purpose="http://example.org/p3" href="...">... </a>
> </div>
>
> which using the ancestor-or-self::*[@id] XSLT pattern could be used to
> create the following subject URU: <http://example.org/namespace#foo>.
>
> This fits along the general practice of using id="foo" as a way of
> specifying what a fragment identifier identifies (in HTML)
But this still doesn't let you define the source of the RDDL link
independently of XHTML links like that was possible in RDDL 1.0.
The real good thing about RDDL 1.0 is that <rddl:resource/> are
fragments that can have a meaning by themselves: they can embed a piece
of rich documentation about the resource that they describe and they can
be very useful for creating modular vocabularies.
Eric
--
Rendez-vous à .doc 2004.
http://www.lra.fr/docarchi/html/sem_congr.html
Upcoming XML schema languages tutorial:
- Santa Clara -half day- (15/03/2004) http://masl.to/?J24916E96
------------------------------------------------------------------------
Eric van der Vlist http://xmlfr.org http://dyomedea.com
(ISO) RELAX NG ISBN:0-596-00421-4 http://oreilly.com/catalog/relax
(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
------------------------------------------------------------------------
Received on Friday, 23 January 2004 12:20:00 UTC