Fix bikeshed build

We are bringing our own spec defaults and install them into the
bikeshed folder when building our container. Now bikeshed requires
an entry in the KDF dataset in order to find the group that we defined.

This commit adds the KDF entry to the list and also defines the
"CR", i.e. "Community Review" status. This is a reasonable start for a
more advanced status management for the documents we maintain here.

Author: thasso

build-tools/Dockerfile

@@ -11,6 +11,8 @@ RUN apk add --no-cache \
 
 COPY data/boilerplate/dashif /usr/lib/python3.12/site-packages/bikeshed/spec-data/boilerplate/dashif
 COPY build-tools/tools /tools
+COPY data/boilerplate/dashif.kdl /tmp/dashif.kdl
+RUN cat /tmp/dashif.kdl >> /usr/lib/python3.12/site-packages/bikeshed/spec-data/boilerplate/doctypes.kdl
 
 RUN mkdir /data
 WORKDIR /data

data/boilerplate/dashif.kdl

@@ -0,0 +1,5 @@
+org "dashif" {
+    group "dashif"
+
+    status "CR" "Community Review"
+}

data/boilerplate/dashif/defaults.include

@@ -2,7 +2,6 @@
   "Issue Tracking": "GitHub https://github.com/Dash-Industry-Forum/DASH-IF-IOP/issues",
   "Repository": "https://github.com/Dash-Industry-Forum/DASH-IF-IOP GitHub",
   "Editor": "SVTA DASH-IF Working Group",
-
   "Default Highlight": "text",
   "Line Numbers": "off",
   "Markup Shorthands": "markdown yes, biblio yes",

specs/live2vod/live2vod.bs

@@ -1,7 +1,7 @@
 <pre class="metadata">
 Revision: 0.9
 Title: Conversion of Live Services to VoD
-!Status: Community Review
+Status: CR
 Shortname: live2vod
 URL: https://dashif.org/Guidelines/live2vod
 Group: dashif