13:45:08 RRSAgent has joined #adapt 13:45:12 logging to https://www.w3.org/2024/08/06-adapt-irc 13:45:12 RRSAgent, make logs Public 13:45:13 please title this meeting ("meeting: ..."), janina 13:45:15 agenda/ 13:45:21 adenda? 13:45:37 Meeting: WAI-Adapt Weekly Teleconference 13:45:44 Date: 06 Aug 2024 13:46:24 Chair: Lionel_Wolberger 13:46:27 agenda+ Introduction, logistics. Any Updates? 13:46:27 agenda+ TPAC Preps 13:46:27 agenda+ Symbols explainer 13:46:27 agenda+ WKD Github actions and PRs 13:58:22 present+ 13:58:25 scribe+ 14:01:29 matatk has joined #adapt 14:02:05 Abhinav has joined #adapt 14:02:16 Lionel_Wolberger has joined #adapt 14:02:40 present+ 14:02:51 present+ 14:02:59 present_+ 14:03:01 present+ 14:03:02 agenda? 14:03:15 rrsagent, make minutes 14:03:16 I have made the request to generate https://www.w3.org/2024/08/06-adapt-minutes.html matatk 14:04:02 scribe+ 14:04:30 zakim, next item 14:04:30 agendum 1 -- Introduction, logistics. Any Updates? -- taken up [from janina] 14:04:42 Russell has joined #adapt 14:04:44 q+ to ask about time off 14:04:48 present+ 14:05:34 Janina expects to be gone Aug 20-22 14:05:44 scribe+ 14:05:51 zakim, next item 14:05:51 I see a speaker queue remaining and respectfully decline to close this agendum, Lionel_Wolberger 14:05:52 matatk: I may be gone on the 20th too 14:05:54 ack me 14:05:54 matatk, you wanted to ask about time off 14:05:55 q? 14:06:17 zakim, next item 14:06:17 agendum 2 -- TPAC Preps -- taken up [from janina] 14:06:17 Lionel_Wolberger: Let's revisit next week 14:08:31 matatk: Reminds people to register especially if in person 14:09:27 matatk: Notes schedule is decided, but we're still working details 14:11:30 Lionel_Wolberger: Recalls to print more AAC handouts 14:12:06 zakim, next item 14:12:06 agendum 3 -- Symbols explainer -- taken up [from janina] 14:12:36 Russell: Just checked and nothing new on 240 14:13:14 matatk: Think we should decide whether we want response ahead of TPAC, or whether we're OK to get closure at TPAC 14:13:33 matatk: If ahead we should be clear on our agenda 14:14:01 matatk: Believe no news from Unicode? Would we know it's not going in this year? 14:14:08 Russell: Believe I would have heard by now 14:14:33 matatk: Are their minutes public? 14:14:50 matatk: Might we start using? 14:15:01 Russell: Advice is to not use until formally adopted 14:15:10 Russell: Believe minutes may be public, will look 14:15:53 matatk: Would be good to have a sense whether there are serious blockers that would put us back more than months 14:16:28 matatk: With that understanding we can figure out next steps and agenda 14:17:36 janina: The "and therefore we should" means changes to the draft 14:17:51 q+ re mapping exercise 14:18:16 ... we care about user agent rendering, and how authors will 'decorate' their content with the correct symbols 14:18:20 ... we need tooling for that 14:18:32 ... this means there are two documents to update 14:18:37 q+ re testing 14:18:41 q? 14:19:08 rrsagent, make minutes 14:19:09 I have made the request to generate https://www.w3.org/2024/08/06-adapt-minutes.html matatk 14:19:17 ... once we get confident that unicode will be there, we can take these steps to rely on it 14:19:33 matatk: If time permits, I suggest we do a mapping excercise 14:19:43 matatk: It would be good to do a mapping exercise from our key to different symbol sets 14:19:58 ... a mapping from our key to a relevant symbol in another set, e.g., ARASAAC 14:20:08 matatk: For now with BCI, but would give us a sense of how viable 14:21:18 matatk: Notes his tool also included rendering; and helps in viability review 14:21:36 matatk: I propose we select a large froup of pages, say 1M 14:21:49 ... decide some portion of the target pages to decorate (perhaps just headings) 14:22:00 matatk: We can test rendering to test how it looks rendered apart from semantic accuracy 14:22:00 ... then have a script screenshot the page 14:22:12 ... we would then see if symbol rendering would break pages 14:22:40 ... the mappings would be part of the registry 14:22:46 matatk: mappings could become registry updates 14:22:52 ... the testing, on rendering would be associated with the specification 14:22:54 matatk: we can work on apart from unicode 14:23:47 janina: ARASAAC is not going into Unicode. 14:23:50 Russell: Agree 14:24:33 janina: The value proposition is that we (a) enable the decoration of symbols and (b) they will render in the symbols ideal for the end user 14:24:58 scribe+ 14:25:08 Lionel_Wolberger: Should we be writing an Explainer before TPAC? 14:26:00 janina: Need to figure out priorities and allocate time as best we can. 14:26:08 janina: We have some next steps. 14:29:12 matatk: If we find unicode not in, it's a reason to go back and update 240 14:29:28 matatk: If the outcome is we'll wait and implement, that's a good outcome 14:29:44 matatk: But also is let's take the registry path in that case; also a good outcome 14:30:03 Russell: I think we're understanding it's not in this year 14:30:20 matatk: Only to know if there's a substantive reason 14:33:50 matatk: We need acceptance from WHAT to push further on adoption with Unicode 14:34:37 Lionel_Wolberger: Our main Adapt TF page from W3C links to https://www.w3.org/WAI/about/groups/task-forces/personalization/ 14:34:51 ... suggest Roy bounce that link to https://www.w3.org/WAI/about/groups/task-forces/adapt/ 14:35:52 Lionel_Wolberger: Suggest our Explainer move symbols up top 14:37:01 zakim, next item 14:37:01 I see a speaker queue remaining and respectfully decline to close this agendum, Lionel_Wolberger 14:37:04 q? 14:37:04 q? 14:37:06 q? 14:37:06 ack me 14:37:07 matatk, you wanted to discuss mapping exercise and to discuss testing 14:37:10 ack matatk 14:37:13 zakim, next item 14:37:13 agendum 4 -- WKD Github actions and PRs -- taken up [from janina] 14:37:22 q+ 14:37:59 ack ma 14:38:09 matatk: Have read most ... very exciting 14:38:29 matatk: I read the materials 14:38:38 ... thanks to Abhinav for the overview 14:38:50 ... there is room for Adapt to define semantics and types of links 14:39:18 ... Linksets supports a rich language for stating, here are links from a particular page 14:39:32 ... e.g., we could state 'here is the accessibility statement for this page' 14:39:51 ... e.g., we could state 'here is the relevant help and support for this page' 14:40:07 ... the significant challenge I see is a "one to many" issue 14:40:17 ... there is no wild card for assigning these mappings 14:40:47 ... Given that I could not find this, it seems a site would have to assign a linkset for every single page 14:40:52 ... There is a standard for URL wildcards 14:41:00 ... so logically, these should be able to be combined 14:41:16 Abhinav: To restate, if a given destination e.g., home, is common to many pages 14:41:29 ... how do we assign this common 'home' page to every single page 14:43:02 https://www.rfc-editor.org/rfc/rfc9264.html#name-link-target-object 14:45:13 matatk: We could ask Phil these questions 14:45:17 +1 14:45:47 matatk: If Phil says no, perhaps we will consider modifying linksets to meet our needs 14:46:38 q+ 14:47:02 q? 14:47:08 ack Lionel_Wolberger 14:47:28 Abhinav: So we could look into extending the RFC if we need to add that capability? 14:47:51 Lionel_Wolberger: Who's the standards body here? 14:48:03 Abhinav has joined #adapt 14:48:06 matatk: IETF (same as well-known URIs) 14:48:18 ... We are talking about IETF and RFC 9264 14:49:56 { "linkset": 14:49:56 [ 14:49:56 { "anchor": "https://example.net/bar", 14:49:56 "next": [ 14:49:57 {"href": "https://example.com/foo1"} 14:49:57 ] 14:49:57 }, 14:49:58 { "anchor": "https://example.net/boo", 14:49:58 "https://example.com/relations/baz" : [ 14:49:58 {"href": "https://example.com/foo2"} 14:49:59 ] 14:49:59 } 14:49:59 ] 14:50:00 } 14:50:50 { 14:50:50 "linkset": [ 14:50:50 { 14:50:50 "anchor": "https://example.com/*", 14:50:51 "href": "https://example.com/home", 14:50:51 "rel": "home" 14:50:51 } 14:50:52 ] 14:50:52 } 14:51:36 Abhinav: I suspect this will not support wildcards 14:57:35 zakim, end meeting 14:57:35 As of this point the attendees have been janina, Abhinav, matatk, Lionel_Wolberger, Russell 14:57:37 RRSAgent, please draft minutes 14:57:38 I have made the request to generate https://www.w3.org/2024/08/06-adapt-minutes.html Zakim 14:57:44 I am happy to have been of service, Lionel_Wolberger; please remember to excuse RRSAgent. Goodbye 14:57:45 Zakim has left #adapt