- From: Mark Baker <distobj@acm.org>
- Date: Mon, 22 Jul 2002 14:37:52 -0400
- To: Hao He <Hao.He@thomson.com.au>
- Cc: www-ws-arch@w3.org
Hi Hao, A quick comment on the architectural elements. As WSDL isn't a complete system, it's hard to extract architectural elements from it because it may not have any. But I think you've done a very good job, especially with Connectors. Here's my thoughts; On Mon, Jul 22, 2002 at 04:19:34PM +1000, Hao He wrote: > Components: requestor and provider Technically these aren't components, but are instead roles that a component could play. I believe that in the context of the implicit architecture of SOAP 1.1 + WSDL, a web server (origin, gateway, or proxy) is still a component, as it is the thing to which the connector is attached. > Connector: ports I'd actually say that the stubs and skeletons (are people doing skeletons with WSDL?) are the connectors. Of course, the ports define connector semantics for any system that uses WSDL, so it's good that you identified this. > Data element: typed data item, messages The only data element I could think of was a URI, which WSDL is used to describe the interface of. Thanks. MB -- Mark Baker, CTO, Idokorro Mobile (formerly Planetfred) Ottawa, Ontario, CANADA. distobj@acm.org http://www.markbaker.ca http://www.idokorro.com
Received on Monday, 22 July 2002 14:25:50 UTC