16:01:05 RRSAgent has joined #tt 16:01:05 logging to https://www.w3.org/2019/01/24-tt-irc 16:01:07 RRSAgent, make logs public 16:01:07 Zakim has joined #tt 16:01:09 Meeting: Timed Text Working Group Teleconference 16:01:09 Date: 24 January 2019 16:01:16 Log: https://www.w3.org/2019/01/24-tt-irc 16:05:07 Present+ Andreas, Gary, Nigel 16:05:11 Regrets: Glenn 16:05:19 scribe: nigel 16:05:23 Chair: Nigel 16:05:38 Present+ Thierry 16:05:56 Agenda: https://github.com/w3c/ttwg/issues/13 16:06:10 Regrets+ Mike 16:06:23 Topic: This meeting 16:06:52 Nigel: Today we have one issue marked for agenda for TTML Profile Registry. 16:07:09 .. TTWG Future Reqs if there's anything to cover, 16:07:20 .. F2F meetings next week 16:07:28 .. TTML in RTP IETF submission 16:07:37 .. Is there any other business, or any specific points to raise? 16:07:53 .. I didn't have reason to add WebVTT to the agenda before, but there's been some discussion on 16:08:08 .. the reflector today, so we can add it if that would help? 16:08:29 Gary: Yes, we can cover WebVTT please. 16:08:31 Nigel: OK 16:08:55 group: [nothing more for the agenda] 16:09:23 Topic: TTML Profile Registry w3c/tt-profile-registry#58 Fix spec reference for etx2 to point to EBU-TT 1.1 16:09:35 github: https://github.com/w3c/tt-profile-registry/pull/58 16:09:43 cyril has joined #tt 16:09:49 Present+ Cyril 16:09:51 scribe: cyril 16:10:07 nigel: PR to fix etx2 16:10:21 ... I raised it, andreas reviewed it, open for 13days 16:10:37 ... it's ready for the editors to merge 16:11:27 SUMMARY: Editors to merge tomorrow at the earliest assuming no new objections 16:11:44 github-bot, end topic 16:11:50 topic: TTWG Future requirements 16:12:08 nigel: Is there anything specific to discuss? 16:12:25 ... there has been some discussion on embedded images 16:12:36 ... it's fine offline 16:12:57 ... no comment on that point 16:13:05 topic: Joint f2f meeting with EBU Timed Text, Feb 1 2019 16:13:50 nigel: I have updated the agenda 16:14:34 ... we need some time on WebVTT 16:14:47 ... I am not sure what the best time would be 16:14:57 gkatsev: day 1 would be good 16:15:46 cyril: If the discussions on the requirements I raised could be discussed at a convenient time for me 16:16:53 ... like 4pm geneva time 16:18:29 nigel: day 1 is mainly those requirements, TTML2, modularization ... 16:18:43 ... live demo as part of the PTS event 16:18:57 ... and the WebVTT implementation report 16:19:59 ... day 2 in the morning is the joint meeting about live ttml 16:20:11 ... and how we handle EBU defining semantics 16:20:31 ... like multiRowAlign but other contributions 16:20:38 ... we need to think about what the options are 16:20:49 ... if you have any other topic let me know 16:21:06 q? 16:21:46 topic: TTML in RTP IETF submission 16:22:05 nigel: we had a bit of feedback from Mike 16:22:20 ... my colleague James just updated a new draft 16:22:30 -> https://datatracker.ietf.org/doc/draft-sandford-payload-rtp-ttml/ RTP Payload for TTML Timed Text 16:22:54 ... one of the thing that generated discussion is the media type definition 16:23:27 ... there seems to be a best practice IETF document saying that you should register the media type for the payload format 16:23:41 ... that explains why the draft copies it 16:23:57 ... that's a bit bizarre 16:24:12 ... but it seems a recommended practice 16:24:23 ... the change control now says W3C has change control over this specification 16:25:20 s/register the media type/include the media type registration 16:25:34 s/bizarre/bizarre (to me, personally) 16:25:57 ... there has been a review/comments from IETF groups as well 16:26:04 ... it's a good sign, has momentum 16:26:30 topic: WebVTT status 16:26:46 nigel: gary and thierry have been discussing this 16:27:44 gkatsev: the status is that unless there is progress on the spec, it will be removed from the charter and not added back soon 16:27:55 ... my question is what would constitute progress 16:28:44 tmichel: the question is not really about the progress on the spec, because it's at CR and stable 16:28:53 ... the issue is really about the implementation report 16:29:00 ... I've looked at wpt.fyi 16:29:15 ... I agree that for APIs, most of the tests pass 80% 16:29:40 ... but the rendering is at about 1% or 2% close to zero 16:29:45 ... it needs to be run manually 16:29:53 ... I discussed with Philippe 16:30:01 ... we need a proper implementation report 16:30:11 showing things are implemented twice 16:30:37 ... if we don't progress to PR, it's unlikely that it will stay in the charter 16:30:55 ... if the implementation report progresses, the transition to PR should be ok 16:31:26 gkatsev: I'm actually working on going through the rendering tests across browsers 16:31:34 tmichel: I've done a bit too 16:31:48 ... my conclusion is that Chrome it was good, Edge was bad and FF was so and so 16:31:56 ... I didn't test Safari 16:32:05 gkatsev: Safari is pretty good as well 16:32:13 tmichel: we need to know where we are 16:32:34 gkatsev: that is what I'm working on and will have results next week 16:33:02 tmichel: you have to know the past and that the efforts have been slowing down, so thank you for joining the group and putting efforts 16:33:08 gkatsev: I totally understand 16:33:19 ... I would like to see it through if we can 16:33:29 q+ 16:33:39 ack nigel 16:33:58 nigel: one question I have is: how would you establish what counts as a feature? 16:34:20 ... as far as I know, WebVTT does not have a list of features in the spec 16:34:35 ... TTML has it but a lot of other specs don't 16:34:41 ... what's your approach Gary? 16:34:57 gkatsev: the way they set it up in WPT is that each test is a feature 16:35:10 ... the rendering tests have standard cues, or 2 cues overlapping 16:35:31 ... it seems that the tests cover a pretty wide variety of "features" 16:35:55 ... for example has a separate file per unicode characters 16:36:13 nigel: if each test is a feature, how do you assess completeness of the testing vs the spec? 16:36:32 gkatsev: as Silvia said, Apple funded the development of the tests based on the spec 16:36:42 ... I'm assuming it's fairly complete 16:36:48 ... but I would need to verify that 16:36:54 q+ 16:36:59 ... but it seems the big and important parts are covered 16:37:27 nigel: it's fair to say that there is always a bit of judgment from the group on what features are and on the coverage 16:38:15 ... if you do that review and see areas are weaker, it would be good to bring that to the group 16:38:17 ack atai2 16:38:36 atai2: could you check if after the tests have been completed, if there were changes to the spec 16:38:54 gkatsev: yes, I can check when the last change to the spec was and the last change to the tests was 16:39:09 ... I doubt there was substantive change to the spec after the tests have been done 16:39:25 atai2: that would be good to review it 16:39:30 ack at 16:39:48 nigel: anything else on webvtt? 16:39:53 gkatsev: not for now 16:40:24 RRSAgent, draft minutes 16:40:24 I have made the request to generate https://www.w3.org/2019/01/24-tt-minutes.html cyril 16:40:49 RRSAgent, pointer 16:40:49 See https://www.w3.org/2019/01/24-tt-irc#T16-40-49 16:41:02 atai2 has left #tt 16:42:51 s/github-bot, end topic// 16:43:19 RRSAgent, draft minutes 16:43:19 I have made the request to generate https://www.w3.org/2019/01/24-tt-minutes.html cyril 16:44:17 s/IETF groups/members of the IETF group 16:44:29 RRSAgent, draft minutes 16:44:29 I have made the request to generate https://www.w3.org/2019/01/24-tt-minutes.html cyril 16:44:39 s/change control over this specification/change control over this specification [i.e. the media type registration] 16:44:51 RRSAgent, draft minutes 16:44:51 I have made the request to generate https://www.w3.org/2019/01/24-tt-minutes.html cyril 16:45:09 s/showing things are implemented twice/.. showing things are implemented twice 16:45:15 RRSAgent, draft minutes 16:45:15 I have made the request to generate https://www.w3.org/2019/01/24-tt-minutes.html cyril 16:46:46 scribeOptions: -noEmbedDiagnostics -final rrsagent, make minutes 16:46:54 scribeOptions: -noEmbedDiagnostics -final 16:47:01 RRSAgent, make minutes 16:47:01 I have made the request to generate https://www.w3.org/2019/01/24-tt-minutes.html cyril