W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > September 2011

Request to progress to Proposed Recommendation for seven specifications

From: Bob Freund <bob.freund@hitachisoftware.com>
Date: Tue, 13 Sep 2011 18:02:55 -0400
Message-Id: <24C7E615-AF48-47D5-A163-08C2E158B66A@hitachisoftware.com>
Cc: public-ws-resource-access@w3.org
To: chairs@w3.org, Tim Berners-Lee <timbl@w3.org>, Philippe Le Hegaret <plh@w3.org>, Yves Lafon <ylafon@w3.org>, Thomas Roessler <tlr@w3.org>
Dear Colleagues

The WS-Resource Access working group requests transition to Proposed Recommendation 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/pr/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/pr/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/pr/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/pr/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/pr/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/pr/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/pr/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 decision was recorded in the 19 July 2011 minutes[2.1]

[2.1] http://www.w3.org/2002/ws/ra/11/07/2011-07-19.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.
There has been no change to this position since cr was initiated.

[4.1] http://www.w3.org/2008/11/ws-ra-charter.html

[5] Evidence that dependencies with other groups has been met.
The OASIS SCA-Assembly specification is now referencing the WS-Event Description specification since they believe it meets their needs.
Other reviewers have indicated their satisfaction with previous comments.  Other outside working groups such as DMTF WS-Man, plan future revisions to their specifications utilizing the new w3 versions.

(6) Evidence that the documents have received wide review and that issues have been formally addressed:
Comments received during CR[6.1]: 35
CR Comments from external reviewers[6.2]: 1
The one logged external comment was resolved consistent with the reviewers request.

There was an additional comment received but not logged[6.3] and was interpreted as a request for information rather than a comment on the specification.  It was answered[6.4] and no further communication has been received.

[6.1] http://tinyurl.com/6deh7qo
[6.2] http://tinyurl.com/6e864lg
[6.3] http://lists.w3.org/Archives/Public/public-ws-resource-access-comments/2011Jun/0000.html
[6.4] http://lists.w3.org/Archives/Public/public-ws-resource-access-comments/2011Jul/0004.html


(7) Objections:

There was one formal objection received[7.1].  This has been previously recorded and discussed during the cr review.  There have been no new formal objections during cr.

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.

During the CR review call it was asked if the potential issue could be tested to be proved to not exist.  This was discussed during WG meetings and the issue originator issued a subsequent email[6.3].  The WG does not believe that it is testable in a practical sense since it would require the construction of special non-conformant test clients and would require the testing of schema validity not otherwise mandated by the specification.

[7.1] http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jun/0014.html
[7.2] http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Dec/0023.html
[7.3] http://lists.w3.org/Archives/Public/public-ws-resource-access/2011May/0003.html


(8) Implementation information:

Information on interop test cases and scenarios are here: http://www.w3.org/2002/ws/ra/test/scenario.html
Test results are listed in a test report at http://www.w3.org/2002/ws/ra/test/testResults.html with numbers referenced back to the test scenarios document.  The results indicate that there are at least two interoperable implementations of all specifications.



(9) Patent Disclosures

There have been no patent disclosures received for any of these specifications

thanks
Bob

Bob Freund
Chair WS-Resource-Access WG
Received on Tuesday, 13 September 2011 22:03:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 13 September 2011 22:03:44 GMT