Maintenance: Rendered delivery items for all three targets

Signed-off-by: Stefan Hagen <stefan@hagen.link>

Author: sthagen

csaf_2.1/prose/share/csaf-v2.1-draft.html

@@ -3736,6 +3736,9 @@ <h3 id="315-language-type-">
         mandatory as most users are used to that.
       </p>
     </blockquote>
+    <p>
+      CSAF Producers SHALL follow the conventions for the capitalization of the subtags. CSAF Validators SHALL treat subtags as case-insensitive unless stated otherwise in the test.
+    </p>
     <p>
       <em>Examples 1:</em><a id='language-type-eg-1'></a><a id='sec-3-1-5-eg-1'></a><a id='example-23'></a>
     </p>
@@ -8452,7 +8455,7 @@ <h3 id="6115-translator-">
       6.1.15 Translator <a id='translator'></a>
     </h3>
     <p>
-      It MUST be tested that <code>/document/source_lang</code> is present if the value <code>translator</code> is used for <code>/document/publisher/category</code>.
+      It MUST be tested that <code>/document/source_lang</code> is present and set if the value <code>translator</code> is used for <code>/document/publisher/category</code>. A CSAF Validator SHALL differentiate in the error message between the key being present but having no or an empty value and not being present at all.
     </p>
     <p>
       The relevant path for this test is:
@@ -8476,6 +8479,11 @@ <h3 id="6115-translator-">
         The required element <code>source_lang</code> is missing.
       </p>
     </blockquote>
+    <blockquote>
+      <p>
+        A tool MAY add the key as a quick fix. In such case, the value still needs to be set - either manually or by other means from the tool, e.g. through a given configuration.
+      </p>
+    </blockquote>
     <h3 id="6116-latest-document-version-">
       6.1.16 Latest Document Version <a id='latest-document-version'></a>
     </h3>
@@ -11539,7 +11547,7 @@ <h3 id="6212-missing-document-language-">
       6.2.12 Missing Document Language <a id='missing-document-language'></a>
     </h3>
     <p>
-      It MUST be tested that the document language member is present.
+      It MUST be tested that the document language member is present and set. A CSAF Validator SHALL differentiate in the error message between the key being present but having no or an empty value and not being present at all.
     </p>
     <p>
       The relevant path for this test is:
@@ -11566,6 +11574,11 @@ <h3 id="6212-missing-document-language-">
         The document language is not defined.
       </p>
     </blockquote>
+    <blockquote>
+      <p>
+        A tool MAY add the key as a quick fix. In such case, the value still needs to be set - either manually or by other means from the tool, e.g. through a given configuration.
+      </p>
+    </blockquote>
     <h3 id="6213-sorting-">
       6.2.13 Sorting <a id='recommended-tests--sorting'></a>
     </h3>
@@ -12930,7 +12943,7 @@ <h3 id="6243-missing-license-expression-">
       6.2.43 Missing License Expression <a id='missing-license-expression'></a>
     </h3>
     <p>
-      It MUST be tested that the license expression is present and set.
+      It MUST be tested that the license expression is present and set. A CSAF Validator SHALL differentiate in the error message between the key being present but having no or an empty value and not being present at all.
     </p>
     <p>
       The relevant path for this test is:
@@ -12952,6 +12965,11 @@ <h3 id="6243-missing-license-expression-">
         The license expression is not defined.
       </p>
     </blockquote>
+    <blockquote>
+      <p>
+        A tool MAY add the key as a quick fix. In such case, the value still needs to be set - either manually or by other means from the tool, e.g. through a given configuration.
+      </p>
+    </blockquote>
     <h3 id="6244-deprecated-license-identifier-">
       6.2.44 Deprecated License Identifier <a id='deprecated-license-identifier'></a>
     </h3>
@@ -17924,7 +17942,7 @@ <h3 id="9114-conformance-clause-14-csaf-basic-validator-">
       </li>
       <li>does not change the CSAF Documents.
       </li>
-      <li>satisfies those normative requirements in sections <a href="#extensions">2.4</a>, <a href="#mandatory-tests">6.1</a>, <a href="#test-presets">6.4</a>, and <a href="#safety-security-and-data-protection-considerations">8</a> that are designated as applying to CSAF Validators.
+      <li>satisfies those normative requirements in sections <a href="#extensions">2.4</a>, <a href="#schema-elements">3</a> <a href="#mandatory-tests">6.1</a>, <a href="#test-presets">6.4</a>, and <a href="#safety-security-and-data-protection-considerations">8</a> that are designated as applying to CSAF Validators.
       </li>
       <li>outputs a warning if an "not implemented warning" occurs as the validation status might not be correct.
       </li>

csaf_2.1/prose/share/csaf-v2.1-draft.md

@@ -2152,6 +2152,9 @@ See IETF language registry: <https://www.iana.org/assignments/language-subtag-re
 > Even though the private use language tags are supported they should not be used to ensure readability across the ecosystem.
 > It is recommended to follow the conventions for the capitalization of the subtags even though it is not mandatory as most users are used to that.
 
+CSAF Producers SHALL follow the conventions for the capitalization of the subtags.
+CSAF Validators SHALL treat subtags as case-insensitive unless stated otherwise in the test.
+
 *Examples 1:*<a id='language-type-eg-1'></a><a id='sec-3-1-5-eg-1'></a><a id='example-23'></a>
 
 ```
@@ -5844,7 +5847,9 @@ The relevant path for this test is:
 
 ### 6.1.15 Translator <a id='translator'></a>
 
-It MUST be tested that `/document/source_lang` is present if the value `translator` is used for `/document/publisher/category`.
+It MUST be tested that `/document/source_lang` is present and set if the value `translator` is used for `/document/publisher/category`.
+A CSAF Validator SHALL differentiate in the error message between the key being present but having no or an empty value and
+not being present at all.
 
 The relevant path for this test is:
 
@@ -5869,6 +5874,9 @@ The relevant path for this test is:
 
 > The required element `source_lang` is missing.
 
+> A tool MAY add the key as a quick fix.
+> In such case, the value still needs to be set - either manually or by other means from the tool, e.g. through a given configuration.
+
 ### 6.1.16 Latest Document Version <a id='latest-document-version'></a>
 
 It MUST be tested that document version has the same value as the `number` in the last item of the revision history when
@@ -8820,7 +8828,9 @@ The relevant path for this test is:
 
 ### 6.2.12 Missing Document Language <a id='missing-document-language'></a>
 
-It MUST be tested that the document language member is present.
+It MUST be tested that the document language member is present and set.
+A CSAF Validator SHALL differentiate in the error message between the key being present but having no or an empty value and
+not being present at all.
 
 The relevant path for this test is:
 
@@ -8848,6 +8858,9 @@ The relevant path for this test is:
 
 > The document language is not defined.
 
+> A tool MAY add the key as a quick fix.
+> In such case, the value still needs to be set - either manually or by other means from the tool, e.g. through a given configuration.
+
 ### 6.2.13 Sorting <a id='recommended-tests--sorting'></a>
 
 It MUST be tested that all keys in a CSAF document are sorted alphabetically.
@@ -10144,6 +10157,8 @@ The relevant paths for this test are:
 ### 6.2.43 Missing License Expression <a id='missing-license-expression'></a>
 
 It MUST be tested that the license expression is present and set.
+A CSAF Validator SHALL differentiate in the error message between the key being present but having no or an empty value and
+not being present at all.
 
 The relevant path for this test is:
 
@@ -10166,6 +10181,9 @@ The relevant path for this test is:
 
 > The license expression is not defined.
 
+> A tool MAY add the key as a quick fix.
+> In such case, the value still needs to be set - either manually or by other means from the tool, e.g. through a given configuration.
+
 ### 6.2.44 Deprecated License Identifier <a id='deprecated-license-identifier'></a>
 
 It MUST be tested that all license identifier and exceptions used are not deprecated.
@@ -14066,8 +14084,9 @@ A program satisfies the "CSAF Basic Validator" conformance profile if the progra
   including also the format validation (cf. section [2.2](#format-validation)).
 * performs all tests of the preset `mandatory` as given in section [6.4.1](#presets-defined-through-test-subsections).
 * does not change the CSAF Documents.
-* satisfies those normative requirements in sections [2.4](#extensions), [6.1](#mandatory-tests), [6.4](#test-presets), and
-  [8](#safety-security-and-data-protection-considerations) that are designated as applying to CSAF Validators.
+* satisfies those normative requirements in sections [2.4](#extensions), [3](#schema-elements)  [6.1](#mandatory-tests),
+  [6.4](#test-presets), and [8](#safety-security-and-data-protection-considerations) that are designated as applying to
+  CSAF Validators.
 * outputs a warning if an "not implemented warning" occurs as the validation status might not be correct.
 
 A CSAF Basic Validator MAY provide one or more additional functions: