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

Re: abstractComponentRefs-37 & RDDL

From: Robin Berjon <robin.berjon@expway.fr>
Date: Mon, 31 Mar 2003 11:04:53 +0200
Message-ID: <3E8804B5.7010300@expway.fr>
To: Tim Bray <tbray@textuality.com>
Cc: WWW-Tag <www-tag@w3.org>

Tim Bray wrote:
> OK, now suppose I want to identify (using Jonathan's example) 
> "operation(TicketAgent/listFlights)" inside the WSDL.  I'm wondering if 
> you could bridge through the RDDL to get there with something along the 
> lines of
> 
> http://example.com/ns/foo.rddl#wsdl/operation(TicketAgent/listFlights)
> 
> So the stuff after the "#wsdl/" is treated as a fragment identifier in 
> the related-resource which the link identified by #wsdl points at.  This 
> could all be done perfectly legally by registering a media-type for RDDL 
> and saying this is how fragments behave.  And in fact, it is fairly true 
> to the basic semantic of #fragments, namely you have to fetch the RDDL 
> to find out what the #wsdl points at so you can figure out what to do 
> with the rest of the fragment.  On the other hand, that '#' jammed in 
> the middle of of the URI is perhaps troubling.
> 
> This is no more than a V.001 strawman, but at this point I kind of like 
> it.  Feedback?

I like it as well, but why not be a little more XPointerish? For instance:

http://example.com/ns/foo.rddl#rddl(wsdl)wsdl(operation(TicketAgent/listFlights))

isn't very different but (given some simple definitions of new XPointer schemes) 
is XPointer compatible.

The rddl(ID) scheme is defined as returning/setting the evaluation context to 
the document pointed to by the XLink on the element identified as ID, but is 
considered to not identify a subresource (yes, this is where this is hackish). 
The wsdl() scheme contains the syntax that the WSD WG settles on.

-- 
Robin Berjon <robin.berjon@expway.fr>
Research Engineer, Expway        http://expway.fr/
7FC0 6F5F D864 EFB8 08CE  8E74 58E6 D5DB 4889 2488
Received on Monday, 31 March 2003 04:07:04 GMT

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