15:00:04 RRSAgent has joined #tt 15:00:04 logging to https://www.w3.org/2019/08/01-tt-irc 15:00:06 RRSAgent, make logs public 15:00:06 Zakim has joined #tt 15:00:08 Meeting: Timed Text Working Group Teleconference 15:00:08 Date: 01 August 2019 15:00:12 Log: https://www.w3.org/2019/08/01-tt-irc 15:00:16 scribe: nigel 15:00:19 Present: Nigel 15:00:21 chair: Nigel 15:01:03 Present+ Glenn, Pierre 15:01:22 Present: Gary 15:01:56 Present: Nigel, Glenn, Pierre, Gary 15:02:18 Present+ Atsushi 15:02:27 no mic today, sorry 15:02:44 Present- Atsushi 15:02:55 Present+ Atsushi_irc-only 15:03:05 Present+ Andreas, Cyril 15:03:30 Topic: This meeting 15:03:42 Nigel: [iterates through agenda] 15:03:45 atai2 has joined #tt 15:03:48 Agenda: https://github.com/w3c/ttwg/issues/53 15:05:33 Nigel: AOB or other points 15:05:40 Glenn: 10 seconds on PR #1096 on TTML2 15:05:41 Nigel: OK 15:06:22 Glenn: If we can handle that right now, all I want to do is remind Cyril to review it. 15:06:28 Cyril: I know, I will get to it today. 15:06:31 Glenn: Thank you, that's all. 15:06:35 Topic: WebVTT 15:07:19 Gary: The main thing that's left is basically deciding if PR #460 is good to go and I can start to work with Philippe 15:07:26 .. to get it through the CR process. 15:07:57 Topic: New snapshot with new at-risk items webvtt#460 15:07:59 github: https://github.com/w3c/webvtt/pull/460 15:08:34 Gary: This has the change for making the region lines a regular long from unsigned long 15:08:53 .. as well as the change to clamp the lines property to the closest value that can be represented 15:09:08 .. It also adds the at-risk items. 15:09:54 Nigel: Looks like the last significant change was 14 days ago and the positive review was older. 15:10:07 Gary: Yes, this incorporates changes that Silvia has also approved from other PRs. 15:10:21 .. The biggest change is the rounding, where I looked at the HTML spec to see how to do it and want someone 15:10:26 .. else to look at it and check it's okay. 15:10:35 Nigel: Nobody has done that yet? 15:10:48 Gary: Silvia approved #470 which was the PR that introduced this, nobody else has. 15:10:56 .. If we're okay with just Silvia then we can go ahead. 15:11:26 Nigel: #470 was 17 days ago and Silvia approved it the same day. 15:11:49 .. In this situation it has had 2 weeks and a positive review so we normally say go ahead and do it. 15:11:55 Gary: Awesome I'll go ahead then. 15:12:04 Nigel: What's the state of the tests for this? 15:12:24 Gary: I need to update the Lines PR to match it, to split the rounded and clamped/unclamped values but now we don't 15:12:32 .. need to verify the unclamped values and can delete that portion. 15:12:50 .. I was going to use the CR time to look through and fix VTT.js implementation and whatnot to get the other things in 15:12:52 .. the IR to pass. 15:13:36 Nigel: From our normal process we can just go ahead at this point. Any objections? 15:13:42 Nigel: Silence, so go ahead. 15:13:47 Gary: Then I'll proceed, thanks. 15:14:21 Topic: Eliminate inconsistent use of xsd:nonNegativeInteger (#983). w3c/ttml2#1135 15:14:32 github: https://github.com/w3c/ttml2/pull/1135 15:15:36 cyril has joined #tt 15:15:46 rrsagent, pointer 15:15:46 See https://www.w3.org/2019/08/01-tt-irc#T15-15-46 15:15:53 Nigel: I added this to the agenda to discuss why we would move away from XSD defined types because generally 15:16:04 .. speaking I feel we should use XSD defined types where they meet our needs. 15:16:07 scribe: cyril 15:16:17 nigel: this is your proposal glenn 15:16:30 ... the first part is about the motivation 15:16:42 ... the issue says there is non-consistency 15:16:57 ... and the internal type does permit "-0" 15:17:07 ... the consistency is a bit of a problem 15:17:23 glenn: the introduction of xsd nonNegative in 3 places 15:17:42 ... the data @length, chunk @length, and isd @size 15:17:48 ... was an oversight from my side 15:18:00 ... I failed to record that we had a non-negative-integer 15:18:19 ... if you look at TTML2 1st 15:18:45 ... you'll find 17 matches on 15:18:59 ... one of them is the definition of non-negative-integer 15:19:53 q+ to note that in some places allowing the sign in numbers would be nonsensical, like in RGB values 15:19:54 q+ 15:19:58 ... the only reason that we might want to have the xsd nonNegative is if we want +0 and -0 and +X be equal to X 15:20:23 ... there is no reason to allow +0 or -0 15:20:34 ... when we have a perfectly good type used in 17 places 15:20:58 ... the other item is the introduction of xsd positiveInteger on the @version on isd 15:21:11 ... in the text of the specification it already says the value must be greater than 0 15:21:12 plh_ has joined #tt 15:21:50 ... like repeatCount 15:22:01 pal has joined #tt 15:22:08 ... or numerator and denominator and framerate ... 15:22:13 q+ 15:22:17 present+ 15:22:27 present+ 15:22:42 ... we should use the same mechanism 15:22:57 ... I checked in today a series of test 15:23:03 ... based on the proposed change 15:23:21 ... I don't see a risk of making this non-backwards compatible change 15:23:33 ... I'm very confident it's going to affect anybody 15:23:43 s/it's going/it's not going/ 15:23:51 nigel: I did a quick scan 15:24:09 ... and in the place where the internal type is used, it would make no sense to use the xsd type 15:24:31 ack ni 15:24:31 nigel, you wanted to note that in some places allowing the sign in numbers would be nonsensical, like in RGB values 15:24:37 ... although I like the idea of using xsd types, I'm happy to make this change 15:24:42 ack atai 15:24:47 atai2: I want to understand the change 15:25:17 ... so it's replacing a type with a more relaxed type 15:25:28 ... that would increase the number of false positive during validation 15:25:39 nigel: we add pattern constraints on some xsd strings 15:25:47 ... maybe we could do that here too 15:26:37 glenn: if we remove the optional sign, it's restricting the number of lexical representations, no increasing it 15:26:55 ... one of the recent commit was to add more pattern 15:27:10 ... I agree the current schema had been a bit inconsistent in that regard 15:27:19 ... but I note that the schema is not normative 15:27:26 q? 15:27:43 ... my intent in this PR is to make things a bit more consistent 15:28:03 ack pal 15:28:28 pal: do these changes make TTML closer to CSS? 15:28:45 glenn: none of these attributes are in the domain of CSS, they are not properties 15:29:02 q? 15:29:08 pal: so I don't have a strong opinion 15:29:23 nigel: any objection to go ahead with this change? 15:29:32 ... hearing none, let's proceed 15:29:45 glenn: I would appreciate your final review nigel 15:29:53 ... like missing pattern 15:30:24 Topic: TTML Tests 15:30:46 nigel: I want to alert people that there are a number of open PR on TTML test repo 15:30:54 ... I like the approach of adding tests with PR on the spec 15:31:16 ... a concrete example was about base64 encoded chunks of data 15:31:34 ... where the spec change is to strip off spaces before passing it to the decoder 15:31:45 ... and test does that by applying character entities 15:31:55 ... that was a good thought exercise 15:32:10 ... please do take a look at them and see if they match your expectations 15:34:29 Topic: 3D extensions 15:34:42 nigel: andreas wanted some clarifications about the next steps 15:34:56 atai2: we continued the discussion for the requirements for 360 subtitles 15:35:06 ... we are in a state where we can start drafting 15:35:11 ... some specification text 15:35:19 ... the question is about the right procedure 15:35:42 ... I think that more people outside of this group are interested and may want to contribute 15:35:49 ... it may be difficult to contribute 15:36:11 ... there was the option to have a discussion in the WICG 15:36:22 ... my thinking is to bring it to that CG 15:36:34 ... but I don't know how it connects to this WG 15:36:41 ... I want to make an explainer for the tag 15:36:47 ... and draft a TTML module 15:37:01 ... I could start over as a TTML module in the CG for example 15:37:22 --> https://github.com/immersive-web/proposals/issues/40 Requirements for subtitles and text in WebXR 15:37:28 ... and as plh is on the call, it'd be good to have a discussion on the interaction between the groups 15:37:43 my understanding of WICG is quite wide range of gathering (and no strong organization), and it should be fine to file new proposal as issue to the repository 15:37:48 nigel: not sure why it would be difficult for people to contribute? 15:37:53 ... are they not W3C members? 15:38:18 atai2: the idea is that people active in W3C could contribute and would be motivated to contribute 15:38:35 ... and having another place than the TTWG would be helpful for that 15:38:41 ... and also for non-member 15:39:01 ... they can comment on github issues but that's not sufficient, they would need to be invited members 15:39:12 ... so having a community group would be helpful 15:39:38 plh: the link above is to where some discussions are happening 15:39:49 ... in terms of doing incubation in CG, it is encouraged 15:40:00 ... using WICG means you don't have to create a new CG 15:40:27 ... people in the CG if they make an actual contribution will have to adhere to the contributing agreement 15:40:54 ... if you want to have people from accessibility, the difficulty is to find the right time to switch to a WG 15:41:01 ... and there is no formula for that 15:41:17 ... if it is still an idea and trying different options, a CG is fine 15:41:42 q+ 15:41:44 ... if it becomes a very serious idea, and you need a WG, at that time we need to check if the TTWG is good or not 15:42:17 ... there was an inclusive XR workshop happening in NY and there was interest and discussions on captioning 15:42:44 ack at 15:42:45 ... the CG option is the safest approach in my opinion 15:42:54 atai2: the idea is quite clear 15:43:33 ... the requirements got clearer 15:43:46 ... we need more experts on making it work 15:43:54 ... we have a pretty good scope 15:44:11 plh: the challenge is making sure that the right people are there 15:44:31 ... most of the people were not aware that W3C was working on that 15:44:44 atai2: the TTML module would define a basic 15:44:52 ... vocabulary 15:45:01 plh: you are assuming people want to use TTML 15:45:08 atai2: it's obvious 15:45:15 plh: to you, not to everybody 15:45:29 atai2: in the Web Community call, that was the response 15:45:42 ... we found no other group or context to specify a solution for this requirement 15:45:43 s/not to/may not to/ 15:46:24 plh: it seems the choice is either the WICG or to create your own CG 15:46:38 atai2: no the choice is either the WICG or the TTWG directly 15:46:52 ... in the community group, we might attract more experts 15:47:12 atai2: one more question 15:47:20 ... nigel asked for explainers for TTML 15:47:34 ... are there explainers for other features submitted to TTML? 15:47:46 nigel: the one for the AD profile exists 15:47:59 -> https://w3ctag.github.io/explainers TAG template for Explainers 15:48:01 -> https://github.com/w3c/tt-reqs/wiki 15:48:02 cyril: the karaoke module also has an explainer 15:49:02 Topic: TTML over RTP IETF draft 15:49:21 nigel: there is an IETF process point called WGLC (last call) 15:49:36 ... at the IETF 105 meeting, this was brought up 15:49:45 ... and the WGLC lapsed without comment 15:49:55 ... the chair asked that even if there was no comment 15:50:15 ... that this group would say that all comments have been taken into account 15:50:19 ... what I propose to do 15:50:29 ... is to say that there are no further comment 15:50:39 ... do people agree or take extra time? 15:51:04 nigel: all of Mike's comments have been addressed 15:51:41 ... seeing nothing more, I will take that as Yes, TTWG has no furhter commenbts on the document 15:51:46 Topic: TPAC Planning 15:51:57 As of this point the attendees have been Nigel, Glenn, Pierre, Gary, Atsushi, Atsushi_irc-only, Andreas, Cyril, plh_, pal 15:52:01 -> https://www.w3.org/wiki/TimedText/tpac2019 TPAC 2019 planning wiki 15:52:04 nigel: there is now a wiki page, thanks atsushi 15:52:13 pal: on the topic of liaisons and TPAC 15:52:35 ... what's happening to add a new subtitle class to CLDR 15:52:59 ... the unicode effort to create/document characteristics of languages across the world 15:53:09 -> https://unicode-org.atlassian.net/browse/CLDR-8915 Our ticket on Unicode CLDR 15:53:13 ... today CLDR has examples of character used for all languages 15:53:20 ... they don't include examples for subtitles 15:53:31 ... they had made a liaison 15:53:58 ... and we recommended unicode to add examples to CLDR 15:54:02 ... that was 4 years ago 15:54:12 ... maybe TPAC is a good time to revive that 15:54:34 nigel: I checked a ticket on CLDR and some comments were made in May 15:54:43 ... Addison asked for some more work 15:55:02 ... happy to add this topic at TPAC 15:55:11 pal: maybe we should follow up before? 15:55:21 plh: do we need Addison or Richard Ishida? 15:55:31 glenn: or Mark from Google 15:55:44 nigel: I'll give myself a task to get in touch with Addison 15:56:07 -> https://github.com/w3c/ttwg/issues/59 TTWG issue 59 15:56:28 nigel: both things make sense: get in touch and follow up at TPAC 15:56:43 s/Mark/Mark Davis/ 15:57:19 nigel: we will be collecting topics for TPAC, please add you names to the participants list 15:57:27 ... if you haven't registered yet, please do 15:57:40 ... registration is only until Sept 6th 15:57:46 glenn: I'm registered 15:58:00 q? 15:58:02 Topic: TTWG Charter status update 15:58:28 plh: the good news is that I had approval from the Director yesterday 15:58:38 ... I'm in the process of preparing the call for review 15:58:44 ... for the AC 15:58:52 https://www.w3.org/2019/08/ttwg-proposed-charter.html 15:59:18 ... I merged the PR as asked by the director 15:59:24 ... it's ready to ship for review 15:59:41 nigel: we did not seem completely happy with some parts of it (the review part) 15:59:48 ... we should make sure we look at that 15:59:49 plh: yes 16:00:01 ... you may grumble about the horizontal review 16:00:15 nigel: I see you added "before entire CR 16:00:24 s/entire/entering/ 16:00:32 s/CR/first CR 16:00:40 plh: people can make comments as part of the AC review 16:00:49 q? 16:01:15 Topic: Karaoke model 16:01:24 scribe: nigel 16:01:36 Cyril: Reminder please look at this - I have received no comments yet 16:01:47 Pierre: Is there an easy way to preview it? 16:01:54 Cyril: I will make sure there's a render somewhere. 16:01:54 s/model/module/ 16:01:58 Pierre: Thanks 16:02:10 atai2 has left #tt 16:02:16 Topic: Meeting close 16:02:34 Nigel: Thanks everyone, we're at time and have just completed the agenda. See you next week. [adjourns meeting] 16:02:38 rrsagent, make minutes 16:02:38 I have made the request to generate https://www.w3.org/2019/08/01-tt-minutes.html nigel 16:17:13 Present- pal, plh_ 16:17:16 Present+ Philippe 16:17:26 Regrets: none 16:18:42 github-bot, end topic 16:20:05 s/open PR on TTML test/open PRs on TTML test 16:22:24 s/seeing nothing more, I will take that as Yes, TTWG has no furhter commenbts on the document/hearing nothing more, I will take that as Yes, TTWG has no further comments on the document 16:24:24 s/I see you added "before entering first CR/I see you added "first" in "before first entering CR" addressing my issue, thank you for that. 16:24:43 s/github-bot, end topic// 16:24:49 rrsagent, make minutes v2 16:24:49 I have made the request to generate https://www.w3.org/2019/08/01-tt-minutes.html nigel 16:27:43 scribeOptions: -final -noEmbedDiagnostics 16:27:45 rrsagent, make minutes v2 16:27:45 I have made the request to generate https://www.w3.org/2019/08/01-tt-minutes.html nigel 18:25:40 Zakim has left #tt 22:37:38 plh has joined #tt