13:50:05 RRSAgent has joined #adapt 13:50:10 logging to https://www.w3.org/2026/07/07-adapt-irc 13:50:10 RRSAgent, make logs Public 13:50:11 please title this meeting ("meeting: ..."), janina 13:50:23 Meeting: WAI-Adapt Teleconference 13:50:29 Date 07 Jul 2026 13:50:34 Chair: Janina 13:50:53 topic: Welcome & Administrivia 13:51:29 topic: DD 13:51:37 topic: AAC 13:51:47 agenda? 13:52:00 zakim, clear agenda 13:52:00 agenda cleared 13:52:15 agenda+ Welcome & Administrivia 13:52:20 agenda+ DD 13:52:26 agenda+ Symbols 13:52:34 agenda+ Be Done 13:56:52 present+ 13:56:57 scribe+ 13:58:04 Russell has joined #adapt 13:58:23 present+ 13:58:51 zakim, next item 13:58:51 agendum 1 -- Welcome & Administrivia -- taken up [from janina] 14:02:05 Abhinav has joined #adapt 14:02:15 present+ 14:08:13 matatk has joined #adapt 14:08:16 present+ 14:13:12 zakim, next item 14:13:12 agendum 2 -- DD -- taken up [from janina] 14:13:41 matatk: Notes we have PR from Abhinav 14:14:43 matatk: Will re-review as requested following Abhinav's adjustments in response to first feedback cycle 14:15:12 Abhinav: Incorporated a few, and commented on others 14:15:29 Abhinav: Noting duplication with spec and Explainer 14:16:23 janina: Just a comment -- we're best practices not normative 14:16:56 matatk: Yes, will live in the same repo and we can avoid duplication of content 14:17:03 matatk: But aimed at different audiences 14:17:32 matatk: Explainer shows design trade-offs and choices. That wouldn't go into our BP Note 14:18:04 matatk: e.g. we started with WKU 14:18:51 matatk: Have seen recent examples using WKU that seem to be headed into the concerns that disuaded us from that approach 14:19:18 matatk: We don't want sites figuring out their own way to solve that 14:19:56 janina: that argues for us figuring it out sooner not later 14:20:15 matatk: Yes, and TAG will help. 14:20:39 matatk: For reference, TAG is collecting some related cases (no need to comment on this): https://github.com/w3ctag/design-reviews/issues/1243 14:26:15 janina: Asks whether we might publish before TPAC? 14:26:35 matatk: We need to figure out subsites and also cross ref our DD with COGA 14:26:55 matatk: But FPWD before TPAC with an Editor's Note about the above 14:27:38 matatk: We want to avoid specifying UI and see what different implementors do 14:27:56 matatk: We probably want to be careful about how deeply we specify subsites 14:28:11 matatk: Some you might want to know from the root; others likely not 14:28:22 matatk: Figuring that out is important 14:28:35 matatk: subsites is different from all the others we have 14:28:51 matatk: How do we know the name? Do we show it? 14:30:00 matatk: Also, we're interested in moving to link sets later, so we should protect that prospective enhancement 14:30:52 matatk: If our approach takes off, link sets is a useful enhancement 14:31:29 Abhinav: we can add a discussion in the doc about what and why of link sets 14:35:23 janina: Asks about the UI implication? 14:35:41 matatk: It's about how much we reveal and where that could affect our backend 14:36:07 matatk: We will benefit from review sooner 14:37:19 zakim, next item 14:37:20 agendum 3 -- Symbols -- taken up [from janina] 14:38:28 Russell: Update on font creation ... 14:38:38 Russell: Installed all and all appears functioning 14:38:58 Russell: All looking good! 14:39:10 Russell: Have had distractions in the form of crashed websites 14:39:46 Russell: Spec from Microsoft is over 2500pp, I've looked through it 14:40:59 Russell: 126 tags available to us 14:41:08 Russell: ccmp for emoji -- we should use 14:41:16 Russell: as opposed to liga for ligature 14:41:34 Russell: There's also a customization opportunity 14:42:11 Russell: Only codes we'll be using are Bliss space, so no conflict with emoji which have their own space inUnicode 14:42:40 Russell: Tool looks really good 14:42:54 Russell: We'll have to consider some choices, e.g. how color is used 14:43:55 Russell: We will have no need to install fonts, simply select which on the web 14:44:08 matatk: Pages can offer fonts 14:44:18 matatk: Not share they're shared across origins 14:44:35 Russell: Downloadable, but only grabs the gliphys needed 14:46:58 janina: Concerned that users have consistent fonts across sites for same meaning 14:46:59 matatk: We can work that out 14:47:11 Russell: Is so well known how to do this 14:47:55 matatk: Proposing font providers host on a CDN 14:48:23 matatk: How does page to know which to use 14:48:30 Russell: The browser knows 14:48:46 matatk: Page provides URI 14:49:05 Russell: Not, user's browser has a configuration with the URI 14:55:56 Russell: Weill be easy enough to gen fonts from this tool I'm using, so we can test approaches 14:56:16 matatk: Options always a good thing 14:59:12 zakim, next item 14:59:12 agendum 4 -- Be Done -- taken up [from janina] 14:59:20 zakim, end meeting 14:59:20 As of this point the attendees have been janina, Russell, Abhinav, matatk 14:59:23 RRSAgent, please draft minutes 14:59:24 I have made the request to generate https://www.w3.org/2026/07/07-adapt-minutes.html Zakim 14:59:31 I am happy to have been of service, janina; please remember to excuse RRSAgent. Goodbye 14:59:31 Zakim has left #adapt 15:30:58 janina has left #adapt