Timed Text (TT) Authoring Format 1.0 – Distribution Format Exchange Profile (DFXP)

1 Introduction

Unless specified otherwise, this section and its sub-sections are non-normative.

The Timed Text Authoring Format (TT AF) Distribution Format Exchange Profile (DFXP) provides a standardized representation of a particular subset of textual information with which stylistic, layout, and timing semantics are associated by an author or an authoring system for the purpose of interchange and potential presentation.

DFXP is expressly designed to meet only a limited set of requirements established by [TTAF1-REQ], and summarized in J Requirements. In particular, only those requirements which service the need of performing interchange with existing, legacy distribution systems are satisfied.

In addition to being used for interchange among legacy distribution content formats, DFXP content may be used directly as a distribution format, providing, for example, a standard content format to reference from a <text> or <textstream> media object element in a [SMIL 2.1] document. Certain properties of DFXP support streamability of content, as described in M Streaming DFXP Content.

Note:

While DFXP was not expressly designed for direct (embedded) integration into a SMIL document instance, such integration is not precluded.

Note:

In some contexts of use, it may be appropriate to employ animated content to depict sign language representations of the same content as expressed by a Timed Text document instance. This use case is not explicitly addressed by DFXP mechanisms, but may be addressed by some external multimedia integration technology, such as SMIL.

1.1 System Model

Use of DFXP is intended to function in a wider context of Timed Text Authoring and Distribution mechanisms that are based upon a system model, depicted in Figure 1 – System Model, wherein the timed text authoring format serves as a bidirectional interchange format among a heterogeneous collection of authoring systems, and as a unidirectional interchange format to a heterogeneous collection of distribution formats after undergoing transcoding or compilation to the target distribution formats as required, and where one particular distribution format is DFXP.

Figure 1 – System Model

1.2 Document Example

A DFXP document instance consists of a tt document element that contains a header and a body, where the header specifies document level metadata, styling definitions and layout definitions, and the body specifies text content intermixed with references to style and layout information and inline timing information.

Example Fragment – DFXP Document Structure
<tt xml:lang="" xmlns="http://www.w3.org/2006/10/ttaf1"> <head> <metadata/> <styling/> <layout/> </head> <body/> </tt>

Document level metadata may specify a document title, description, and copyright information. In addition, arbitrary metadata drawn from other namespaces may be specified.

Example Fragment – DFXP Metadata
<metadata xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata"> <ttm:title>Timed Text DFXP Example</ttm:title> <ttm:copyright>The Authors (c) 2006</ttm:copyright> </metadata>

Styling information may be specified in the form of style specification definitions that are referenced by layout and content information.

In Example Fragment – DFXP Styling, four style sets of specifications are defined, with one set serving as a collection of default styles.

Example Fragment – DFXP Styling
<styling xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling"> <!-- s1 specifies default color, font, and text alignment --> <style xml:id="s1" tts:color="white" tts:fontFamily="proportionalSansSerif" tts:fontSize="22px" tts:textAlign="center" /> <!-- alternative using yellow text but otherwise the same as style s1 --> <style xml:id="s2" style="s1" tts:color="yellow"/> <!-- a style based on s1 but justified to the right --> <style xml:id="s1Right" style="s1" tts:textAlign="end" /> <!-- a style based on s2 but justified to the left --> <style xml:id="s2Left" style="s2" tts:textAlign="start" /> </styling>

Example Fragment – DFXP Styling

<styling xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
  <!-- s1 specifies default color, font, and text alignment -->
  <style xml:id="s1"
    tts:color="white"
    tts:fontFamily="proportionalSansSerif"
    tts:fontSize="22px"
    tts:textAlign="center"
  />
  <!-- alternative using yellow text but otherwise the same as style s1 -->
  <style xml:id="s2" style="s1" tts:color="yellow"/>
  <!-- a style based on s1 but justified to the right -->
  <style xml:id="s1Right" style="s1" tts:textAlign="end" />     
  <!-- a style based on s2 but justified to the left -->
  <style xml:id="s2Left" style="s2" tts:textAlign="start" />
</styling>

Layout information defines one or more regions into which content is intended to be presented. A region definition may reference one or more sets of style specifications in order to permit content flowed in the region to inherit from these styles. In Example Fragment – DFXP Layout, the region definition makes reference to style specification s1 which allows all content flowed into the region to inherit from the region's styles (in the case that a style is not already explicitly specified on content or inherited via the content hierarchy.)

Example Fragment – DFXP Layout
<layout xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling"> <region xml:id="subtitleArea" style="s1" tts:extent="560px 62px" tts:padding="5px 3px" tts:backgroundColor="black" tts:displayAlign="after" /> </layout>

Example Fragment – DFXP Layout

<layout xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
  <region xml:id="subtitleArea"
    style="s1"
    tts:extent="560px 62px"
    tts:padding="5px 3px"
    tts:backgroundColor="black"
    tts:displayAlign="after"
  />
</layout>

The content of a DFXP document instance is expressed in its body, which is organized in terms of block and inline text elements. The hierarchical organization of content elements serves a primary role in determining both spatial and temporal relationships. For example, in Example Fragment – DFXP Body, each paragraph (p element) is flowed into its target region in the specified lexical order; furthermore, the active time interval of each paragraph is timed in accordance to its parent or sibling according to the applicable time containment semantics — in this case, the division parent is interpreted as a parallel time container.

Example Fragment – DFXP Body
<body region="subtitleArea"> <div> <p xml:id="subtitle1" begin="0.76s" end="3.45s"> It seems a paradox, does it not, </p> <p xml:id="subtitle2" begin="5.0s" end="10.0s"> that the image formed on<br/> the Retina should be inverted? </p> <p xml:id="subtitle3" begin="10.0s" end="16.0s" style="s2"> It is puzzling, why is it<br/> we do not see things upside-down? </p> <p xml:id="subtitle4" begin="17.2s" end="23.0s"> You have never heard the Theory,<br/> then, that the Brain also is inverted? </p> <p xml:id="subtitle5" begin="23.0s" end="27.0s" style="s2"> No indeed! What a beautiful fact! </p> <p xml:id="subtitle6a" begin="28.0s" end="34.6s" style="s2Left"> But how is it proved? </p> <p xml:id="subtitle6b" begin="28.0s" end="34.6s" style="s1Right"> Thus: what we call </p> <p xml:id="subtitle7" begin="34.6s" end="45.0s" style="s1Right"> the vertex of the Brain<br/> is really its base </p> <p xml:id="subtitle8" begin="45.0s" end="52.0s" style="s1Right"> and what we call its base<br/> is really its vertex, </p> <p xml:id="subtitle9a" begin="53.5s" end="58.7s"> it is simply a question of nomenclature. </p> <p xml:id="subtitle9b" begin="53.5s" end="58.7s" style="s2"> How truly delightful! </p> </div> </body>

Example Fragment – DFXP Body

<body region="subtitleArea">
  <div>
    <p xml:id="subtitle1" begin="0.76s" end="3.45s">
      It seems a paradox, does it not,
    </p>
    <p xml:id="subtitle2" begin="5.0s" end="10.0s">
      that the image formed on<br/>
      the Retina should be inverted?
    </p>
    <p xml:id="subtitle3" begin="10.0s" end="16.0s" style="s2">
      It is puzzling, why is it<br/>
      we do not see things upside-down?
    </p>
    <p xml:id="subtitle4" begin="17.2s" end="23.0s">
      You have never heard the Theory,<br/>
      then, that the Brain also is inverted?
    </p>
    <p xml:id="subtitle5" begin="23.0s" end="27.0s" style="s2">
      No indeed! What a beautiful fact!
    </p>
    <p xml:id="subtitle6a" begin="28.0s" end="34.6s" style="s2Left">
      But how is it proved?
    </p>
    <p xml:id="subtitle6b" begin="28.0s" end="34.6s" style="s1Right">
      Thus: what we call
    </p>
    <p xml:id="subtitle7" begin="34.6s" end="45.0s" style="s1Right">
      the vertex of the Brain<br/>
      is really its base
    </p>
    <p xml:id="subtitle8" begin="45.0s" end="52.0s" style="s1Right">
      and what we call its base<br/>
      is really its vertex,
    </p>
    <p xml:id="subtitle9a" begin="53.5s" end="58.7s">
      it is simply a question of nomenclature.
    </p>
    <p xml:id="subtitle9b" begin="53.5s" end="58.7s" style="s2">
      How truly delightful!
    </p>
  </div>    
</body>

The first subtitle Subtitle 1 – Time Interval [0.76, 3.45) is presented during the time interval 0.76 to 3.45 seconds. This subtitle inherits its font family, font size, foreground color, and text alignment from the region into which it is presented. Since no region is explicitly specified on the paragraph, the nearest ancestor that specifies a region determines the region. Note also that content is presented at the bottom (after edge) of the containing region due to the tts:displayAlign="after" being specified on the region definition.

Note:

The notation "[X,Y]" denotes a closed interval from X to Y, including X and Y; "[X,Y)" denotes a right half-open interval from X to Y, including X but not including Y; "(X,Y]" denotes a left half-open interval from X to Y, not including X but including Y; "(X,Y)" denotes an open interval from X to Y, not including X or Y.

Subtitle 1 – Time Interval [0.76, 3.45)

The second subtitle continues with the default style, except that it contains two lines of text with an intervening author-specified line break. Note the effects of the use of tts:textAlign="center" to specify the paragraph's alignment in the inline progression direction.

Subtitle 2 – Time Interval [5.0, 10.0)

The third subtitle continues, using a variant style which overrides the default style's foreground color with a different color.

Subtitle 3 – Time Interval [10.0, 16.0)

The fourth subtitle reverts to the default style.

Subtitle 4 – Time Interval [17.2, 23.0)

The fifth subtitle continues, again using a variant style which overrides the default style's foreground color with a different color.

Subtitle 5 – Time Interval [23.0, 27.0)

During the next active time interval, two distinct subtitles are simultaneously active, with the paragraph expressing each subtitle using a different style that overrides color and paragraph text alignment of the default style. Note that the flow order is determined by the lexical order of elements as they appear in the content hierarchy.

Subtitles 6a and 6b – Time Interval [28.0, 34.6)

The next subtitle is specified in a similar manner using a style override to give a paragraph right (end) justified in the inline progression direction.

Subtitle 7 – Time Interval [34.6, 45.0)

The eighth subtitle uses the same style override as the previous subtitle in order to maintain the right (end) justification of the paragraph.

Subtitle 8 – Time Interval [47.3, 49.0)

During the final (ninth) active time interval, two distinct subtitles are again simultaneously active, but with a different style applied to the second paragraph to override the default color. Note that the flow order is determined by the lexical order of elements as they appear in the content hierarchy.

Subtitles 9a and 9b – Time Interval [53.5, 58.7)

The examples shown above demonstrate the primary types of information that may be authored using DFXP: metadata, styling, layout, timing, and content. In typical cases, styling and layout information are separately specified in a document instance. Content information is expressed in a hierarchical fashion that embodies the organization of both spatial (flow) and timing information. Content makes direct or indirect references to styling and layout information and may specify inline overrides to styling.

2 Definitions

2.1 Acronyms

DFXP	Distribution Format Exchange Profile
TT	Timed Text
TT AS	Timed Text Authoring System
TT AF	Timed Text Authoring Format
TT WG	Timed Text Working Group

2.2 Terminology

Abstract Document Instance: An instance of an abstract data set as represented by a Reduced XML Infoset.
Abstract Document Type: A set of constraints that defines a class of XML Information Sets [XML InfoSet].
Attribute Information Item: Each specified or defaulted attribute of an XML document corresponds with an attribute information item as defined by [XML InfoSet], §2.3.
Character Information Item: Each data character appearing in an XML document corresponds with a character information item as defined by [XML InfoSet], §2.6.
Content Processor: A processing system capable of importing (receiving) timed text authoring format content for the purpose of transforming, presenting, or otherwise processing the content.
Content Profile: A collection of features and extensions that are (or may be) employed by timed text authoring format content.
Content Region: A logical region into which rendered content is placed when modeling or performing presentation processing.
Element Information Item: Each element appearing in an XML document corresponds with an element information item as defined by [XML InfoSet], §2.2.
Exchange Profile: A content profile that serves a set of needs for content interchange.
Extension: A syntactic or semantic expression or capability that is defined and labeled (using a extension designation) in another (public or private) specification.
Feature: A syntactic or semantic expression or capability that is defined and labeled (using a feature designation) in this specification (or a future revision of this specification).
Processor: See Content Processor.
Processor Profile: A collection of features and extensions that must or may be implemented (supported) by by a content processor.
Profile Definition Document: A document that defines a specific collection of features and extensions for which support is required or optional in a recipient content processor.
Region: A logical construct that models authorial intention regarding desired or potential presentation processing, and which is represented as a rectangular area of a presentation surface into which content is composed and rendered during presentation processing.
Reduced XML Infoset: An XML Information Set [XML InfoSet] that satisfieds the constraints specify by A Reduced XML Infoset.
Root Container Region: A logical region that establishes a coordinate system into which content regions are placed and optionally clipped.
Timed Text: Textual information that is intrinsically or extrinsically associated with timing information.
Timed Text Authoring Format: A content type that represents timed text media for the purpose of interchange among authoring systems.
Timed Text Authoring System: A content authoring system capable of importing and exporting timed text authoring format content.

2.3 Documentation Conventions

Within normative prose in this specification, the words may, should, and must are defined as follows:

may: Conforming documents and/or TT AF processors are permitted to, but need not behave as described.
should: Conforming documents and/or TT AF processors are strongly recommended to, but need not behave as described.
must: Conforming documents and/or TT AF processors are required to behave as described; otherwise, they are in error.

All normative syntactic definitions of XML representations and other related terms are depicted with a light orange background color and labeled as "XML Representation" or "Syntax Representation", such as in the following:

XML Representation – Element Information Item: example
<example count = integer size = (large\|medium\|small) : medium> Content: (all \| any*) </example>

In an XML representation, bold-face attribute names (e.g. count above) indicate a required attribute information item, and the rest are optional. Where an attribute information item has an enumerated type definition, the values are shown separated by vertical bars, as for size above; if there is a default value, it is shown following a colon. Where an attribute information item has a built-in simple type definition defined in [XML Schema Part 2], a hyperlink to its definition therein is given.

The allowed content of the information item is shown as a grammar fragment, using the Kleene operators ?, * and +. Each element name therein is a hyperlink to its own illustration.

All content of this specification that is not explicitly marked as non-normative is considered to be normative. If a section or appendix header contains the the expression "Non-Normative", then the entirety of the section or appendix is considered non-normative.

All paragraphs marked as a Note are considered non-normative.

Example code fragments are depicted with a light blue-green background color and labeled as "Example Fragment", such as in the following:

Example Fragment – Sample
<tt xml:lang="" xmlns="http://www.w3.org/2006/10/ttaf1"> <head> <metadata/> <styling/> <layout/> </head> <body/> </tt>

3 Conformance

This section specifies the general conformance requirements for TT AF content and processors.

3.1 Content Conformance

A TT AF document instance conforms to this specification if the following criteria are satisfied:

When transporting a document instance in a context in which a MIME Media Type [MIME] identifies the content type of the interchanged document instance, then the specified media type is application/ttaf+xml in conformance with [XML Media Types] § 7, with which an optional profile parameter may appear, the value of which conforms to a profile designator as defined by 5.2 Profiles.
The document instance is or can be represented as a Reduced XML Infoset as defined by A Reduced XML Infoset.
The Reduced XML Infoset that corresponds to the document instance is or can be associated with one of the TT AF Abstract Document Types defined by 4 Document Types.
The Reduced XML Infoset that corresponds to the document instance is a Valid Abstract Document Instance of the associated Abstract Document Type.
The Reduced XML Infoset satisfies all additional mandatory syntactic and semantic constraints defined by this specification. In addition, this Infoset should satisfy the web content accessibility guidelines specified by [WCAG].

3.2 Processor Conformance

3.2.1 Generic Processor Conformance

A TT AF processor conforms to this specification if the following generic processor criteria are satisfied:

The processor provides at least one mechanism for notionally instantiating a Reduced XML Infoset representation of a conformant TT AF document instance.
If a process does or can perform validation of a candidate TT AF document instance, then it provides at least one mechanism to implicitly or explicitly associate the Reduced XML Infoset representation of a conformant TT AF document instance with one of the TT AF Abstract Document Types defined by 4 Document Types.
The processor does not a priori reject or abort the processing of a conformant TT AF document instance unless the processor does not support some required (mandatory) feature specified or implied by a TT AF content profile declared to apply to the document instance.
The processor supports all mandatory processing semantics defined by this specification.
If the processor supports some optional processing semantics defined by this specification, then it does so in a manner consistent with the defined semantics.

A TT AF document instance for which a compliance claim is made must specify either (1) a ttp:profile attribute on its root tt element as defined by 6.2.7 ttp:profile or (2) a ttp:profile element as a child of the head element as defined by 6.1.1 ttp:profile.

4 Document Types

This section defines the following TT AF Abstract Document Types:

4.1 DFXP Content

Each abstract document type consists of the following constraints:

a non-empty collection of element types, where each element type consists of a name, a (possibly empty) collection of attributes, and a content specification
a non-empty collection of element types that may appear as the document element

An Abstract Document Instance may be assessed in terms of validity, and is considered to be a Valid Abstract Document Instance if it satisfies the following condition: if after

pruning all element information items whose names are not members of the collection of element types defined by the associated abstract document type, then
pruning character information item children from any remaining element in case that all character children of the element denote XML whitespace characters and the element's type is defined as empty in the associated Abstract Document Type, and then
pruning all attribute information items having expanded names such that the namespace URI of the expanded names are not listed in Table 1 – Namespaces,

then the document element is one of the document element types permitted by the associated abstract document type, the descendants of the document element satisfy their respective element type's content specifications, all required attributes are present, and the declared value of each attribute satisfies the type declared by the associated abstract document type.

Note:

While a conformant processor may not a priori reject a conformant document instance that adheres to a supported content profile, a given document instance may be constrained by the author or authoring tool to satisfy a more restrictive definition of validity.

4.1 DFXP Content

DFXP Content is an abstract document type of the Timed Text Authoring Format intended to be used for interchange among distribution systems. This document type is defined in terms of the element and attribute vocabulary specified in 5 Vocabulary.

This specification defines two types of normative schemas that may be used to validate a subset of conformant DFXP document instances:

C.1 Relax NG Schema
C.2 XML Schema Definition (XSD) Schema

The (root) document element of a DFXP document instance must be a tt element, as defined by 7.1.1 tt.

Note:

The schemas included in this specification do not validate all syntactic constraints defined by this specification. In particular, performing validation with one of the above referenced schemas may result in a false positive indication of validity. However, their use will not produce a false negative indication of validity when used with a compliant validating processor.

5 Vocabulary

This section defines the namespaces, profiles, and vocabulary (as an element an attribute catalog) of the Timed Text Authoring Format (TT AF) as follows:

5.1 Namespaces
5.2 Profiles
5.3 Catalog

5.1 Namespaces

The Timed Text Authoring Format (TT AF) employs a number of namespaces for elements and certain global attributes. The following table specifies this set of namespaces and indicates the default prefix used within this specification and the normative URI that denotes each namespace.

Note:

In a specific document instance, it is not required that the default prefixes shown below are used. Any prefix or namespace binding that satisfies the constraints of XML Namespaces may be used that is associated with the specified namespace URI.

Table 1 – Namespaces
Name	Prefix	Value
TT	`tt:`	`http://www.w3.org/2006/10/ttaf1`
TT Parameter	`ttp:`	`http://www.w3.org/2006/10/ttaf1#parameter`
TT Style	`tts:`	`http://www.w3.org/2006/10/ttaf1#styling`
TT Metadata	`ttm:`	`http://www.w3.org/2006/10/ttaf1#metadata`
TT Profile	none	`http://www.w3.org/2006/10/ttaf1/profile`
TT Feature	none	`http://www.w3.org/2006/10/ttaf1/feature`
TT Extension	none	`http://www.w3.org/2006/10/ttaf1/extension`

Note:

If a reference to an element type is used in this specification and the name of the element type is not namespace qualified, then the TT Namespace applies.

For certain namespaces defined above, the default prefix is specified as none if no XML vocabulary is defined in the namespace by this specification (nor expected to be defined in a future version of this specification). In such cases, the use of the namespace URI is for purposes other than defining XML vocabulary, e.g., for designating profiles, features, extensions and for dereferencing standard profile definitions.

All TT AF Namespaces are mutable [NSState]; all undefined names in these namespaces are reserved for future standardization by the W3C.

5.2 Profiles

The Timed Text Authoring Format (TT AF) employs a number of standard, predefined profiles of its vocabulary and associated semantics. The following table specifies this set of profiles, indicating a normative name and designator for each predefined profile, and where each of these profiles is formally elaborated in G Profiles.

Table 2 – Profiles
Name	Designator
DFXP Transformation	`http://www.w3.org/2006/10/ttaf1/profile/dfxp-transformation`
DFXP Presentation	`http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation`
DFXP Full	`http://www.w3.org/2006/10/ttaf1/profile/dfxp-full`

A profile designator must adhere to the xsd:anyURI data type defined by [XML Schema Part 2], §3.2.17. If the profile designator is expressed as a relative URI, then it must be absolutized by using the TT Profile Namespace value as the base URI.

Note:

For example, if a profile designator is expressed as dfxp-presentation, then the absolutized profile designator would be http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation.

A profile designator is not restricted to the set of designators enumerated in Table 2 – Profiles, but may be any URI that feasibly dereferences a TT AF Profile Definition Document.

The profile of TT AF that must be supported by a TT AF content processor in order to process a document instance is specified either (1) by specifying a ttp:profile attribute on the root tt element, as defined by 6.2.7 ttp:profile, or (2) by including one or more ttp:profile elements in the head element, in accordance with 6.1.1 ttp:profile.

If a ttp:profile element appears as a descendant of the tt element, then the ttp:profile attribute should not be specified on the tt element. If both a ttp:profile element and a ttp:profile attribute are present (in a given document instance), then the ttp:profile attribute must be ignored for the purpose of determining the declared profile requirements.

If more than one ttp:profile element appears in a TT AF document instance, then all specified profiles apply simultaneously. In such a case, if some feature or some extension is specified by one profile to be used (mandatory and enabled) and by another profile to be required (mandatory) or optional (voluntary), then that feature or extension must be considered to be used (mandatory and enabled); if some feature or some extension is specified by one profile to be merely required (mandatory) and by another profile to be optional (voluntary), then that feature or extension must be considered to be required (mandatory).

If neither ttp:profile attribute nor ttp:profile element is present in a TT AF document instance, and if the document interchange context does not specify a profile, then the DFXP Transformation profile applies.

Note:

It is intended that the ttp:profile attribute be used when the author wishes to reference one of the standard, predefined profiles of TT AF content, and does not wish to modify (by supersetting or subsetting) that profile. This attribute may also be used by an author to indicate the use of a non-standard profile, in which case the specified profile designator expresses a URI that denotes an externally defined TT AF Profile Definition Document. However, it is not required that a conformant TT AF content processor be able to dereference such an externally specified profile definition.

In contrast, it is intended that the ttp:profile element be used when the author wishes to make use of a modified predefined profile or wishes to include in the document instance a non-standard profile definition not based upon one of the predefined profiles.

A predefined profile is supersetted by specifying some feature or extension to be required (mandatory) that was either not specified in the underlying, baseline profile or was specified as optional (voluntary) in the baseline profile. A predefined profile is subsetted by specifying some feature or extension to be optional (voluntary) that was specified as required in the underlying, baseline profile.

When a baseline profile is modified by subsetting, the resulting, derived profile is referred to as a subtractive profile; when modified by supersetting, the result is referred to as an additive profile. It is also possible to define a derived profile that is simultaneously subtractive and additive.

If a TT AF document instance makes use of a feature defined by E.1 Feature Designations and if the intended use of the document requires the recognition and processing of that feature, then the document must include a required feature or a used feature specification in one of its declared or referenced profiles. If a TT AF document instance makes use of an extension designatable by F.1 Extension Designations and if the intended use of the document requires the recognition and processing of that extension, then the document must include a required extension or a used extension specification in one of its declared or referenced profiles.

Note:

A required or used feature specification is expressed directly (or indirectly by referring to a profile) by means of a ttp:feature element where the value of its value attribute is required or use, respectively. A required or used extension specification is expressed directly (or indirectly by referring to a profile) by means of a ttp:extension element where the value of its value attribute is required or use, respectively.

An example of an author defined additive, derived profile of the DFXP Presentation profile is shown below in Example Fragment – DFXP Additive Profile.

Example Fragment – DFXP Additive Profile
<tt xml:lang="" xmlns="http://www.w3.org/2006/10/ttaf1"> <head> <profile use="dfxp-presentation" xmlns="http://www.w3.org/2006/10/ttaf1#parameter"> <features xml:base="http://www.w3.org/2006/10/ttaf1/feature"> <feature value="required">#fontStyle-italic</feature> </features> </profile> </head> <body/> </tt>

Example Fragment – DFXP Additive Profile

<tt xml:lang="" xmlns="http://www.w3.org/2006/10/ttaf1">
 <head>
   <profile use="dfxp-presentation" xmlns="http://www.w3.org/2006/10/ttaf1#parameter">
     <features xml:base="http://www.w3.org/2006/10/ttaf1/feature">
       <feature value="required">#fontStyle-italic</feature>
     </features>
   </profile>
 </head>
 <body/>
</tt>

Note:

In the above example, the baseline profile is declared to be the DFXP Presentation profile, which is then additively modified by making the #fontStyle-italic feature required (rather than optional as it is defined in G.2 DFXP Presentation Profile). Note also the resetting of the default XMLNS binding on the profile element to the TT Parameter Namespace.

5.3 Catalog

The vocabulary of the Timed Text Authoring Format (TT AF) is defined in the following major catalogs (divisions of vocabulary):

5.3.1 Core Catalog
5.3.2 Extension Catalog

The core catalog defines the baseline, core vocabulary of the TT AF, and, in particular, the vocabulary of DFXP. The extension catalog serves as a placeholder for extensions to the core vocabulary defined by DFXP.

5.3.1 Core Catalog

The core vocabulary catalog is intended to satisfy the needs of DFXP while providing a baseline vocabulary for future profiles. This vocabulary is divided into distinct categories, specified in detail in the following sections:

6 Parameters
7 Content
8 Styling
9 Layout
10 Timing
11 Animation
12 Metadata

The core element vocabulary specified for use with a TT AF document instance is enumerated in Table 3 – Element Vocabulary.

Table 3 – Element Vocabulary
Module	Elements
Animation	set
Content	body, div, p, span, br
Document	tt
Head	head
Layout	layout, region
Metadata	metadata
Metadata Items	ttm:actor, ttm:agent, ttm:copyright, ttm:desc, ttm:name, ttm:title
Parameter Items	ttp:profile, ttp:features, ttp:feature, ttp:extensions, ttp:extension
Styling	styling, style

Element vocabulary groups that are used in defining content models for TT AF element types are enumerated in Table 4 – Element Vocabulary Groups.

Table 4 – Element Vocabulary Groups
Group	Elements
Animation.class	set
Block.class	div \| p
Inline.class	span \| br \| `#PCDATA`
Metadata.class	metadata \| ttm:agent \| ttm:copyright \| ttm:desc \| ttm:title
Parameters.class	ttp:profile

The attribute vocabulary specified for use with the core vocabulary catalog is enumerated in Table 5 – Attribute Vocabulary.

Table 5 – Attribute Vocabulary
Module	Attributes
Core Attributes	xml:id, xml:lang, xml:space
Layout	region
Metadata Attributes	ttm:agent, ttm:role
Parameter Attributes	ttp:cellResolution, ttp:clockMode, ttp:frameRate, ttp:frameRateMultipler, ttp:markerMode, ttp:pixelAspectRatio, ttp:profile, ttp:smpteMode, ttp:subFrameRate, ttp:tickRate, ttp:timeBase
Styling	style
Styling Attributes	tts:backgroundColor, tts:color, tts:direction, tts:display, tts:displayAlign, tts:dynamicFlow, tts:extent, tts:fontFamily, tts:fontSize, tts:fontStyle, tts:fontWeight, tts:lineHeight, tts:opacity, tts:origin, tts:overflow, tts:padding, tts:showBackground, tts:textAlign, tts:textDecoration, tts:textOutline, tts:unicodeBidi, tts:visibility, tts:wrapOption, tts:writingMode, tts:zIndex
Timing Attributes	begin, dur, end, timeContainer

Note:

Only those attributes defined as either (1) global, i.e., namespace qualified, or (2) shared element-specific, i.e., not namespace qualified but shared across multiple element types, are listed in Table 5 – Attribute Vocabulary above.

Note:

All vocabulary defined by the TT AF consistently makes use of the so-called lowerCamelCase naming convention. In some cases, this results in the change of a name when the name was based upon another specification that used a different naming convention.

5.3.2 Extension Catalog

The extension vocabulary catalog is intended for use by future profiles of the TT AF, and is not further defined by this version of this specification.

In addition to standardized extension vocabulary, a conforming TT AF document instance may contain arbitrary namespace qualified elements that reside in any namespace other than those namespaces defined for use with this specification. Furthermore, a conforming TT AF document instance may contain arbitrary namespace qualified attributes on TT AF defined vocabulary where such attributes reside in any namespace other than those defined for use with this specification.

6 Parameters

This section specifies the parameters matter of the core vocabulary catalog, where parameters are to be understood as information that is either (1) essential or (2) of significant importance for the purpose of interpreting the semantics of other types of information expressed by core vocabulary items or for establishing a processing context by means of which TT AF content can be related to an external environment.

6.1 Parameter Element Vocabulary

The following elements, all defined in the TT Parameter Namespace, specify parametric information that applies to a document or a content processor:

6.1.1 ttp:profile
6.1.2 ttp:features
6.1.3 ttp:feature
6.1.4 ttp:extensions
6.1.5 ttp:extension

6.1.1 ttp:profile

The ttp:profile element is used to specify a collection of used (mandatory and enabled), required (mandatory), and optional (voluntary) features and extensions that must or may be supported by a TT AF content processor in order to process a TT AF document that makes use (or may make use) of such features and extensions.

Note:

The difference between a feature and an extension is where it is defined an how it is labeled: if defined in this specification (or a future revision thereof) and labeled with a feature designation in E Features, then it is considered to be a feature; if defined in another specification and labeled there with an extension designation, then it is considered to be an extension. In general, features are expected to be defined by the W3C standards process, while extensions are expected to be defined by third parties.

This specification defines two distinct uses of the ttp:profile element:

as a child of the head element within a TT AF document instance;
as the root element of a TT AF Profile Definition document instance;

When a tt:profile element appears within a TT AF document instance, its purpose is to express authorial intentions about which features and extensions must or may be supported by a recipient content processor. In addition, the element indirectly expresses information about the set of features or extensions that are (or may expected to be) used by the document instance.

When a tt:profile element is used by a TT AF Profile Definition document instance, it serves to publish a machine readable specification of a specific TT AF content profile, of which this specification defines four such Profile Definition Documents in G Profiles.

The ttp:profile element accepts as its children zero or more elements in the Metadata.class element group, followed by zero or more ttp:features elements, followed by zero or more ttp:extensions elements.

XML Representation – Element Information Item: ttp:profile
<ttp:profile use = string xml:id = ID {any attribute not in default or any TT namespace}> Content: Metadata.class, ttp:features, ttp:extensions* </ttp:profile>

If specified, the use attribute must adhere to the xsd:anyURI data type defined by [XML Schema Part 2], §3.2.17, and, furthermore, must denote a profile designator in accordance with 5.2 Profiles. In this case, the profile designator must refer to (1) a standard, predefined TT AF Profile Definition Document as defined by G Profiles, or (2) a dereferenceable resource representing a valid TT AF Profile Definition document instance. In either case, the referenced profile serves as the baseline profile of the specifying ttp:profile element.

If the use attribute is not specified, then the baseline profile of the ttp:profile element must be considered to be the empty (null) profile, i.e., a profile definition containing no feature or extension specifications.

The collection of features and extensions of a profile are determined according to the following ordered rules:

initialize the features and extensions of the profile to the empty set;
if a use attribute is present, then augment the profile with the set of features and extensions specified by the referenced baseline profile;
for each ttp:feature and ttp:extension element descendant of the ttp:profile element, using a post-order traversal, merge the specified feature or extension with the features and extensions of the profile, where merging a feature or extension entails replacing an existing feature or extension specification, if it already exists, or adding a new feature or extension specification, if it does not yet exist in the profile;

A conformant TT AF processor is not required to be able to dereference a TT AF Profile Definition Document that is not one of the standard, predefined profiles defined by G Profiles. A conformant TT AF processor may make use of a built-in, static form of each standard, predefined profile so as not to require dereferencing a network resource.

If a TT AF processor is unable to dereference a non-standard TT AF Profile Definition Document, then it must not further process the document without the presence of an explicit override from an end-user or some implementation specific parameter traceable to an end-user or to a user or system configuration setting. If a TT AF processor aborts processing of a TT AF document instance due to the inability to reference a non-standard TT AF Profile Definition Document, then some end-user notification should be given unless the end-user or system has disabled such a notification, or if the processor does not permit or entail the intervention of an end-user.

The ttp:profile element is illustrated by the following example.

Example Fragment – ttp:profile
<ttp:profile use="dfxp-presentation"> <ttp:features xml:base="http://www.w3.org/2006/10/ttaf1/feature"> <ttp:feature>#rollUp</ttp:feature> </ttp:features> </ttp:profile>

Note:

In the above example, the DFXP presentation profile is used as the baseline profile. This baseline profile is then supersetted (thus creating an additive derived profile) by requiring support for #rollUp feature.

6.1.2 ttp:features

The ttp:features element is a container element used to group infomation about feature support requirements.

The ttp:features element accepts as its children zero or more elements in the Metadata.class element group, followed by zero or more ttp:feature elements.

XML Representation – Element Information Item: ttp:features
<ttp:features xml:base = string : TT Feature Namespace xml:id = ID {any attribute not in default or any TT namespace}> Content: Metadata.class, ttp:feature </ttp:features>

If specified, the xml:base attribute must (1) adhere to the xsd:anyURI data type defined by [XML Schema Part 2], §3.2.17, (2) express an absolute URI that adheres to [XML Base] and, (3) express a feature namespace as defined by E.1 Feature Designations. If not specified, the xml:base attribute's default value applies, which is the TT Feature Namespace.

The xml:base attribute is used to permit the abbreviation of feature designation URIs expressed by child ttp:feature elements.

6.1.3 ttp:feature

The ttp:feature element is used to specify infomation about support requirements for a particular feature.

The children of the ttp:feature element must express a non-empty sequence of character information items that adheres to the xsd:anyURI data type defined by [XML Schema Part 2], §3.2.17.

XML Representation – Element Information Item: ttp:feature
<ttp:feature value = (optional\|required\|use) : required xml:id = ID {any attribute not in default or any TT namespace}> Content: #PCDATA </ttp:feature>

If the URI expressed by the content of the ttp:feature element is a relative URI, then, when combined with the feature namespace value expressed by the xml:base attribute of the nearest ancestor ttp:features element, it must express an absolute URI. In either case (original absolute URI or resulting absolutized URI), the URI expressed by the ttp:feature element must further adhere to the syntax of a feature designation as defined by E.1 Feature Designations.

If the URI expressed by the content of the ttp:feature element is a relative URI, then an xml:base attribute should be specified on the nearest ancestor ttp:features element.

The value attribute specifies whether a conforming TT AF processor must or may implement the designated feature in order to process the document. If the value of the value attribute is optional, then the processor need not implement or otherwise support the feature in order to process the document; if the value is required, then the processor must implement or otherwise support the feature in order to process the document; if the value is use, then the processor must both (1) implement or otherwise support the feature and (2) enable (activate) use of the feature.

Note:

The default value of the value attribute is required, as indicated in the above element information item definition. Therefore, if a value attribute is not specified on a ttp:feature element, it is equivalent to specifying that support for the feature is required.

If the value of the value attribute is required or use, and if the TT AF processor implementation does not support the feature, then it must not further process the document without the presence of an explicit override from an end-user or some implementation specific parameter traceable to an end-user or to a user or system configuration setting. If a TT AF processor aborts processing of a TT AF document instance due to the specification of a required, but unsupported feature by this element, then some end-user notification should be given unless the end-user or system has disabled such a notification, or if the processor does not permit or entail the intervention of an end-user.

If the value of the value attribute is optional, and if the TT AF processor implementation does not support the feature, then it may further process the document even in the case that some use of the feature is present in the document. In the case of actual use of a feature designated as optional, the default semantics associated with that feature apply; that is, the processor may behave as if the feature were not actually used or referenced by the document. Notwithstanding the above, the syntactic presence or reference to an optional feature by a document must not be considered to be a violation of document validity or a barrier to further processing if the syntactic expression is well-formed and valid.

The ttp:feature element is illustrated by the following example.

Example Fragment – ttp:feature
<ttp:profile use="http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation"> <ttp:features xml:base="http://www.w3.org/2006/10/ttaf1/feature"> <ttp:feature value="required">#fontStyle-italic</ttp:feature> <ttp:feature value="required">#textDecoration-under</ttp:feature> </ttp:features> </ttp:profile>

Example Fragment – ttp:feature

<ttp:profile use="http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation">
  <ttp:features xml:base="http://www.w3.org/2006/10/ttaf1/feature">
    <ttp:feature value="required">#fontStyle-italic</ttp:feature>
    <ttp:feature value="required">#textDecoration-under</ttp:feature>
  </ttp:features>
</ttp:profile>

Note:

In the above example, the DFXP presentation profile is used as the baseline profile. This baseline profile is then modified by two ttp:feature elements in order to superset the baseline profile (since neither #fontStyle-italic nor #textDecoration-under are required by the DFXP presentation profile). Note that the explicit specification of required on the value attribute on these two ttp:feature elements is not strictly necessary, since it is the default value of this attribute.

The effect of this example is to express authorial intentions that italic font style and text underlining must be supported.

6.1.4 ttp:extensions

The ttp:extensions element is a container element used to group infomation about extension support requirements.

The ttp:extensions element accepts as its children zero or more elements in the Metadata.class element group, followed by zero or more ttp:extension elements.

XML Representation – Element Information Item: ttp:extensions
<ttp:extensions xml:base = string : TT Extension Namespace xml:id = ID {any attribute not in default or any TT namespace}> Content: Metadata.class, ttp:extension </ttp:extensions>

If specified, the xml:base attribute must (1) adhere to the xsd:anyURI data type defined by [XML Schema Part 2], §3.2.17, (2) express an absolute URI that adheres to [XML Base] and, (3) express an extension namespace as defined by F.1 Extension Designations. If not specified, the xml:base attribute's default value applies, which is the TT Extension Namespace.

The xml:base attribute is used to permit the abbreviation of feature designation URIs expressed by child ttp:extension elements.

6.1.5 ttp:extension

The ttp:extension element is used to specify infomation about support requirements for a particular extension.

The children of the ttp:extension element must express a non-empty sequence of character information items that adheres to the xsd:anyURI data type defined by [XML Schema Part 2], §3.2.17.

XML Representation – Element Information Item: ttp:extension
<ttp:extension value = (optional\|required\|use) : required xml:id = ID {any attribute not in default or any TT namespace}> Content: #PCDATA </ttp:extension>

If the URI expressed by the content of the ttp:extension element is a relative URI, then, when combined with the extension namespace value expressed by the xml:base attribute of the nearest ancestor ttp:extensions element, it must express an absolute URI. In either case (original absolute URI or resulting absolutized URI), the URI expressed by the ttp:extension element must further adhere to the syntax of an extension designation as defined by F.1 Extension Designations.

If the URI expressed by the content of the ttp:feature element is a relative URI, then an xml:base attribute should be specified on the nearest ancestor ttp:extensions element.

The value attribute specifies whether a conforming TT AF processor must or may implement the designated extension in order to process the document. If the value of the value attribute is optional, then the processor need not implement or otherwise support the extension in order to process the document; if the value is required, then the processor must implement or otherwise support the extension in order to process the document; if the value is use, then the processor must both (1) implement or otherwise support the extension and (2) enable (activate) use of the extension.

Note:

The default value of the value attribute is required, as indicated in the above element information item definition. Therefore, if a value attribute is not specified on a ttp:extension element, it is equivalent to specifying that support for the extension is required.

If the value of the value attribute is required or use, and if the TT AF processor implementation does not support the extension, then it must not further process the document without the presence of an explicit override from an end-user or some implementation specific parameter traceable to an end-user or to a user or system configuration setting. If a TT AF processor aborts processing of a TT AF document instance due to the specification of a required, but unsupported extension by this element, then some end-user notification should be given unless the end-user or system has disabled such a notification, or if the processor does not permit or entail the intervention of an end-user.

If the value of the value attribute is optional, and if the TT AF processor implementation does not support the extension, then it may further process the document even in the case that some use of the extension is present in the document. In the case of actual use of an extension designated as optional, the default semantics associated with that extension apply; that is, the processor may behave as if the extension were not actually used or referenced by the document. Notwithstanding the above, the syntactic presence or reference to an optional extension by a document must not be considered to be a violation of document validity or a barrier to further processing if the syntactic expression is well-formed and valid.

The ttp:extension element is illustrated by the following example.

Example Fragment – ttp:extension
<ttp:profile use="http://www.w3.org/2006/10/ttaf1/profile/dfxp-transformation"> <ttp:extensions xml:base="http://foo.bar.example.org/ttaf1/extension"> <ttp:extension value="use">#prefilter-by-language</ttp:extension> </ttp:extensions> </ttp:profile>

Example Fragment – ttp:extension

<ttp:profile use="http://www.w3.org/2006/10/ttaf1/profile/dfxp-transformation">
  <ttp:extensions xml:base="http://foo.bar.example.org/ttaf1/extension">
    <ttp:extension value="use">#prefilter-by-language</ttp:extension>
  </ttp:extensions>
</ttp:profile>

Note:

In the above example, the DFXP transformation profile is used as the baseline profile. This baseline profile is then supersetted by specifying that support and use is required for a private extension defined in a third party namespace.

The effect of this example is to express authorial intentions that a recipient processor must support the DFXP transformation profile and must also support and use an extension defined by a third party.

6.2 Parameter Attribute Vocabulary

The following attributes are defined in the TT Parameter Namespace.

6.2.1 ttp:cellResolution
6.2.2 ttp:clockMode
6.2.3 ttp:frameRate
6.2.4 ttp:frameRateMultiplier
6.2.5 ttp:markerMode
6.2.6 ttp:pixelAspectRatio
6.2.7 ttp:profile
6.2.8 ttp:smpteMode
6.2.9 ttp:subFrameRate
6.2.10 ttp:tickRate
6.2.11 ttp:timeBase

Unless explicitly stated otherwise, linear white-space (LWSP) may appear between tokens of a value of a TT Parameter.

6.2.1 ttp:cellResolution

The ttp:cellResolution attribute may be used by an author to express the number of horizontal and vertical cells into which the root container region area is divided for the purpose of expressing presentation semantics in terms of a uniform grid.

If specified, the value of this attribute must adhere to the following syntax:

Syntax Representation – ttp:cellResolution
ttp:cellResolution : columns rows // columns != 0; rows != 0 columns \| rows : <digit>+

If not specified, the number of columns and rows must be considered to be 32 and 15, respectively. If specified, then columns or rows must not be zero (0).

Note:

The choice of values 32 and 15 are based on this being the maximum number of columns and rows defined by [CEA-608-C].

A ttp:cellResolution attribute is considered to be significant only when specified on the tt element.

Note:

The use of a uniform grid is employed only for the purpose of measuring lengths and expressing coordinates. In particular, it is not assumed that the presentation of text or the alignment of individual glyph areas is coordinated with this grid. Such alignment is possible, but requires the use of a monospaced font and a font size whose EM square exactly matches the cell size.

6.2.2 ttp:clockMode

The ttp:clockMode attribute is used to specify the interpretation of time expressions as real-time time coordinates when operating with time base of clock as defined by 6.2.11 ttp:timeBase.

Note:

See 10.3 Time Value Expressions for the specification of time expression syntax.

If specified, the value of this attribute must adhere to the following syntax:

Syntax Representation – ttp:clockMode
ttp:clockMode : "local" \| "gps" \| "utc"

If the time base, defined by 6.2.11 ttp:timeBase, is designated as clock, then this parameter applies as follows: if the parameter's value is local, then time expressions are interpreted as local wall-clock time coordinates; if utc, then time expressions are interpreted as UTC time coordinates [UTC]; if gps, then time expressions are interpreted as GPS time coordinates [GPS].

Note:

The primary difference between GPS time and UTC time is that GPS time is not adjusted for leap seconds, while UTC time is adjusted as follows: UTC = TAI (Temp Atomique International) + leap seconds accumulated since 1972. TAI is maintained by the Bureau International des Poids et Mesures (BIPM) in Sevres, France. The GPS system time is steered to a Master Clock (MC) at the US Naval Observatory which is kept within a close but unspecified tolerance of TAI.

If not specified, the value of this parameter must be considered to be utc.

A ttp:clockMode attribute is considered to be significant only when specified on the tt element.

6.2.3 ttp:frameRate

The ttp:frameRate attribute is used to specify the frame rate of a related media object or the intrinsic frame rate of a document instance in case it is intended to function as an independent media object.

If specified, the value of this attribute must adhere to the following syntax:

Syntax Representation – ttp:frameRate
ttp:frameRate : <digit>+ // value > 0

The frame rate that applies to a document instance is used to interpret time expressions that are expressed in frames as defined by 10.3.1 <timeExpression>.

A frame is interpreted as a division of a second of media time, such that if the frame rate is specified as F, then a second of media time is divided into F intervals of equal duration, where each interval is labeled as frame f, with f ∈ [0…F−1].

If not specified, the frame rate must be considered to be equal to some application defined frame rate, or if no application defined frame rate applies, then thirty (30) frames per second. If specified, then the frame rate must be greater than zero (0).

A ttp:frameRate attribute is considered to be significant only when specified on the tt element.

6.2.4 ttp:frameRateMultiplier

The ttp:frameRateMultiplier attribute is used to specify a multiplier to be applied to the frame rate specified by a ttp:frameRate attribute in order to compute the effective frame rate.

If specified, the value of this attribute must adhere to the following syntax:

Syntax Representation – ttp:frameRateMultiplier
ttp:frameRateMultiplier : numerator ( ":" denominator )? // denominator != 0 numerator \| denominator : <digit>+

A frame rate multiplier is used when the desired frame rate cannot be expressed as an integral number of frames per second.

If not specified, the frame rate multiplier must be considered to be equal to one (1:1). If a denominator is specified, then it must not be zero (0). If no denominator is specified, then a denominator of one (1) applies.

A ttp:frameRateMultiplier attribute is considered to be significant only when specified on the tt element.

Note:

The frame rate multiplier used for synchronizing with NTSC [SMPTE 170M] formatted video objects at 30 frames per second is nominally 1000:1001. The nominal frame rate of NTSC video is defined as the chrominance sub-carrier frequency of 3,579,545.45…Hz (= 5.0MHz × 63/88) times the ratio 2/455 divided by the number of horizontal lines per frame of 525, which yields a frame rate of 29.970029970029… (= 30 × 1000/1001) frames per second. Other frame rate multipliers apply to different regions of usage and video format standards.

Note:

Except in the case of PAL/M, the frame rate multiplier used for synchronizing with PAL formatted video objects at 25 frames per second is nominally 1:1.

6.2.5 ttp:markerMode

The ttp:markerMode attribute is used to specify constraints on the interpretation and use of time expressions that correspond with [SMPTE 12M] time coordinates when operating with time base of smpte as defined by 6.2.11 ttp:timeBase.

If specified, the value of this attribute must adhere to the following syntax:

Syntax Representation – ttp:markerMode
ttp:markerMode : "continuous" \| "discontinuous"

If the time base, defined by 6.2.11 ttp:timeBase, is designated as smpte, then this parameter applies as follows: if the parameter's value is continuous, then [SMPTE 12M] time coordinates may be assumed to be linear and either monotonically increasing or decreasing; however, if discontinuous, then any assumption must not be made regarding linearity or monotonicity of time coordinates.

If not specified, the value of this parameter must be considered to be continuous.

A ttp:markerMode attribute is considered to be significant only when specified on the tt element.

If a value of discontinuous applies, then time expressions must not be converted to either media time or real time coordinates, arithmetical operators (addition, multiplication) are not defined on time expressions, and, consequently, any expression of a duration must be ignored.

Note:

When operating with smpte time base and discontinuous marker mode, there is no effective time coordinate space; rather, all time expressions are interpreted as labeled synchronization events (markers), where some external synchronization context emits these events, which, when they correspond with time expressions that denote the same label, cause a temporal interval to begin or end accordingly.

An additional side-effect of operating in discontinuous mode is that time expressions of children have no necessary relationship with time expressions of their temporal container; that is, temporal containers and children of these containers are temporally activated and inactivated independently based on the occurrence of a labeled synchronization (marker) event.

Note:

The notion of marker discontinuity as captured by this parameter is logically independent from the method used to count frames as expressed by the ttp:smpteMode parameter. In particular, even if the ttp:smpteMode parameter is specified as dropNTSC or dropPAL, the marker mode may be specified as continuous, even in the presence of frame count discontinuities induced by the frame counting method, unless there were some other non-linearity or discontinuity in marker labeling, for example, two consecutive frames labeled as 10:00:00:00 and 10:00:01:00.

6.2.6 ttp:pixelAspectRatio

The ttp:pixelAspectRatio attribute may be used by a content author to express the aspect ratio of non-square pixels in the production of content that makes use of pixel coordinates.

If specified, the value of this attribute must adhere to the following syntax:

Syntax Representation – ttp:pixelAspectRatio
ttp:pixelAspectRatio : width ":" height // width != 0; height != 0 width \| height : <digit>+

If not specified, then square pixels (i.e., aspect ratio 1:1) must be assumed to apply. If specified, then width or height must not be zero.

A ttp:pixelAspectRatio attribute is considered to be significant only when specified on the tt element.

Note:

This parameter may be used by a content transcoder or translator in order to convert pixel measurements between different pixel aspect ratios while still maintaining authorial layout intentions.

6.2.7 ttp:profile

The ttp:profile attribute may be used by a content author to express the profile of the Timed Text Authoring Format (TT AF) used in a document instance.

If specified, the value of this attribute must adhere to the xsd:anyURI data type defined by [XML Schema Part 2], §3.2.17, and, further, must specify a profile designator in accordance with 5.2 Profiles.

A ttp:profile attribute is considered to be significant only when specified on the tt element.

6.2.8 ttp:smpteMode

The ttp:smpteMode attribute is used to specify constraints on the interpretation and use of frame counts that correspond with [SMPTE 12M] time coordinates when operating with time base of smpte as defined by 6.2.11 ttp:timeBase.

If specified, the value of this attribute must adhere to the following syntax:

Syntax Representation – ttp:smpteMode
ttp:smpteMode : "dropNTSC" \| "dropPAL" \| "nonDrop"

If the time base, defined by 6.2.11 ttp:timeBase, is designated as smpte, then this parameter applies as follows: if the parameter's value is nonDrop, then, within any given second of a time expression, frames count from 0 to N−1, where N is the value specified by the ttp:frameRate parameter, but while ignoring any value specified by the ttp:frameRateMultiplier parameter.

Note:

When operating in nonDrop mode, a second of a time expression may or may not be equal to a second of real time during normal (1x speed) forward playback. If the ttp:frameRateMultiplier parameter is specified and is not equal to 1:1, then a second of a time expression will either be shorter or longer than a second of elapsed play in real time.

If this parameter's value is dropNTSC, then, within any given second of a time expression except the second 00, frames count from 0 to N−1, where N is the value specified by the ttp:frameRate parameter, but while ignoring any value specified by the ttp:frameRateMultiplier parameter. If the second of a time expression is 00 and the minute of the time expression is not 00, 10, 20, 30, 40, or 50, then frame codes 00 and 01 are dropped during that second; otherwise, these frame codes are not dropped.

Note:

For example, when operating in dropNTSC mode with ttp:frameRate of 30, a discontinuity in frame count occurs between consecutive frames as shown in the following sequence of time expressions: 01:08:59:28, 01:08:59:29, 01:09:00:02, 01:09:00:03.

If this parameter's value is dropPAL, then, within any given second of a time expression except the second 00, frames count from 0 to N−1, where N is the value specified by the ttp:frameRate parameter, but while ignoring any value specified by the ttp:frameRateMultiplier parameter. If the second of a time expression is 00 and the minute of the time expression is even but not 00, 20, or 40, then frame codes 00 through 03 are dropped during that second; otherwise, these frame codes are not dropped.

Note:

For example, when operating in dropPAL mode with ttp:frameRate of 30, a discontinuity in frame count occurs between consecutive frames as shown in the following sequence of time expressions: 01:09:59:28, 01:09:59:29, 01:10:00:04, 01:10:00:04.

Note:

The dropPAL mode is also known as the M/PAL or PAL (M) drop-frame code, which uses PAL modulation with the NTSC frame rate of ~29.97 frames/second. The M/PAL system is used primarily in Brazil.

If not specified, then nonDrop must be assumed to apply.

A ttp:smpteMode attribute is considered to be significant only when specified on the tt element.

6.2.9 ttp:subFrameRate

The ttp:subFrameRate attribute is used to specify the sub-frame rate of a related media object or the intrinsic sub-frame rate of a document instance in case it is intended to function as an independent media object.

If specified, the value of this attribute must adhere to the following syntax:

Syntax Representation – ttp:subFrameRate
ttp:subFrameRate : <digit>+ // value > 0

The sub-frame rate that applies to a document instance is used to interpret time expressions that are expressed in sub-frames as defined by 10.3.1 <timeExpression>.

A sub-frame is interpreted as a division of a frame of media time, such that if the sub-frame rate is specified as S, then a frame of media time is divided into S intervals of equal duration, where each interval is labeled as sub-frame s, with s ∈ [0…S−1].

If not specified, the sub-frame rate must be considered to be equal to one (1). If specified, then the sub-frame rate must be greater than zero (0).

A ttp:subFrameRate attribute is considered to be significant only when specified on the tt element.

Note:

The sub-frame is sometimes referred to as a field in the context of synchronization with an interlaced video media object.

6.2.10 ttp:tickRate

The ttp:tickRate attribute is used to specify the tick rate of a related media object or the intrinsic tick rate of content of a document instance in case it is intended to function as an independent media object.

If specified, the value of this attribute must adhere to the following syntax:

Syntax Representation – ttp:tickRate
ttp:tickRate : <digit>+ // value > 0

The tick rate that applies to a document instance is used to interpret time expressions that are expressed in ticks by using the t metric as defined by 10.3.1 <timeExpression>.

A tick is interpreted as an integral division of a second of media time, such that if the tick rate is specified as T, then a second of media time is divided into T intervals of equal duration, where each interval is labeled as tick t, with t ∈ [0…T−1].

If not specified, then if a frame rate is specified, the tick rate must be considered to be the effective frame rate multiplied by the sub-frame rate (i.e., ticks are interpreted as sub-frames); or, if no frame rate is specified, the tick rate must be considered to be one (1) tick per second of media time. If specified, then the tick rate must not be zero (0).

Note:

There is no predefined relationship between ticks and frames or sub-frames. Ticks are an arbitrary division of seconds that permit use of fixed point arithmetic rather than fractional (and potentially inexact) expressions of seconds.

A ttp:tickRate attribute is considered to be significant only when specified on the tt element.

6.2.11 ttp:timeBase

The ttp:timeBase attribute is used to specify the temporal coordinate system by means of which time expressions are interpreted in a document instance.

If specified, the value of this attribute must adhere to the following syntax:

Syntax Representation – ttp:timeBase
ttp:timeBase : "media" \| "smpte" \| "clock"

If the time base is designated as media, then a time expression denotes a coordinate in some media object's time line, where the media object may be an external media object with which the content of a document instance is to be synchronized, or it may be the content of a document instance itself in a case where the timed text content is intended to establish an independent time line.

Note:

When using a media time base, if that time base is paused or scaled positively or negatively, then it is expected that the presentation of associated Timed Text content will be similarly paused, accelerated, or decelerated, respectively. The means for controlling an external media time base is outside the scope of this specification.

If the time base is designated as smpte, then a time expression denotes a [SMPTE 12M] time coordinate with which the content of a document instance is to be synchronized. In this case, the value of the ttp:markerMode and ttp:smpteMode parameters apply, as defined by 6.2.5 ttp:markerMode and 6.2.8 ttp:smpteMode, respectively.

If the time base is designated as clock, then the time expression denotes a coordinate in some real-world time line as established by some real-time clock, such as the local wall-clock time or UTC (Coordinated Universal Time) or GPS (Global Positioning System) time lines.

If not specified, the default time base must be considered to be media.

A ttp:timeBase attribute is considered to be significant only when specified on the tt element.

When operating with either media or smpte time bases, a diachronic presentation of a document instance may be subject to transformations of the controlling time line, such as temporal reversal, dilation (expansion), or constriction (compression); however, when operating with the clock time base, no transformations are permitted, and diachronic presentation proceeds on a linear, monotonically increasing time line based on the passage of real time.

Note:

Due to there being only one time base parameter that applies to a given document instance, the interpretation of time expressions is uniform throughout the document instance.

7 Content

This section specifies the content matter of the core vocabulary catalog.

7.1 Content Element Vocabulary

The following elements specify the structure and principal content aspects of a document instance:

7.1.1 tt
7.1.2 head
7.1.3 body
7.1.4 div
7.1.5 p
7.1.6 span
7.1.7 br

7.1.1 tt

The tt element serves as the root, document element of a document instance.

The tt element accepts as its children zero or one head element followed by zero or one body element.

XML Representation – Element Information Item: tt
<tt tts:extent = string xml:id = ID xml:lang = string xml:space = (default\|preserve) : default {any attribute in TT Parameter namespace} {any attribute not in default or any TT namespace}> Content: head?, body? </tt>

XML Representation – Element Information Item: tt

<tt
  tts:extent = string
  xml:id = ID
  xml:lang = string
  xml:space = (default|preserve) : default
  {any attribute in TT Parameter namespace}
  {any attribute not in default or any TT namespace}>
  Content: head?, body?
</tt>

The temporal beginning and ending of a document instance represented by a tt element is defined in relationship with some external application or presentation context. The temporal interval defined by these points is referred to subsequently as the external time interval.

A document instance has an implicit duration that is equal to the implicit duration of the body element of the document, if present, or zero, if not present.

If the tts:extent attribute is specified on the tt element, then it must adhere to 8.2.8 tts:extent, in which case it specifies the spatial extent of the root container region in which content regions are located and presented. If no tts:extent attribute is specified, then the spatial extent of the root container region is considered to be determined by the external authoring or presentation context.

An xml:lang attribute must be specified on the tt element. If the attribute value is empty, it signifies that there is no default language that applies to the text contained within the document instance.

If no xml:space attribute is specified upon the tt element, then it must be considered as if the attribute had been specified with a value of default.

7.1.2 head

The head element is a container element used to group header matter, including metadata, profile, styling, and layout information.

The head element accepts as its children zero or more elements in the Metadata.class element group, followed by zero or more elements in the Parameters.class element group, followed by zero or one styling element, followed by zero or one layout element.

Any metadata specified by children in the Metadata.class element group applies semantically to the document instance as a whole, and not just the head element.

Any parameters specified by children in the Parameters.class element group applies semantically to the document instance as a whole, and not just the head element.

A styling child element is used to specify style constructs that are referenced from other style constructs, by layout constructs, and by content elements.

A layout child element is used to specify layout constructs that are referenced by content elements.

XML Representation – Element Information Item: head
<head xml:id = ID xml:lang = string xml:space = (default\|preserve) {any attribute not in default or any TT namespace}> Content: Metadata.class, Parameters.class, styling?, layout? </head>

To the extent that time semantics apply to the content of the head element, the implied time interval of this element is defined to be coterminous with the external time interval.

7.1.3 body

The body element functions as a logical container and a temporal structuring element for a sequence of textual content units represented as logical divisions.

The body element accepts as its children zero or more elements in the Metadata.class element group, followed by zero or more elements in the Animation.class element group, followed by zero or more div elements.

Any metadata specified by children in the Metadata.class element group applies semantically to the body element and its descendants as a whole.

Any animation elements specified by children in the Animation.class element group apply semantically to the body element.

XML Representation – Element Information Item: body
<body begin = <timeExpression> dur = <timeExpression> end = <timeExpression> region = IDREF style = IDREFS timeContainer = (par\|seq) xml:id = ID xml:lang = string xml:space = (default\|preserve) {any attribute in TT Metadata namespace} {any attribute in TT Style namespace} {any attribute not in default or any TT namespace}> Content: Metadata.class, Animation.class, div* </body>

XML Representation – Element Information Item: body

<body
  begin = <timeExpression>
  dur = <timeExpression>
  end = <timeExpression>
  region = IDREF
  style = IDREFS
  timeContainer = (par|seq)
  xml:id = ID
  xml:lang = string
  xml:space = (default|preserve)
  {any attribute in TT Metadata namespace}
  {any attribute in TT Style namespace}
  {any attribute not in default or any TT namespace}>
  Content: Metadata.class*, Animation.class*, div*
</body>

An author may specify a temporal interval for a body element using the begin, dur, and end attributes. If the begin point of this interval remains unspecified, then the begin point is interpreted as the begin point of the external time interval. Similarly, if the end point of this interval remains unspecified, then the end point is interpreted as the end point of the external time interval.

Note:

A TT AF document instance referenced from a SMIL presentation is expected to follow the same timing rules as apply to other SMIL media objects.

If relative begin or end times are specified on the body element, then these times are resolved by reference to the begin and end time of the external time interval.

If the external time interval is shorter than the computed duration of the body element, then the active time interval of a document instance is truncated to the active end point of the external time interval.

An author may associate a set of style properties with a body element by means of either the style attribute or inline style attributes or a combination thereof.

Note:

Style properties that are associated with a body element in a document instance are available for style inheritance by descendant content elements such as div, p, span and br.

If no timeContainer attribute is specified on a body element, then it must be interpreted as having parallel time containment semantics.

7.1.4 div

The div element functions as a logical container and a temporal structuring element for a sequence of textual content units represented as logical sub-divisions or paragraphs.

Note:

When rendered on a continuous (non-paged) visual presentation medium, a div element is expected to generate one or more block areas that contain zero or more child block areas generated by the div element's descendant p elements.

If some block area generated by a div element does not contain any child areas, then it is not expected to be presented.

The div element accepts as its children zero or more elements in the Metadata.class element group, followed by zero or more elements in the Animation.class element group, followed by zero or more div or p elements.

Any metadata specified by children in the Metadata.class element group applies semantically to the div element and its descendants as a whole.

Any animation elements specified by children in the Animation.class element group apply semantically to the div element.

XML Representation – Element Information Item: div
<div begin = <timeExpression> dur = <timeExpression> end = <timeExpression> region = IDREF style = IDREFS timeContainer = (par\|seq) xml:id = ID xml:lang = string xml:space = (default\|preserve) {any attribute in TT Metadata namespace} {any attribute in TT Style namespace} {any attribute not in default or any TT namespace}> Content: Metadata.class, Animation.class, Block.class* </div>

XML Representation – Element Information Item: div

<div
  begin = <timeExpression>
  dur = <timeExpression>
  end = <timeExpression>
  region = IDREF
  style = IDREFS
  timeContainer = (par|seq)
  xml:id = ID
  xml:lang = string
  xml:space = (default|preserve)
  {any attribute in TT Metadata namespace}
  {any attribute in TT Style namespace}
  {any attribute not in default or any TT namespace}>
  Content: Metadata.class*, Animation.class*, Block.class*
</div>

An author may associate a set of style properties with a div element by means of either the style attribute or inline style attributes or a combination thereof.

Note:

Style properties that are associated with a div element in a document instance are available for style inheritance by descendant content elements such as div, p, span, and br.

If no timeContainer attribute is specified on a div element, then it must be interpreted as having parallel time containment semantics.

7.1.5 p

A p element represents a logical paragraph, serving as a transition between block level and inline level formatting semantics.

The p element accepts as its children zero or more elements in the Metadata.class element group, followed by zero or more elements in the Animation.class element group, followed by zero or more span element, br element, or text nodes interpreted as anonymous spans.

Any metadata specified by children in the Metadata.class element group applies semantically to the p element and its descendants as a whole.

Any animation elements specified by children in the Animation.class element group apply semantically to the p element.

XML Representation – Element Information Item: p
<p begin = <timeExpression> dur = <timeExpression> end = <timeExpression> region = IDREF style = IDREFS timeContainer = (par\|seq) xml:id = ID xml:lang = string xml:space = (default\|preserve) {any attribute in TT Metadata namespace} {any attribute in TT Style namespace} {any attribute not in default or any TT namespace}> Content: Metadata.class, Animation.class, Inline.class* </p>

XML Representation – Element Information Item: p

<p
  begin = <timeExpression>
  dur = <timeExpression>
  end = <timeExpression>
  region = IDREF
  style = IDREFS
  timeContainer = (par|seq)
  xml:id = ID
  xml:lang = string
  xml:space = (default|preserve)
  {any attribute in TT Metadata namespace}
  {any attribute in TT Style namespace}
  {any attribute not in default or any TT namespace}>
  Content: Metadata.class*, Animation.class*, Inline.class*
</p>

An author may associate a set of style properties with a p element by means of either the style attribute or inline style attributes or a combination thereof.

Note:

Style properties that are associated with a p element in a document instance are available for style inheritance by descendant content elements such as span and br.

If no timeContainer attribute is specified on a p element, then it must be interpreted as having parallel time containment semantics.

If a sequence of children of a p element consists solely of character information items, then that sequence must be considered to be an anonymous span for the purpose of applying style properties that apply to span elements.

7.1.6 span

The span element functions as a logical container and a temporal structuring element for a sequence of textual content units having inline level formatting semantics.

When presented on a visual medium, a span element is intended to generate a sequence of inline areas, each containing one or more glyph areas.

The span element accepts as its children zero or more elements in the Metadata.class element group, followed by zero or more elements in the Animation.class element group, followed by zero or more span elements, br elements, or text nodes interpreted as anonymous spans.

Any metadata specified by children in the Metadata.class element group applies semantically to the span element and its descendants as a whole.

Any animation elements specified by children in the Animation.class element group apply semantically to the span element.

XML Representation – Element Information Item: span
<span begin = <timeExpression> dur = <timeExpression> end = <timeExpression> region = IDREF style = IDREFS timeContainer = (par\|seq) xml:id = ID xml:lang = string xml:space = (default\|preserve) {any attribute in TT Metadata namespace} {any attribute in TT Style namespace} {any attribute not in default or any TT namespace}> Content: Metadata.class, Animation.class, Inline.class* </span>

XML Representation – Element Information Item: span

<span
  begin = <timeExpression>
  dur = <timeExpression>
  end = <timeExpression>
  region = IDREF
  style = IDREFS
  timeContainer = (par|seq)
  xml:id = ID
  xml:lang = string
  xml:space = (default|preserve)
  {any attribute in TT Metadata namespace}
  {any attribute in TT Style namespace}
  {any attribute not in default or any TT namespace}>
  Content: Metadata.class*, Animation.class*, Inline.class*
</span>

An author may associate a set of style properties with a span element by means of either the style attribute or inline style attributes or a combination thereof.

Note:

Style properties that are associated with a span element in a document instance are available for style inheritance by descendant content elements such as span and br.

If no timeContainer attribute is specified on a span element, then it must be interpreted as having parallel time containment semantics.

7.1.7 br

The br element denotes an explicit line break.

XML Representation – Element Information Item: br
<br style = IDREFS xml:id = ID xml:lang = string xml:space = (default\|preserve) {any attribute in TT Metadata namespace} {any attribute in TT Style namespace} {any attribute not in default or any TT namespace}> Content: Metadata.class, Animation.class </br>

XML Representation – Element Information Item: br

<br
  style = IDREFS
  xml:id = ID
  xml:lang = string
  xml:space = (default|preserve)
  {any attribute in TT Metadata namespace}
  {any attribute in TT Style namespace}
  {any attribute not in default or any TT namespace}>
  Content: Metadata.class*, Animation.class*
</br>

When presented on a visual medium, the presence of a br element must be interpreted as a forced line break.

Note:

The visual presentation of a br element is intended to produce the same effect as the ASCII control code CR followed by the control code NL when presented on a teletype device. Therefore, two br elements in sequence will produce a different effect than a single br element.

7.2 Content Attribute Vocabulary

This section defines the following common attributes used with many or all element types in the core vocabulary catalog:

7.2.1 xml:id
7.2.2 xml:lang
7.2.3 xml:space

7.2.1 xml:id

The xml:id attribute is used as defined by [XML ID].

The xml:id attribute may be used with any element in the core vocabulary catalog.

7.2.2 xml:lang

The xml:lang attribute is used as defined by [XML 1.0], §2.12, Language Identification.

The xml:lang attribute must be specified on the tt element and may be specified by an instance of any other element type in the core vocabulary catalog.

7.2.3 xml:space

The xml:space attribute is used as defined by [XML 1.0], §2.10, White Space Handling.

The xml:space attribute may be used with any element in the core vocabulary catalog.

The semantics of the value default are fixed to mean that when performing presentation processing of a document instance as described by 9.3.3 Synchronic Flow Processing, processing must occur as if the following properties were specified on the affected elements of the intermediate XSL-FO document:

suppress-at-line-break="auto"
linefeed-treatment="treat-as-space"
white-space-collapse="true"
white-space-treatment="ignore-if-surrounding-linefeed"

Similarly, the semantics of the value preserve are fixed to mean that when performing presentation processing, processing must occur as if the following properties were specified on the affected elements of the intermediate XSL-FO document:

suppress-at-line-break="retain"
linefeed-treatment="preserve"
white-space-collapse="false"
white-space-treatment="preserve"

When performing other types of processing intended to eventually result in a visual presentation by means other than those described in this specification, the semantics of space collapsing and preservation as described above should be respected. For other types of processing, the treatment of the xml:space attribute is processor dependent, but should respect the semantics described above if possible.

8 Styling

This section specifies the styling matter of the core vocabulary catalog, where styling is to be understood as a separable layer of information that applies to content and that denotes authorial intentions about the presentation of that content.

No normative use of an <?xml-stylesheet ... ?> processing instruction is defined by this specification.

8.1 Styling Element Vocabulary

The following elements specify the structure and principal styling aspects of a document instance:

8.1.1 styling
8.1.2 style

8.1.1 styling

The styling element is a container element used to group styling matter, including metadata that applies to styling matter.

The styling element accepts as its children zero or more elements in the Metadata.class element group, followed by zero or more style elements.

XML Representation – Element Information Item: styling
<styling xml:id = ID xml:lang = string xml:space = (default\|preserve) {any attribute not in default or any TT namespace}> Content: Metadata.class, style </styling>

To the extent that time semantics apply to the content of the styling element, the implied time interval of this element is defined to be coterminous with the external time interval.

8.1.2 style

The style element is used to define a set of style specifications expressed as a specified style set in accordance with 8.4.4.2 Specified Style Set Processing.

The style element accepts as its children zero or more metadata elements.

XML Representation – Element Information Item: style

<style
  style = IDREFS
  xml:id = ID
  xml:lang = string
  xml:space = (default|preserve)
  {any attribute in TT Style namespace}
  {any attribute not in default or any TT namespace}>
  Content: Metadata.class*
</style>

If a style element appears as a descendant of a region element, then the style element must be ignored for the purpose of computing referential styles as defined by 8.4.1.2 Referential Styling and 8.4.1.3 Chained Referential Styling.

Note:

That is to say, when referential styling is used by an element to refer to a style element, then the referenced style element must appear as a descendant of the styling element, and not in any other context.

8.2 Styling Attribute Vocabulary

This section defines the 8.2.1 style attribute used with both style definition elements as well as content elements.

In addition, this section specifies the following attributes in the TT Style Namespace for use with style definition elements, certain layout elements, and content elements that support inline style specifications:

8.2.2 tts:backgroundColor
8.2.3 tts:color
8.2.4 tts:direction
8.2.5 tts:display
8.2.6 tts:displayAlign
8.2.7 tts:dynamicFlow
8.2.8 tts:extent
8.2.9 tts:fontFamily
8.2.10 tts:fontSize
8.2.11 tts:fontStyle
8.2.12 tts:fontWeight
8.2.13 tts:lineHeight
8.2.14 tts:opacity
8.2.15 tts:origin
8.2.16 tts:overflow
8.2.17 tts:padding
8.2.18 tts:showBackground
8.2.19 tts:textAlign
8.2.20 tts:textDecoration
8.2.21 tts:textOutline
8.2.22 tts:unicodeBidi
8.2.23 tts:visibility
8.2.24 tts:wrapOption
8.2.25 tts:writingMode
8.2.26 tts:zIndex

Unless explicitly stated otherwise, linear white-space (LWSP) may appear between tokens of a value of a TT Style or TT Style Extension Property.

Note:

This specification makes use of lowerCamelCased local names for style attributes that are based upon like-named properties defined by [XSL 1.1]. This convention is likewise extended to token values of such properties.

Note:

A style property may be expressed as a specified attribute on any content element type independently of whether the property applies to that element type. This capability permits the expression of an inheritable style property on ancestor elements to which the property property does not apply.

8.2.1 style

The style attribute is used by referential style association to reference one or more style elements each of which define a specified style set.

The style attribute may be specified by an instance of the following element types:

body
div
p
region
span
style

Note:

See the specific element type definitions that permit use of the style attribute, as well as 8.4.1.2 Referential Styling and 8.4.1.3 Chained Referential Styling, for further information on its semantics.

8.2.2 tts:backgroundColor

The tts:backgroundColor attribute is used to specify a style property that defines the background color of a region or an area generated by content flowed into a region.

This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however, this attribute applies as a style property only to those element types indicated in the following table.

Values:	<color>
Initial:	`transparent`
Applies to:	`body`, `div`, `p`, `region`, `span`
Inherited:	no
Percentages:	N/A
Animatable:	discrete

For the purpose of determining applicability of this style property, each character child of a p element is considered to be enclosed in an anonymous span.

The tts:backgroundColor style is illustrated by the following example.

Example Fragment – Background Color

<region xml:id="r1">
  <style tts:extent="306px 114px"/>
  <style tts:backgroundColor="red"/>
  <style tts:color="white"/>
  <style tts:displayAlign="after"/>
  <style tts:padding="3px 40px"/>
</region>
...
<p region="r1" tts:backgroundColor="purple" tts:textAlign="center">
  Twinkle, twinkle, little bat!<br/>
  How <span tts:backgroundColor="green">I wonder</span> where you're at!
</p>

Example Rendition – Background Color

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.7.2.

8.2.3 tts:color

The tts:color attribute is used to specify a style property that defines the foreground color of marks associated with an area generated by content flowed into a region.

Values:	<color>
Initial:	see prose
Applies to:	`span`
Inherited:	yes
Percentages:	N/A
Animatable:	discrete

For the purpose of determining applicability of this style property, each character child of a p element is considered to be enclosed in an anonymous span.

The initial value of the tts:color property is considered to be implementation dependent. In the absence of end-user preference information, a conformant presentation processor should use an initial value that is highly contrastive to the background color of the root container region.

The tts:color style is illustrated by the following example.

Example Fragment – Color

<region xml:id="r1">
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="after"/>
  <style tts:textAlign="center"/>
</region>
...
<p region="r1">
  In spring, when woods are <span tts:color="green">getting green</span>,<br/>
  I'll try and tell you what I mean.
</p>

Example Rendition – Color

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.17.1.

8.2.4 tts:direction

The tts:direction attribute is used to specify a style property that defines the directionality of an embedding or override according to the Unicode bidirectional algorithm.

Values:	`ltr` \| `rtl`
Initial:	`ltr`
Applies to:	`p`, `span`
Inherited:	yes
Percentages:	N/A
Animatable:	discrete

For the purpose of determining applicability of this style property, each character child of a p element is considered to be enclosed in an anonymous span.

If a specified value of this attribute is not supported, then a presentation processor must ignore the attribute.

The tts:direction style is illustrated by the following example.

Example Fragment – Direction

<region xml:id="r1">
  <style tts:extent="265px 84px"/>
  <style tts:padding="5px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="after"/>
  <style tts:textAlign="center"/>
</region>
...
<p region="r1">
  Little birds are playing<br/>
  Bagpipes on the shore,<br/>
  <span tts:unicodeBidi="bidiOverride" tts:direction="rtl">where the tourists snore.</span>
</p>

Example Rendition – Direction

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.27.1.

8.2.5 tts:display

The tts:display attribute is used to specify a style property that defines whether an element is a candidate for layout and composition in a region.

Values:	`auto` \| `none`
Initial:	`auto`
Applies to:	`body`, `div`, `p`, `region`, `span`
Inherited:	no
Percentages:	N/A
Animatable:	discrete

For the purpose of determining applicability of this style property, each character child of a p element is considered to be enclosed in an anonymous span.

If the value of this attribute is auto, then the affected element is a candidate for region layout and presentation; however, if the value is none, then the affected element and its descendants must be considered ineligible for region layout and presentation.

The tts:display style is illustrated by the following example.

Example Fragment – Display

<region xml:id="r1">
  <style tts:extent="369px 119px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="before"/>
  <style tts:textAlign="start"/>
</region>
...
<div region="r1">
  <p dur="5s">
    [[[
    <span tts:display="none">
      <set begin="1s" dur="1s" tts:display="auto"/>
      Beautiful soup,
    </span>
    <span tts:display="none">
      <set begin="2s" dur="1s" tts:display="auto"/>
      so rich and green,
    </span>
    <span tts:display="none">
      <set begin="3s" dur="1s" tts:display="auto"/>
      waiting in a hot tureen!
    </span>
    ]]]
  </p>
</div>

Example Rendition – Display

Note:

The semantics of the style property represented by this attribute are based upon that defined by [CSS2], § 9.2.5.

8.2.6 tts:displayAlign

The tts:displayAlign attribute is used to specify a style property that defines the alignment of block areas in the block progression direction.

Values:	`before` \| `center` \| `after`
Initial:	`before`
Applies to:	`region`
Inherited:	yes
Percentages:	N/A
Animatable:	discrete

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value before were specified.

The tts:displayAlign style is illustrated by the following example.

Example Fragment – Display Align

<region xml:id="r1">
  <style tts:extent="128px 66px"/>
  <style tts:origin="0px 0px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="before"/>
  <style tts:textAlign="start"/>
</region>
<region xml:id="r2">
  <style tts:extent="192px 66px"/>
  <style tts:origin="128px 66px"/>
  <style tts:backgroundColor="green"/>
  <style tts:color="white"/>
  <style tts:displayAlign="after"/>
  <style tts:textAlign="start"/>
</region>
<region xml:id="r3">
  <style tts:extent="128px 66px"/>
  <style tts:origin="0px 132px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="before"/>
  <style tts:textAlign="start"/>
</region>
<region xml:id="r4">
  <style tts:extent="192px 66px"/>
  <style tts:origin="128px 198px"/>
  <style tts:backgroundColor="green"/>
  <style tts:color="white"/>
  <style tts:displayAlign="after"/>
  <style tts:textAlign="start"/>
</region>
...
<div>
  <p region="r1">I sent a message to the fish:</p>
  <p region="r2">I told them<br/> "This is what I wish."</p>
  <p region="r3">The little fishes of the sea,</p>
  <p region="r4">They sent an<br/> answer back to me.</p>
</div>

Example Rendition – Display Align

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.13.4.

8.2.7 tts:dynamicFlow

The tts:dynamicFlow attribute is used to specify a style property that defines how to dynamically flow content into and out of a region over some time interval.

This style property applies only to a region when the tts:overflow property for that region has the value dynamic.

Values:	`none` \| `rollUp` \| <flowFunction>+ <flowIntervalFunction>*
Initial:	`none`
Applies to:	`region`
Inherited:	no
Percentages:	N/A
Animatable:	discrete

If the value of this attribute is none, then no dynamic flow semantics apply.

If the value of this attribute is rollUp, then this value is interpreted as a shorthand value equivalent to out(line,smooth) clear(0.433s).

Note:

The choice of a definite duration of 0.433 seconds for the clear interval for roll up dynamic flow timing is based upon recommendations specified in [CC-DECODER-REQ], p. 792.

If the value of this attribute contains a single <flowFunction>, then that flow function applies equally to fill into and clear from dynamic flow operations.

If either fill() or clear() <flowIntervalFunction> is not specified, then the auto value for the missing <flowIntervalFunction> applies. Multiple instances of the same <flowIntervalFunction> must not appear in the value of this attribute.

The normative processing model for dynamic flow behavior is specified in B Dynamic Flow Processing Model.

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value none were specified.

The tts:dynamicFlow style is illustrated by the following example, and depicted in an SVG Animation.

Example Fragment – Dynamic Flow

<region xml:id="r1">
  <style tts:extent="140px 70px"/>
  <style tts:displayAlign="after"/>
  <style tts:backgroundColor="transparent"/>
  <style tts:fontFamily="proportionalSansSerif"/>
  <style tts:fontSize="18px"/>
  <style tts:overflow="dynamic"/>
  <style tts:dynamicFlow="in(word,jump) fill(1.0s) out(line,smooth) clear(0.3s)"/>
</region>
...
<p region="r1">
  <span tts:backgroundColor="black" tts:color="white">
    Five o'clock tea!<br/>
    Ever to thee,<br/>
    Faithful I'll be,<br/>
    Five o'clock tea!<br/>
    <br/>
    <br/>
    <br/>
  </span>
</p>

Example Rendition – Dynamic Flow – Discrete Frames

8.2.8 tts:extent

The tts:extent attribute is used to specify the width and height of a region area (which may be the root container region).

Values:	`auto` \| <length> <length>
Initial:	`auto`
Applies to:	`tt`, `region`
Inherited:	no
Percentages:	relative to width and height of root container region
Animatable:	discrete

If the value of this attribute consists of two <length> specifications, then they must be interpreted as width and height, where the first specification is the width, and the second specification is the height.

If the value of this attribute is auto, then the initial value of the style property must be considered to be the same as the root container extent.

The root container extent is determined either by a tts:extent specified on the tt element, if present, or by the external authoring context, if not present. If tts:extent is specified on the tt element, then the width and height must be expressed in terms of two <length> specifications, and these specifications must be expressed as non-percentage, definite lengths using pixel units.

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value auto were specified.

The tts:extent style is illustrated by the following example.

Example Fragment – Extent

<region xml:id="r1">
  <style tts:extent="330px 122px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="after"/>
  <style tts:textAlign="center"/>
</region>
...
<p region="r1">
  'Tis the voice of the Lobster:<br/>
  I heard him declare,<br/>
  "You have baked me too brown,<br/>
  I must sugar my hair."
</p>

Example Rendition – Extent

8.2.9 tts:fontFamily

The tts:fontFamily attribute is used to specify a style property that defines the font family from which glyphs are selected for glyph areas generated by content flowed into a region.

Values:	(<familyName> \| <genericFamilyName>) (`","` (<familyName> \| <genericFamilyName>))*
Initial:	`default`
Applies to:	`span`
Inherited:	yes
Percentages:	N/A
Animatable:	discrete

Note:

The initial value, default, is a generic font family name, and is further described in 8.3.8 <genericFamilyName> below.

For the purpose of determining applicability of this style property, each character child of a p element is considered to be enclosed in an anonymous span.

If a specified font family is not available, then a presentation processor must attempt to map the specified font family to an available font family that has similar typographic characteristics, or, in the absence of such a mapping, it must interpret the font family as if the value default were specified.

The tts:fontFamily style is illustrated by the following example.

Example Fragment – Font Family

<region xml:id="r1">
  <style tts:extent="474px 146px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="center"/>
  <style tts:textAlign="start"/>
  <style tts:fontFamily="proportionalSansSerif"/>
</region>
...
<div region="r1">
  <p>
    "The time has come," the Walrus said,<br/>
    "to talk of many things:
  </p>
  <p tts:textAlign="end" tts:fontFamily="monospaceSerif">
    Of shoes, and ships, and sealing wax,<br/>
    Of cabbages and kings,
  </p>
  <p>
    And why the sea is boiling hot,<br/>
    and whether pigs have wings."
  </p>
</div>

Example Rendition – Font Family

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.8.2.

8.2.10 tts:fontSize

The tts:fontSize attribute is used to specify a style property that defines the font size for glyphs that are selected for glyph areas generated by content flowed into a region, where font size is interpreted as a scaling transform to the font's design EM square.

Values:	<length> <length>?
Initial:	`1c`
Applies to:	`span`
Inherited:	yes
Percentages:	relative to parent element's font size
Animatable:	discrete

If a single <length> value is specified, then this length applies equally to horizontal and vertical scaling of a glyph's EM square; if two <length> values are specified, then the first expresses the horizontal scaling and the second expresses vertical scaling.

Note:

Use of independent horizontal and vertical font sizes is expected to be used with cell based metrics in order to denote fonts that are two rows in height and one column in width.

If horizontal and vertical sizes are expressed independently, then the metrics of the <length> values must be the same.

The <length> value(s) used to express font size must be non-negative.

For the purpose of determining applicability of this style property, each character child of a p element is considered to be enclosed in an anonymous span.

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value 1c were specified.

The tts:fontSize style is illustrated by the following example.

Example Fragment – Font Size

<region xml:id="r1">
  <style tts:extent="299px 97px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="center"/>
  <style tts:textAlign="center"/>
  <style tts:fontFamily="proportionalSansSerif"/>
  <style tts:fontSize="18px"/>
</region>
...
<p region="r1">
  Then fill up the glasses<br/>
  with treacle and ink,<br/>
  Or anything else<br/>
  that is <span tts:fontSize="24px">pleasant</span> to drink.
</p>

Example Rendition – Font Size

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.8.4.

8.2.11 tts:fontStyle

The tts:fontStyle attribute is used to specify a style property that defines the font style to apply to glyphs that are selected for glyph areas generated by content flowed into a region, where the mapping from font style value to specific font face or style parameterization is not determined by this specification.

Values:	`normal` \| `italic` \| `oblique` \| `reverseOblique`
Initial:	`normal`
Applies to:	`span`
Inherited:	yes
Percentages:	N/A
Animatable:	discrete

For the purpose of determining applicability of this style property, each character child of a p element is considered to be enclosed in an anonymous span.

Use of values oblique and reverseOblique denote a shear and reverse shear transformation (at an unspecified angle) in the inline progression dimension.

If a specified font style is not available, then a presentation processor must attempt to map the specified font style to an available font style that has similar typographic characteristics, or, in the absence of such a mapping, it must interpret the font style as if the value normal were specified.

The tts:fontStyle style is illustrated by the following example.

Example Fragment – Font Style

<region xml:id="r1">
  <style tts:extent="331px 84px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="after"/>
  <style tts:textAlign="center"/>
  <style tts:fontFamily="proportionalSansSerif"/>
</region>
...
<p region="r1">
  In autumn, when the leaves are brown,<br/>
  Take pen and ink, and <span tts:fontStyle="italic">write it down.</span>
</p>

Example Rendition – Font Style

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.8.7.

8.2.12 tts:fontWeight

The tts:fontWeight attribute is used to specify a style property that defines the font weight to apply to glyphs that are selected for glyph areas generated by content flowed into a region, where the mapping from font weight value to specific font face or weight parameterization is not determined by this specification.

Values:	`normal` \| `bold`
Initial:	`normal`
Applies to:	`span`
Inherited:	yes
Percentages:	N/A
Animatable:	discrete

For the purpose of determining applicability of this style property, each character child of a p element is considered to be enclosed in an anonymous span.

If a specified font weight is not available, then a presentation processor must attempt to map the specified font weight to an available font weight that has similar typographic characteristics, or, in the absence of such a mapping, it must interpret the font weight as if the value normal were specified.

The tts:fontWeight style is illustrated by the following example.

Example Fragment – Font Weight

<region xml:id="r1">
  <style tts:extent="376px 95px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="center"/>
  <style tts:textAlign="center"/>
  <style tts:fontFamily="proportionalSansSerif"/>
</region>
...
<p region="r1">
  They told me you had been to her,<br/>
  <span tts:fontWeight="bold">and mentioned me to him:</span><br/>
  She gave me a good character<br/>
  <span tts:fontWeight="bold">but said I could not swim.</span>
</p>

Example Rendition – Font Weight

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.8.9.

8.2.13 tts:lineHeight

The tts:lineHeight attribute is used to specify a style property that defines the inter-baseline separation between line areas generated by content flowed into a region.

Values:	`normal` \| <length>
Initial:	`normal`
Applies to:	`p`
Inherited:	yes
Percentages:	relative to this element's font size
Animatable:	discrete

If the value of this attribute is normal, then the initial value of the style property must be considered to be the same as the largest font size that applies to any descendant element.

If specified as a <length>, then the length must be non-negative.

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value normal were specified.

The tts:lineHeight style is illustrated by the following example.

Example Fragment – Line Height

<region xml:id="r1">
  <style tts:extent="255px 190px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="center"/>
  <style tts:textAlign="start"/>
  <style tts:fontFamily="proportionalSansSerif"/>
  <style tts:fontSize="16px"/>
  <style tts:lineHeight="32px"/>
</region>
...
<p region="r1">
  He thought he saw an elephant,<br/>
  That practised on a fife:<br/>
  He looked again, and found it was<br/>
  A letter from his wife.<br/>
  "At length I realise," he said,<br/>
  "The bitterness of Life.
"</p>

Example Rendition – Line Height

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.15.4.

8.2.14 tts:opacity

The tts:opacity attribute is used to specify a style property that defines the opacity (or transparency) of marks associated with a region.

When presented onto a visual medium, the opacity of the region is applied uniformly and on a linear scale to all marks produced by content targeted to the region.

Values:	<alpha>
Initial:	`1.0`
Applies to:	`region`
Inherited:	no
Percentages:	N/A
Animatable:	discrete

An <alpha> value greater than 1.0 must be considered equivalent to an <alpha> value of 1.0.

The tts:opacity style is illustrated by the following example.

Example Fragment – Opacity

<region xml:id="r1" dur="5s">
  <set begin="0s" dur="1s" tts:opacity="1.00"/>
  <set begin="1s" dur="1s" tts:opacity="0.75"/>
  <set begin="2s" dur="1s" tts:opacity="0.50"/>
  <set begin="3s" dur="1s" tts:opacity="0.25"/>
  <set begin="4s" dur="1s" tts:opacity="0.00"/>
  <style tts:extent="304px 77px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="after"/>
  <style tts:textAlign="center"/>
</region>
...
<p region="r1">
  The sun was shining on the sea
</p>

Example Rendition – Opacity

Note:

The semantics of the style property represented by this attribute are based upon that defined by [CSS3 Color], § 3.2.

8.2.15 tts:origin

The tts:origin attribute is used to specify the x and y coordinates of the origin of a region area with respect to the origin of the root container extent, if specified, or the external authoring context, if not specified.

Values:	`auto` \| <length> <length>
Initial:	`auto`
Applies to:	`region`
Inherited:	no
Percentages:	relative to width and height of root container region
Animatable:	discrete

If the value of this attribute consists of two <length> specifications, then they must be interpreted as x and y coordinates, where the first specification is the x coordinate, and the second specification is the y coordinate.

If the value of this attribute is auto, then the initial value of the style property must be considered to be the same as the root container origin. The root container origin is determined by the external authoring context.

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value auto were specified.

The tts:origin style is illustrated by the following example.

Example Fragment – Origin

<region xml:id="r1">
  <style tts:origin="40px 40px"/>
  <style tts:extent="308px 92px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="center"/>
  <style tts:textAlign="center"/>
</region>
...
<p region="r1">
  "To dine!" she shrieked in dragon-wrath.<br/>
  "To swallow wines all foam and froth!<br/>
   To simper at a table-cloth!"
</p>

Example Rendition – Origin

8.2.16 tts:overflow

The tts:overflow attribute is used to specify a style property that defines whether a region area is clipped or not if the descendant areas of the region overflow its extent.

Values:	`visible` \| `hidden` \| `dynamic`
Initial:	`hidden`
Applies to:	`region`
Inherited:	no
Percentages:	N/A
Animatable:	discrete

If the value of this attribute is visible, then content should not be clipped outside of the affected region, and region composition and layout must be performed as if the region's width and height were unconstrained, but with a well-defined origin. If the value is hidden or dynamic, then content should be clipped outside of the affected region.

Note:

Unless a manual line break element br is used by the content author, a paragraph of a given region will generate no more than one line area in that region if the value of the tts:overflow style that applies to the region is visible and if the applicable tts:wrapOption style is noWrap.

If the value of this attribute is dynamic, then content is dynamically flowed into and out of the affected region according to the values of the tts:dynamicFlow style property; in this case, the semantics of the tts:dynamicFlow apply whether or not the affected region has overflowed.

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value hidden were specified.

The tts:overflow style is illustrated by the following example.

Example Fragment – Overflow

<region xml:id="r1">
  <style tts:extent="232px 40px"/>
  <style tts:origin="0px 0px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="red"/>
  <style tts:displayAlign="before"/>
  <style tts:textAlign="start"/>
  <style tts:fontFamily="proportionalSansSerif"/>
  <style tts:fontSize="18px"/>
  <style tts:wrapOption="noWrap"/>
  <style tts:overflow="visible"/>
</region>
<region xml:id="r2">
  <style tts:extent="232px 40px"/>
  <style tts:origin="0px 43px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="red"/>
  <style tts:displayAlign="before"/>
  <style tts:textAlign="start"/>
  <style tts:fontFamily="proportionalSansSerif"/>
  <style tts:fontSize="18px"/>
  <style tts:wrapOption="noWrap"/>
  <style tts:overflow="hidden"/>
</region>
...
<p region="r1">
  "But wait a bit," the Oysters cried,<br/>
  "Before we have our chat;
</p>
<p region="r2">
  For some of us are out of breath,<br/>
  And all of us are fat!"
</p>

Example Rendition – Overflow

Note:

In the above example, the tts:noWrap is set to noWrap to prevent automatic line wrapping (breaking); if this were not specified, then overflow would occur in the block progression direction as opposed to the inline progression direction.

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.20.2.

8.2.17 tts:padding

The tts:padding attribute is used to specify padding (or inset) space on all sides of a region area.

Values:	<length> \| <length> <length> \| <length> <length> <length> \| <length> <length> <length> <length>
Initial:	`0px`
Applies to:	`region`
Inherited:	no
Percentages:	relative to width and height of region
Animatable:	discrete

If the value of this attribute consists of one <length> specification, then that length applies to all edges of the affected areas. If the value consists of two <length> specifications, then the first applies to the before and after edges, and the second applies to the start and end edges. If three <length> specifications are provided, then the first applies to the before edge, the second applies to the start and end edges, and the third applies to the after edge. If four <length> specifications are provided, then they apply to before, end, after, and start edges, respectively.

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value 0px were specified.

The tts:padding style is illustrated by the following example.

Example Fragment – Padding

<region xml:id="r1">
  <style tts:extent="446px 104px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="after"/>
  <style tts:textAlign="center"/>
  <style tts:padding="10px 40px"/>
</region>
...
<p region="r1" tts:backgroundColor="red">
  Just the place for a Snark! I have said it twice:<br/>
  That alone should encourage the crew.<br/>
  Just the place for a Snark! I have said it thrice:<br/>
  What I tell you three times is true.
</p>

When rendering an area to which padding applies, the background color that applies to the area is rendered into the padded portion of the area.

Example Rendition – Padding

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.29.15, except that individual shorthand values map to writing mode relative padding values as defined by [XSL 1.1], § 7.7.31, 7.7.32, 7.7.33, and 7.7.34.

8.2.18 tts:showBackground

The tts:showBackground attribute is used to specify constraints on when the background color of a region is intended to be presented.

Values:	`always` \| `whenActive`
Initial:	`always`
Applies to:	`region`
Inherited:	no
Percentages:	N/A
Animatable:	discrete

If the value of this attribute is always, then the background color of a region is always rendered when performing presentation processing on a visual medium; if the value is whenActive, then the background color of a region is rendered only when some content is selected into the region.

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value always were specified.

The tts:showBackground style is illustrated by the following example.

Example Fragment – Show Background

<region xml:id="r1">
  <style tts:origin="0px 0px"/>
  <style tts:extent="265px 100px"/>
  <style tts:backgroundColor="black"/>
  <style tts:showBackground="always"/>
  <style tts:color="white"/>
  <style tts:displayAlign="before"/>
  <style tts:textAlign="start"/>
</region>
<region xml:id="r2">
  <style tts:origin="205px 60px"/>
  <style tts:extent="290px 100px"/>
  <style tts:backgroundColor="red"/>
  <style tts:color="white"/>
  <style tts:displayAlign="before"/>
  <style tts:textAlign="end"/>
  <style tts:showBackground="whenActive"/>
</region>

Note:

The semantics of the style property represented by this attribute are based upon that defined by [SMIL 2.1], § 5.3.1.

8.2.19 tts:textAlign

The tts:textAlign attribute is used to specify a style property that defines how inline areas are aligned within a containing block area in the inline progression direction.

Values:	`left` \| `center` \| `right` \| `start` \| `end`
Initial:	`start`
Applies to:	`p`
Inherited:	yes
Percentages:	N/A
Animatable:	discrete

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value start were specified.

The tts:textAlign style is illustrated by the following example.

Example Fragment – Text Align

<region xml:id="r1">
  <style tts:extent="355px 43px"/>
  <style tts:origin="0px 0px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:textAlign="start"/>
</region>
<region xml:id="r2">
  <style tts:extent="355px 43px"/>
  <style tts:origin="0px 47px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:textAlign="end"/>
</region>
...
<p region="r1">
  Beware the Jabberwock, my son!<br/>
  The jaws that bite, the claws that catch!
</p>
<p region="r2">
  Beware the Jubjub bird, and shun<br/>
  The frumious Bandersnatch!
</p>

Example Rendition – Text Align

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.15.9.

8.2.20 tts:textDecoration

The tts:textDecoration attribute is used to specify a style property that defines a text decoration effect to apply to glyph areas or other inline areas that are generated by content flowed into a region.

Values:	`none` \| [ [ `underline` \| `noUnderline` ] \|\| [ `lineThrough` \| `noLineThrough` ] \|\| [ `overline` \| `noOverline` ] ]
Initial:	`none`
Applies to:	`span`
Inherited:	yes
Percentages:	N/A
Animatable:	discrete

For the purpose of determining applicability of this style property, each character child of a p element is considered to be enclosed in an anonymous span.

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value none were specified.

The tts:textDecoration style is illustrated by the following example.

Example Fragment – Text Decoration

<region xml:id="r1">
  <style tts:extent="385px 82px"/>
  <style tts:origin="0px 0px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:padding="5px 2px"/>
  <style tts:textDecoration="underline"/>
</region>
...
<p region="r1">
  The sea was wet<span tts:textDecoration="noUnderline"> as </span>wet
  <span tts:textDecoration="noUnderline">
    could be,<br/>
    The sand was dry as dry.<br/>
    <span tts:textDecoration="lineThrough">There weren't any</span>
    You <span tts:textDecoration="lineThrough">couldn't</span>
    could not see a cloud<br/>
    Because no cloud was in the sky.
  </span>
</p>

Example Rendition – Text Decoration

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.16.4.

8.2.21 tts:textOutline

The tts:textOutline attribute is used to specify a style property that defines a text outline effect to apply to glyphs that are selected for glyph areas generated by content flowed into a region.

Values:	`none` \| <color>? <length> <length>?
Initial:	`none`
Applies to:	`span`
Inherited:	yes
Percentages:	relative to this element's font size
Animatable:	discrete

For the purpose of determining applicability of this style property, each character child of a p element is considered to be enclosed in an anonymous span.

The value of this attribute consists of an optional <color> term followed by one or two <length> terms. If a color term is present, then it denotes the outline color; if no color term is present, the computed value of the tts:color applies. The first length term denotes the outline thickness and the second length term, if present, indicates the blur radius.

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value none were specified.

The tts:textOutline style is illustrated by the following example.

Example Fragment – Text Outline

<region xml:id="r1">
  <style tts:backgroundColor="transparent"/>
  <style tts:color="yellow"/>
  <style tts:textOutline="black 2px 0px"/>
  <style tts:fontFamily="proportionalSansSerif"/>
  <style tts:fontSize="24px"/>
</region>
...
<p>
  How doth the little crocodile<br/>
  Improve its shining tail,<br/>
  And pour the waters of the Nile<br/>
  On every golden scale!<br/>
  How cheerfully he seems to grin,<br/>
  How neatly spreads his claws,<br/>
  And welcomes little fishes in,<br/>
  With gently smiling jaws!
</p>

Example Rendition – Text Outline

8.2.22 tts:unicodeBidi

The tts:unicodeBidi attribute is used to specify a style property that defines a directional embedding or override according to the Unicode bidirectional algorithm.

Values:	`normal` \| `embed` \| `bidiOverride`
Initial:	`normal`
Applies to:	`p`, `span`
Inherited:	no
Percentages:	N/A
Animatable:	discrete

For the purpose of determining applicability of this style property, each character child of a p element is considered to be enclosed in an anonymous span.

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value normal were specified.

The tts:unicodeBidi style is illustrated by the following example.

Example Fragment – Unicode Bidirectionality

<region xml:id="r1">
  <style tts:extent="265px 84px"/>
  <style tts:padding="5px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="after"/>
  <style tts:textAlign="center"/>
</region>
...
<p region="r1">
  Little birds are playing<br/>
  Bagpipes on the shore,<br/>
  <span tts:unicodeBidi="bidiOverride" tts:direction="rtl">where the tourists snore.</span>
</p>

Example Rendition – Unicode Bidirectionality

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.27.6.

8.2.23 tts:visibility

The tts:visibility attribute is used to specify a style property that defines whether generated areas are visible or not when rendered on a visual presentation medium.

Values:	`visible` \| `hidden`
Initial:	`visible`
Applies to:	`body`, `div`, `p`, `region`, `span`
Inherited:	yes
Percentages:	N/A
Animatable:	discrete

For the purpose of determining applicability of this style property, each character child of a p element is considered to be enclosed in an anonymous span.

The tts:visibility style has no affect on content layout or composition, but merely determines whether composed content is visible or not.

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value visible were specified.

The tts:visibility style is illustrated by the following example.

Example Fragment – Visibility

<region xml:id="r1">
  <style tts:extent="398px 121px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style/>
</region>
...
<p region="r1" dur="4s">
  <span tts:visibility="hidden">
    <set begin="1s" tts:visibility="visible"/>
    Curiouser
  </span>
  <span tts:visibility="hidden">
    <set begin="2s" tts:visibility="visible"/>
    and
  </span>
  <span tts:visibility="hidden">
    <set begin="3s" tts:visibility="visible"/>
    curiouser!
  </span>
</p>

Example Rendition – Visibility

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.28.8.

8.2.24 tts:wrapOption

The tts:wrapOption attribute is used to specify a style property that defines whether or not automatic line wrapping (breaking) applies within the context of the affected element.

Values:	`wrap` \| `noWrap`
Initial:	`wrap`
Applies to:	`span`
Inherited:	yes
Percentages:	N/A
Animatable:	discrete

For the purpose of determining applicability of this style property, each character child of a p element is considered to be enclosed in an anonymous span.

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value wrap were specified.

The tts:wrapOption style is illustrated by the following example.

Example Fragment – Wrap Option

<region xml:id="r1">
  <style tts:extent="192px 117px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:displayAlign="after"/>
  <style tts:overflow="hidden"/>
  <style tts:wrapOption="noWrap"/>
</region>
...
<p>
  I'll tell thee everything I can:<br/>
  There's little to relate.<br/>
  I saw an aged aged man,<br/>
  A-sitting on a gate.
</p>

Example Rendition – Wrap Option

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.15.13.

8.2.25 tts:writingMode

The tts:writingMode attribute is used to specify a style property that defines the block and inline progression directions to be used for the purpose of stacking block and inline areas within a region area.

Values:	`lrtb` \| `rltb` \| `tbrl` \| `tblr` \| `lr` \| `rl` \| `tb`
Initial:	`lrtb`
Applies to:	`region`
Inherited:	no
Percentages:	N/A
Animatable:	discrete

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value lrtb were specified.

The tts:writingMode style is illustrated by the following example.

Example Fragment – Writing Mode

<region xml:id="r1">
  <style tts:extent="50px 570px"/>
  <style tts:origin="0px 0px"/>
  <style tts:padding="10px 3px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:writingMode="tbrl"/>
</region>
<region xml:id="r2">
  <style tts:extent="310px 50px"/>
  <style tts:origin="70px 120px"/>
  <style tts:padding="10px 3px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:writingMode="rltb"/>
</region>
...
<p region="r1">
  I sometimes dig for buttered rolls,<br/>
  Or set limed twigs for crabs:
</p>
<p region="r2" tts:direction="rtl" tts:unicodeBidi="bidiOverride">
  I sometimes search the grassy knolls for the wheels of Hansom-cabs.
</p>

Example Rendition – Writing Mode

Note:

In the second paragraph in the above example that targets region r2, the tts:unicodeBidi and tts:direction properties are set to bidiOverride and rtl, respectively, in order to override the normally left-to-right directionality of characters in the Latin script.

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.27.7.

8.2.26 tts:zIndex

The tts:zIndex attribute is used to specify a style property that defines the front-to-back ordering of region areas in the case that they overlap.

Values:	`auto` \| <integer>
Initial:	`auto`
Applies to:	`region`
Inherited:	no
Percentages:	N/A
Animatable:	discrete

If two areas are associated with the same Z-index value, then, if those areas overlap in space, the area(s) generated by lexically subsequent elements must be rendered over area(s) generated by lexically prior elements, where lexical order is defined as the postorder traversal of a document instance.

The semantics of the value auto are those defined by [XSL 1.1], § 7.28.9, where the tt element is considered to establish the root stacking context.

If a specified value of this attribute is not supported, then a presentation processor must interpret the attribute as if the value auto were specified.

The tts:zIndex style is illustrated by the following example.

Example Fragment – Z Index

<region xml:id="r1">
  <style tts:origin="0px 0px"/>
  <style tts:extent="400px 100px"/>
  <style tts:padding="5px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:zIndex="0"/>
</region>
<region xml:id="r2">
  <style tts:origin="100px 60px"/>
  <style tts:extent="400px 100px"/>
  <style tts:padding="5px"/>
  <style tts:backgroundColor="red"/>
  <style tts:color="white"/>
  <style tts:textAlign="end"/>
  <style tts:zIndex="1"/>
</region>
<region xml:id="r3">
  <style tts:origin="0px 120px"/>
  <style tts:extent="400px 100px"/>
  <style tts:padding="5px"/>
  <style tts:backgroundColor="black"/>
  <style tts:color="white"/>
  <style tts:zIndex="2"/>
</region>
<region xml:id="r4">
  <style tts:origin="100px 180px"/>
  <style tts:extent="400px 100px"/>
  <style tts:padding="5px"/>
  <style tts:backgroundColor="red"/>
  <style tts:color="white"/>
  <style tts:textAlign="end"/>
  <style tts:zIndex="3"/>
</region>
...
<p region="r1">
  I passed by his garden, and marked, with one eye,<br/>
  How the Owl and the Panther were sharing a pie.
</p>
<p region="r2">
  The Panther took pie-crust, and gravy, and meat,<br/>
  While the Owl had the dish as its share of the treat.
</p>
<p region="r3">
  When the pie was all finished, the Owl, as a boon,<br/>
  Was kindly permitted to pocket the spoon:
</p>
<p region="r4">
  While the Panther received knife and fork<br/>
  with a growl,<br/>
  And concluded the banquet by...
</p>

Example Rendition – Z Index

Note:

The semantics of the style property represented by this attribute are based upon that defined by [XSL 1.1], § 7.28.9.

8.3 Style Value Expressions

Style property values include the use of the following expressions:

8.3.1 <alpha>
8.3.2 <color>
8.3.3 <digit>
8.3.4 <duration>
8.3.5 <familyName>
8.3.6 <flowFunction>
8.3.7 <flowIntervalFunction>
8.3.8 <genericFamilyName>
8.3.9 <hexDigit>
8.3.10 <integer>
8.3.11 <length>
8.3.12 <namedColor>
8.3.13 <quotedString>
8.3.14 <string>

8.3.1 <alpha>

An <alpha> expression is used to express an opacity value, where 0 means fully transparent and 1 means fully opaque.

Syntax Representation – <alpha>
<alpha> : float

In the above syntax representation, the syntactic element float must adhere to the lexical representation defined by [XML Schema Part 2] § 3.2.4.1. If the value represented is less than 0.0, then it must be interpreted as equal to 0.0; similarly, if the value represented is greater than 1.0, then it must be interpreted as 1.0.

If a presentation processor does not support a specific, valid opacity value, then it must interpret it as being equal to the closest supported value.

8.3.2 <color>

A <color> expression is used to specify a named color, exact RGB color triple, or exact RGBA color tuple, where the alpha component, if expressed, is maximum (255) at 100% opacity and minimum (0) at 0% opacity, and where the applicable color space is defined by [SRGB].

Syntax Representation – <color>

<color>
  : "#" rrggbb
  | "#" rrggbbaa
  | "rgb" "(" r-value "," g-value "," b-value ")"
  | "rgba" "(" r-value "," g-value "," b-value "," a-value ")"
  | <namedColor>

rrggbb
  :  <hexDigit>{6}

rrggbbaa
  :  <hexDigit>{8}

r-value | g-value | b-value | a-value
  : component-value

component-value
  : non-negative-integer                    // valid range: [0,255]

non-negative-integer
  : <digit>+

When expressing RGB component values, these values are considered to not be premultiplied by alpha.

For the purpose of performing presentation processing such that non-opaque or non-transparent alpha or opacity values apply, then the semantics of compositing functions are defined with respect to the use of the [SRGB] color space for both inputs and outputs of the composition function.

Note:

The use of [SRGB] for the stated semantics of composition is not meant to prevent an actual processor from using some other color space either for internal or external purposes. For example, a presentation processor may ultimately convert the SRGB values used here to the YUV color space for rendition on a television device.

If a presentation processor does not support a specific, valid color or alpha value, then it must interpret it as being equal to the closest supported value.

8.3.3 <digit>

A <digit> is used to express integers and other types of numbers or tokens.

Syntax Representation – <digit>
<digit> : "0" \| "1" \| "2" \| "3" \| "4" \| "5" \| "6" \| "7" \| "8" \| "9"

8.3.4 <duration>

A <duration> expression is used to express a temporal duration value.

Syntax Representation – <duration>
<duration> : <digit>+ ( "." <digit>+ )? metric metric : "s" // seconds \| "ms" // milliseconds \| "f" // frames \| "t" // ticks

It is an error to omit the metric component of a duration.

When operating with smpte time base and discontinuous mode, a duration expression must be considered to denote a duration in (local) real-time, independently of the governing time base.

8.3.5 <familyName>

A <familyName> expression specifies a font family name.

If the name contains a quotation delimiter character, then it must be expressed as a <quotedString>. If the name contains a whitespace character, then it should be expressed as a <quotedString>; however, if it is expressed as a <string>, then it must not contain a COMMA ',' character.

Syntax Representation – <familyName>
<familyName> : <string> \| <quotedString>

8.3.6 <flowFunction>

A <flowFunction> expression specifies a unit of content to be dynamic flowed into and out of a region according to an optional dynamic flow style.

Syntax Representation – <flowFunction>

<flowFunction>
  : "in(" flowArguments ")"
  | "out(" flowArguments ")"

flowArguments
  : flowUnit [ "," flowStyle ]

flowUnit
  : "glyph"
  | "line"
  | "character"
  | "word"
  | extensionToken

flowStyle
  : "jump"
  | "smooth"
  | extensionToken

extensionToken
  : "x-" <token>

Dynamic flow can be specified independently for flowing content into its region and flowing it out of its region. These two phases of dynamic flow are specified using the in() and out() flow functions respectively.

Dynamic flow occurs on the basis of specific visual or semantic content units. In the case of glyph and line, the unit of dynamic flow is based upon a visually rendered construct (glyph) or upon an area of the area tree produced by formatting the affected content. In the case of character and word, the unit of dynamic flow is based upon a semantic unit associated with one or more visually rendered or area units.

The dynamic flow unit word must be interpreted as being dependent upon the language or writing system of the affected content. If the language or writing system is unknown or unspecified, then word is interpreted as follows:

If the affected content consists solely or mostly of Unified CJK Ideographic characters or of characters of another Unicode character block that are afforded similar treatment to that of Unified CJK Ideographic characters, then word is to be interpreted as if character were specified.
Otherwise, word is to be interpreted as denoting a sequence of one or more characters that are not interpreted as an XML whitespace character.

When a flow unit is flowed into or out of its region, the manner by which the unit is flowed is controlled by the optional flowStyle argument of the relevant flow function. If the flow style is specified as jump, or if no flow style is specified, then the flow unit is instantaneously transitioned into, within, or out of the region. If the flow style is smooth, then the flow unit is smoothly transitioned by means of pixel based exposure, movement, or hiding, respectively.

If a presentation processor that supports dynamic flow does not the smooth flow style, then this flow style must be interpreted as if the jump flow style were specified.

8.3.7 <flowIntervalFunction>

A <flowIntervalFunction> expression specifies an interval or duration that affects dynamic flow timing behavior.

Syntax Representation – <flowIntervalFunction>

<flowIntervalFunction>
  : "fill(" flowIntervalArguments ")"
  | "clear(" flowIntervalArguments ")"

flowIntervalArguments
  : "auto"
  | <duration>
  | flowIntervalRate

flowIntervalRate
  : <digit>+ ( "." <digit>+ )?

The fill() flow interval function is used to determine the computed fill interval state parameter for performing dynamic flow processing, which expresses the duration of time between fill timer events, as specified by B.5.1 Fill Timer, which in turn, limits the dynamic flowed content fill rate.

The clear() flow interval function is used to determine the computed clear interval state parameter for performing dynamic flow processing, which expresses the duration of time between clear timer events, as specified by B.5.2 Clear Timer, which in turn, limits the dynamic flowed content retention period.

If a <duration> is specified as an argument to a flow interval function, then it is considered to represent a definite duration. If a flow interval rate is specified as an argument to a flow interval function, then it is considered to represent a definite rate in units per second, where the applicable unit is determined in the context of whether the rate is used with an fill() or clear() flow interval function.

The computed fill and clear interval values are defined by B.3 Flow Interval Timing Calculation.

8.3.8 <genericFamilyName>

A <genericFamilyName> expression specifies a font family using a general token that indicates a class of font families.

The resolution of a generic family name to a concrete font instance is considered to be implementation dependent, both in the case of content authoring and content interpretation.

Syntax Representation – <genericFamilyName>
<genericFamilyName> : "default" \| "monospace" \| "sansSerif" \| "serif" \| "monospaceSansSerif" \| "monospaceSerif" \| "proportionalSansSerif" \| "proportionalSerif"

The mapping between a generic (font) family name and an actual font is not determined by this specification; however, the distinction of monospace versus proportional and serif versus sans-serif should be maintained if possible when performing presentation.

If a generic (font) family name of monospace is specified, then it may be interpreted as equivalent to either monospaceSansSerif or monospaceSerif. The generic family names sansSerif and serif are to be interpreted as equivalent to proportionalSansSerif and proportionalSerif, respectively.

If the generic family name default is specified (or implied by an initial value), then its typographic characteristics is considered to be implementation dependent; however, it is recommended that this default font family be mapped to an monospaced, sans-serif font.

8.3.9 <hexDigit>

A <hexDigit> is used to express integers and other types of numbers or tokens that employ base 16 arithmetic.

For the purpose of parsing, no distinction must be made between lower and upper case.

Syntax Representation – <hexDigit>
<hexDigit> : <digit> \| "a" \| "b" \| "c" \| "d" \| "e" \| "f" \| "A" \| "B" \| "C" \| "D" \| "E" \| "F"

8.3.10 <integer>

An <integer> expression is used to express an arbitrary, signed integral value.

Syntax Representation – <integer>
<integer> : ( "+" \| "-" )? <digit>+

8.3.11 <length>

A <length> expression is used to express either a coordinate component of point in a cartesian space or a distance between two points in a cartesian space.

Syntax Representation – <length>

<length>
  : 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
  : <digit>+

non-negative-real
  : <digit>* "." <digit>+

units
  : "px"
  | "em"
  | "c"                                     // abbreviation of "cell"

It is an error to omit the units component of a scalar length value.

The semantics of the unit of measure px (pixel) are as defined by [XSL 1.1], § 5.9.13.

When specified relative to a font whose size is expressed as a single length measure or as two length measures of equal length, the unit of measure em is considered to be identical to that defined by [XSL 1.1], § 5.9.13; however, when specified relative to a font whose size is expressed as two length measures of non-equal lengths, then one em is equal to the inline progression dimension of the anisomorphically scaled font when used to specify lengths in the inline progression direction and equal to the block progression dimension of the scaled font when used to specify lengths in the block progression direction.

The semantics of the unit of measure c (cell) are defined by the parameter 6.2.1 ttp:cellResolution.

8.3.12 <namedColor>

A <namedColor> is used to express an RGBA color with a convenient name, and where the applicable color space is defined by [SRGB].

For the purpose of parsing, no distinction must be made between lower and upper case.

Syntax Representation – <namedColor>

<namedColor>
  : "transparent"                           // #00000000
  | "black"                                 // #000000ff
  | "silver"                                // #c0c0c0ff
  | "gray"                                  // #808080ff
  | "white"                                 // #ffffffff
  | "maroon"                                // #800000ff
  | "red"                                   // #ff0000ff
  | "purple"                                // #800080ff
  | "fuchsia"                               // #ff00ffff
  | "magenta"                               // #ff00ffff (= fuchsia)
  | "green"                                 // #008000ff
  | "lime"                                  // #00ff00ff
  | "olive"                                 // #808000ff
  | "yellow"                                // #ffff00ff
  | "navy"                                  // #000080ff
  | "blue"                                  // #0000ffff
  | "teal"                                  // #008080ff
  | "aqua"                                  // #00ffffff
  | "cyan"                                  // #00ffffff (= aqua)

Note:

Except for transparent, the set of named colors specified above constitutes a proper subset of the set of named colors specified by [SVG 1.1], § 4.2.

8.3.13 <quotedString>

A <quotedString> is used to express a delimited string that may contain a whitespace or a quotation delimiter character. Two types of quotation delimiters are provided in order to accommodate strings that contain the other delimiter.

Syntax Representation – <quotedString>
<quotedString> : "\"" ( char - { "\"" } )* "\"" \| "\'" ( char - { "\'" } )* "\'"

In the above syntax representation, the syntactic element char must adhere to production [2] Char as defined by [XML 1.0] § 2.2.

8.3.14 <string>

A <string> expression consists of a sequence of characters where no character is a quotation delimiter character.

Syntax Representation – <string>
<string> : ( char - { "\"" \| "\'" } )+

In the above syntax representation, the syntactic element char must adhere to production [2] Char as defined by [XML 1.0] § 2.2.

8.4 Style Resolution

This section defines the semantics of style resolution in terms of a standard processing model as follows:

8.4.1 Style Association
8.4.2 Style Inheritance
8.4.3 Style Resolution Value Categories
8.4.4 Style Resolution Processing

Any implementation of this model is permitted provided that the externally observable results are consistent with the results produced by this model.

Note:

The semantics of style resolution employed here are based upon [XSL 1.1], § 5.

8.4.1 Style Association

Style association is a sub-process of 8.4.4 Style Resolution Processing used to determine the specified style set of each content and layout element.

Style matter may be associated with content and layout matter in a number of ways:

inline styling
referential styling
chained referential styling

In addition to the above, style matter may be associated with layout matter using:

nested styling

8.4.1.1 Inline Styling

Style properties may be expressed in an inline manner by direct specification of an attribute from the TT Style Namespace on the affected element. When expressed in this manner, the association of style information is referred to as inline styling.

Style properties associated by inline styling are afforded a higher priority than all other forms of style association.

Example – Inline Styling
<p tts:color="white">White 1 <span tts:color="yellow">Yellow</span> White 2</p>

Note:

In the above example, the two text fragments "White 1 " and " White 2", which are interpreted as anonymous spans, are not associated with a color style property; rather, they inherit their color style from their parent p element as described in 8.4.2.1 Content Style Inheritance below.

8.4.1.2 Referential Styling

Style properties may be expressed in an out-of-line manner and referenced by the affected element using the style attribute. When expressed in this manner, the association of style information is referred to as referential styling.

If a style attribute specifies multiple references, then those references are evaluated in the specified order, and that order applies to resolution of the value of a style property in the case that it is specified along multiple reference paths.

The use of referential styling is restricted to making reference to style element descendants of a styling element. It is considered an error to reference a style element that is a descendant of a layout element.

Note:

The use of referential styling encourages the reuse of style specifications while sacrificing locality of reference.

Note:

A single content element may be associated with style properties by a hybrid mixture of inline and referential styling, in which case inline styling is given priority as described above by 8.4.1.1 Inline Styling.

Example – Referential Styling
<style xml:id="s1" tts:color="white"/> <style xml:id="s2" tts:color="yellow"/> ... <p style="s1">White 1 <span style="s2">Yellow</span> White 2</p>

Note:

8.4.1.3 Chained Referential Styling

Style properties may be expressed in an out-of-line manner and may themselves reference other out-of-line style properties, thus creating a chain of references starting at the affected element. When expressed in this manner, the association of style information is referred to as chained referential styling.

If the same style property is specified in more than one referenced style set, then the last referenced style set applies, where the order of application starts from the affected element and proceeds to referenced style sets, and, in turn, to subsequent, recursively referenced style sets.

A loop in a sequence of chained style references must be considered an error.

Note:

The use of chained referential styling encourages the grouping of style specifications into general and specific sets, which further aids in style specification reuse.

Note:

A single content element may be associated with style properties by a hybrid mixture of inline, referential styling, and chained referential styling, in which case inline styling is given priority as described above by 8.4.1.1 Inline Styling.

Example – Chained Referential Styling
<style xml:id="s1" tts:color="white" tts:fontFamily="monospaceSerif"/> <style xml:id="s2" style="s1" tts:color="yellow"/> ... <p style="s1">White Monospace</p> <p style="s2">Yellow Monospace</p>

8.4.1.4 Nested Styling

Style properties may be expressed in an nested manner by direct specification of one or more style element children of the affected element. When expressed in this manner, the association of style information is referred to as nested styling.

Style properties associated by nested styling are afforded a lower priority than inline styling but with higher priority than referential styling.

Example – Nested Styling
<region xml:id="r1"> <style tts:extent="128px 66px"/> <style tts:origin="0px 0px"/> <style tts:displayAlign="center"/> </region>

Note:

In this version of this specification, nested styling applies only to the region element.

8.4.2 Style Inheritance

Style inheritance is a sub-process of 8.4.4 Style Resolution Processing used to determine the specified style set of each content and layout element.

Styles are further propagated to content matter using:

content style inheritance
region style inheritance

For the purpose of determining inherited styles, the element hierarchy of an intermediate synchronic document form of a DFXP document instance must be used, where such intermediate forms are defined by 9.3.2 Intermediate Synchronic Document Construction.

Note:

The intermediate synchronic document form is utilized rather than the original form in order to facilitate region inheritance processing.

8.4.2.1 Content Style Inheritance

Style properties are inherited from ancestor content elements within an intermediate synchronic document if a style property is not associated with a content element (or an anonymous span) and the style property is designated as inheritable.

If a style property is determined to require inheritance, then the inherited value must be the value of the same named style property in the computed style set of the element's immediate ancestor element within the applicable intermediate synchronic document.

Example – Content Style Inheritance
<p tts:fontFamily="monospaceSansSerif"> <span tts:color="yellow">Yellow Monospace</span> </p>

Note:

In the above example, the span element that encloses the character items Yellow Monospace is not associated with a tts:fontFamily style property and this property is inheritable; therefore, the value of the tts:fontFamily style is inherited from the computed style set of the ancestor p element, and is added to the specified style set of the span element.

8.4.2.2 Region Style Inheritance

Style properties are inherited from a region element in the following case:

if a style property P is not associated with a content element or an anonymous span E and the style property is designated as inheritable, and
if that style property P is in the computed style set of region R, and
if that element E is flowed into (presented within) region R.

Example – Region Style Inheritance
<region xml:id="r1"> <style tts:color="yellow"/> <style tts:fontFamily="monospaceSerif"/> </region> ... <p region="r1">Yellow Monospace</p>

Note:

In the above example, the anonymous span that encloses the character items Yellow Monospace effectively inherits the tts:color and tts:fontFamily styles specified on the region element into which the p element is flowed (presented).

8.4.3 Style Resolution Value Categories

During style resolution, layout, and presentation processing, three categories of style property values are distinguished as follows:

specified values
computed values
actual values

8.4.3.1 Specified Values

Values of style properties that are associated with or inherited by an element or anonymous span are referred to as specified values. The set of all specified style properties of a given element is referred to as the specified style set of that element.

8.4.3.2 Computed Values

When style properties are specified using relative value expressions, such as a named color, a relative unit (e.g., cell), or a percentage, then they need to be further resolved into absolute units, such as an RGB triple, pixels, etc.

During the style resolution process, all specified style values are reinterpreted (or recalculated) in absolute terms, and then recorded as computed values. The set of all computed style properties of a given element is referred to as the computed style set of that element.

When a style value is inherited, either explicitly or implicitly, it is the computed value of the style that is inherited from an ancestor element. This is required since the resolution of certain relative units, such as percentage, require evaluating the expression in the immediate (local) context of reference, and not in a distant (remote) context of reference where the related (resolving) expression is not available.

8.4.3.3 Actual Values

During the actual presentation process, other transformations occur that map some value expressions to concrete, physical values. For example, the colors of computed style values are further subjected to closest color approximation and gamma correction during the display process. In addition, length value expressions that use pixels in computed style values are considered to express logical rather than physical (device) pixels. Consequently, these logical pixels are subject to being further transformed or mapped to physical (device) pixels during presentation.

The final values that result from the logical to device mapping process are referred to as actual values. The set of all actual style properties of a given element is referred to as the actual style set of that element.

Note:

More than one set of actual values may be produced during the process of presentation. For example, a DFXP presentation processor device may output an RGBA component video signal which is then further transformed by an NTSC or PAL television to produce a final image. In this case, both color and dimensions may further be modified prior to presentation.

Note:

In general, a DFXP presentation processor will not have access to actual style set values; as a consequence, no further use or reference to actual values is made below when formally describing the style resolution process.

8.4.4 Style Resolution Processing

The process of style resolution is defined herein as the procedure (and results thereof) for resolving (determining) the computed values of all style properties that apply to content and layout elements:

8.4.4.1 Conceptual Definitions
8.4.4.2 Specified Style Set Processing
8.4.4.3 Computed Style Set Processing
8.4.4.4 Style Resolution Process

The process described here forms an integral sub-process of 9.3 Region Layout and Presentation.

8.4.4.1 Conceptual Definitions

For the purpose of interpreting the style resolution processing model specified below, the following conceptual definitions apply:

[style property]

a style property, P, is considered to consist of a tuple [name, value], where the name of the property is a tuple [namespace value, unqualified name] and the value of the property is a tuple [category, type, value expression]

Example – conceptual style property
[ ["http://www.w3.org/2006/10/ttaf1#styling", "color"], ["specified", color, "red"] ]

[style (property) set]

a style (property) set consists of an unordered collection of style properties, where no two style properties within the set have an identical name, where by "identical name" is meant equality of namespace value of name tuple and unqualified name of name tuple;

in a specified style (property) set, the category of each style property is "specified"; a specified style (property) set of an element E is referred to as SSS(E);

Example – conceptual (specified) style (property) set

{
  [
    ["http://www.w3.org/2006/10/ttaf1#styling", "backgroundColor"],
    ["specified", color, 0x00FF00 ]
  ],
  [
    ["http://www.w3.org/2006/10/ttaf1#styling", "color"],
    ["specified", color, "red" ]
  ],
  [
    ["http://www.w3.org/2006/10/ttaf1#styling", "fontSize"],
    ["specified", length, "1c" ]
  ],
  [
    ["http://www.w3.org/2006/10/ttaf1#styling", "lineHeight"],
    ["specified", length, "117%" ]
  ]
}

in a computed style (property) set, the category of each style property is either "specified" or "computed"; a computed style (property) set of an element E is referred to as CSS(E);

Example – conceptual (computed) style (property) set

{
  [
    ["http://www.w3.org/2006/10/ttaf1#styling", "backgroundColor"],
    ["specified", color, 0x00FF00 ]
  ],
  [
    ["http://www.w3.org/2006/10/ttaf1#styling", "color"],
    ["computed", color, 0xFF0000 ]
  ],
  [
    ["http://www.w3.org/2006/10/ttaf1#styling", "fontSize"],
    ["computed", length, "24px" ]
  ],
  [
    ["http://www.w3.org/2006/10/ttaf1#styling", "lineHeight"],
    ["computed", length, "28px" ]
  ]
}

[style (property) merging]

a style property P_new is merged into a style (property) set, SS, as follows: if a style property P_old is already present in SS where the name of P_new is identical to the name of P_old, then replace P_old in SS with P_new; otherwise, add P_new to SS;

[style (property) set merging]

a style (property) set SS_new is merged into an existing style (property) set SS_old as follows: for each style property P_new in SS_new, merge P_new into SS_old;

8.4.4.2 Specified Style Set Processing

The specified style set SSS of an element or anonymous span E, SSS(E), is determined according to the following ordered rules:

[initialization] initialize the specified style set SSS of E to the empty set;
[referential and chained referential styling] for each style element S_REF referenced by a style attribute specified on E, and in the order specified in the style attribute, then, if S_REF is a descendant of a styling element, merge the specified style set of S_REF, SSS(S_REF), into the specified style set of E, SSS(E);
[nested styling] for each nested style element child S_NEST of E, and in the specified order of child elements, merge the specified style set of S_NEST, SSS(S_NEST), into the specified style set of E, SSS(E);
[inline styling] for each style property P expressed as a specified styling attribute of E, merge P into the specified style set of E, SSS(E);
[implicit inheritance] if the element type of E is not the styling element type style, then for each inheritable style property P_INH in the set of style properties defined above in 8.2 Styling Attribute Vocabulary, perform the following ordered sub-steps:
1. if P_INH is present in the specified style set of E, SSS(E), then continue to the next inheritable style property;
2. if the element type of E is the layout element type region, then set P′ to the initial value of property P, where the initial value of a property is determined according to the specific property definition found above in 8.2 Styling Attribute Vocabulary;
3. if the element type of E is a content element type or anonymous span, then set P′ to the result of looking up the value of P in the computed style set of the immediate ancestor element of E, i.e., CSS(PARENT(E));
4. if the value of P′ is not undefined, then merge P′ into the specified style set of E, SSS(E).

8.4.4.3 Computed Style Set Processing

The computed style set CSS of an element or anonymous span E, CSS(E), is determined according to the following ordered rules:

[resolve specified styles] determine (obtain) the specified style set SSS of E, namely, SSS(E), in accordance with 8.4.4.2 Specified Style Set Processing;
[initialization] initialize CSS(E) to a (deep) copy of SSS(E);
[filter] if E is a style element, then return CSS(E) as the resulting computed style set without further resolution; otherwise, continue with the next rule;
[relative value resolution] for each style property P in CSS(E), where the value type of P is relative, perform the following ordered sub-steps:
1. replace the relative value of P with an equivalent, non-relative (computed) value;
2. set the category of P to "computed";

Note:

As a result of the filtering rule above, the computed style set of a style element includes only specified values, in which case relative value expressions remain relative; consequently, the resolution of relative value expressions (that may be assigned by means of referential style association) always takes place in the context of a layout or content element which has a presentation context, and not in the non-presentation, declaration context of a referentiable style element.

8.4.4.4 Style Resolution Process

The top-level style resolution process is defined as follows: using a preorder traversal of each element and anonymous span, E, of an intermediate synchronic document, DOC_inter, perform the following ordered sub-steps:

[filter] if the element type of E is not the styling element type style, is not the layout element type region, and is not one of the content element types body, div, p, span, br, or anonymous span, then continue to the next element in the preorder traversal;
[resolve computed styles] determine (obtain) the computed style set CSS of E, namely, CSS(E), in accordance with 8.4.4.3 Computed Style Set Processing.

9 Layout

This section specifies the layout matter of the core vocabulary catalog, where layout is to be understood as a separable layer of information that applies to content and that denotes authorial intentions about the presentation of that content.

Note:

The two layers of layout and style matter are considered to be independently separable. Layout matter specifies one or more spaces or areas into which content is intended to be presented, while style matter specifies the manner in which presentation occurs within the layout.

In certain cases, a content author may choose to embed (inline) style matter directly into layout or content matter. In such cases, an alternative exists – use of referential styling – in which the style matter is not embedded (inlined).

9.1 Layout Element Vocabulary

The following elements specify the structure and principal layout aspects of a document instance:

9.1.1 layout
9.1.2 region

9.1.1 layout

The layout element is a container element used to group layout matter, including metadata that applies to layout matter.

The layout element accepts as its children zero or more elements in the Metadata.class element group, followed by zero or more region elements.

XML Representation – Element Information Item: layout
<layout xml:id = ID xml:lang = string xml:space = (default\|preserve) {any attribute not in default or any TT namespace}> Content: Metadata.class, region </layout>

To the extent that time semantics apply to the content of the layout element, the implied time interval of this element is defined to be coterminous with the external time interval.

9.1.2 region

The region element is used to define a space or area into which content is to be flowed for the purpose of presentation.

In addition, and in accordance with 8.4.2.2 Region Style Inheritance, the region element may be used to specify inheritable style properties to be inherited by content that is flowed into it.

The region element accepts as its children zero or more elements in the Metadata.class element group, followed by zero or more elements in the Animation.class element group, followed by zero or more style elements.

Any metadata specified by children in the Metadata.class element group applies semantically to the region element and its descendants as a whole. Any animation elements specified by children in the Animation.class element group apply semantically to the region element. Any style child element must be considered a local style definition that applies only to the containing region element, i.e., does not apply for resolving referential styling.

XML Representation – Element Information Item: region

<region
  begin = <timeExpression>
  dur = <timeExpression>
  end = <timeExpression>
  style = IDREFS
  timeContainer = (par|seq)
  ttm:role = string
  xml:id = ID
  xml:lang = string
  xml:space = (default|preserve)
  {any attribute in TT Style namespace}
  {any attribute not in default or any TT namespace}>
  Content: Metadata.class*, Animation.class*, style*
</region>

If begin and (or) end attributes are specified on a region element, then they specify the beginning and (or) ending points of a time interval during which the region is eligible for activation and with respect to which animation child elements of the region are timed. If specified, these begin and end points are relative to the time interval of the nearest ancestor element associated with a time interval, irregardless of whether that interval is explicit or implied.

The nearest ancestor element of a region element that is associated with a time interval is the document instance's root tt element.

If a dur attribute is specified on the region element, then it specifies the simple duration of the region.

For the purpose of determining the semantics of presentation processing, a region that is temporally inactive must not produce any visible marks when presented on a visual medium.

Note:

A region element may be associated with a time interval for two purposes: (1) in order to temporally bound the presentation of the region and its content, and (2) to provide a temporal context in which animations of region styles may be effected.

For example, an author may wish a region that is otherwise empty, but may have a visible background color to be presented starting at some time and continuing over the region's duration. The simple duration of the region serves additionaly to scope the presentation effects of content that is targeted to the region. An author may also wish to move a region within the root container extent or change a region's background color by means of animation effects. In both of these cases, it is necessary to posit an active time interval for a region.

If no timeContainer attribute is specified on a region element, then it must be interpreted as having parallel time containment semantics.

If a ttm:role attribute is specified on a region element, then it must adhere to the value syntax defined by Syntax Representation – ttm:role, and where the role(s) identified by this attribute expresses the semantic role(s) of the region independently from the semantic role(s) of any content targeted to (associated with) the region.

9.2 Layout Attribute Vocabulary

This section defines the 9.2.1 region attribute used with content elements.

9.2.1 region

The region attribute is used to reference a region element which defines a space or area into which a content element is intended to be flowed.

The region attribute may be specified by an instance of the following element types:

body
div
p
span

Note:

See 9.3 Region Layout and Presentation below for further information on content flow in a region.

9.3 Region Layout and Presentation

This section defines the semantics of region layout and presentation in terms of a standard processing model as follows:

9.3.1 Default Region
9.3.2 Intermediate Synchronic Document Construction
9.3.3 Synchronic Flow Processing
9.3.4 Elaborated Example

Any implementation is permitted provided that the externally observable results are consistent with the results produced by this model.

9.3.1 Default Region

If a DFXP document instance does not specify a region element, then a default region is implied with the following characteristics:

the identity of the default region is considered to be anonymous;
the extent of the default region is the same as the root container region;
the temporal interval of the default region is the same as temporal interval of the document instance;

Furthermore, if no region element was specified, then the region attribute must not be specified on any content element in the document instance.

If a default region is implied for a given document instance, then the body element is implicitly targeted to (associated with) the default region.

When implying a default region, the document instance is to be treated as if a region element and its parent layout element were specified in a head element, and a matching region attribute were specified on the body element as shown in the following example:

Example – Implied Default Region
<tt xml:lang="" xmlns="http://www.w3.org/2006/10/ttaf1"> <head> <layout> <region xml:id="anonymous"/> </layout> </head> <body region="anonymous"/> </tt>

Note:

In the above example, a default region element and region attribute are implied. In addition, a layout container element is implied for the implied region element.

9.3.2 Intermediate Synchronic Document Construction

For the purposes of performing presentation processing, the active time duration of a document instance is divided into a sequence of time coordinates where at each time coordinate, some element becomes temporally active or inactive, then, at each such time coordinate, a document instance is mapped from its original, source form, DOC_source, to an intermediate synchronic document form, DOC_inter, as follows:

for each temporally active region R, replicate the sub-tree of DOC_source headed by the body element;
evaluating this sub-tree in a postorder traversal, prune elements if they are not a content element, if they are temporally inactive, if they are empty, or if they aren't associated with region R;
if the pruned sub-tree is non-empty, then reparent it to the R element;
finally, after completing the above steps, prune the original body element from the intermediate document, then prune all region, begin, end, and dur attributes, which are no longer semantically relevant;

A content element is associated with a region according to the following ordered rules, where the first rule satisfied is used and remaining rules are skipped:

if the element specifies a region attribute, then the element is associated with the region referenced by that attribute;
if some ancestor of that element specifies a region attribute, then the element is associated with the region referenced by the most immediate ancestor that specifies this attribute;
if the element contains a descendant element that specifies a region attribute, then the element is associated with the region referenced by that attribute;
if a default region was implied (due to the absence of any region element), then the element is associated with the default region;
the element is not associated with any region.

The pseudo-code shown in Example – Content Hierarchy Region Mapping provides one possible algorithm that implements these processing steps.

Example – Content Hierarchy Region Mapping

PREPARE-CONTENT ( D ) := 
  foreach R in SELECT ( D, "/tt/head/layout/region" )
    if TEMPORALLY-ACTIVE? ( R )
      APPEND-CHILDREN ( R, SELECT ( D, "/tt/body" ) )
      foreach E in POSTORDER-TRAVERSE ( R )
        if ! CONTENT-ELEMENT? ( E ) or ! TEMPORALLY-ACTIVE? ( E ) or EMPTY? ( E ) or REGION-OF ( E ) != R
            then PRUNE ( E )
  PRUNE ( SELECT ( D, "/tt/body" ) )
  PRUNE ( SELECT ( D, "//*/@region" ) )
  PRUNE ( SELECT ( D, "//*/@begin" ) )
  PRUNE ( SELECT ( D, "//*/@end" ) )
  PRUNE ( SELECT ( D, "//*/@dur" ) )
 
REGION-OF ( E ) :=
  if NULL? ( E )
    return NULL
  else if HAS-ATTRIBUTE? ( E, "region" )
    return VALUE-OF-ATTRIBUTE ( E, "region" )
  else
    return REGION-OF ( PARENT-OF ( E ) )

The result of performing the processing described above will be a sequence of N intermediate synchronic document instances, DOC_inter₀ … DOC_{inter_N−1}.

9.3.3 Synchronic Flow Processing

Subsequent to performing a temporal (synchronic) slice and subsequent remapping of regionally selected content hierarchy, the resulting intermediate synchronic document is subjected to a flow transformation step that produces a rooted flow object tree represented as an XSL FO document instance as defined by [XSL 1.1], and semantically extended by TT AF specific style properties that have no XSL FO counterpart.

Each intermediate synchronic document produced by 9.3.2 Intermediate Synchronic Document Construction is mapped to an XSL FO document instance, F, as follows:

perform the following ordered sub-steps to create anonymous spans:
1. for each significant text node in a content element, synthesize an anonymous span to enclose the text node, substituting the new anonymous span for the original text node child in its sibling and parent hierarchy;
2. for each contiguous sequence of anonymous spans, replace the sequence with a single anonymous span which contains a sequence of text nodes representing the individual text node children of the original sequence of anonymous spans;
3. for each span element whose child is a single anonymous span, replace the anonymous span with its sequence of child text nodes;
resolve styles according to 8.4.4.4 Style Resolution Process;
map the tt element to an fo:root element, populated initially with an fo:layout-master-set element that contains a valid fo:simple-page-master that, in turn, contains an fo:region-body child, where the root container extent expressed on the tt element is mapped to page-width and page-height attributes on the fo:simple-page-master element;
map the layout element to an fo:page-sequence element and a child fo:flow element that reference the page master and page region defined by the simple page master produced above;
map each non-empty region element to an fo:block-container element with an absolute-position attribute with value absolute, and where the region's position and extent are mapped to equivalent top, left, width, and height attributes;
for each body, div, and p element that is not associated with a tts:display style property with the value none, map the element to a distinct fo:block element, populating the style properties of fo:block by using the computed style set associated with each original TT AF content element;
for the resulting fo:block formatting object produced in the previous step that corresponds to the body element, synthesize and append to the end of its children an empty fo:block with the following attributes: space-after.optimum, space-after.maximum, and space-after.conditionality, where the value of the former two attributes is the height or width of the containing fo:block-container element, whichever of these is designated as the block progression dimension, and where the value of the last is retain;
for each span element that is not associated with a tts:display style property with the value none and for each anonymous span that is a child of a p or span element, map the element or sequence of character items to a distinct fo:inline element, populating the style properties of fo:inline by using the computed style set associated with each original TT AF content element or anonymous span;
for each br element that is not associated with a tts:display style property with the value none, map the element to a distinct fo:character element having the following properties:
- character="
  "
- suppress-at-line-break="retain"
for each TT AF style property attribute in some computed style set that has no counterpart in [XSL 1.1], map that attribute directly through to the relevant formatting object produced by the input TT AF content element to which the style property applies;
optionally, synthesize a unique id attribute on each resulting formatting object element that relates that element to the input element that resulted in that formatting object element;

For each resulting XSL FO document instance DOC_FO, if processing requires presentation on a visual medium, then apply the formatting semantics prescribed by [XSL 1.1] in order to produce an XSL FO area tree that may then be subsequently rendered onto the visual medium.

Note:

In the XSL FO area tree produced by formatting DOC_FO, the page-viewport-area, which is generated by fo:page-sequence element by reference to the sole generated fo:simple-page-master element, corresponds to the root container region defined above in 2 Definitions.

Note:

Due to the possible presence of TT AF style properties or style property values in a given DFXP document instance for which there is no [XSL 1.1] counterpart, the use of a compliant [XSL 1.1] formatting processor is not necessarily sufficient to satisfy the presentation semantics defined by this specification.

9.3.4 Elaborated Example

An example of the processing steps described above is elaborated below, starting with Example – Sample Source Document.

Example – Sample Source Document

<tt tts:extent="640px 480px" xml:lang="en"
  xmlns="http://www.w3.org/2006/10/ttaf1"
  xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
  <head>
    <layout>
      <region xml:id="r1">
        <style tts:origin="10px 100px"/>
        <style tts:extent="620px 96px"/>
        <style tts:fontSize="40px"/>
        <style tts:fontWeight="bold"/>
        <style tts:backgroundColor="black"/>
        <style tts:color="red"/>
        <style tts:textAlign="center"/>
        <style tts:displayAlign="center"/>
      </region>
      <region xml:id="r2">
        <style tts:origin="10px 300px"/>
        <style tts:extent="620px 96px"/>
        <style tts:fontSize="40px"/>
        <style tts:fontWeight="bold"/>
        <style tts:backgroundColor="black"/>
        <style tts:color="yellow"/>
        <style tts:textAlign="center"/>
        <style tts:displayAlign="center"/>
      </region>
    </layout>
  </head>
  <body xml:id="b1">
    <div xml:id="d1" begin="0s" dur="2s">
      <p xml:id="p1" region="r1">Text 1</p>
      <p xml:id="p2" region="r2">Text 2</p>
    </div>
    <div xml:id="d2" begin="1s" dur="2s">
      <p xml:id="p3" region="r2">Text 3</p>
      <p xml:id="p4" region="r1">Text 4</p>
    </div>
  </body>
</tt>

In the above document, the content hierarchy consists of two divisions, each containing two paragraphs. This content is targeted (selected into) one of two non-overlapping regions that are styled identically except for their position and their foreground colors, the latter of which is inherited by and applies to the (and, in this case, anonymous) spans reparented into the regions.

The following, first intermediate document shows the synchronic state at time interval [0,1), during which time only division d1 is temporally active, and where paragraphs p1 and p2 (and their ancestors) are selected into regions r1 and r2, respectively.

Note:

The intermediate documents shown below are not valid DFXP document instances, but rather, are representations of possible internal processing states used for didactic purposes.

Example – Intermediate Document – [0s,1s)

<tt tts:extent="640px 480px" xml:lang="en"
  xmlns="http://www.w3.org/2006/10/ttaf1"
  xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
  <head>
    <layout>
      <region xml:id="r1">
        <style tts:origin="10px 100px"/>
        <style tts:extent="620px 96px"/>
        <style tts:fontSize="40px"/>
        <style tts:fontWeight="bold"/>
        <style tts:backgroundColor="black"/>
        <style tts:color="red"/>
        <style tts:textAlign="center"/>
        <style tts:displayAlign="center"/>
        <body xml:id="b1-1">
          <div xml:id="d1-1">
            <p xml:id="p1">Text 1</p>
          </div>
        </body>
      </region>
      <region xml:id="r2">
        <style tts:origin="10px 300px"/>
        <style tts:extent="620px 96px"/>
        <style tts:fontSize="40px"/>
        <style tts:fontWeight="bold"/>
        <style tts:backgroundColor="black"/>
        <style tts:color="yellow"/>
        <style tts:textAlign="center"/>
        <style tts:displayAlign="center"/>
        <body xml:id="b1-2">
          <div xml:id="d1-2">
            <p xml:id="p2">Text 2</p>
          </div>
        </body>
      </region>
    </layout>
  </head>
</tt>

An XSL FO document instance produced by performing flow processing upon the first intermediate document is shown below.

Example – XSL FO Document – [0s,1s)

<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
  <fo:layout-master-set>
    <fo:simple-page-master master-name="m1"
      page-width="640px" page-height="480px">
      <fo:region-body/>
    </fo:simple-page-master>
  </fo:layout-master-set>
  <fo:page-sequence master-reference="m1">
    <fo:flow flow-name="xsl-region-body">
      <!-- region (r1) -->
      <fo:block-container id="r1" absolute-position="absolute"
        left="10px" top="100px" width="620px" height="96px"
        background-color="black" display-align="center">
        <!-- body (b1) -->
        <fo:block id="b1-1">
          <!-- div (d1) -->
          <fo:block id="d1-1">
            <!-- p (p1) -->
            <fo:block id="p1" text-align="center">
              <fo:inline font-size="40px" font-weight="bold"
              color="red">Text 1</fo:inline>
            </fo:block>
          </fo:block>
          <!-- body's space filler ->
          <fo:block
            space-after.optimum="96px"
            space-after.maximum="96px"
            space-after.conditionality="retain"/>
        </fo:block>
      </fo:block-container>
      <!-- region (r2) -->
      <fo:block-container id="r2" absolute-position="absolute"
        left="10px" top="300px" width="620px" height="96px"
        background-color="black" display-align="center">
        <!-- body (b1) -->
        <fo:block id="b1-2">
          <!-- div (d1) -->
          <fo:block id="d1-2">
            <!-- p (p2) -->
            <fo:block id="p2" text-align="center">
              <fo:inline font-size="40px" font-weight="bold"
              color="yellow">Text 2</fo:inline>
            </fo:block>
          </fo:block>
          <!-- body's space filler ->
          <fo:block
            space-after.optimum="96px"
            space-after.maximum="96px"
            space-after.conditionality="retain"/>
        </fo:block>
      </fo:block-container>
    </fo:flow>
  </fo:page-sequence>
</fo:root>

The following, second intermediate document shows the synchronic state at time interval [1,2), at which time both divisions d1 and d2 are temporally active, and where paragraphs p1 and p4 (and their ancestors) are selected into region r1 and paragraphs p2 and p3 (and their ancestors) are selected into region r2.

Example – Intermediate Document – [1s,2s)

<tt tts:extent="640px 480px" xml:lang="en"
  xmlns="http://www.w3.org/2006/10/ttaf1"
  xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
  <head>
    <layout>
      <region xml:id="r1">
        <style tts:origin="10px 100px"/>
        <style tts:extent="620px 96px"/>
        <style tts:fontSize="40px"/>
        <style tts:fontWeight="bold"/>
        <style tts:backgroundColor="black"/>
        <style tts:color="red"/>
        <style tts:textAlign="center"/>
        <style tts:displayAlign="center"/>
        <body xml:id="b1-1">
          <div xml:id="d1-1">
            <p xml:id="p1">Text 1</p>
          </div>
          <div xml:id="d2-1">
            <p xml:id="p4">Text 4</p>
          </div>
        </body>
      </region>
      <region xml:id="r2">
        <style tts:origin="10px 300px"/>
        <style tts:extent="620px 96px"/>
        <style tts:fontSize="40px"/>
        <style tts:fontWeight="bold"/>
        <style tts:backgroundColor="black"/>
        <style tts:color="yellow"/>
        <style tts:textAlign="center"/>
        <style tts:displayAlign="center"/>
        <body xml:id="b1-2">
          <div xml:id="d1-2">
            <p xml:id="p2">Text 2</p>
          </div>
          <div xml:id="d2-2">
            <p xml:id="p3">Text 3</p>
          </div>
        </body>
      </region>
    </layout>
  </head>
</tt>

The following, third intermediate document shows the synchronic state at time interval [2,3), at which time only division d2 is temporally active, and where paragraphs p4 and p3 (and their ancestors) are selected into regions r1 and r2, respectively.

Example – Intermediate Document – [2s,3s)

<tt tts:extent="640px 480px" xml:lang="en"
  xmlns="http://www.w3.org/2006/10/ttaf1"
  xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
  <head>
    <layout>
      <region xml:id="r1">
        <style tts:origin="10px 100px"/>
        <style tts:extent="620px 96px"/>
        <style tts:fontSize="40px"/>
        <style tts:fontWeight="bold"/>
        <style tts:backgroundColor="black"/>
        <style tts:color="red"/>
        <style tts:textAlign="center"/>
        <style tts:displayAlign="center"/>
        <body xml:id="b1-1">
          <div xml:id="d2-1">
            <p xml:id="p4">Text 4</p>
          </div>
        </body>
      </region>
      <region xml:id="r2">
        <style tts:origin="10px 300px"/>
        <style tts:extent="620px 96px"/>
        <style tts:fontSize="40px"/>
        <style tts:fontWeight="bold"/>
        <style tts:backgroundColor="black"/>
        <style tts:color="yellow"/>
        <style tts:textAlign="center"/>
        <style tts:displayAlign="center"/>
        <body xml:id="b1-2">
          <div xml:id="d2-2">
            <p xml:id="p3">Text 3</p>
          </div>
        </body>
      </region>
    </layout>
  </head>
</tt>

9.4 Line Layout

The semantics of line layout, including line breaking, defined by [XSL 1.1] apply to the performance of the composition and layout of lines for presentation processing of a document instance on a visual medium.

If a profile that applies to a document instance requires use of the #lineBreak-uax14 feature (i.e., the value attribute for the feature is specified as use), then the recommendations defined by Line Breaking Algorithm [UAX14] apply when performing line layout on the content of the document instance.

10 Timing

This section specifies the timing matter of the core vocabulary catalog, where timing is to be understood as a separable layer of information that applies to content and that denotes authorial intentions about the temporal presentation of that content.

10.1 Timing Element Vocabulary

10.2 Timing Attribute Vocabulary

This section defines the following basic timing attributes for use with timed elements:

10.2.1 begin
10.2.2 end
10.2.3 dur

In addition, this section defines the 10.2.4 timeContainer attribute for use with timed elements that serve simultaneously as timing containers.

10.2.1 begin

The begin attribute is used to specify the begin point of a temporal interval associated with a timed element. If specified, the value of a begin attribute must adhere to a <timeExpression> specification as defined by 10.3.1 <timeExpression>.

The begin point of a temporal interval is included in the interval; i.e., the interval is left-wise closed.

The semantics of the begin attribute are those defined by [SMIL 2.1], § 10.4.1, while taking into account any overriding semantics defined by this specification.

10.2.2 end

The end attribute is used to specify the ending point of a temporal interval associated with a timed element. If specified, the value of an end attribute must adhere to a <timeExpression> specification as defined by 10.3.1 <timeExpression>.

The ending point of a temporal interval is not included in the interval; i.e., the interval is right-wise open.

The presentation effects of a non-empty active temporal interval include the frame immediately prior to the frame (or tick) equal to or immediately following the time specified by the ending point, but do not extend into this latter frame (or tick).

Note:

For example, if an active interval is [10s,10.33333s), and the frame rate is 30 frames per second, then the presentation effects of the interval are limited to frames 300 through 309 only (assuming that 0s corresponds with frame 0). The same holds if the active interval is specified as [300f,310f).

The semantics of the end attribute are those defined by [SMIL 2.1], § 10.4.1, while taking into account any overriding semantics defined by this specification.

10.2.3 dur

The dur attribute is used to specify the duration of a temporal interval associated with a timed element. If specified, the value of a dur attribute must adhere to a <timeExpression> specification as defined by 10.3.1 <timeExpression>.

The semantics of the dur attribute are those defined by [SMIL 2.1], § 10.4.1, while taking into account any overriding semantics defined by this specification.

10.2.4 timeContainer

The timeContainer attribute is used to specify a local temporal context by means of which timed child elements are temporally situated.

If specified, the value of a timeContainer attribute must be one of the following:

par
seq

If the time container semantics of an element instance is par, then the temporal intervals of child elements are considered to apply in parallel, i.e., simultaneously in time. Furthermore, the specification of the time interval of each child element is considered to be relative to the temporal interval of the container element instance.

If the time container semantics of an element instance is seq, then the temporal intervals of child elements are considered to apply in sequence, i.e., sequentially in time. Furthermore, the specification of the time interval of each child element is considered to be relative to the temporal interval of its sibling elements, unless it is the first child element, in which case it is considered to be relative to the temporal interval of the container element instance.

Each time container is considered to constitute an independent time base, i.e., time coordinate system.

If a timeContainer attribute is not specified on an element that has time container semantics, then par time container semantics must apply.

Time container semantics applies only to the following element types:

body
div
p
region
span

The semantics of parallel and sequential time containment are those defined by [SMIL 2.1], § 10.3.2, while taking into account any overriding semantics defined by this specification.

10.3 Time Value Expressions

Timing attribute values include the use of the following expressions:

10.3.1 <timeExpression>

10.3.1 <timeExpression>

A <timeExpression> is used to specify a coordinate along some time base, where the applicable time base is determined by the ttp:timeBase parameter.

Note:

See 6.2.11 ttp:timeBase, 6.2.3 ttp:frameRate, 6.2.9 ttp:subFrameRate, and 6.2.10 ttp:tickRate for further information on explicit specification of time base, frame rate, sub-frame rate, and tick rate.

Syntax Representation – <timeExpression>

<timeExpression>
  : clock-time
  | offset-time

clock-time
  : hours ":" minutes ":" seconds ( fraction | ":" frames ( "." sub-frames )? )?

offset-time
  : time-count fraction? metric

hours
  : <digit> <digit>
  | <digit> <digit> <digit>+

minutes | seconds
  : <digit> <digit>

frames
  : <digit> <digit>
  | <digit> <digit> <digit>+

sub-frames
  : <digit>+

fraction
  : "." <digit>+

time-count
  : <digit>+

metric
  : "h"                 // hours
  | "m"                 // minutes
  | "s"                 // seconds
  | "ms"                // milliseconds
  | "f"                 // frames
  | "t"                 // ticks

If a <timeExpression> is expressed in terms of a clock-time, then leading zeroes are used when expressing hours, minutes, seconds, and frames less than 10. Minutes are constrained to the range [0…59], while seconds are constrained to [0…60], where the value 60 applies only to leap seconds.

If a <timeExpression> is expressed in terms of a clock-time and a frames term is specified, then the value of this term must be constrained to the interval [0…F-1], where F is the frame rate determined by the the ttp:frameRate parameter as defined by 6.2.3 ttp:frameRate.

If a <timeExpression> is expressed in terms of a clock-time and a sub-frames term is specified, then the value of this term must be constrained to the interval [0…S-1], where S is the sub-frame rate determined by the the ttp:subFrameRate parameter as defined by 6.2.9 ttp:subFrameRate.

10.4 Time Intervals

The semantics of time containment, durations, and intervals defined by [SMIL 2.1] apply to the interpretation of like-named timed elements and timing vocabulary defined by this specification, given the following constraints:

The implicit duration of an anonymous span is defined as follows: if the anonymous span's parent time container is a parallel time container, then the implicit duration is equivalent to the indefinite duration value as defined by [SMIL 2.1]; if the anonymous span's parent time container is a sequential time container, then the implicit duration is equivalent to zero.
The implicit duration of a body, div, p, or span element is determined in accordance to (1) whether the element is a parallel or sequential time container, and (2) the semantics of [SMIL 2.1] as applied to these time containers.
The implicit duration of the region element is defined to be equivalent to the indefinite duration value as defined by [SMIL 2.1].
If the governing time mode is media or smpte with mode continuous, then time expressions must be interpreted as equivalent to offset clock values related to the associated media time line.
If the governing time mode is smpte with mode discontinuous, then time expressions must be interpreted as equivalent to marker values produced by an external marker event source, in which case all time expressions are equivalent to event based timing in [SMIL 2.1].
If the governing time mode is clock, then time expressions must be interpreted as equivalent to wallclock time expressions in [SMIL 2.1], where the applicable wallclock used is determined by the clock mode parameter.

11 Animation

This section specifies the animation matter of the core vocabulary catalog, where animation is to be understood as a separable layer of information that combines timing and styling in order to denote authorial intention about (temporally) dynamic styling of content.

11.1 Animation Element Vocabulary

The following elements specify the structure and principal animation aspects of a document instance:

11.1.1 set

11.1.1 set

The set element is used as a child element of a content element or a region element in order to express a discrete change of some style parameter value that applies over some time interval.

The set element accepts as its children zero or more elements in the Metadata.class element group.

XML Representation – Element Information Item: set

<set
  begin = <timeExpression>
  dur = <timeExpression>
  end = <timeExpression>
  xml:id = ID
  xml:lang = string
  xml:space = (default|preserve)
  {a single attribute in TT Style namespace}
  {any attribute not in default or any TT namespace}>
  Content: Metadata.class*
</set>

Note:

The use of multiple set element children may be used to effect fade and position transitions.

An example of using the set element to animate content styling is illustrated below:

Example Fragment – Content Style Animation

...
<p dur="5s" tts:color="yellow">
<set begin="1s" dur="1s" tts:color="red"/>
<set begin="2s" dur="1s" tts:color="green"/>
<set begin="3s" dur="1s" tts:color="red"/>
Text with Flashing Colors!
</p>
...

Note:

In the above example, the foreground color of the content "Text with Flashing Colors" is animated from yellow, to red, to green, to red, then back to yellow over a 5 second period.

An example of using the set element to animate region styling is illustrated below:

Example Fragment – Region Style Animation

<tt xml:lang="" xmlns="http://www.w3.org/2006/10/ttaf1"
    xmlns:ttp="http://www.w3.org/2006/10/ttaf1#parameter"
    xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling"
    ttp:cellResolution="40 16">
    <head>
      <layout>
	<region xml:id="r1" timeContainer="seq">
	  <set dur="10s" tts:origin=" 8c 14c"/>
	  <set dur="2s"  tts:origin=" 2c  2c"/>
	  <set dur="3s"  tts:origin=" 8c 14c"/>
	  <set dur="2s"  tts:origin="14c  4c"/>
	  <set dur="10s" tts:origin=" 8c 14c"/>
	  <style tts:extent="24c 2c"/>
	</region>
      </layout>
    </head>
    <body region="r1">...</body>
</tt>

Note:

In the above example, the root container region is divided into a cell grid of 40 columns and 16 rows. A region, r1, with dimensions of 24 columns and 2 rows is then positioned within the root container region, with its position varying over time in order to create an effect of moving the region, which may be desirable so as to avoid obscuring characters in an underlying video with captions.

Note:

The semantics of the set element are based upon that defined by [SMIL 2.1], § 3.5.2.

11.2 Animation Attribute Vocabulary

12 Metadata

This section specifies the metadata matter of the core vocabulary catalog, where metadata is to be understood as a separable layer of information that applies to parameters, content, style, layout, timing, and even metadata itself, where the information represented by metadata takes one of two forms: (1) metadata defined by this specification for standardized use in a document instance, and (2) arbitrary metadata defined outside of the scope of this specification, whose use and semantics depend entirely upon an application's use of TT AF content.

12.1 Metadata Element Vocabulary

The 12.1.1 metadata element serves as a generic container element for grouping metadata information.

In addition, the following elements, all defined in the TT Metadata Namespace, provide standard representations for common metadata that is expected to be commonly used in a document instances:

12.1.2 ttm:title
12.1.3 ttm:desc
12.1.4 ttm:copyright
12.1.5 ttm:agent
12.1.6 ttm:name
12.1.7 ttm:actor

12.1.1 metadata

The metadata element functions as a generic container for metadata information.

Metadata information may be expressed by a metadata element in one of two (non-mutually exclusive) manners: (1) by specifying one or more metadata attributes on the metadata element, and (2) by specifying one or more child elements in the metadata element that express metadata. Both types of metadata are referred to in this document as metadata items.

XML Representation – Element Information Item: metadata

<metadata
  xml:id = ID
  xml:lang = string
  xml:space = (default|preserve)
  {any attribute in TT Metadata namespace}
  {any attribute not in default or any TT namespace}>
  Content: ({any element in TT Metadata namespace}|{any element not in any TT namespace})*
</metadata>

Note:

The meaning of a specific metadata item must be evaluated in the context of where it appears. The core vocabulary catalog permits an arbitrary number of metadata element children of any content element type except for the tt element. See specific element vocabulary definitions for any constraints that apply to such usage.

The use of document metadata is illustrated by the following example.

Example Fragment – Document Metadata

...
<head>
  <metadata xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata">
    <ttm:title>Document Metadata Example</ttm:title>
    <ttm:desc>This document employs document metadata.</ttm:desc>
  </metadata>
</head>
...

The use of element metadata is illustrated by the following example.

Example Fragment – Element Metadata

...
<div>
  <metadata xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata">
    <ttm:title>Chapter 6 – Sherlock Holmes Gives a Demonstration</ttm:title>
    <ttm:desc>Holmes shows Watson how the murderer entered the window.</ttm:desc>
  </metadata>
</div>
...

The use of metadata attribute items is illustrated by the following example.

Example Fragment – Metadata Attribute Items
... <div xmlns:ext="http://foo.bar.example.org/ttaf1#metadata"> <metadata ext:ednote="remove this division prior to publishing"/> </div> ...

Note:

In the above example, a global attribute from a foreign (external) namespace is used to express a metadata attribute that applies semantically to the containing div element. Note that the attribute may also be expressed directly on the div element; however, in this case the author wishes to segregate certain metadata attributes by expressing them indirectly on metadata elements.

12.1.2 ttm:title

The ttm:title element is used to express a human-readable title of a specific element instance.

XML Representation – Element Information Item: ttm:title
<ttm:title xml:id = ID xml:lang = string xml:space = (default\|preserve) {any attribute not in default or any TT namespace}> Content: #PCDATA </ttm:title>

Note:

No specific use of the ttm:title element is defined by this specification.

Examples of the ttm:name element are shown above in Example Fragment – Document Metadata and Example Fragment – Element Metadata.

12.1.3 ttm:desc

The ttm:desc element is used to express a human-readable description of a specific element instance.

XML Representation – Element Information Item: ttm:desc
<ttm:desc xml:id = ID xml:lang = string xml:space = (default\|preserve) {any attribute not in default or any TT namespace}> Content: #PCDATA </ttm:desc>

Note:

No specific use of the ttm:desc element is defined by this specification.

Examples of the ttm:desc element are shown above in Example Fragment – Document Metadata and Example Fragment – Element Metadata.

12.1.4 ttm:copyright

The ttm:copyright element is used to express a human-readable copyright that applies to some scoping level.

A copyright statement that applies to a document as a whole should appear as a child of the head element.

XML Representation – Element Information Item: ttm:copyright
<ttm:copyright xml:id = ID xml:lang = string xml:space = (default\|preserve) {any attribute not in default or any TT namespace}> Content: #PCDATA </ttm:copyright>

Note:

No specific use of the ttm:copyright element is defined by this specification.

12.1.5 ttm:agent

The ttm:agent element is used to define an agent for the purpose of associating content information with an agent who is involved in the production or expression of that content.

The ttm:agent element accepts as its children zero or more ttm:name elements followed by zero or one ttm:actor element.

At least one ttm:name element child should be specified that expresses a name for the agent, whether it be the name of a person, character, group, or organization.

XML Representation – Element Information Item: ttm:agent

<ttm:agent
  type = (person|character|group|organization|other)
  xml:id = ID
  xml:lang = string
  xml:space = (default|preserve)
  {any attribute not in default or any TT namespace}>
  Content: ttm:name*, ttm:actor?
</ttm:agent>

A type attribute must be specified on each ttm:agent element, and, if specified, must have one of the following values:

person
character
group
organization
other

If the value of the type attribute is character, then the ttm:agent element instance should specify a ttm:actor child that specifies the agent that plays the role of the actor.

A ttm:agent metadata item is considered to be significant only when specified as a child of the head element or as a child of a metadata element child of the head element.

Note:

A ttm:agent element instance is typically referenced using a ttm:agent attribute on a content element.

Note:

If a character agent is played by multiple actors, then multiple character agents may be specified (and referenced) wherein different definitions of the character specify different actors.

The use of agent metadata is illustrated by the following example.

Example Fragment – Agent Metadata


<tt xml:lang="en" xmlns="http://www.w3.org/2006/10/ttaf1" xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata">
  <head>
    <ttm:agent xml:id="connery" type="person">
      <ttm:name type="family">Connery</ttm:name>
      <ttm:name type="given">Thomas Sean</ttm:name>
      <ttm:name type="alias">Sean</ttm:name>
      <ttm:name type="full">Sir Thomas Sean Connery</ttm:name>
    </ttm:agent>
    <ttm:agent xml:id="bond" type="character">
      <ttm:name type="family">Bond</ttm:name>
      <ttm:name type="given">James</ttm:name>
      <ttm:name type="alias">007</ttm:name>
      <ttm:actor agent="connery"/>
    </ttm:agent>
  </head>
  <body>
    <div>
      ...  
      <p ttm:agent="bond">I travel, a sort of licensed troubleshooter.</p>
      ...  
    </div>
  </body>
</tt>

Note:

In the above example, two agents, a real (person) agent, Sean Connery, and a fictitious (character) agent, James Bond, are defined, where the latter is linked to the former by means of the a ttm:actor element. A reference is then made from content (the p element) to the character agent associated with (responsible for producing) that content. Note that in this example the ttm:agent metadata items are specified as immediate children of the document's head element rather than being placed in a container metadata element.

12.1.6 ttm:name

The ttm:name element is used to specify a name of a person, character, group, or organization.

XML Representation – Element Information Item: ttm:name

<ttm:name
  type = (full|family|given|alias|other)
  xml:id = ID
  xml:lang = string
  xml:space = (default|preserve)
  {any attribute not in default or any TT namespace}>
  Content: #PCDATA
</ttm:name>

A type attribute must be specified on each ttm:name element, and, if specified, must have one of the following values:

full
family
given
alias
other

The relationship between the type of a name and the syntactic expression of the name is not defined by this specification.

Two examples of the ttm:name element are shown above in Example Fragment – Agent Metadata.

12.1.7 ttm:actor

The ttm:actor element is used to link the definition of a (role-based) character agent with another agent that portrays the character.

XML Representation – Element Information Item: ttm:actor
<ttm:actor agent = IDREF xml:id = ID xml:lang = string xml:space = (default\|preserve) {any attribute not in default or any TT namespace}> Content: EMPTY </ttm:actor>

The agent attribute of a ttm:actor element must reference a ttm:agent element that denotes the person, group, or organization acting the part of a character.

An example of the ttm:actor element is shown above in Example Fragment – Agent Metadata.

12.2 Metadata Attribute Vocabulary

This section specifies the following attributes in the TT Metadata Namespace for use with the metadata element and with certain content elements:

12.2.1 ttm:agent
12.2.2 ttm:role

Note:

Only certain metadata item attributes may be used with content elements. See the definitions of content elements to determine permissible usage.

12.2.1 ttm:agent

The ttm:agent attribute takes an IDREFS value, and is used with certain content elements to designate the agents that perform or are involved in the performance of the content.

If specified, a ttm:agent attribute must reference ttm:agent element instances that appear as a descendent of the same document instance as that of the referring element.

An example of the ttm:agent attribute is shown above in Example Fragment – Agent Metadata.

12.2.2 ttm:role

The ttm:role attribute may be used by a content author to express the roles, functions, or characteristics of some content element that is so labeled.

If specified, the value of this attribute must adhere to the following syntax, where the syntactic element S must adhere to production [3] S as defined by [XML 1.0] § 2.3:

Syntax Representation – ttm:role

ttm:role
  role ( S role )*

role
  : "action"
  | "caption"
  | "description"
  | "dialog"
  | "expletive"
  | "kinesic"
  | "lyrics"
  | "music"
  | "narration"
  | "quality"
  | "sound"
  | "source"
  | "suppressed"
  | "reproduction"
  | "thought"
  | "title"
  | "transcription"
  | extension-role

extension-role
  : "x-" token-char+

token-char
  : { XML NameChar }    // XML 1.1 Production [4a]

Note:

All values of ttm:role that do not start with the prefix x- are reserved for future standardization.

Feature	Transformation	Presentation
`#animation`	O	O
`#backgroundColor`	O	O
`#backgroundColor-block`	O	O
`#backgroundColor-inline`	O	O
`#backgroundColor-region`	O	O
`#bidi`	O	O
`#cellResolution`	O	O
`#clockMode`	O	O
`#color`	O	O
`#content`	M	M
`#core`	M	M
`#direction`	O	O
`#display`	O	O
`#display-block`	O	O
`#display-inline`	O	O
`#display-region`	O	O
`#displayAlign`	O	O
`#dynamicFlow`	O	O
`#dynamicFlow-character`	O	O
`#dynamicFlow-clear`	O	O
`#dynamicFlow-fill`	O	O
`#dynamicFlow-glyph`	O	O
`#dynamicFlow-in`	O	O
`#dynamicFlow-jump`	O	O
`#dynamicFlow-line`	O	O
`#dynamicFlow-out`	O	O
`#dynamicFlow-rollUp`	O	O
`#dynamicFlow-smooth`	O	O
`#dynamicFlow-teletext`	O	O
`#dynamicFlow-word`	O	O
`#extent`	O	O
`#fontFamily`	O	O
`#fontFamily-generic`	O	O
`#fontFamily-non-generic`	O	O
`#fontSize`	O	O
`#fontSize-anisomorphic`	O	O
`#fontSize-isomorphic`	O	O
`#fontStyle`	O	O
`#fontStyle-italic`	O	O
`#fontWeight`	O	O
`#fontWeight-bold`	O	O
`#frameRate`	O	O
`#frameRateMultiplier`	O	O
`#layout`	O	O
`#length`	O	O
`#length-cell`	O	O
`#length-em`	O	O
`#length-integer`	O	O
`#length-negative`	O	O
`#length-percentage`	O	O
`#length-pixel`	O	O
`#length-positive`	O	O
`#length-real`	O	O
`#lineBreak-uax14`	O	O
`#lineHeight`	O	O
`#markerMode`	O	O
`#metadata`	O	O
`#nested-div`	O	O
`#nested-span`	O	O
`#opacity`	O	O
`#origin`	O	O
`#overflow`	O	O
`#overflow-dynamic`	O	O
`#padding`	O	O
`#padding-1`	O	O
`#padding-2`	O	O
`#padding-3`	O	O
`#padding-4`	O	O
`#pixelAspectRatio`	O	O
`#presentation`	O	M
`#profile`	M	M
`#rollUp`	O	O
`#showBackground`	O	O
`#smpteMode`	O	O
`#structure`	M	M
`#styling`	O	O
`#styling-chained`	O	O
`#styling-inheritance-content`	O	O
`#styling-inheritance-region`	O	O
`#styling-inline`	O	O
`#styling-nested`	O	O
`#styling-referential`	O	O
`#subFrameRate`	O	O
`#textAlign`	O	O
`#textAlign-absolute`	O	O
`#textAlign-relative`	O	O
`#textDecoration`	O	O
`#textDecoration-over`	O	O
`#textDecoration-through`	O	O
`#textDecoration-under`	O	O
`#textOutline`	O	O
`#textOutline-blur`	O	O
`#tickRate`	O	O
`#timeBase-clock`	O	O
`#timeBase-media`	O	O
`#timeBase-smpte`	O	O
`#timeContainer`	O	O
`#time-clock`	O	O
`#time-clock-with-frames`	O	O
`#time-offset`	M	M
`#time-offset-with-frames`	O	O
`#time-offset-with-ticks`	O	O
`#timing`	M	M
`#transformation`	M	O
`#unicodeBidi`	O	O
`#visibility`	O	O
`#visibility-block`	O	O
`#visibility-inline`	O	O
`#visibility-region`	O	O
`#wrapOption`	O	O
`#writingMode`	O	O
`#writingMode-vertical`	O	O
`#writingMode-horizontal`	O	O
`#writingMode-horizontal-lr`	O	O
`#writingMode-horizontal-rl`	O	O
`#zIndex`	O	O

Feature	Comments
`#content`	`body`, `div`, `p`, `span`, `br`
`#core`	@`xml:id`, @`xml:lang`, @`xml:space`
`#profile`
`#structure`	`tt`, `head`
`#time-offset`
`#timing`	@`begin`, @`dur`, @`end`
`#transformation`

Feature	Comments
`#content`	`body`, `div`, `p`, `span`, `br`
`#core`	@`xml:id`, @`xml:lang`, @`xml:space`
`#profile`
`#presentation`
`#structure`	`tt`, `head`
`#time-offset`
`#timing`	@`begin`, @`dur`, @`end`

ID	Name	Status	Comments
R100	Specification Format	S
R101	Specification Modularity	S
R102	Specification Organization	S
R103	Core and Periphery	S	TT extension namespaces
R104	Evolution of Core	S	TT extension namespaces
R105	Ownership of Core	S	TT namespaces
R106	Surjection of Core	S
R107	Evolution of Periphery	S	TT extension namespaces
R108	Ownership of Periphery	S	Non-TT namespaces
R109	Transformation	S	Supports 3GPP, QText, RealText, SAMI
R110	Streamable Transformation	S	Progressive decoding
R111	Accessibility – Content	S	Alternative document instances
R112	Accessibility – Authoring System	S
R200	Authorability	S
R201	Multiple Natural Languages	S	Alternative document instances
R202	Natural Language Coverage	S	Unicode 4.0
R203	Natural Language Association Granularity	S	See `xml:lang`
R204	Minimum Character Representability	S	Unicode 4.0
R205	Intrinsic and Extrinsic Text Content	P	Intrinsic only
R206	Markup Association	P	Intrinsic only
R207	Conditional Content	N
R208	Flowed Text	S
R209	Logical Flowed Text Vocabulary	S
R210	Presentational Flowed Text Vocabulary	S	Implied mapping from logical flowed text.
R211	Flowed Text Vocabulary Relationship	S
R212	Flowed Text Vocabulary Separation	N
R213	Non-Flowed Text	N
R214	Non-Flowed Text Vocabulary	N
R215	Hybrid Flowed and Non-Flowed Text	N
R216	Hyperlinking	N	Can support via XLink
R217	Embedded Graphics	N
R218	Non-Embedded Graphics	N
R219	Embedded Fonts	N
R220	Non-Embedded Fonts	N
R221	Descriptive Vocabulary	S	See `ttm:agent`, `ttm:role`
R222	Embedded Audio	N
R223	Non-Embedded Audio	N
R290	Markup Format	S
R291	Markup Format and Unicode Interaction	S
R292	Extrinsic Resource References	N	No extrinsic references
R293	Schema Validity Specification	S
R300	Inline Styling	S
R301	Inline Styling Form	P	Inline and referential styling
R301	Out-of-Line Styling	N
R301	Out-of-Line Styling Form	N
R304	Styling Prioritization	S
R305	Style Parameters – Aural	N
R306	Style Parameters – Visual	P	Supports absolute position, background color, color, display none, display alignment, font family, font size, font style, font weight, height, line height, origin, opacity, overflow, padding (before, after, start, end), text alignment, text shadow (as outline), visibility, width, writing mode, z-index
R307	Style Parameters – Temporal Fill Mode	S	See `tts:dynamicFlow`
R390	Style Parameter Symmetry	S
R391	Style Parameter Definitions	S
R392	Style Parameter Shorthands	S
R401	Inline Timing	S
R402	Out-of-Line Timing	N
R403	Synchronization Parameters	P	Supports begin, end, dur
R404	Synchronization Parameter Value Spaces	P	Supports offset values, media marker values (SMPTE 12M), wallclock values
R405	Time Containment Semantics	P	Supports sequential, parallel
R500	Animation Modes	P	Supports discrete
R501	Scroll Animation	S	See `tts:dynamicFlow`
R502	Highlight Animation	S	`<set tts:backgroundColor="..."/>`
R503	Fade Transition Animation	S	`<set tts:opacity="..."/>`
R504	Animated Style Parameters – Aural	N
R505	Animated Style Parameters – Visual	P	Supports animating background color, color, display, opacity, origin, visibility
N506	Animated Content	S
R600	Metadata Item Association	S	See `metadata`, `Metadata.class`
R601	Metadata Item Constituents	P	Supports name, value
R602	Metadata Item Value Representation	P	See `metadata`
R603	Metadata Item Extensibility	S	See `metadata`
R604	Metadata Item Validation	S	See `metadata`
R690	Dublin Core Preference	N	Uses `ttm:copyright`, `ttm:desc`, `ttm:title`

Element	Model	Reference	Details	Notes
`tt:body`	`xhtml:body`	[XHTML 1.0]	-@class, -@dir, -@lang, -@on, -@title; +@begin, +@dur, +@end, +@region, +@timeContainer, +@ttm:, +@tts:*; content model subsetted to zero or more division (div) children, and supersetted by optional metadata and animation children	1,2
`tt:br`	`xhtml:br`	[XHTML 1.0]	-@class, -@title; +@ttm:, +@tts:, +@xml:lang, +@xml:space; content model supersetted by optional metadata and animation children for congruity with other content vocabulary	1,2
`tt:div`	`xhtml:div`	[XHTML 1.0]	-@class, -@dir, -@lang, -@on, -@title; +@begin, +@dur, +@end, +@region, +@timeContainer, +@ttm:, +@tts:*, +@xml:space; content model subsetted to zero or more paragraph (p) children, and supersetted by optional metadata and animation children	1,2,3
`tt:head`	`xhtml:head`	[XHTML 1.0]	-@dir, -@lang, -@profile; +@id, +@xml:space; content model changed to optional metadata children, followed by optional styling child, followed by optional layout child	1,3
`tt:layout`	`fo:simple-page-master`	[XSL 1.1]	conceptual derivation	4
`tt:metadata`	`svg:metadata`	[SVG 1.1]	-@xml:base; +@ttm:*, +@xml:lang, +@xml:space; content model subsetted to foreign namespace element content only (no #PCDATA)	3,5
`tt:p`	`xhtml:p`	[XHTML 1.0]	-@class, -@dir, -@lang, -@on, -@title; +@begin, +@dur, +@end, +@region, +@timeContainer, +@ttm:, +@tts:*, +@xml:space; content model subsetted to zero or more span children, and supersetted by optional metadata and animation children	1,2,3
`tt:region`	`fo:region-*`	[XSL 1.1]	conceptual derivation	4
`tt:set`	`svg:set`	[SVG 1.1]	-@* except begin, dur, end; +@tts:*, +@xml:lang, +@xml:space	3,6
`tt:span`	`xhtml:span`	[XHTML 1.0]	-@class, -@dir, -@lang, -@on, -@title; +@begin, +@dur, +@end, +@region, +@timeContainer, +@ttm:, +@tts:*, +@xml:space; content model subsetted to zero or more #PCDATA or break (br) children, and supersetted by optional metadata and animation children	1,2,3
`tt:style`	style specification	[CSS2]	XML representation of identified set of pairs of style property name and value, with optional inclusion of other styles by reference to other style elements	7
`tt:styling`	`xhtml:style`	[XHTML 1.0]	XML representation of a set of style specifications sets, each represented by a style child element	1,7
`tt:tt`	`xhtml:html`	[XHTML 1.0]	-@dir, -@lang; +@id, +@ttp:*, +@xml:space; content model subsetted by permitting body and/or head to be optional	1,8
`ttm:actor`	`mpeg7:Creator`	[MPEG7-5]	conceptual derivation	4
`ttm:agent`	`mpeg7:Agent`	[MPEG7-5]	conceptual derivation	4
`ttm:copyright`	`mpeg7:CopyrightString`	[MPEG7-5]	conceptual derivation	4
`ttm:desc`	`svg:desc`	[SVG 1.1]	-@class, -@style, -@xml:base	2,5,9
`ttm:name`	`mpeg7:Name`	[MPEG7-5]	conceptual derivation	4
`ttm:title`	`svg:title`	[SVG 1.1]	-@class, -@style, -@xml:base	2,5,9
`ttp:extension`	`@requiredExtensions`	[SVG 1.1]	conceptual derivation	10
`ttp:extensions`	`@requiredExtensions`	[SVG 1.1]	conceptual derivation	10
`ttp:feature`	`@requiredFeatures`	[SVG 1.1]	conceptual derivation	10
`ttp:features`	`@requiredFeatures`	[SVG 1.1]	conceptual derivation	10
`ttp:profile`	`@baseProfile`	[SVG 1.1]	conceptual derivation	11

Attribute	Model	Reference	Details	Notes
`begin`	`begin`	[SMIL 2.1]	see notes	2,3,4
`dur`	`dur`	[SMIL 2.1]	see notes	2,3,4
`end`	`end`	[SMIL 2.1]	see notes	2,3,4
`region`	`master-reference`	[XSL 1.1]	conceptual derivation
`style`	`class`	[CSS2]	dereferences style specification(s) directly
`timeContainer`	`timeContainer`	[SMIL 2.1]	-excl, -none; no default attribute value	5
`ttm:agent`	none		used to attribute agent of content
`ttm:role`	none		used to attribute role of content
`ttp:cellResolution`	none		expresses uniform grid resolution for cell based coordinates
`ttp:clockMode`	none		determines how to interpret time expressions
`ttp:frameRate`	none		expresses integral frame rate
`ttp:frameRateMultiplier`	none		used to express non-integral, rational frame rates
`ttp:markerMode`	none		expresses marker continuity semantics
`ttp:pixelAspectRatio`	none		expresses pixel aspect ratio of related media
`ttp:profile`	none		expresses profile of TT AF used by document instance
`ttp:smpteMode`	none		expresses frame counting (drop) modes
`ttp:subFrameRate`	none		expresses sub-frame rate
`ttp:tickRate`	none		used to interpret tick based time expressions
`ttp:timeBase`	none		used to interpret semantics of time expressions
`tts:backgroundColor`	`background-color`	[XSL 1.1]	`-inherit`	1,6
`tts:color`	`color`	[XSL 1.1]	`-inherit`	6
`tts:direction`	`direction`	[XSL 1.1]	`-inherit`
`tts:display`	`display`	[CSS2]	only `auto`, `none`
`tts:displayAlign`	`display-align`	[XSL 1.1]	`-inherit`	1
`tts:dynamicFlow`	none		defines dynamic overflow behavior
`tts:extent`	`width`, `height`	[XSL 1.1]	shorthand property
`tts:fontFamily`	`font-family`	[XSL 1.1]	`-inherit`, extends generic family names	1
`tts:fontSize`	`font-size`	[XSL 1.1]	`-inherit`	1,7
`tts:fontStyle`	`font-style`	[XSL 1.1]	`-inherit`, uses alias `reverseOblique` for `backslant`	1
`tts:fontWeight`	`font-weight`	[XSL 1.1]	`-inherit`, `-bolder`, `-lighter`, `-<number>`	1
`tts:lineHeight`	`line-height`	[XSL 1.1]	`-inherit`, `-<number>`, `-<space>`	1
`tts:opacity`	`opacity`	[CSS3 Color]	`-inherit`
`tts:origin`	`top`, `left`	[XSL 1.1]	shorthand property
`tts:overflow`	`overflow`	[XSL 1.1]	`-inherit`, `-auto`, `-error-if-overflow`; `+dynamic`	8
`tts:padding`	`padding`	[XSL 1.1]	`-inherit`	9
`tts:showBackground`	`showBackground`	[SMIL 2.1]	`-inherit`
`tts:textAlign`	`text-align`	[XSL 1.1]	`-inherit`	1
`tts:textDecoration`	`text-decoration`	[XSL 1.1]	`-inherit`	1,10,13
`tts:textOutline`	`text-shadow`	[XSL 1.1]	`-inherit`	11,13
`tts:unicodeBidi`	`unicode-bidi`	[XSL 1.1]	`-inherit`	1
`tts:visibility`	`visibility`	[XSL 1.1]	`-inherit`, `-collapse`
`tts:wrapOption`	`wrap-option`	[XSL 1.1]	`-inherit`	1
`tts:writingMode`	`writing-mode`	[XSL 1.1]	`-inherit`, `+tblr`	1
`tts:zIndex`	`z-index`	[XSL 1.1]	`-inherit`	1
`xml:id`	`xml:id`	[XML ID]	complies with model
`xml:lang`	`xml:lang`	[XML 1.0]	complies with model
`xml:space`	`xml:space`	[XML 1.0]	see notes	12

Requirement	YES	NO	N/A	Notes
Requirement 01: Include a conformance clause	YES
Requirement 02: Define the scope.	YES
Requirement 03: Identify who or what will implement the specification.	YES
Requirement 04: Make a list of normative references.	YES
Requirement 05: Define the terms used in the normative parts of the specification.	YES
Requirement 06: Create conformance labels for each part of the conformance model.	YES
Requirement 07: Use a consistent style for conformance requirements and explain how to distinguish them.	YES
Requirement 08: Indicate which conformance requirements are mandatory, which are recommended, and which are optional.	YES
Requirement 09: If the technology is subdivided, then indicate which subdivisions are mandatory for conformance.	YES
Requirement 10: If the technology is subdivided, then address subdivision constraints.	YES
Requirement 11: Address Extensibility.	YES
Requirement 12: Identify deprecated features.			N/A	1
Requirement 13: Define how each class of product handles each deprecated feature.			N/A	1

Guideline	YES	NO	N/A	Notes
Good Practice 01: Define the specification's conformance model in the conformance clause.	YES
Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.	YES
Good Practice 03: Provide the wording for conformance claims.	YES
Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.		NO
Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.	YES
Good Practice 06: Provide examples, use cases, and graphics.	YES
Good Practice 07: Write sample code or tests.	YES
Good Practice 08: When imposing requirements by normative references, address conformance dependencies.	YES			1
Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.	YES
Good Practice 10: Use terms already defined without changing their definition.	YES			2
Good Practice 11: Use formal languages when possible.	YES
Good Practice 12: Write Test Assertions.		NO		3
Good Practice 13: Create subdivisions of the technology when warranted.	YES
Good Practice 14: If the technology is profiled, define rules for creating new profiles.	YES
Good Practice 15:Use optional features as warranted.	YES
Good Practice 16: Clearly identify optional features.	YES
Good Practice 17: Indicate any limitations or constraints on optional features.	YES
Good Practice 18: If extensibility is allowed, define an extension mechanism.	YES
Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.	YES
Good Practice 20: Define error-handling for unknown extensions.	YES			4
Good Practice 21: Explain how to avoid using a deprecated feature.			N/A	5
Good Practice 22: Identify obsolete features.			N/A	5
Good Practice 23: Define an error handling mechanism.	YES