Draft Minutes from WS-RX TC Call 14 August 2008

Sanjay,

Please add roll call to these minutes.

Minutes: 14 August 2008, WS-RX TC

Approval of Minutes from Jul 17, 2008: Approved

Review of Action Items

   AI# 0144  Doug to update the issues list: Closed

Proposal to ask TC Admin to start a special majority vote to accept specifications as CS

Which other specifications do we want references as Designated Cross References (DCR) in the ballot?

Note that as per the TC process, for each DCR, we need to specify certain information for the purposes of opening the specification approval ballot with DCRs. Here is the relevant text from the TC

Process.  The text of a proposed Designated Cross-Reference Change to a specification must include and may only include: the name, version and revision number; expected approval status; date; and URI for each other specification to be cross-referenced.

Motion from momartin:

Motion to initiate three WS-RX Committee Specification electronic ballots for:

1.WS-ReliableMessaging 1.2

2.WS-ReliableMessagingPolicy 1.2

3.WS-MakeConnection 1.1

This motion includes the following DCR:

Adopt a "Designated Cross-Reference Change" as part of the WS-RX Committee Specification Approval, which includes:

(1) The list of other OASIS specifications (including version number) referenced by WS-RM 1.2 and whose cross-references are to be updated upon successful completion of the expected approval action:

              WS-Security Policy 1.3 [1]

              WS-Trust 1.4 [2]

              WS-SecureConversation 1.4 [3]

              WS-ReliableMessagingPolicy 1.2 [4]

(2) The list of the other OASIS specification (including version number) referenced by WS-RMP 1.2 and whose cross-references are to be updated upon successful completion of the expected approval action:

              WS-Security Policy 1.3 [1]

              WS-ReliableMessaging 1.2 [5]

(3) The list of other OASIS specifications (including version number) referenced by WS-MC 1.1 and whose cross-references are to be updated upon successful completion of the expected approval action:

              WS-Security Policy 1.3 [1]

              WS-Trust 1.4 [2]

              WS-SecureConversation 1.4 [3]

              WS-ReliableMessaging 1.2 [5]

              WS-ReliableMessagingPolicy 1.2 [4]

Expected approval status for all cross-references: Committee Specification

Time horizon date: 30 November 2008

WS-SX set: See [1], [2], [3]

WS-RX set: See [4], [5]

This is set forth in the Designated Cross-Reference Change in the OASIS TC Process in Section 2.19 http://www.oasis-open.org/committees/process.php#crossRefs]

This TC acknowledges that approval and publication of the specification may be delayed by the Designated Cross-Reference Changes.

[1] http://docs.oasis-open.org/ws-sx/ws-securitypolicy/v1.3/

[2] http://docs.oasis-open.org/ws-sx/ws-trust/v1.4/

[3] http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/

[4] http://docs.oasis-open.org/ws-rx/wsrmp/200702

[5] http://docs.oasis-open.org/ws-rx/wsrm/200702

To answer questions about options and implications of this motion, Patil explained criteria around these ballots (McRae mail: http://lists.oasis-open.org/archives/ws-rx/200808/msg00013.html):

1. At WS-RX ballots close (fail):

WS-RX specs remain unchanged. They remain Committee Drafts.

2. At WS-RX ballots close (pass):

WS-RX specs remain unchanged. They are not updated to Committee Specification status. They remain in limbo until one of the following occurs:

3. WS-SX ballots close (pass) on or before 30 Nov:

WS-RX specs become Committee Specifications. All DCRs are updated.

4. WS-SX ballots close (fail) on or before 30 Nov:

WS-RX specs become Committee Specifications. Only DCRs to other WS-RX specs are updated.

5. WS-SX does not reach ballot on/before 30 Nov:

WS-RX specs become Committee Specifications. Only DCRs to other WS-RX specs are updated.

Approved unanimously: Motion/Monica J. Martin Second/Ram Jeyaraman

Next meeting is 11 September 2008 sponsored by Microsoft.

ws-rx message