- From: Thierry MICHEL <tmichel@w3.org>
- Date: Thu, 6 Jul 2017 11:24:10 +0200
- To: Nigel Megitt <nigel.megitt@bbc.co.uk>, Dae Kim <dakim@netflix.com>
- Cc: "public-tt@w3.org" <public-tt@w3.org>
Le 06/07/2017 à 10:53, Nigel Megitt a écrit :
> It's published. We don't generally make announcements when publishing a
> WD for WR but I think there may be a way to do so. Thierry, does the
> spec announce list (sorry, I forget its proper name) normally get used
> for WRs or just CRs?
We could use Chairs's list (this was used for former Last Call
announcement), and also public TT (Glenn already did it).
There is no specific process for a WD Wide Review. This specific WD step
does not exist in the W3C Process nor in the "W3C Technical Report
Transition document. But we are required to make a wide review.
As a matter of fact, a WD Wide Review is not a transition.
For CR, the W3C Communications Team sends a transition announcement to
w3c-ac-members@w3.org and chairs@w3.org and on the W3C home page.
>
> Additionally what we do normally do is send liaison messages out to
> request review. That's the next immediate step for TTML2.
Yes we will send messages to W3C Groups mentionned in the charter [1]
and external groups, like we recently did for IMSC.
Thierry
[1] https://www.w3.org/2016/05/timed-text-charter.html
>
> Nigel
>
>
> From: Dae Kim <dakim@netflix.com <mailto:dakim@netflix.com>>
> Date: Wednesday, 5 July 2017 at 21:55
> To: Nigel Megitt <nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk>>
> Cc: "public-tt@w3.org <mailto:public-tt@w3.org>" <public-tt@w3.org
> <mailto:public-tt@w3.org>>
> Subject: Re: {agenda} TTWG Meeting 2017-07-06
>
> Can we start with the WR status of TTML2?
> I believe we're ready but did not see any announcements.
>
> -Dae
>
> *Dae Kim | Senior Video Engineer | Encoding Technology*
> *9420 94f4 a834 b038 2920 34b3 38ad b632 3738 942c 942f*
>
> On Wed, Jul 5, 2017 at 9:48 AM, Nigel Megitt <nigel.megitt@bbc.co.uk
> <mailto:nigel.megitt@bbc.co.uk>> wrote:
>
> *This meeting is scheduled for up to 120m. Please be ready for a
> prompt start at 10:03am Boston time. *
>
> Our teleconference is scheduled with reference to Boston Time,
> the correct time of this teleconference in your locale may change.
>
> Check https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170706T10&p1=43
> <https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170706T10&p1=43>
>
> Thursdays 10:03am-12:00pm Boston local
>
> *Joining details: *
>
> see https://lists.w3.org/Archives/Member/member-tt/2016Oct/0009.html
> <https://lists.w3.org/Archives/Member/member-tt/2016Oct/0009.html>
> (members-only link – if you can't see this and wish to join
> please contact me)
>
> *Agenda+ Assign Roles*
>
> *Chairs: *Nigel Megitt
>
> *Scribe:* usually Nigel – open to offers!
>
> *Regrets: *Andreas
>
> *Activity since last meeting:** *
> See individual agenda items for recent activity on specific products
>
>
> Cross-product TTWG
> board: http://www.w3.org/AudioVideo/TT/board/
> <http://www.w3.org/AudioVideo/TT/board/>
>
> *We are still using tracker for /actions/ unrelated to issues.*
> *Please do not add or modify /issues/ in tracker!*
>
>
> IMSC: https://github.com/w3c/imsc/pulse
> <https://github.com/w3c/imsc/pulse>
> TTML1: https://github.com/w3c/ttml1/pulse
> <https://github.com/w3c/ttml1/pulse>
> TTML2: https://github.com/w3c/ttml2/pulse
> <https://github.com/w3c/ttml2/pulse>
> TTML Profile
> Registry: https://github.com/w3c/tt-profile-registry/pulse
> <https://github.com/w3c/tt-profile-registry/pulse>
> TTML-WebVTT
> mapping: https://github.com/w3c/ttml-webvtt-mapping/pulse
> <https://github.com/w3c/ttml-webvtt-mapping/pulse>
>
> WebVTT:* *https://github.com/w3c/webvtt/pulse
> <https://github.com/w3c/webvtt/pulse>
>
> *Agenda+ Prioritise discussion for this meeting and look ahead*
> *
> *
> Check-point for order of topics – I'd suggest, subject to
> reordering:
> 1. TPAC advanced planning
> 2. IMSC
> 3. TTML issue assignment and progress tracking
> 4. TTML1 & TTML2 issues, actions, PRs, editorial actions etc
> 5. WebVTT feedback (David Singer to Chair if present)
> 6. HDR in PNG
> 7. Progress on HTMLCue proposal (placeholder)
> 8. AOB – please notify of any other AOB now!
>
>
>
> Reminder re future milestones and meetings:
>
> _July Meetings:_
>
> Thursday 13th July: TTWG phone meeting 2 Hour(s)
> Thursday 20th July: TTWG phone meeting 2 Hour(s)
> Thursday 27th July: TTWG phone meeting 2 Hour(s)
>
> _Further ahead:_
> _
> _
> Thursday 3rd August: TTWG phone meeting ? Hour(s)
> Thursday 10th August: TTWG phone meeting ? Hour(s)
> Thursday 17th August: TTWG phone meeting ? Hour(s) - NM away
> Thursday 24th August: TTWG phone meeting ? Hour(s) - NM away
> Thursday 31st August: TTWG phone meeting ? Hour(s)
>
> _
> _
> _IMSC 2 and TTML2 publication events:_ see the timeline of
> upcoming work
> at _https://www.w3.org/wiki/TimedText/Publications#Timeline_of_TTML2_and_IMSC2_work
> <https://www.w3.org/wiki/TimedText/Publications#Timeline_of_TTML2_and_IMSC2_work> _
>
>
> *Agenda+ TPAC 2017 Advanced planning*
> *
> *
> As Chair I have completed the WBS survey, requesting:
>
> Attendance for ~10 people.
> No preference for date, meet on any two days.
> Flexible about days.
> Joint meeting with CSS WG and with Web and TV IG.
> Avoid overlap with Web and TV IG.
> Permit observers.
> Not member confidential.
> Estimate ~6 attending technical plenary.
> Estimate ~3 attending AC sessions Tuesday and Thursday.
>
> https://www.w3.org/2017/11/TPAC/Overview.html
> <https://www.w3.org/2017/11/TPAC/Overview.html>
> *
> *
> Chair was asked for further clarification about the joint
> meetings and the overlap avoidance; since Web and TV IG are
> likely to meet on the Monday, and CSSWG on the Monday and
> Tuesday, I requested Thursday and Friday for the main TTWG
> meetings with joint agenda slots with the other two groups on
> Monday and/or Tuesday.
>
> ID State Title Person Due Date Associated with
> ACTION-497
> <https://www.w3.org/AudioVideo/TT/tracker/actions/497>(edit)
> <https://www.w3.org/AudioVideo/TT/tracker/actions/497/edit>
> open Invite csswg to joint meeting at tpac 2017, with list of
> topics. <https://www.w3.org/AudioVideo/TT/tracker/actions/497>
> Nigel Megitt 2017-06-15
>
>
> _Collate list of the issues we want to open with CSS WG_
> _
> _
> We need to put this together as part of the agenda for a request
> to meet at TPAC.
>
>
> *Agenda+ IMSC (now incorporates Unicode ticket)*
>
> _IMSC1.0.1 Internationalisation issues_ (if Richard and/or
> Addison are able to attend)
>
> _Progress on publication of IMSC 1.0.1 CR_
>
> The transition request has been made with a request to proceed
> without a Director's call. However the team and Director has not
> managed to process this in time for publication on July 6th as
> requested.
>
>
> IMSC 1.0.1 WD for Wide Review published
> at https://www.w3.org/TR/ttml-imsc1.0.1/
> <https://www.w3.org/TR/ttml-imsc1.0.1/>
> IMSC 1 Rec available
> at https://www.w3.org/TR/2016/REC-ttml-imsc1-20160421/
> <https://www.w3.org/TR/2016/REC-ttml-imsc1-20160421/>
> Patent policy call for exclusions sent 2017-02-03, archived
> at https://lists.w3.org/Archives/Public/public-tt/2017Feb/0006.html
> <https://lists.w3.org/Archives/Public/public-tt/2017Feb/0006.html>
>
> Editor's draft is directly viewable
> at http://w3c.github.io/imsc/imsc1/spec/ttml-ww-profiles.html
> <http://w3c.github.io/imsc/imsc1/spec/ttml-ww-profiles.html>
> IMSC Implementation
> Page: https://www.w3.org/wiki/TimedText/IMSC1_implementation_page <https://www.w3.org/wiki/TimedText/IMSC1_implementation_page>.
> IMSC Tests repository: https://github.com/w3c/imsc-tests
> <https://github.com/w3c/imsc-tests>
>
> *Unicode CLDR discussion*
> Unicode ticket is at http://unicode.org/cldr/trac/ticket/8915
> <http://unicode.org/cldr/trac/ticket/8915>
> Pierre's response to the recent update is
> at http://unicode.org/cldr/trac/ticket/8915#comment:9
> <http://unicode.org/cldr/trac/ticket/8915#comment:9>
> Email response from Shervin at
> Unicode https://lists.w3.org/Archives/Public/public-tt/2016Dec/0018.html
> <https://lists.w3.org/Archives/Public/public-tt/2016Dec/0018.html>
>
> Merged IMSC pull requests: None
>
> Open IMSC pull requests: None
>
> New or discussed IMSC issues: None
>
> Closed IMSC issues:
>
> Should the character sets be minimum *font* requirements?
> <https://github.com/w3c/imsc/issues/236>
>
> Prepare CR draft <https://github.com/w3c/imsc/issues/244>
>
> ittp:activeArea clarification
> <https://github.com/w3c/imsc/issues/227>
>
> Determination of the color in leading in tts:fillLineGap
> <https://github.com/w3c/imsc/issues/228>
>
> Publish CR <https://github.com/w3c/imsc/issues/248>
>
> Merged IMSC Tests pull requests: None
>
> Open IMSC Tests pull requests: None
>
> New or discussed IMSC Tests issues:
>
> Text does not overflow in WrapOption00X.ttml
> <https://github.com/w3c/imsc-tests/issues/22>
>
> Closed IMSC Tests issues: None
>
>
> *Agenda+ TTML issue assignment and progress tracking (20 minutes
> maximum)*
>
> We have now published the WD for WR however there are still many
> issues open, and we intend also to apply multiple fixes as
> already agreed for TTML1.
>
> At the moment of writing this agenda, there are:
>
> TTML1 issues:
>
> * 28 open issues with no milestone, 1 (#199) marked as
> discussed and agreed
> * 48 open issues in "3rd Ed" milestone, 14 marked as discussed
> and agreed
>
> TTML2 issues:
>
> * 1 open issues on the Editor's WR Work List milestone, of
> which 1 is not labelled as "PR Open";
> * 50 open issues with no milestone, all of which have no PR, and
> * 7 open issues awaiting some feedback on disposition, which
> are in the "Group's WR action required list" milestone,
> including #316 which is to review the deprecations before
> finalising the WR.
>
>
> *Agenda+ TTML1 & TTML2 issues, actions, PRs, editorial actions etc*
>
> Horizontal Review:
>
> CSS Review of TTML2, threads: FW: TTML2 horizontal review with
> CSS
> <https://lists.w3.org/Archives/Public/public-tt/2016Dec/0013.html> and Fwd:
> Subtitle/caption styling + TTML + CSS
> <https://lists.w3.org/Archives/Public/public-tt/2016Dec/0019.html>
>
> Internationalisation review by r12a has generated several new
> issues on TTML2 and comments on existing issues (see below),
> this week mainly about alignment with relatively recent CSS
> developments.
>
> CSS 2.2 request for reviews from TTWG et al: Pre-announcement of
> CR for CSS 2.2 & request for reviews
> <https://lists.w3.org/Archives/Public/public-tt/2016Dec/0017.html> When
> can we schedule a review and gather feedback?
>
> Actions:
> ID State Title Person Due Date Associated with
> ACTION-443
> <https://www.w3.org/AudioVideo/TT/tracker/actions/443>(edit)
> <https://www.w3.org/AudioVideo/TT/tracker/actions/443/edit>
> open Prepare a document showing mapping arib ruby extension
> features to ttml2 for use as a liaison document to arib.
> <https://www.w3.org/AudioVideo/TT/tracker/actions/443> Glenn
> Adams 2016-08-26 TTML2
> <https://www.w3.org/AudioVideo/TT/tracker/products/4>
> ACTION-462
> <https://www.w3.org/AudioVideo/TT/tracker/actions/462>(edit)
> <https://www.w3.org/AudioVideo/TT/tracker/actions/462/edit>
> open Create issue on ttml2 to add "mapping from other versions
> and profiles of ttml"
> <https://www.w3.org/AudioVideo/TT/tracker/actions/462> Glenn
> Adams 2016-04-28 TTML2
> <https://www.w3.org/AudioVideo/TT/tracker/products/4>
>
>
> Most recent WD published
> at https://www.w3.org/TR/2017/WD-ttml2-20170106
> <https://www.w3.org/TR/2017/WD-ttml2-20170106>/
>
> Merged TTML1 Pull Requests: None
> Merged TTML2 Pull Requests:
>
> Add audio related features (#195).
> <https://github.com/w3c/ttml2/pull/396>
>
> Open TTML1 Pull Requests: None
>
> Open TTML2 Pull Requests: None
>
> New TTML1 Issues: None
>
> New TTML2 Issues: None
>
> Closed TTML1 Issues: None
> Closed TTML2 Issues:
>
> Add support for Audio Description requirements
> <https://github.com/w3c/ttml2/issues/195>
>
> Discussed TTML1 Issues: None
> Discussed TTML2 Issues: None
>
> Questions about ttp:mediaOffset
> <https://github.com/w3c/ttml2/issues/323>
>
>
> *Focus topic(s) for this week*
>
> What should we focus on next while TTML2 is in WR – TTML1 3rd Ed?
>
> _Issues_
>
> *Iterate through open issues with no PR* – decide action to take
> on each, e.g. defer to CR, defer to TTML.next, close etc.
>
> If there are any issues that we decide need to be resolved
> before WR *a proposal for the fix* is needed ASAP (basically,
> it's too late already unless it can easily be agreed by the group).
>
>
> Current open issues: https://github.com/w3c/ttml1/issues
> <https://github.com/w3c/ttml1/issues> and https://github.com/w3c/ttml2/issues
> <https://github.com/w3c/ttml2/issues>
> See spreadsheet of editorial actions
> at https://github.com/w3c/ttml2/blob/master/spec/ednotes.xlsx
> <https://github.com/w3c/ttml2/blob/master/spec/ednotes.xlsx>
> Edit/build instructions now in README in ttml2/spec/
> at https://github.com/w3c/ttml2/blob/master/spec/README.md
> <https://github.com/w3c/ttml2/blob/master/spec/README.md>
>
>
> *Agenda+ WebVTT review feedback*
>
> ID State Title Person Due Date Associated with
> ACTION-396
> <https://www.w3.org/AudioVideo/TT/tracker/actions/396>(edit)
> <https://www.w3.org/AudioVideo/TT/tracker/actions/396/edit>
> open Produce evidence of request for wide review for webvtt,
> for the archive
> <https://www.w3.org/AudioVideo/TT/tracker/actions/396> David
> Singer 2015-04-17 WebVTT 1.0
> <https://www.w3.org/AudioVideo/TT/tracker/products/8>
>
>
> _Discussion on WebVTT review feedback and next steps._
>
> What are the WG's views on the dispositions generated by the CG?
>
> _Resolve to publish a new WD? (not strictly necessary)_
>
> WebVTT Wide review wiki
> page: https://www.w3.org/wiki/WebVTT_Wide_Review
> <https://www.w3.org/wiki/WebVTT_Wide_Review>
>
> Open Pull requests:
>
> Prepare a new WD. <https://github.com/w3c/webvtt/pull/351>
>
> Merged Pull requests: None
>
> New issues: None
> Closed issues: None
>
> Recently discussed issues:
>
> Prepare a new WD. <https://github.com/w3c/webvtt/pull/351>
>
>
>
> *Agenda+ HDR in PNG*
>
> Repo for PQ HDR in PNG: https://github.com/w3c/png-hdr-pq
> <https://github.com/w3c/png-hdr-pq>
> Draft WG Note: https://w3c.github.io/png-hdr-pq/
> <https://w3c.github.io/png-hdr-pq/>
>
> Merged pull requests: none
>
> Open pull requests:
>
> Clarifies fallback strategy and editorial clean-up
> <https://github.com/w3c/png-hdr-pq/pull/4>
>
> New or discussed issues:
>
> Clarifies fallback strategy and editorial clean-up
> <https://github.com/w3c/png-hdr-pq/pull/4>
>
> Closed issues: None
>
> Note that there has been some positive feedback about the
> direction of this recently.
>
> *Agenda+ **HTMLCue proposal progress update.*
>
> ID State Title Person Due Date Associated with
> ACTION-441
> <https://www.w3.org/AudioVideo/TT/tracker/actions/441>(edit)
> <https://www.w3.org/AudioVideo/TT/tracker/actions/441/edit>
> open Kick off the analysis work on the vttcue carrying html
> idea. <https://www.w3.org/AudioVideo/TT/tracker/actions/441>
> Andreas Tai 2015-11-05
>
>
> See https://lists.w3.org/Archives/Public/public-tt/2016Apr/0012.html
> <https://lists.w3.org/Archives/Public/public-tt/2016Apr/0012.html> for
> further information on this, this week.
>
> Also HTML import and HTMLCue?
> <https://lists.w3.org/Archives/Public/public-tt/2016Sep/0003.html> email
> from 2016-09-06.
>
> [placeholder agenda item]
>
>
> *Agenda+ AOB*
>
> *References*
>
> Wiki http://www.w3.org/wiki/TimedText
> <http://www.w3.org/wiki/TimedText>
>
>
>
Received on Thursday, 6 July 2017 09:24:29 UTC