Re: [DRAFT-V2] Transition request: TTML2 to Candidate Recommendation - Second version (CR2).

Thanks Thierry,

Aside from the links that will need updating, just one comment on the changed text, and one typo spotted, inline below.

Nigel


From: Thierry MICHEL <tmichel@w3.org<mailto:tmichel@w3.org>>
Date: Monday, 18 June 2018 at 15:31
To: Nigel Megitt <nigel.megitt@bbc.co.uk<mailto:nigel.megitt@bbc.co.uk>>
Cc: W3C Public TTWG <public-tt@w3.org<mailto:public-tt@w3.org>>
Subject: Re: [DRAFT-V2] Transition request: TTML2 to Candidate Recommendation - Second version (CR2).


Nigel,

Following is a V2 of the Transition draft for TTML2 to Candidate Recommendation - Second version (CR2).
Please let me know if you are OK and I will send it to director, etc.

Thierry
 ______________________


This is a Transition request: TTML2 to Candidate Recommendation - Second version (CR2).

# Document title, URLs, estimated publication date

Timed Text Markup Language 2 (TTML2)
W3C Candidate Recommendation 28 June 2018

ED: https://rawgit.com/w3c/ttml2/ga/cr2-cfc-build/index.html


# Abstract

https://rawgit.com/w3c/ttml2/ga/cr2-cfc-build/index.html#abstract


# Status

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.


This is the Second Candidate Recommendation (CR2) of the Timed Text Markup Language 2 (TTML2), and is intended to be progressed to a W3C Recommendation. If you wish to make comments regarding this document, please file an issue on GitHub or send email to public-tt@w3.org<mailto:public-tt@w3.org> (subscribe, archives) with a subject line starting with [ttml2]. W3C publishes a Candidate Recommendation to indicate that the document is believed to be stable and to encourage implementation by the developer community. This Candidate Recommendation is expected to advance to Proposed Recommendation no earlier than 9 August 2018.

For this specification to exit CR, the following criteria must be met, as documented in the Working Group's implementation report. For each feature introduced in this specification:

    At least two independent implementations must support the feature. If both transformation semantics and presentation semantics are defined for the feature, then at least one implementation must be a transformation processor and at least one implementation must be a presentation processor;

    At least one of those implementations must be a validating processor that successfully verifies valid or invalid use of the feature as applicable.

The following features are at-risk, and may be dropped during the CR period:

    #animation-version-2
    #border-radii
    #bpd
    #display-inlineBlock
    #extent-measure
    #font
    #fontSelectionStrategy-character
    #ipd
    #lineShear
    #rubyAlign-withBase
    #shear
    #textOrientation-sideways-LR
    #validation

The term “at-risk” is a W3C Process term-of-art, and does not necessarily imply that the feature is in danger of being dropped or delayed. It means that the Working Group believes the feature may have difficulty being interoperably implemented in a timely manner, and marking it as such allows the Working Group to drop the feature if necessary when transitioning to the Proposed Recommendation stage without having to publish a new Candidate Recommendation omitting the feature.

A cumulative summary of all changes applied to this version since the current (TTML1, 2nd Edition) Recommendation was published is available at Timed Text Markup Language 2 (TTML2) Change Summary. An abbreviated list of changes affecting language syntax can be found at U Changes to Vocabulary from TTML1.

This document has been produced by the Timed Text (TT) Working Group as part of the W3C Video in the Web Activity, following the procedures set out for the W3C Process. The authors of this document are listed in the header of this document.

Publication as a Candidate Recommendation does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 1 February 2018 W3C Process Document.


# Link to group's decision to request transition

Call for Consensus to request transition of TTML2 to CR2 is available at

https://lists.w3.org/Archives/Public/public-tt/2018Jun/0083.html


The CfC says "if no objection to requesting transition is received by end of Tuesday 26th June then the Resolution is passed and I will request the transition to CR2".
During the June 14th TTWG call, PlH said that if we would request Transition to CR2 before 21st June, we could be able to publish CR2 on June 28th, pending there are no objection raised before June 26th.


# Changes

Several substantive changes since previous CR1 publication (March 13th 2018),
https://rawgit.com/w3c/ttml2/ga/cr2-cfc-build/ttml2-changes.html#change-history-ttml2-cr1-to-ttml2-cr2


Note the W3C HTML Diff service may not be working:
https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2F2018%2FCR-ttml2-20180313%2F&doc2=https%3A%2F%2Frawgit.com%2Fw3c%2Fttml2%2Fga%2Fcr2-cfc-build%2Findex.html


Therefore we also provide a static Diff file between CR1 and CR2 is available at
https://www.w3.org/2018/06/ttml2-cr-diff.html



Commits:
https://github.com/w3c/ttml2/commits/master


# Requirements satisfied

The goal of TTML2 remains valid as in the requirements document at

The requirements document does not define the goal of TTML2, so change this statement to:

TTML2 Appendix M describes how TTML2 satisfies the requirements document at:


https://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427/.



 # Dependencies met (or not)

The Working Group maintains ongoing liaisons with various groups,
inlcuding SMPTE, EBU.

s/inlcuding/including



For wide reviews, the Group reached the Media and Enternaiment IG,
Privacy IG< Web Security IG, I18n, APA, Web Media Text Tracks CG, Web
Platform WG, CSS WG, TAG.


# Wide Review

https://lists.w3.org/Archives/Public/public-tt/2017Jul/0041.htmlhttps://github.com/w3c/i18n-activity/issues/428https://lists.w3.org/Archives/Public/public-tt/2017Jul/0069.htmlhttps://lists.w3.org/Archives/Public/public-tt/2017Jul/0062.htmlhttps://lists.w3.org/Archives/Public/public-tt/2017Aug/0015.htmlhttps://lists.w3.org/Archives/Public/public-tt/2017Sep/0071.htmlhttps://lists.w3.org/Archives/Public/public-tt/2017Oct/0032.html


# Issues addressed

The closed issues are at https://github.com/w3c/ttml2/milestone<https://github.com/w3c/ttml2/milestone/2?closed=1>

CR2 issues are relevant to publication
https://github.com/w3c/ttml2/milestone/2



# Formal Objections

None

# Implementation

Refer to above SotD, for exit criteria (remaining the same as CR1) and for list of features at risk.

Refer to implementation report for implementation experience.
https://www.w3.org/wiki/TTML/TTML2ImplementationReport


 # Patent disclosures

None

https://www.w3.org/2004/01/pp-impl/34314/status



Regards,

Nigel Megitt, Chair of the Timed Text Working Group.
Thierry Michel, Team Contact for the Timed Text Working Group.













----------------------------

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.

---------------------