W3C home > Mailing lists > Public > public-tt@w3.org > January 2018

Scheduling of Topics in f2f-Meeting, 2017-01-09/2017-01-10, Cupertino

From: Andreas Tai <tai@irt.de>
Date: Fri, 5 Jan 2018 14:36:23 +0100
To: 'Timed Text Working Group' <public-tt@w3.org>
Message-ID: <001201d3862a$2da9af80$88fd0e80$@irt.de>
Dear Nigel, all,

As mentioned in the telco on 2017-01-04 I will participate in the next f2f
meeting remotely. Because I will be in the CET timezone, I would be grateful
if topics I either contributed to or plan to contribute could be dealt with
at the beginning of the meeting. 

It would be perfect for me, if we could start on Day 1 with the TTML1 issues
and on Day 2 with IMSC 1.1 issues. Part of the IMSC 1.1 issues, that could
dealt with at the beginning of Day2, include issue #275-#278 (how to handle
multiRowAlign, linePadding, activeArea and fillLineGap).

Below are a list of tickets where I am actively involved. For TTML2 there
are only two issues where my contribution may be helpful. The other issues I
opened seem already been resolved.

Best regards,


## TTMl1 
* https://github.com/w3c/ttml1/issues/251  (Use of attributes in TTML
namespace but NOT defined in TTML1)  

## IMSC 1.1
* #277 Should ebutts:multiRowAlign be deprecated?
* #278 Should ebutts:linePadding be deprecated? 
* #276 Should itts:fillLineGap be deprecated?
* #275 Should ittp:activeArea be deprecated?

## TTML2
* https://github.com/w3c/ttml2/issues/442 (Make backward compatibility
* https://github.com/w3c/ttml2/issues/439 (Foreign namespace elements not
reflected in syntax)

(Seem already to have been addressed)
* https://github.com/w3c/ttml2/issues/437 (Change summary not up to date)
* https://github.com/w3c/ttml2/issues/438  (Duplicated text for attributes
in TT Style Namespace)
Received on Friday, 5 January 2018 13:47:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:44:29 UTC