[ttml2] editorial: remove empty lines in spec source
authorGlenn Adams <glenn@skynav.com>
Tue, 23 Sep 2014 12:46:20 -0600
changeset 712 926c39122963
parent 711 5ca0c4a3fd71
child 713 33151db6397b
[ttml2] editorial: remove empty lines in spec source
ttml2/spec/ttml2.xml
--- a/ttml2/spec/ttml2.xml	Mon Sep 22 22:20:54 2014 -0600
+++ b/ttml2/spec/ttml2.xml	Tue Sep 23 12:46:20 2014 -0600
@@ -126,9 +126,7 @@
 <langusage><language id='en-us'>English</language></langusage>
 <revisiondesc><p>Last Modified: $Date$</p></revisiondesc>
 </header>
-
 <body>
-
 <div1 id="intro">
 <head>Introduction</head>
 <p><emph>Unless specified otherwise, this section and its sub-sections are non-normative.</emph></p>
@@ -165,7 +163,6 @@
 certain contexts, such as profile names and designators, and the short name
 <code>ttaf1-dfxp</code> used in URLs to refer to this specification.</p>
 </note>
-
 <div2 id="model">
 <head>System Model</head>
 <p>Use of TTML is intended to function in a wider context of Timed Text
@@ -185,7 +182,6 @@
 </tbody>
 </table>
 </div2> <!-- model -->
-
 <div2 id="example">
 <head>Document Example</head>
 <p>A TTML <loc href="#terms-document-instance">document instance</loc> consists of a <el>tt</el> document element that contains
@@ -489,7 +485,6 @@
 and may specify inline overrides to styling.</p>
 </div2> <!-- example -->
 </div1> <!-- intro -->
-
 <div1 id="definitions">
 <head>Definitions</head>
 <div2 id="acronyms">
@@ -1073,7 +1068,6 @@
 </def>
 </gitem>
 </glist>
-
 <p>If normative specification language takes an imperative form,
 then it is to be treated as if the term <phrase role="strong">must</phrase>
 applies. Furthermore, if normative language takes a declarative form,
@@ -1164,7 +1158,6 @@
 </table>
 </div2> <!-- conventions -->
 </div1> <!-- definitions -->
-
 <div1 id="conformance">
 <head>Conformance</head>
 <p>This section specifies the general conformance requirements for
@@ -1208,12 +1201,10 @@
 </item>
 </olist>
 </div2> <!-- conformance-content -->
-
 <div2 id="conformance-processor">
 <head>Processor Conformance</head>
 <div3 id="conformance-generic-processor">
 <head>Generic Processor Conformance</head>
-
 <ednote>
 <name>Profile Processing</name>
 <date>2014-05-21</date>
@@ -1225,7 +1216,6 @@
 <date>2014-05-21</date>
 <edtext>Add requirement to invoke validation processing procedure. Add and use definition of 'validating processor'.</edtext>
 </ednote>
-
 <p>A TTML <loc href="#terms-content-processor">content processor</loc> conforms to this specification if the following
 generic processor criteria are
 satisfied:</p>
@@ -1273,7 +1263,6 @@
 </item>
 </olist>
 </div3> <!-- conformance-generic-processor -->
-
 <div3 id="conformance-transformation-processor">
 <head>Transformation Processor Conformance</head>
 <p>A TTML <loc href="#terms-content-processor">content processor</loc> is a conformant TTML <loc href="#terms-transformation-processor">transformation processor</loc> if
@@ -1294,7 +1283,6 @@
 <edtext>Should we also require support for DFXP Transformation Profile?</edtext>
 </ednote>
 </div3> <!-- conformance-transformation-processor -->
-
 <div3 id="conformance-presentation-processor">
 <head>Presentation Processor Conformance</head>
 <p>A TTML <loc href="#terms-content-processor">content processor</loc> is a conformant TTML <loc href="#terms-presentation-processor">presentation processor</loc> if
@@ -1315,9 +1303,7 @@
 <edtext>Should we also require support for DFXP Presentation Profile?</edtext>
 </ednote>
 </div3> <!-- conformance-presentation-processor -->
-
 </div2> <!-- conformance-processor -->
-
 <div2 id="claims">
 <head>Claims</head>
 <p>Any claim of compliance with respect to the conformance of a TTML <loc href="#terms-document-instance">document instance</loc> or
@@ -1345,7 +1331,6 @@
 support for a <loc href="#terms-feature">feature</loc> not defined by <bibref ref="ttml1"/>.</p>
 </div2> <!-- claims -->
 </div1> <!-- conformance -->
-
 <div1 id="doctypes">
 <head>Document Types</head>
 <p>This section defines the following TTML <emph>Abstract Document Types</emph>:</p>
@@ -1430,7 +1415,6 @@
 </note>
 </div2> <!-- ttml-content-doctype -->
 </div1> <!-- doctypes -->
-
 <div1 id="vocabulary">
 <head>Vocabulary</head>
 <p>This section defines the
@@ -1527,46 +1511,36 @@
 <bibref ref="nsstate"/>; all undefined names in these namespaces are reserved for future
 standardization by the W3C.</p>
 </div2> <!-- vocabulary-namespaces -->
-
 <div2 id="vocabulary-profiles">
 <head>Profiles</head>
-
 <p>This section describes the TTML profiling sub-system and high level requirements that apply to this sub-system. At the end of this section
 appears a sub-section containing examples of profile specifications and examples of how these specifications are referenced and used.</p>
-
 <div3 id="vocabulary-profile-introduction">
 <head>Introduction</head>
-
 <p><emph>This sub-section is non-normative.</emph></p>
-
 <p>A given profile may be used by a Timed Text Markup Language content author for one of two functions: (1) to declare that a
 <loc href="#terms-document-instance">document instance</loc> adheres to a collection of constraints on what
 vocabulary is used and how it is used, or (2) to declare that a <loc href="#terms-processor">processor</loc> must satisfy certain conditions on how
 content is processed. The first of these functions is termed a <loc href="#terms-content-profile">content profile</loc>, while
 the second is termed a <loc href="#terms-processor-profile">processor profile</loc>.</p>
-
 <p>A <loc href="#terms-content-profile">content profile</loc> is used to allow an author to declare, at authoring time,
 what constraints the author intends to apply to a <loc href="#terms-document-instance">document instance</loc>. Such a
 declaration permits downstream processors to perform content validation or verification, as well as to guide or limit subsequent
 transformation or editing of content in order to maintain adherence to an author specified content profile. In addition, a
 downstream processor may use a content profile declaration to perform an early determination of its ability to process the features
 implied by the content profile.</p>
-
 <p>Content profiles are declared by using (1) the <loc href="#parameter-attribute-contentProfiles"><att>ttp:contentProfiles</att></loc>
 attribute on the root <el>tt</el> element, (2) one or more top-level <loc href="#parameter-vocabulary-profile"><el>ttp:profile</el></loc>
 elements of type <code>content</code>, or (3) a combination of these two mechanisms. If not declared, no content profile is implied.</p>
-
 <p>A <loc href="#terms-processor-profile">processor profile</loc> is used to allow an author to declare, at authoring time,
 what processing must be supported when processing a <loc href="#terms-document-instance">document instance</loc>, such that, if a
 processor is not able to perform the indicated processing, then processing should be aborted. Such a declaration permits downstream
 processors to avoid processing content that cannot be processed in a manner that meets the requirements of the content author.</p>
-
 <p>Processor profiles are declared by using (1) the <loc href="#parameter-attribute-processorProfiles"><att>ttp:processorProfiles</att></loc>
 attribute on the root <el>tt</el> element, (2) one or more <loc href="#parameter-vocabulary-profile"><el>ttp:profile</el></loc>
 elements of type <code>processor</code>, or (3) a combination of these two mechanisms.
 If not declared, a processor profile is inferred from a declared content profile or from a
 <loc href="#terms-default-profile">default profile</loc>.</p>
-
 <note role="elaboration">
 <p>It is not a requirement on a conformant <loc href="#terms-document-instance">document instance</loc> that a processor profile be internally
 declared by use of a <loc href="#parameter-vocabulary-profile"><el>ttp:profile</el></loc> element or internally referenced by a
@@ -1576,7 +1550,6 @@
 agreement, out-of-band protocol, or common use (between sender and receiver) of a processor profile defined
 by an external specification.</p>
 </note>
-
 <note role="elaboration">
 <p>It is intended that the <att>ttp:processorProfiles</att> attribute be used when
 the author wishes to reference one (or more) of the standard, predefined processor profiles of
@@ -1602,26 +1575,20 @@
 It is also possible to define a derived profile that is simultaneously subtractive
 and additive.</p>
 </note>
-
 <p>A content author is not limited to using a single profile, but may make reference to multiple profiles of either type, i.e.,
 multiple content profiles and/or multiple processor profiles. When multiple profiles are referenced, their respective specifications
 are combined to form a single effective content profile that applies to the document and a single effective processor profile
 that applies to a processor when processing the document. In addition, an author is not limited to making reference to externally
 defined profiles, but may define one or more profiles inline within a document.</p>
-
-</div3>
-
+</div3>
 <div3 id="semantics-profile-examples">
 <head>Profile Examples</head>
-
 <p><emph>This sub-section is non-normative.</emph></p>
-
 <ednote>
 <name>More profile examples.</name>
 <date>2014-05-21</date>
 <edtext>Add more examples depicting new profiling features defined in TTML2.</edtext>
 </ednote>
-
 <p>An example of an author defined
 additive, derived profile of the TTML Presentation
 profile is shown
@@ -1654,29 +1621,23 @@
 in <specref ref="profile-ttml2-presentation"/>). Note also the resetting of the
 default XMLNS binding on the <el>profile</el> element to the TT Parameter Namespace.</p>
 </note>
-
-</div3>
-
+</div3>
 <div3 id="vocabulary-profile-designators">
 <head>Profile Designators</head>
-
 <ednote>
 <name>Reference by designator to internally defined profile.</name>
 <date>2014-05-26</date>
 <edtext>Handle case where a designator refers to an internally defined profile.</edtext>
 </ednote>
-
 <p>A profile is referenced in one of two ways according to whether the profile is defined externally to the referring document or
 is defined inline within the referring document. When defined externally, a profile is referenced by means of a
 <loc href="#terms-profile-designator">profile designator</loc>. When defined internally (inline), a profile is referenced either implicitly
 or by means of <loc href="#terms-profile-fragment-identifier">profile fragment identifier</loc>.</p>
-
 <ednote>
 <name>Profile Fragment Identifiers.</name>
 <date>2014-05-26</date>
 <edtext>Update following to account for use of profile fragment identifier as a profile designator.</edtext>
 </ednote>
-
 <p>A profile designator must adhere to the
 <code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
 &sect;3.2.17. If the profile designator is expressed as a relative URI,
@@ -1693,14 +1654,11 @@
 <loc href="#terms-document-instance">document instance</loc>. Nothwithstanding this constraint, a profile designator is not restricted to the set of designators enumerated
 in <specref ref="profile-vocab-table"/>, but may be any URI that feasibly dereferences a TTML <loc href="#terms-profile-definition-document">profile definition document</loc>
 provided it does not use the TT Profile Namespace as a prefix.</p>
-
 <div4 id="vocabulary-profile-standard-designators">
 <head>Standard Designators</head>
-
 <p>The Timed Text Markup Language (TTML) employs a number of
 standard, predefined profiles of its
 vocabulary and associated semantics.</p>
-
 <p>The following table specifies this set of
 profiles, indicating
 a normative name
@@ -1752,19 +1710,14 @@
 <p>For definitions of the DFXP profiles, see <bibref ref="ttml1"/>. For definition of the SDP US profile, see <bibref ref="sdpus"/>.</p>
 </note>
 </div4>
-
-</div3>
-
+</div3>
 <div3 id="semantics-profile-semantics">
 <head>Profile Semantics</head>
-
 <div4 id="semantics-profile-state">
 <head>Profile State Object Concepts</head>
 <p>This section defines a number of conceptual state objects used by subsequently defined algorithms (procedures and functions). It is not required that an
 implementation create such objects in the form specified here, but may use any convenient, internal representation that represents equivalent information.</p>
-
 <glist>
-
 <gitem id="semantics-profile-state-profile-specification">
 <label>[profile specification]</label>
 <def>
@@ -1794,7 +1747,6 @@
 </glist>
 </def>
 </gitem>
-
 <gitem id="semantics-profile-state-combined-profile-specification-set">
 <label>[combined profile specification set]</label>
 <def>
@@ -1820,7 +1772,6 @@
 </glist>
 </def>
 </gitem>
-
 <gitem id="semantics-profile-state-empty-profile-specification-set">
 <label>[empty profile specification set]</label>
 <def>
@@ -1829,7 +1780,6 @@
 <loc href="#semantics-profile-state-combined-profile-specification-set-specifications"><phrase role="strong">specifications</phrase></loc> fields are empty sets</p>
 </def>
 </gitem>
-
 <gitem id="semantics-profile-state-profile">
 <label>[profile]</label>
 <def>
@@ -1884,20 +1834,15 @@
 </glist>
 </def>
 </gitem>
-
 </glist>
-
 </div4>
-
 <div4 id="semantics-content-profile-processing">
 <head>Content Profile Semantics</head>
-
 <ednote>
 <name>Validation Processing</name>
 <date>2014-05-21</date>
 <edtext>Add validation processing procedures.</edtext>
 </ednote>
-
 <glist>
 <gitem id="semantics-procedure-construct-effective-content-profile">
 <label>[construct effective content profile]</label>
@@ -1956,12 +1901,9 @@
 </def>
 </gitem>
 </glist>
-
 </div4>
-
 <div4 id="semantics-processor-profile-processing">
 <head>Processor Profile Semantics</head>
-
 <glist>
 <gitem id="semantics-procedure-abort-if-unsupported-processor-profile">
 <label>[abort if unsupported processor profile]</label>
@@ -2040,7 +1982,6 @@
 </olist>
 </def>
 </gitem>
-
 <gitem id="semantics-procedure-construct-inferred-processor-profile">
 <label>[construct inferred processor profile]</label>
 <def>
@@ -2099,7 +2040,6 @@
 </olist>
 </def>
 </gitem>
-
 <gitem id="semantics-procedure-construct-default-processor-profile">
 <label>[construct default processor profile]</label>
 <def>
@@ -2110,7 +2050,6 @@
 from which a <loc href="#terms-processor-profile">processor profile</loc> can be inferred, then the
 <loc href="#terms-default-processor-profile">default processor profile</loc> is that <loc href="#terms-processor-profile">processor profile</loc>;</p>
 </item>
-
 <item>
 <p>otherwise, if the <loc href="#terms-content-processor">content processor</loc> is primarily characterized as a
 <loc href="#terms-presentation-processor">presentation processor</loc>, then:</p>
@@ -2137,7 +2076,6 @@
 </item>
 </olist>
 </item>
-
 <item>
 <p>otherwise, if the <loc href="#terms-content-processor">content processor</loc> is primarily characterized as a
 <loc href="#terms-transformation-processor">transformation processor</loc>, then:</p>
@@ -2175,13 +2113,9 @@
 </gitem>
 </glist>
 
-
 </div4>
-
-</div3>
-
+</div3>
 </div2> <!-- vocabulary-profiles -->
-
 <div2 id="vocabulary-overview">
 <head>Catalog</head>
 <p>The vocabulary of the Timed Text Markup Language (TTML) is
@@ -2541,7 +2475,6 @@
 </div3>
 </div2> <!-- vocabulary-overview -->
 </div1> <!-- vocabulary -->
-
 <div1 id="parameters">
 <head>Parameters</head>
 <p>This section specifies the <emph>parameters</emph> matter of the
@@ -3118,7 +3051,6 @@
 <p>The value <phrase role="obsoleted"><code>use</code></phrase> of the <att>value</att> attribute is <phrase role="obsoleted">obsoleted</phrase>. If it
 appears in a profile specification, then it must be interpreted as if <code>required</code>
 had been specified.</p>
-
 <p>If some well known extension is not specified by
 a <el>ttp:extension</el> element in a content profile, then it must be interpreted as if the extension were specified
 with the <att>value</att> attribute equal to <code>optional</code>. However, if not specified in a processor profile, no claim
@@ -3163,7 +3095,6 @@
 </note>
 </div3>
 </div2> <!-- parameter-element-vocabulary -->
-
 <div2 id="parameter-attribute-vocabulary">
 <head>Parameter Attribute Vocabulary</head>
 <p>The following attributes are defined in the TT Parameter Namespace.</p>
@@ -3211,7 +3142,6 @@
 <eg xml:space="preserve">
 ttp:cellResolution
   : columns rows                            // <emph>columns</emph> != 0; <emph>rows</emph> != 0
-
 columns | rows
   : <loc href="#style-value-digit">&lt;digit&gt;</loc>+
 </eg>
@@ -3320,13 +3250,10 @@
   : designators
   | "all(" designators ")"
   | "any(" designators ")"
-
 designators
   : designator (lwsp designator)*
-
 designator
   : xsd:anyURI
-
 lwsp
   : ( ' ' | '\t' | '\n' | '\r' )+
 </eg>
@@ -3584,7 +3511,6 @@
 <eg xml:space="preserve">
 ttp:frameRateMultiplier
   : numerator denominator                   // <emph>numerator</emph> != 0; <emph>denominator</emph> != 0
-
 numerator | denominator
   : <loc href="#style-value-digit">&lt;digit&gt;</loc>+
 </eg>
@@ -3861,7 +3787,6 @@
 <eg xml:space="preserve">
 ttp:mediaOffset
   : sign? <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>                  // restricted to <emph>offset-time</emph> form
-
 sign
   : "+" | "-"
 </eg>
@@ -3958,7 +3883,6 @@
 <eg xml:space="preserve">
 ttp:pixelAspectRatio
   : width height                            // <emph>width</emph> != 0; <emph>height</emph> != 0
-
 width | height
   : <loc href="#style-value-digit">&lt;digit&gt;</loc>+
 </eg>
@@ -4002,7 +3926,6 @@
 <eg xml:space="preserve">
 <phrase role="deprecated">ttp:profile</phrase>
   : designator
-
 designator
   : xsd:anyURI
 </eg>
@@ -4039,13 +3962,10 @@
   : designators
   | "all(" designators ")"
   | "any(" designators ")"
-
 designators
   : designator (lwsp designator)*
-
 designator
   : xsd:anyURI
-
 lwsp
   : ( ' ' | '\t' | '\n' | '\r' )+
 </eg>
@@ -4061,7 +3981,6 @@
 attribute is considered to be significant only when specified on the
 <el>tt</el> element.</p>
 </div3>
-
 <div3 id="parameter-attribute-processorProfileCombination">
 <head>ttp:processorProfileCombination</head>
 <p>The <att>ttp:processorProfileCombination</att> attribute is used to specify the
@@ -4301,7 +4220,6 @@
 on the interpretation of time expressions according to the designated time base.</p>
 </note>
 </div3>
-
 <div3 id="parameter-attribute-validation">
 <head>ttp:validation</head>
 <p>The <att>ttp:validation</att> attribute is used to specify whether validation processing
@@ -4426,7 +4344,6 @@
 </div3>
 </div2> <!-- parameter-attribute-vocabulary -->
 </div1> <!-- parameters -->
-
 <div1 id="content">
 <head>Content</head>
 <p>This section specifies the <emph>content</emph> matter of the core
@@ -4992,7 +4909,6 @@
 </div3>
 </div2> <!-- content-attribute-vocabulary -->
 </div1> <!-- content -->
-
 <div1 id="styling">
 <head>Styling</head>
 <p>This section specifies the <emph>styling</emph> matter of the core
@@ -5141,7 +5057,6 @@
 </note>
 </div3>
 </div2> <!-- styling-element-vocabulary -->
-
 <div2 id="styling-attribute-vocabulary">
 <head>Styling Attribute Vocabulary</head>
 <p>This section defines the <specref ref="style-attribute-style"/> attribute used
@@ -5343,7 +5258,6 @@
 that defined by <bibref ref="xsl11"/>, &sect; 7.8.2.</p>
 </note>
 </div3>
-
 <div3 id="style-attribute-border">
 <head>tts:border</head>
 <p>The <att>tts:border</att> attribute is used to specify a style property that
@@ -5462,7 +5376,6 @@
 that defined by <bibref ref="xsl11"/>, &sect; 7.31.3.</p>
 </note>
 </div3>
-
 <div3 id="style-attribute-color">
 <head>tts:color</head>
 <p>The <att>tts:color</att> attribute is used to specify a style property that
@@ -8412,7 +8325,6 @@
 </note>
 </div3>
 </div2> <!-- styling-attribute-vocabulary -->
-
 <div2 id="styling-style-value-expressions">
 <head>Style Value Expressions</head>
 <p>Style property values include the use of the following expressions:</p>
@@ -8468,7 +8380,6 @@
 the computed value, then the value most distant from 0, i.e., the greatest opacity, is used.</p>
 </note>
 </div3>
-
 <div3 id="style-value-border-color">
 <head>&lt;border-color&gt;</head>
 <p>A &lt;border-color&gt; expression is used to express the color of one
@@ -8487,7 +8398,6 @@
 </tbody>
 </table>
 </div3>
-
 <div3 id="style-value-border-style">
 <head>&lt;border-style&gt;</head>
 <p>A &lt;border-style&gt; expression is used to express the style of one
@@ -8515,7 +8425,6 @@
 it must be interpreted as if a style of <code>solid</code> were specified; however, an implementation that
 supports borders must minimally support the <code>none</code> and <code>solid</code> values.</p>
 </div3>
-
 <div3 id="style-value-border-width">
 <head>&lt;border-width&gt;</head>
 <p>A &lt;border-width&gt; expression is used to express the width of one
@@ -8542,7 +8451,6 @@
 <p>If a border width is expressed as a <loc href="#style-value-length">&lt;length&gt;</loc>,
 then it must not take the form of a percentage value; i.e., it must take the form of a scalar value.</p>
 </div3>
-
 <div3 id="style-value-color">
 <head>&lt;color&gt;</head>
 <p>A &lt;color&gt; expression is used to specify a named color, exact RGB color triple,
@@ -8562,19 +8470,14 @@
   | "rgb" "(" r-value "," g-value "," b-value ")"
   | "rgba" "(" r-value "," g-value "," b-value "," a-value ")"
   | <loc href="#style-value-namedColor">&lt;namedColor&gt;</loc>
-
 rrggbb
   :  <loc href="#style-value-hexDigit">&lt;hexDigit&gt;</loc>{6}
-
 rrggbbaa
   :  <loc href="#style-value-hexDigit">&lt;hexDigit&gt;</loc>{8}
-
 r-value | g-value | b-value | a-value
   : component-value
-
 component-value
   : non-negative-integer                    // valid range: [0,255]
-
 non-negative-integer
   : <loc href="#style-value-digit">&lt;digit&gt;</loc>+
 </eg>
@@ -8643,39 +8546,29 @@
 &lt;familyName&gt;
   : unquoted-string
   | quoted-string
-
 unquoted-string
   : identifier ( lwsp identifier )*
-
 lwsp
   : ( ' ' | '\t' | '\n' | '\r' )+
-
 identifier
   : [-]? identifier-start identifier-following*
-
 identifier-start
   : [_a-zA-Z]
   | non-ascii-or-c1
   | escape
-
 identifier-following
   : [_a-zA-Z0-9-]
   | non-ascii-or-c1
   | escape
-
 non-ascii-or-c1
   : [^\0-\237]
-
 escape
   : '\\' <emph>char</emph>
-
 quoted-string
   : double-quoted-string
   | single-quoted-string
-
 double-quoted-string
   : '"' ( [^"\\] | escape )+ '"'
-
 single-quoted-string
   : "'" ( [^'\\] | escape )+ "'"
 </eg>
@@ -8814,29 +8707,21 @@
 &lt;length&gt;
   : scalar
   | percentage
-
 scalar
   : number units
-
 percentage
   : number "%"
-
 sign
   : "+" | "-"
-
 number
   : sign? non-negative-number
-
 non-negative-number
   : non-negative-integer
   | non-negative-real
-
 non-negative-integer
   : <loc href="#style-value-digit">&lt;digit&gt;</loc>+
-
 non-negative-real
   : <loc href="#style-value-digit">&lt;digit&gt;</loc>* "." <loc href="#style-value-digit">&lt;digit&gt;</loc>+
-
 units
   : "px"
   | "em"
@@ -8936,7 +8821,6 @@
 </note>
 </div3>
 </div2> <!-- styling-style-value-expressions -->
-
 <div2 id="semantics-style-resolution">
 <head>Style Resolution</head>
 <p>This section defines the semantics of style resolution in terms of
@@ -9628,7 +9512,6 @@
 </div3>
 </div2> <!-- semantics-style-resolution -->
 </div1> <!-- styling -->
-
 <div1 id="layout">
 <head>Layout</head>
 <p>This section specifies the <emph>layout</emph> matter of the core
@@ -9790,7 +9673,6 @@
 (associated with) the region.</p>
 </div3>
 </div2> <!-- layout-element-vocabulary -->
-
 <div2 id="layout-attribute-vocabulary">
 <head>Layout Attribute Vocabulary</head>
 <p>This section defines the <specref ref="layout-attribute-region"/> attribute used with <loc href="#terms-content-element">content elements</loc>.</p>
@@ -9817,7 +9699,6 @@
 </note>
 </div3>
 </div2> <!-- layout-attribute-vocabulary -->
-
 <div2 id="semantics-region-layout">
 <head>Region Layout and Presentation</head>
 <p>This section defines the semantics of region layout and
@@ -9914,13 +9795,11 @@
 the latter as an <emph>explicit inline region specification</emph>; furthermore, the former is considered
 to be a syntactic shorthand for the latter, and is processed by converting it into the latter as
 described below.</p>
-
 <p>Inline regions are processed in accordance with the procedure
 <phrase role="strong"><loc href="#procedure-process-inline-regions">[process inline regions]</loc></phrase>, which
 entails first generating implied inline regions, and then generating out-of-line regions that correspond with implied
 or explicit inline regions. This latter procedure additionally binds content elements associated with inline regions
 to the corresponding generated out-of-line regions.</p>
-
 <note role="elaboration">
 <p>A <loc href="#terms-content-element">content element</loc> can only be associated with a single
 <loc href="#terms-region">region</loc>. Consequently, if a <loc href="#terms-content-element">content element</loc>
@@ -9930,7 +9809,6 @@
 both an <emph>implied inline region specification</emph> and an <emph>explicit inline region specification</emph>,
 then the former is ignored in favor of the latter.</p>
 </note>
-
 <glist>
 <gitem id="procedure-process-inline-regions">
 <label>[process inline regions]</label>
@@ -10076,9 +9954,7 @@
 </def>
 </gitem>
 </glist>
-
 <p>The use of an <emph>implied inline region specification</emph> and the resulting generated inline region is shown by the following two example documents.</p>
-
 <table id="semantics-inline-region-input-example-1-implied" role="example">
 <caption>Example &ndash; Implied Inline Region Specification</caption>
 <tbody>
@@ -10098,7 +9974,6 @@
 </tr>
 </tbody>
 </table>
-
 <p></p>
 <table id="semantics-generated-out-of-line-region-example-1-implied" role="example">
 <caption>Example &ndash; Generated Inline Region</caption>
@@ -10120,11 +9995,9 @@
 </tr>
 </tbody>
 </table>
-
 <p>The use of an <emph>explicit inline region specification</emph> or a generated inline region that derives from
 an <emph>implicit inline region specification</emph>
 and the resulting generated out-of-line region is shown by the following two example documents.</p>
-
 <table id="semantics-inline-region-input-example-2-explicit" role="example">
 <caption>Example &ndash; Explicit or Generated Inline Region Specification</caption>
 <tbody>
@@ -10145,7 +10018,6 @@
 </tr>
 </tbody>
 </table>
-
 <p></p>
 <table id="semantics-generated-out-of-line-region-example-2-explicit" role="example">
 <caption>Example &ndash; Generated Out-of-line Region</caption>
@@ -10535,7 +10407,6 @@
 </table>
 </div3>
 </div2> <!-- semantics-region-layout -->
-
 <div2 id="semantics-line-layout">
 <head>Line Layout</head>
 <p>If a profile that applies to a <loc href="#terms-document-instance">document instance</loc>
@@ -10548,7 +10419,6 @@
 line layout on the content of the <loc href="#terms-document-instance">document instance</loc>.</p>
 </div2> <!-- semantics-line-layout -->
 </div1> <!-- layout -->
-
 <div1 id="timing">
 <head>Timing</head>
 <p>This section specifies the <emph>timing</emph> matter of the core
@@ -10561,7 +10431,6 @@
 <p>No timing related element vocabulary is defined for use in the core
 vocabulary catalog.</p>
 </div2> <!-- timing-element-vocabulary -->
-
 <div2 id="timing-attribute-vocabulary">
 <head>Timing Attribute Vocabulary</head>
 <p>This section defines the following basic timing attributes for use with timed elements:</p>
@@ -10685,7 +10554,6 @@
 while taking into account any overriding semantics defined by this specification.</p>
 </div3>
 </div2> <!-- timing-attribute-vocabulary -->
-
 <div2 id="timing-time-value-expressions">
 <head>Time Value Expressions</head>
 <p>Timing attribute values include the use of the following expressions:</p>
@@ -10698,7 +10566,6 @@
 some time base, where the applicable time base is determined by the
 <att>ttp:timeBase</att> parameter, and where the semantics defined
 by <specref ref="time-expression-semantics"/> apply.</p>
-
 <note role="example">
 <p>See
 <specref ref="parameter-attribute-frameRate"/>,
@@ -10716,33 +10583,24 @@
 &lt;timeExpression&gt;
   : clock-time
   | offset-time
-
 clock-time
   : hours ":" minutes ":" seconds ( fraction | ":" frames ( "." sub-frames )? )?
-
 offset-time
   : time-count fraction? metric
-
 hours
   : <loc href="#style-value-digit">&lt;digit&gt;</loc> <loc href="#style-value-digit">&lt;digit&gt;</loc>
   | <loc href="#style-value-digit">&lt;digit&gt;</loc> <loc href="#style-value-digit">&lt;digit&gt;</loc> <loc href="#style-value-digit">&lt;digit&gt;</loc>+
-
 minutes | seconds
   : <loc href="#style-value-digit">&lt;digit&gt;</loc> <loc href="#style-value-digit">&lt;digit&gt;</loc>
-
 frames
   : <loc href="#style-value-digit">&lt;digit&gt;</loc> <loc href="#style-value-digit">&lt;digit&gt;</loc>
   | <loc href="#style-value-digit">&lt;digit&gt;</loc> <loc href="#style-value-digit">&lt;digit&gt;</loc> <loc href="#style-value-digit">&lt;digit&gt;</loc>+
-
 sub-frames
   : <loc href="#style-value-digit">&lt;digit&gt;</loc>+
-
 fraction
   : "." <loc href="#style-value-digit">&lt;digit&gt;</loc>+
-
 time-count
   : <loc href="#style-value-digit">&lt;digit&gt;</loc>+
-
 metric
   : "h"                 // hours
   | "m"                 // minutes
@@ -10778,7 +10636,6 @@
 when the <code>clock</code> time base applies.</p>
 </div3>
 </div2> <!-- timing-time-value-expressions -->
-
 <div2 id="timing-time-intervals">
 <head>Time Intervals</head>
 <p>The semantics of time containment, durations, and intervals defined by
@@ -10828,7 +10685,6 @@
 </ulist>
 </div2> <!-- timing-time-intervals -->
 </div1> <!-- timing -->
-
 <div1 id="animation">
 <head>Animation</head>
 <p>This section specifies the <emph>animation</emph> matter of the
@@ -10977,7 +10833,6 @@
 with Continuously Varying Colors!" is continuously animated from yellow, to red, to green, to
 red, then back to yellow over a 5 second period.</p>
 </note>
-
 <p>An example of using the <el>animate</el> element to animate region
 styling is illustrated below:</p>
 <table id="animation-vocabulary-animate-example-2" role="example">
@@ -11117,7 +10972,6 @@
 with Flashing Colors!" is animated from yellow, to red, to green, to
 red, then back to yellow over a 5 second period.</p>
 </note>
-
 <p>An example of using the <el>set</el> element to animate region
 styling is illustrated below:</p>
 <table id="animation-vocabulary-set-example-2" role="example">
@@ -11320,24 +11174,18 @@
 <eg xml:space="preserve">
 &lt;keySplines&gt;
   : control [ lwsp? ";" lwsp? control ]*
-
 control
   : x1 comma? y1 comma? x2 comma? y2
-
 x1, x2, y1, y2
   : coordinate
-
 coordinate                                // 0 &ge; <emph>value</emph> &ge; 1
   : whole
   | whole "." fraction
   | "." fraction
-
 whole, fraction
   : <loc href="#style-value-digit">&lt;digit&gt;</loc>+
-
 comma
   : ","
-
 lwsp
   : ( ' ' | '\t' | '\n' | '\r' )+
 </eg>
@@ -11361,15 +11209,12 @@
 <eg xml:space="preserve">
 &lt;keyTimes&gt;
   : time [ lwsp? ";" lwsp? time ]*
-
 time                                // 0 &ge; <emph>value</emph> &ge; 1
   : whole
   | whole "." fraction
   | "." fraction
-
 whole, fraction
   : <loc href="#style-value-digit">&lt;digit&gt;</loc>+
-
 lwsp
   : ( ' ' | '\t' | '\n' | '\r' )+
 </eg>
@@ -11392,7 +11237,6 @@
 &lt;repeatCount&gt;
   : count
   | "indefinite"
-
 count:
   : <loc href="#style-value-digit">&lt;digit&gt;</loc>+                       // <emph>value</emph> > 0
 </eg>
@@ -11405,7 +11249,6 @@
 </div3>
 </div2> <!-- animation-value-expressions -->
 </div1> <!-- animation -->
-
 <div1 id="metadata">
 <head>Metadata</head>
 <p>This section specifies the <emph>metadata</emph> matter of the core
@@ -11417,7 +11260,6 @@
 specification for standardized use in a <loc href="#terms-document-instance">document instance</loc>, and (2) arbitrary
 metadata defined outside of the scope of this specification, whose use and
 semantics depend entirely upon an application's use of TTML Content.</p>
-
 <div2 id="metadata-element-vocabulary">
 <head>Metadata Element Vocabulary</head>
 <p>The <specref ref="metadata-vocabulary-metadata"/> element serves as
@@ -11513,7 +11355,6 @@
 </tbody>
 </table>
 <p></p>
-
 <p>The use of metadata attribute items is illustrated by the following example.</p>
 <table id="metadata-vocabulary-metadata-example-3" role="example">
 <caption>Example Fragment &ndash; Foreign Metadata Attribute Items</caption>
@@ -11713,7 +11554,6 @@
 <tr>
 <td>
 <eg xml:space="preserve">
-
 &lt;tt xml:lang="en" xmlns="http://www.w3.org/ns/ttml" xmlns:ttm="http://www.w3.org/ns/ttml#metadata"&gt;
   &lt;head&gt;
     <phrase role="strong">&lt;ttm:agent xml:id="connery" type="person"&gt;</phrase>
@@ -11821,7 +11661,6 @@
 <specref ref="metadata-vocabulary-agent-example-1"/>.</p>
 </div3>
 </div2> <!-- metadata-element-vocabulary -->
-
 <div2 id="metadata-attribute-vocabulary">
 <head>Metadata Attribute Vocabulary</head>
 <p>This section specifies the following attributes in the TT Metadata Namespace
@@ -11869,7 +11708,6 @@
 <eg xml:space="preserve">
 ttm:role
   role ( <emph>S</emph> role )*
-
 role
   : "action"
   | "caption"
@@ -11889,10 +11727,8 @@
   | "title"
   | "transcription"
   | extension-role
-
 extension-role
   : "x-" token-char+
-
 token-char
   : { XML NameChar }    // XML 1.1 Production [4a]
 </eg>
@@ -11919,9 +11755,7 @@
 </div3>
 </div2> <!-- metadata-attribute-vocabulary -->
 </div1> <!-- metadata -->
-
 </body>
-
 <back>
 <div1 id="reduced-infoset">
 <head>Reduced XML Infoset</head>
@@ -12314,13 +12148,10 @@
 <eg xml:space="preserve">
 feature-designation
   : feature-namespace designation
-
 feature-namespace
   : <emph>TT Feature Namespace</emph>                    // http://www.w3.org/ns/ttml/feature/
-
 designation
   : "#" token-char+
-
 token-char
   : { XML NameChar }                        // XML 1.1 Production [4a]
 </eg>
@@ -14725,7 +14556,6 @@
 <loc href="#document-structure-vocabulary-head"><el>head</el></loc>
 </td>
 </tr>
-
 <tr>
 <td><loc href="#feature-time-offset"><code>#time-offset</code></loc></td>
 <td></td>
@@ -14823,14 +14653,11 @@
 <eg xml:space="preserve">
 extension-designation
   : extension-namespace designation
-
 extension-namespace
   : <emph>TT Extension Namespace</emph>                  // http://www.w3.org/ns/ttml/extension/
   | <emph>Other Extension Namespace</emph>               // expressed as an absolute URI
-
 designation
   : "#" token-char+
-
 token-char
   : { XML NameChar }                        // XML 1.1 Production [4a]
 </eg>
@@ -14896,7 +14723,6 @@
 <eg xml:space="preserve">&profile-ttml2-full;</eg>
 </div2>
 </div1>
-
 <div1 id="references">
 <head>References</head>
 <p><emph>This appendix is normative.</emph></p>
@@ -15791,7 +15617,6 @@
 <td>[email protected], [email protected], [email protected]:base</td>
 <td>2,5,9</td>
 </tr>
-
 <tr>
 <td><loc href="#parameter-vocabulary-extension"><code>ttp:extension</code></loc></td>
 <td><code>@requiredExtensions</code></td>