RE: Timeline for producing final versions with references to WS-Policy 1.5

["Patil, Sanjay" <sanjay.patil@sap.com>]

Title: RE: Timeline for producing final versions with references to WS-Policy 1.5

Hi Kevin, Chris,

Any chance that my question below would get answered in the coming week! Please note that the WS-RX TC's schedule (and even decision about when to convene the next meeting) depends upon what we hear from you.

[Copying the SX-TC on this thread since I forgot to do that before].

Thanks,
Sanjay Patil
OASIS WS-RX TC Co-Chair

_____________________________________________
From:   Patil, Sanjay 
Sent:   Thursday, Jan 17, 2008 14:37 PM
To:     'klawrenc@us.ibm.com'; 'ckaler@microsoft.com'
Cc:     ws-rx@lists.oasis-open.org
Subject:        Timeline for producing final versions with references to WS-Policy 1.5




Dear Chairs of the OASIS WS-SX TC,

On behalf of the OASIS WS-RX TC, I wanted to bring to your attention and get your advise regarding an open issue for the WS-RX TC [1] that is dependent upon the WS-SX TC's plans.

Here is the gist of the issue as I understand:
Some of the WS-RM specifications (produced by the WS-RX TC) have references to the WS-SecurityPolicy, WS-SecureConversation and WS-Trust specifications. We think that these references should be updated to point to the final versions of the WS-SX TC's specifications that reference WS-Policy 1.5 specifications. In this regard, we would like to understand your plans and tentative timeline for progressing the WS-SX TC's specifications.

If waiting until the WS-SX TC's specifications (with references to WS-Policy 1.5) reach a final (OASIS Standard) status is going to introduce excessive delays for the WS-RX TC, then the WS-RX TC may decide to reference the WS-SX TC's Committee Drafts/Specifications (with references to WS-Policy 1.5). It is therefore important for the WS-RX TC to understand your specification progression plans/timeline as soon as possible.

Thanks,
Sanjay Patil
OASIS WS-RX TC Co-Chair

[1] http://www.oasis-open.org/archives/ws-rx/200710/msg00005.html