From 8befd90145e400458897d88c27ddea69dd33dcea Mon Sep 17 00:00:00 2001 From: fantasai Date: Mon, 11 Dec 2023 22:09:03 -0500 Subject: [PATCH 1/6] Reduce confusion wrt registry sections #800 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Rename “registry section” to “embedded registry”. * Move paragraph about Patent Policy to its own section. * Remove the words “purely documentational” because it's easy to confuse with “informative” / “non-normative”. * Add “(only)” to the sentence making registries non-normative for Patent Policy purposes. --- index.bs | 31 +++++++++++++++++++------------ 1 file changed, 19 insertions(+), 12 deletions(-) diff --git a/index.bs b/index.bs index 067f1970..95d52670 100644 --- a/index.bs +++ b/index.bs @@ -2844,7 +2844,7 @@ Types of Technical Reports in order to document collections of values or other data. These are typically published in a separate [=registry report=], although they can also be directly embedded in [=Recommendation Track=] documents - as a [=registry section=]. + as a [=embedded registry=]. [=registry definition|Defining a registry=] requires [=wide review=] and [=consensus=], but once set up, changes to registry entries are lightweight and can even be done without a [=Working Group=]. @@ -4672,20 +4672,12 @@ Publishing Registries [=Registries=] can be published either as a stand-alone [=technical report=] on the [=Registry Track=] called a registry report, - or incorporated as part of a [=Recommendation=] as a registry section. + or incorporated as part of a [=Recommendation=] as a embedded registry. - A [=registry report=] or [=registry section=] - is purely documentational, - is not subject to the W3C Patent Policy, - and must not contain any requirements on implementations. - For the purposes of the Patent Policy [[PATENT-POLICY]], - any [=registry section=] in a [=Recommendation track=] document - is not a normative portion of that specification. - - The [=registry report=] or [=registry section=] must: + The [=registry report=] or [=embedded registry=] must: From 7ca39250850714dc22cb9d779bc1c25e29a277ce Mon Sep 17 00:00:00 2001 From: Florian Rivoal Date: Wed, 13 Dec 2023 10:58:07 +0900 Subject: [PATCH 2/6] Update index.bs Co-authored-by: Chris Needham --- index.bs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.bs b/index.bs index 95d52670..19dcee17 100644 --- a/index.bs +++ b/index.bs @@ -2844,7 +2844,7 @@ Types of Technical Reports in order to document collections of values or other data. These are typically published in a separate [=registry report=], although they can also be directly embedded in [=Recommendation Track=] documents - as a [=embedded registry=]. + as an [=embedded registry=]. [=registry definition|Defining a registry=] requires [=wide review=] and [=consensus=], but once set up, changes to registry entries are lightweight and can even be done without a [=Working Group=]. From 886427a5acc7ada28210f26c85b97ece4966443e Mon Sep 17 00:00:00 2001 From: Florian Rivoal Date: Wed, 13 Dec 2023 10:58:18 +0900 Subject: [PATCH 3/6] Update index.bs Co-authored-by: Chris Needham --- index.bs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.bs b/index.bs index 19dcee17..97184a4c 100644 --- a/index.bs +++ b/index.bs @@ -4672,7 +4672,7 @@ Publishing Registries [=Registries=] can be published either as a stand-alone [=technical report=] on the [=Registry Track=] called a registry report, - or incorporated as part of a [=Recommendation=] as a embedded registry. + or incorporated as part of a [=Recommendation=] as an embedded registry. The [=registry report=] or [=embedded registry=] must:
    From 17f2d3f918d59068478a9ed2f1296b185586db0b Mon Sep 17 00:00:00 2001 From: Florian Rivoal Date: Wed, 13 Dec 2023 10:58:31 +0900 Subject: [PATCH 4/6] Update index.bs Co-authored-by: Chris Needham --- index.bs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.bs b/index.bs index 97184a4c..e6840a47 100644 --- a/index.bs +++ b/index.bs @@ -4677,7 +4677,7 @@ Publishing Registries The [=registry report=] or [=embedded registry=] must:
    • - Clearly label the [=registry report=]/[=embedded registry=], + Clearly label the [=registry report=] or [=embedded registry=], its [=registry tables|tables=], and its [=registry definitions=] as such, including a link to [[#registries]] in this Process. From 4227e84e63e1014a6bac1e525d4e10e01f8f3299 Mon Sep 17 00:00:00 2001 From: Florian Rivoal Date: Wed, 13 Dec 2023 10:59:14 +0900 Subject: [PATCH 5/6] Update index.bs Co-authored-by: Nigel Megitt --- index.bs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.bs b/index.bs index e6840a47..708e8514 100644 --- a/index.bs +++ b/index.bs @@ -2842,8 +2842,8 @@ Types of Technical Reports
      [=Working Groups=] can also publish [=registries=] in order to document collections of values or other data. - These are typically published in a separate [=registry report=], - although they can also be directly embedded in [=Recommendation Track=] documents + These can either be published in a [=registry report=], + or directly embedded in [=Recommendation Track=] documents as an [=embedded registry=]. [=registry definition|Defining a registry=] requires [=wide review=] and [=consensus=], but once set up, changes to registry entries are lightweight From 2e75ddd9c2819942bdb5ecac70208c184d220825 Mon Sep 17 00:00:00 2001 From: Florian Rivoal Date: Thu, 25 Jan 2024 01:04:35 +0900 Subject: [PATCH 6/6] Phrasing clarification Co-authored-by: Ted Thibodeau Jr --- index.bs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.bs b/index.bs index 708e8514..35dad91a 100644 --- a/index.bs +++ b/index.bs @@ -2842,8 +2842,8 @@ Types of Technical Reports
      [=Working Groups=] can also publish [=registries=] in order to document collections of values or other data. - These can either be published in a [=registry report=], - or directly embedded in [=Recommendation Track=] documents + A registry can be published either as a distinct [=registry report=], + or directly within [=Recommendation Track=] a document as an [=embedded registry=]. [=registry definition|Defining a registry=] requires [=wide review=] and [=consensus=], but once set up, changes to registry entries are lightweight