| The Big SOA Grid TM | ||||||||
| Specification | Category | Summary | Standards Body | Version | Status | Date | Notes | Submitter / Committee Members / Editors |
| BPEL4WS | Orchestration | BPEL4WS, which stands for Business Process Execution Language for Web Services, has been incorporated into the WS-BPEL specification. | OASIS | 1.1 | http://www-106.ibm.com/developerworks/webservices/library/ws-bpel/ | May 5, 2003 | Microsoft, IBM, Siebel Systems, BEA, SAP | |
| MTOM (Message Transmission Optimization Mechanism) | Messaging | Standard which provides a mechanism to specify pass-through elements in Header/Body as well as MIME attachments. | W3C | 1.2 (Recommendation) | http://www.w3.org/TR/soap12-mtom/ | January 25, 2005 | Microsoft, IBM, BEA, Canon | |
| SAML | Security | SAML, or Security Assertion Markup Language, is an XML-based specification designed to authenticate and authorize a consumer of a service. | OASIS | 1.1 | http://www.oasis-open.org/committees/download.php/3400/oasis-sstc-saml-1.1-pdf-xsd.zip | August 28, 2003 | Sun, RSA, Netegrity | |
| 2.0 | http://docs.oasis-open.org/security/saml/v2.0/saml-2.0-os.zip | February 28, 2005 | SAML offers additional protocols for handling all aspects of authentication and authorization. It is also typically evaluated as a component of a larger entity: WS-Security | Enosis Group LLC, PA Consulting, RSA, Sun, NTT, NCSA, BEA, Entrust, Internet2, Oracle | ||||
| SOAP | Messaging | Simple Object Access Protocol defines an XML Procotol to communicate with Web Services. | W3C | 1.1 | http://www.w3.org/TR/2000/NOTE-SOAP-20000508/ | May 8, 2000 | Microsoft, IBM, Canon, Oracle Corporation, Sun Microsystems, W3C, UserLand Software, DevelopMentor | |
| 1.2 (Recommendation) | http://www.w3.org/TR/soap12-part0/ | April 27, 2007 | WSO2, Sun, IONA, Oracle, TIBCO, IBM, Sonic Software, Sonoa Systems, BEA | |||||
| SOAP w/Attachments | Messaging | Standard which extendes SOAP to support the inclusion of the MIME media type / attachments. The attachments are typically used to communicate non-SOAP/XML information (binary data, images, audio etc.) | W3C | 1.2 | http://www.w3.org/TR/soap12-af/ | June 8, 2004 | Microsoft, IBM | |
| XML | Data/Data Definition | The Extensible Markup Language (XML) is a subset of SGML and designed to provide a portable mechanism for exchanging information over the Web similar to the previously successful HTML. Currently in the Fourth Edition of v1.0 | W3C | 1.0 | http://www.w3.org/TR/1998/REC-xml-19980210 | February 10, 1998 | Textuality, Microsoft, University of Illinois at Chicago | |
| 1.0 | http://www.w3.org/TR/2006/REC-xml-20060816 | September 29, 2006 | Textuality/Netscape, Microsoft, W3C, Sun Microsystems | |||||
| XML Schema | Data/Data Definition | XML Schema represents a set of rules used to describe a valid XML document. It utilitzes namespaces to resolve conflicts and data types. | W3C | 1.0 | http://www.w3.org/XML/Schema#dev | May 2, 2001 | SGML Works!, Oracle Corporation, Kaiser Permanente, W3C | |
| 1.1 (Submission) | http://www.w3.org/TR/xmlschema-1 | October 28, 2004 | University of Edinburgh, Oracle, Commerce One, Lotus Development | |||||
| XPath | Data Transformation/Extraction | XPath, also known as XML Path Language, provides a common syntax and semantics for addressing a part of an XML document. | W3C | 1.0 (Recommendation) | http://www.w3.org/TR/xpath | November 16, 1999 | ||
| 2.0 (Requirements) | http://www.w3.org/TR/xpath20req/ | June 3, 2005 | Primary goals include simplified manipulation of string and XML content, as well as improved interoperability and ease-of-use | AT&T, Oracle | ||||
| XQuery | Data Transformation/Extraction | XQuery, also known as XML Query, is a specialized query language, similar to SQL, designed to locate information within XML documents. The goal is to make it possible to interact with XML as easily as with databases. | W3C | 1.0 (Recommendation) | http://www.w3.org/TR/xquery | January 23, 2007 | IBM, AT&T, Oracle, DataDirect | |
| XSLT | Data Transformation/Extraction | XSLT is a language typically employed to transform information between different XML formats, from XML into another format, or for converting XML data for display on a web page. | W3C | 1.0 (Recommendation) | http://www.w3.org/TR/xslt | November 16, 1999 | Saba, Microsoft, University of Edinburgh, Arbortext, Adobe | |
| 2.0 (Recommendation) | http://www.w3.org/TR/xslt20/ | January 23, 2007 | Offers many new functionality and usability enhancements. Note that it's designed to be used in conjunction with XPath 2.0 | |||||
| WS-Addressing | Messaging | Standard which provides a transport neutral approach towards referring to Web Services and messages. | W3C | 1.0 (Recommendation) | http://www.w3.org/TR/ws-addr-core/ | May 9, 2006 | Sun Microsystems, IBM, Microsoft, BEA, SAP | |
| WS-AtomicTransaction | Transactions | Atomic transactions typically refer to "all-or-nothing" events that are also generally short-lived. This specification states how these transactions should behave, along with their interaction with coordination services (as defined by WS-Coordination). | OASIS | 1.1 | http://docs.oasis-open.org/ws-tx/wstx-wsat-1.1-spec-os/wstx-wsat-1.1-spec-os.html | April 16, 2007 | IBM, IONA, JBoss | |
| WS-Base Notification | Messaging | A base standard for a web services notifications that specifically describes a NotificationProducer and NotificationConsumer. | OASIS | 1.3 (Ratified) | http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsn | October 11, 2006 | IBM, TIBCO, HP | |
| WS-I Basic Profile | Interoperability | This specification is designed to foster conformance and interoperability among vendor implementations of key service standards such as WSDL, SOAP, and UDDI. | WS-I | 1.1 | http://www.ws-i.org/Profiles/BasicProfile-1.1.html | April 10, 2006 | Microsoft, IBM, SAP, BEA, webMethods | |
| 1.2 (Board approval draft) | http://www.ws-i.org/Profiles/BasicProfile-1.2.html | March 28, 2007 | Fixes 1.1 errors, adds support for WS-Addressing and MTOM binary attachments | Microsoft, IBM, SAP, BEA, webMethods | ||||
| WS-I Basic Security Profile | Interoperability | This specification is designed to foster conformance and interoperability among vendor implementations of key security standards such as WS-Security, SAML, Kerberos, X.509, REL. | WS-I | 1.0 | http://www.ws-i.org/Profiles/BasicSecurityProfile-1.0.html | March 30, 2007 | IBM, Microsoft, Layer 7, Nortel | |
| 1.1 (Working group approval draft) | http://www.ws-i.org/Profiles/BasicSecurityProfile-1.1.html | February 20, 2007 | IBM, Microsoft, Layer 7, Nortel | |||||
| WS-BPEL | Orchestration | WS-BPEL, which stands for Web Services Business Process Execution Language, is a specialized, XML-based language designed to orchestrate business-oriented interactions, typically among Web services. | OASIS | 2.0 | http://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.html | April 11, 2007 | IBM, Microsoft, BEA, Intalio, Adobe, Systinet, JBoss, Sterling Commerce, SAP, Deloitte, TIBCO, webMethods, Oracle | |
| WS-Brokered Notification | Messaging | Standard which defines a web services notiification broker. A notification broker provides advanced messaging features for NotificationProducers and NotificationConsumers. | OASIS | 1.3 (Ratified) | http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsn | October 11, 2006 | Sonic Software, webMethods | |
| WS-Business Activity | Transactions | This specification, in concert with WS-Coordination, is designed to support long-running activities that may span organizations and even involve manual steps. | OASIS | 1.1 | http://docs.oasis-open.org/ws-tx/wstx-wsba-1.1-spec-os/wstx-wsba-1.1-spec-os.html | April 16, 2007 | IBM, IONA, JBoss | |
| WS-Coordination | Transactions | WS-Coordination serves as a guideline and set of protocols for synchronizing and coordinating distributed computational tasks and activities. | OASIS | 1.1 | http://docs.oasis-open.org/ws-tx/wstx-wscoor-1.1-spec-os/wstx-wscoor-1.1-spec-os.html | April 16, 2007 | These activities can be both short running (as specified by WS-AtomicTransaction), and long running (as specified by WS-BusinessActivity). | Microsoft, IONA, IBM |
| WS-Distributed Management | Management | Standard that focuses on distributed management of devices using Web Services or in the management of Web Services. | OASIS | 1.0 (Legacy) | http://www.oasis-open.org/committees/wsdm/ipr.php | September 10, 2003 | IBM, Talking Blocks, Computer Associates International | |
| 1.0/1.1 | http://docs.oasis-open.org/wsdm/wsdm-muws1-1.1-spec-os-01.htm | August 1, 2006 | IBM, AmberPoint, HP | |||||
| WS-Federation | Interoperability | This specification enhances WS-Trust to support distributed trust authentication and authorization across realms. | OASIS | 1.2 | http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsfed | June 18, 2007 | IBM, Microsoft | |
| WS-Policy | Policy | Standard which focuses on describing a Web Service's policies. | W3C | 1.2 (Submission) | http://www.w3.org/Submission/WS-Policy/ | April 25, 2006 | Verisign, Microsoft, Sonic Software, IBM , SAP, BEA | |
| 1.5 (Recommendation) | http://www.w3.org/TR/ws-policy/ | September 4, 2007 | Microsoft, BEA, Nokia, IBM, webMethods, Layer 7, SAP | |||||
| WS-Reliable Messaging | Messaging | A transport-independent standard which enables Web Services to transmit messages across nodes reliably | OASIS | 1.1 | http://docs.oasis-open.org/ws-rx/wsrm/v1.1/wsrm.html | June 14, 2007 | WS02, IBM, SAP, Coastin, BEA, Oracle | |
| WS-Secure Conversation | Interoperability | This specification defines extensions on WS-Security to allow security context establishment and sharing, and session key derivation. | OASIS | 1.3 | http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-sx | March 1, 2007 | IBM, Microsoft, Nortel, Verisign | |
| WS-Security | Security | WS-Security is a flexible specification designed to secure Web services. It's composed of several standards, including X.509, SAML, Kerberos, Rights Expression Language, SOAP with attachments. | OASIS | 1.0 | http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf | April 5, 2002 | IBM, Sun, Microsoft, Verisign | |
| 1.1 | http://www.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-os-SOAPMessageSecurity.pdf | February 21, 2006 | 1.1 schema is a superset of the 1.0 schema, rather than a replacement | IBM, Sun, Microsoft, Verisign | ||||
| WS-Topics | Messaging | XML Model that describes topics and is used in combination with WS-Base Notification. | OASIS | 1.3 (Ratified) | http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsn | October 11, 2006 | HP, IBM | |
| WS-Transaction | Transactions | An amalgamation of specifications that describe how Web service transactions, both short running (as specified by WS-AtomicTransaction), and long running (as specified by WS-BusinessActivity) should behave using coordinated resources (WS-Coordination) | OASIS | 1.1 | (See WS-AtomicTransaction, WS-BusinessActivity, and WS-Coordination specifications) | February 28, 2007 | Adobe, BEA, Fujitsu, Hitachi, IBM, IONA, Microsoft, Nortel, Oracle, Red Hat, Ricoh, Sun, TIBCO | |
| WS-Trust | Interoperability | This specification defines extensions that extend WS-Security to exchange security tokens and establish trust relationships | OASIS | 1.3 | http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-sx | March 19, 2007 | IBM, Microsoft, Nortel, Verisign | |
| WSDL | Service Description | Web Services Description Language is an XML format which describes a network service including supported messages, operations, bindings and location on the network. | W3C | 1.1 | http://www.w3.org/TR/wsdl | March 15, 2001 | Microsoft, IBM | |
| 2.0 (Recommendation) | http://www.w3.org/TR/wsdl20/ | June 26, 2007 | IBM, Canon, WS02, Sun Microsystems | |||||
| UDDI | Registry | UDDI, which means Universial Description, Discovery, and Integration, is an XML registry originally designed to let providers of publicly-available Web services register their offerings. It also made it possible for potential consumers of these services to discover them. | OASIS | 2.0 | http://www.oasis-open.org/committees/uddi-spec/doc/tcspecs.htm#uddiv2 | July 19, 2002 | IBM, Accenture, BEA, Fujitsu, Microsoft, HP, Verisign, Oracle, Sun, Intel, SAP, webMethods | |
| 3.0 (3.02) | http://www.oasis-open.org/committees/uddi-spec/doc/tcspecs.htm#uddiv3 | October 19, 2004 | Many improvements, including better WSDL capabilities, data model enhancements, multi-registry topologies, and a new subscription API. | Microsoft, Sun, HP, Oracle, Intel, SAP | ||||
| XACML | Interoperability | This specification defines an access control policy via XML | OASIS | 2.0 | http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xacml#XACML20 | June 28, 2007 | AOL,Atos Origin,BEA Systems,Boeing,Booz Allen Hamilton,Entrust,Hewlett-Packard,IBM,Internet2,Neustar,Nokia,NTT,OpenNetwork,Principal Identity,RSA Security,Sigaba,Sun Microsystems,Trustgenix | |
| XKMS | Interoperability | Standard which specifies how to register and distribute public keys. This standard is meant to be used in conjunction with XML Signatures, | W3C | 2.0 | http://www.w3.org/TR/xkms/ | March 30, 2001 | Verisign, Microsoft, webMethods | |