13:41:27 <RRSAgent> RRSAgent has joined #adapt
13:41:32 <RRSAgent> logging to https://www.w3.org/2025/07/22-adapt-irc
13:41:32 <Zakim> RRSAgent, make logs Public
13:41:33 <Zakim> please title this meeting ("meeting: ..."), janina
13:41:48 <janina> Meeting: WAI-Adapt Teleconference
13:41:54 <janina> Date: 22 Jul 2025
13:42:02 <janina> Chair: Lionel_Wolberger
13:42:57 <janina> regrets: Abhinav_Kumar
13:43:44 <janina> regrets+ Annalu_Waller
13:47:48 <janina> agenda+ Introductions. Updates.
13:47:48 <janina> agenda+ Symbols
13:47:48 <janina> agenda+ Well Known Destinations
13:47:48 <janina> agenda+ Recruitment
13:56:02 <Lionel> Lionel has joined #Adapt
13:56:06 <Lionel> agenda?
14:01:16 <Russell> Russell has joined #adapt
14:01:23 <Russell> present+
14:01:28 <janina>  ppresent+
14:01:34 <janina> present+
14:02:33 <matatk> matatk has joined #adapt
14:02:48 <matatk> present+
14:03:01 <matatk> agenda?
14:08:43 <Lionel> present+
14:08:45 <Lionel> scribe+
14:08:49 <Lionel> zakim, next item
14:08:49 <Zakim> agendum 1 -- Introductions. Updates. -- taken up [from janina]
14:09:47 <Lionel> zakim, close this item
14:09:47 <Zakim> agendum 1 closed
14:09:48 <Zakim> I see 3 items remaining on the agenda; the next one is
14:09:48 <Zakim> 2. Symbols [from janina]
14:09:51 <Lionel> zakim, next item
14:09:51 <Zakim> agendum 2 -- Symbols -- taken up [from janina]
14:11:02 <Lionel> matatk: Note Adapt TF did get the TPAC meetings that we have asked for: (1) Session with WHAT-WG
14:11:11 <Lionel> ... to cover the Ruby implementation issues
14:11:32 <Lionel> ... suggesting adding a 'type' element
14:12:18 <Lionel> ... and (2) COGA meeting to discuss items that were under the Personalization umbrella
14:12:46 <Lionel> ... still considering (3) meeting with CSS regarding media queries, but since this is Adapt Roadmap, we may not request that meeting
14:13:24 <Lionel> janina: We should consider a breakout for 'show and tell'
14:14:12 <Lionel> ... of the revised prototype
14:14:39 <Lionel> ... and support a socializing agenda, looking for implementation commitments
14:20:38 <Lionel> Lionel: Matthew is taking the action item, to go to COGA planning and get a meeting prior to TPAC
14:21:21 <Lionel> matatk: The COGA item will require the new WKD prototype to be working on ruby
14:21:43 <Lionel> s/on ruby/with the new approach
14:22:23 <Lionel> matatk: COGA's persistent request regarding WKD is understanding what will appear on the WKD
14:22:31 <Lionel> ... e.g., if it says help, what kind of hlep
14:22:59 <Lionel> ... does the WKD procedure need to already future-proof for that ability, to cite what kind of content will be on the WKD
14:23:24 <matatk> topic: Symbols (actually)
14:23:34 <Lionel> rrsagent, make minutes
14:23:35 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/22-adapt-minutes.html Lionel
14:24:41 <matatk> Draft PR (still working on it) to update explainer post-workshop: https://github.com/w3c/adapt/pull/323
14:24:41 <gb> https://github.com/w3c/adapt/pull/323 -> Pull Request 323 Symbols explainer post-workshop (by matatk)
14:29:32 <Lionel> Lionel: (Reading the introduction for group editing)
14:30:04 <Lionel> janina: Add an indicator on the reason we chose BCI: Long used by people committed to symbolic communication
14:30:10 <Lionel> ... add a hyperlink
14:33:45 <Lionel> matatk: edit, 'We're working closely with BCI on this approach, which broadly speaking is comprised of the following:'
14:36:25 <Lionel> matatk: No need for a link to the registry below, as each of these bullets has a section below.
14:40:22 <Lionel> Lionel: (Discussing the order of the bullets)
14:46:11 <Lionel> Topic: Ruby Considerations
14:48:19 <Lionel> Russell: I found that CJK languages have homographs
14:48:31 <Lionel> ... a single symbol can have multiple meanings
14:49:38 <Lionel> ... a similar example in Roman characters would be 'lead' which can be 'to lead' (pronounced leed) or 'the element lead' (pronounced led)
14:50:57 <Lionel> ... i also note the i18n objection to our use of ruby
14:51:34 <matatk> q+
14:51:56 <Lionel> ... WIth my knowledge of coding, adding an attribute seems to be of similar difficulty to adding a new attribute, say 'adapt-symbol', which under the hood points to the same ruby code
14:52:14 <Lionel> ... I am aware that perhaps adding a new HTML element has its own challenges
14:53:45 <Lionel> matatk: If I translate, you are saying-- the use case is, can this approach support adding a symbol to a japanese word?
14:53:49 <Lionel> ... in other words, can you use 'ruby' on an element that already has 'ruby'?
14:54:01 <Lionel> ... the other issue to my mind is, 'overloading'
14:54:14 <Lionel> ... they feel 'ruby' has not been used enough, it is isolated to CJK
14:54:27 <janina> q+
14:54:31 <Lionel> ... I personally like having a seperate element
14:54:32 <janina> ack ma
14:54:45 <Lionel> ... I advocate that author's needs should come before the developers' needs
14:55:02 <Lionel> janina: If we really decide we want to advocate for a seperate element
14:55:18 <Lionel> ... we need a real insider develoepr from Google perhaps, who can advocate for this
14:55:35 <Lionel> ... we, as designers, cannot really opine that a seperate element is simpler
14:56:04 <Lionel> Russell: Ruby on ruby, I believe you can do that. Not sure about three layers, which could occur
14:56:11 <Lionel> janina: We need to test for that
14:56:25 <Lionel> Russell: I believe it will it
14:57:58 <Lionel> zakim, end meeting
14:57:58 <Zakim> As of this point the attendees have been Russell, janina, matatk, Lionel
14:58:00 <Zakim> RRSAgent, please draft minutes
14:58:01 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/22-adapt-minutes.html Zakim
14:58:07 <Zakim> I am happy to have been of service, Lionel; please remember to excuse RRSAgent.  Goodbye
14:58:07 <Zakim> Zakim has left #adapt