- From: Asir Vedamuthu <asirv@webmethods.com>
- Date: Thu, 27 Jan 2005 10:25:50 -0500
- To: "'www-ws-desc@w3.org'" <www-ws-desc@w3.org>
[*** Re-sending this e-mail, for some reason, this e-mail disappeared. Apologize, if it shows up twice] Issue <quote> 2.1.1 "The components directly defined within a single Definitions component are said to belong to the same target namespace."-- what about included components in the same namespace? </quote> http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC52a Discussion Actually, Part 1, Section 2.1 is inconsistent on this topic: Section 2.1.1 The Definitions Component [1] - says that "The set of interfaces/binding/services/etc. available in the Definitions component include those that are defined within the component itself and those that are imported and/or included." Section 2.1.1 The Definitions Component [1] - declares that components belong to the same target namespace: "The components directly defined within a single Definitions component are said to belong to the same target namespace". Section 2.1.3 Mapping Definitions' XML Representation to Component Properties [2] - brings components from the included and imported namespaces: "{interfaces} The set of Interface components corresponding to all the interface element information items in the [children] of the definitions element information item, if any, plus any included or imported Interface components (see 4. Modularizing WSDL descriptions). {bindings} The set of Binding components corresponding to all the binding element information items in the [children] of the definitions element information item, if any, plus any included or imported Binding components (see 4. Modularizing WSDL descriptions). {services} The set of Service components corresponding to all the service element information items in the [children] of the definitions element information item, if any, plus any included or imported Service components (see 4. Modularizing WSDL descriptions)." Proposed Resolution Re-state in simple terms: the Description (LC43) Component is a container for Interface, Binding, Service, Element Declaration, Type Definition and Extensibility components. That's it. Include and import are at a different level, composition. This level is different from the component model. Composition is clearly answered in the mapping section. [1] http://www.w3.org/TR/2004/WD-wsdl20-20040803/#Definitions_details [2] http://www.w3.org/TR/2004/WD-wsdl20-20040803/#Definitions_Mapping Regards, Asir S Vedamuthu asirv at webmethods dot com http://www.webmethods.com/
Received on Thursday, 27 January 2005 16:43:53 UTC