Issue 6289: Multiple target namespaces in Wsdl File (wsdlcorba-ftf) Source: (Mr. Tom Rutt, nobody) Nature: Uncategorized Issue Severity: Summary: A WSDL description can contain multiple namespaces, including: - the description can have its own target namespace - the description can use wsdl: import to import a wsdl namespace - zero or moer schema in the types section has a target namespace (which is allowed, by WS-I profile, to be same as target namespace for the wsdl description - The schema in a types section can use xsd:import to import multiple namespaces. The current wsdl to corba inteworking spec only discusses the first namespace in the above list. The specification needs to clarify that each of the multiple namespaces in the wsdl description needs to be mapped to its own IDL module (using the same naming algorithm as currently specified for the wsdl target namespace) Propose solution: Amend the specification to map each namespace in the wsdl description to its own IDL module. Resolution: Close with new text mapping each target namespace to its own IDL module Revised Text: Change in 6.3.1 the first sentence: “ An IDL module is generated for each WSDL file. “ to the following: “ A WSDL document may contain several different target namespaces associated with WSDL and XML constructs which are translated to corresponding IDL constructs. A WSDL description can contain multiple namespaces, including: - the wsdl:definitions element can have its own target namespace - the wsdl:definition can use wsdl:import to import a wsdl namespace - zero or more schema in the types section each have a target namespace (which is allowed, by WS-I profile, to be same as target namespace for the wsdl description - The schema in a types section can use xsd:import to import multiple namespaces. “ Before the example add the following: “ Using the same algorithm as specified above to map from the target namespace value to an IDL module name and type prefix, the mapping from WSDL to IDL shall use a separate IDL module for each of the target namespaces which contain constructs which are mapped to IDL constructs. “ Actions taken: October 6, 2003: received issue March 10, 2004: closed issue Discussion: End of Annotations:===== te: Mon, 06 Oct 2003 10:03:04 -0400 From: Tom Rutt Reply-To: tom@coastin.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en To: wsdlcorba-ftf@omg.org, issues@omg.org, Juergen Boldt Subject: Multiple target namespaces in Wsdl File - New Issue Here is another new issue: A WSDL description can contain multiple namespaces, including: - the description can have its own target namespace - the description can use wsdl: import to import a wsdl namespace - zero or moer schema in the types section has a target namespace (which is allowed, by WS-I profile, to be same as target namespace for the wsdl description - The schema in a types section can use xsd:import to import multiple namespaces. The current wsdl to corba inteworking spec only discusses the first namespace in the above list. The specification needs to clarify that each of the multiple namespaces in the wsdl description needs to be mapped to its own IDL module (using the same naming algorithm as currently specified for the wsdl target namespace) Propose solution: Amend the specification to map each namespace in the wsdl description to its own IDL module. -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@fsw.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133 Date: Wed, 15 Oct 2003 14:09:56 -0400 From: Tom Rutt Reply-To: tom@coastin.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en To: wsdlcorba-ftf@omg.org Subject: Issue 6289 proposal for wordsmith here is the last proposal for wordsmith. I will send a vote out with all issue resolutions this friday. Tom Rutt -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@fsw.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133 Issue 6289: Multiple target namespaces in Wsdl File (wsdlcorba-ftf) Click here for this issue's archive. Source: Fujitsu (Mr. Tom Rutt, tom@coastin.com) Nature: Uncategorized Issue Severity: Summary: A WSDL description can contain multiple namespaces, including: - the description can have its own target namespace - the description can use wsdl: import to import a wsdl namespace - zero or moer schema in the types section has a target namespace (which is allowed, by WS-I profile, to be same as target namespace for the wsdl description - The schema in a types section can use xsd:import to import multiple namespaces. The current wsdl to corba inteworking spec only discusses the first namespace in the above list. The specification needs to clarify that each of the multiple namespaces in the wsdl description needs to be mapped to its own IDL module (using the same naming algorithm as currently specified for the wsdl target namespace) Propose solution: Amend the specification to map each namespace in the wsdl description to its own IDL module. Resolution: Close with new text mapping each namespace to its own IDL module Revised Text: Change in 6.3.1 the first sentence: “ An IDL module is generated for each WSDL file. “ to the following: “ A WSDL document may contain several different target namespaces associated with WSDL and XML constructs which are translated to corresponding IDL constructs. A WSDL description can contain multiple namespaces, including: - the wsdl:definitions element can have its own target namespace - the wsdl:definition can use wsdl:import to import a wsdl namespace - zero or more schema in the types section each have a target namespace (which is allowed, by WS-I profile, to be same as target namespace for the wsdl description - The schema in a types section can use xsd:import to import multiple namespaces. “ Before the example add the following: “ Using the same algorithm as specified above to map from the target namespace value to an IDL module name and type prefix, the mapping from WSDL to IDL shall use a separate IDL module for each of the target namespaces which contain constructs which are mapped to IDL constructs. “ Actions taken: