-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathindex.html
1300 lines (1259 loc) · 62.5 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<script defer src="https://www.w3.org/Tools/respec/respec-w3c" class="remove"></script>
<script class="remove">
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
specStatus: "ED",
// the specification's short name, as in https://www.w3.org/TR/short-name/
shortName: "dapt",
// if there a publicly available Editor's Draft, this is the link
edDraftURI: "https://w3c.github.io/dapt/",
// editors, add as many as you like
// only "name" is required
editors: [
{ name: "Cyril Concolato", w3cid: "36324", mailto: "[email protected]", url: "", company: "Netflix", companyURL: "https://www.netflix.com/"},
{ name: "Nigel Megitt", w3cid: "64750", mailto: "[email protected]", url: "", company: "British Broadcasting Corporation", companyURL: "https://www.bbc.co.uk"},
],
// name of the WG
group: "wg/timed-text",
github: "w3c/dapt",
wgPublicList: "public-tt",
// local bibliography
localBiblio: {
"WHP051": {
title: "BBC R&D White Paper WHP 051. Audio Description: what it is and how it works",
publisher: " N.E. Tanton, T. Ware and M. Armstrong",
status: "October 2002 (revised July 2004)",
href: "http://www.bbc.co.uk/rd/publications/whitepaper051",
},
},
};
</script>
<style>
table.coldividers td + td { border-left:1px solid gray; }
table.syntax { border: 0px solid black; width: 85%; border-collapse: collapse }
table.syntax caption { font-weight: bold; text-align: left; padding-bottom: 0.5em }
table.syntax th { border: 0px solid black; text-align: left }
table.syntax td { border: 0px solid black }
table.syntax div { background-color: #ffffc8 }
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
ul.short-list { margin: 0; padding-left: 0; list-style-position: inside;}
.note {font-size:small}
.equation {text-indent: 10%;}
.example {font-size: small}
.inline-note {font-size: small}
.deprecation {background-color: #EBEBFE; border: 3px double; margin: 2px;}
.deprecation::before {content: "\26A0"; margin:0.2em; font-size:2em; float:left;}
body {
font-family: sans-serif;
line-height: 24px;
}
span.label {
display: inline-block;
border-radius: 3px;
}
span.permitted::before {
content: "\00A0\2713\00A0"
}
span.prohibited::before {
content: "\00A0\2718\00A0"
}
span.permitted-deprecated::before {
font-weight: bold;
content: "\00A0!\00A0"
}
span.label::after {
content: "\00A0";
}
span.permitted {
color: black;
background-color: #50FF50;
}
span.prohibited {
color: black;
background-color: #FF5F5F;
}
span.permitted-deprecated {
color: black;
background-color: #FFC000;
}
</style>
</head>
<body>
<h1 id="title">Dubbing and Audio description Profiles of TTML2</h1>
<section id="abstract">
This specification defines <abbr title="Dubbing and Audio description Profiles of TTML2">DAPT</abbr>, a <abbr title="Timed Text Markup Language">TTML</abbr>-based file format for the exchange of timed text content in dubbing and audio description workflows.
</section>
<section id="sotd">
</section>
<section id="scope">
<h2>Scope</h2>
<p>This specification defines a text-based profile of the Timed Text Markup Language version 2.0 [[TTML2]] based on [[ttml-imsc1.1]].
This profile is intended to support dubbing and audio description workflows worldwide,
to meet the requirements defined in [[[?DAPT-REQS]]], and to permit the visual presentation
features within [[ttml-imsc1.1]].
<p class="issue" data-number="5"></p>
</section>
<section class='informative' id="introduction">
<h2>Introduction</h2>
<p>Creating a dub is a complex, multi-step process that involves:
<ul>
<li>Transcribing and timing the dialogue in the original language from a completed show to create a source transcription text</li>
<li>Notating dialogue events with character information and other annotations</li>
<li>Generating localization notes to guide further adaptation</li>
<li>Translating the dialogue to a target language</li>
<li>Adapting the translation to the dubbing and subtitling specifications; ex. matching the actor’s lip movements in the case of dubs and considering reading speeds and shot changes.</li>
</ul>
</p>
<p>The result of creating a dubbing script can be useful as a starting point for creation of subtitles or closed captions in alternate languages;
This specification is designed to facilitate conversion to [[ttml-imsc1.1]] documents,
for example by permitting IMSC styling syntax to be carried in DAPT documents.
</p>
<p>Creating audio description content is also a complex process with similar steps.</p>
<p>
<a>Audio Description</a>, also known as Video Description, is an audio service to assist viewers who can not fully see a visual presentation
to understand the content, usually achieved by mixing a ‘<a>description</a>’ audio track
with the <a>main programme audio</a>, at moments when this does not clash with dialogue, to deliver an <a>audio description mixed audio track</a>.
More information about what <a>Audio Description</a> is and how it works can be found at [[WHP051]].
</p>
<p class="issue" data-number="28"></p>
<p>This specification defines DAPT, a TTML-based format for the exchange of timed text content among authoring and prompting tools in the localization and audio description pipeline.
A DAPT file is designed to carry pertinent information for dubbing or audio description such as type of script, dialogues, descriptions, timing, metadata, original language text, transcribed text, language information, and to be extensible for future annotations.
This specification first defines the data model (see [[[#data-model]]]) for DAPT scripts and then its representation as a TTML document with restrictions (see [[[#ttml-format]]]).</p>
<section id="intro-example">
<h3>Example documents</h3>
<p class="ednote">Do we need examples with metadata e.g. script type?</p>
<p class="issue" data-number="48"></p>
<p>The top level structure of a document is as follows:</p>
<pre class="example"
data-include="examples/intro-top-level.xml"
data-include-format="text">
</pre>
<p>The following examples correspond to the timed text scripts produced
at each stage of the workflow described in [[DAPT-REQS]].</p>
<p>The first example shows a script where timed opportunities for descriptions
or transcriptions have been identified but no text has been written:</p>
<pre class="example"
data-include="examples/intro-times-only.xml"
data-include-format="text">
</pre>
<p>When descriptions or transcriptions are added this becomes a Pre Recording Script: Text with times, or Original language Text with times:</p>
<pre class="example"
data-include="examples/intro-times-and-text.xml"
data-include-format="text">
</pre>
<p>After translating the text, this becomes Text in original language and dub language with times:</p>
<pre class="example"
data-include="examples/intro-original-language-with-dub-language.xml"
data-include-format="text">
</pre>
<p>After creating audio recordings, if not using text to speech, instructions for playback
mixing can be inserted. For example, The gain of "received" audio can be changed before mixing in
the audio played from inside the <code>span</code>, smoothly
animating the value on the way in and returning it on the way out:</p>
</p>
<pre class="example"
data-include="examples/intro-script-with-gain.xml"
data-include-format="text">
</pre>
<p>In the above example, the <code>div</code> element's
<code>begin</code> time becomes the "syncbase" for its child,
so the times on the <code>animate</code> and <code>span</code>
elements are relative to 25s here.
The first <code>animate</code> element drops the gain from 1
to 0.39 over 0.3s, freezing that value after it ends,
and the second one raises it back in the
final 0.3s of this description. Then the <code>span</code> is
timed to begin only after the first audio dip has finished.</p>
<p>If the audio recording is long and just a snippet needs to be played,
that can be done using <code>clipBegin</code> and <code>clipEnd</code>.
If we just want to play the part of the audio from file from 5s to
8s it would look like:</p>
<pre class="example"
data-include="examples/intro-script-with-audio-clipped.xml"
data-include-format="text">
</pre>
<p>Or audio attributes can be added to trigger the text to be spoken:
</p>
<pre class="example"
data-include="examples/intro-script-with-speak.xml"
data-include-format="text">
</pre>
</section>
</section>
<section id="conventions">
<h2>Documentation Conventions</h2>
<p>
This document uses the same conventions as [[TTML2]] for the specification of parameter attributes, styling attributes and metadata elements. In particular:
</p>
<p>
Section 2.3 of [[TTML2]] specifies conventions used in the [[XML]] representation of elements; and
Sections 6.2 and 8.2 of [[TTML2]] specify conventions used when specifying the syntax of attribute values.
</p>
<p>
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 expression "non-normative", then the entirety of the section or appendix is considered non-normative.
</p>
<p>
This specification uses Feature designations as defined in Appendices E at [[TTML2]]:
when making reference to content conformance, these designations refer to the syntactic expression or the semantic capability associated with each designated Feature; and
when making reference to processor conformance, these designations refer to processing requirements associated with each designated Feature.
If the name of an element referenced in this specification is not namespace qualified, then the TT namespace applies (see <a href="#namespaces">9.3 Namespaces</a>.)
</p>
</section>
<section id="definitions">
<h2>Definitions</h2>
<p>
The following terms are used in this proposal:
</p>
<p>
<dfn>Audio description</dfn> An audio rendition of a <a>Description</a> or a set of <a>Descriptions</a>.
</p>
<p>
<dfn>Audio description mixed audio track</dfn> The output of an audio mixer incorporating the main programme audio and the audio description.
</p>
<p>
<dfn data-lt="Description|Descriptions">Description</dfn> A set of words that describe an aspect of the programme presentation, suitable for rendering into audio by means of vocalisation and recording or used as a <a>Text Alternative</a> source for text to speech translation.
</p>
<p>
<dfn data-lt="Document Instance|Document Instances" data-cite="ttml2#terms-document-instance">Document Instance</dfn> As defined by [[TTML2]].
</p>
<p>
<dfn data-cite="ttml2#terms-document-interchange-context">Document Interchange Context</dfn> As defined by [[TTML2]].
</p>
<p>
<dfn data-cite="ttml2#terms-document-processing-context">Document Processing Context</dfn> See Section 2.2 at [[TTML2]].
</p>
<p>
<dfn data-cite="ttml2#terms-feature">Feature</dfn> See Section 2.2 at [[TTML2]].
</p>
<p>
<dfn data-cite="ttml2#terms-intermediate-synchronic-document">Intermediate Synchronic Document</dfn> See Section 11.3.1.3 at [[TTML2]].
</p>
<p>
<dfn data-cite="ttml2#style-value-lwsp">Linear White-Space</dfn> See Section 2.3 at [[TTML2]].
</p>
<p>
<dfn>Main programme audio</dfn> The audio associated with the programme prior to any mixing with audio description.
</p>
<p>
<dfn data-cite="ttml2#terms-presentation-processor">Presentation processor</dfn> See Section 2.2 at [[TTML2]].
</p>
<p>
<dfn data-cite="ttml2#terms-processor">Processor</dfn> Either a Presentation processor or a Transformation processor.
</p>
<p>
<dfn data-cite="ttml2#terms-profile">Profile</dfn> A TTML profile specification is a document that lists all the features of TTML that are required / optional / prohibited within “document instances” (files) and “processors” (things that process the files), and any extensions or constraints.
</p>
<p>
<dfn data-cite="ttml2#terms-related-media-object">Related Media Object</dfn> See Section 2.2 at [[TTML2]].
</p>
<p>
<dfn>Related Video Object</dfn> A <a>Related Media Object</a> that consists of a sequence of image frames, each a rectangular array of pixels.
</p>
<p>
<dfn data-cite="ttml2#terms-root-container-region">Root Container Region</dfn> See Section 2.2 at [[TTML2]].
</p>
<p>
<dfn>Text Alternative</dfn> As defined in [[WCAG20]].
</p>
<p>
<dfn data-cite="ttml2#terms-transformation-processor">Transformation processor</dfn> See Section 2.2 at [[TTML2]].
</p>
</section>
<section id="conformance">
<p>
A <a>Document Instance</a> that conforms to the profile defined herein:
</p>
<ul style="list-style-type:disc">
<li>MUST satisfy all normative provisions specified by the profile;</li>
<li>MAY include any vocabulary, syntax or attribute value associated with a Feature whose disposition is permitted or optional in the profile;</li>
<li>MUST include any vocabulary, syntax or attribute value associated with a Feature whose disposition is required in the profile.</li>
<li>MUST NOT include any vocabulary, syntax or attribute value associated with a Feature whose disposition is prohibited in the profile.</li>
</ul>
<p class="note">
A <a>Document Instance</a>, by definition, satisfies the requirements of Section 3.1 at [[TTML2]], and hence a Document Instance that conforms to a profile defined herein is also a conforming TTML2 Document Instance.
</p>
<p>
A <a>presentation processor</a> that conforms to the profile defined in this specification:
</p>
<ul style="list-style-type:disc">
<li>MUST satisfy the Generic Processor Conformance requirements at Section 3.2.1 of [[TTML2]]</li>
<li>MUST satisfy all normative provisions specified by the profile; and</li>
<li>MUST implement presentation semantic support for every Feature designated as permitted or required by the profile, subject to any additional constraints on each Feature as specified by the profile.</li>
<li>MAY implement presentation semantic support for every Feature designated as optional by the profile, subject to any additional constraints on each Feature as specified by the profile.</li>
</ul>
<p>
A <a>transformation processor</a> that conforms to the profile defined in this specification:
</p>
<ul style="list-style-type:disc">
<li>MUST satisfy the Generic Processor Conformance requirements at Section 3.2.1 of [[TTML2]];</li>
<li>MUST satisfy all normative provisions specified by the profile; and</li>
<li>MUST implement transformation semantic support for every Feature designated as permitted or required by the profile, subject to any additional constraints on each Feature as specified by the profile.</li>
<li>MAY implement transformation semantic support for every Feature designated as optional by the profile, subject to any additional constraints on each Feature as specified by the profile.</li>
</ul>
<p class="note">
The use of the terms <a>presentation processor</a>
and <a>transformation processor</a> within this document does not imply conformance <i>per se</i> to any of the Standard Profiles defined in [[TTML2]].
In other words, it is not considered an error for a <a>presentation processor</a> or <a>transformation processor</a> to conform to the profile defined in this document without also conforming to the TTML2 Presentation Profile or the TTML2 Transformation Profile.
</p>
<p class="note">
This document does not specify presentation processor or transformation processor behavior when processing or transforming a non-conformant Document Instance.
</p>
<p class="note">
The permitted and prohibited dispositions do not refer to the specification of a ttp:feature or ttp:extension element as being permitted or prohibited within a ttp:profile element.
</p>
</section>
<section id="data-model">
<h2>DAPT Data Model and corresponding TTML syntax</h2>
<p>This section specifies the data model for DAPT and its corresponding TTML syntax.</p>
<p class="issue" data-number="12"></p>
<section>
<h3>DAPT Script</h3>
<p>A <dfn>DAPT Script</dfn> is a document resulting from an authoring workflow with the properties defined in the following sections. It is represented as a TTML document with the structure and constraints also defined in the following sections.</p>
<section>
<h4>Script Type</h4>
<p>The <dfn>Script Type</dfn> property describes the type of documents used Dubbing and Audio Description workflows, among the following: <a>Original Language Dialogue List</a>, <a>Translated Dialogue List</a>, <a>Pre-recording Dub Script</a>, <a>As-recorded Dub Script</a>, and <a>Audio Description Script</a>.</p>
<p>To represent this property, the following TTML structure and constraints apply:
<ul>
<li>The <code>head</code> element MUST be present</li>
<li>A single <code>metadata</code> element MUST be present in the <code>head</code> element with the <code>ttm:role</code> attribute set to one of the values defined below.</li>
</ul>
</p>
<p class="issue" data-number="24"></p>
<p class="issue" data-number="32"></p>
<p class="issue" data-number="33"></p>
<p>The definitions of the types of documents and the corresponding <code>ttm:role</code> values are:
<ul>
<li><dfn>Original Language Dialogue List</dfn>: When the <code>ttm:role</code> value is <code>x-DUBBING_ORIGINAL_DIALOGUE_LIST</code>, the document represents a literal transcription of the dialogues and on-screen text in their original spoken/written language(s).
<aside class="example">If a movie contains dialogues in English and Hebrew, the <a>Original Language Dialogue List</a> will contain some <a>Events</a> in English and some in Hebrew. None of the events are translated.</aside>
</li>
<li><dfn>Translated Dialogue List</dfn>: When the <code>ttm:role</code> value is <code>x-DUBBING_TRANSLATED_DIALOGUE_LIST</code>, the document represents a translation of the dialogues or on-screen text in a common language. It is meant to be adapted to produce a <a>Pre-Recording Dub Script</a>. It may contain <a>Events</a> from the <a>Original Language Dialogue List</a> for context, to assist in the adaption process.
<aside class="example">If a movie contains dialogues in English and Hebrew, the French <a>Translated Dialogue List</a> will contain at least the translation in French of all <a>Events</a>. It may still retain text content in Hebrew and English to assist further processing.</aside>
</li>
<li><dfn>Pre-recording Dub Script</dfn>: When the <code>ttm:role</code> value is <code>x-DUBBING_PRE_RECORDING</code>, the document represents the result of the adaptation of a <a>Translated Dialogue List</a> for dubbing, e.g. for better lip-sync. It may also contain <a>Events</a> from the <a>Original Language Dialogue List</a> for context, to assist further processing.</li>
<li><dfn>As-recorded Dub Script</dfn>: When the <code>ttm:role</code> value is <code>x-DUBBING_AS_RECORDED</code>, the document represents a transcription of the output of the dubbing workflow. It may also contain <a>Events</a> from the <a>Original Language Dialogue List</a> for context and quality verifications.</li>
<li><dfn>Audio Description Script</dfn>: When the <code>ttm:role</code> value is <code>x-AUDIO_DESCRIPTION</code>, the document represents text script, times, optional links to audio and mixing instructions for the purpose of producing an audio description audio track.</li>
</ul>
</p>
<pre class="example">
...
<head>
<metadata ttm:role="x-DUBBING_DIALOGUE_LIST"/>
</head>
...
</pre>
<p class="issue" data-number="11"></p>
<p class="issue" data-number="13"></p>
</section>
<section>
<h4>Primary Language</h4>
<p>The <dfn>Primary Language</dfn> represents the default language for the <a>Text</a> content of <a>Events</a>. It is represented in TTML with the following structure and constraints:
<ul>
<li>the <code>xml:lang</code> attribute shall be present on the <code>tt</code> element and its value shall not be empty.</li>
</ul>
</p>
<p class="note">When multiple languages are used in a script, the <a>Primary Language</a> can correspond to the language of the majority of events, to the language being spoken for the longest duration, or to the language arbitrarily chosen by the author.</p>
</section>
<section>
<h4>Events</h4>
<p>The <dfn>Events</dfn> part of the model provides the list of timed text events corresponding to dialogues, on screen text, or descriptions. to the default language for the <a>Text</a> content of <a>Events</a>.</p>
<p>A DAPT script MUST specify an <a>Events</a> list.</p>
</section>
<section>
<h4>Characters</h4>
<p>The <dfn>Characters</dfn> part of the model provides the list of characters referenced in the <a>Events</a>.</p>
<p>Dubbing scripts MUST specify a <a>Characters</a> list.</p>
</section>
<p class="issue" data-number="14"></p>
</section>
<section>
<h3>Character</h3>
<p>A <dfn>Character</dfn> has the following properties.</p>
<section>
<h4>Character Identifier</h4>
<p>Each <a>Character</a> in a Dubbing Script MUST have an <dfn data-lt="Character Identifier">Identifier</dfn>.</p>
</section>
<section>
<h4>Character Name</h4>
<p>Each <a>Character</a> in a Dubbing Script MUST have a <dfn data-lt="Character Name">Name</dfn>. This is the name of the character used in <a>Events</a>.</p>
</section>
<section>
<h4>Talent Name</h4>
<p>Each <a>Character</a> in a Dubbing Script MAY have at most one <dfn data-lt="Character Talent Name">Talent Name</dfn>. This is the name of the actor speaking dialogues for this <a>Character</a>.</p>
</section>
<section>
<h4>Character Style</h4>
<p>Each <a>Character</a> in a Dubbing Script MAY have at most one <dfn data-lt="Character Style">Style</dfn>. This is a set of styles for <a>Events</a> associated with this <a>Character</a>.</p>
<p class="issue" data-number="29"></p>
<p class="issue" data-number="15"></p>
</section>
</section>
<section>
<h3>Event</h3>
<p>An <dfn>Event</dfn> has the following properties.</p>
<section>
<h4>Event Identifier</h4>
<p>Each <a>Event</a> MUST have a unique <dfn>Event Identifier</dfn>.</p>
</section>
<section>
<h4>Event Type</h4>
<p>Each <a>Event</a> in a Dubbing Script MAY have at most one <dfn>Event Type</dfn> used to identify if the <a>Event</a> represents spoken text or on screen text, and in the later case, the type of on-screen text (title, credit, location, ...).</p>
</section>
<section>
<h4>Character Identifier</h4>
<p>Each <a>Event</a> in a Dubbing Script MUST have one or more identifiers of <a>Character</a> involved in this <a>Event</a>.</p>
<p class="note">While typically, an <a>Event</a> corresponds to one single character, there are cases where multiple characters can speak the same text at the same time.</p>
</section>
<section>
<h4>Start</h4>
<p>Each <a>Event</a> MUST have a <dfn>Start</dfn> property.</p>
</section>
<section>
<h4>End</h4>
<p>Each <a>Event</a> MUST have a <dfn>End</dfn> property.</p>
<p class="note">Typically <a>Events</a> do not overlap in time. However, there may be cases where they do, e.g. when different <a>Characters</a> speak different text at the same time.</p>
</section>
<section>
<h4>Text</h4>
<p>Each <a>Event</a> MUST have a <dfn>Text</dfn> property, which provides the main text content for this <a>Event</a>.</p>
<p>It MAY have a <dfn>Text Styles</dfn> property, which provides styles associated with the <a>Text</a> of this <a>Event</a>.</p>
<p class="issue" data-number="15"></p>
<p>It MAY have a <dfn>Text Language</dfn> property. If not present, the <a>Text</a> is assumed to be in the Script <a>Primary Language</a>.</p>
<p class="note">In <a>Original Language Dialogue List</a>, <a>Events</a> may be in different languages.</p>
</section>
<section>
<h4>Contextual Text</h4>
<p>Each <a>Event</a> MAY have a <dfn>Contextual Text</dfn> property, which is a representation of the <a>Text</a> in a different language. It may be used to assist in the processing of the <a>Text</a>.
<p class="note">For example, when a <a>Pre-Recording Dub Script</a> needs to be adjusted, having this additional text in the original language(s) could be useful.</p>
<p class="issue" data-number="16"></p>
<p class="issue" data-number="21"></p>
<p>It MAY have a <dfn>Contextual Text Styles</dfn> property, which provides styles associated with the <a>Contextual Text</a> of this <a>Event</a>.</p>
<p class="issue" data-number="15"></p>
<p>It MAY have a <dfn>Contextual Text Language</dfn> property, representing the language of the <a>Contextual Text</a> content.</p>
</section>
<section>
<h4>Event Description</h4>
<p>Each <a>Event</a> MAY have an <dfn>Event Description</dfn> property, as a human-readable description of the <a>Event</a>. </p>
<p class="issue" data-number="30"></p>
<p class="note">It does not have to be unique for this <a>Event</a>. It may be used to identify in a human-readable way one or more <a>Events</a> that need to be processed together, e.g. in a batch recording.</p>
<p class="issue" data-number="20"></p>
</section>
<section>
<h4>On Screen</h4>
<p>Each <a>Event</a> MAY have a <dfn>On Screen</dfn> property, which is an annotation indicating the position of the <a>character</a> during the <a>Event</a>:
<ul>
<li>ON - the <a>character</a> is on screen for the entire duration</li>
<li>OFF - the <a>character</a> is off screen for the entire duration</li>
<li>ON_OFF - the <a>character</a> starts on screen, but goes off screen at some point</li>
<li>OFF_ON - the <a>character</a> starts off screen, but goes on screen at some point</li>
</ul>as a human-readable description of the <a>Event</a>.
</p>
</section>
</section>
</section>
<section id="ttml-format">
<h4>TTML Format</h4>
<p>This section defines the TTML format based on the data model defined in [[[#data-model]]].</p>
<p class="issue" data-number="25"></p>
<section>
<h4>Identification and Profile Signaling</h4>
<p>TTML documents representing DAPT Scripts shall be compliant with the Text Profile defined in [[!ttml-imsc1.1]] with the additional constraints defined in this specification.</p>
<p>TTML documents representing DAPT Scripts shall specify a <code>ttp:contentProfiles</code> attribute on the <code>tt</code> element with one value equal to <code>http://www.w3.org/ns/ttml/profile/dapt</code>. Other values such as the text profile designator [[!ttml-imsc1.1]] of may be present.</p>
</section>
<section id="profile-resolution-semantics">
<h3>Profile Resolution Semantics</h3>
<p>
For the purpose of content processing, the determination of the resolved profile SHOULD take into account both the signaled profile, as defined in <a href="#profile-signaling-section"></a>, and profile metadata, as designated by either (or both) the Document Interchange Context or (and) the Document Processing Context, which MAY entail inspecting document content.
</p>
<p>
If the resolved profile is not the Profile supported by the Processor but is feasibly interoperable with the Profile, then the resolved profile is the Profile.
If the resolved profile is undetermined or not supported by the Processor, then the Processor SHOULD nevertheless process the Document Instance using the Profile; otherwise, processing MAY be aborted.
If the resolved profile is not the proposed Profile, processing is outside the scope of this specification.
</p>
<p>
If the resolved profile is the profile supported by the Processor, then the Processor SHOULD process the Document Instance according to the Profile.
</p>
</section>
</section>
<section id="profile-constraints">
<h2>Constraints</h2>
<section id="Document Encoding">
<h3>Document Encoding</h3>
<p>
A Document Instance MUST use UTF-8 character encoding as specified in [[UNICODE]].
</p>
</section>
<section id="foreign-elements-and-attributes">
<h3>Foreign Element and Attributes</h3>
<p>
A <a>Document Instance</a> MAY contain elements and attributes that are neither specifically permitted nor forbidden by a profile.
</p>
<p class ="note">
<a>Document Instances</a> remain subject to the content conformance requirements specified at Section 3.1 of [[TTML2]].
In particular, a Document Instance can contain elements and attributes not in any TT namespace, i.e. in foreign namespaces, since such elements and attributes are pruned by the algorithm at Section 4 of [[TTML2]] prior to evaluating content conformance.
</p>
<p class ="note">
For validation purposes it is good practice to define and use a content specification for all foreign namespace elements and attributes used within a Document Instance.
</p>
<p>
A <a>transformation processor</a> SHOULD preserve such elements or attributes whenever possible.
</p>
<p class="ednote">Do we need to say that a presentation processor may ignore foreign vocab?</p>
</section>
<section id="namespaces">
<h3>Namespaces</h3>
<p>
The following namespaces (see [[xml-names]]) are used in this specification:
</p>
<table class="simple">
<thead>
<tr>
<th>Name</th>
<th>Prefix</th>
<th>Value</th>
<th>Defining Specification</th>
</tr>
</thead>
<tbody>
<tr>
<td>XML</td>
<td><code>xml</code></td>
<td><code>http://www.w3.org/XML/1998/namespace</code></td>
<td>[[xml-names]]</td>
</tr>
<tr>
<td>TT</td>
<td><code>tt</code></td>
<td><code>http://www.w3.org/ns/ttml</code></td>
<td>[[TTML2]]</td>
</tr>
<tr>
<td>TT Parameter</td>
<td><code>ttp</code></td>
<td><code>http://www.w3.org/ns/ttml#parameter</code></td>
<td>[[TTML2]]</td>
</tr>
<tr>
<td>TT Feature</td>
<td><em>none</em></td>
<td><code>http://www.w3.org/ns/ttml/feature/</code></td>
<td>[[TTML2]]</td>
</tr>
<tr>
<td>TT Audio Style</td>
<td><em>tta:</em></td>
<td><code>http://www.w3.org/ns/ttml#audio</code></td>
<td>[[TTML2]]</td>
</tr>
<tr>
<td>DAPT Metadata</td>
<td><code>daptm</code></td>
<td><code>http://www.w3.org/ns/ttml/profile/dapt#metadata</code></td>
<td><em>This specification</em></td>
</tr>
</tbody>
</table>
<p>
The namespace prefix values defined above are for convenience and Document Instances MAY use any prefix value that conforms to [[xml-names]].
</p>
<p>
The namespaces defined by this proposal document are mutable [[namespaceState]]; all undefined names in these namespaces are reserved for future standardization by the W3C.
</p>
</section>
<section id="related-video-object-section">
<h3>Related Video Object</h3>
<p>
A <a>Document Instance</a> MAY be associated with a <a>Related Video Object</a>.
</p>
<p class="note">
While this specification contains specific provisions when a <a>Document Instance</a> is associated with a <a>Related Video Object</a>, it does not prevent the use of a Document Instance with other kinds of Related Media Object, e.g. an audio only object.
</p>
</section>
<section id="synchronization-section">
<h3>Synchronization</h3>
<p class="ednote">Check if we need this, and if we do, rework for audio - e.g. relate to audio sample, or other quantisation units?</p>
<p>
Each intermediate synchronic document of the Document Instance is intended to be rendered starting on a specific frame and removed by a specific frame of the Related Video Object.
</p>
<p class="note">In the context of this specification rendering could be visual presentation of text,
for example to show an actor what words to speak, or could be audible playback of an audio resource,
or could be physical or haptic, such as a Braille display.
</p>
<p>
When mapping a media time expression M to a frame F of a Related Video Object (or Related Media Object), e.g. for the purpose of mixing audio sources signalled by a Document Instance into the main program audio of the <a>Related Video Object</a>, the presentation processor MUST map M to the frame F with the presentation time that is the closest to, but not less, than M.
</p>
<p>
EXAMPLE 1
A media time expression of 00:00:05.1 corresponds to frame ceiling( 5.1 × ( 1000 / 1001 × 30) ) = 153 of a <a>Related Video Object</a> with a frame rate of 1000 / 1001 × 30 ≈ 29.97.
</p>
<p class="note">
In typical scenario, the same video program (the <a>Related Video Object</a>) will be used for Document Instance authoring, delivery and user playback.
The mapping from media time expression to <a>Related Video Object</a> above allows the author to precisely associate <a>audio description</a> content with video frames, e.g. around existing audio dialogue and sound effects.
In circumstances where the video program is downsampled during delivery, the application can specify that, at playback, the relative video object be considered the delivered video program upsampled to is original rate, thereby allowing audio content to be presented at the same temporal locations it was authored.
</p>
</section>
<section id="profile-signaling-section">
<h3>Profile Signaling</h3>
<p>TTML documents representing DAPT Scripts MUST specify a <code>ttp:contentProfiles</code> attribute
on the <code>tt</code> element with one value equal to the designator of the <a>DAPT 1.0</a> profile
to which the Document Instance conforms.
Other values MAY be present to declare conformance to other profiles of [[TTML2]].</p>
<section id="profile-designator">
<h4>Profile Designator</h4>
<p>This profile is associated with the following profile designator:</p>
<table class="simple">
<thead>
<tr>
<th>Profile Name</th>
<th>Profile Designator</th>
</tr>
</thead>
<tbody>
<tr>
<td><dfn data-dfn-type="dfn" id="dfn-dapt-1-0">DAPT 1.0</dfn></td>
<td><code>http://www.w3.org/ns/ttml/profile/dapt</code></td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="features-section">
<h3>Features</h3>
<p>
See <a href="#conformance" class="sec-ref">Conformance</a> for a definition of <em>permitted</em>, <em>prohibited</em> and <em>optional</em>.
</p>
<p class="ednote">Intent is to make it as easy as possible to transform a Document Instance into
IMSC, so we need to check that there are no IMSC permitted features that we prohibit, or if there
are, then we can explain the reason.
</p>
<p class="ednote">Editorial task: go through this list of features and check the disposition of each. IMSC-only features should be optional.</p>
<table class="simple">
<tbody>
<tr>
<th style="width:20%" style="text-align:center">Feature</th>
<th style="width:10%" style="text-align:center">Disposition</th>
<th style="text-align:center">Additional provision</th>
</tr>
<tr>
<td colspan="3" style="text-align:center"><em>Relative to the TT Feature namespace</em></td>
</tr>
<tr>
<td><code>#animation-version-2</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#audio</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#audio-description</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#audio-speech</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#backgroundColor-block</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#backgroundColor-region</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#cellResolution</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#chunk</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#clockMode</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#clockMode-gps</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#clockMode-local</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#clockMode-utc</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#content</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#contentProfiles</code></td>
<td>required</td>
<td></td>
</tr>
<tr>
<td><code>#core</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#data</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#display-block</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#display-inline</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#display-region</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#display</code></td>
<td>prohibited<p class="ednote">Consider display="none" in relation to AD content</p></td>
<td></td>
</tr>
<tr>
<td><code>#dropMode</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#dropMode-dropNTSC</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#dropMode-dropPAL</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#dropMode-nonDrop</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#embedded-audio</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#embedded-data</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#extent-root</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#extent</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#frameRate</code></td>
<td>permitted</td>
<td>
If the <a href="#dfn-document-instance" class="internalDFN" data-link-type="dfn">Document Instance</a> includes any time expression that uses the <code>frames</code> term or any
offset time expression that uses the <code>f</code> metric, the <code>ttp:frameRate</code> attribute <em class="rfc2119" title="MUST">MUST</em> be present
on the <code>tt</code> element.
</td>
</tr>
<tr>
<td><code>#frameRateMultiplier</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#gain</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#layout</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#length-cell</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#length-integer</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#length-negative</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#length-percentage</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#length-pixel</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#length-positive</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#length-real</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#length</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#markerMode</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#markerMode-continuous</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#markerMode-discontinuous</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#metadata</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#opacity</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#origin</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#overflow</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#overflow-visible</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#pan</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#pitch</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#pixelAspectRatio</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#presentation</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#processorProfiles</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td id="profile-constraints"><code>#profile</code></td>
<td>permitted</td>
<td>
See <a href="#profile-signaling-section" class="sec-ref"></a>.
</td>
</tr>
<tr>
<td><code>#region-timing</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#resources</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#showBackground</code></td>
<td>prohibited</td>
<td></td>
</tr>
<tr>
<td><code>#source</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#speak</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#speech</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#structure</code></td>
<td>permitted</td>
<td></td>
</tr>
<tr>
<td><code>#styling</code></td>
<td>permitted</td>