Remove Status field from Supplement docs

This field causes some confusion for Supplement docs, for the
standard scs-0001-v1 merely states that these docs may be kept
in Draft state, which provides no certainty as to what should
be done. Here, I propose to go for maximum certainty by simply
stating they are kept in Draft state in perpetuity, and
therefore, the field is not even present in them.

Signed-off-by: Matthias Büchse <[email protected]>

Author: mbuechse

Standards/scs-0001-v1-sovereign-cloud-standards.md

@@ -107,7 +107,7 @@ embedded in the markdown header.
 | Field name      | Requirement                                                                | Description                                                                           |
 | --------------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
 | `type`          | REQUIRED                                                                   | one of `Procedural`, `Standard`, `Decision Record`, or `Supplement`                   |
-| `status`        | REQUIRED                                                                   | one of `Draft`, `Stable`, `Deprecated`, or `Rejected`                                 |
+| `status`        | REQUIRED precisely when `type` is not `Supplement`                         | one of `Draft`, `Stable`, `Deprecated`, or `Rejected`                                 |
 | `track`         | REQUIRED                                                                   | one of `Global`, `IaaS`, `KaaS`, `IAM`, `Ops`                                         |
 | `supplements`   | REQUIRED precisely when `type` is `Supplement`                             | list of documents that are extended by this document (e.g., multiple major versions)  |
 | `deprecated_at`  | REQUIRED if `status` is `Deprecated`                                       | ISO formatted date indicating the date after which the deprecation is in effect       |
@@ -193,7 +193,9 @@ In case there is little or no activity in some team, the SIG Standardization/Cer
 can take decisions on behalf of such a team. The SIG will seek alignment with the Project
 Board for decisions with large impact to ensure we have the wanted broad alignment.
 
-Supplements may be kept in Draft state, because they are not authoritative.
+From this perspective,
+Supplements are perpetually kept in Draft state, because they are not authoritative,
+and this state is not recorded in the document (i.e., no Status field).
 
 ### Proposal phase
 
@@ -223,8 +225,9 @@ for a Supplement of `scs-0100-v3-flavor-naming.md`,
 the file name might be `scs-0100-w1-flavor-naming-implementation-testing.md` (note the `w1`!).
 
 The metadata MUST indicate the intended `track` and `type` of the document,
-and the `status` MUST be set to `Draft`;
-for a Supplement, the `supplements` field MUST be set
+and the `status` MUST be set to `Draft`,
+except for a Supplement;
+where, instead, the `supplements` field MUST be set
 to a list of documents (usually containing one element).
 
 Upon acceptance by the group of people identified by the `track`,

Standards/scs-0004-w1-achieving-certification-implementation.md

@@ -2,7 +2,6 @@
 title: "Implementation hints for achieving SCS-compatible certification"
 type: Supplement
 track: Global
-status: Draft
 supplements:
   - scs-0004-v1-achieving-certification.md
 ---

Standards/scs-0007-w1-certification-integrators-implementation-notes.md

@@ -2,7 +2,6 @@
 title: "Implementation hints for achieving Certified SCS Integrator"
 type: Supplement
 track: Global
-status: Stable
 supplements:
   - scs-0007-v1-certification-integrators.md
 ---

Standards/scs-0100-w1-flavor-naming-implementation-testing.md

@@ -2,7 +2,6 @@
 title: "SCS Flavor Naming Standard: Implementation and Testing Notes"
 type: Supplement
 track: IaaS
-status: Draft
 supplements:
   - scs-0100-v1-flavor-naming.md
   - scs-0100-v2-flavor-naming.md

Standards/scs-0101-w1-entropy-implementation-testing.md

@@ -2,7 +2,6 @@
 title: "SCS Entropy: Implementation and Testing Notes"
 type: Supplement
 track: IaaS
-status: Draft
 supplements:
   - scs-0101-v1-entropy.md
 ---

Standards/scs-0102-w1-image-metadata-implementation-testing.md

@@ -2,7 +2,6 @@
 title: "SCS Image Metadata: Implementation and Testing Notes"
 type: Supplement
 track: IaaS
-status: Draft
 supplements:
   - scs-0102-v1-image-metadata.md
 ---

Standards/scs-0104-w1-standard-images-implementation.md

@@ -2,7 +2,6 @@
 title: "SCS Standard Images: Implementation and Testing Notes"
 type: Supplement
 track: IaaS
-status: Draft
 supplements:
   - scs-0104-v1-standard-images.md
 ---

Standards/scs-0116-w1-key-manager-implementation-testing.md

@@ -2,7 +2,6 @@
 title: "SCS Key Manager Standard: Implementation and Testing Notes"
 type: Supplement
 track: IaaS
-status: Draft
 supplements:
   - scs-0116-v1-key-manager-standard.md
 ---

Standards/scs-0118-w1-example-impacts-of-failure-scenarios.md

@@ -2,7 +2,6 @@
 title: "SCS Taxonomy of Failsafe Levels: Examples of Failure Cases and their impact on IaaS and KaaS resources"
 type: Supplement
 track: IaaS
-status: Draft
 supplements:
   - scs-0118-v1-taxonomy-of-failsafe-levels.md
 ---

Standards/scs-0121-w1-Availability-Zones-Standard.md

@@ -2,7 +2,6 @@
 title: "SCS Availability Zones: Implementation and Testing Notes"
 type: Supplement
 track: IaaS
-status: Draft
 supplements:
   - scs-0121-v1-Availability-Zones-Standard.md
 ---