Re: Transition Request to CR for IMSC1.0.1

Le 12/07/2017 à 16:14, Xueyuan a écrit :
>
> Hi Thierry,
>
> On 12/07/2017 18:41, Thierry MICHEL wrote:
>> Xueyuan
>>
>> Sure, I had drafted ACs announcement a few days ago and got it
>> validated by PLH.
> Thank you for your quick response and the draft. Wrt comment on this
> document, is there somewhere people can learn about issues raised during
> the CR review period (e.g., a link to an GitHub issues list)?


https://github.com/w3c/ttml2/issues
and
W3C Public TTWG <public-tt@w3.org>

>>
>> For the home page news use the following:
> Got it. Thank you!
>
> Best Regards,
> Xueyuan
>>
>> This document specifies two profiles of [TTML1]: a text-only profile
>> and an image-only profile. These profiles are intended to be used
>> across subtitle and caption delivery applications worldwide, thereby
>> simplifying interoperability, consistent rendering and conversion to
>> other subtitling and captioning formats.
>> This revision of the IMSC1 adds two new features (ittp:activeArea and
>> itts:fillLineGap) to the Recommendation dated 21 April 2016
>>
>>
>> Best,
>> thierry
>> ________________________________________________________
>>
>>
>> Dear Advisory Committee Representative,
>> Chairs,
>>
>> I am pleased to announce that IMSC1.0.1 is a W3C Candidate
>> Recommendation:
>>
>> * Title: TTML Profiles for Internet Media Subtitles and Captions 1.0.1
>> (IMSC1)
>>
>> * URI:   https://www.w3.org/TR/2017/CR-ttml-imsc1.0.1-20170713/
>>
>> The approval and publication are in response to this transition request:
>>
>> https://lists.w3.org/Archives/Member/chairs/2017AprJun/0154.html
>>
>> Comments regarding this document are welcome. Please send them by
>> 2017-08-13 to public-tt@w3.org with [imsc] at the start of your
>> email's subject.
>>
>> This Candidate Recommendation is expected to advance to Proposed
>> Recommendation no earlier than 13 August 2017.
>>
>> This publication is the result of a revision of the IMSC1
>> Recommendation dated 21 April 2016, adding two new features (6.7.5
>> ittp:activeArea and 6.7.6 itts:fillLineGap features).
>> This document is designed such that Processors and document instances
>> that conform to the Recommendation dated 21 April 2016 also conform to
>> this revision.
>>
>> There were no Formal Objections.
>>
>> Patent disclosures relevant to this specification may be found on the
>> Timed Text Working Group's patent disclosure page in conformance with
>> W3C policy:
>>    https://www.w3.org/2004/01/pp-impl/34314/status
>>
>> As the Advisory Committee review begins at the same time as Candidate
>> Recommendation, you may start to review the specification and indicate
>> whether you endorse it as a W3C Recommendation or object to its
>> advancement by completing the following questionnaire:
>>    https://www.w3.org/2002/09/wbs/33280/IMSC101/
>>
>> The review will end no less than 4 weeks after publication as a
>> Proposed Recommendation. Additional details about the review are
>> available in the questionnaire.
>>
>> This Call for Implementations and Review follow section 6.4 "Candidate
>> Recommendation" of the W3C Process Document:
>>    https://www.w3.org/2017/Process-20170301/#candidate-rec
>>
>> Thank you,
>>
>> For Tim Berners-Lee, Director, and
>> Philippe Le Hégaret, Project Management Lead;
>> Xueyuan Jia, W3C Marketing & Communications
>>
>> ==============================================
>> Quoting from
>> TTML Profiles for Internet Media Subtitles and Captions 1.0.1 (IMSC1)
>> W3C Candidate Recommendation 13 July 2017
>>
>> This Version:
>>   https://www.w3.org/TR/2017/CR-ttml-imsc1.0.1-20170713/
>> Latest Published Version:
>>   https://www.w3.org/TR/ttml-imsc1.0.1/
>>
>>
>> Abstract:
>>
>> This document specifies two profiles of [TTML1]: a text-only profile
>> and an image-only profile. These profiles are intended to be used
>> across subtitle and caption delivery applications worldwide, thereby
>> simplifying interoperability, consistent rendering and conversion to
>> other subtitling and captioning formats.
>>
>> It is feasible to create documents that simultaneously conform to both
>> [ttml10-sdp-us] and the text-only profile.
>>
>> The document defines extensions to [TTML1], as well as incorporates
>> extensions specified in [ST2052-1] and [ EBU-TT-D].
>>
>> Both profiles are based on [SUBM].
>>
>>
>> Status of This Document:
>>
>> 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 document was published by the Timed Text Working Group as a
>> Candidate Recommendation. This document is intended to become a W3C
>> Recommendation. Comments regarding this document are welcome. Please
>> send them to public-tt@w3.org (subscribe, archives) with [imsc] at the
>> start of your email's subject. 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 13 August 2017.
>>
>> Please see the Working Group's implementation report.
>>
>> For this specification to exit the CR stage, at least 2 independent
>> implementations of every feature defined in this specification but not
>> already present in [IMSC1] need to be documented in the implementation
>> report. The implementation report is based on implementer-provided
>> test results for the exit criteria test suite. The Working Group does
>> not require that implementations are publicly available but encourages
>> them to be so.
>> The Working Group has not identified features "at risk" for this
>> specification.
>>
>> A list of the substantive changes applied since the initial Working
>> Draft is found at substantive-changes-summary.txt.
>>
>> This revision of the document is designed such that Processors and
>> document instances that conform to the Recommendation dated 21 April
>> 2016 also conform to this revision. As a result, review should focus
>> on the modifications made since the Recommendation dated 21 April
>> 2016, including the 6.7.5 ittp:activeArea and 6.7.6 itts:fillLineGap
>> features.
>>
>> For convenience, a complete diff between this version and the
>> Recommendation dated 21 April 2016 is found at diff.html.
>>
>> 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 5 February
>> 2004 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 March 2017 W3C Process Document.
>>
>>
>> -------------------------------------------------
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Thierry
>>
>> Le 12/07/2017 à 11:56, Xueyuan a écrit :
>>>
>>> Hi Thierry,
>>>
>>> Could you please provide a draft announcement (including an AC review
>>> form) for the IMSC1 CR publication?
>>>
>>> We also do Homepage news for CR publication. Please recommend a Homepage
>>> news draft, or we could post the default news generated based on the
>>> document's abstract.
>>>
>>> Regarding to the announcement to members, please see below for some
>>> reference info that you might need:
>>>
>>> Transition announcement should include the following info:
>>> https://www.w3.org/Guide/transitions?profile=CR&cr=new#trans-annc
>>>
>>> Template to easily generate the draft:
>>> https://www.w3.org/new-doc-from-template?location=%2FTeam%2F&template=%2Fafs%2Fw3.org%2Fpub%2FWWW%2FTeam%2FTemplates%2Fcfi.html&submit=Continue...
>>>
>>>
>>>
>>> Some samples at:
>>> https://www.w3.org/Search/Mail/Member/search?keywords=&hdr-1-name=subject&hdr-1-query=candidate+recommendation&index-grp=Member__FULL+Public__FULL&index-type=t&type-index=w3c-ac-members
>>>
>>>
>>>
>>> Regards,
>>> Xueyuan
>>>
>>>
>>> On 08/07/2017 03:23, Ralph Swick wrote:
>>>> I have reviewed this transition request.  On behalf of the Director I
>>>> approve TTML Profiles for Internet Media Subtitles and Captions 1.0.1
>>>> (IMSC1) as a Candidate Recommendation.
>>>>
>>>> -Ralph
>>>>
>>>> On 6/30/2017 10:18 AM, Thierry MICHEL wrote:
>>>>> Dear Director, PlH,
>>>>>
>>>>> This is a Transition Request from the Timed Text WG for publication
>>>>> of a Candidate Recommendation of the "TTML Profiles for Internet
>>>>> Media Subtitles and Captions 1.0.1 (IMSC1)".
>>>>>
>>>>> Transition details below.
>>>>>
>>>>>
>>>>> 1. Boilerplate ...
>>>>>
>>>>> * Document title: TTML Profiles for Internet Media Subtitles and
>>>>> Captions 1.0.1 (IMSC1)
>>>>>
>>>>> * Document URI:
>>>>> https://www.w3.org/TR/2017/CR-ttml-imsc1.0.1-20170706/
>>>>>
>>>>> Latest published version:
>>>>>      https://www.w3.org/TR/ttml-imsc1.0.1/
>>>>>
>>>>> * Estimated publication date: 06 July 2017
>>>>>
>>>>> * Abstract:
>>>>> This document specifies two profiles of [TTML1]: a text-only profile
>>>>> and an image-only profile. These profiles are intended to be used
>>>>> across subtitle and caption delivery applications worldwide, thereby
>>>>> simplifying interoperability, consistent rendering and conversion to
>>>>> other subtitling and captioning formats.
>>>>> It is feasible to create documents that simultaneously conform to
>>>>> both [ttml10-sdp-us] and the text-only profile.
>>>>> The document defines extensions to [TTML1], as well as incorporates
>>>>> extensions specified in [ST2052-1] and [ EBU-TT-D].
>>>>> Both profiles are based on [SUBM].
>>>>>
>>>>> * SotD:
>>>>>
>>>>>   This document was published by the Timed Text Working Group as a
>>>>> Candidate Recommendation. This document is intended to become a W3C
>>>>> Recommendation. Comments regarding this document are welcome. Please
>>>>> send them to public-tt@w3.org (subscribe, archives) with [imsc] at
>>>>> the start of your email's subject. 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 06 August 2017.
>>>>>
>>>>> Please see the Working Group's implementation report.
>>>>>
>>>>> For this specification to exit the CR stage, at least 2 independent
>>>>> implementations of every feature defined in this specification but
>>>>> not already present in [IMSC1] need to be documented in the
>>>>> implementation report. The implementation report is based on
>>>>> implementer-provided test results for the exit criteria test suite.
>>>>> The Working Group does not require that implementations are publicly
>>>>> available but encourages them to be so.
>>>>> The Working Group has not identified features "at risk" for this
>>>>> specification.
>>>>>
>>>>> A list of the substantive changes applied since the initial Working
>>>>> Draft is found at substantive-changes-summary.txt.
>>>>>
>>>>> This revision of the document is designed such that Processors and
>>>>> document instances that conform to the Recommendation dated 21 April
>>>>> 2016 also conform to this revision. As a result, review should focus
>>>>> on the modifications made since the Recommendation dated 21 April
>>>>> 2016, including the 6.7.5 ittp:activeArea and 6.7.6 itts:fillLineGap
>>>>> features.
>>>>>
>>>>> For convenience, a complete diff between this version and the
>>>>> Recommendation dated 21 April 2016 is found at diff.html.
>>>>>
>>>>> 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 5 February
>>>>> 2004 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 March 2017 W3C Process Document.
>>>>>
>>>>>
>>>>> 2. Record of the WG's Decision to request the CR Transition:
>>>>>
>>>>> The decision to advance this spec to CR is recorded in the following
>>>>> meeting minutes:
>>>>> [From the Minutes]:
>>>>> RESOLUTION: Publish IMSC 1.0.1 based on the current ED with request
>>>>> for review by August 6 assuming there are no changes due to comments
>>>>> by ARIB tomorrow and the differences issue is resolved.
>>>>> See
>>>>> https://www.w3.org/2017/06/29-tt-minutes.html
>>>>>
>>>>>
>>>>> Note: The "differences issue" shown in the resolution
>>>>> text quoted above is in fact resolved by generating the resource
>>>>> referenced by 3.
>>>>>
>>>>>
>>>>> 3. Report of Important Changes to the Document since the 30 September
>>>>> 2014
>>>>>
>>>>> A list of the substantive changes (only very few substantive changes)
>>>>> applied since the First Public Working Draft (02 February 2017) is
>>>>> available at
>>>>>
>>>>> https://www.w3.org/TR/2017/CR-ttml-imsc1.0.1-20170706/substantive-changes-summary.txt
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 4. Evidence that the document satisfies Group's Requirements:
>>>>>
>>>>> No requirements were defined for this specification in the Timed Text
>>>>> Working Group's charter at
>>>>> https://www.w3.org/2016/05/timed-text-charter.html
>>>>>
>>>>> 5. Evidence Dependencies With Other Groups Met:
>>>>>
>>>>> The specification has the following normative references:
>>>>> https://www.w3.org/TR/2017/CR-ttml-imsc1.0.1-20170706/#normative-references
>>>>>
>>>>>
>>>>>
>>>>> IMSC 1.0.1 includes 4 normative references to W3C specifications. All
>>>>> are W3C Recommendations.
>>>>>
>>>>> Dependencies with other groups have been explored and ensuing issues
>>>>> resolved during the previous WD version and during the wide review WD
>>>>> publication.
>>>>>
>>>>> Additionally, the Timed Text Working Group chairs and team contacts
>>>>> are
>>>>> confident that they do not have any dependencies with other working
>>>>> groups that have not been satisfied.
>>>>>
>>>>>
>>>>> 6. Evidence that the document has received Wide Review:
>>>>>
>>>>> This document is governed by the 1 March 2017 W3C Process Document.
>>>>> Therefore no Last Call WD was published but the last WD publication
>>>>> (22 March 2017) triggered a call for review with the same
>>>>> requirements as a Last Call WD.
>>>>>
>>>>> This version of IMSC1 makes editorial corrections and adds two
>>>>> optional features (6.7.5 ittp:activeArea and 6.7.6 itts:fillLineGap)
>>>>> over the Recommendation dated 21 April 2016. Processors and document
>>>>> instances that conform to the Recommendation dated 21 April 2016 also
>>>>> conform to this version of the specification.
>>>>>
>>>>> The specification has been widely reviewed both by public commenters,
>>>>> by other W3C working groups and by key participants involved in work
>>>>> at other organizations.
>>>>>
>>>>> The Timed Text Working Group requested review from WGs those listed
>>>>> for
>>>>> coordination in the TTWG Charter. The chairs of the working group
>>>>> listed have been copied on the distribution list of this transition
>>>>> announcement as well as other individuals known to have expressed
>>>>> prior interest.
>>>>>
>>>>> * Dependencies with W3C Groups (Listed in the TTWG charter)
>>>>>      - Web Platform Working Group
>>>>>      - Accessible Platform Architectures (APA) Working Group
>>>>>      - CSS Working Group
>>>>>
>>>>> * Liaisons with W3C Groups: (Listed in the TTWG charter)
>>>>>      - Web and TV Interest Group
>>>>>      - Web Media Text Tracks Community Group
>>>>>      - Internationalization (i18n) Working Group
>>>>>
>>>>> * Additional W3C Groups: (Not listed in the TTWG charter)
>>>>>      - Privacy Interest Group
>>>>>      - Web Security Interest Group
>>>>>      - TAG / Self-Review Questionnaire
>>>>>
>>>>> * External Groups
>>>>>
>>>>>      - ISO/IEC JTC-1/SC-29 WG 11 Moving Picture Experts Group (MPEG)
>>>>>      - Society of Motion Picture and Television Engineers (SMPTE)
>>>>>      - European Broadcasting Union (EBU)
>>>>>      - Digital Entertainment Content Ecosystem (DECE)
>>>>>      - DVB Project: Technical Module (DVB-TM)
>>>>>      - Advanced Television Systems Committee (ATSC)
>>>>>      - Association of Radio Industries and Businesses (ARIB)
>>>>>
>>>>> * Additional External Groups (Not listed in the TTWG charter)
>>>>>
>>>>>      - TTA
>>>>>      - ITU-T Group 16 IPTV
>>>>>      - IPTV Forum Japan
>>>>>      - HbbTV
>>>>>      - ETSI MCD
>>>>>      - DLNA
>>>>>      - DTG
>>>>>      - DASH-IF
>>>>>      - CTA
>>>>>      - 3GPP
>>>>>
>>>>> 7. Evidence that Issues Have Been Formally Addressed:
>>>>>
>>>>> During the wide review period, 13 comments were raised.
>>>>>
>>>>> - 13 comments were processed by the TTWG. Proposals were either
>>>>> approved by commenter or didn't received any feedback to the TTWG
>>>>> response.
>>>>>
>>>>> Comments, Messages responding to individual commenters and responses
>>>>> from commenters are available in the
>>>>> Disposition of comments for the Timed Text Working Group
>>>>> https://www.w3.org/wiki/IMSC1.0.1_Comments_tracker
>>>>>
>>>>>
>>>>> 8. Objections:
>>>>>
>>>>> There are no Formal Objection from a TTWG Member or other parties,
>>>>> during the preparation of this specification.
>>>>>
>>>>>
>>>>> 9. Features marked as "at risk":
>>>>>
>>>>> The Working Group has not identified features "at risk" for this
>>>>> specification.
>>>>>
>>>>> 10. Implementation Information:
>>>>>
>>>>> CR exit criteria from the SoTD section:
>>>>>
>>>>> "For this specification to exit the CR stage, at least 2 independent
>>>>> implementations of every feature defined in this specification but
>>>>> not already present in [IMSC1] need to be documented in the
>>>>> implementation report. The implementation report is based on
>>>>> implementer-provided test results for the exit criteria test suite.
>>>>> The Working Group does not require that implementations are publicly
>>>>> available but encourages them to be so."
>>>>>
>>>>> A first draft of the IMSC1.0.1 implementation report is available at
>>>>> https://www.w3.org/wiki/TimedText/IMSC1_0_1_Implementation_Report
>>>>>
>>>>> CR Test Suite:
>>>>> A preliminary testsuite (a repository of subtitle documents
>>>>> conforming to IMSC 1.0.1) is available, but we expect it to evolve
>>>>> significantly during the CR stage.
>>>>>
>>>>> https://www.w3.org/TR/2017/CR-ttml-imsc1.0.1-20170706/exit-criteria-tests/
>>>>>
>>>>>
>>>>>
>>>>> The new features have been already deployed in one implementation.
>>>>>
>>>>> The TTWG will collect additional implementation experience that will
>>>>> help demonstrate interoperability according to the CR exit criteria.
>>>>>
>>>>>
>>>>> 11. Patent Disclosures: none
>>>>> https://www.w3.org/2004/01/pp-impl/34314/status
>>>>>
>>>>> This document is governed by the 1 March 2017 W3C Process Document.
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> Nigel Megitt, Chair of the Timed Text Working Group.
>>>>> Thierry Michel, Team Contact for the Timed Text Working Group.
>>>>
>>>
>>
>

Received on Wednesday, 12 July 2017 15:44:03 UTC