From 0e5585b995f2ce6f81f42ae78da2489b6483da0b Mon Sep 17 00:00:00 2001 From: Florian Rivoal Date: Mon, 21 Jul 2025 20:46:19 +0200 Subject: [PATCH 1/3] Editorial reorg of text defining REC track statuses * Switched the definition of REC track to point to the full list of maturity stages, rather than the summarized version of it. * Move a few paragraphs around, for ease of reading Co-authored-by: fantasai --- index.bs | 39 +++++++++++++++++++-------------------- 1 file changed, 19 insertions(+), 20 deletions(-) diff --git a/index.bs b/index.bs index 9c338336..7b801d25 100644 --- a/index.bs +++ b/index.bs @@ -3468,9 +3468,6 @@ The W3C Recommendation Track
  • Publication as a [=W3C Recommendation=]. - A W3C Recommendation Track document - is any document whose current status is one of the four in the numbered list above. - 
     			path: basic-rec-track.svg
@@ -3478,23 +3475,25 @@ The W3C Recommendation Track
 		
    Non-Normative Summary of the [=Recommendation Track=]
    - This Process defines certain [=Recommendation Track=] publications as Patent Review Drafts. - Under the 2004 Patent Policy (and its 2017 update) [[!PATENT-POLICY-2004]], - these correspond to “Last Call Working Draft” in the Patent Policy; - Starting from the 2020 Patent Policy [[!PATENT-POLICY-2020]], - these correspond to “Patent Review Draft” in the Patent Policy [[!PATENT-POLICY]]. - - W3C may end work on a technical report at any time. - + Only sufficiently technically mature work should be advanced. As described in [[#transition-reqs]], the [=Team=] will decline a request to advance in maturity stage and return the specification to a [=Working Group=] for further work if it determines that the requirements for advancement have not been met. + Note: Should faster advancement to meet scheduling considerations be desired, + this can be achieved by reducing the scope of the technical report to a subset that is adequately mature and deferring + less stable features to other technical reports. + + W3C may end work on a technical report at any time. +

    Maturity Stages on the Recommendation Track

    + A W3C Recommendation Track document + is any document whose current status is one of those described below. +
    Working Draft (WD) @@ -3690,11 +3689,16 @@ Maturity Stages on the Recommendation Track
    - Only sufficiently technically mature work should be advanced. + This Process defines certain [=Recommendation Track=] publications as Patent Review Drafts. + Under the 2004 Patent Policy (and its 2017 update) [[!PATENT-POLICY-2004]], + these correspond to “Last Call Working Draft” in the Patent Policy; + Starting from the 2020 Patent Policy [[!PATENT-POLICY-2020]], + these correspond to “Patent Review Draft” in the Patent Policy [[!PATENT-POLICY]]. - Note: Should faster advancement to meet scheduling considerations be desired, - this can be achieved by reducing the scope of the technical report to a subset that is adequately mature and deferring - less stable features to other technical reports. + [=Working Groups=] and [=Interest Groups=] may make available [=Editor's drafts=]. + Editor's drafts (ED) have no official standing whatsoever, + and do not necessarily imply consensus of a [=Working Group=] or [=Interest Group=], + nor are their contents endorsed in any way by W3C. When publishing an updated version of an existing [=Candidate Recommendation=] or [=Recommendation=], technical reports are expected to meet the same maturity criteria as when they are first published under that status. @@ -3704,11 +3708,6 @@ Maturity Stages on the Recommendation Track it is also permissible to publish an updated [=CR=] or [=REC=] following the usual process, even if only some of these flaws have been satisfactorily addressed. - [=Working Groups=] and [=Interest Groups=] may make available [=Editor's drafts=]. - Editor's drafts (ED) have no official standing whatsoever, - and do not necessarily imply consensus of a [=Working Group=] or [=Interest Group=], - nor are their contents endorsed in any way by W3C. -

    Implementation Experience

    From a53b49999369766d16f2abdaef2be655dc997e29 Mon Sep 17 00:00:00 2001 From: Florian Rivoal Date: Wed, 23 Jul 2025 20:37:35 +0900 Subject: [PATCH 2/3] Use more precise phrasing Co-authored-by: Jeffrey Yasskin --- index.bs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.bs b/index.bs index 7b801d25..6be587e9 100644 --- a/index.bs +++ b/index.bs @@ -3492,7 +3492,7 @@ The W3C Recommendation Track Maturity Stages on the Recommendation Track A W3C Recommendation Track document - is any document whose current status is one of those described below. + is any document whose current status is one of those described in this section.
    From 3ca46152538fd1f202edbdc4ff060b456cf14635 Mon Sep 17 00:00:00 2001 From: Florian Rivoal Date: Wed, 23 Jul 2025 16:44:29 +0200 Subject: [PATCH 3/3] Use more open-ended phrasing --- index.bs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.bs b/index.bs index 6be587e9..c288ae8d 100644 --- a/index.bs +++ b/index.bs @@ -3459,7 +3459,7 @@ The W3C Recommendation Track and if there is support from its Membership, W3C publishes it as a Recommendation. - In summary, the W3C Recommendation Track consists of: + In summary, the main steps of W3C Recommendation Track are:
    1. Publication of the [=First Public Working Draft=].