The section "ValueType" needs to describe inheritance. The order between member (not inherited, inherited, indirectly inherited) must be defined. // IDL valuetype sampleY : sampleX

; // XSD <xsd:complexType name="sampleY"> <xsd:sequence> <xsd:element name="a" maxOccurs="1" minOccurs="1" type="xsd:short"/> <xsd:element name="b" maxOccurs="1" minOccurs="1" type="xsd:int"/> <xsd:element name="c" maxOccurs="1" minOccurs="1" type="xsd:string"/> </xsd:sequence> <xsd:attribute name="id" type="xsd:ID" use="optional"/> </xsd:complexType>

Agree to add description of value type inheritance

I have some notes and questions to CORBA IDL to WSDL mapping. 1. corba.wsdl contains xsd:url type. But this type is not defined in schema. There is only xsd:anyURI. I think corba.wsdl is not valid wsdl!!! 2. TypeCode is mapped to url to wsdl document and type name. Why TypeCode is not mapped to QName? 3. Any is mapped to CORBA:TypeCode and xsd:any. I think better is mapping to xsd:any. Type is defined by xsi:type attribute in soap message. 4. Object reference is mapped to sequence of url. But this urls are urls to CORBA interfaces. It is not usefull for me. I neednot return corba reference (it is irrelevant for soap client), I need to return address of webservice or whole EndpointReference from ws-addresing, which transform soap messages to calls on this CORBA::reference. 5. Contact information for this specification mars@omg.org is not valid.

close without change

Section 1.2.8.2
In the example for attributes mapping.
The get accessor maps to an operation with only an output message. It seems like a notification operation according to WSDL specification. But the semantics of attribute accessors should be request-response .So a get accessor should be mapped to a couple of messages.
Proposed solution :
Define the incoming message as a message without any parameter as the following:
<message name="MyAttrs._get_strAttr" />
<message name="MyAttrs._get_strAttrResponse" >
<part name="_return" type="xsd:string"/>
</message>
¡­
<portType name="MyAttrs" >
<operation name="_get_strAttr" >
<output message="tns:MyAttrs._get_strAttrResponse"/>
<fault message=¡±tns:CORBA.SystemException¡±/>
</operation>

Accept proposal from source

Section 1.2.8.2
Also, in the example for operation mapping.
<portType name="SomeInterface" >
<operation name="bar" >
<input message="tns:SomeInterface.bar"/>
<output message="tns:SomeInterface.barResponse"/>
<fault message=¡±tns:CORBA.SystemException¡±/>
</operation>
</portType>
Here defines the fault message, yet its type is not CORBA.SystemExceptionMessage defined ahead, but CORBA.SystemException, which is defined as a complextype.
Proposed solution: Maybe the following is right:
<fault message=¡±tns:CORBA.SystemExceptionMessage¡±/>

Accept proposal from source

Section 1.2.8.2
In the example:
<message name="CORBA.SystemExceptionMessage" >
<part name="_return" type="CORBA.SystemException"/>
</message>
CORBA Specification says that CORBA Exception cannot be passed as paramters or return value. But the example seems to ¡°return¡± a SystemException.
Proposed solution: Maybe the example should be defined as the following according to the exception mapping rules:
<message name="CORBA.SystemExceptionMessage" >
<part name="exception" type="CORBA.SystemException"/>
</message>

Close with no change. While confusing, the use of "_return" for the name is not invalid

CORBA fixed types are mapped to the XML Schema "decimal" type (not "integer")

And the element "restriction" of the map becomes : <xsd:restriction base="xsd:decimal">

The xsd:integer type have a facet fractionDigits fixed to 0.

: Accept solution proposed by source

The mapping does not state what value should be used for the default
case.

Proposed Resolution:
Add text stating that any valid value for the discriminant, other than
those used
in the union definition, can be inserted for the default case.

Accept proposal from source

Section 1.2.7.10 ­
Only public state members are mapped. Since use of the Dynamic Any api
allows access to both the private
and public members, this restriction was challenged by the AB reviewer
as unwarranted.
Also the sentence "For example, DII/DSI bridges will be unable to
process value types." is not justified.

The dynamic ANY api can be used to access value type state members in a
DII/DSI based gateway.
If private state cannot be represented, an input value type parameter
which has private state will not be mapped to the IDL server.

Proposed Solution:
Delete offending sentence about dynamic gateways.
Unless the private member restriction can be justified, change the spec
to map both private and public value type state members.

Remove the restriction of not mapping Private state members

section 1.2.8.2 , 1.2.8.4 and 1.2.8.5 - In all the Example WSDL, the
target namespace in definitions and the namespace in import using URL
"http://tempuri.org/anExample/.." do not seem correct.

Proposed Resolution: fix the example after resolving the Type prefix FTF

issue on namespace and module name uniqueness.

Fix the examples to use the correct target namespace url

Section 1.2.7.10.3 - need to represent value type in IDL sequence as an
IdRef/value choice.

Proposed Resolution:
fix spec to use the idRef/Value choice for sequence<valueType>.

see above

section 1.2.4 - The sentence "The most significatn is that XML flattens
the constructed namespace to a single targeted namespace when an XML
schema is imported." does not seem quite correct. Avoiding a large
number of files for the wsdl processor to deal with is a major reason
cited by the submitters.

Proposed Solution: Replace the offending sentence, with: "Having a
separate namespace for each imported module results in a large number of

files for the WSDL processor to deal with when constructing a gateway."

Agree to editorial fix

Section 1.2.3 - there is an inconsistency, in that the documentation
schema for the repository ID dos not include the version of the mapping,

as included in the URL source documentation schema.
Knowing what version of the IDL to WSDL mapping produced the WSDL is
important for gateway design.

Proposed Resolution: add mapping version to the respositoryID
documentation schema.

Add mapping version to the repositoryID documentation schema

Section 1.2.3 - need to have appropriate text to describe the nature of
the source "hint". Examples might be included, using filenames.

Proposed Resolution: FTF should determine appropriate text.

The nature of the hint can remain an implementation specific matter

Section 1.2.2.1 -
tns is a single namespace for all mapped IDL from the entire corba
world.
The module names for IDL across this vast namespace, need to be
sufficiently qualified with pre-fixes (such as Type ID, or Pragma
Prefix) to avoid module name collisions.

Proposed Resolution: FTF needs to determine appropriate prefixes or
namespaces to assure module name uniqueness in the generated WSDL

see above

duplicate of issue # 9602

In Corba to WSDL/SOAP Interworking Spec:
In section 1.2.x there are several typographical errors in the
XML schema productions for the examples. Several schema productions
could not validate as written.

Proposed Resolution: correct the typographical errors to allow the xml schema productions to validate.
Revised Text:
Change G1: to make specification text consistent with the validated machine readable example files, in
http://www.omg.org/cgi-bin/doc?ptc/04-10-12
---------------------------------
In 1.2.1.1 change the namespace prefixes:
"wsdl" to "w" and "SOAP-ENC" to "soapenc"

Throughout the document, wherever soap encoding array is used:
Change:
"
SOAP-ENC
"
To:
"
soapenc
"
And:
Change:
"
wsdl:
"
To:
"
w:
"
And
Change:
"[]"
To:
""
--------------------------------end change G1

In 1.2.6.1, apply change G1
And:
Change:
"
</xsd.complexType>
"
To:
"
</xsd:complexType>
"

In 1.2.7.1 Change:
"<simpleType" to "<xsd:simpleType" and "</simpleType" to "</xsd:simpleType"

In 1.2.7.3 Change:
Example.Number>
to:
Example.Number">
And change:
Example.OtherNumber>
To:
Example.OtherNumber">
And Change:
"
xsd:sequence>
xsd:element name="dummy" type="xsd:int" maxOccurs="1" minOccurs="1" />
/xsd:sequence>
"
To:
"
<xsd:sequence>
<xsd:element name="dummy" type="xsd:int" maxOccurs="1" minOccurs="1"/>
</xsd:sequence>
"
And change:
"
xsd:complexContent>
xsd:restriction base="tns:S">
xsd:sequence>
xsd:element name="dummy" type="xsd:int" maxOccurs="1" minOccurs="1" />
"
To:
"
<xsd:complexContent>
<xsd:restriction base="tns:S">
<xsd:sequence>
<xsd:element name="dummy" type="xsd:int" maxOccurs="1" minOccurs="1"/>
"

In 1.2.7.5 apply change G1:

In 1.2.7.6
apply change G1 to arrayLong example:
apply change G1 to struct S example
apply change G1 to matrix example

In 1.2.7.10 change: <complexType to: <xsd:complexType
And change: <xsd:attribute> to: <xsd:attribute

correct the typographical errors to allow the xml schema productions to validate

In Corba to WSDL/SOAP Interworking Spec:
In section 1.2.11, the CORBA namespace file is missing the production for _VALREF.

Proposed Resolution: Add the production for _VALREF to the corba.wsdl file
Revised Text:
Add the following production, from 1.2.7.10, to the corba.wsdl file in 1.2.11:
"
<xsd:complexType name="_VALREF">
<xsd:attribute name="ref" type="xsd:IDREF" use="optional" />
<!-- empty attribute used for null semantics, i.e., value graph end nodes -->
</xsd:complexType>
"

Add the production for _VALREF to the corba.wsdl file.

In Corba to WSDL/SOAP Interworking Spec:
In section 1.2.7.5 and 1.2.7.6, the examples of soap encoded array
types have the SE prefix after the module identifier. The "_SE"
prefix is supposed to be at the beginning of the mapped type name.

Proposed Resolution: fix the examples to change "Example.SE" to "_SE_Example."
Revised Text:
In 1.2.7.5 three occurances:
<xsd:complexType name="Example._SE_longSeq">

<xsd:complexType name="Example._SE_strSeq">

<xsd.complexType name="Example._SE_structSeq">

In 1.2.7.6 one occurance:

<xsd:complexType name="Example._SE_arrayLong" >

Change:
"
"Example.SE"
To
"_SE_Example."

Change the mapping definition text to agree with the examples.

In Corba to WSDL/SOAP Interworking Spec:
In section 1.2.6.1 a soap encoded form for the sequence is used, however the type identifier does not have the SE suffix.

Proposed Resolution: fix the example to be a WS-I BP compliant sequence mapping only.
Revised Text:
In 1.2.6.1, change:
"
which maps to:
"
To:
"
which maps to (only the WS-I BP compliant version is shown for simplicity):
"
And, remove the following explicit lines (where … denotes intervening lines to be retained):
"
<xsd:complexContent>
<xsd:restriction base="SOAP-ENC:Array">
…
<xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="xsd:string[]"/>
</xsd:restriction>
</xsd:complexContent>
"

fix the example to be a WS-I BP compliant sequence mapping only

: In Corba to WSDL/SOAP Interworking Spec:
In section 1.2.7.6, the IDL identifier "S" at top level has already been used for another example.

Also have to make editorial corrections to allow schema to validate.

Proposed Resolution: change second use of "S" To "T", and apply resolution to issue 8991
Revised Text:
In 1.2.7.6 change the following explicitly listed lines: (where "…" implies one or more intervening lines)
"
struct S {
…
<xsd:complexType name="_SE_S.field_ArrayOfint">
…
<xsd:complexType name="_SE_S">
…
<xsd:element name="field" type="S._SE_field_ArrayOfint" nillable="true" maxOccurs="1" minOccurs="1"/>
…
<xsd:complexType name="S.field_ArrayOfint">
…
<xsd:complexType name="S">

<xsd:element name="field" type="S.field_ArrayOfint" nillable="true" maxOccurs="1" minOccurs="1"/>
…
"
To: (this change also incorporates resolution to Issue 8991)
"
struct T {
…
<xsd:complexType name="_SE_T.field_ArrayOfint">
…
<xsd:complexType name="_SE_T">
…
<xsd:element name="field" type="_SE_T.field_ArrayOfint" nillable="true" maxOccurs="1" minOccurs="1"/>
…
<xsd:complexType name="T.field_ArrayOfint">
…
<xsd:complexType name="T">
…
<xsd:element name="field" type="T.field_ArrayOfint" nillable="true" maxOccurs="1" minOccurs="1"/>
…
"

change second use of "S" To "T", and apply resolution to issue 8991

Multi-dimensional arrays in IDL are required to be mapped to intermediate types for each of the sub-arrays. The naming scheme used by the specification can lead to name collision. Referring to section 1.2.7.6 page 1-14, an IDL with the following declaration typedef long matrix [5][3]; maps to complex types as below: <xsd:complexType name="_SE_ArrayOfint"> ... </xsd:complexType> <xsd:complexType name="_SE_matrix"> ... </xsd:complexType> <xsd:complexType name="ArrayOfint"> ... </xsd:complexType> <xsd:complexType name="matrix"> ... </xsd:complexType> However, if you have another type in the above IDL typedef long anotherMatrix[5][3]; This will also map to complex types with names _SE_ArrayOfint, _SE_anotherMatrix, ArrayOfint, anotherMatrix leading to name collision between XML schema types. Same goes for more than two-dimensional arrays. Proposed resolution: To have name collision-free types, an approach can be to include the name and size of that particular array. For example, the above IDL will produce the following schema types. <xsd:complexType name="_SE_ArrayOfint_matrix_3"> <xsd:complexContent> <xsd:restriction base="SOAP-ENC:Array"> <xsd:sequence> <xsd:element name="item" type="xsd:int" minOccurs="3" maxOccurs="3"/> </xsd:sequence> <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="xsd:int[]"/> </xsd:restriction> </xsd:complexContents> </xsd:complexType> <xsd:complexType name="_SE_matrix"> <xsd:complexContent> <xsd:restriction base="SOAP-ENC:Array"> <xsd:sequence> <xsd:element name="item" type="_SE_matrix_3" minOccurs="5" maxOccurs="5"/> </xsd:sequence> <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="_SE_matrix_3[]"/> </xsd:restriction> </xsd:complexContents> </xsd:complexType> <xsd:complexType name="ArrayOfint_matrix_3"> <xsd:sequence> <xsd:element name="item" type="xsd:int" minOccurs="3" maxOccurs="3"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="matrix"> <xsd:sequence> <xsd:element name="item" type="matrix_3" minOccurs="5" maxOccurs="5"/> </xsd:sequence> </xsd:complexType>

append "_<n>" suffix to the nth arising collision with the collided ArrayOf<type> identifier

The specification in section 1.2.7.6 page 1-14 gives the following IDL as example for multi-dimensional arrays typedef long matrix[5][3] What the above array is mapped to is semantically equivalent to matrix[3][5]. Proposed resolution: What we think should be the correct order for the expanded multi-dimenstional array is shown in the following XSD schema: <xsd:complexType name="_SE_ArrayOfint_matrix_3"> <xsd:complexContent> <xsd:restriction base="SOAP-ENC:Array"> <xsd:sequence> <xsd:element name="item" type="xsd:int" minOccurs="3" maxOccurs="3"/> </xsd:sequence> <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="xsd:int[]"/> </xsd:restriction> </xsd:complexContents> </xsd:complexType> <xsd:complexType name="_SE_matrix"> <xsd:complexContent> <xsd:restriction base="SOAP-ENC:Array"> <xsd:sequence> <xsd:element name="item" type="_SE_matrix_3" minOccurs="5" maxOccurs="5"/> </xsd:sequence> <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="_SE_matrix_3[]"/> </xsd:restriction> </xsd:complexContents> </xsd:complexType> <xsd:complexType name="ArrayOfint_matrix_3"> <xsd:sequence> <xsd:element name="item" type="xsd:int" minOccurs="3" maxOccurs="3"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="matrix"> <xsd:sequence> <xsd:element name="item" type="matrix_3" minOccurs="5" maxOccurs="5"/> </xsd:sequence> </xsd:complexType>

Close as Duplicate to issue 8992

The specification in section 1.2.7.6 page 1-14 gives the following IDL as example for multi-dimensional arrays typedef long matrix[5][3] What the above array is mapped to is semantically equivalent to matrix[3][5]. Proposed resolution: What we think should be the correct order for the expanded multi-dimenstional array is shown in the following XSD schema: <xsd:complexType name="_SE_ArrayOfint_matrix_3"> <xsd:complexContent> <xsd:restriction base="SOAP-ENC:Array"> <xsd:sequence> <xsd:element name="item" type="xsd:int" minOccurs="3" axOccurs="3"/> </xsd:sequence> <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="xsd:int[]"/> </xsd:restriction> </xsd:complexContents> </xsd:complexType> <xsd:complexType name="_SE_matrix"> <xsd:complexContent> <xsd:restriction base="SOAP-ENC:Array"> <xsd:sequence> <xsd:element name="item" type="_SE_matrix_3" minOccurs="5" maxOccurs="5"/> </xsd:sequence> <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="_SE_matrix_3[]"/> </xsd:restriction> </xsd:complexContents> </xsd:complexType> <xsd:complexType name="ArrayOfint_matrix_3"> <xsd:sequence> <xsd:element name="item" type="xsd:int" minOccurs="3" maxOccurs="3"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="matrix"> <xsd:sequence> <xsd:element name="item" type="matrix_3" minOccurs="5" maxOccurs="5"/> </xsd:sequence> </xsd:complexType>

see above

In section 1.2.7.6 page 1-13, the implicit IDL declaration of the following struct S

; generates a complex type _SE_S.field_ArrayOfint for the soap-encoded ::S::field. The complex type _SE_S (corresponding to soap-encoded struct S) refers to field with type S._SE_field_ArrayOfint. There is no schema type _S._SE_field_ArrayOfint. Resolution: The soap-encoded name of S.field should be _S._SE_field_ArrayOfint as shown in the following excerpt. <xsd:complexType name="S._SE_field_ArrayOfint"> <xsd:complexContent> <xsd:restriction base="SOAP-ENC:Array"> <xsd:sequence> <xsd:element name="item" type="xsd:int" minOccurs="10" maxOccurs="10"/> </xsd:sequence> <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="xsd:int[]"/> </xsd:restriction> </xsd:complexContents> </xsd:complexType> <xsd:complexType name="_SE_S"> <xsd:sequence> <xsd:element name="field" type="S._SE_field_ArrayOfint" minOccurs="1" maxOccurs="1" </xsd:sequence> </xsd:complexType>

see above