15:00:31 RRSAgent has joined #tt 15:00:31 logging to https://www.w3.org/2019/05/02-tt-irc 15:00:33 RRSAgent, make logs public 15:00:33 Zakim has joined #tt 15:00:35 Meeting: Timed Text Working Group Teleconference 15:00:35 Date: 02 May 2019 15:01:24 scribe: Cyril 15:01:28 chair: Nigegl 15:01:31 chair: Nigel 15:01:52 Present: Cyril, Glenn, Andreas 15:02:02 Agenda: https://github.com/w3c/ttwg/issues/36 15:02:21 Present+ Nigel 15:02:27 Present+ Gary 15:02:29 gkatsev has joined #tt 15:02:43 Log: https://www.w3.org/2019/05/02-tt-irc 15:03:19 Present+ Pierre 15:03:42 Topic: this meeting 15:03:57 nigel: we'll talk about charter, and as sub-point, explainers 15:04:13 ... on the ttreq, we have 3d reqs on the agenda 15:04:23 ... webvtt 15:04:32 ... in terms of TTML2 and TTML3 nothing on the agenda 15:04:44 ... we have one item for the profile registry 15:04:52 ... AOB I duplicated the event 15:04:59 ... from last week 15:05:21 pal: do you have issue 1043 on the agenda? 15:05:50 ... also I would like to make progress on fonts and embedded font files, IMSC issue 472 15:06:24 nigel: on 1043 I took the agenda off last week because we said we'll talk offline 15:06:48 pal: on 472, it's about how to prevent somebody from going crazy here 15:07:10 Topic: TTWG Charter 15:07:55 Regrets: Thierry 15:08:12 nigel: we don't have plh 15:08:33 ... is everyone happy to send the draft to W3M for review in order to submit it to AC 15:08:37 ... any objection to it? 15:09:08 pal: we spoke a lot about it and we're all happy 15:09:32 resolution: forward the current draft charter to W3M for review 15:09:50 s/resolution/RESOLUTION/ 15:10:07 nigel: next one is we set a deadline for explainers 15:10:14 ... there has been some work which is good 15:10:19 ... not everything is there 15:10:26 ... we have 2 explainers on the wiki 15:10:34 -> https://github.com/w3c/tt-reqs/wiki tt-reqs wiki 15:10:47 ... one on audio description and one on karaoke 15:11:35 cyril: I have 2 explainers left: responsive timed text and advanced japanser 15:11:48 nigel: I had to do an explainer on live 15:12:00 ... I'm waiting for some elements from EBU 15:12:08 ... it's good to have some progress 15:12:17 plh has joined #tt 15:12:23 Present+ Philippe 15:12:44 nigel: it would be good if people could have a read and send feedback 15:13:13 rrsagent, generate minutes 15:13:13 I have made the request to generate https://www.w3.org/2019/05/02-tt-minutes.html plh 15:13:54 scribe: nigel 15:14:08 Cyril: I wasn't sure exactly how to write the explainer, and am not sure if it's what was expected. 15:14:23 .. It seems to be a living design document. 15:14:52 Glenn: I think we're overblowing process. We should not mandate these explainers. 15:15:07 .. On the point about karaoke, I have to say I'm not on board with the proposal in terms of the approach 15:15:19 .. and need to discuss an alternative way that does not introduce a new element type. 15:15:24 Cyril: I'm open to discussion. 15:15:39 Glenn: I have some ideas about how to do it. I think we should avoid prematurely documenting 15:16:02 .. design choices that might make the explainer misleading. 15:16:25 scribe: cyril 15:16:41 nigel: I don't see a problem with having a living document 15:16:48 ... describingg the design 15:16:57 ... it's a tool to try and reach consensus 15:17:13 ... we should try to produce them 15:18:08 plh: it will take a week or two to get feedback on the charter 15:18:22 ... I don't expect to receive much feedback given that the document is light 15:18:33 nigel: do you need anything more regarding deliverables 15:19:41 plh: I would expect the charter to be approved by the director by the end of june 15:19:57 ... since there is no change of scope, we can go ahead with working drafts 15:20:08 ... I'm not even sure we'll send a new call for participation 15:20:28 nigel: one goal of the charter revision was to make it clear that the audio description would be in charter 15:20:40 ... members of the audio description cg might join 15:21:00 ... it was unclear that we had audio description on the charter 15:21:16 plh: then I will issue a call to join and you will have 45 days to rejoin 15:22:38 scribe: nigel 15:22:53 Cyril: On the Karaoke proposal I'm trying to implement a renderer for the new features 15:23:11 .. I'm trying to represent quite complex examples and try to make sure that it is simple for simple 15:23:24 .. examples. I also have a draft specification but it might completely change depending on the outcome. 15:23:42 .. I wrote it as an extension to TTML2 in the sense that it defines a new feature, just one at the moment. 15:24:02 .. It is an extension in the sense that it defines some vocabulary that is added on top of TTML2. 15:24:11 .. It doesn't mention modules. 15:24:33 Glenn: Just to let you know what I'm thinking is that instead of an element type have a new 15:24:46 .. attribute tts:marker with some values. We should discuss this further. 15:25:00 Cyril: Yes, I'm open to discussing it. I would like to conclude soon to move to a FPWD. 15:25:03 q+ 15:25:09 Glenn: Let's schedule some discussion time 15:25:17 Pierre: I'd like to be part of those discussion 15:25:21 ack plh 15:25:44 Philippe: I don't know how this relates to the old CSS aural properties 15:25:52 Glenn: I don't think it's related at all. I'm familiar with those. 15:26:03 .. The new audio properties intersect with those but not the marker concept. 15:26:15 Philippe: I don't think those old CSS properties were implemented largely. 15:26:25 .. I wanted to add that Explainers are wanted by the TAG for example. 15:26:40 .. It's not just for the purpose of a WG conversation. It will be useful further down the line. 15:26:53 Cyril: I agree to write these explainers especially for that purpose. 15:27:02 .. Otherwise I'm of the opinion that it adds a burden as Glenn. 15:28:02 scribe: Cyril 15:28:14 nigel: explainers will be helpful for others 15:28:24 plh: to determine if they want to review the specification 15:28:48 nigel: any other comment on the explainers? 15:29:05 Topic: 3D requirements 15:29:12 atai2: I wanted to give an update 15:29:23 ... there are 3 things we need to consider 15:29:33 ... 1 reqs have been submitted 15:29:40 ... 2 liaison sent to MPEG 15:29:49 ... 3 discussion on going with broader community 15:30:18 ... for the requirements, after discussing with stakeholders, we need some more discussions about the scope 15:30:43 ... one main question is if it should be just for subtitles in 360 or omnidirectional media or should it be applicable to VR and AR 15:30:51 ... first reaction is always yes 15:31:11 ... but then for AR and VR it's much more complicated because the viewer is moving 15:31:35 ... we need to discuss if we want to limit the scope 15:31:43 ... MPEG liaison is only 360 15:32:00 ... from the draft from MPEG, it's really another area we need to work in 15:32:14 ... we need to see if need to specify additional information items, positioning ... 15:32:26 ... or if we have a complete different environment that we need to work with 15:32:36 ... we could review how fonts are handled 15:32:52 ... I think we should just discuss MPEG draft deeply 15:33:19 ... on the broader discussion, the immersive web always asks to open an issue before they decide to work on it 15:33:23 ... Peter filed an issue there 15:33:29 ... some discussion on-going 15:33:41 ... I tried to get attention from accessibility groups 15:33:51 ... I spoke to Alan Sterns from CSS 15:34:13 ... we need to have a broader spectrum of people looking at it 15:34:31 ... there will be a call on May 21st, 10 am PT, to discuss this in the Immersive CG 15:34:37 ... everybody can join 15:35:07 ... I hope we can have a discussion on the TTWG meeting next week before the call to see how the grgoup handles this issue 15:35:37 Topic: WebVTT 15:35:50 gkatsev: last night I submitted a PR to add in a couple of file tests missing 15:36:17 ... I've always started thinking about what to say in the IR and should be able to produce it soon 15:36:32 nigel: the Web Platform tests have not been rerun 15:36:36 ... are they run nightly> 15:36:42 s/>/? 15:36:51 ... possibly not every day 15:36:57 plh: are they run automatically? 15:37:04 gkatsev: I think so 15:37:16 nigel: are you talking about wpt.fyi ? 15:37:31 s/nigel/gkatsev/ 15:37:58 gkatsev: because a lot of the tests are rendering tests, my spreadsheet is probably most up to date 15:38:07 nigel: ok so we expect the IR in the coming week 15:38:56 Topic: TTML Profile Registry 15:39:16 nigel: about issue 71 15:39:28 github: https://github.com/w3c/tt-profile-registry/issues/71 15:39:56 cyril: the request is to add a substantive change in the IANA section that defines the combination operators 15:40:09 ... mike is not on the call for a while 15:40:18 ... but he does think that it ought to be there 15:40:37 ... my recollection is that it should be defined and compliant to RFC 15:40:56 glenn: we have to qualify what you mean by "define" 15:41:03 s/cyril/nigel 15:41:13 ... it is not defined in the body of the media type registration 15:41:31 nigel: at the moment it is defined what it means 15:41:47 scribe: nigel 15:41:59 Cyril: The syntax is defined but absent from the IANA registry. 15:42:08 .. It seems odd to have an informal definition when the rest is formal. 15:42:22 Glenn: The only issue previously was if we should trigger the IANA review process. 15:42:30 .. If everyone is happy with that then we can go ahead. 15:42:47 Pierre: I'm not objecting to going through the IANA process but noting that we have trouble 15:43:05 .. getting this out so I'm concerned about our level of resource. 15:43:18 Glenn: We have updated our document and IANA references our document so we have formally 15:43:21 .. updated it. 15:46:43 scribe: Cyril 15:46:48 cyril: I will prepare a PR 15:47:43 nigel: I don't share the concern about resources given that we don't have a hard deadline 15:48:18 Topic: TTML2 and TTML3 Pull Requests 15:48:49 github: https://github.com/w3c/ttml2/issues/1043 15:49:01 nigel: last time we said that we would deal with this offline 15:49:21 pal: given that we are all here, we could have a shot at closing it 15:49:27 atai2 has left #tt 15:49:29 glenn: let's spend 5 min 15:49:44 pal: my homework was to review Glenn's PR 15:49:57 atai2 has joined #tt 15:50:08 ... there are 2 subtle points: text nodes being ignored and the applicability of styles to containers 15:50:18 ... the PR that Glenn had proposed adresses both 15:50:27 ... I'm happy with the way the PR adresses the first point 15:50:39 ... not found a better way of doing it 15:50:45 ... on the second part, I'm less happy 15:50:49 ... it's buried in a note 15:51:04 atai2 has left #tt 15:51:08 ... and it does not address specifically if a propery applies or not 15:51:44 glenn: it's my opinion that if we define that LWSP is ignored in that context, irrespective of white-space attribute, for presentation 15:51:54 ... and if we say that LWSP is forbidden 15:52:15 ... we just need to add text for the error case 15:52:24 pal: look at the example I posted in 1043 15:52:44 ... there are 2 underlines that appear underneath hello 15:52:57 nigel: I did not notice that before 15:54:49 pal: my question is do we actually want text decoration to apply to the text container, ever 15:55:04 glenn: you can construct an example that does not even involve ruby 15:55:18 ... with outer spans and inner spans 15:55:35 ... the intent of the specification is to not apply to all of them 15:55:53 ... also similar to XSL FO 15:56:10 pal: for div and p, this is obvious that it does not apply 15:56:26 ... what I have not tried is the difference between inline block vs inline 15:56:56 glenn: the semantic model for decoration in TTML is that it only applies to the most deeply nested text characters 15:57:08 ... you don't have decorations applied to upper leve 15:57:14 s/leve/level/ 15:57:25 ... ttpe does not do the behavior you are describing 15:57:38 ... it may be an artefact of CSS or IMSC.js 15:57:47 pal: I'm of hte same opinion 15:57:57 ... that it does not apply to text container 15:58:01 q+ 15:58:06 ... but I want it to be clear 15:58:23 glenn: I'm not happy to have the same text in all properties 15:58:38 ... I can tweak the note 15:58:49 pal: that note is not sufficient 15:58:57 ... it does not cover the case we are looking at right now 15:59:55 nigel: Pierre's proposal very clearly is to add a clause to apply to to the various style attributes 16:00:12 ... to add unless text container or ruby container 16:00:18 ... any objection to that? 16:00:30 glenn: we decided to avoid repetition 16:00:42 nigel: you can refactor that to avoid repetition 16:00:52 ... for example defining a term for a class of span 16:01:09 ack n 16:01:48 glenn: on this text decoration, I'm not sure that an interpretation of TTML2 can lead to that 16:02:12 nigel: my reading of this is that you can interpret it that way 16:02:26 ... if you think adding a normative statement is a no-op 16:02:38 ... there should be no problem going ahead 16:03:20 nigel: we are over time, we'll adjourn to same time next week 16:03:22 regrets for next week 16:04:15 rrsagent, make minutes 16:04:15 I have made the request to generate https://www.w3.org/2019/05/02-tt-minutes.html nigel 16:05:14 s/Nigegl/Nigel/g 16:05:41 s/chair: Nigel// 16:05:43 rrsagent, make minutes 16:05:43 I have made the request to generate https://www.w3.org/2019/05/02-tt-minutes.html nigel 16:06:55 s/we don't have plh/we don't have plh yet [later update: he joined a few minutes later] 16:07:52 s/Topic: TTML Profile Registry/TTML Profile Registry issue #71 16:08:27 s/Topic: TTML2 and TTML3 Pull Requests/TTML2 Issue #1043 16:08:43 rrsagent, make minutes 16:08:43 I have made the request to generate https://www.w3.org/2019/05/02-tt-minutes.html nigel 16:09:38 s/TTML Profile Registry issue #71/Topic: TTML Profile Registry issue #71 16:09:57 s/TTML2 Issue #1043/Topic: TTML2 Issue #1043 16:09:59 rrsagent, make minutes 16:09:59 I have made the request to generate https://www.w3.org/2019/05/02-tt-minutes.html nigel 16:11:17 scribeOptions: -final -noEmbedDiagnostics 16:11:18 rrsagent, make minutes 16:11:18 I have made the request to generate https://www.w3.org/2019/05/02-tt-minutes.html nigel