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

No I was not suggesting a CR3.

On Wed, Jul 18, 2018 at 10:52 AM Nigel Megitt <nigel.megitt@bbc.co.uk>
wrote:

> Thanks both.
>
> Glenn, are you suggesting that if we were to prepare a minimal TTML2 CR3
> that references TTML1 3rd Ed and would publish both TTML1 3rd Ed CR2 and
> TTML2 CR3 on the same day then that would still work within the timescales
> that you are hoping for, and that the extra testing and implementation time
> would indeed be helpful? At this stage, if we are able to move to a mode
> where we keep TTML1 and TTML2 publications "locked" together, I would
> welcome that.
>
> Kind regards,
>
> Nigel
>
>
> From: Thierry MICHEL <tmichel@w3.org>
> Date: Wednesday, 18 July 2018 at 07:46
> To: Glenn Adams <glenn@skynav.com>, Nigel Megitt <nigel.megitt@bbc.co.uk>
> Cc: TTWG <public-tt@w3.org>, Pierre-Anthony Lemieux <pal@sandflow.com>
> Subject: Re: CfC: Request transition of TTML1 3ED to CR2
>
> Here is a proposed  TML1 3rd Edition CR2 Publication timeline
>
> July 17th Nigel sends TTML1 3Ed CfC  (14 days period)  - Done -
> July 31th end of CfC
> Aug 01st Pierre sends  TTML1 3Ed final document
> Aug 02nd Thierry upload document at final destination on TR and checks
> TTML1 3Ed CR against validators
> Aug 02nd  Thierry sends TTML1 3Ed CR2 Transition request to director
> (needs about a week for approval)
> Aug 07th Thierry sends TTML1 3Ed CR2 Publication request to webmaster
> (needs 1 or 2 days ahead of publication)
> Aug 07th Thierry sends TTML1 3Ed CR2 announcement draft to com team
> Aug 09th TTML1 3Ed CR2 Publication
>
> September 6th : Deadline for comments
> September 18th :request to Proposed Recommendation, showing adequate
> implementation experience
> October 8th : Last day of the 60 days exclusion opportunity
>
> Thierry
>
>
>
> On 17/07/2018 21:47, Glenn Adams wrote:
>
> 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
>>
>>
>
>
>
> ----------------------------
>
> http://www.bbc.co.uk
> This e-mail (and any attachments) is confidential and may contain personal
> views which are not the views of the BBC unless specifically stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in
> reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
>
> ---------------------
>