TTWG Meeting 2019-07-04

[nigelmegitt]

Agenda

1. This meeting
2. WebVTT
3. TTML2
4. AOB – please notify of any other AOB now!
4.1 TTWG Charter status

Time

15:00 - 16:00 (1 hour) 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=20190704T15&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: Andreas, Cyril, Philippe

Prioritise discussion for this meeting and look ahead

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

Note I did not raise w3c/tt-profile-registry#71 specifically on this agenda because I suspect that we will not have all of @mikedo , @cconcolato and @skynavga on the call - if that suspicion is wrong, we will try to cover that long-standing issue.

---

WebVTT

Implementation report: https://www.w3.org/wiki/TimedText/WebVTT_Implementation_Report

Web Platform Tests

Progress on test for unsigned short number space for lines

Specification edits

PR to add new at-risk features: w3c/webvtt#460

---

Agenda+ TTML2

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

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

---

Agenda+ AOB

TTWG Charter status update

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

[andreastai]

Regrets for this meeting

[plehegar]

Regrets for this meeting

[gkatsev]

I've created new issues for each test that is failing. There are two issues that potentially warrant discussion: w3c/webvtt#467 and w3c/webvtt#468. Though, in either case, I don't think either of them should block the at-risk CR from progressing.

[cconcolato]

Regrets for this meeting.

[nigelmegitt]

Minutes at https://www.w3.org/2019/07/04-tt-minutes.html