The Minds Behind SOAP and XML Web Services – 7 People Redefining Software
Seven protocol designers helped turn XML messaging into SOAP and Web Services, creating a major cross-vendor interoperability stack for enterprise distributed systems.
TL;DR
Seven protocol designers helped turn XML messaging into SOAP and Web Services, creating a major cross-vendor interoperability stack for enterprise distributed systems. [1][2]
Why you should read it anyway
Before ubiquitous JSON APIs, enterprises needed a language-neutral way to describe, transport, secure, and extend structured messages across incompatible platforms. SOAP became the envelope at the center of a much larger Web Services stack.
Imagine where SOAP and XML Web Services would be without them
Without SOAP, XML-RPC and other middleware would still evolve, but WSDL-driven enterprise interoperability, WS-* standards, and cross-vendor service tooling would have developed in a more fragmented way.
Time Estimate of how many years we would be hindered without them for human progress
Editorial counterfactual estimate: 4–8 years. This is not a measured historical fact. It is an editorial estimate of how much slower the field might have matured without this cluster of people, institutions, specifications, and tools.
The 7 people behind SOAP and XML Web Services
1. Don Box
Why they matter: was a principal architect of SOAP and a major advocate of XML-based distributed computing, helping define a vendor-neutral envelope for structured messages.[1]
2. Dave Winer
Why they matter: co-created XML-RPC and participated in the early SOAP lineage, helping move remote procedure calls onto simple Internet protocols and XML.[2]
3. Bob Atkinson
Why they matter: was one of the original SOAP specification authors at Microsoft and helped shape its envelope and extensibility model.[3]
4. Mohsen Al-Ghosein
Why they matter: was an original SOAP co-author and helped define the protocol as an XML-based messaging framework rather than a language-specific RPC system.[4]
5. Henrik Frystyk Nielsen
Why they matter: co-authored SOAP specifications and brought deep HTTP expertise to the interaction between XML messaging and Web transport.[5]
6. Noah Mendelsohn
Why they matter: played a major role in W3C XML Protocol and SOAP standardization, helping guide SOAP from vendor proposal toward an open Web standard.[1]
7. Jean-Jacques Moreau
Why they matter: served as a key editor and contributor to SOAP 1.2 at the W3C, helping formalize the protocol’s processing and extensibility model.[2]
How they each differ from one another
Winer helped establish XML-RPC; Box, Atkinson, Al-Ghosein, and Nielsen created early SOAP; Mendelsohn and Moreau helped move SOAP into formal W3C standardization.
Final Take
SOAP was heavier than the HTTP API styles that followed, but it solved a real historical problem: interoperable enterprise messaging across languages, operating systems, and vendors before today’s simpler API conventions existed.
Works Cited
- 01W3C — SOAP 1.2 w3.org
- 02
- 03XML-RPC Specification xmlrpc.com
- 04
- 05Microsoft Research / SOAP historical materials learn.microsoft.com
CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.
Submit a research lead