Progress update.

At our meeting on the 18th of June, we agreed that the document was stable enough to proceed to PR, assuming adequate implementation. In the interim I have been able to verify that we are indeed very close to that goal, with the following exceptions:

Overline/throughline. The XFSI implementation seems to have a bug which is preventing this from working. Glenn is investigating, this is well understood technology however, and I believe will not be a problem..

Reverse oblique text format; no one has implemented this. This I believe can be deleted from the spec without issue.

Philippe and I will be preparing the transition request and  Philippe will be updating the implementation report on the website shortly.

Thanks,
Sean.

From: Geoff Freed [mailto:geoff_freed@wgbh.org]
Sent: 14 June 2010 13:25
To: Sean Hayes; public-tt@w3.org
Subject: Re: New CR draft


i'll be out of the office from 6/16-7/7, so regrets for this meeting.

g.



On 6/11/10 9:32 AM, "Sean Hayes" <Sean.Hayes@microsoft.com> wrote:
Today is the deadline, and I have had no comments, so I am assuming this draft meets everyone's needs. I promised to convene a meeting today to advance the spec; however due to other issues, including half the week without internet connection I was unable to do so.

This meeting will now be next week, the 18th of June.

Philippe, can you set up the bridge accordingly, thanks.

Sean.


From: public-tt-request@w3.org [mailto:public-tt-request@w3.org] On Behalf Of Sean Hayes
Sent: Thursday, May 13, 2010 10:13 PM
To: public-tt@w3.org
Subject: New CR draft

Attention TTWG.

As no implementation information has been forthcoming, Philippe and I have edited the CR document to remove the 'at risk' dynamic flow feature. In addition the conversion to the TTML name has been completed. The document is available at [1].

Note, due to some intense discussions on the HTML5 WG list recently, I have also changed some of the language around the styling vocabulary. This now  hopefully makes it clearer that XSL is used as an exemplar technology that exhibits presentation semantics which would render TTML as an author would expect; but that TTML does not require an XSL processor. These changes are editorial in nature, and not substantive, as at no time has it been the intention that TTML require XSL.  However please review these changes in case I changed something significant in error.

One of the benefits of these editorial changes is that it will make it easier to migrate TTML to a CSS3 stylesheet based presentation system, as that standard matures. To that end I have made one technical change, which is to make the content model of the <style> element EMPTY. This allows the option in the future to use that element to contain inline stylesheet data as PCDATA, or to point to an external stylesheet resource without invalidating existing content. I do not consider this a substantive change either, since the content model previously only allowed metadata.

Please review this latest draft carefully. This draft should replace the current CR draft shortly. Absent any objections on the list (i.e. silence will be deemed consent), I intend to convene a TTWG call on the 11th of June to formally move that TTML be advanced to PR.

[1] http://dev.w3.org/cvsweb/~checkout~/2008/tt/spec/ttaf1-dfxp.html?content-type=text/html;%20charset=utf-8


Sean Hayes