-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TTWG Meeting 2024-09-27 TPAC In person / hybrid all day #291
Comments
I'd love to get this PR merged, or discuss any blocking feedback... Above PR resolves: As you're aware, the motivating use case is to enable a new web standard accessibility feature for conveying times of flashing lights common in movies and other streaming video. The above issue and PR are effectively blocking prerequisites for: We should meet either way, since even if PR 523 is resolved by then, there could be additional discussion for how to manage the registry of different metadata type values (e.g. "video.strobing.general-flash") and their respective specifications, including but not limited to the flashing lights use case. |
Agenda+ @palemieux present considerations for a new edition of IMSC |
Agenda+ @nigelmegitt Run-through of work needed to take TTML2 Second Edition from CR to Rec. |
Agenda+ request from @marcoscaceres to present and discuss on improvements to WebVTT Interop testing, 30-45 minutes. |
@cookiecrook hey, we're looking to schedule a slot for WebVTT for Friday afternoon. I was wondering if you had any time constraints on that. Thanks! |
@eric-carlson expressed a preference to complete WebVTT items by 3pm when he will need to leave. |
I can work around Eric's schedule. The following are the times I can be available on Thursday and Friday
|
With @gkatsev’s feedback this week on w3c/webvtt#523, I have enough to work on. Thank you! Happy to meet Friday if you’d still like to, or I can yield that time. Either is fine with me. |
Topics
Agenda for today:
10:30-11:00 break
12:30-14:00 lunch
|
See also the TTWG Wiki page for TPAC 2024.
The text was updated successfully, but these errors were encountered: