[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Electronic Ballots for CS and OS
Mary Greetings! The WSRX TC today voted to withdraw the current CS specs that are in limbo waiting for the WSSX DCRs. In addition we voted: The WS-RX TC instructs the Chairs to request the TC administrator to initiate six electronic ballots described below each one of 7 days duration to approve WS-ReliableMessaging v1.2, WS-ReliableMessagingPolicy v1.2, and WS-MakeConnection v1.1 specifications as a Committee Specification and to send those specifications to OASIS for a standardization vote." -- Do you approve WS-ReliableMessaging v1.2 [1] as a Committee Specification with the Designated Cross Reference (DCR) changes described below? Per Section 2.19 Designated Cross-Reference Changes of the OASIS TC Process document, the Committee Specification version of WS-ReliableMessaging v1.2 will be updated to refer to the Committee Specification version of the Designated Cross-References identified below when they are available. WS-SecurityPolicy v1.3 Committee Draft 03 URI: http://docs.oasis-open.org/ws-sx/ws-securitypolicy/v1.3/cd/ws-securitypolicy-1.3-spec-cd-03.doc Expected approval status: Committee Specification (expected date: November 200 WS-Trust v1.4 Committee Draft 03 URI: http://docs.oasis-open.org/ws-sx/ws-trust/v1.4/cd/ws-trust-1.4-spec-cd-03.doc Expected approval status: Committee Specification (expected date: November 200 WS-SecureConversation v1.4 Committee Draft 03 URI: http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/cd/ws-secureconversation-1.4-spec-cd-03.doc Expected approval status: Committee Specification (expected date: November 200 WS-ReliableMessagingPolicy v1.2 Committee Draft 02 URI: http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.2-spec-cd-02.doc Expected approval status: Committee Specification (expected date: concurrently under ballot for approval as Committee Specification) The 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-rx/wsrm/200702/wsrm-1.2-spec-cd-02.doc -- Should the ballot to approve WS-ReliableMessaging v1.2 [1] as a Committee Specification pass, do you also approve to send the specification to OASIS for a standardization vote with the Designated Cross Reference (DCR) changes described below? Per Section 2.19 Designated Cross-Reference Changes of the OASIS TC Process document, the OASIS Standard version of WS-ReliableMessaging v1.2 will be updated to refer to the OASIS Standard version of the Designated Cross-References identified below when they are available. WS-SecurityPolicy v1.3 as updated per the ballot to approve the above-referenced specification as a Committee Specification. Expected approval status: OASIS Standard (expected date: February 2009) WS-Trust v1.4 as updated per the ballot to approve the above-referenced specification as a Committee Specification. Expected approval status: OASIS Standard (expected date: February 2009) WS-SecureConversation v1.4 as updated per the ballot to approve the above-referenced specification as a Committee Specification. Expected approval status: OASIS Standard (expected date: February 2009) WS-ReliableMessagingPolicy v1.2 as updated per the ballot to approve the above-referenced specification as a Committee Specification. Expected approval status: OASIS Standard (expected date: February 2009) The 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-rx/wsrm/200702/wsrm-1.2-spec-cd-02.doc -- Do you approve WS-ReliableMessagingPolicy v1.2 [1] as a Committee Specification with the Designated Cross Reference (DCR) changes described below? Per Section 2.19 Designated Cross-Reference Changes of the OASIS TC Process document, the Committee Specification version of WS-ReliableMessagingPolicy v1.2 will be updated to refer to the Committee Specification version of the Designated Cross-References identified below when they are available. WS-SecurityPolicy v1.3 Committee Draft 03 URI: http://docs.oasis-open.org/ws-sx/ws-securitypolicy/v1.3/cd/ws-securitypolicy-1.3-spec-cd-03.doc Expected approval status: Committee Specification (expected date: November 200 WS-ReliableMessaging v1.2 Committee Draft 02 URI: http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.2-spec-cd-02.doc Expected approval status: Committee Specification (expected date: concurrently under ballot for approval as Committee Specification) The 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-rx/wsrmp/200702/wsrmp-1.2-spec-cd-02.doc -- Should the ballot to approve WS-ReliableMessagingPolicy v1.2 [1] as a Committee Specification pass, do you also approve to send the specification to OASIS for a standardization vote with the Designated Cross Reference (DCR) changes described below? Per Section 2.19 Designated Cross-Reference Changes of the OASIS TC Process document, the OASIS Standard version of WS-ReliableMessagingPolicy v1.2 will be updated to refer to the OASIS Standard version of the Designated Cross-References identified below when they are available. WS-SecurityPolicy v1.3 as updated per the ballot to approve the above-referenced specification as a Committee Specification. Expected approval status: OASIS Standard (expected date: February 2009) WS-ReliableMessaging v1.2 updated per the ballot to approve the above-referenced specification as a Committee Specification. Expected approval status: OASIS Standard (expected date: February 2009) The 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-rx/wsrmp/200702/wsrmp-1.2-spec-cd-02.doc -- Do you approve WS-MakeConnection v1.1 [1] as a Committee Specification with the Designated Cross Reference (DCR) changes described below? Per Section 2.19 Designated Cross-Reference Changes of the OASIS TC Process document, the Committee Specification version of WS-MakeConnection v1.1 will be updated to refer to the Committee Specification version of the Designated Cross-References identified below when they are available. WS-SecurityPolicy v1.3 Committee Draft 03 URI: http://docs.oasis-open.org/ws-sx/ws-securitypolicy/v1.3/cd/ws-securitypolicy-1.3-spec-cd-03.doc Expected approval status: Committee Specification (expected date: November 200 WS-Trust v1.4 Committee Draft 03 URI: http://docs.oasis-open.org/ws-sx/ws-trust/v1.4/cd/ws-trust-1.4-spec-cd-03.doc Expected approval status: Committee Specification (expected date: November 200 WS-SecureConversation v1.4 Committee Draft 03 URI: http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/cd/ws-secureconversation-1.4-spec-cd-03.doc Expected approval status: Committee Specification (expected date: November 200 WS-ReliableMessaging v1.2 Committee Draft 02 URI: http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.2-spec-cd-02.doc Expected approval status: Committee Specification (expected date: concurrently under ballot for approval as Committee Specification) WS-ReliableMessagingPolicy v1.2 Committee Draft 02 URI: http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.2-spec-cd-02.doc Expected approval status: Committee Specification (expected date: concurrently under ballot for approval as Committee Specification) The 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-rx/wsmc/200702/wsmc-1.1-spec-cd-02.doc -- Should the ballot to approve WS-MakeConnection v1.1 [1] as a Committee Specification pass, do you also approve to send the specification to OASIS for a standardization vote with the Designated Cross Reference (DCR) changes described below? Per Section 2.19 Designated Cross-Reference Changes of the OASIS TC Process document, the OASIS Standard version of WS-MakeConnection v1.1 will be updated to refer to the OASIS Standard version of the Designated Cross-References identified below when they are available. WS-SecurityPolicy v1.3 as updated per the ballot to approve the above-referenced specification as a Committee Specification. Expected approval status: Committee Specification (expected date: February 2009) WS-Trust v1.4 as updated per the ballot to approve the above-referenced specification as a Committee Specification. Expected approval status: Committee Specification (expected date: February 2009) WS-SecureConversation v1.4 as updated per the ballot to approve the above-referenced specification as a Committee Specification. Expected approval status: Committee Specification (expected date: February 2009) WS-ReliableMessaging v1.2 as updated per the ballot to approve the above-referenced specification as a Committee Specification. Expected approval status: Committee Specification (expected date: February 2009) WS-ReliableMessagingPolicy v1.2 as updated per the ballot to approve the above-referenced specification as a Committee Specification. Expected approval status: Committee Specification (expected date: February 2009) The 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-rx/wsmc/200702/wsmc-1.1-spec-cd-02.doc The latest specs that we voted on for CD are here: http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/30089/WSRX%20v1.2-CD02.zip Thanks very much Paul -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair VP, Apache Synapse Office: +44 844 484 8143 Cell: +44 798 447 4618 blog: http://pzf.fremantle.org paul@wso2.com "Oxygenating the Web Service Platform", www.wso2.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]