- From: <bugzilla@jessica.w3.org>
- Date: Wed, 03 Nov 2010 16:38:53 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11207
John Foliot <jfoliot@stanford.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jfoliot@stanford.edu
--- Comment #2 from John Foliot <jfoliot@stanford.edu> 2010-11-03 16:38:52 UTC ---
(In reply to comment #1)
> Why do we want to remove WebSRT specifics?
At this time the media sub-group of the Accessibility Task Force desire that
the language be as neutral and technology agnostic as possible. It is unclear
_at this time_ if WebSRT is sufficient for meeting all of the user requirements
and author needs that we have identified. We are currently evaluating a number
of time formats (WebSRT, TTML, etc.) to determine which, if any, best meets
these needs, which is why we are asking that folks review the user
requirements.
> Why do we want to try and
> genericize the API, when there aren't currently plans to add additional timed
> text formats?
Curious to know where this assertion is coming from, as AFAIK this has never
been discussed within the W3C, and this is a topic that I have been following
most closely. Implementers might be experimenting with WebSRT today (and there
is usefulness in that), but at this time I do not believe a final decision has
been made to standardize on a specific time format.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 3 November 2010 16:38:55 UTC