Fwd: WS-RA WG requests CR progression for seven specifications

Begin forwarded message:

> Resent-From: chairs@w3.org
> From: Bob Freund <bob.freund@hitachisoftware.com>
> Date: April 13, 2011 4:18:10 PM EDT
> To: Tim Berners-Lee <timbl@w3.org>, Ralph Swick <swick@w3.org>, Yves Lafon <ylafon@w3.org>, tir@w3.org
> Cc: chairs@w3.org, w3t-comm@w3.org
> Subject: WS-RA WG requests CR progression for seven specifications
> 
> Dear Colleagues
> 
> The WS-Resource Access working group requests transition to CR status for seven WS-Resource Access specifications:
> WS-Transfer, WS-Fragment, WS-Metadata Exchange, WS-Eventing, WS-Event Descriptions, WS-Enumeration, and WS-SOAP Assertions
> In each case below, document URIs refer to publication-ready drafts located in snapshot directories.
> 
> (1) Document title, URIs, Abstract and Status
> All documents are anticipated to be published 21 April 2011, (depending on the scheduling of the Director's call).  The cr is expected to end on 20 May 2011
> 
> (a) WS-Transfer
> URL: http://www.w3.org/2002/ws/ra/snapshots/cr/wst.html
> Abstract: http://www.w3.org/2002/ws/ra/snapshots/cr/wst.html#abstract
> Status: http://www.w3.org/2002/ws/ra/snapshots/cr/wst.html#sotd
> 
> (b) WS-Fragment
> URL: http://www.w3.org/2002/ws/ra/snapshots/cr/wsfrag.html
> Abstract: http://www.w3.org/2002/ws/ra/snapshots/cr/wsfrag.html#abstract
> Status: http://www.w3.org/2002/ws/ra/snapshots/cr/wsfrag.html#sotd
> 
> (c) WS-Metadata Exchange
> URL: http://www.w3.org/2002/ws/ra/snapshots/cr/wsmex.html
> Abstract: http://www.w3.org/2002/ws/ra/snapshots/cr/wsmex.html#abstract
> Status: http://www.w3.org/2002/ws/ra/snapshots/cr/wsmex.html#sotd
> 
> (d) WS-Eventing
> URL: http://www.w3.org/2002/ws/ra/snapshots/cr/wseventing.html
> Abstract: http://www.w3.org/2002/ws/ra/snapshots/cr/wseventing.html#abstract
> Status: http://www.w3.org/2002/ws/ra/snapshots/cr/wseventing.html#sotd
> 
> (e) WS-Event Description
> URL: http://www.w3.org/2002/ws/ra/snapshots/cr/wsevd.html
> Abstract: http://www.w3.org/2002/ws/ra/snapshots/cr/wsevd.html#abstract
> Status: http://www.w3.org/2002/ws/ra/snapshots/cr/wsevd.html#sotd
> 
> (f) WS-Enumeration
> URL: http://www.w3.org/2002/ws/ra/snapshots/cr/wsenum.html
> Abstract: http://www.w3.org/2002/ws/ra/snapshots/cr/wsenum.html#abstract
> Status: http://www.w3.org/2002/ws/ra/snapshots/cr/wsenum.html#sotd
> 
> (g) WS-SOAP Assertion
> URL: http://www.w3.org/2002/ws/ra/snapshots/cr/wssa.html
> Abstract: http://www.w3.org/2002/ws/ra/snapshots/cr/wssa.html#abstract
> Status: http://www.w3.org/2002/ws/ra/snapshots/cr/wssa.html#sotd
> 
> 
> (2) Record of the decision to request the transition:
> The initial decision was recorded in the 11 January 2011 minutes[2.1]
> Subsequent to that decision and before the progression to cr a breaking issue was discovered in some early test activities so the progression was delayed.
> The WG voted by electronic ballot on March 30 to progress to cr once again once issues related to those changes were resolved. 
> An email was recorded to summarize this decision[2.2].
> 
> [2.1] http://www.w3.org/2002/ws/ra/11/01/2011-01-11.html#item04
> [2.2] http://lists.w3.org/Archives/Public/public-ws-resource-access/2011Apr/0005.html
> 
> 
> (3) Record of Changes
> The status section and change record in each document records the noteworthy changes. None invalidate earlier reviews.
> 
> 
> (4) Evidence that the document satisfies group's requirements:
> The requirements satisfied by the document are contained in the group's charter[4.1]
> 
> During the course of specification development, the working group decided to eliminate the WS-ResourceTransfer specification and to replace it with the WS-Fragment specification.  In addition practical issues related to the structure of event notifications were addressed with the production of the WS-Event Description specification and the issue of versioning of the SOAP specifications was addressed by the WS-SOAP Assertions specification.
> 
> [4.1] http://www.w3.org/2008/11/ws-ra-charter.html
> 
> 
> (5) Evidence that the documents have received wide review and that issues have been formally addressed:
> Comments received during last call[5.1]: 71
> Last Call Comments from external reviewers[5.2]: 17
> 
> [5.1] http://tinyurl.com/4lv4wza
> [5.2] http://tinyurl.com/4cm3mqv
> 
> 
> (6) Objections:
> 
> There was one formal objection received[6.1].
> 
> Discussion of that objection led to new technical issues which were resolved.
> 
> The formal objection was not withdrawn however the objecting entity provided a notice[6.2] that it would not stand in the way of progression.
> 
> [6.1] http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jun/0014.html
> [6.2] http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Dec/0023.html
> 
> 
> (7) Features marked as "at risk":
> 
> There are no features at risk
> 
> 
> (8) Implementation information:
> 
> Information on interop test cases and testing are here: http://www.w3.org/2008/xmlsec/wiki/Interop
> 
> The working group intends to issue a call for implementations and demonstrate at least two interoperable implementations before requesting advancement to PR.
> 
> 
> (9) Patent Disclosures
> 
> There have been no patent disclosures received for any of these specifications
> 
> thanks
> Bob
> 
> Bob Freund
> Chair WS-Resource-Access WG
> 
>