W3C: The Leading Web Standards Organization

• Engineering the Web's foundation
  • (x)HTML, XML, CSS, VoiceXML, Web Services, Semantic Web, Security, Accessibility, Internationalization, Privacy, Architecture

• Royaltee-Free standard
• 420+ Members
• 40+ Liaisons
• 20 Offices
  • Including in India, China, South Africa

http://www.w3.org/

Web Services Protocol

Web Services Description

Policy 1.5 Interoperability

Organization	Round 1	Round 2 WSDL1.1	Round 2 WSDL2.0	Round 3 WSDL1.1	Round 3 WSDL2.0	Round 4 UDDI	Round 4 External WSDL1.1	Round 4 External WSDL2.0	Round 4 MediaType	Round 4 Negative Test
Axway	108 of 108	12 of 12	N/A	28 of 28	N/A	N/A	N/A	N/A	N/A	N/A
BEA	108 of 108	12 of 12	N/A	28 of 28	N/A	N/A	N/A	N/A	N/A	3 of 3
IBM	108 of 108	12 of 12	76 of 76	32 of 32	12 of 12	N/A	2 of 2	2 of 2	4 of 4	3 of 3
Layer-7	108 of 108	12 of 12	N/A	32 of 32	N/A	34 of 34	N/A	N/A	4 of 4	3 of 3
Microsoft	108 of 108	12 of 12	N/A	24 of 24	N/A	N/A	N/A	N/A	4 of 4	3 of 3
Oracle	N/A	N/A	N/A	28 of 32	N/A	N/A	2 of 2	N/A	0 of 0	N/A
Sun	97 of 97	12 of 12	N/A	28 of 28	N/A	N/A	N/A	N/A	4 of 4	3 of 3
webMethods	N/A	N/A	N/A	N/A	N/A	34 of 34	N/A	N/A	N/A	N/A
WSO2	108 of 108	12 of 12	76 of 76	28 of 28	12 of 12	N/A	0 of 0	0 of 0	0 of 0	0 of 0
WSO2-C	N/A	N/A	76 of 76	N/A	12 of 12	N/A	N/A	0 of 0	N/A	N/A

Schema/Databinding Interoperability

Toolkit	Results
Axis 1.4	75% 16% 9%
Axis2 1.3 (ADB)	84% 7% 9%
Axis2 1.3 (XMLBeans)	94% 6%
.NET 2.0.50727.42	92% 3% 5%
IBM RAD 7.0 (JAX-RPC)	57% 1% 42%
Mono 1.1.13.8	83% 8% 9%
gSOAP2 C 2.7.10	87% 6% 7%
gSOAP2 C++ 2.7.10	88% 5% 7%
PHP5 5.2.0	88% 7% 5%
SOAP4R 20051204	56% 3% 41%
SOAP4R 1.5.8	56% 3% 41%
Spring 1.0m3 (Castor)	12% 24% 64%
Spring 1.0m3 (JAXB2)	88% 6% 6%
Spring 1.0m3 (XMLBeans)	88% 12%
WCF 3.0	42% 53% 5%
Weblogic Server 10.0	93% 1% 6%
XBinder 1.4	54% 46%
XFire 1.2.5 (JAXB2)	86% 2% 12%
XFire 1.2.5 (XMLBeans)	88% 12%
ZSI 2.0	53% 5% 42%

Web Services at W3C

Focused on the Core architecture of Web Services.

W3C Recommendations:

• SOAP 1.2 (2003)
• SOAP MTOM (2005)
• Web Services Addressing 1.0 (2006)
• WSDL 2.0 (2007)
• Web Services Policy 1.5 (2007)
• Semantic Annotations for WSDL and XML Schema (2007)

Ongoing work around Web Services

• MTOM Policy Assertion
• XML Schema Patterns for Databinding
• SOAP Binding over Java Messaging System (JMS) (just starting)

Member Submissions versus W3C Recommendations

W3C Members can submit technologies to W3C for consideration:

• SOAP 1.1 (2000)
• WSDL 1.1 (2001)
• WSCL, WSCI (2002)
• WS-Addressing, WS-MessageDelivery (2004)
• WSMO, SWSF, WS-Polling, WSDL-S (2005)
• WS-Policy 1.2, WS-Eventing, WS-Enumeration, WS-Tranfer, WS-MTOMPolicy (2006)
• WS-PAEPR, SOAP over Java Message Service (2007)

Those are NOT W3C Recommendations and are NOT endorsed by W3C.

Challenges for Enterprise

• Greatest challenge is not to build more layers but getting the ones we have working
• Missing technology that would allow SOAP clients to consume REST and vice versa
• Innovator's dilemma: educating users to possibilities, vendors implementing technology
• Center of gravity to deal with spec errata, intended use, new questions; continued interop events
• SDOs do not solve problems but are venue where people need to agree on solutions and follow through

The Way Forward

• Undoing REST vs. SOAP
  • Representational State Transfer (REST)
  • Need to leverage strength in both approaches
  • Well-defined bridges
  • Combination, not convergence to single solution
• Putting the Web in Web Services (and vice versa)
  • Unproductive pattern of WS taken off the Web, e.g. WS-Addressing reference parameters
  • Expose WS resources, e.g. WSDLs, using URIs
  • Allow all concerned to reference the same resources from either approach without needing specialized tooling
  • Description beyond WSDL needed for WS and services on Web (see WADL as "REST DL")
• Need for Coordination
  • Short term goal must be solving interoperability problem
  • Goals of coordination
    • Maintenance of errata
    • Clarification of ambiguity during implementation
    • Coordination of disconnects between specs
    • Maintenance/coordination of test suites
    • Coordination of comments on usefulness for real-world problems
    • Sponsoring interop events
    • Capture of interop results as body of best practice
  • Prepare for "new legacy" of different versions of specs

谢谢