W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > October 2005

Re: simple case of IRIs for Components in WSDL 2.0

From: Arthur Ryman <ryman@ca.ibm.com>
Date: Tue, 18 Oct 2005 10:13:58 -0400
To: Bijan Parsia <bparsia@isr.umd.edu>
Cc: David Orchard <dorchard@bea.com>, "Henry S. Thompson" <ht@inf.ed.ac.uk>, Jonathan Marsh <jmarsh@microsoft.com>, Pat Hayes <phayes@ihmc.us>, public-ws-desc-comments@w3.org, public-ws-desc-comments-request@w3.org
Message-ID: <OFBBE348BE.7AEC2339-ON8525709E.004C8687-8525709E.004E2C8F@ca.ibm.com>

Let me explain the XML Infoset versus Component thing.

A URI-Reference is a URI and a fragment.

If the URI is used to retrieve a WSDL document (as an XML Infoset) then 
the fragment refers to some element information item (EII). That is why we 
register the fragment syntax with the IANA media registration for 

If the URI is the namespace of a WSDL document then the fragment 
identifies a component in the WSDL component model for that namespace. We 
sometimes refer to this case as the component designator case.

The two cases are consistent when the namespace actually dereferences to 
the WSDL document, i.e. the EII maps to the component.

BTW, one thing I still don't understand is why the parens cause a parsing 
problem. The XPointer syntax results in balanced parens so it should be 
easy to parse, e.g. when the URI-Reference is the argument of some 
function call.

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca

Bijan Parsia <bparsia@isr.umd.edu> 
10/13/2005 04:13 PM

Pat Hayes <phayes@ihmc.us>
public-ws-desc-comments@w3.org, "Henry S. Thompson" <ht@inf.ed.ac.uk>, 
public-ws-desc-comments-request@w3.org, Jonathan Marsh 
<jmarsh@microsoft.com>, Arthur Ryman/Toronto/IBM@IBMCA, David Orchard 
Re: simple case of IRIs for Components in WSDL 2.0

Oh, and duh. WSDL is an XML thing. These fragments are being used to 
identify subresources of WSDL. That the *user* of them might not be XML 
is irrelevant.

So pointing to my papers was a bit of a red herring. Even if XPointer 
*is* an XML thing, it's an interface to an XML thing and this exactly 
what we're doing, supplying identifiers for parts of an XML (though I'm 
still confused about Infoset items vs. components) thing. See my 
quotation of the definition of "application".

Received on Tuesday, 18 October 2005 14:14:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:31:03 UTC