Re: CfC: Request transition of TTML1 3ED to CR2

As an FYI, PLH's scheduling tool [1] shows an (earliest) date of October 30
for REC based on normal scheduling constraints. Note also that even if we
are ready to go to CR2 on 08/01, that due to other constraints, TTML1 CR2
couldn't be published until 08/07. Assuming the W3M will not accept the
request to shorten the 60 day exclusion period, this works out to a minimal
delay of 47 days for TTML2 (assuming TTML2 could have met its best case
dates in the first place). On the other hand, this will give 47 more days
before TTML2 has to go to PR (moving from August 9 to September 25), and
thus provide additional time for test construction and implementation
progress.

[1]
https://w3c.github.io/spec-releases/milestones/?cr=2018-08-01&noFPWD=true

On Tue, Jul 17, 2018 at 12:43 PM, Nigel Megitt <nigel.megitt@bbc.co.uk>
wrote:

> Thank you for this Pierre,
>
> This allows me to issue this Call for Consensus for requesting transition
> of TTML1 3rd Edition to CR2, noting that publication timetables mean that
> the deadline for comments of 23rd August will have to move later.
>
> As agreed <https://www.w3.org/2018/07/12-tt-minutes.html#resolution01>
> during last week's call please *review* the draft of TTML1 3rd Edition
> CR2 at https://rawgit.com/w3c/ttml1/feature/move-to-CR2-build/index.html with
> a view to agreeing to request transition to CR2. Comments can be made on pull
> request #357 <https://github.com/w3c/ttml1/pull/357> or raised as new
> issues on the repository.
>
> The review period for this Call for Consensus, according to our Decision
> Policy, ends at the end of 31st July 2018 (UK time).
>
> This version incorporates the following substantive changes:
>
> Merged #355 Update tts:lineHeight='normal' algorithm to match TTML2
> <https://github.com/w3c/ttml1/pull/355>
> Merged #356 Clarify the default value of blur radius for tts:textOutline
> <https://github.com/w3c/ttml1/pull/356>
>
> Those changes are both straight back-ports from changes already agreed for
> TTML2 CR2. When we request transition it is my intention to point to the
> existing TTML2 CR2 exclusion period and argue that these changes are *already
> covered* by the exclusion period for TTML2, and that we therefore do not
> need an additional exclusion period. Both the changes and their context of
> use are effectively the same. If I am successful in arguing this case, it
> should allow us to match our intention to reference TTML1 3rd Edition from
> TTML2, by the time we get to Rec.
>
> Regardless of this, we should request this transition (to TTML1 3rd Ed
> CR2) if we have consensus so to do.
>
> Kind regards,
>
> Nigel
>
>
> From: Pierre-Anthony Lemieux <pal@sandflow.com>
> Date: Tuesday, 17 July 2018 at 16:26
> To: Thierry MICHEL <tmichel@w3.org>, Nigel Megitt <nigel.megitt@bbc.co.uk>
> Cc: TTWG <public-tt@w3.org>
> Subject: TTML1 3ED CR2
>
> ​​
> Hi Thierry and Nigel,
>
> All outstanding PRs have been merged, and candidate TTML1 3ED CR2 is ready
> at:
>
> https://github.com/w3c/ttml1/pull/357
>
> Best,
>
> -- Pierre
>
>