Re: WSDL 1.2 drops use="encoded"

Rich,

I've been bringing this issue up in XMLP and in WS-Desc for some time
now, but I don't seem to be persuasive enough.

If you and other people come to one of the groups and say you need SOAP
1.2 Encoding supported directly in WSDL 1.2 because you actually need
SOAP Encoding, the groups would probably work on the schema language. I
don't think this is an issue of resources because I'd happily volunteer
to do an initial proposal, as I believe I've said before.

The alternative to inventing a SOAP Data Model Schema Language was to
specify precisely how XML Schema works with use="encoded", which I
believe would have been much more work to get right and sort out all the
corner cases.

So, voice your needs! Many (including myself) seem to share the
understanding that people are shying away from SOAP Encoding. This may
be because XML is just sufficient, or it may be because SOAP Encoding
doesn't play nicely with XML Schema and there are no alternatives as
yet.

Hope we don't end up with any hard feelings,

                      Jacek Kopecky
                      Systinet Corporation
                      http://www.systinet.com/



On Thu, 2003-03-06 at 21:35, Rich Salz wrote:
> So you're saying it's okay to drop use="encoded" because I can create a
> new schema language that directly supports SOAP RPC encoding, find a
> standards organization to "finish up" my new schema language, and then
> work to get it supported by the current "WSDL wizard" vendors?
> 
> Unh, no thanks.
> 	/r$
>

Received on Friday, 7 March 2003 02:27:44 UTC