WSDL Usage Experience with XML Schema 1.0 Jonathan Marsh Chair, WS Description WG

WSDL Overview single … <xs:element name="checkAvailabilityResponse"> … … …

WSDL Overview WSDL depends on XML Schema Many similarities: Many similarities: Component model Import/Include QName references/symbol spaces Component designators Some blurred lines of responsibility Some blurred lines of responsibility WSDL-defined schema extensions Versioning

Describing base64Binary <xs:complexType name="JPEGPictureType" xmime:expectedContentTypes="image/jpeg"> <xs:element name="JPEGPicture" type="tns:JPEGPictureType" /> see

Describing References <wsa:EndpointReference xmlns:wsa= " xmlns:wsaw=" xmlns:fabrikam=" fabrikam:Inventory

Describing References <xs:schema xmlns:wsa=" xmlns:fabrikam=" <xs:complexType name="InventoryReference" wsdlx:interface="fabrikam:Inventory">

Versioning LC124 only remaining open issue Versioning of message structure is a common way to version a Web service. Versioning of message structure is a common way to version a Web service. Known problems with and UPA make versioning of message structure difficult. Known problems with and UPA make versioning of message structure difficult.

LC124 proposal(s) Allow, encourage, or mandate ignoring of unknown content in a message. Define, reference, or suggest an algorithm such as Henry’s “validate-twice.” Provide syntax to engage/suppress this behavior. Model in WSDL or as schema extension.

LC124 questions Schema descriptions primarily used for code generation, not by validation. Does an ignore-unknown rule impact code generation or mapping of XML data to programming constructs? Is this a WSDL problem or an XML Schema problem?

the end