TTWG Meeting 2019-06-13

[nigelmegitt]

Agenda

1. This meeting
2. WebVTT transition to PR
3. TTML2 and TTML3 Pull Requests
4. TTML Profile Registry
5. PNG in PQ HDR
6. AOB – please notify of any other AOB now!
6.1 TTWG Charter status

Time

15:00 - 17:00 (2 hours) UTC

Please be ready for a prompt start at 15:03am UTC time.

Our teleconference is scheduled with reference to UTC Time, the correct time of this teleconference in your locale may change.

Check https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190613T15&p1=1440

Joining details:

see 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)

Future meetings and recent activity:

See the TTWG project board for upcoming meetings.

See individual agenda items for recent activity on specific products.

See the TTWG home page for links to repositories and recent activity.

---

Agenda+ This meeting

Assign Roles

Chairs: Nigel Megitt

Scribe: Cyril

Regrets: Thierry

Prioritise discussion for this meeting and look ahead

Check-point for order of topics and any other business.

---

WebVTT transition to PR

Implementation report: https://www.w3.org/wiki/TimedText/WebVTT_Implementation_Report
CfC: https://lists.w3.org/Archives/Public/public-tt/2019Jun/0008.html

What are the actions before proceeding with the request to transition?

• Test to verify that implementations pass when using int number space lines values

Open queries:

• text-wrap: balance email from Nigel
• text-combine: upright email from Pierre

Web Platform Tests

Specification edits

PR to remove at-risk features: w3c/webvtt#453

---

TTML2

Clarify use of 'applies to' in style property definition tables (#1088). w3c/ttml2#1089

There's a repeated comment on several of the following issues that "ruby container" is not a thing, and there's proposal separately to define it as a term, so that it can be used by reference in the proposed way. If we can get to consensus on which approach to take it may help resolve several of the subsequent issues.

Clarify text decoration application (#1078). w3c/ttml2#1079

Clarify text emphasis application (#1080). w3c/ttml2#1081

Clarify application of font selection strategy (#1082). w3c/ttml2#1083

Clarify application of font variant (#1084). w3c/ttml2#1085

Clarify text combine application (#1086). w3c/ttml2#1087

Emphasize null style semantics in context of ruby container spans (#1100). w3c/ttml2#1101

Add module framework (#1066). w3c/ttml2#1096

Merge policy

Reminder from the Chair of the merge policy for TTML repos:

• A pull request is treated as a call for consensus. A review "approval" is taken as a positive confirmation of agreement; a "request changes" is taken as an objection and blocks consensus.
• No pull request can be merged without at least one approval.
• If there is consensus after the Decision Period has elapsed, 10 working days, taken as 2 calendar weeks, then the pull request can be merged.
• In minor editorial cases such as obvious typos, approved pull requests with no "Request Changes" can be merged sooner.
• The Editor has some discretion, and needs to assess the complexity of the change and the likely need for review. If in doubt, leave for the full review period.
• If a Member wishes to request that a simple looking editorial change is nevertheless left open for a longer review period, they should do so on the pull request - a comment suffices.

The goal is that we have consensus for all changes merged into the ED to make transitioning to a published document a lighter task.

---

TTML Profile Registry

The codecs parameter should have a formal definition of the use of the combination operators. w3c/tt-profile-registry#71

---

Agenda+ PNG in PQ HDR

ICC Profile link broken w3c/png-hdr-pq#7

There's an outstanding question for @plehegar on this since February - can we bump it along?

---

Agenda+ AOB

TTWG Charter status update

Hopefully @plehegar can let us know if there's been progress since last time

[nigelmegitt]

@skynavga requested that we meet for 2 hours for this call.

The standing arrangement for 2 hour meetings is that we begin them at 1400 UTC, ie one hour earlier than normal, and end at the same time as normal.

However next week I have a clash with another W3C meeting (Positive Work Environment, since you ask, a thing I’m keen on promoting, and on learning about), so there was a suggestion that we instead begin at 1500 UTC and continue until 1700 UTC instead.

Proposal: Schedule this meeting for 2 hours beginning 1500 UTC

Please use 👍 and 👎 voting on this comment where:

• 👍 means you're fine with 1500-1700 UTC
• 👎 means 1500-1700 UTC causes you a problem

I'll take a view based on the votes when I prepare the agenda on Tuesday.

[skynavga]

👍

…

On Thu, Jun 6, 2019 at 10:30 AM Nigel Megitt ***@***.***> wrote: @skynavga <https://github.com/skynavga> requested that we meet for 2 hours for this call. The standing arrangement for 2 hour meetings is that we begin them at 1400 UTC, ie one hour earlier than normal, and end at the same time as normal. However next week I have a clash with another W3C meeting (Positive Work Environment, since you ask, a thing I’m keen on promoting, and on learning about), so there was a suggestion that we instead begin at 1500 UTC and continue until 1700 UTC instead. Proposal: Schedule this meeting for 2 hours beginning 1500 UTC Please use 👍 and 👎 voting on this comment where: - 👍 means you're fine with 1500-1700 UTC - 👎 means 1500-1700 UTC causes you a problem — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#42?email_source=notifications&email_token=AAC4E342KJJ3IBRT62LJEP3PZE3TVA5CNFSM4HMZPMY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXDNORA#issuecomment-499570500>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAC4E34HJA7AOFNJ32JYWR3PZE3TVANCNFSM4HMZPMYQ> .

[skynavga]

Nigel, Please place the following TTML2 issues on the agenda for the next meeting (in the indicated order). - #1107 <w3c/ttml2#1107> - #1089 <w3c/ttml2#1089> - #1079 <w3c/ttml2#1079> - #1081 <w3c/ttml2#1081> - #1083 <w3c/ttml2#1083> - #1085 <w3c/ttml2#1085> - #1087 <w3c/ttml2#1087> - #1101 <w3c/ttml2#1101> - #1096 <w3c/ttml2#1096> Of course, if any of these can be closed prior to the meeting, then we can remove from the agenda. Thanks, Glenn

…

On Thu, Jun 6, 2019 at 10:30 AM Nigel Megitt ***@***.***> wrote: @skynavga <https://github.com/skynavga> requested that we meet for 2 hours for this call. The standing arrangement for 2 hour meetings is that we begin them at 1400 UTC, ie one hour earlier than normal, and end at the same time as normal. However next week I have a clash with another W3C meeting (Positive Work Environment, since you ask, a thing I’m keen on promoting, and on learning about), so there was a suggestion that we instead begin at 1500 UTC and continue until 1700 UTC instead. Proposal: Schedule this meeting for 2 hours beginning 1500 UTC Please use 👍 and 👎 voting on this comment where: - 👍 means you're fine with 1500-1700 UTC - 👎 means 1500-1700 UTC causes you a problem — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#42?email_source=notifications&email_token=AAC4E342KJJ3IBRT62LJEP3PZE3TVA5CNFSM4HMZPMY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXDNORA#issuecomment-499570500>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAC4E34HJA7AOFNJ32JYWR3PZE3TVANCNFSM4HMZPMYQ> .

[skynavga]

I meant to say PRs, not issues.

…

On Thu, Jun 6, 2019 at 11:05 AM Glenn Adams ***@***.***> wrote: Nigel, Please place the following TTML2 issues on the agenda for the next meeting (in the indicated order). - #1107 <w3c/ttml2#1107> - #1089 <w3c/ttml2#1089> - #1079 <w3c/ttml2#1079> - #1081 <w3c/ttml2#1081> - #1083 <w3c/ttml2#1083> - #1085 <w3c/ttml2#1085> - #1087 <w3c/ttml2#1087> - #1101 <w3c/ttml2#1101> - #1096 <w3c/ttml2#1096> Of course, if any of these can be closed prior to the meeting, then we can remove from the agenda. Thanks, Glenn On Thu, Jun 6, 2019 at 10:30 AM Nigel Megitt ***@***.***> wrote: > @skynavga <https://github.com/skynavga> requested that we meet for 2 > hours for this call. > > The standing arrangement for 2 hour meetings is that we begin them at > 1400 UTC, ie one hour earlier than normal, and end at the same time as > normal. > > However next week I have a clash with another W3C meeting (Positive Work > Environment, since you ask, a thing I’m keen on promoting, and on learning > about), so there was a suggestion that we instead begin at 1500 UTC and > continue until 1700 UTC instead. > Proposal: Schedule this meeting for 2 hours beginning 1500 UTC > > Please use 👍 and 👎 voting on this comment where: > > - 👍 means you're fine with 1500-1700 UTC > - 👎 means 1500-1700 UTC causes you a problem > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#42?email_source=notifications&email_token=AAC4E342KJJ3IBRT62LJEP3PZE3TVA5CNFSM4HMZPMY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXDNORA#issuecomment-499570500>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAC4E34HJA7AOFNJ32JYWR3PZE3TVANCNFSM4HMZPMYQ> > . >

[nigelmegitt]

@skynavga Thank you for the advanced list. My usual practice is to assign issues and PRs with the “Agenda” label to the agenda when I prepare it, usually on a Tuesday.

[nigelmegitt]

Minutes at https://www.w3.org/2019/06/13-tt-minutes.html