16:06:08 RRSAgent has joined #pronunciation 16:06:13 logging to https://www.w3.org/2024/12/09-pronunciation-irc 16:06:13 RRSAgent, make logs Public 16:06:14 please title this meeting ("meeting: ..."), matatk 16:06:15 Agenda+ Agenda Review, Membership & Announcements 16:06:15 Agenda+ Review Use Cases 16:06:15 Agenda+ Action Items 16:06:15 Agenda+ Github Issues and examples 16:06:16 Agenda+ Other Business 16:06:22 present+ 16:06:22 present+ 16:06:26 present+ 16:06:37 IrfanA has joined #pronunciation 16:06:43 present+ 16:06:54 zakim, next topic 16:06:54 I don't understand 'next topic', PaulG 16:06:58 zakim, next item 16:06:58 agendum 1 -- Agenda Review, Membership & Announcements -- taken up [from PaulG] 16:07:18 Update from Matthew on documents: https://lists.w3.org/Archives/Public/public-pronunciation/2024Nov/0006.html 16:08:08 matatk: the first three are straight-forward and we can decide what to do with. The others aren't as clear. 16:08:44 ... we need an explainer but it's not usually in the TR space. It has a well-known TAG format which we should compy. 16:09:10 ... consistency in the format helps with sharing it widely 16:09:41 ... we'll use that to help others understand the problems we're trying to solve and considered alternatives (which would never be in a spec) 16:10:40 ... If we can decide which documents we'll proceed with, we can separate out the use cases as we discussed last time. 16:13:24 ... notes from the 11th with Janina confirms this approach of splitting the spec up into smaller chunks that might be better fits. 16:14:37 ... We need to "fix the things you can't do on the web" by restarting the documents with just the problem statements. 16:16:36 ... We'll need to also clean up the "dangling" specs that we're not moving forward with. 16:17:04 scribe+ 16:17:14 PaulG: We also have good content in the wiki that we don't want to lose 16:17:52 ... e.g. reasons for delays - we need to show a compelling reason for everyone (noting that our educational partners were adamant that it's core to the required functionality). 16:18:30 PaulG: do we want a second repo, share the current, or something else? 16:19:12 matatk: it's up to us how we want to organize but we can make changes later. We can also, maybe, keep the TR space but rehome the repo for a doc 16:23:13 PaulG: how do we want to handle facilitators? 16:25:18 I'd want the future facilitators to have the organization that makes the most sense for them and what they want to focus on. 16:25:42 matatk: we can seek APA input for the split 16:26:02 ... like a horizontal review based solely on the use cases document 16:26:50 but we can also do the community group approach which may have some advantages to incubate ideas and source new ideas 16:35:06 IrfanA: There may be an existing CG that could help with some of our use cases? We should look. 16:38:00 *group discussion about docs* 16:38:02 1. https://www.w3.org/TR/pronunciation-gap-analysis-and-use-cases/ - deprecate 16:38:46 2. https://www.w3.org/TR/pronunciation-gap-analysis/ - update, using sec 4 from 1 16:39:27 3. https://www.w3.org/TR/pronunciation-use-cases/ - update, w/o implementation detail (our north star as PaulG mentioned) 16:41:08 4. https://www.w3.org/TR/pronunciation-user-scenarios/ - fold into 3, and update as needed 16:45:31 5. https://www.w3.org/TR/spoken-html/ - no 16:45:49 6. https://www.w3.org/TR/pronunciation-explainer/ - yes, but not at this URL 16:46:48 PaulG: Could APA chairs discuss in planning about how to coordinate the split, and who'll make decisions on it? 16:47:07 matatk: yes, sure, will continue to bring Janina and Roy in on this. 16:47:10 zakim, end meeting 16:47:10 As of this point the attendees have been matatk, PaulG, Alan, IrfanA 16:47:11 RRSAgent, please draft minutes 16:47:12 I have made the request to generate https://www.w3.org/2024/12/09-pronunciation-minutes.html Zakim 16:47:19 I am happy to have been of service, matatk; please remember to excuse RRSAgent. Goodbye 16:47:19 Zakim has left #pronunciation