Re: Announce: A Busy Developer's Guide to SOAP 1.1

[Dave Winer <dave@userland.com>]

Ken thanks for the pushback, but we're far more flexible than you say.

We've put a stake in the ground, no one else was willing or ready to do
that. Yes, this works with our app, but..

We changed two key parts to the spec yesterday, re parameter order and
encoding, both of which broke our app.

We also extended the discussion period by 24 hours. Please get in the loop
and tell us where else we need to change, or if you prefer, put up your own
interop spec.

Finally, to really follow the discussion and the changes, which are
happening rapidly, please read the archives of the soapbuilder list.

Dave


----- Original Message -----
From: "Ken MacLeod" <ken@bitsko.slc.ut.us>
To: <xml-dist-app@w3.org>; <xml-dev@lists.xml.org>;
<xml-rpc@yahoogroups.com>
Sent: Friday, March 30, 2001 8:34 AM
Subject: Re: Announce: A Busy Developer's Guide to SOAP 1.1


> "Dave Winer" <dave@userland.com> writes:
>
> > Good afternoon. Here's a pointer to a specification that describes a
> > subset of SOAP 1.1 that we believe is the common subset supported by
> > most if not all SOAP 1.1 implementations.
> >
> > http://www.xmlrpc.com/aBusyDevelopersGuideToSoap11
> >
> > Interop is the hot topic now, but it's proving to be a slow
> > process. We felt we could accelerate it by offering developers a
> > specification of a small subset of SOAP that provides a lot of
> > value, is easy to implement and offers a chance for interop to mean
> > something very soon.
>
> For full disclosure, it should probably be noted that this particular
> subset of SOAP for the most part only includes features that match
> with Userland's product Frontier, and that Userland fully and solely
> controls the specification of this subset.
>
> Reworded, this is not merely a "simple" subset of SOAP, but one that
> particularly favors one vendor's product.
>
>   -- Ken
>