Character
In Dubbing Scripts, it is necessary to identify each character in the programme. This is done with a Character object which has the following properties:
@@ -534,44 +589,45 @@
Character
- A Character is represented in TTML with the following structure and constraints:
-
- - If the Character has a Talent Name property:
-
- - A
<ttm:agent>
element corresponding to the Talent Name
- MUST be present at the path
- /tt/head/metadata/ttm:agent
, with the following constraints:
-
- - its
type
attribute MUST be set to person
- - its
xml:id
attribute MUST be set.
- - it MUST have a
<ttm:name>
child element whose
- type
MUST be set to full
and its content set to the Talent Name
-
-
- - If more than one Character is associated with the same
- Talent Name there SHOULD be a single
-
<ttm:agent>
element corresponding to that Talent Name,
- referenced separately by each of the Characters.
- - Each
<ttm:agent>
element corresponding to a Talent Name
- SHOULD appear before any of the Character <ttm:agent>
elements
- whose <ttm:actor>
child element references it.
-
+ A Character is represented in TTML with the following structure and constraints:
+
+ - If the Character has a Talent Name property:
+
+ - A
<ttm:agent>
element corresponding to the Talent Name
+ MUST be present at the path
+ /tt/head/metadata/ttm:agent
, with the following constraints:
+
+ - its
type
attribute MUST be set to person
+ - its
xml:id
attribute MUST be set.
+ - it MUST have a
<ttm:name>
child element whose
+ type
MUST be set to full
and its content set to the Talent Name
+
+
+ - If more than one Character is associated with the same
+ Talent Name there SHOULD be a single
+
<ttm:agent>
element corresponding to that Talent Name,
+ referenced separately by each of the Characters.
+ - Each
<ttm:agent>
element corresponding to a Talent Name
+ SHOULD appear before any of the Character <ttm:agent>
elements
+ whose <ttm:actor>
child element references it.
+
+
- - The Character is represented by a
<ttm:agent>
element present at the path
- /tt/head/metadata/ttm:agent
, with the following constraints:
-
- - The
type
attribute MUST be set to character
.
- - The
xml:id
attribute MUST be present on the ttm:agent
and set to the Character Identifier.
- - The
ttm:agent
MUST contain a ttm:name
element with its type
attribute set to alias
and its content set to the Character Name.
- - If the Character has a Talent Name, it MUST contain a
<ttm:actor>
child element.
- That child element MUST have an agent
attribute set to
- the xml:id
of the <ttm:agent>
element
- corresponding to the Talent Name,
- that is, whose type
is set to person
.
-
-
+ - The Character is represented by a
<ttm:agent>
element present at the path
+ /tt/head/metadata/ttm:agent
, with the following constraints:
+
+ - The
type
attribute MUST be set to character
.
+ - The
xml:id
attribute MUST be present on the ttm:agent
and set to the Character Identifier.
+ - The
ttm:agent
MUST contain a ttm:name
element with its type
attribute set to alias
and its content set to the Character Name.
+ - If the Character has a Talent Name, it MUST contain a
<ttm:actor>
child element.
+ That child element MUST have an agent
attribute set to
+ the xml:id
of the <ttm:agent>
element
+ corresponding to the Talent Name,
+ that is, whose type
is set to person
.
+
+
-
+
...
<metadata>
<ttm:agent type="character" xml:id="character_1">
@@ -579,11 +635,9 @@ Character
</ttm:agent>
</metadata>
...
-
-
-
+
-
+
...
<metadata>
<ttm:agent type="person" xml:id="actor_A">
@@ -595,42 +649,41 @@ Character
</ttm:agent>
</metadata>
...
-
-
All <ttm:agent>
elements SHOULD be contained in the first <metadata>
element in the <head>
element.
- There can be multiple
<metadata>
elements in the
<head>
element,
- for example to include
proprietary metadata
- but the above recommends that only one is used to define the characters.
-
-
+
+ All <ttm:agent>
elements SHOULD be contained in the first <metadata>
element in the <head>
element.
+ There can be multiple
<metadata>
elements in the
<head>
element,
+ for example to include
proprietary metadata
+ but the above recommends that only one is used to define the characters.
+
+
- A Character Style is represented in TTML with the following structure and constraints:
-
- - Each Character Style is represented by one or more
<style>
elements
- at the path /tt/head/styling/style
.
- - Each such
<style>
element is associated with the Character by having a ttm:agent
attribute
- whose value is the xml:id
of the <ttm:agent>
element representing the Character.
- - A Script Event MAY apply Character Styles by including the
xml:id
of each style
- in the style
attribute of the <div>
element that defines that Script Event.
- - A Text object MAY apply Character Styles by including the
xml:id
of each style
- in the style
attribute of the <p>
element that defines that Text object.
- - A Script Event SHOULD NOT apply a Character Style for a Character that is not associated with that Script Event.
- - A Text object SHOULD NOT apply a Character Style for a Character that is not associated with that Text object's Script Event.
-
-
-
- Any style attribute defined in [[ttml2]] or [[ttml-imsc1.2]]
- (or other profiles using non-W3C namespaces) can be present on the <style>
element.
- A <style>
element MAY omit the ttm:agent
attribute if it is not associated with a Character.
- Such styles MAY be applied in the same way as any other style, via a reference in the style
attribute.
- Character Styles are applied to Script Events and Text by using the style
attribute to specify the set of applicable styles.
- Presentation Processors MUST NOT apply character styles to text if they are not specified using the style
attribute.
-
-
-
+ A Character Style is represented in TTML with the following structure and constraints:
+
+ - Each Character Style is represented by one or more
<style>
elements
+ at the path /tt/head/styling/style
.
+ - Each such
<style>
element is associated with the Character by having a ttm:agent
attribute
+ whose value is the xml:id
of the <ttm:agent>
element representing the Character.
+ - A Script Event MAY apply Character Styles by including the
xml:id
of each style
+ in the style
attribute of the <div>
element that defines that Script Event.
+ - A Text object MAY apply Character Styles by including the
xml:id
of each style
+ in the style
attribute of the <p>
element that defines that Text object.
+ - A Script Event SHOULD NOT apply a Character Style for a Character that is not associated with that Script Event.
+ - A Text object SHOULD NOT apply a Character Style for a Character that is not associated with that Text object's Script Event.
+
+
+ Any style attribute defined in [[ttml2]] or [[ttml-imsc1.2]]
+ (or other profiles using non-W3C namespaces) can be present on the <style>
element.
+ A <style>
element MAY omit the ttm:agent
attribute if it is not associated with a Character.
+ Such styles MAY be applied in the same way as any other style, via a reference in the style
attribute.
+ Character Styles are applied to Script Events and Text by using the style
attribute to specify the set of applicable styles.
+ Presentation Processors MUST NOT apply character styles to text if they are not specified using the style
attribute.
+
+
+
...
@@ -652,12 +705,12 @@ Character
-