You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The expectation is that these editorial changes may be made without process issue.
IMSC vNext requirements window
As discussed in #117 the window for IMSC vNext requirements is now open. Placeholder agenda item for discussing closing date, scope etc.
ARIB incoming liaison
The ARIB issues have now been raised as separate GitHub issues, which we should iterate through over the coming weeks as time allows, with the scope of review being to collate any responses to be included in a response to ARIB, and any other actions.
Note that in previous meetings we managed to get through most of these, with discussion in the order listed below up to w3c/imsc#549. We did not conclude the discussion of w3c/imsc#550 during #121 so it remains on the agenda. Resulting actions to be collated at #116.
CSS font-matching algorithm may introduce fingerprinting issues w3c/ttml2#1202 (PING review)
Following the discussion in #121@nigelmegitt wrote to the Chairs of PING on Thursday 11th June, CC the two groups' team contacts, to request a joint meeting to try to resolve this remaining issue, and at the time of writing this (2020-06-16Z16:48) has not received a response.
Agenda+ AOB
The text was updated successfully, but these errors were encountered:
Agenda
1. This meeting
2. WebVTT
2.1 Where should "headers" go relative to the
WEBVTT
magic string? w3c/webvtt#4853. IMSC 1.2
3.1 PR Published
3.1.1 Late changes
3.2 IMSC vNext requirements window
3.3 ARIB incoming liaison #116
3.3.1 [WR/ARIB] Mixture of text and image w3c/imsc#5433.3.2 [WR/ARIB] Character Sets w3c/imsc#5443.3.3 [WR/ARIB] (meta) Compatibility with ARIB-TTML w3c/imsc#5453.3.4 [WR/ARIB] Compatibility with ARIB-TTML / 1. Image handling w3c/imsc#5463.3.5 [WR/ARIB] Compatibility with ARIB-TTML / 2. Font handling w3c/imsc#5473.3.6 [WR/ARIB] Compatibility with ARIB-TTML / 3. Animation w3c/imsc#5483.3.7 [WR/ARIB] Compatibility with ARIB-TTML / 4. Audio presentation w3c/imsc#5493.3.8 [WR/ARIB] Compatibility with ARIB-TTML / 5. Additional style control w3c/imsc#550
4. TTML2 2nd Edition Implementation Report
4.1 CSS font-matching algorithm may introduce fingerprinting issues w3c/ttml2#1202 (PING review)
5. AOB – please notify of any other AOB now!
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=20200618T15&p1=1440
Calendar for this meeting: https://www.w3.org/AudioVideo/TT/wip/meeting-20200618.ics
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:
Regrets:
Previous meeting: https://www.w3.org/2020/06/11-tt-minutes.html
Prioritise discussion for this meeting and look ahead
Check-point for order of topics and any other business.
WebVTT
Where should "headers" go relative to the
WEBVTT
magic string? w3c/webvtt#485Proposal from Roger Pantos to define this in the HLS RFC.
IMSC1.2
PR published
Published PR, dated version: https://www.w3.org/TR/2020/PR-ttml-imsc1.2-20200616/
Late changes
For PR:
Needed prior to Rec:
The expectation is that these editorial changes may be made without process issue.
IMSC vNext requirements window
As discussed in #117 the window for IMSC vNext requirements is now open. Placeholder agenda item for discussing closing date, scope etc.
ARIB incoming liaison
The ARIB issues have now been raised as separate GitHub issues, which we should iterate through over the coming weeks as time allows, with the scope of review being to collate any responses to be included in a response to ARIB, and any other actions.
Note that in previous meetings we managed to get through most of these, with discussion in the order listed below up to w3c/imsc#549. We did not conclude the discussion of w3c/imsc#550 during #121 so it remains on the agenda. Resulting actions to be collated at #116.
[WR/ARIB] Mixture of text and image w3c/imsc#543We discussed this at length in #117, so we may skip it this time.
[WR/ARIB] Character Sets w3c/imsc#544Proposal is in IMSC vNext to reference the ARIB set for "ja" language.
[WR/ARIB] (meta) Compatibility with ARIB-TTML w3c/imsc#545[WR/ARIB] Compatibility with ARIB-TTML / 1. Image handling w3c/imsc#546[WR/ARIB] Compatibility with ARIB-TTML / 2. Font handling w3c/imsc#547[WR/ARIB] Compatibility with ARIB-TTML / 3. Animation w3c/imsc#548[WR/ARIB] Compatibility with ARIB-TTML / 4. Audio presentation w3c/imsc#549[WR/ARIB] Compatibility with ARIB-TTML / 5. Additional style control w3c/imsc#550
We should work through these before returning to #116 to prepare a liaison response.
TTML2 2nd Edition Implementation Report
All tests are now completed in the w3c/ttml2-tests repo
Status of this? Does it reflect the test suite changes? @cconcolato volunteered to update it with the tests as we expect them to be.
https://www.w3.org/wiki/TimedText/TTML2SecondEditionImplementationReport
CSS font-matching algorithm may introduce fingerprinting issues w3c/ttml2#1202 (PING review)
Following the discussion in #121 @nigelmegitt wrote to the Chairs of PING on Thursday 11th June, CC the two groups' team contacts, to request a joint meeting to try to resolve this remaining issue, and at the time of writing this (2020-06-16Z16:48) has not received a response.
Agenda+ AOB
The text was updated successfully, but these errors were encountered: