stuff

WS-I ponders asynchrony and reliability - so what are we talking about?

This Working Group will focus on the development of the Basic Profile versions 1.2 and 2.0.

The Basic Profile 1.2 will be based upon the following specifications:
1. WS-I Basic Profile 1.1 [20]
2. W3C WS-Addressing 1.0 - Core [1]
3. W3C WS-Addressing 1.0 - SOAP Binding [2]
4. W3C WS-Addressing 1.0 – WSDL Binding [21]***
5. SOAP 1.1 Binding for MTOM 1.0 [REF]

The Basic Profile 1.2 should include the minimum number of changes required to incorporate WS-Addressing and allow for composition with the Secure Reliable Messaging Profile 1.0. Once the Basic Profile 1.2 is progressed to Working Group Approval draft, the Working Group will next focus on development of Basic Profile 2.0.

The Basic Profile 2.0 will be based upon the following specifications**:
1. W3C WS-Addressing 1.0 - Core [1] ***
2. W3C WS-Addressing 1.0 - SOAP Binding [2] ***
3. W3C WS-Addressing 1.0 – WSDL Binding [21] ***
4. W3C SOAP Version 1.2 Part 1: Messaging Framework [3]
5. W3C SOAP Version 1.2 Part 2: Adjuncts [4]
6. W3C Message Transmission Optimization Method [5]
7. W3C XML-binary Optimized Packaging [6]
8. W3C Namespaces in XML [7]
9. W3C XML 1.0 Second Edition [8]
10. W3C WSDL 1.1 [9]
11. W3C XML Schema 2001 Part 1: Structures [10]
12. W3C XML Schema 2001 Part 2: Datatypes [11]
13. OASIS UDDI 2 [REF]
14. OASIS UDDI 3 [12]
15. WSDL 1.1 Binding Extension for SOAP 1.2 [22]
.
The Basic Profile version 2.0, when practical, should cleanly compose with the following specifications:

Basic Security Profile 1.0 and related profiles:
1. WS-I Basic Security Profile 1.0 [13]
2. WS-I REL Token Profile 1.0 [14]
3. WS-I Kerberos Token Profile 1.0 [15]
4. WS-I SAML Token Profile 1.0 [16]

Basic Security Profile 1.1 and related profiles:
5. WS-I Basic Security Profile 1.1 [17]
6. WS-I REL Token Profile 1.1 [18]
7. WS-I Kerberos Token Profile 1.0
8. WS-I SAML Token Profile 1.0

Reliable Secure Profile 1.0:
9. WS-I Reliable Secure Profile 1.0 [19] *

* The Basic Profile Working Group will coordinate closely with the Reliable Secure Working Group as their respective profiles are developed. Steps should be taken to ensure clean composition between these profiles.
** In order to have clean composition between specifications, the Board is expected to extend the list of referenced specifications for additional bindings as appropriate.
*** The referenced specification must be a W3C PR before the Basic Profile 2.0 is advanced to WGAD status. The WS-I Board will not take the profile to Final Material until the referenced specifications become W3C REC.

The scenarios and requirements work should consider interoperability issues identified across a wide range of Web services applications (e.g., mobile, devices, intermediaries, enterprise applications, etc.)

Finally, the WG is charged with collaborating with the Liaison Committee to produce derivative material of the WS-I Basic Profile 1.1 and Simple SOAP Binding Profile 1.0 that satisfies the requirements of a formal PAS submission to ISO of the WS-I Basic Profile 1.1 and Simple SOAP Binding Profile 1.0.

Unless approved by the Board, this Working Group will not develop material for any profiles other than the Basic Profile versions 1.2 and 2.0, or create deliverables not explicitly defined in this charter.

This Working Group will focus on the development of the RSP 1.0.

The RSP 1.0 will be based upon the following specifications:
1. OASIS WS-ReliableMessaging 1.1 [1] *
2. OASIS WS-SecureConversation 1.3 [2] *
For clarity, this profile will not provide guidance for the policy adjuncts (e.g., WS-ReliableMessaging Policy Assertion [ref]) to these specifications.

The RSP 1.0, when practical, will compose with the following specifications:
1. WS-I Basic Profile 1.2 [6] **
2. WS-I Basic Profile 2.0 [3] **
3. WS-I Basic Security Profile 1.0 [4]
4. WS-I Basic Security Profile 1.1 [5]
If current guidance in these profiles prohibits such composition, the working groups should identify these requirements and determine whether additional errata or revisions are required.

* The referenced specification must be an OASIS Committee Specification before the RSP 1.0 is advanced to WGAD status. The WS-I Board will not take a profile to Final Material until the referenced specifications become OASIS Standard.
** The RSP 1.0 will be designed to require the use of WS-I Basic Profile version 1.2 or 2.0. Care should be taken to coordinate with this activity to avoid any incompatibilities.

This Working Group will be developing scenarios, requirements and profile guidance in parallel with the related standardization efforts within the OASIS WS-Reliable Exchange Technical Committee. The scenarios and requirements work should consider interoperability issues identified across a wide range of Web services applications (e.g., mobile, devices, intermediaries, enterprise applications, etc.). Working Group Members should work to ensure appropriate feedback is provided to the OASIS committee.

RSP 1.0 must list all underlying protocol binding restrictions, if any, that will be employed by the directly referenced specifications upon which this profile is based. It will clarify how these options are indicated - e.g. use of anonymous replyTo in WS-Addressing. RSP 1.0 may further narrow binding options allowed by these specifications as appropriate.

Unless approved by the Board, this Working Group will not develop material for any profile other than the RSP 1.0, or create deliverables not explicitly defined in this charter.