13:55:43 RRSAgent has joined #adapt 13:55:47 logging to https://www.w3.org/2025/07/08-adapt-irc 13:55:47 RRSAgent, make logs Public 13:55:48 please title this meeting ("meeting: ..."), matatk 13:55:53 meeting: Adapt Weekly Telecon 13:55:56 chair: Lionel 13:56:03 present+ 13:56:10 agenda+ Announcements 13:56:13 agenda+ Symbols 13:56:19 agenda+ Well-known destinations 13:56:24 agenda+ AOB 13:56:25 janina has joined #adapt 13:56:29 agenda+ Be done 13:56:30 zakim, who's here? 13:56:30 Present: matatk 13:56:32 On IRC I see janina, RRSAgent, Zakim, matatk, gb, jcraig, hadleybeeman, Roy_Ruoxi 13:56:40 agenda? 14:04:13 Russell has joined #adapt 14:05:07 Lionel_Wolberger has joined #Adapt 14:05:09 Abhinav has joined #adapt 14:05:18 present+ 14:05:45 present+ 14:05:48 rrsagent, make minutes 14:05:50 I have made the request to generate https://www.w3.org/2025/07/08-adapt-minutes.html matatk 14:06:05 present+ 14:06:25 present+ 14:06:35 agenda? 14:06:37 scribe+ 14:06:42 zakim, next item 14:06:42 agendum 1 -- Announcements -- taken up [from matatk] 14:06:48 scribe+ 14:06:58 Annalu has joined #adapt 14:07:11 present + 14:11:50 zakim, next item 14:11:50 agendum 2 -- Symbols -- taken up [from matatk] 14:13:03 Symbols issues: https://github.com/w3c/adapt/issues?q=is%3Aissue%20state%3Aopen%20label%3ASymbols 14:14:18 I still need to add use cases - hope to do this 3rd & 4th week of July while I am away. 14:17:41 Tracking issue for Jeffrey's ruby proposal: https://github.com/w3c/a11y-review/issues/234 14:17:43 https://github.com/w3c/a11y-review/issues/234 -> Issue 234 Add a way to indicate the semantics of ruby annotations (by w3cbot) [tracker] [s:html-ruby-extensions] 14:19:30 q+ to understand how a new attirb solves the ruby problem 14:19:50 matatk: No further action needed currently 14:20:59 janina: I am trying to understand this scenario. When a browser has not been updated to this new spec, the browser will render this ruby markup 14:21:06 ... is that an acceptable outcome? 14:21:59 matatk: Browsers are evergreen today and expected to be uptodate 14:22:34 ... for (rarer) embedded systems, or legacy systems, they are likely not being used to access new web pages that will feature this new use of Ruby 14:22:47 Lionel_Wolberger: +1 to Matt's response 14:23:34 scribe+ 14:23:49 janina: I am happy if implementers are happy, but would like this to be explicitly acknowledged. 14:23:55 rrsagent, make minutes 14:23:57 I have made the request to generate https://www.w3.org/2025/07/08-adapt-minutes.html matatk 14:24:34 q? 14:24:37 ack ja 14:24:37 janina, you wanted to understand how a new attirb solves the ruby problem 14:24:40 ack janina 14:24:45 Lionel_Wolberger: I'd like to take your objection in the context of risk, and think the risk is low that this will impact users. There are older/embedded scenarios, but probably not going to be impacted. 14:24:54 rrsagent, make minutes 14:24:56 I have made the request to generate https://www.w3.org/2025/07/08-adapt-minutes.html Lionel_Wolberger 14:25:10 Russell: If the symbols are being specified, and not added automatically, i.e. the web page is created with symbols in it... 14:25:57 ... then it really would trash the web page. So wanted to openly state that. Maybe everyone else had that clear in their mind. An old page doesn't get symbols; you have to explicitly add symbols there. 14:26:13 janina: I'm imagining someone using an AI agent to do this, but they'd expect symbols. 14:26:31 Russell: So we are not trashing pages where the author didn't have an intention for symbols to be there. 14:26:54 janina: Are users upset to see rubies in mixed-language pages? 14:27:10 Russell: The intent of ruby is just within CJK, it's a pronunciation guide. 14:27:34 Russell: Is ruby used outside of Japanese? 14:27:47 Russell: I found not many examples, and they were all Japanese. 14:28:17 janina: I am satisfied with the answers here, but we should give transparency and share these risks and mitigations. 14:28:18 janina: I'm satisfied with what I'm hearing in this call, but think it's wise for us to explicitly clear this up with browsers and W3C management at TPAC. 14:28:44 Russell: I agree that we don't want to be putting symbols on pages where they're not expected. 14:32:09 bye 14:34:56 present- 14:35:13 zakim, next item 14:35:13 agendum 3 -- Well-known destinations -- taken up [from matatk] 14:36:22 WKD issues that aren't proposed destinations: https://github.com/w3c/adapt/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Well-known%20destinations%22%20-label%3Aproposed-destination 14:53:52 Lionel_Wolberger: We closed 5 proposed destinations; we expect to further reduce the list in future 14:54:18 matatk: We will need to speak with COGA. 14:54:31 ... they have an important concern about the differing needs of different people 14:54:44 ... the type of help on the help page is significant to them 14:55:27 janina: I suspect web content cannot support such sharp, clean divisions 14:56:03 ... more helpful may be, how do you exit from a wrong turn (many people do not know the 'back' command) 14:56:13 ... WKD can help people return from such wrong turns 14:57:40 zakim, end meeting 14:57:40 As of this point the attendees have been matatk, Abhinav, Russell, Lionel_Wolberger, janina 14:57:42 RRSAgent, please draft minutes 14:57:44 I have made the request to generate https://www.w3.org/2025/07/08-adapt-minutes.html Zakim 14:57:50 I am happy to have been of service, Lionel_Wolberger; please remember to excuse RRSAgent. Goodbye 14:57:50 Zakim has left #adapt