NEW ISSUE: Interface compatibility refers to input/output types whichis ambiguous when using WSDL 1.1

[Anish Karmarkar <Anish.Karmarkar@oracle.com>]

Title:  Interface compatibility refers to input/output types which is 
ambiguous when using WSDL 1.1

Description:
In ASM60017 it states:
"compatibility between the source interface and the target interface for 
a wire for the individual operations is defined as compatibility of the 
signature, that is operation name, input types, and output types MUST be 
the same."

There are two problems with this:
1) We allow different interface languages to be used in SCA, so it is 
not clear how the operation name and type comparison would be made to 
determine if they are the "same".
2) When using WSDL 1.1 interface, there are two "types" allowed: XML 
Schema element decl or XML Schema type. How is "sameness" determined in 
a case where the reference uses XML Schema element decl and the service 
uses a XML Schema type.

Proposal:

Outline --
1) Use the WSDL 1.1 interface as the canonical interface language and 
require that "sameness" be determined after the interfaces are mapped to 
WSDL 1.1.
2) Two interfaces A and B, where A uses XML Schema element decl and B 
uses XML Schema type are considered incompatible.

Text change --
replace ASM60017 with:
"compatibility between the source interface and the target interface for 
a wire for the individual operations is defined as compatibility of the 
signature, that is operation name, input types, and output types MUST be 
the same, ***after the interfaces are mapped to WSDL 1.1 portTypes***."

add addition text as follows:
WSDL 1.1 message parts can point to XML Schema element declaration or 
XML Schema types. When determining compatibility between two WSDL 
operations, a message part that points to an XML Schema element 
declaration is considered to be incompatible with a message part that 
points to an XML Schema type.

-Anish
--