Timed Text Markup Language: Difference between revisions

Revision as of 17:37, 21 March 2016

Revision as of 16:56, 29 May 2016

Line 23:

|title=WebVTT versus TTML: XML considered harmful for web captions?

|accessdate=16 February 2015

}}</ref> Nonetheless, in February 2012 the [[Federal Communications Commission|FCC]] declared the [[Society of Motion Picture and Television Engineers|SMPTE]] closed-captioning standard for online video content, a superset of TTML, as a "safe harbor interchange, delivery format".<ref>{{cite web |url=https://www.smpte.org/news-events/news-releases/fcc-declares-smpte-closed-captioning-standard-online-video-content-safe |title=FCC Declares SMPTE Closed-Captioning Standard For Online Video Content As Safe Harbor Interchange, Delivery Format |accessdate=20 February 2015}}</ref>

It is not clear whether the HTML5 specification will document the usage of any other timed text format with the <code>&lt;track&gt;</code> tag. However, as of February 2015, W3C only documents the usage of WebVTT with HTML5 and its specification had 434 entries in its commit history, ranging from March 2013 to January 2015, while the latest TTML specification hadn't been modified since September 2013. Recent versions of [[Internet Explorer]] introduced support for TTML files in the <code>&lt;track&gt;</code> element,<ref>{{cite web|url=http://ie.microsoft.com/Testdrive/HTML5/Captions/Default.html |title=Simple Delivery Profile for TTML Captions |accessdate=20 February 2015}}</ref> while other browsers still require [[Javascript]], such as in the W3C Timed Text Working Group's [http://www.w3.org/2009/02/ThisIsCoffee.html 2009 demo] of DFXP features. TTML is still the format of choice for some applications that don't rely on HTML5, such as the popular [[set-top box]] [[Roku]].<ref>{{cite web