- From: Amy Lewis <alewis@tibco.com>
- Date: Thu, 17 Jul 2003 09:52:27 -0400
- To: Michael Rowley <mrowley@bea.com>
- Cc: www-ws-desc@w3.org
Dear Michael, On Wed, 16 Jul 2003 17:21:06 -0400 Michael Rowley <mrowley@bea.com> wrote: > Great example. Now assume that Ma & Pa want to advertize a URI for > subscribing to their service _without_ implying the binding that will > be used in the URI. How do they do that? You obviously can't send > out any of the soap:address locations, since they imply a transport. > You can't send the URI of the "ma-pa-market-service" element, since > that is for more than one interface. Seems you would need to send out > two URIs -- the one for "ma-pa-market-service" and the one for the > "ma-pa-market-admin" interface. Two URIs are necessary in order to > refer to the most useful concept that is provided by WSDL: a reference > > to a service independent of the mechanism used to communicate with it. Why is that the most useful concept? What can I do with these two URIs? If I want to subscribe ... I need a URL. No? Amy! -- Amelia A. Lewis Architect, TIBCO/Extensibility, Inc. alewis@tibco.com
Received on Thursday, 17 July 2003 09:51:23 UTC