From 0d426eaed68d78c907096f6bc4a524f9dab12b3e Mon Sep 17 00:00:00 2001
From: Dimitris Apostolou The General
smpte.js
script contains the code that renders the HTML document provided by the author into an HTML
- document approprtiate for publication. This rendering happens automatically when loading the document in a web browser.
<section id="sec-foreword"> - <p>This is the additional infomation relevant to the document.</p> + <p>This is the additional information relevant to the document.</p> </section>
cite
element shall contain an id
attribute with value prefixed by
bib-
.li
element may contain additional title infomation.
+ li
element may contain additional title information.
li
element may contain one a
element that contains a location where the reference can
be retrieved.id
attribute of the dl
element shall be equal to terms-int-defs
.dt
element contains a single term, abbreviation or symbol. Zero or more additional dt
elements
can follow the first dt
element, in which case all the terms, abbreviations and symbols in the immediately
- preceding dt
elements are synomys.dt
elements are synonyms.
dd
element immediately following the last dt
element, if present, shall be
a definition.dd
element, if present, shall contain a single reference to a bibliographic entry,
@@ -649,13 +649,13 @@ An Annex section shall not contain nested annex sections.
<section class="annex" id="sec-addtional-info"> +<section class="annex" id="sec-additional-info"> <h2>Additional Info</h2> - <section id="sec-addtional-info-sub-section"> + <section id="sec-additional-info-sub-section"> <h3>Additional Info Sub Section</h3> <p>Some technical content</p> </section> - <section id="sec-addtional-info-sub-section-more"> + <section id="sec-additional-info-sub-section-more"> <h3>Additional Info Sub Section More</h3> <p>Some technical content</p> </section> @@ -711,7 +711,7 @@Additional elements section
<section id="sec-elements"> <ol> <li> - <a id="element-sample-text" title="Description of the elemnent" href="./elements/form.docx"></a> + <a id="element-sample-text" title="Description of the element" href="./elements/form.docx"></a> </li> </ol> </section>@@ -884,7 +884,7 @@Lists of key-value pairs
Lists
-A list can be inserted using either an
+ol
orul
element. Theul
(unordered list) element should be used when the order of listed items is not meaniful or important. Theol
(ordered list) element should be only used when the order of listed items is meaningful and/or important to the list and/or document.A list can be inserted using either an
ol
orul
element. Theul
(unordered list) element should be used when the order of listed items is not meaningful or important. Theol
(ordered list) element should be only used when the order of listed items is meaningful and/or important to the list and/or document.General guidelines for lists: @@ -1517,7 +1517,7 @@
Column Alignment
- Classes are available to center align columns 1-8 (as
col-x-center
), and mutliple classes totable
may be added to align more columns as needed. + Classes are available to center align columns 1-8 (ascol-x-center
), and multiple classes totable
may be added to align more columns as needed.Tables over 8 columns wide should not be used and instead split into multiple smaller tables. @@ -1892,7 +1892,7 @@
List
type
ExamplesList Nesting
- Both
ol
andul
elements may be nexted as many times within ali
element as needed to achieve the required results. See below for various examples. + Bothol
andul
elements may be nested as many times within ali
element as needed to achieve the required results. See below for various examples.@@ -2058,7 +2058,7 @@Mapping
pubState
andpubStage
to Document Status- @@ -2148,7 +2148,7 @@Undergoing intial draft or revision in DG/SG/WG +Undergoing initial draft or revision in DG/SG/WG WD
draft
Sample Workflow
Project is approved @@ -2195,7 +2195,7 @@-
- If document is an intial draft, skip to Workflow Step (2)
+- If document is an initial draft, skip to Workflow Step (2)
- If document is a revision, skip to Workflow Step (3)
Sample Workflow
Document is updated in PR to <meta itemprop="pubState" content="pub" />
,<meta itemprop="pubStage" content="WD" />
and<meta itemprop="pubDateTime" content="2023-04-15" />
(assumed date of completion).PR is approved by document editor and DG chair. PR is merged to main
.A release is created targeted at -main
named20230415-wd
with a tag of the same name.The tooling creates the zip needed for TC 2-week preFCD review, with redlines against lastest edition and/or last draft (if applicable) +The tooling creates the zip needed for TC 2-week preFCD review, with redlines against latest edition and/or last draft (if applicable) ZIP is sent to TC for 2-week preFCD review Continue to Workflow Step (6) @@ -2230,7 +2230,7 @@Sample Workflow
PR is merged to main
.A release is created targeted at main
named20230415-cd1
(or20230515-cd1
if Workflow Step 7 was used) with a tag of the same name.If document is to continue to FCD ballot, the ZIP file that is generated by the tooling in -main
with required redlines is sent to the TC for FCD ballot. Skip to Workflow Step (9)If document is to undergo a PCD period, the contents in the ZIP file generated by the tooling in +main
are used for the PCD. After PCD period ends, go back to Workflow Step (6). See for itterative CD naming.If document is to undergo a PCD period, the contents in the ZIP file generated by the tooling in main
are used for the PCD. After PCD period ends, go back to Workflow Step (6). See for iterative CD naming.Continue to Workflow Step (9)