-
Notifications
You must be signed in to change notification settings - Fork 12
/
index.html
733 lines (721 loc) · 32 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
<!DOCTYPE html>
<html lang="en">
<head>
<meta content="text/html; charset=utf-8" http-equiv="content-type">
<title>TTML Media Type Definition and Profile Registry</title>
<script src="https://www.w3.org/Tools/respec/respec-w3c" async="" class="remove"></script>
<script class="remove">
var respecConfig = {
// specification status (e.g. WD, LCWD, WG-NOTE, etc.). If in doubt use ED.
specStatus: "ED",
//specStatus: "WG-NOTE",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "ttml-profile-registry",
// if there a publicly available Editor's Draft, this is the link
edDraftURI: "https://w3c.github.io/tt-profile-registry/",
// editors, add as many as you like
// only "name" is required
editors: [
{
name: "Mike Dolan",
company: "TBT",
w3cid: "34379"
},
{
name: "Nigel Megitt",
company: "British Broadcasting Corporation",
w3cid: "64750"
}
],
formerEditors: [
{
name: "Glenn Adams",
company: "Skynav",
w3cid: "34030"
}
],
// name of the WG
group: "wg/timed-text",
// name (without the @w3c.org) of the public mailing to which comments are due
wgPublicList: "public-tt",
subjectPrefix: "[TTML-Profile-Registry]",
otherLinks: [{
key: 'Publication history',
data: [{
value: 'https://www.w3.org/standards/history/ttml-profile-registry',
href: 'https://www.w3.org/standards/history/ttml-profile-registry'
}]
}, {
key: 'Repository',
data: [{
value: 'We are on Github.',
href: 'https://github.com/w3c/tt-profile-registry/'
}, {
value: 'File a bug.',
href: 'https://github.com/w3c/tt-profile-registry/issues'
}, {
value: 'Commit history.',
href: 'https://github.com/w3c/tt-profile-registry/commits/gh-pages/index.html'
}]
}],
localBiblio: {
"IMSC1.0.1": {
aliasOf: "ttml-imsc1.0.1-20180424"
},
"IMSC1.1": {
aliasOf: "ttml-imsc1.1-20181108"
},
"IMSC1.2": {
aliasOf: "ttml-imsc1.2-20200804"
},
"TTML1-1e": {
aliasOf: "ttml1-20101118"
},
"TTML1-2e": {
aliasOf: "ttml1-20130924"
},
"TTML1-3e": {
aliasOf: "ttml1-20181108"
},
"TTML1-SDP-US": {
aliasOf: "ttml10-sdp-us-20130205"
},
"TTML2-1e": {
aliasOf: "ttml2-20181108"
},
"UV-DMedia": {
title: "Common File Format & Media Formats Specification version 2.2",
href: "http://uvcentral.com/sites/default/files/files/PublicSpecs/CFFMediaFormat-2_2.pdf",
publisher: "DECE",
date: "31 July 2015"
},
"NetflixIMSC1.1TextProfile":{
title: "Netflix IMSC 1.1 Text Profile",
href: "https://www.netflix.com/ns/imsc1.1/text/1",
publisher: "Netflix",
date: "24 November 2020"
}
}
// !!!! IMPORTANT !!!! MAKE THE ABOVE BLINK IN YOUR HEAD
};
</script>
<style>
table.coldividers td + td { border-left:1px solid gray; text-align: center;}
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 }
</style>
</head>
<body>
<section id="abstract">
<h2>Abstract</h2>
<p>This document defines
the <a href="#mediatype"><code>application/ttml+xml</code></a> media
type and provides a registry of compact (short) identifiers that may be
used to identify TTML processor profiles. A processor profile specifies
a set of capabilities that a processor must support in order to process
a document, where this profile may be defined in a specification
document, in
a <a href="https://www.w3.org/TR/ttml1/#vocabulary-profiles">TTML
Profile Definition Document</a>, inline within a TTML Document Instance,
or by using a combination of these methods. This document only
considers the first two of these methods since the third method (the use
of inline profile definitions) is not considered to be an identifiable,
shared profile definition, but rather, a private profile definition
scoped to the document instance in which it is defined.</p>
</section> <!-- abstract -->
<section id="sotd"></section> <!-- sotd -->
<section id="purpose" class="informative">
<h2>Purpose</h2>
<p>This document serves two purposes: (1) to define the Media Type
<code>application/ttml+xml</code>, and (2) to define a registry
of compact (short) identifiers of TTML processor profiles.</p>
<p>As a registry, this document is intended to provide a central location for enumerating
identified TTML processor profiles, or, more strictly speaking, TTML
decoder/processors, where each entry in the registry identifies a
particular profile which is understood to implement a processor capable
of satisfying the constraints of a defined TTML processor profile that
takes the form of a TTML Profile Definition Document. By utilizing a
common registry, it is possible to avoid name collisions among different
profile defining fora.</p>
<div class="note">
<p>In the context of this registry, the term <i>profile</i>
means <i>processor profile</i>. It explicitly does not
mean <i>content profile</i>. That is, nothing about the use
of the <code>profile</code>
or <code>codecs</code> parameters described here is
intended to be used to identify or make claims about whether
a TTML resource conforms with a TTML Content Profile or any
type of TTML Profile that may be interpreted in whole or in
part as making statements about the conformance of a TTML
resource or the features of TTML (or other external
specifications) actually used in the resource.</p>
</div>
<p>Applications using the entries in this registry are encouraged to support
the <code>codecs</code> parameter.</p>
<p>The <code>codecs</code> parameter value syntax is defined as
<code>codecs-parameter-value</code> as follows,
expressed using the syntax expression conventions defined by §2.3 of [[TTML2-1e]].</p>
<table class="syntax">
<tbody>
<tr>
<td>
<div class="exampleInner">
<pre class="nohighlight">
identifier
: element // element defined by [RFC6381]
// where "+", "|" and "." are prohibited characters
// ("." is reserved as a hierarchy delimiter in [RFC6381])
and-group
: identifier ["+" identifier]* // no linear white-space is implied or permitted
// between each token
codecs-parameter-value
: and-group ["|" and-group]* // no linear white-space is implied or permitted
// between each token
</pre>
</div>
</td>
</tr>
</tbody>
</table>
<p>The <code>codecs</code> parameter may
employ either (or both) of two combination operators, <code>+</code> (AND) and <code>|</code> (OR), which may be
used to specify, respectively, that all processor profiles apply
(simultaneously) or that any processor profile of a list of profiles may
apply individually. If both operators are used, then
the <code>+</code> operator has precedence.</p>
<p class="note">The <code>+</code> and <code>|</code> operators
are intended to have semantics equivalent to
the <code>all(...)</code> and the <code>any(...)</code>
function syntax supported by
the <code>ttp:processorProfiles</code> attribute as defined by
[[TTML2-1e]], §6.2.8. Take note, however, that the
combined use of both <code>all(...)</code> and <code>any(...)</code> in
a <code>ttp:processorProfiles</code> attribute value
expression is not directly supported by [[TTML2-1e]], and,
therefore, an application that encounters a combination of
both operators in a <code>codecs</code> value expression will
need to process such combination semantics as a higher level
protocol outside the scope of [[TTML2-1e]] semantics.</p>
<p class="note">The example <code>A+B|C+D|E</code> specifies that a TTML processor that implements
any one of the <code>A+B</code> or <code>C+D</code> or <code>E</code> processor profiles satisfies
the requirements to fetch and begin decode/processing of a TTML
document, where <code>X+Y</code> means that both <code>X</code> and <code>Y</code> processor profiles must be
supported, and <code>X|Y</code> means that either <code>X</code> or <code>Y</code> processor profile must be
supported.</p>
<p class="note">For example,
the <code>codecs</code> string for specifying either a TTML processor that supports
[[IMSC1.0.1]] Text Profile or one that supports [[EBU-TT-D-1]]
would be `"im1t|etd1"`.
The <code>codecs</code> string for specifying a TTML processor that supports
the union of sets of required features of both
[[IMSC1.0.1]] Text Profile and [[EBU-TT-D-1]]
would be `"im1t+etd1"`.</p>
<p class="note">Another <code>codecs</code> parameter is defined by
[[RFC6381]] for application/mp4 (ISO BMFF) and
extended for TTML by [[iso14496-30]].</p>
<p></p>
</section> <!-- purpose -->
<section id="mediatype" class="normative">
<h2>Media Type Registration</h2>
<p>This section defines the media type "application/ttml+xml",
and, in conformance with
<a href="https://www.ietf.org/rfc/rfc4288.txt">BCP 13</a>
and <a href="http://www.w3.org/2002/06/registering-mediatype.html">W3CRegMedia</a>,
serves as the registration thereof with the Internet Assigned
Numbers Authority (IANA).</p>
<p>This updated definition supersedes the initial registration
information specified in [[!TTML1-1e]], Appendix C, as updated
by [[!TTML1-2e]], Appendix C.</p>
<dl>
<dt class="label">Type name:</dt>
<dd>
<p>application</p>
</dd>
<dt class="label">Subtype name:</dt>
<dd>
<p>ttml+xml</p>
</dd>
<dt class="label">Required parameters:</dt>
<dd>
<p>None.</p>
</dd>
<dt class="label">Optional parameters:</dt>
<dd>
<dl>
<dt class="label">charset</dt>
<dd>
<p>If specified, the <code>charset</code> parameter must match the XML
encoding declaration, or if absent, the actual encoding. See also Encoding
Considerations below.</p>
</dd>
<dt class="label">profile</dt>
<dd>
<p>The document profile of a TTMLDocument Instance may be specified using
an optional <code>profile</code> parameter, which, if specified, the value
of which must adhere to the syntax and semantics of
<code>ttp:profile</code> parameter defined by <a href=
"https://www.w3.org/TR/2013/REC-ttml1-20130924/#parameter-attribute-profile">TTML 1.0 Second Edition, Section 6.2.8 ttp:profile</a> of the published specification.</p>
</dd>
<dt class="label">codecs</dt>
<dd>
<p>The optional <code>codecs</code> parameter provides a
short form version of the <code>profile</code>
parameter with multiple-profile combinatorial
capability. If a short (4-character) form of a profile
is registered in
the <a href="https://www.w3.org/TR/ttml-profile-registry/">TTML
Profile Registry</a>, it is recommended that
this <code>codecs</code> parameter be used and not
the <code>profile</code> parameter. The nominal value
of this parameter is a single 4 character code from
the registry.</p>
<p>Additionally, applications using the entries in the
registry are encouraged to adopt the following
combination syntax:</p>
<p>Employ two combination operators, '+' (AND) and '|'
(OR), which may be used to specify, respectively, that
multiple processor profiles apply (simultaneously) or
that any processor profile of a list of profiles may
apply individually. If both operators are used in a
codecs value, then the '+' operator has precedence.</p>
<p>The example: "A+B|C+D|E" states that a TTML processor
that implements any one of A+B or C+D or E processor
profiles satisfies, at first order, the requirements
to fetch and begin decode/processing of a TTML
document, where X+Y means that both X and Y processor
profiles must be supported, and X|Y means that either
X or Y processor profile must be supported.</p>
</dd>
</dl>
</dd>
<dt class="label">Encoding considerations:</dt>
<dd>
<p>Same for application/xml, except constrained to either UTF-8 or UTF-16. See
<a href="https://tools.ietf.org/html/rfc7303">IETF RFC 7303, XML Media Types, Section 3.2</a>. For the purpose of
filling out the IANA Application for Media Type
(http://www.iana.org/cgi-bin/mediatypes.pl), the value <em>binary</em>
applies.</p>
</dd>
<dt class="label">Security considerations:</dt>
<dd>
<p>As with other XML types and as noted
in <a href="https://tools.ietf.org/html/rfc7303">IETF RFC
7303, XML Media Types, Section 10</a>, repeated expansion
of maliciously constructed XML entities can be used to
consume large amounts of memory, which may cause XML
processors in constrained environments to fail.</p>
<p>In addition, because of the extensibility features for
TTML and of XML in general, it is possible that
"application/ttml+xml" may describe content that has
security implications beyond those described
here. However, TTML does not provide for any sort of
active or executable content, and if the processor follows
only the normative semantics of the published
specification, this content will be outside TTML
namespaces and may be ignored. Only in the case where the
processor recognizes and processes the additional content,
or where further processing of that content is dispatched
to other processors, would security issues potentially
arise. And in that case, they would fall outside the
domain of this registration document.</p>
<p>Although not prohibited, there are no expectations that
XML signatures or encryption would normally be
employed.</p>
</dd>
<dt class="label">Interoperability considerations:</dt>
<dd>
<p>The published specification describes processing
semantics that dictate behavior that must be followed when
dealing with, among other things, unrecognized elements
and attributes, both in TTML namespaces and in other
namespaces.</p>
<p>Because TTML is extensible, conformant
"application/ttml+xml" processors may expect (and enforce)
that content received is well-formed XML, but it cannot be
guaranteed that the content is valid to a particular DTD
or Schema or that the processor will recognize all of the
elements and attributes in the document.</p>
</dd>
<dt class="label">Published specification:</dt>
<dd>
<p>This media type registration is extracted from
the <a href="https://www.w3.org/TR/ttml-profile-registry/">TTML
Profile Registry</a>.</p>
</dd>
<dt class="label">Applications that use this media type:</dt>
<dd>
<p>TTML is used in the television industry for the purpose
of authoring, transcoding and exchanging timed text
information and for delivering captions, subtitles, and
other metadata for television material repurposed for the
Web or, more generally, the Internet.</p>
<p>There is partial and full support of TTML in components
used by several Web browsers plugins, and in a number of
caption authoring tools.</p>
</dd>
<dt class="label">Additional information:</dt>
<dd>
<dl>
<dt class="label">Magic number(s):</dt>
<dt class="label">File extension(s):</dt>
<dd>
<p>.ttml</p>
</dd>
<dt class="label">Macintosh file type code(s):</dt>
<dd>
<p>"TTML"</p>
</dd>
<dt class="label">Fragment identifiers:</dt>
<dd>
<p>For documents labeled as application/ttml+xml, the
fragment identifier notation is intended to be used
with xml:id attributes, as described in section 7.2.1
of the <a href="https://www.w3.org/TR/ttml1/">Timed
Text Markup Language 1 (TTML1)</a> specification.</p>
</dd>
</dl>
</dd>
<dt class="label">Person & email address to contact for
further information:</dt>
<dd>
<p>Timed Text Working Group (public-tt@w3.org)</p>
</dd>
<dt class="label">Intended usage:</dt>
<dd>
<p>COMMON</p>
</dd>
<dt class="label">Restrictions on usage:</dt>
<dd>
<p>None</p>
</dd>
<dt class="label">Author:</dt>
<dd>
<p>The published specification is a work product of the
World Wide Web Consortium's Timed Text (TT) Working
Group.</p>
</dd>
<dt class="label">Change controller:</dt>
<dd>
<p>The W3C has change control over this specification.</p>
</dd>
</dl>
</section> <!-- mediatype -->
<section id="Registration_Entry_Requirements_and_Update_Process" class="normative">
<h2>Registration Entry Requirements and Update Process</h2>
<ol>
<li><p>Each entry must include a unique identification, where the
scope of uniqueness is the set of identifiers defined in
this registry. An identifier must conform with
the <code>element</code> non-terminal of [[!RFC6381]]
and, furthermore, may not contain any of the characters in the regular
expression character class <code>[+|.]</code>.</p>
<div class="note">
<p>As a consequence of the above syntactic constraints,
the value space of the <code>codecs</code> parameter described
in <a href="#mediatype"></a> above is a syntactic subset of the
definition of the <code>codecs</code> parameter
defined by [[RFC6381]].</p>
</div>
</li>
<li>Each entry must include an absolute URI that serves as the
TTML Profile Designator that identifies the processor
profile.</li>
<li>Each entry should include a link that references a TTML
Profile Definition Document that formally specifies the
processor profile using TTML profile definition
vocabulary.</li>
<li>Each entry should include a link that references a public
available specification (PAS) that defines the identified
processor profile.</li>
<li>Each entry must include contact information of the
requestor.</li>
</ol>
<p>An update to this registry is an addition, change or deletion
of an entry. Any person can request an update to this registry
by email notice to the chairman of the Timed Text Working
Group who will place it on an upcoming meeting agenda and
notify the requestor. Consideration and disposition of the
request is by consensus of the W3C Timed Text Working
Group. The Chair will then notify the requestor of the outcome
and update the registry accordingly. Although profiles can be
deleted, there is no intent to re-use deleted profile
values. That is, the intent is that profile entries are
"stable".</p>
</section> <!-- Registration_Entry_Requirements_and_Update_Process -->
<section id="registry" class="normative">
<h2>Registry</h2>
<p>This section is the registry of short form profile
identifiers. The first sub-section details how such
identifiers should be dereferenced to profile designators, the
specifications that define those profiles, and the contact
organisation for each profile. The second sub-section
describes the mechanism used by each profile to permit
identification of the profile of a TTML Document Instance by
inspection of that document.</p>
<section id="registry-profile-designator-specifications">
<h2>Profile designator and specifications</h2>
<p>The following table defines the Profile Designator for each
short form Profile Identifier in this Registry, alongside
the public specification document in which the profile is
defined, and the relevant contact organisation. Entries are
ordered alphabetically according to the short profile
identifier.</p>
<table class="simple" style="width:100%; border: 2px solid black">
<thead>
</thead>
<tbody>
<tr>
<th style="width: 2%; text-align:left"> Profile Identifier
</th>
<th style="width: 28%; text-align:left"> Profile Designator
</th>
<th style="width: 5%; text-align:left"> Public Specification(s)
</th>
<th style="width: 2%; text-align:left"> Requestor Contact
</th>
</tr>
<tr>
<td> <code>cfi1</code>
</td>
<td> <code>http://www.decellc.org/profile/cff-tt-image-1.1</code>
</td>
<td> [[!UV-DMedia]]
</td>
<td> <a rel="nofollow" class="external text" href="https://www.myuv.com/en/us/ultraviolet-business">DECE</a>
</td>
</tr>
<tr>
<td> <code>cft1</code>
</td>
<td> <code>http://www.decellc.org/profile/cff-tt-text-1.1</code>
</td>
<td> [[!UV-DMedia]]
</td>
<td> <a rel="nofollow" class="external text" href="https://www.myuv.com/en/us/ultraviolet-business">DECE</a>
</td>
</tr>
<tr>
<td> <code>ede1</code> </td>
<td> <code>urn:IRT:ebu-tt-basic-de:2013-07</code> </td>
<td> <a rel="nofollow" class="external text" href="https://www.irt.de/en/publications/technical-guidelines.html">IRT
Technical Guidelines</a> </td>
<td> <a rel="nofollow" class="external text" href="https://www.irt.de/">IRT</a>
</td>
</tr>
<tr>
<td> <code>etd1</code>
</td>
<td> <code>urn:ebu:tt:distribution:2014-01</code>
</td>
<td> [[!EBU-TT-D-1]]
</td>
<td> <a rel="nofollow" class="external text" href="https://tech.ebu.ch/subtitling">EBU</a>
</td>
</tr>
<tr>
<td> <code>etd2</code>
</td>
<td> <code>urn:ebu:tt:distribution:2018-04</code>
</td>
<td> [[!EBU-TT-D-1-0-1]]
</td>
<td> <a rel="nofollow" class="external text" href="https://tech.ebu.ch/subtitling">EBU</a>
</td>
</tr>
<tr>
<td> <code>etl1</code>
</td>
<td> <code>urn:ebu:tt:live:2017-05</code>
</td>
<td> [[!EBU-TT-Live-1-0]]
</td>
<td> <a rel="nofollow" class="external text" href="https://tech.ebu.ch/subtitling">EBU</a>
</td>
</tr>
<tr>
<td> <code>etx1</code>
</td>
<td> <code>urn:ebu:tt:exchange:2012-07</code>
</td>
<td> [[!EBU-TT-1-0]]
</td>
<td> <a rel="nofollow" class="external text" href="https://tech.ebu.ch/subtitling">EBU</a>
</td>
</tr>
<tr>
<td> <code>etx2</code>
</td>
<td> <code>urn:ebu:tt:exchange:2015-09</code>
</td>
<td> [[!EBU-TT-1-1]]
</td>
<td> <a rel="nofollow" class="external text" href="https://tech.ebu.ch/subtitling">EBU</a>
</td>
</tr>
<tr>
<td> <code>etx3</code>
</td>
<td> <code>urn:ebu:tt:exchange:2017-05</code>
</td>
<td> [[!EBU-TT-1-2]]
</td>
<td> <a rel="nofollow" class="external text" href="https://tech.ebu.ch/subtitling">EBU</a>
</td>
</tr>
<tr>
<td> <code>im1i</code>
</td>
<td> <code>http://www.w3.org/ns/ttml/profile/imsc1/image</code>
</td>
<td> [[!IMSC1.0.1]]
</td>
<td> <a rel="nofollow" class="external text" href="http://www.w3.org/AudioVideo/TT/">TTWG</a>
</td>
</tr>
<tr>
<td> <code>im1t</code>
</td>
<td> <code>http://www.w3.org/ns/ttml/profile/imsc1/text</code>
</td>
<td> [[!IMSC1.0.1]]
</td>
<td> <a rel="nofollow" class="external text" href="http://www.w3.org/AudioVideo/TT/">TTWG</a>
</td>
</tr>
<tr>
<td> <code>im2i</code>
</td>
<td> <code>http://www.w3.org/ns/ttml/profile/imsc1.1/image</code>
</td>
<td> [[!IMSC1.1]] [[!IMSC1.2]]
</td>
<td> <a rel="nofollow" class="external text" href="http://www.w3.org/AudioVideo/TT/">TTWG</a>
</td>
</tr>
<tr>
<td> <code>im2t</code>
</td>
<td> <code>http://www.w3.org/ns/ttml/profile/imsc1.1/text</code>
</td>
<td> [[!IMSC1.1]]
</td>
<td> <a rel="nofollow" class="external text" href="http://www.w3.org/AudioVideo/TT/">TTWG</a>
</td>
</tr>
<tr>
<td> <code>im3t</code>
</td>
<td> <code>http://www.w3.org/ns/ttml/profile/imsc1.2/text</code>
</td>
<td> [[!IMSC1.2]]
</td>
<td> <a rel="nofollow" class="external text" href="http://www.w3.org/AudioVideo/TT/">TTWG</a>
</td>
</tr>
<tr>
<td> <code>nst1</code>
</td>
<td> <code>https://www.netflix.com/ns/imsc1.1/text/1</code>
</td>
<td> [[!NetflixIMSC1.1TextProfile]]
</td>
<td> <a rel="nofollow" class="external text" href="http://www.netflix.com">Netflix</a>
</td>
</tr>
<tr>
<td> <code>rtp1</code>
</td>
<td> <code>urn:ietf:rfc:8759#processor</code>
</td>
<td> [[!RFC8759]]
</td>
<td> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/wg/avtcore/about/">IETF (avtcore)</a>
</td>
</tr>
<tr>
<td> <code>tt1f</code>
</td>
<td> <code>http://www.w3.org/ns/ttml/profile/dfxp-full</code>
</td>
<td> [[!TTML1-3e]]
</td>
<td> <a rel="nofollow" class="external text" href="http://www.w3.org/AudioVideo/TT/">TTWG</a>
</td>
</tr>
<tr>
<td> <code>tt1p</code>
</td>
<td> <code>http://www.w3.org/ns/ttml/profile/dfxp-presentation</code>
</td>
<td> [[!TTML1-3e]]
</td>
<td> <a rel="nofollow" class="external text" href="http://www.w3.org/AudioVideo/TT/">TTWG</a>
</td>
</tr>
<tr>
<td> <code>tt1s</code>
</td>
<td> <code>http://www.w3.org/ns/ttml/profile/sdp-us</code>
</td>
<td> [[!TTML1-SDP-US]]
</td>
<td> <a rel="nofollow" class="external text" href="http://www.w3.org/AudioVideo/TT/">TTWG</a>
</td>
</tr>
<tr>
<td> <code>tt1t</code>
</td>
<td> <code>http://www.w3.org/ns/ttml/profile/dfxp-transformation</code>
</td>
<td> [[!TTML1-3e]]
</td>
<td> <a rel="nofollow" class="external text" href="http://www.w3.org/AudioVideo/TT/">TTWG</a>
</td>
</tr>
<tr>
<td> <code>tt2f</code>
</td>
<td> <code>http://www.w3.org/ns/ttml/profile/ttml2-full</code>
</td>
<td> [[!TTML2-1e]]
</td>
<td> <a rel="nofollow" class="external text" href="http://www.w3.org/AudioVideo/TT/">TTWG</a>
</td>
</tr>
<tr>
<td> <code>tt2p</code>
</td>
<td> <code>http://www.w3.org/ns/ttml/profile/ttml2-presentation</code>
</td>
<td> [[!TTML2-1e]]
</td>
<td> <a rel="nofollow" class="external text" href="http://www.w3.org/AudioVideo/TT/">TTWG</a>
</td>
</tr>
<tr>
<td> <code>tt2t</code>
</td>
<td> <code>http://www.w3.org/ns/ttml/profile/ttml2-transformation</code>
</td>
<td> [[!TTML2-1e]]
</td>
<td> <a rel="nofollow" class="external text" href="http://www.w3.org/AudioVideo/TT/">TTWG</a>
</td>
</tr>
</tbody>
</table>
</section> <!-- registry-profile-designator-specifications -->
</section> <!-- registry -->
</body>
</html>