W3C home > Mailing lists > Public > www-tag@w3.org > January 2003

Re: RDDL proposal from Sandro Hawke

From: Sandro Hawke <sandro@w3.org>
Date: Fri, 03 Jan 2003 19:50:06 -0500
Message-Id: <200301040050.h040o6X25955@wadimousa.hawke.org>
To: Tim Bray <tbray@textuality.com>
cc: www-tag@w3.org

> Sandro Hawke wrote:
> > Let's just use the existing "rel" and "type" attributes on a-href
> > elements.  
> 
> This is elegantly simple and minimal, but has one shortcoming: there's 
> no obvious way to determine which href= is that of the purpose and which 
> is that of the nature.  I.e. I want to fetch a RDDL and say "find me a 
> related resource which is an XML Schema and is appropriate for run-time 
> validation"  What's the solution to that?  Do we have to have just one 
> reserved attribute? -Tim

I'm sorry, I don't understand.  "A" elements have optional "rel" and
"type" attributes, and it seems to me that "rel" matches Purpose
(which is a relation between the namespace and the other thing) and
"type" matches Nature (which is intrinsic to the other thing).   And
of course "href" is there to actually identify the other thing.

So in your example, you could search the RDDL document for "A"
elements with type=(XML Schema) and rel=(run-time validation), then
follow the href.  If anything has the right rel but no type given, you
could try a content-negotation GET and see if you can get an XML
Schema.

Does that make more sense?

    -- sandro
Received on Friday, 3 January 2003 19:54:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:14 GMT