1. WSDL 1.2 Binding Changes Sanjiva Weerawarana WSDL WG F2F – July 2003 Raleigh, NC

2. Motivation Without we can make WSDL 1.2 bindings dramatically simpler

3. Overview s in general SOAP binding HTTP binding –@encodingStyle=rpc –General documents

4. Make @interface optional to make binding more reusable binding details.. If any elements are present, then @interface MUST be present service/@interface MUST match deref(endpoint/@binding)/@interface Allow to point to bindings or inline bindings: <endpoint name=“ncname” [bindings=“list-of-qnames”]> inlined-bindings address-binding

5. SOAP Binding Define default SOAP binding rules –@body goes into –Each of @headers goes into Define new binding element for default rule for wsoap:operation/@soapActionURI –Proposal = interfaceTNS#operation-name Drop, Change : add new header or add @role/@mustUnderstand –Drop @type, @namespace, @localname, @encodingStyle –Add @mustUnderstand?? Retain : update Drop : drop @protocol Change : add @protocol Cool feature: No need to pay attention to /definitions/interface/operation/@encodingStyle=rpc

6. HTTP Binding For @encodingStyle=rpc case –If types are all simple, then can do HTTP GET/POST binding for content-type=form-url- encoded URL rewriting, POST body, … –Basically s!@part=“foo”!xpath:/foo!g For other cases –Natural text/xml binding with input/@body as input payload and output/@body as output payload

7. Example - Today element-decls <binding name=ncname interface=qname> <endpoint name=ncname binding=qname>

8. Example - Tomorrow element-decls <endpoint name=ncname binding=“x:foo”> <soap:address protocol=“..” location=“…”/>