WS-I Basic Profiles

Comparison of Profiles: See WS-I website: http://ws-i.org/deliverables/matrix.aspx Note: As of Dec 2010, WS-I became part of OASIS; see http://www.oasis-ws-i.org/ Legend: Yellow cell means there was a change in the profile.
BP 1.0 BP 1.1 2004-04-16 Final Material
http://www.wsi.org/Profiles/BasicProfile-1.0.html
i

v0.7 13 May 2011

BP 1.2 BP 2.0ii 2010-11-09 Final Material

http://ws-i.org/Profiles/BasicProfile1.2-2010-11-09.html

2006-04-10 Final Material ISO/IEC 29361:2008

http://www.wsi.org/Profiles/BasicProfile-1.1.html

2010-11-09 Final Material

http://ws-i.org/Profiles/BasicProfile2.0-2010-11-09.html

XML 1.0 (Second Edition) XML Schema Part 1: Structures XML Schema Part 2: Datatypes WSDL 1.1 SOAP 1.1

XML 1.0 (Second Edition) Namespaces in XML 1.0 XML Schema Part 1: Structures XML Schema Part 2: Datatypes WSDL 1.1 SOAP 1.1

XML 1.0 (Fourth Edition) Namespaces in XML 1.0 (Second Edition) XML Schema Part 1: Structures (Second Edition) XML Schema Part 2: Datatypes (Second Edition) WSDL 1.1 SOAP 1.1

XML 1.0 (Fourth Edition) Namespaces in XML 1.0 (Second Edition) XML Schema Part 1: Structures (Second Edition) XML Schema Part 2: Datatypes (Second Edition) WSDL 1.1iii WSDL 1.1 Binding Extension for SOAP 1.2 SOAP Version 1.2 Part 1: Messaging Framework (Second Edition)iv SOAP Version 1.2 Part 2: Adjuncts (Second Edition) Attachments Profile Version 1.0 (i.e., MIME)

Attachments Profile Version 1.0v (i.e., MIME) XML-Binary Optimized Packaging (XOP) SOAP MTOM SOAP 1.1 Binding for MTOM 1.0 SOAP 1.1 Request Optional Response HTTP Binding UDDI Version 2.04 API Specification UDDI Version 2.03 Data Structure Reference UDDI Version 2 XML Schema RFC2616: HTTP 1.1 RFC2965: HTTP State Management Mechanism RFC2246: TLS Protocol 1.0 RFC2818: HTTP over TLS SSL Protocol 3.0 RFC2459: Internet X.509 PKI Certificate and CRL Profile

XML-Binary Optimized Packaging (XOP) SOAP MTOM dropped dropped UDDI Version 2.04 API Specification UDDI Version 2.03 Data Structure Reference UDDI Version 2 XML Schema RFC2616: HTTP 1.1 RFC2965: HTTP State Management Mechanism RFC2246: TLS Protocol 1.0 RFC2818: HTTP over TLS SSL Protocol 3.0 RFC2459: Internet X.509 PKI Certificate and CRL Profile XML Media Types RFC3986: Uniform Resource Identifier (URI): Generic Syntax WS-Addressing 1.0 - Core

UDDI Version 2.04 API Specification UDDI Version 2.03 Data Structure Reference UDDI Version 2 XML Schema RFC2616: HTTP 1.1 RFC2965: HTTP State Management Mechanism RFC2246: TLS Protocol 1.0 RFC2818: HTTP over TLS SSL Protocol 3.0 RFC2459: Internet X.509 PKI Certificate and CRL Profile

UDDI Version 2.04 API Specification UDDI Version 2.03 Data Structure Reference UDDI Version 2 XML Schema RFC2616: HTTP 1.1 RFC2965: HTTP State Management Mechanism RFC2246: TLS Protocol 1.0 RFC2818: HTTP over TLS SSL Protocol 3.0 RFC2459: Internet X.509 PKI Certificate and CRL Profile

WS-Addressing 1.0 - Core

BP 1.0 BP 1.1

BP 1.2 BP 2.0 WS-Addressing 1.0 - SOAP Binding (except for sections 2, 3, 5.1.2, 5.2.2 and 6.1) WS-Addressing 1.0 - Metadata (except for sections 4.1.1, 4.4.2, 4.4.3 and 5.2) RFC2119: Key words for use in RFCs to Indicate Requirement Levels Namespaces in XML 1.0 (Second Edition) WS-I Conformance Claim Attachment Mechanisms Version 1.0 RFC3986: Uniform Resource Identifier (URI): Generic Syntax WS-Addressing 1.0 - SOAP Binding (except for sections 4, 5.1.1, 5.2.1 and 6.2) WS-Addressing 1.0 - Metadata (except for sections 4.1.1, 4.4.2, 4.4.3 and 5.2) RFC2119: Key words for use in RFCs to Indicate Requirement Levels Namespaces in XML 1.0 (Second Edition) WS-I Conformance Claim Attachment Mechanisms Version 1.0 RFC3986: Uniform Resource Identifier (URI): Generic Syntax

Notes 1. Re: WS-Policy WSDL 1.1 disallows the use of extensibility elements on certain elements and the use of extensibility attributes on others. However, the WS-I Basic Profile 1.1 [BP 1.1] overrules this restriction and allows element extensibility everywhere. Therefore, the Policy reference SHOULD be attached using <wsp:PolicyReference> as child element unless it is absolutely necessary to maintain the original WSDL 1.1 restriction, in which case the @wsp:PolicyURIs attribute should be used for those restricted cases.vi

This Profile is derived from the Basic Profile 1.0 by incorporating any errata to date and separating out those requirements related to the serialization of envelopes and their representation in messages. Such requirements are now part of the Simple SOAP Binding Profile 1.0, identified with a separate conformance claim.
ii

This Profile (BP 2.0) is the first version of the WS-I Basic Profile that changes the version of SOAP in the profile scope from SOAP 1.1 to the W3C SOAP 1.2 Recommendation . As such, BP 1.1 conformant messages are inherently incompatible with those conformant with BP 2.0, while receivers and instances processing these messages may or may not support these two versions of the Basic Profile. WS-I Basic Profile Version 2.0, Working Group Draft, 2010-0331, section 1.2.1, [online document] http://ws-i.org/profiles/BasicProfile-2.0-WGD.html
iii

WS-I Basic Profile 1.2 and 2.0 working group charter states: This Working Group will focus on the development of the Basic Profile versions 1.2 and 2.0. WSDL 2.0 guidance is explicitly out of scope for this Working Group. (See http://www.ws-i.org/docs/charters/WSBasic_Profile_Charter2-1.pdf)
iv

The Basic Profile 2.0 is the first version of the WS-I Basic Profile that changes the version of SOAP in the profile scope from SOAP 1.1 to the W3C SOAP 1.2 Recommendation. As such, clients, servers and the artifacts that comprise a Basic Profile 1.0, 1.1 or 1.2 conformant application are inherently incompatible with an application that is conformant with the Basic Profile 2.0.
v

WS-I BP 1.2 is NOT intended to be composed with the Simple SOAP Binding Profile 1.0. The Attachments Profile 1.0 adds support for SOAP with Attachments [and MIME bindings], and is intended to be used in combination with this Profile.
vi

http://www.w3.org/Submission/WS-PolicyAttachment/, section 4.