Re: WSDL binding for DIME

Hi,

Ok, this comes just in time!. Two questions:

-- For both the open and closed content layouts, the ordering of the =
secondary payloads is constrained:

"Secondary message parts MUST appear in the DIME message in the same =
order as the references to those parts appear in the SOAP message."

Is this actually necessary? It may optimize some apps, but as long as =
all payloads are uniquely id'd why not allow any order, at least for the =
"open" layout?

-- Shouldn't the RPC example include an <output> message definition, =
assuming it's a request/response MEP?

RC

I'm surprised this didn't get announced here, but here's the doc.

http://gotdotnet.com/team/xml_wsspecs/dime/WSDL-Extension-for-DIME.htm

BTW, you may want to fix the links in the ToC.

Cheers
Simon
www.pocketsoap.com