From 15f93f34b81a7d6c91aa4462abc818e34d342011 Mon Sep 17 00:00:00 2001 From: plehegar Date: Thu, 30 Sep 2021 18:10:10 -0400 Subject: [PATCH 01/15] Initial stab at living CR/REC --- process/living-cr-rec.html | 121 +++++++++++++++++++++++++++++++++++++ 1 file changed, 121 insertions(+) create mode 100644 process/living-cr-rec.html diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html new file mode 100644 index 000000000..14001733f --- /dev/null +++ b/process/living-cr-rec.html @@ -0,0 +1,121 @@ + + + + + Candidate Recommendation Snapshots and Recommendations + + + + + + +
+

Introduction

+ +

+ This document is intended to help Working Groups in deciding whether to + maintain a document using revised Candidate Recommendations or revised Recommendations. +

+

W3C Process

+

The W3C Process offers two ways to maintain a document on the Recommendation track:

+
+
Revising a Candidate Recommendation
+
+ Candidate Recommendation Snapshots get similar patent commitments to W3C Recommendations but do not get + endorsed by W3C as standards for the Web. The document can be revised rapidly by publishing Candidate + Recommendation Drafts on a daily basis. +
+
Recommendations
+
+ Recommendations are endorsed by W3C as standards for the Web. The document can be revised rapidly by publishing candidate + corrections/additions on a daily basis. +
+
+ +

When should a Group keep a document as a Candidate Recommendation?

+ +

+ A document remains in Candidate Recommendation if one or more of the conditions apply: +

+
    +
  1. Unresolved issues that prevent any meaningful/core subset of the document to move forward
    2. +
  2. Insufficient test coverage to demonstrate adequate implementation experience
    3. +
  3. Insufficient adequate implementation experience
    4. +
+ +

When should a Group keep a document as a Recommendation?

+ +

+ A document remains in Recommendation if one or more of the conditions apply: +

+
    +
  1. A meaningful/core subset of the document can be normative and received adequate implementation experience
    2. +
  2. Future corrections and improvements can be dealt through a revision of the Recommendation, including for new features
    3. +
+

Note: A Working Group should not move to Proposed Recommendations without considering how to maintain/revise the future Recommendation.

+ +

Ensuring the future of your Recommendation

+

+ Here are considerations to allow a Recommendation to be revised: +

+ + +
+
plh@w3.org
+ + From e7c25bcb944e8a4b21b422a7fb2b4ab4817a6298 Mon Sep 17 00:00:00 2001 From: plehegar Date: Fri, 14 Jan 2022 08:18:37 -0500 Subject: [PATCH 02/15] Put more emphasis on Recommendation --- process/living-cr-rec.html | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html index 14001733f..280d2debf 100644 --- a/process/living-cr-rec.html +++ b/process/living-cr-rec.html @@ -92,6 +92,16 @@

When should a Group keep a document as a Candidate Recommendation?Insufficient adequate implementation experience +

When should a Group move to Recommendation?

+

+ Unless one or more of the 3 conditions to remain in Candidate Recommendation are valid, a Working Group is strongly + encouraged to move forward to Recommendation. +

+

+ Getting to Recommendation is the only way to receive the full endorsement from the W3C for a technical specification. + Candidate Recommendations are not endorsed by W3C. +

+

When should a Group keep a document as a Recommendation?

From 7cd538790546c8188e9d3b8e1c7d83359a6d3243 Mon Sep 17 00:00:00 2001 From: plehegar Date: Fri, 14 Jan 2022 08:26:42 -0500 Subject: [PATCH 03/15] Suggests moving back to Note track --- process/living-cr-rec.html | 3 +++ 1 file changed, 3 insertions(+) diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html index 280d2debf..f3f7331ca 100644 --- a/process/living-cr-rec.html +++ b/process/living-cr-rec.html @@ -92,6 +92,9 @@

When should a Group keep a document as a Candidate Recommendation?Insufficient adequate implementation experience +

If unresolved technical issues remain for long period of time due to the impossibility of finding technical + solutions, the Working Group should consider moving the document on the Note track.

+

When should a Group move to Recommendation?

Unless one or more of the 3 conditions to remain in Candidate Recommendation are valid, a Working Group is strongly From e1a79cb67243340fc24a735dc36aa3c42fd2e0bd Mon Sep 17 00:00:00 2001 From: Philippe Le Hegaret Date: Thu, 20 Jan 2022 15:27:35 -0500 Subject: [PATCH 04/15] Update process/living-cr-rec.html Co-authored-by: Nigel Megitt --- process/living-cr-rec.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html index f3f7331ca..9b344e858 100644 --- a/process/living-cr-rec.html +++ b/process/living-cr-rec.html @@ -93,7 +93,8 @@

When should a Group keep a document as a Candidate Recommendation?

If unresolved technical issues remain for long period of time due to the impossibility of finding technical - solutions, the Working Group should consider moving the document on the Note track.

+ solutions, the Working Group should consider moving the document to a Discontinued Draft or, + if there are no IPR issues, to the Note track.

When should a Group move to Recommendation?

From 97a2b2d13dcc64e244a00250e66187441a506955 Mon Sep 17 00:00:00 2001 From: plehegar Date: Tue, 25 Jan 2022 13:32:28 -0500 Subject: [PATCH 05/15] Consider moving it to Discontinued --- process/living-cr-rec.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html index 9b344e858..379fc9a28 100644 --- a/process/living-cr-rec.html +++ b/process/living-cr-rec.html @@ -93,8 +93,7 @@

When should a Group keep a document as a Candidate Recommendation?

If unresolved technical issues remain for long period of time due to the impossibility of finding technical - solutions, the Working Group should consider moving the document to a Discontinued Draft or, - if there are no IPR issues, to the Note track.

+ solutions, the Working Group should consider moving the document to the Discontinued Draft status.

When should a Group move to Recommendation?

From 602517f8e499a11f8a4e877eb0602cec249efee1 Mon Sep 17 00:00:00 2001 From: plehegar Date: Tue, 25 Jan 2022 13:32:43 -0500 Subject: [PATCH 06/15] Moving a REC back to WD or CR --- process/living-cr-rec.html | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html index 379fc9a28..38b606a48 100644 --- a/process/living-cr-rec.html +++ b/process/living-cr-rec.html @@ -128,6 +128,17 @@

Ensuring the future of your Recommendation

  • Once proper reviews are done, proposed corrections and proposed additions can be made normative.
    • +

    When should a Group move a Recommendation back to Working Draft or Candidate Recommendation?

    + +

    + A document should be moved back to Working Draft or Candidate Recommendation if one or more of the conditions apply: +

    +
      +
    1. New features and the
      2. +
    2. Future corrections and improvements can be dealt through a revision of the Recommendation, including for new features
      3. +
    +

    Note: A Working Group should not move to Proposed Recommendations without considering how to maintain/revise the future Recommendation.

    +
    plh@w3.org
    From 6fe4d6301aa85e17f8d889cc7378662fe77c5a62 Mon Sep 17 00:00:00 2001 From: Philippe Le Hegaret Date: Tue, 1 Feb 2022 11:15:42 -0500 Subject: [PATCH 07/15] s/Insufficient adequate/Inadequate/ Co-authored-by: Wendy Seltzer --- process/living-cr-rec.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html index 38b606a48..30a059cd1 100644 --- a/process/living-cr-rec.html +++ b/process/living-cr-rec.html @@ -89,7 +89,7 @@

    When should a Group keep a document as a Candidate Recommendation?
  • Unresolved issues that prevent any meaningful/core subset of the document to move forward
  • Insufficient test coverage to demonstrate adequate implementation experience
    • -
  • Insufficient adequate implementation experience
    • +
  • Inadequate implementation experience

    • If unresolved technical issues remain for long period of time due to the impossibility of finding technical From 8699b84f97bf0b9b2120e5da44b180058ec052a6 Mon Sep 17 00:00:00 2001 From: Philippe Le Hegaret Date: Tue, 1 Feb 2022 11:16:26 -0500 Subject: [PATCH 08/15] Move to REC asap Co-authored-by: chaals --- process/living-cr-rec.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html index 30a059cd1..27851d6e6 100644 --- a/process/living-cr-rec.html +++ b/process/living-cr-rec.html @@ -97,7 +97,7 @@

    When should a Group keep a document as a Candidate Recommendation?When should a Group move to Recommendation?

    - Unless one or more of the 3 conditions to remain in Candidate Recommendation are valid, a Working Group is strongly + As soon as it is ready. Unless one or more of the 3 conditions to remain in Candidate Recommendation are valid, a Working Group is strongly encouraged to move forward to Recommendation.

    From cdd085062e7ffb6e0adf13bc672bf51bd42fd3ab Mon Sep 17 00:00:00 2001 From: Philippe Le Hegaret Date: Tue, 1 Feb 2022 11:21:16 -0500 Subject: [PATCH 09/15] Update process/living-cr-rec.html Co-authored-by: chaals --- process/living-cr-rec.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html index 27851d6e6..865837806 100644 --- a/process/living-cr-rec.html +++ b/process/living-cr-rec.html @@ -114,7 +114,7 @@

    When should a Group keep a document as a Recommendation?

  • A meaningful/core subset of the document can be normative and received adequate implementation experience
  • Future corrections and improvements can be dealt through a revision of the Recommendation, including for new features
    • -

    Note: A Working Group should not move to Proposed Recommendations without considering how to maintain/revise the future Recommendation.

    +

    Note: A Working Group should not move a specification to Proposed Recommendation without considering how to maintain/revise the future Recommendation.

    Ensuring the future of your Recommendation

    From 11f7539ac7d706f201608e24a6c4a9860d22cfcc Mon Sep 17 00:00:00 2001 From: Philippe Le Hegaret Date: Tue, 1 Feb 2022 11:21:22 -0500 Subject: [PATCH 10/15] Update process/living-cr-rec.html Co-authored-by: chaals --- process/living-cr-rec.html | 1 - 1 file changed, 1 deletion(-) diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html index 865837806..71fc17db0 100644 --- a/process/living-cr-rec.html +++ b/process/living-cr-rec.html @@ -137,7 +137,6 @@

    When should a Group move a Recommendation back to Working Draft or
  • New features and the
  • Future corrections and improvements can be dealt through a revision of the Recommendation, including for new features
    • -

    Note: A Working Group should not move to Proposed Recommendations without considering how to maintain/revise the future Recommendation.

    plh@w3.org
    From d04c48250c9b1eafeee79b0ab0cd4226785af02e Mon Sep 17 00:00:00 2001 From: Philippe Le Hegaret Date: Tue, 1 Feb 2022 11:22:27 -0500 Subject: [PATCH 11/15] Update process/living-cr-rec.html Co-authored-by: chaals --- process/living-cr-rec.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html index 71fc17db0..c348f1a60 100644 --- a/process/living-cr-rec.html +++ b/process/living-cr-rec.html @@ -92,7 +92,7 @@

    When should a Group keep a document as a Candidate Recommendation?Inadequate implementation experience -

    If unresolved technical issues remain for long period of time due to the impossibility of finding technical +

    If technical issues remain unresolved for a long time, solutions, the Working Group should consider moving the document to the Discontinued Draft status.

    When should a Group move to Recommendation?

    From 97beb2aace27b120cb40fb8dc0baa104d1df5252 Mon Sep 17 00:00:00 2001 From: Philippe Le Hegaret Date: Fri, 2 Sep 2022 07:49:39 -0400 Subject: [PATCH 12/15] Update process/living-cr-rec.html Co-authored-by: chaals --- process/living-cr-rec.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html index c348f1a60..3332696bf 100644 --- a/process/living-cr-rec.html +++ b/process/living-cr-rec.html @@ -84,7 +84,7 @@

    W3C Process

    When should a Group keep a document as a Candidate Recommendation?

    - A document remains in Candidate Recommendation if one or more of the conditions apply: + A document is not ready to advance to Recommendation if one or more of the conditions apply:

    1. Unresolved issues that prevent any meaningful/core subset of the document to move forward
      2. From d9fffd48837b4ff9e58f7da1422ff77dcd472982 Mon Sep 17 00:00:00 2001 From: Philippe Le Hegaret Date: Fri, 2 Sep 2022 07:49:43 -0400 Subject: [PATCH 13/15] Update process/living-cr-rec.html Co-authored-by: chaals --- process/living-cr-rec.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html index 3332696bf..db9abbe93 100644 --- a/process/living-cr-rec.html +++ b/process/living-cr-rec.html @@ -87,7 +87,7 @@

      When should a Group keep a document as a Candidate Recommendation?
        -
      1. Unresolved issues that prevent any meaningful/core subset of the document to move forward
        2. +
      2. Unresolved issues prevent any useful subset of the document moving forward
      3. Insufficient test coverage to demonstrate adequate implementation experience
      4. Inadequate implementation experience
      From 1984e8028af07c1fb706d9d69823b512f04da5f6 Mon Sep 17 00:00:00 2001 From: plehegar Date: Fri, 2 Sep 2022 07:56:12 -0400 Subject: [PATCH 14/15] One condition to move back to WD or CR --- process/living-cr-rec.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html index db9abbe93..2b59ec4d2 100644 --- a/process/living-cr-rec.html +++ b/process/living-cr-rec.html @@ -134,8 +134,7 @@

      When should a Group move a Recommendation back to Working Draft or A document should be moved back to Working Draft or Candidate Recommendation if one or more of the conditions apply:

        -
      1. New features and the
        2. -
      2. Future corrections and improvements can be dealt through a revision of the Recommendation, including for new features
        3. +
      3. The document was improperly moved to Recommendation
      From 44f298f17e2247338480cc032e92a758865902fd Mon Sep 17 00:00:00 2001 From: plehegar Date: Wed, 7 Sep 2022 15:07:08 -0400 Subject: [PATCH 15/15] Remove HTML comment --- process/living-cr-rec.html | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/process/living-cr-rec.html b/process/living-cr-rec.html index 2b59ec4d2..c8f94fb2f 100644 --- a/process/living-cr-rec.html +++ b/process/living-cr-rec.html @@ -43,21 +43,6 @@

      Candidate Recommendation Snapshots and Recommendations

      This Guidebook is the collected wisdom of the W3C Group Chairs and other collaborators.

    -

    Introduction