Re: component designators spec - where art thou?

Sanjiva,

I'm not sure what the SHOULD refers to, but the fragment syntax I proposed 
now is consistent with Web Architecture since we recommended that 
namespace URI's point to WSDL documents. The way this works is as follows:

1. register the new content type with IANA. in our case it is 
application/wsdl+xml
2. register/describe the new fragment syntax with the new content type 
registration

Now the algorithm is as follows for intertrepping a URI such as 
namespace-uri#fragment

1. dereference namespace-uri and get a resource whose content type is 
application/wsdl+xml
2. intepret the fragment as defined by application/wsdl+xml - this 
idenitfies a component

The fragment syntax I proposed was compliant with the XPointer Framework. 
The syntax has to be updated to reflect the current state of the spec, but 
the general form is component-type(name-path) where component-type is 
interface, binding, operation, etc, and name-path is the hierarchical path 
formed by the NCNames of the component and its parents, e.g. 
operation(myInterface/myOperation).

Arthur Ryman,
Rational Desktop Tools Development

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
intranet: http://w3.torolab.ibm.com/DEAB/



"Sanjiva Weerawarana" <sanjiva@watson.ibm.com> 
Sent by: www-ws-desc-request@w3.org
03/15/2004 10:31 AM

To
<www-ws-desc@w3.org>
cc

Subject
component designators spec - where art thou?







I'd like to fulfill the following:

EDTODO    2004-03-04: Editors to add back the WSDL Component Designators
                      back to the spec as SHOULD.

Arthur?


Sanjiva.