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

Motivation Without we can make WSDL 1.2 bindings dramatically simpler

Overview s in general SOAP binding HTTP binding –General documents

optional to make binding more reusable binding details.. If any elements are present, MUST be present MUST match Allow to point to bindings or inline bindings: <endpoint name=“ncname” [bindings=“list-of-qnames”]> inlined-bindings address-binding

SOAP Binding Define default SOAP binding rules goes into –Each goes into Define new binding element for default rule for –Proposal = interfaceTNS#operation-name Drop, Change : add new header or Retain : update Drop : Change : Cool feature: No need to pay attention to

HTTP Binding case –If types are all simple, then can do HTTP GET/POST binding for content-type=form-url- encoded URL rewriting, POST body, … –Basically For other cases –Natural text/xml binding with as input payload and as output payload

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

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