On our way to W3C Recommendation

Philippe Le Hégaret,
W3C Architecture Domain

Web Services Addressing face-to-face

February 25, 2005

W3C Recommendation Track

Going to Last Call

The Working Group believes that:

• It satisfied the relevant technical requirements (e.g., of the charter or requirements document) in the Working Draft
• It satisfied significant dependencies with other groups

The Group needs to:

1. Record the group's decision to request advancement
2. Specify the deadline for review comments (no less than 3 weeks after the announcement);
3. Identify known dependencies and solicit review from all dependent Working Groups;
4. Report unfulfilled requirements or dependencies

The Working Group will announce Last Call

Going to Candidate Recommendation

1. Record the group's decision to request advancement;
2. Indicate whether the document has been modified substantively since the previous step: A substantive change (whether deletion, inclusion, or other modification) is one where someone could reasonably expect that making the change would invalidate an individual's review or implementation experience;
3. Report which, if any, of the Working Group's requirements for this document have changed since the previous step;
4. Report any changes in dependencies with other groups;
5. Show evidence of wide review;
6. Formally address all issues raised;
7. Report any formal objections.

When satisfied, the Director will announce Candidate Recommendation

Formally Addressing an Issue

• Send a substantive response to the reviewer who raised the issue, including the rationale for the decision;
• In case of misunderstanding, the group should seek clarification from the reviewer;
• The group SHOULD reply to a reviewer's initial comments in a timely manner;
• The group SHOULD set a time limit for acknowledgment by a reviewer of the group's substantive response: a reviewer cannot block a group's progress

Formal objections

1. The individual SHOULD cite technical arguments and propose changes that would remove the objection; (these proposals MAY be vague or incomplete).
2. The Chair MUST report it to the Director in the next request to advance the document;
3. If an objection does not include such information (see 1), the Chair is NOT REQUIRED to report it at later review stages.

Going to Proposed Recommendation

1. All general requirements for advancement (i.e. same as Going to Candidate Recommendation)
2. A test suite intended to promote implementation of the Candidate Recommendation, and to assess interoperability between these implementations. (from Web Services Addressing charter)
3. Demonstrate four interoperable implementations during the Call for Implementations step. (from Web Services Addressing charter)
4. Make a report of present and expected implementations

When satisfied, the Director will announce Proposed Recommendation

Going to Recommendation

The Director publishes a W3C Recommendation when satisfied that there is significant support for the technical report from the Advisory Committee, the Team, W3C Working Groups, and the public.

Documents

• W3C Process
• Working Group Charter
• Role of the Group Chair
• Role of the Team Contact