Fixes #100

w3c · Jul 29, 2022 · df320eb · df320eb
1 parent d46bf2a
commit df320eb
Show file tree

Hide file tree

Showing 2 changed files with 29 additions and 1 deletion.
diff --git a/documents-respec.html b/documents-respec.html
@@ -244,6 +244,10 @@ <h2>Other documents</h2>
 <section id=notes>
   <h2>W3C Note track</h2>
 
+  <p><a href='https://www.w3.org/Consortium/Process/#recs-and-notes'>W3C
+    Notes and W3C Statements</a> are published to either to document information
+    other than technical specifications, such as use cases motivating a
+    specification and best practices for its use.</p>
 
   <section id=DNOTE>
     <h2>Draft Note</h2>
@@ -305,6 +309,10 @@ <h2>Statements</h2>
   </section>
   <section id='registries'>
       <h2>W3C Registry Track</h2>
+
+      <p><a href='https://www.w3.org/Consortium/Process/#recs-and-notes'>Registries</a>
+      are published to document collections of values or other data.</p>
+
       <section id='DRY'>
       <h2>Draft Registry</h2>
 
@@ -378,6 +386,10 @@ <h2>W3C Standardization track</h2>
 
 <p>The classes of specifications listed in this section have received different levels of review by W3C Members, by software developers, and by other W3C groups and interested parties according to W3C Process. These specifications are intended to eventually receive endorsement by W3C.
 
+<p><a href='https://www.w3.org/Consortium/Process/#recs-and-notes'>Technical
+  reports on the W3C Recommendation Track</a> are developed in order to ultimately
+  produce normative specifications or guidelines as standards for the Web.</p>
+
 <section id=WD>
   <h2>Working Draft</h2>
 

diff --git a/documents.html b/documents.html
@@ -23,8 +23,11 @@
 .dfn-panel.docked{position:fixed;left:.5em;top:unset;bottom:2em;margin:0 auto;max-width:calc(100vw - .75em * 2 - .5em - .2em * 2);max-height:30vh;overflow:auto}
 </style>
 
+
 <title>Documents published at W3C</title>
 
+
+
 <style id="respec-mainstyle">
 @keyframes pop{
 0%{transform:scale(1,1)}
@@ -110,6 +113,7 @@
 
 
 <body class="h-entry informative"><div class="head">
+
     <h1 id="title" class="title">Documents published at W3C</h1>
   </div>
 <section id="abstract" class="introductory"><h2>Abstract</h2>
@@ -323,6 +327,10 @@ <h1 id="title" class="title">Documents published at W3C</h1>
 <section id="notes"><div class="header-wrapper"><h3 id="x2-5-w3c-note-track"><bdi class="secno">2.5 </bdi><abbr title="World Wide Web Consortium">W3C</abbr> Note track</h3><a class="self-link" href="#notes" aria-label="Permalink for Section 2.5"></a></div>
 
 
+  <p><a href="https://www.w3.org/Consortium/Process/#recs-and-notes"><abbr title="World Wide Web Consortium">W3C</abbr>
+    Notes and <abbr title="World Wide Web Consortium">W3C</abbr> Statements</a> are published to either to document information
+    other than technical specifications, such as use cases motivating a
+    specification and best practices for its use.</p>
 
   <section id="DNOTE"><div class="header-wrapper"><h4 id="x2-5-1-draft-note"><bdi class="secno">2.5.1 </bdi>Draft Note</h4><a class="self-link" href="#DNOTE" aria-label="Permalink for Section 2.5.1"></a></div>
 
@@ -384,6 +392,10 @@ <h1 id="title" class="title">Documents published at W3C</h1>
   </section>
   <section id="registries"><div class="header-wrapper"><h2 id="x3-w3c-registry-track"><bdi class="secno">3. </bdi><abbr title="World Wide Web Consortium">W3C</abbr> Registry Track</h2><a class="self-link" href="#registries" aria-label="Permalink for Section 3."></a></div>
 
+
+      <p><a href="https://www.w3.org/Consortium/Process/#recs-and-notes">Registries</a>
+      are published to document collections of values or other data.</p>
+
       <section id="DRY"><div class="header-wrapper"><h3 id="x3-1-draft-registry"><bdi class="secno">3.1 </bdi>Draft Registry</h3><a class="self-link" href="#DRY" aria-label="Permalink for Section 3.1"></a></div>
 
 
@@ -457,7 +469,11 @@ <h1 id="title" class="title">Documents published at W3C</h1>
 
 <p>The classes of specifications listed in this section have received different levels of review by <abbr title="World Wide Web Consortium">W3C</abbr> Members, by software developers, and by other <abbr title="World Wide Web Consortium">W3C</abbr> groups and interested parties according to <abbr title="World Wide Web Consortium">W3C</abbr> Process. These specifications are intended to eventually receive endorsement by <abbr title="World Wide Web Consortium">W3C</abbr>.
 
-</p><section id="WD"><div class="header-wrapper"><h3 id="x4-1-working-draft"><bdi class="secno">4.1 </bdi>Working Draft</h3><a class="self-link" href="#WD" aria-label="Permalink for Section 4.1"></a></div>
+</p><p><a href="https://www.w3.org/Consortium/Process/#recs-and-notes">Technical
+  reports on the <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation Track</a> are developed in order to ultimately
+  produce normative specifications or guidelines as standards for the Web.</p>
+
+<section id="WD"><div class="header-wrapper"><h3 id="x4-1-working-draft"><bdi class="secno">4.1 </bdi>Working Draft</h3><a class="self-link" href="#WD" aria-label="Permalink for Section 4.1"></a></div>
 
 
 <p>A Working Draft is a document that <abbr title="World Wide Web Consortium">W3C</abbr> has published for review and for simple historical reference. A Working Draft is a work in progress and the content is not required to have full consensus of the Group participants, though the Group must have consensus to publish the draft. Per the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy of September 2020, the first publication of the specification as a Working Draft marks the commencement of formal IPR licensing commitments.