Difference between revisions of "BP Timetable"

From Government Linked Data (GLD) Working Group Wiki
Jump to: navigation, search
(Changed transition to CR to 02 May (W3C publication date))
(Updated to reflect chairs' call on 19 March.)
Line 22: Line 22:
 
! Milestone / activity !! Target date(s) !! What needs to be done  
 
! Milestone / activity !! Target date(s) !! What needs to be done  
 
|-
 
|-
| class="doc0" | Transition to Last Call || 2013-03-26 || Last Call announcement
+
| class="doc0" | Publish as First Public Working Draft || 2013-03-26 ||
 +
* The Chair sends a transition request to the Domain Lead
 +
* The document is published (email to the Webmaster)
 +
* The chair sends an announcement to the W3C chairs mailing list and to the Working Group.
 +
(From http://www.w3.org/2005/08/01-transitions.html )
 +
|-
 +
| class="doc0" | FPWD Comment period || 2013-03-26 - 2013-04-10 ||
 +
* Record the group's decision to request advancement.
 +
* Fulfill the relevant requirements of the Working Group charter and those of any accompanying requirements documents, or report which relevant requirements have not been fulfilled.
 +
* Indicate which dependencies with other groups the Working Group believes it has satisfied, and report which dependencies have not been satisfied.
 +
(From http://www.w3.org/2005/10/Process-20051014/tr#last-call )
 +
* Preparation of mailing list for comments.
 +
(From http://www.w3.org/2005/08/01-transitions.html )
 +
|-
 +
| class="doc0" | Transition to Last Call || 2013-04-16 || Last Call announcement
 
* Record the group's decision to request advancement.  
 
* Record the group's decision to request advancement.  
 
* Fulfill the relevant requirements of the Working Group charter and those of any accompanying requirements documents, or report which relevant requirements have not been fulfilled.  
 
* Fulfill the relevant requirements of the Working Group charter and those of any accompanying requirements documents, or report which relevant requirements have not been fulfilled.  
Line 30: Line 44:
 
(From http://www.w3.org/2005/08/01-transitions.html )
 
(From http://www.w3.org/2005/08/01-transitions.html )
 
|-
 
|-
| class="doc0" | Last Call Period || 2013-03-26 - 2013-04-16 for comments ||  
+
| class="doc0" | Last Call Period || 2013-04-16 - 2013-05-07 for comments ||  
* Comment period should be at least three weeks long.
+
A Working Group develops the document during this period. Public review and feedback to the Working Group is welcome during this period.  
* External issues are raised; the Working Group must resolve them.
+
(from http://www.w3.org/Consortium/Process/Process-19991111/tr.html#RecsWD )
* Working drafts modified as necessary.
+
(from http://www.w3.org/Consortium/Process/Process-19991111/tr.html#last-call )
+
 
* Nominated working group participant gathers all comments onto a web page; ensures the working group reviews and responds to them.
 
* Nominated working group participant gathers all comments onto a web page; ensures the working group reviews and responds to them.
* [[F2F3]] on 2013-04-11 and 2013-04-12 can be used to review comments.
+
* [[F2F3]] on 2013-04-11 and 2013-04-12 will be used to review comments.
 
|-
 
|-
| class="doc0" | Last Call transition to Candidate Recommendation || 2013-05-02 ||  
+
| class="doc0" | Last Call transition to Candidate Recommendation || 2013-05-21 ||  
 
* Resolution by the Working Group to request the transition.
 
* Resolution by the Working Group to request the transition.
 
* Notification of W3C working groups with dependencies that a Last Call is coming.
 
* Notification of W3C working groups with dependencies that a Last Call is coming.

Revision as of 14:50, 19 March 2013

Timetable and checklist for Best Practices

This is a working page for the Government Linked Data working group. It may be subject to change/revision at any time.

Overview

Status of Deliverables
Editor's Draft w3.org/TR Timetable Target Status
(Early May)
Tracker Contact Notes
Best Practices FPWD+LC on 26-Mar CR tracker Bernadette Hyland

This table is duplicated on the wiki's main page.

Detailed timetable and checklist

W3C Technical Report Development Process
Milestone / activity Target date(s) What needs to be done
Publish as First Public Working Draft 2013-03-26
  • The Chair sends a transition request to the Domain Lead
  • The document is published (email to the Webmaster)
  • The chair sends an announcement to the W3C chairs mailing list and to the Working Group.

(From http://www.w3.org/2005/08/01-transitions.html )

FPWD Comment period 2013-03-26 - 2013-04-10
  • Record the group's decision to request advancement.
  • Fulfill the relevant requirements of the Working Group charter and those of any accompanying requirements documents, or report which relevant requirements have not been fulfilled.
  • Indicate which dependencies with other groups the Working Group believes it has satisfied, and report which dependencies have not been satisfied.

(From http://www.w3.org/2005/10/Process-20051014/tr#last-call )

  • Preparation of mailing list for comments.

(From http://www.w3.org/2005/08/01-transitions.html )

Transition to Last Call 2013-04-16 Last Call announcement
  • Record the group's decision to request advancement.
  • Fulfill the relevant requirements of the Working Group charter and those of any accompanying requirements documents, or report which relevant requirements have not been fulfilled.
  • Indicate which dependencies with other groups the Working Group believes it has satisfied, and report which dependencies have not been satisfied.

(From http://www.w3.org/2005/10/Process-20051014/tr#last-call )

  • Preparation of mailing list for comments.

(From http://www.w3.org/2005/08/01-transitions.html )

Last Call Period 2013-04-16 - 2013-05-07 for comments

A Working Group develops the document during this period. Public review and feedback to the Working Group is welcome during this period. (from http://www.w3.org/Consortium/Process/Process-19991111/tr.html#RecsWD )

  • Nominated working group participant gathers all comments onto a web page; ensures the working group reviews and responds to them.
  • F2F3 on 2013-04-11 and 2013-04-12 will be used to review comments.
Last Call transition to Candidate Recommendation 2013-05-21
  • Resolution by the Working Group to request the transition.
  • Notification of W3C working groups with dependencies that a Last Call is coming.
  • Request for the transition meeting, to include:
    • Record of the Working Group's decision to request the transition
    • Record of important changes to the document
    • Evidence that the document satisfies the Working Group's requirements
    • Evidence that dependencies with other groups are met (or not)
    • Evidence that the document has received wide review
    • Evidence that issues have been formally addressed
    • Objections
    • Implementation information
    • Patent disclosures

(from http://www.w3.org/2005/08/01-transitions.html )

Call for Implementations (Candidate Rec period)
  • Gather implementations.

(from http://www.w3.org/2005/10/Process-20051014/tr#cfi )

  • Note: When a Working Group "skips CR", then for the transition to Proposed Recommendation, the Working Group must satisfy both the requirements to advance to CR and to advance to PR.

(from http://www.w3.org/2005/08/01-transitions.html#transreq )

Call for review of a Proposed Recommendation (Transition to Proposed Rec)
  • Request for transition, which asks the Working Group to:
    • Record the group's decision to request advancement.
    • Provide public documentation of all changes (both substantive and minor) to the technical report 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. Other changes (e.g., clarifications, bug fixes, editorial repairs, and minor error corrections) are minor changes.
    • Report which, if any, of the Working Group's requirements for this document have changed since the previous step.
    • Report any changes in dependencies with other groups.
    • Show evidence of wide review.
    • Formally address all issues raised about the document since the previous step.
    • Report any Formal Objections.

(from http://www.w3.org/2005/10/Process-20051014/tr#transition-reqs )

  • Additionally, the Working Group has:
    • Shown that each feature of the technical report has been implemented. Preferably, the Working Group SHOULD be able to demonstrate two interoperable implementations of each feature. If the Director believes that immediate Advisory Committee review is critical to the success of a technical report, the Director MAY accept to Call for Review of a Proposed Recommendation even without adequate implementation experience;
    • Satisfied any other announced entrance criteria (e.g., any included in the request to advance to Candidate Recommendation, or announced at Last Call if the Working Group does not intend to issue a Call for Implementations).

(from http://www.w3.org/2005/10/Process-20051014/tr#cfi )

Review of a Proposed Recommendation
  • The announcement begins a review period that MUST last at least four weeks.
  • During the review period, the Working Group requests endorsement and support from Members (e.g., testimonials as part of a press release).

(from http://www.w3.org/2005/10/Process-20051014/tr#cfr )

Publication of a 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. The decision to advance a document to Recommendation is a W3C decision.

(from http://www.w3.org/2005/10/Process-20051014/tr#rec-publication )