[Webkit-unassigned] [Bug 110479] [Meta] Implement support for TTML

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=110479





--- Comment #19 from Glenn Adams <glenn at skynav.com>  2013-02-22 05:05:50 PST ---
(In reply to comment #17)
> I think your only alternative is to render TTML as an overlay graphic on the video video. Is that your plan for this bug?

Yes.

> I'd take a look at a mapping specification when you've created it. However, I personally don't think we should proliferate more file formats for <track> on the Web, because it just causes support issues. I am very wary of the vast complexity of the TTML ecosystem with now at least 5 different and partially non-compatible formats and more forthcoming. It's a support nightmare in the making.

Well, one could view WebVTT as a proliferation of file formats. One could view WebM as a proliferation of file formats. I find this argument about file formats unrealistic. They are there. Why do we have XHR and WebSockets and WebRTC and Server-Sent Events? WebVTT has no more claim to legitimacy in the Web than TTML, and probably less since it isn't even a published standard.

The issue of different profiles of TTML is also a non-issue. There are well defined ways in TTML to manage feature spaces and required features in an implementation. The same cannot be said for WebVTT. You are already promoting extensions to WebVTT that will eventually create different sets of implemented features. How will you manage them? TTML has an answer to this.

I really don't want to fall into a side by side comparison of WebVTT and TTML. It is not a productive use of time. There are legitimate reasons to use both and they are different reasons.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.