W3C

Timed Text Working Group Teleconference

26 March 2020

Attendees

Present
Andreas, Atsushi, Cyril, Gary, Glenn, Nigel, Pierre
Regrets
-
Chair
Gary, Nigel
Scribe
cyril, nigel

Meeting minutes

<atsushi> (will join after i18n WG call ends,,, hope in short time)

This meeting

nigel: looking light today
… IMSC1.2, TTML2 2nd ed IR
… and some AOBs
… to alert people to minor tweaks in the charter

<atsushi> AOB+ added https://‌www.w3.org/‌TR/‌ttml-imsc/‌rec and it points to https://‌www.w3.org/‌TR/‌ttml-imsc1.1/ (got right now)

nigel: thanks to atsushi for preparing calendar files
… and about a joint session with PING
… any other business that other people want to add?

atsushi: I pasted it on IRC a new link
… which points to the latest IMSC spec

IMSC 1.2

nigel: the main news is we published CR
… thanks everybody

<nigel> IMSC 1.2 CR

nigel: we do expect to have an empty IR
… because it's a profile
… and the tests are already in TTML2
… we do have some editorial changes
… Pierre, any concern from an editorial perspective?

pal: yes
… my first concern is that I've not heard back from the commenter
… it's been 2 weeks ago

nigel: on accessibility?

pal: yes
… it could all be that this was confusion due to the spec not being clear
… a potential solution could be to add an introduction
… really editorial but some work
… I don't know how to get the commenter back

nigel: Given it's been a couple of weeks it's fine for me to poke that group

pal: If we meet with PING, we might do the same with APA

nigel: I'll propose that
… would you rather try and schedule that during the call or as a separate call?

pal: this is going to be detailed so not necessary to be in the call

cyril: we are not very busy in the calls these days, we could use them

atai: agree

nigel: for PING we may need a different time
… but for APA, I'll offer that time

nigel: other issues on IMSC1.2?
… similar concerns?

pal: no, the rest, I don't foresee any issue
… thanks again to everybody for getting to CR

TTML2 2nd Edition Implementation Report

nigel: thanks Glenn for the work on the tests
… I'm now up to date on all but 1
… the one I haven't managed to comment on is the one audio in body
… I'm aware that I'm going to be on the hook for providing implementation
… and I want to make sure our implementation is working
… my review approach has been checking the spec changes
… and that the tests match something sensible with the spec

glenn: you found a couple of good issues to fix, thanks
… I have a couple of minor issues to deal with
… early next week should be fixed

nigel: I'll keep reviewing them

glenn: you should be able to get one set of implementations through TTT next week
… I haven't checked other implementations

nigel: I encourage everybody else to have a look at the current PR
… the more eyes the better

cyril: anybody looked at the draft IR?

glenn: not yet

cyril: probably needs updating based on the new PRs

glenn: I'll get to that probably early next week

<nigel> TTML2 2nd Ed IR

nigel: with those pull requests, we add various test files, so we need to do a second pass
… anything else on TTML2?

Minor Charter updates

nigel: somehow we published the charter with "fix me" comments in the charter document
… atsushi noticed them and made some changes

atsushi: the changes are already live now

nigel: the changes section at the end and the team contact have been changed
… no need for approval from the team
… this is an informative item
… questions?

Calendar files in agendas

nigel: you might have noticed that this agenda included a link , in the time section to a *.ics file
… when we discussed the DST switch, someone suggested that we should have a calendar reminder
… we can now easily do it, thanks to Atsushi
… it seems to be possible to create an ICS with multiple meetings or per meeting
… the multiple meetings in one file did not work for me
… have a look
… every agenda issue has one of these things in it
… it's early days, any feedback is useful

<atsushi> https://‌calendar.google.com/‌calendar/‌embed?src=23takkp7lmcssc6b6ggmpr7m1mhfac2d%40import.calendar.google.com&ctz=Asia%2FTokyo

cyril: not sure it's that useful if the file changes every meeting

pal: agree with cyril

atsushi: I pasted into IRC, the one I added to my calendar
… you may get several events

https://‌calendar.google.com/‌calendar/‌embed?src=23takkp7lmcssc6b6ggmpr7m1mhfac2d%40import.calendar.google.com&ctz=Asia%2FTokyo

cyril: I don't have permission to view

<atsushi> https://‌www.w3.org/‌AudioVideo/‌TT/‌wip/‌meetings.ics

nigel: you need to be logged in Google

pal: I've just tried to add the ICS file and we'll see if it works

gkatsev: it looks like there is a way to make recurrent events in ICS
… the issue is that you have to do it manually

<gkatsev> ics reccurance rules

nigel: Is there general feeling that 1 ICS file with recurrence rule would be useful?

atsushi: until the next DST change it could work
… but I'm worried about recurrence after the next DST change

<nigel> TimeAndDate ICS generator

nigel: I could look at timeanddate creating the ICS

Arranging joint session with PING

nigel: pete said that he cannot make our time

nigel: what I'm tempted to do is suggest the hour afterwards

pal: I'll be available next week at the hour following the meeting

nigel: nice, for European folks that would be an hour later
… for US, it would be the same hour as today

nigel: I'll go back to PING and propose that

imsc/rec link

nigel: IMSC1.1 has a link to latest IMSC1 recommendation

<nigel> IMSC 1.1 has a link to "Latest IMSC1 recommendation:"

nigel: and it points to https://‌www.w3.org/‌TR/‌ttml-imsc1.0.1/

<nigel> is where it points

nigel: resolves to IMSC 1.0.1
… but I'm really expecting 1.1
… and when we publish 1.2 it should point to that

pal: yes, the link is broken

nigel: atsushi made some changes

<nigel> New "latest" link

atsushi: the /rec link is new and points to the latest recommendation of IMSC

<nigel> where it resolves to today

atsushi: regardless of the version of TTML IMSC
… now it is pointing to 1.1

nigel: thanks
… the proposal is that we do replacement of the latest IMSC1 link in IMSC1.1 to point to that /rec
… I think that's possible to do in-place

atsushi: yes

cyril: we also need to change the link in 1.0.1

nigel: yes

cyril: and also the 1.0 spec

https://‌www.w3.org/‌TR/‌2016/‌REC-ttml-imsc1-20160421/

nigel: there is also a banner that tells you it's outdated which points to IMSC1.0.1
… 1.0.1 is still out and is not superseeded

<atsushi> https://‌www.w3.org/‌TR/‌ttml-imsc1.0/

cyril: we should be clear that the latest IMSC1.0 is 1.0.1 but the latest IMSC is 1.1 and soon 1.2

nigel: right

cyril: we need 2 links: latest 1.0 spec and latest IMSC

pal: people who have kept a link to 1.0 and got there, see it's outdated, they should get a link to 1.0.1

nigel: agree
… I think where it says "Latest IMSC1 Recommendation" we need to say "Latest IMSC Recommendation" and point to the rec link
… that change applies to 3 current document: 1.0.1 REC, 1.1 REC and 1.2 CR

cyril: agree, but what do we do this link http://‌www.w3.org/‌TR/‌ttml-imsc1/?
… because strictly speaking the latest is 1.1 or 1.2

pal: historically, IMSC1 was IMSC1.0
… maybe it's not perfect, but not completely broken

nigel: if we change the link pointed to by http://‌www.w3.org/‌TR/‌ttml-imsc1/ we would need to change 1.0 and 1.0.1, and that's extra work
… my inclination is not to do this extra work

atsushi: I need a WG agreement and resolution

Resolution: Change "Latest IMSC1 Recommendation" to "Latest IMSC Recommendation" and point to the rec link in 3 current documents: 1.0.1 REC, 1.1 REC and 1.2 CR

nigel: in 1.2 we could wait for PR but it's confusing

atsushi: from a process point of view, there is no edited CR

pal: in the past, we made such minor changes without going through the process

nigel: let's try to do the resolution and revisit if we have a problem

atsushi: I will draft an email and CC Nigel

Meeting close

Nigel: Thanks everyone, that's our agenda completed, apologies we're 2 minutes over.
… [adjourns meeting]

Summary of resolutions

  1. Change "Latest IMSC1 Recommendation" to "Latest IMSC Recommendation" and point to the rec link in 3 current documents: 1.0.1 REC, 1.1 REC and 1.2 CR
Minutes manually created (not a transcript), formatted by scribe.perl version 114 (Tue Mar 17 13:45:45 2020 UTC).