Re: EndpointRefs-47

Henry Thompson writes:

> The suggestion made at the f2f, as I understood it, was to 
> allow only the prefixes which were bound in the WSDL 
> description identified by the primary URI, i.e. http://example.
> com/fabrikam/acct.

This seems to make the association of EPRs to URIs dependent on a 
particular WSDL file.  While it's true that many users of WSA will also 
use WSDL, I don't think that's required, and I don't think it should be 
required. 

The specific implication of your proposal seems to be that the EPR:

<wsa:EndpointReference xmlns:p="http://example.com/FabrikamRefParms">
  <wsa:Address>
    http://example.com/fabrikam/acct
  </wsa:Address>
  . . .
  <wsa:ReferenceParameters>
    <p:CustomerKey>
      412
    </p:CustomerKey>
  </wsa:ReferenceParameters>
</wsa:EndpointReference>

maps to:

    http://example.com/fabrikam/acct?fabrikam:CustomerKey=412

(note the switch of prefix on customer key) iff both ends of the 
connection agree that there's a wsdl file establishing the prefix 
association from frakam: to http://example.com/FabrikamRefParms.  You wind 
up pretty close to a situation where the only actor that really 
understands the URI is the server that minted it, in which case it's not 
clear why globally unique  naming of the parameters is of great value at 
all.  If the server knows the WSDL, then presumably it can use:

    http://example.com/fabrikam/acct?parm1=412

since it knows that the WSDL calls for only one parameter anyway. 

I presume that the WSA folks are using globally unique parameter names for 
a reason, and I'm not yet convinced that grounding the URI mappings in a 
WSDL file is appropriate. 

Noah

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------








ht@inf.ed.ac.uk (Henry S. Thompson)
10/20/05 04:38 AM
 
        To:     noah_mendelsohn@us.ibm.com
        cc:     "David Orchard" <dorchard@bea.com>, www-tag@w3.org
        Subject:        Re: EndpointRefs-47


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

noah_mendelsohn writes:

> Henry Thompson asks:
>
>> Why not use the following URI to identify that endpoint:
>> 
>>   http://example.com/fabrikam/acct?fabrikam:CustomerKey=412

> I feel like I'm missing something.  This proposal seems to take the 
> namespace prefix, which has almost no semantic significance in the EPR, 
> and makes it the qualifier for the query string parameter in the URI.>

The suggestion made at the f2f, as I understood it, was to allow
only the prefixes which were bound in the WSDL description identified
by the primary URI, i.e. http://example.com/fabrikam/acct.

ht
- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of 
Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged 
spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDV1d0kjnJixAXWBoRAjNmAJ4qLsHG5/6digUKgCl04bwTJDH13ACdGBIX
ct6YYI1lgJSFyD7uhbWbDv4=
=xsog
-----END PGP SIGNATURE-----

Received on Thursday, 20 October 2005 14:43:26 UTC