16:00:23 RRSAgent has joined #tt 16:00:23 logging to https://www.w3.org/2020/02/20-tt-irc 16:00:26 RRSAgent, make logs Public 16:00:27 Meeting: Timed Text Working Group Teleconference 16:00:52 Previous meeting: https://www.w3.org/2020/02/13-tt-minutes.html 16:01:08 Present: Pierre, Cyril, Nigel 16:01:10 Chair: Nigel 16:01:13 scribe: nigel 16:01:34 Regrets: Andreas, Glenn, Atsushi 16:02:23 Topic: This meeting 16:03:12 Present+ Gary 16:03:14 Chair+ Gary 16:04:33 Nigel: Today we have [iterates through agenda] and we're quite light on people so let's see what we can do. 16:04:41 .. Any other business to raise for the meeting? 16:04:55 group: [no other business] 16:05:01 Topic: IMSC 1.2 HR 16:05:17 Nigel: Let's look at the issue: 16:05:19 github: https://github.com/w3c/ttwg/issues/76 16:05:51 Nigel: I checked the "Privacy" box because I believe Jeffrey Yaskin's response covered IMSC 1.2 as well as TTML2 16:07:53 .. I filed an issue for TAG earlier in the week. 16:08:08 .. It was slightly unsatisfying because the issue template asked for good things that I don't think we have. 16:08:40 .. In particular I chose the best thing I could find for the explainer, but I don't know if we have anything better. 16:09:18 Pierre: I think that thread has all the information. 16:10:11 .. There's another thread I think, the actual issue on imsc-vnext-reqs. 16:10:18 Nigel: I looked at that and decided it was not as useful. 16:10:22 Pierre: Alright, thanks. 16:10:50 Nigel: Then I think we have not updated the security and privacy self review for IMSC 1.2. 16:10:57 Pierre: I remember spending a lot of time on this, maybe for IMSC 1.1 16:11:19 plh has joined #tt 16:11:59 present+ 16:12:09 Nigel: The thing here is that the changes we have made do potentially impact security. 16:12:23 Pierre: Look at w3c/imsc#503 16:12:46 Nigel: Ah, great, thank you! 16:12:53 Pierre: We did a lot of work, we just don't remember. 16:12:56 Nigel: Right! 16:13:31 .. I've added that in to the TAG request 16:14:02 .. I also did request an expedited review since the delta is small. 16:15:54 https://www.w3.org/wiki/DocumentReview#Horizontal_Groups 16:16:05 .. The last box in this HR review is for security. We have not sent this I think. 16:16:17 Philippe: You have to send it to public-web-security. 16:16:28 Pierre: Let's make sure we have not done this already. 16:16:37 Nigel: If I'd done it I should have added it to this issue. 16:16:52 https://www.w3.org/Search/Mail/Public/search?type-index=public-web-security&index-type=t&keywords=imsc&search=Search 16:16:56 Philippe: [searches the archive] I don't have anything for IMSC since 1.1. 16:17:15 Nigel: OK I need to send something. 16:17:22 Philippe: You copy/paste what you have to that list. 16:17:43 Cyril: Given that IMSC is a profile of TTML and TTML went through that step do we need to do anything? 16:17:49 Philippe: That's a good point. 16:18:00 .. It doesn't hurt to send an email. Do you need to hold on it to get an answer? 16:18:03 .. My suggestion would be no. 16:18:18 Gary: Also back in October Nigel sent a security review request for TTML2 2nd Ed. 16:18:39 Philippe: A simple email saying we plan to move this forward and given it is a profile we don't believe it 16:19:02 .. needs a security review, so this is for information. 16:19:09 Nigel: Okay I can certainly do that. 16:20:36 https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/i18n-activity 16:21:01 .. This is good, the number of upstream dependencies has reduced. 16:21:34 Philippe: I see TTML2 related issues on i18n. 16:21:48 Nigel: All those are in hand, and labelled to be dealt with in a future edition of TTML2. 16:21:59 Philippe: Then I agree likely we won't get new issues for IMSC 1.2. 16:22:58 Pierre: We could pick a target date for IMSC 1.2 CR today and work towards that. 16:23:13 .. Given we don't know of outstanding issues and we think the risk is low maybe we should just do that. 16:23:17 .. Then we can let HR groups know. 16:24:02 .. What about 3 weeks? 16:24:12 Nigel: Our Charter says to allow 3 months for HR. 16:24:29 "The Working Group is advised to seek a review at least 3 months before first entering CR and is encouraged to proactively notify the horizontal review groups when major changes occur in a specification following a review." 16:24:49 Pierre: I don't think 3 months is warranted for this size of change. 16:24:59 .. I propose saying 3 weeks and let TAG know. 16:25:19 .. Be apologetic, ask them to let us know if they want us to hold off. 16:25:30 Philippe: I would give 4 weeks because 28 days is mentioned in the Process quite often. 16:25:36 Pierre: OK that's fine with me, let's do that. 16:25:58 Philippe: NB the Charter provides "advice" not a requirement. 16:26:13 Pierre: I guess in this case it is just to avoid going to CR and then the TAG coming back with a major issue that 16:26:31 .. requires a 2nd CR. It makes sense to give them a couple of weeks for a quick review to see if they have a bad reaction. 16:26:58 Nigel: OK sure I will add a message to Tess on the ticket. 16:27:08 Philippe: You should give them the option to ask for more time. 16:27:10 Nigel: Yes. 16:29:26 Nigel: OK if we are to publish CR in 4 weeks then we will need a resolution to publish, and time to prep for the 16:29:28 .. publication. 16:29:36 .. Are there any open issues we plan to resolve in IMSC 1.2? 16:29:42 .. [looks] Seems like no. 16:29:52 .. We need to make sure the IMSC 1.1 errata are factored in. 16:30:02 Pierre: We were pretty methodical in doing that I believe. 16:30:37 Nigel: OK given the number of people on the call I think it is fairer to issue a CfC for publication. 16:30:40 Pierre: I think so yes. 16:30:56 Nigel: But just as a checkpoint, does anyone on this call have any objections to publishing in 4 weeks? 16:31:02 group: [no objections] 16:31:24 Pierre: Nigel, let me know if you need any input on the email to the TAG, I will be happy to help. 16:31:28 Nigel: OK, thank you for the offer. 16:32:08 .. I think that's it for this topic. 16:32:45 SUMMARY: @nigelmegitt to send messages to Security and TAG and the other HR recipients advising of the plan to publish in 4 weeks, and to issue CfC for publication. 16:33:00 Topic: TTML2 2nd Edition CR Publication 16:33:20 Nigel: The specific subtopic here was tests; I'm not aware of any progress. Anyone? 16:34:24 Cyril: Nothing to report from me. I noticed there are plenty of audio related features. 16:34:31 Nigel: OK I should really look at that. 16:34:38 Cyril: Also anyone else interested in those features. 16:35:19 Nigel: OK we have nothing more to discuss on this I think. 16:35:33 Topic: Meeting close 16:36:07 Nigel: Thanks everyone. We've done what we can today. See you next week. [adjourns meeting] 16:36:10 rrsagent, make minutes 16:36:10 I have made the request to generate https://www.w3.org/2020/02/20-tt-minutes.html nigel 16:38:07 s/Chair+ Gary// 16:38:11 Chair: Nigel, Gary 16:38:53 rrsagent, make minutes 16:38:53 I have made the request to generate https://www.w3.org/2020/02/20-tt-minutes.html nigel 16:40:27 s/Chair: Nigel, Gary// 16:40:48 s/Chair: Nigel/Chair: Nigel, Gary 16:40:55 rrsagent, make minutes 16:40:55 I have made the request to generate https://www.w3.org/2020/02/20-tt-minutes.html nigel 16:42:18 zakim, end meeting 16:42:18 As of this point the attendees have been Pierre, Cyril, Nigel, Gary, plh 16:42:21 RRSAgent, please draft minutes v2 16:42:21 I have made the request to generate https://www.w3.org/2020/02/20-tt-minutes.html Zakim 16:42:24 I am happy to have been of service, nigel; please remember to excuse RRSAgent. Goodbye 16:42:28 Zakim has left #tt 16:42:32 scribeOptions: -final -noEmbedDiagnostics 16:42:36 rrsagent, make minutes v2 16:42:36 I have made the request to generate https://www.w3.org/2020/02/20-tt-minutes.html nigel 16:42:41 github-bot, end topic 16:43:05 Agenda: https://github.com/w3c/ttwg/issues/95 16:43:07 rrsagent, make minutes v2 16:43:07 I have made the request to generate https://www.w3.org/2020/02/20-tt-minutes.html nigel 16:43:10 github-bot, end topic 16:43:45 s/github-bot, end topic//g 16:43:47 rrsagent, make minutes v2 16:43:47 I have made the request to generate https://www.w3.org/2020/02/20-tt-minutes.html nigel 16:44:02 github-bot, end topic 17:03:04 github-bot has joined #tt