/
fdd000568.xml
764 lines (762 loc) · 49.5 KB
/
fdd000568.xml
1
<?xml version="1.0" encoding="UTF-8"?><fdd:FDD id="fdd000568" titleName="Timed Text Markup Language Version 1 (TTML1)" shortName="TTML1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:fdd="http://www.loc.gov/preservation/digital/formats/schemas/fdd/v1" xsi:schemaLocation="http://www.loc.gov/preservation/digital/formats/schemas/fdd/v1 http://www.loc.gov/preservation/digital/formats/schemas/fdd/v1/fdd-v1-2.xsd"> <fdd:properties> <fdd:gdfrGenreSelection> <fdd:gdfrGenre>text</fdd:gdfrGenre> </fdd:gdfrGenreSelection> <fdd:formatCategories> <fdd:category>file-format</fdd:category> </fdd:formatCategories> <fdd:gdfrConstraint>structured</fdd:gdfrConstraint> <fdd:updates> <fdd:date>2023-04-07</fdd:date> </fdd:updates> <fdd:draftStatus>Preliminary</fdd:draftStatus> </fdd:properties> <fdd:identificationAndDescription> <fdd:fullName>Timed Text Markup Language Version 1 (TTML1)</fdd:fullName> <fdd:keywords> <fdd:keyword>accessibility formats</fdd:keyword> <fdd:keyword>subtitle formats</fdd:keyword> <fdd:keyword>caption formats</fdd:keyword> </fdd:keywords> <fdd:description> <p>Timed Text Markup Language Version 1 (TTML1) is an XML-based format for the interchange of timed text media, but also can be used as an authoring and distribution format. TTML1 is defined by the <a href="https://www.w3.org/">World Wide Web Consortium (W3C)</a> and is specified in the <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/">Timed Text Markup Language (TTML1) (Third Edition)</a> W3C Recommendation 08 November 2018 (referenced throughout this document).</p> <p>TTML1 is the first version specification of the Timed Text Markup Language (TTML) W3C Recommendation standard, previously referred to as Distribution Format Exchange Profile (DFXP). TTML1 was specified by the Timed Text Working Group (TTWG) and the W3C Recommendation First Edition was released in November 2010. See <a href="#notes">History</a> for more information.</p> <p>Per <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/#intro">TTML1 specification</a>, “In the first edition of this specification, the version number 1.0 was used to refer to this version of TTML. In this second edition, this version number is simplified to 1 as a result of a determination to call the next (future) version 2 instead of 1.1."</p> <p>W3C Timed Text documentation <a href="https://www.w3.org/AudioVideo/TT/docs/TTML-Profiles.html">TTML and Derivative Captions Formats</a> describes Time Text Markup Language (TTML1) as “textual information that may be used directly as a distribution format for online captioning and subtitles, and as interchange format among legacy distribution content formats. It is a superset that encompasses preceding captioning approaches. It supports the semantics of most of the closed caption files.”</p> <p> <b>System Model</b> </p> <p>Per <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/#model">specification</a>, TTML timed text files are designed to be used as a bidirectional interchange format for authoring systems and as a unidirectional interchange format for distribution formats.</p> <p> <b>TTML1 Document Instance:</b> </p> <p>A Document Instance is a defined TTML document, per <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/#terms">specification</a>, “a concrete realization of a TTML document, where the concrete form is specific to the context of reference.”</p> <p> <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/#example">Specification</a> Example Fragment:<br/> <tt xml:lang="" xmlns="http://www.w3.org/ns/ttml"><br/> <br/> <br/> <head><br/> <br/> <metadata/><br/> <styling/><br/> <layout/><br/> <br/> </head><br/> <body/><br/> </tt><br/> </p> <p>Consisting of a <b>tt (root) document element</b> containing:</p> <ul> <li>Header: optional, specifies document level metadata, styling definitions, and layoutdefinitions. <ul> <li>Metadata including document title, description, and copyright information, other arbitrary information from other namespaces, i.e., information used by the processing and rendering tools.</li> <li>Styling – may use style specification definitions that are referenced by layout and content information, i.e., desired look and feel of subtitles/captions.</li> <li>Layout – defines one or regions where content is intended to be presented, i.e., size and location of the caption box.</li> </ul> </li> <li>Body: text content intermixed with references to style, layout, and timing information, the subtitles and/or captions. <ul> <li>Document Instance - organized using block and inline text elements, spatial and temporal relationships are determined by the content hierarchical organization.</li> </ul> </li> </ul> <p>The TTML1 specification defines the <b>TTML Abstract Document Type</b> as a set of constraints that defines a class of XML Information Sets and <b>TTML Content</b> as a profile intended to be used for interchange among distribution systems.</p> <p>TTML1 specification defines the XML namespaces, profiles, and vocabulary (element/attribute catalog).</p> <p>Namespaces specified in the TTML1 specification include TT, TT Parameter, TT Style, TT Metadata, TT Profile, TT Feature, and TT Extension.</p> <p> <b>TTML1 Profiles and Extensions:</b> </p> <p>W3C Timed Text documentation <a href="https://www.w3.org/AudioVideo/TT/docs/TTML-Profiles.html">TTML and Derivative Captions Formats</a> states, “TTML allows extensibility and profiling, therefore multiple caption formats have been developed by the W3C or other external organizations.” Per the <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/#vocabulary-profiles">TTML1 specification</a>, TTML “employs a number of standard, predefined profiles of its vocabulary and associated semantics.”</p> <ul> <li>DFXP Full <ul> <li>Includes all the features of TTML</li> </ul> </li> </ul> <ul> <li>DFXP Presentation <ul> <li>Subset, used for minimum compliance for presentation processing (purpose: layout, format, and render/present TTML content) </li> </ul> </li> </ul> <ul> <li>DFXP Transformation <ul> <li>Subset used for minimum compliance for transformation processing (purpose: transform or rewrite TTML content) </li> </ul> </li> </ul> <ul> <li> <a href="https://www.w3.org/TR/ttml10-sdp-us/">TTML Simple Delivery Profile for Closed Captions (SDP-US)</a>| W3C Working GroupNote 05 February 2013 <ul> <li>Focused on streamlining closed caption delivery on the Internet, supports core TTML1 features</li> <li>Subset to support features required by US Government closed captioning for online presentation</li> </ul> </li> </ul> <ul> <li> <a href="https://www.w3.org/TR/ttml-imsc1.0.1/">TTML Text and Image Profiles for Internet Media Subtitles and Captions 1.0.1 (IMSC1)</a> | W3C Recommendation 24 April 2018, edited in place 27 April 2020 <ul> <li>Pair of TTML1 profiles, text-only profile (superset of SDP-US) and image-only profile</li> <li>Intended to simplify interoperability, consistent rendering and conversion across multiple subtitle/caption formats and applications</li> </ul> </li> </ul> <p>External TTML Profiles (Restricting and/or Extending TTML caption formats):</p> <ul> <li>Society of Motion Picture and Television Engineers Timed Text <a href="https://ieeexplore.ieee.org/document/7291854">(SMPTE-TT) SMPTE ST 2052</a> <ul> <li>Used for representing captions or subtitles</li> <li>Adopted as "safe harbor interchange and delivery format" by the US federal Communications Commission (FCC), January 2012</li> </ul> </li> </ul> <ul> <li>EBU Timed Text (EBU-TT) <a href="https://tech.ebu.ch/docs/tech/tech3350.pdf">EBU Tech 3350 v1.1</a> <ul> <li>Defined for the interchange and archiving of subtitles</li> <li>Developed by the European Broadcasting Union (Europe’s 75 national broadcasters)</li> </ul> </li> </ul> <ul> <li>Common File Format Timed Text <a href="https://www.uvcentral.com/files/CFFMediaFormat-1.1r1.pdf">(CFF-TT)</a> <ul> <li>pair of TTML profiles from <a href="https://www.uvcentral.com/">UltraViolet</a> - Digital Entertainment Content Ecosystem (DECE)</li> <li>Standards/services for online distributions of movies and TV shows</li> </ul> </li> </ul> <p>The TTML1 specification defines the vocabulary, divided into two catalogs, core and extension. The core catalog defines the baseline vocabulary of TTML, in particular TTML Content. The extension catalog is a placeholder for vocabulary extensions defined by TTML.</p> <p>The core catalog baseline vocabulary includes Parameters, Content, Styling, Layout, Timing, Animation, and Metadata.</p> <p>Defined TTML1 elements include set, body, div, p, span, br, tt, head, layout, region, metadata, ttm:actor, ttm:agent, ttm:copyright, ttm:desc, ttm:name, ttm:title, ttp:profile, ttp:features, ttp:feature, ttp:extensions, ttp:extension, styling, and style.</p> <p>Parameters are either essential or of significant importance for interpreting TTML Content.</p> <p>Content specifies the structure and principal content.</p> <p> <b>Uses of TTML1</b> </p> <p> <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/#media-types-registration">TTML1 specification</a> describes the TTML1 format as mainly used in the broadcast industry and by online applications for the purpose of authoring, transcoding, and exchanging timed text information. Typically used when adding captioning/subtitles to video content such as movies, films, or presentations.</p> </fdd:description> <fdd:shortDescription>TTML1 is an XML-based format for the interchange of timed text media, but also can be used as an authoring and distribution format.</fdd:shortDescription> <fdd:productionPhase>Primarily middle state for the delivery of captions and subtitles online, but also developed for the purpose of authoring, transcoding, and exchanging time text information.</fdd:productionPhase> <fdd:relationships> <fdd:relationship> <fdd:typeOfRelationship>Defined via</fdd:typeOfRelationship> <fdd:relatedTo> <fdd:id>fdd000075</fdd:id> <fdd:shortName>XML</fdd:shortName> <fdd:titleName>Extensible Markup Language (XML)</fdd:titleName> </fdd:relatedTo> </fdd:relationship> <fdd:relationship> <fdd:typeOfRelationship>Component of</fdd:typeOfRelationship> <fdd:relatedTo> <fdd:id>fdd000481</fdd:id> <fdd:shortName>HTML5</fdd:shortName> <fdd:titleName>HyperText Markup Language (HTML) 5</fdd:titleName> </fdd:relatedTo> <fdd:comment> <p>The TTML1 <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/">specification</a> states “While TTML is not expressly designed for direct(embedded) integration into an HTML or a SMIL document instance, such integration isnot precluded.”</p> <p>TTML may provide a "<a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/#intro">standard content format</a> to reference from a <track> element in anHTML5 document.</p> </fdd:comment> </fdd:relationship> <fdd:relationship> <fdd:typeOfRelationship>Component of</fdd:typeOfRelationship> <fdd:relatedTo> <fdd:id>fdd000572</fdd:id> <fdd:shortName>SMIL</fdd:shortName> <fdd:titleName>Synchronized Multimedia Integration Language</fdd:titleName> </fdd:relatedTo> <fdd:comment> <p>The TTML1 <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/">specification</a> states “While TTML is not expressly designed for direct (embedded) integration into an HTML or a SMIL document instance, such integration is not precluded.”</p> <p>TTML may provide a <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/#intro">standard content format</a> to reference from a <text> or <textstream> media element in a SMIL2.1 document.</p> <p> <a href="https://www.w3.org/TR/ttml1/#derivation">Vocabulary Derivation</a> - TTML element vocabulary items are based on the syntactic and/or semantic model defined by the reference SMIL 2.1.</p> </fdd:comment> </fdd:relationship> <fdd:relationship> <fdd:typeOfRelationship>May contain</fdd:typeOfRelationship> <fdd:relatedTo> <fdd:id>fdd000482</fdd:id> <fdd:shortName>CSS</fdd:shortName> <fdd:titleName>Cascading Style Sheet (CSS) Markup</fdd:titleName> </fdd:relatedTo> <fdd:comment> <p>CSS style specification syntax is mapped to XML by use of attributes defined in the TTStyle Namespace.</p> <p> <a href="https://www.w3.org/TR/ttml1/#derivation">Vocabulary Derivation</a> - TTML element vocabulary items are based on the syntacticand/or semantic model defined by the reference CSS2, CSS3.</p> </fdd:comment> </fdd:relationship> <fdd:relationship> <fdd:typeOfRelationship>May contain</fdd:typeOfRelationship> <fdd:relatedTo> <fdd:id>fdd000483</fdd:id> <fdd:shortName>XHTML 1.0</fdd:shortName> <fdd:titleName>Extensible HyperText Markup Language (XHTML)</fdd:titleName> </fdd:relatedTo> <fdd:comment> <p> <a href="https://www.w3.org/TR/ttml1/#derivation">Vocabulary Derivation</a> - TTML element vocabulary items are based on the syntacticand/or semantic model defined by the reference XHTML 1.0.</p> </fdd:comment> </fdd:relationship> <fdd:relationship> <fdd:typeOfRelationship>May contain</fdd:typeOfRelationship> <fdd:relatedTo> <fdd:id>fdd000020</fdd:id> <fdd:shortName>SVG 1.1</fdd:shortName> <fdd:titleName>Scalable Vector Graphics (SVG) File Format Family</fdd:titleName> </fdd:relatedTo> <fdd:comment> <p> <a href="https://www.w3.org/TR/ttml1/#derivation">Vocabulary Derivation</a> - TTML element vocabulary items are based on the syntacticand/or semantic model defined by the reference SVG 1.1</p> </fdd:comment> </fdd:relationship> <fdd:relationship> <fdd:typeOfRelationship>May contain</fdd:typeOfRelationship> <fdd:relatedTo> <fdd:shortName>MPEG 7-5</fdd:shortName> <fdd:titleName>Multimedia Content Description Interface (MPEG 7-5)</fdd:titleName> </fdd:relatedTo> <fdd:comment> <p>Not described separately on this website at this time.</p> <p> <a href="https://www.w3.org/TR/ttml1/#derivation">Vocabulary Derivation</a> - TTML element vocabulary items are based on the syntacticand/or semantic model defined by the reference MPEG 7-5.</p> <p> <a href="https://www.iso.org/standard/34228.html">ISO/IEC 15938-1:2002Information technology — Multimedia content description interface — Part 1: Systems</a>.</p> </fdd:comment> </fdd:relationship> <fdd:relationship> <fdd:typeOfRelationship>May contain</fdd:typeOfRelationship> <fdd:relatedTo> <fdd:shortName>XSL 1.1</fdd:shortName> <fdd:titleName>Extensible Stylesheet Language (XSL) Version 1.1</fdd:titleName> </fdd:relatedTo> <fdd:comment> <p>Not described separately on this website at this time.</p> <p> <a href="https://www.w3.org/TR/ttml1/#derivation">Vocabulary Derivation</a> - TTML element vocabulary items are based on the syntacticand/or semantic model defined by the reference XSL 1.1.</p> <p> <a href="https://www.w3.org/TR/xsl11/">Extensible Stylesheet Language (XSL) Version 1.1</a>.</p> </fdd:comment> </fdd:relationship> <fdd:relationship> <fdd:typeOfRelationship>Has later version</fdd:typeOfRelationship> <fdd:relatedTo> <fdd:id>fdd000588</fdd:id> <fdd:shortName>TTML2</fdd:shortName> <fdd:titleName>Timed Text Markup Language (TTML), Version 2 (TTML2)</fdd:titleName> </fdd:relatedTo> <fdd:comment> <p>Timed Text Markup Language (TTML), Version 2, also referred to as TTML2.</p> </fdd:comment> </fdd:relationship> <fdd:relationship> <fdd:typeOfRelationship>Component of</fdd:typeOfRelationship> <fdd:relatedTo> <fdd:id>fdd000573</fdd:id> <fdd:shortName>DVB-SUB</fdd:shortName> <fdd:titleName>Digital Video Broadcasting; Subtitling systems (DVB-SUB)</fdd:titleName> </fdd:relatedTo> <fdd:comment>Per <a href="https://www.etsi.org/deliver/etsi_en/300700_300799/300743/01.06.01_20/en_300743v010601a.pdf">standard</a>, the document "specifies the transport of TTML subtitle streams in DVB MPEG-2 transport streams, based on the MPEG-2 system described in <a href="https://www.iso.org/standard/83239.html">ISO/IEC 13818-1</a>...The present document provides syntax for delivery of TTML subtitle streams over MPEG-2 transport stream, and is based on EBU-TT-D compatible with the IMSC1 Text Profile of W3C TTML." See <fddLink id="fdd000568">TTML1</fddLink> for more information on the W3C's IMSC1 Text Profile.</fdd:comment> </fdd:relationship> </fdd:relationships> </fdd:identificationAndDescription> <fdd:localUse> <fdd:experience>Likely exists in LC collections but not separately documented.</fdd:experience> <fdd:preference>The Library of Congress has not defined format preferences for caption or subtitle files for <a href="https://www.loc.gov/preservation/resources/rfs/moving.html">moving image works</a> in the Recommended Formats Statement.</fdd:preference> </fdd:localUse> <fdd:sustainabilityFactors> <fdd:disclosure>Open standard and fully documented. <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/">Timed Text Markup Language (TTML1) (Third Edition)</a> is a W3C Recommendation which is considered Web standard.</fdd:disclosure> <fdd:documentation> <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/">Timed Text Markup Language 1 (TTML1) (Third Edition) | W3C Recommendation 08 November 2018, edited in place 20 August 2020</a> is the most current specification and is maintained by the <a href="https://www.w3.org/AudioVideo/TT/">W3C’s Timed Text Working Group (TTWG)</a>. The mission of TTWG is “to develop W3C Recommendations for media online captioning by developing and maintaining new versions of the Timed Text Markup Language (TTML).”</fdd:documentation> <fdd:adoption> <p>Widely adopted format in the television industry and supported by most modern media players, caption software, and video recording software.</p> <p> <a href="https://support.google.com/youtube/answer/2734698?hl=en">YouTube</a>, <a href="https://partnerhelp.netflixstudios.com/hc/en-us/articles/360000456768-What-does-a-properly-formatted-TTML-file-look-like-">Netflix</a>, Amazon Prime Video (link to content provided but can't be made active this website's XML schema due to forbidden punctuation: https://videodirect.amazon.com/home/help?topicId=G201979140&ref_=avd_sup_G201979140), and <a href="http://www.telestream.net/vantage/TimedText.htm">Telestream</a> are some supporters of the TTML format.</p> <p>According to Andrea Tai in <a href="https://www.balisage.net/Proceedings/vol17/print/Tai01/BalisageVol17-Tai01.html">Balisage Paper: XML in the Air – How TTML can change the Workflows for Broadcast Subtitles</a> from August 2016, “The adoption of TTML started with DFXP as pre-final candidate recommendation and quickly gained popularity. Unfortunately, the final TTML 1 version specification changed not only the name of the format from ‘Timed Text (TT) Authoring Format 1.0 – Distribution Format Exchange Profile (DFXP)’ to ‘Timed Text Markup Language 1 (TTML1)’ but also replaced XML namespaces (the local names of nearly all elements and attributes remained the same). This led not only to confusion (the older version is often not associated with TTML because of the different spec title) but is also an interoperability problem. Although two simple XSLT scripts exist that replace namespaces in both directions out of the box, an XML-compliant TTML 1 player is not able to process DFXP files and an XML-compliant DFXP player is not able to process TTML 1 files.”</p> <p>In a press release from W3C in January 2016, <a href="https://www.w3.org/2016/01/emmyawardttml.html.en">World Wide Web Consortium (W3C) to Receive Emmy ® Award for Standards Work on Accessible Video Captioning and Subtitles</a>. The category recognized TTML’s standard and how it “helps ensure that the needs of people with disabilities, particularly people who are deaf or hard of hearing, are addressed.”</p> <p>Liam Moran in the featured article on StreamingMedia.com titled, <a href="https://www.streamingmedia.com/Articles/Editorial/Featured-Articles/The-Complete-Guide-to-Closed-Captions-152459.aspx">The Complete Guide to Closed Captions</a>, April 2022, “But TTML is on a major comeback campaign. The international ATSC 3.0 broadcast standard adopted TTML as its mandatory captioning standard, specifically the IMSC1 profile that defines the subset of the TTML specification required for captions and subtitles. ATSC 3.0 went nationwide in South Korea in 2016, and the transition is occurring in the U.S. under the NextGen TV moniker, which is currently on the air on more than 150 TV stations in 43 cities. Apple enthusiastically added support for IMSC1/TTML captions to the HTTP Live Streaming (HLS) specification in 2017...That TTML is both the captioning standard for broadcast television and the adopted standard used by streaming industry leaders like Netflix presents an obvious benefit to content producers and points the way to a bright future for TTML.”</p> </fdd:adoption> <fdd:licensingAndPatents> <p>None.</p> <p>The W3C Patent Policy has the goal of assuring that all W3C Recommendations can be implemented on a royalty-free basis.</p> </fdd:licensingAndPatents> <fdd:transparency> <p>Based on XML and hence readable with a basic viewer or editor, although editing software is recommended, especially for users not familiar with XML.</p> <p>Per TTML1 specification, <a href="https://www.w3.org/TR/ttml1/#concrete-encoding">M Concrete Encoding (Non-Normative)</a>:</p> <p>In the absence of other requirements, it is recommended that a Document Instance be concretely encoded as a well-formed XML 1.0 [XML 1.0] document using the UTF-8 character encoding.</p> <p>Note: When using XML 1.0 as the concrete encoding of TTML, only the following named character entities are defined: &amp;, &apos;, &lt;, &gt;, and &quot;.</p> <p> <a href="https://www.loc.gov/preservation/digital/formats/contact_format.shtml">Comments welcome</a>.</p> </fdd:transparency> <fdd:selfDocumentation> <p>TTML1 specifications since Timed Text (TT) Authoring Format 1.0 define a <b>metadata element</b> within the <b>header section</b> of the TTML1 document. Document level metadata may specify a document title, description, copyright, agent, name, and actor information. Additionally, arbitrary metadata can be drawn from other specified namespaces.</p> <p>Per <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/#metadata">specification</a>, the metadata element functions as a generic container and is understood to be a separable layer of information that applies to parameters, content, style, layout, timing, and metadata itself (two forms: documents specified and arbitrary).</p> <p> <a href="https://www.loc.gov/preservation/digital/formats/contact_format.shtml">Comments welcome</a>.</p> </fdd:selfDocumentation> <fdd:externalDependencies> <p>None beyond availability of supporting software.</p> <p>TTML1 specification <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/#media-types-registration">Interoperability Considerations</a>:<br/>“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> <p> <a href="https://www.loc.gov/preservation/digital/formats/contact_format.shtml">Comments welcome</a>.</p> </fdd:externalDependencies> <fdd:techProtection> <p>TTML1 specification <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/#media-types-registration">Security Considerations</a>:</p> <p>“As with other XML types and as noted in <a href="https://www.rfc-editor.org/rfc/rfc7303#section-10">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 constrainedenvironments to fail.<br/> <br/>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.<br/> <br/>Although not prohibited, there are no expectations that XML signatures or encryption would normally be employed.”<br/> </p> <p> <a href="https://www.loc.gov/preservation/digital/formats/contact_format.shtml">Comments welcome</a>.</p> </fdd:techProtection> </fdd:sustainabilityFactors> <fdd:qualityAndFunctionalityFactors> <fdd:textQF> <fdd:normalText> <p>Good support. Per the <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/#requirements">specification</a>, TTML1 text files have a minimum character representability of Unicode 4.0, using UTF-8 character encoding. W3C Timed Text documentation <a href="https://www.w3.org/AudioVideo/TT/docs/TTML-Profiles.html">TTML and Derivative Captions Formats</a> describes TTML as content elements are HTML-like elements (such as <div>, <p>, <span>) and style elements arespecified via a simple XML-based styling system.</p> <p> <a href="https://www.loc.gov/preservation/digital/formats/contact_format.shtml">Comments welcome</a>.</p> </fdd:normalText> <fdd:structure> <p>Some support. XML-based which is ideal for document structure. <a href="https://www.speechpad.com/">SpeechPad.com</a>, a captioning video service, in their <a href="https://www.speechpad.com/captions/ttml">TTML information page</a>, state “TTML is very similar to HTML, in that it consists of a collection of nested structural elements, with tags to mark the beginning and end of each element.”</p> <p> <a href="https://www.loc.gov/preservation/digital/formats/contact_format.shtml">Comments welcome</a>.</p> </fdd:structure> <fdd:layout> <p>Some support. TTML1 files support optional styling and layout layers. As described in the <a href="https://www.w3.org/TR/ttml1/#layout">specification</a>, the layers are considered independently separable; layout specifies wherethe author intends for the content to be presented; and style specifies how the content will be presented in the layout, referenced by the layout and content information.</p> <p>Styling and layout elements may rely on supportive software, where one rendering program supports more options than another.</p> <p>W3C Timed Text documentation <a href="https://www.w3.org/AudioVideo/TT/docs/TTML-Profiles.html">TTML and Derivative Captions Formats</a> states, “There is partial and full support of TTML in components used by several Web browsers agents, and in a number of caption authoring tools.”</p> <p>The TTML1 <a href="https://www.w3.org/TR/ttml1/#styling">specification</a> states, “Styling attributes are included in TTML to enable authorial intent of presentation to be included within a self-contained document...TTML Processors are not required to present Document Instances in anyparticular way; but an implementation of this model by a TTML Presentation Processor that provides externally observable results that are consistent with this model is likely to lead to a user experience that closely resembles the experience intended by the documents' authors.”</p> <p> <a href="https://www.loc.gov/preservation/digital/formats/contact_format.shtml">Comments welcome</a>.</p> </fdd:layout> <fdd:mathDiag> <p>Low Support. Little to no information on TTML1’s support of mathematics, chemical formulae, diagrams, etc.</p> <p> <a href="https://www.loc.gov/preservation/digital/formats/contact_format.shtml">Comments welcome</a>.</p> </fdd:mathDiag> <fdd:beyondText> <p>Some support. The TTML <a href="https://www.w3.org/TR/ttml1/#intro">specification</a> mentions that certain properties of TTML support streamability of content, providing some useful streaming scenarios, but it is also non-normative.</p> <p>TTML <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/#animation">specification</a> notes the set element specified for animation aspects, such as expressing a discrete change in some style parameters applied over a time interval. Semantics for the set element are based on the defined <a href="https://www.w3.org/TR/2011/REC-SVG11-20110816/">SVG 1.1 specification</a>.</p> <p> <a href="https://www.loc.gov/preservation/digital/formats/contact_format.shtml">Comments welcome</a>.</p> </fdd:beyondText> </fdd:textQF> </fdd:qualityAndFunctionalityFactors> <fdd:fileTypeSignifiers> <fdd:signifiersGroup> <fdd:filenameExtension> <fdd:sigValues> <fdd:sigValue>ttml</fdd:sigValue> </fdd:sigValues> <fdd:note>Per specification. See <a href="https://www.w3.org/TR/ttml1/#media-types-registration">https://www.w3.org/TR/ttml1/#media-types-registration</a>.</fdd:note> </fdd:filenameExtension> <fdd:filenameExtension> <fdd:sigValues> <fdd:sigValue>dfxp</fdd:sigValue> </fdd:sigValues> <fdd:note>Per specification, previous drafts referred to TTML as DFXP (Distribution Format Exchange Profile), the term is retained for historical reasons in certain contexts, such as profiles and designators. See <a href="https://www.w3.org/TR/ttml1/#intro">https://www.w3.org/TR/ttml1/#intro</a>. <br/> <br/> <a href="https://en.wikipedia.org/wiki/Timed_Text_Markup_Language">TTML's Wikipedia page</a> lists this as an extension. <br/> <br/> According to Rudolf Boogerman in <a href="https://www.miracletutorials.com/how-to-create-captionssubtitles-for-video-and-audio-in-webtvv-srt-dfxp-format/">How to Create Captions/Subtitles for Video and Audio in WebVTT, SRT, DFXP Format</a>, Updated March 2019, users can “save the file with an .dfxp extension, like mycaption.dfxp, but you also may use mycaption.xml since this basically is a XML file.” See <a href="#notes">Notes</a> for more information found on file extensions.<br/> <br/> <a href="https://www.loc.gov/preservation/digital/formats/contact_format.shtml">Comments welcome</a>.</fdd:note> </fdd:filenameExtension> <fdd:filenameExtension> <fdd:sigValues> <fdd:sigValue>xml</fdd:sigValue> </fdd:sigValues> <fdd:note> <a href="https://en.wikipedia.org/wiki/Timed_Text_Markup_Language">TTML's Wikipedia page</a> lists this as an extension. <br/> <br/>According to Rudolf Boogerman in <a href="https://www.miracletutorials.com/how-to-create-captionssubtitles-for-video-and-audio-in-webtvv-srt-dfxp-format/">How to Create Captions/Subtitles for Video and Audio in WebVTT, SRT, DFXP Format</a>, Updated March 2019, users can “save the file with an .dfxp extension, like mycaption.dfxp, but you also may use mycaption.xml since this basically is a XML file.” See <a href="#notes">Notes</a> for more information found on file extensions.<br/> <br/> <a href="https://www.loc.gov/preservation/digital/formats/contact_format.shtml">Comments welcome</a>.</fdd:note> </fdd:filenameExtension> <fdd:internetMediaType> <fdd:sigValues> <fdd:sigValue>application/ttml+xml</fdd:sigValue> </fdd:sigValues> <fdd:note>Per specification. See <a href="https://www.w3.org/TR/ttml1/#media-types-registration">https://www.w3.org/TR/ttml1/#media-types-registration</a> </fdd:note> </fdd:internetMediaType> <fdd:other> <fdd:tag>Mac OS file type</fdd:tag> <fdd:values> <fdd:sigValues> <fdd:sigValue>TTML</fdd:sigValue> </fdd:sigValues> <fdd:note>See <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/">https://www.w3.org/TR/2018/REC-ttml1-20181108/</a> </fdd:note> </fdd:values> </fdd:other> <fdd:other> <fdd:tag>Pronom PUID</fdd:tag> <fdd:values> <fdd:sigValueNA>See note.</fdd:sigValueNA> <fdd:note>PRONOM has no corresponding entry as of April 2023.</fdd:note> </fdd:values> </fdd:other> <fdd:other> <fdd:tag>Wikidata Title ID</fdd:tag> <fdd:values> <fdd:sigValues> <fdd:sigValue>Q25339304</fdd:sigValue> </fdd:sigValues> <fdd:note>Wikidata entry for Timed Text Markup Language. See <a href="https://www.wikidata.org/wiki/Q25339304">https://www.wikidata.org/wiki/Q25339304</a>. Wikidata does not specify a version of TTML.</fdd:note> </fdd:values> </fdd:other> </fdd:signifiersGroup> </fdd:fileTypeSignifiers> <fdd:notes> <fdd:general> <p> <b>Timed Text Working Group</b> </p> <p>The <a href="https://www.w3.org/AudioVideo/TT/">TTWG</a> maintains the <a href="https://www.w3.org/wiki/TimedText">Time Text wiki</a> that includes TTWG’s list of <a href="https://www.w3.org/wiki/TimedText/TTML1-3ED_implementation_report">known implementations</a>, as well as publications and other resources.</p> <ul> <li> <a href="https://www.w3.org/2021/Process-20211102/">W3C.org - Implementation Experience</a> – required to show that a specification issufficiently clear, complete, and relevant to market needs, ensures independentimplementation of each specification feature.</li> </ul> <p>-</p> <p>According to the <a href="http://www.telestream.net/vantage/overview.htm">Vantage</a>’s (media processing platform) <a href="http://www.telestream.net/pdfs/app-notes/app-Vantage-Timed-Text-Flip.pdf">Timed Text Flip Application Note</a>, “Essentially, all TTML files are XML's. However, packaging of video programming with side car TTML caption/subtitle files need to meet the required specifications to be accepted by a video programming distributor. Therefore, Timed Text Flip has the following bindable options:</p> <ul> <li>.XML—Often used for SMPTE TT 2052 captioning file format. This extension is thedefault</li> <li>.dfxp—This is a legacy naming extension used by proprietary video depositories andgeneric implementation of TTML</li> <li>.ttml—This extension should be used for IMSC 1.0 subtitling TTML profile</li> <li>.itt—This extension should be used for the iTT (iTunes subtitling) profile”</li> </ul> </fdd:general> <fdd:history> <p>W3C announced the creation of the <a href="https://www.w3.org/AudioVideo/TT/">Timed Text Working Group (TTWG)</a> in early 2003, as part of the Synchronized Multimedia Activity (SYMM), designers of the Synchronized Multimedia Integration Language (SMIL) (fdd000572), a markup language used for authoring multimedia presentations. The TTWG’s mission was to develop an XML-based format used to represent streamable text synchronized with other time media, i.e., audio or video.</p> <p>At the time there was no standard method of displaying text synchronized to another element onthe Web. The three most popular media players, Apple’s QuickTime Player, Microsoft’s MediaPlayer, and RealNetwork’s RealPlayer, all supported their own proprietary text formats, meaningmedia authors had to create multiple files to support more than one player. Multiple incompatiblecaptioning and subtitle formats created issues for interoperable presentations, but also increasedthe cost of captioning Web content. It was determined that a standardized timed-text formatcould reduce duplicate work, but also simplify creating and distributing synchronized text acrossmultiple devices, such as media players, but also caption encoders, character generators, andother text-display devices.</p> <p>The TTWG included vendors from the streaming multimedia technologies, web browsercompanies, and representatives from the accessibility communities, working on the goal toharmonize one or more of the existing formats, but their focus was on the development of anXML-based representation, incorporating all the functionality of the existing formats to becomethe base standard interchange format.</p> <p>The base standard was called <a href="https://www.w3.org/TR/2006/WD-ttaf1-dfxp-20060427/">Timed Text Authoring Format (TT AF) Distribution FormatExchange Profile (DFXP)</a>, released in 2004, and was intended to cover all aspects of timed texton the Web and to become the standard captioning interchange format. The TT AF defined timedtext representation for interchanging between systems, while the DFXP document specifiedvocabulary, semantics, and styling for TT AF, with its purpose for exchanging timed textinformation among legacy distribution formats. The <a href="https://web.archive.org/web/20090927073917/http://www.w3.org/TR/2009/CR-ttaf1-dfxp-20090924/">Time Text (TT) Authoring Format –Distribution Format Exchange Profile (DFXP) W3C Recommendation</a> was released in 2009.</p> <p>In February 2010, the TTWG changed the name of TTAF DFXP and released a newspecification called <a href="https://web.archive.org/web/20100902164033/http://www.w3.org/TR/ttaf1-dfxp/">Time Text Markup Language (TTML) 1.0 W3C CandidateRecommendation</a>. The TTML standard framework addressed requirements from three majorgroups, web developers, movie producers, and live broadcasters. One standard would not satisfyall of the needs of each group, leading to TTML being developed as a base standard, definingfeatures needed for captioning and new Profiles could be defined that incorporated groups ofthese features. Profiles are based on the main specification, but are developed with certainconstraints, extensions, or both depending on the application. TTML is a complex but flexiblecaption format used for authoring, interchange, and distribution cases. TTML has two versions ofthe TTML specification, TTML1 (described here) and TTML2 (fdd000588).</p> <ul> <li>Per <a href="https://www.w3.org/TR/ttml1/#intro">specification</a>: “In the first edition of this specification, the version number 1.0 wasused to refer to this version of TTML. In this second edition, this version number issimplified to 1 as a result of a determination to call the next (future) version 2 instead of1.1.”</li> </ul> <p>-</p> <p> <a href="https://www.w3.org/TR/2018/REC-ttml1-20181108/">Timed Text Markup Language 1 (TTML1) (Third Edition) | W3C Recommendation 08November 2018</a>, edited in place 20 August 2020 is the most current specification and ismaintained by the W3C’s Timed Text Working Group (TTWG).</p> <p>-</p> <p> <a href="https://www.w3.org/PM/Groups/chairboard.html?gid=34314">Participating Organizations of the Timed Text Working Group (TTWG)</a> include: Adobe, Apple Inc., Brightcove, British Broadcasting Corporation, ERICSSON, Google LLC, Igalia, Kodansha, Publishers, Ltd., MovieLabs, Mux, and Netflix.</p> </fdd:history> </fdd:notes> <fdd:formatSpecifications> <fdd:urls> <fdd:url> <fdd:urlReference> <link>https://www.w3.org/TR/2018/REC-ttml1-20181108/</link> <tag>Timed Text Markup Language 1 (TTML1) (Third Edition) | W3C Recommendation 08 November 2018, edited in place 20 August 2020</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlGroup> <fdd:intro>Previous Editions</fdd:intro> <fdd:urlList> <fdd:urlReference> <link>https://www.w3.org/TR/2018/PR-ttml1-20181004/</link> <tag>Timed Text Markup Language 1 (TTML1) (Third Edition) | W3C Proposed Recommendation 04 October 2018</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/TR/2018/CR-ttml1-20180809/</link> <tag>Timed Text Markup Language 1 (TTML1) (Third Edition) | W3C Candidate Recommendation 09 August 2018</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/TR/2018/CR-ttml1-20180424/</link> <tag>Timed Text Markup Language 1 (TTML1) (Third Edition) | W3C Candidate Recommendation 24 April 2018</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/TR/2013/REC-ttml1-20130924/</link> <tag>Timed Text Markup Language 1 (TTML1) (Second Edition) | W3C Recommendation 24 September 2013</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</link> <tag>Timed Text Markup Language (TTML) 1.0 | W3C Recommendation 18 November 2010</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/TR/2010/CR-ttaf1-dfxp-20100223/</link> <tag>Timed Text Markup Language (TTML) 1.0 | W3C Candidate Recommendation 23 February 2010</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/TR/2010/PR-ttaf1-dfxp-20100914/</link> <tag>Timed Text Markup Language (TTML) 1.0 | W3C Proposed Recommendation 14 September 2010 </tag> <comment>Includes property sets that can store document-level properties (metadata).</comment> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/TR/2009/CR-ttaf1-dfxp-20090924/</link> <tag>Timed Text (TT) Authoring Format 1.0 – Distribution Format Exchange Profile (DFXP) | W3C Candidate Recommendation 24 September 2009</tag> </fdd:urlReference> </fdd:urlList> </fdd:urlGroup> </fdd:url> </fdd:urls> </fdd:formatSpecifications> <fdd:usefulReferences> <fdd:urls> <fdd:url> <fdd:urlGroup> <fdd:intro>W3C.org (www.w3.org)</fdd:intro> <fdd:urlList> <fdd:urlReference> <link>https://www.w3.org/TR/2018/REC-ttml1-20181108/</link> <tag>Timed Text Markup Language 1 (TTML1) (Third Edition) | W3C Recommendation</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/TR/ttml/all/</link> <tag>TTML Cover Page</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/AudioVideo/TT/</link> <tag>Timed Text Working Group</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/PM/Groups/chairboard.html?gid=34314</link> <tag>TTWG Chair Dashboard</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/AudioVideo/TT/docs/TTML-Profiles.html</link> <tag>TTML and derivative Captions Formats</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/AudioVideo/timetext.html</link> <tag>Standarized Timed-Text Format</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/community/whatwg/</link> <tag>Web Hypertext Application Technology Community Group</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/2016/01/emmyawardttml.html.en</link> <tag>W3C Press Release - World Wide Web Consortium (W3C) to Receive Emmy ®Award for Standards Work on Accessible Video Captioning and Subtitles,January 2016</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/standards/types#</link> <tag>Documents Published at W3C</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/Consortium/Patent-Policy-20200915/</link> <tag>W3C Patent Policy</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/TR/ttml-profile-registry/</link> <tag>TTML Media Type Definition and Profile Registry | W3C Working Group Note 19 November 2020</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/TR/ttml-imsc1.0.1/</link> <tag>TTML Profiles for Internet Media Subtitles and Captions 1.0.1 (IMSC1) | W3C Recommendation 24 April 2018, edited in place 27 April 2020</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/TR/2013/NOTE-ttml10-sdp-us-20130205/</link> <tag>TTML Simple Delivery Profile for Closed Captions (US) | A profile of TTML for internet delivery of Captions originated in the United States | W3C Working Group Note 05 February 2013</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/TR/2021/CR-ttml2-20210309/</link> <tag>Timed Text Markup Language 2 (TTML2) (2nd Edition) | W3C Candidate Recommendation Snapshot 09 March 2021</tag> </fdd:urlReference> <fdd:urlReference> <link>https://w3c.github.io/ttml3/index.html</link> <tag>Timed Text Markup Language 3 (TTML3) | W3C Working Draft 15 February 2022 </tag> <comment>Status: The "document is an editor's copy that has no official standing."</comment> </fdd:urlReference> <fdd:urlReference> <link>https://www.w3.org/wiki/TTML/Documentation</link> <tag>TTML Wiki Documentation</tag> </fdd:urlReference> </fdd:urlList> </fdd:urlGroup> </fdd:url> <fdd:url> <fdd:urlReference> <link>https://en.wikipedia.org/wiki/Timed_Text_Markup_Language/</link> <tag>Wikipedia – Timed Text Markup Language</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlReference> <link>https://www.iana.org/assignments/media-types/application/ttml+xml</link> <tag>IANA.org - TTML</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlReference> <link>https://www.researchgate.net/publication/269098564_XML_Family_of_Languages_Overview_and_Classification_of_W3C_Specifications</link> <tag>ResearchGate.net - XML Family of Language. Overview and Classification of W3CSpecifications</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlReference> <link>https://www.balisage.net/Proceedings/vol17/print/Tai01/BalisageVol17-Tai01.html</link> <tag>Balisage.net - Balisage Paper: XML in the air – How TTML Can Change the Workflowsfor Broadcast Subtitles</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlReference> <link>https://www.streamingmedia.com/Articles/Editorial/Featured-Articles/The-Complete-Guide-to-Closed-Captions-152459.aspx</link> <tag>StreamingMedia.com - The Complete Guide to Closed Captions</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlGroup> <fdd:intro>SpeechPad.com</fdd:intro> <fdd:urlList> <fdd:urlReference> <link>https://www.speechpad.com/captions/ttml</link> <tag>TTML (Timed Text Markup Language)</tag> </fdd:urlReference> <fdd:urlReference> <link>https://www.speechpad.com/captions/xml-ttml-dfxp-smpte-tt-subtitles-captions</link> <tag>History of XML Captions</tag> </fdd:urlReference> </fdd:urlList> </fdd:urlGroup> </fdd:url> <fdd:url> <fdd:urlReference> <link>https://www.miracletutorials.com/how-to-create-captionssubtitles-for-video-and-audio-in-webtvv-srt-dfxp-format/</link> <tag>MiracleTurorials.com - How to Create Captions/Subtitles for Video and Audio inWebVTT, SRT, DFXP Format</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlReference> <link>http://xml.coverpages.org/ni2003-01-23-c.html</link> <tag>CoverPages.org - W3C Chartes Timed-Text Working Group (TTWG)</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlReference> <link>https://www.mux.com/blog/subtitles-captions-webvtt-hls-and-those-magic-flags</link> <tag>Mux.com - Subtitles, Captions, WebVTT, HLS, and those magic flags</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlReference> <link>https://www.capitalcaptions.com/subtitles-and-captioning/closed-captioning-translation-and-forced-narrative-or-forced-subtitles/</link> <tag>CaptialCaptions.com - Closed Captioning, Translation and Forced Narrative or ForcedSubtitles</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlReference> <link>https://codesequoia.wordpress.com/2011/12/15/ttml_dfxp_smptett/</link> <tag>CodeSequoia.Wordpress.com - TTML, DFXP, and SMPTE-TT</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlReference> <link>https://www.atsc.org/wp-content/uploads/2016/12/A343-2017-Captions-and-Subtitles-4.pdf</link> <tag>ATSC.org - ATSC Standard: Captions and Subtitles (A/343)</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlReference> <link>https://dvb.org/?standard=dvb-ttml-subtitling-systems</link> <tag>DVB.org - DVB-TTML (Subtitling) - Timed Text Markup Language</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlReference> <link>https://learn.microsoft.com/en-us/openspecs/ie_standards/ms-ttml/16bc3854-9a56-48b1-97e5-ae5d41de67d5</link> <tag>Microsoft.com - Mircosoft Edge/Internet Explorer Timed Text Markup Language(TTML) 1.0 Standards Support Document</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlReference> <link>http://www.telestream.net/pdfs/app-notes/app-Vantage-Timed-Text-Flip.pdf</link> <tag>Vantage Manual, TeleStream.net - Using Timed Text Flip in Vantage</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlReference> <link>https://whatwg.org/</link> <tag>WHATWG.org - Welcome to the WHATWG Community</tag> </fdd:urlReference> </fdd:url> <fdd:url> <fdd:urlReference> <link>https://www.wikidata.org/wiki/Q25339304</link> <tag>Wikidata – Timed Text Markup Language</tag> </fdd:urlReference> </fdd:url> </fdd:urls> </fdd:usefulReferences></fdd:FDD>