W3C home > Mailing lists > Public > public-tt@w3.org > March 2009

RE: [minutes] 20090313 Timed Text Working Group

From: Geoff Freed <geoff_freed@wgbh.org>
Date: Fri, 13 Mar 2009 21:28:13 -0400
To: "public-tt@w3.org" <public-tt@w3.org>
Message-id: <E36081A12A13F146AC32D7724B0E89120761DFBAC6@EXCHCCR.wgbh.org>

apologies to the group for missing the call-- i was caught up in a project that wouldn't end.  i'll beon the 3/27 call.


From: public-tt-request@w3.org [public-tt-request@w3.org] On Behalf Of Philippe Le Hegaret [plh@w3.org]
Sent: Friday, March 13, 2009 12:57 PM
To: public-tt@w3.org
Subject: [minutes] 20090313 Timed Text Working Group

Available at


Text version:

13 Mar 2009

   See also: [2]IRC log

      [2] http://www.w3.org/2009/03/13-tt-irc


          Plh, Sean, David, Franz





     * [3]Topics
         1. [4]Test results
         2. [5]Schedule
         3. [6]Next meeting
     * [7]Summary of Action Items

Test results

   Sean: I'm working on an implementation, called TimedTextPad
   ... I cover all of the timing
   ... Paragraph002 is incorrect now, since body is a par
   ... so Timing and content are well covered
   ... and Glenn covers those pretty well as well
   ... issue is with Styling
   ... three major grouping of functionalities
   ... color: background, visibility, opcate, color
   ... I pass all of those. Glenn does. Philippe as well
   ... so we're fine
   ... then fonts stuff
   ... fonts is relatively easy to pass for me and should be
   ... both Glenn and Philippe pass those
   ... tests aren't very well organized
   ... some of those tests need to be slightly reworked
   ... the only problematic one at is the blur raduis on text outline
   ... Glenn and Philippe don't do

   Philippe: willing to submit new tests for font family?

   Sean: eventually, I'll figure out if every test is correct
   ... some of the tests cannot be told if they work or not
   ... biggest concern is writing mode and unicode bidi group
   ... vertical text and right to left. so, we don't have that many
   feature that don't have two implementations

   Sean: there are some stress tests we could provide
   ... like lots of nested, multiple regions
   ... ie testing the implementation rather than the spec

   Philippe: would be nice to have, but not a requirement

   Sean: could put them into a separate bucket
   ... we need the animation tests and all the other in the spreadsheet

   Philippe: will do

   Sean: can you run Glen's implementation?

   Philippe: not for the 27 unfortunately

   Sean: I'll run tests on Glen then [David will send Glenn's
   implementation to Sean]

   David: what about the metadata test?

   Sean: our implementations don't do anything with those

   Philippe: at least, we don't crash :)

   Sean: If I get around the rest, I might do something

   David: we do something with them, when converting to our own XML
   ... the color code that we use is sophisticated
   ... using scene details as well
   ... I could send a pointer around, it's under license GPLv2

   Sean: interested to the code but license issue :(.
   ... so, we're in a pretty good shape for the test results
   ... how about parameters: cell resolution? clock mode?

   David: if you're dealing with region, it would be relatively easy

   Sean: yes
   ... framerate is fine, no sure with multipliers. but that basic

   Philippe: I could deal with some of those as well but don't have
   time at the moment


   Sean: let's pick May 1. June 1 for end of last call
   ... July 1 done with comments
   ... PR by July 1

   Philippe: that would be REC in August. not the best time for a press

   sean: then, let's say press release last week of August or first
   week of september

   Philippe: if Glenn doesn't show up by April 1, we can look into
   finding an alternate editor

   David: there was two or three required features (like the
   requiredFeatures attribute) what the authoring system is required to
   support. What about those?

   Sean: I'll look at the features in appendix C. Since we don't have
   spec text for those, we might have to drop them.
   ... we should leave April for writing and testing implementations
   ... for example. for blur radius, we need to have that text

   Philippe: we should make it clear that everything needs to be
   implemented no later than July 1. Everything that it is not is out.
   All issues should be identified by April 1. No more new things into
   the draft after May 1.

Next meeting

   No meeting on March 20

   Next meeting is March 27

   Regrets from plh

Received on Saturday, 14 March 2009 01:32:42 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:24:04 UTC