Cart
[Home] [By Thread] [By Date] [Recent Entries]
Joel, these are relevant points, but only in a historic sense. SOAP is what it is. I learned a tremendous amount from the process and will share what I learned when there's enough time to do that. Right now the clock is ticking, interop is a vague concept being determined through perceived market muscle, not with a philosophy of inclusion. That's what's happening *now*. What happened before is probably related to that. But we have no power over the past, it is what it is. Dave ----- Original Message ----- From: "Joel Bender" <jjb5@c...> To: "XML-Dev" <xml-dev@l...> Sent: Thursday, March 29, 2001 8:00 AM Subject: Re: Announce: A Busy Developer's Guide to SOAP 1.1 > > 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. > > This is not a SOAP bash, or flame bait...but could you describe in a > few paragraphs > > (a) is so complicated that there arose a common subset of what > developers have been able to get working > > (b) makes it difficult for busy developers to understand and > therefore a "busy developer's guide" is needed > > (c) what you've learned about the SOAP development process that > led to this state, and how you recommend other organizations > avoid the same problems? > > It strikes me that 'simple' is no longer the operative word and is > now a historical artifact. > > > Joel > > ------------------------------------------------------------------ > The xml-dev list is sponsored by XML.org, an initiative of OASIS > <http://www.oasis-open.org> > > The list archives are at http://lists.xml.org/archives/xml-dev/ > > To unsubscribe from this elist send a message with the single word > "unsubscribe" in the body to: xml-dev-request@l...
|
