08:23:13 RRSAgent has joined #personalization 08:23:13 logging to https://www.w3.org/2022/01/17-personalization-irc 08:23:15 RRSAgent, make logs Public 08:23:16 please title this meeting ("meeting: ..."), Lionel_Wolberger 08:25:30 meeting: APA Personalization Task Force January 17th Meeting 09:43:51 Roy has joined #personalization 09:57:14 Roy has joined #personalization 10:24:22 Roy has joined #personalization 15:06:12 RRSAgent has joined #personalization 15:06:12 logging to https://www.w3.org/2022/01/17-personalization-irc 15:06:19 RRSAgent, make minutes 15:06:19 I have made the request to generate https://www.w3.org/2022/01/17-personalization-minutes.html Matthew_Atkinson 15:06:31 zakim, start meeting 15:06:31 RRSAgent, make logs Public 15:06:32 please title this meeting ("meeting: ..."), Lionel_Wolberger 15:06:50 agenda? 15:06:52 meeting: APA Personalization Task Force January 17th Meeting 15:07:56 scribe: Lionel 15:08:03 zakim, next item 15:08:03 agendum 1 -- Content Module Implementations Status (Follow-up on i18n issue #144) -- taken up [from Lionel_Wolberger] 15:08:58 Janina: We have a zip file (the hummous recipe) to demonstrate the RTL and LTR switches will work well with Personalization's proposed markup 15:09:05 ... The file has English and Hebrew 15:09:16 ... and is marked up with appropriate symbols 15:09:40 ... We had in mind the Chrome extensions that Lisa previously 15:10:03 ... When we have it working we will send this with a cover note to i18n, and show them how to render the Hummous recipe 15:10:25 ... the Chrome extension is parsing the page looking for an aui- prefix rather than data- ('data dash') 15:10:31 q+ 15:10:46 ... the way forward, either change the chrome extension and change the code to parse for data- 15:11:04 ... or change the Hummous file data- to aui- (or whatever is required) 15:11:17 ack Matthew_Atkinson 15:11:20 Matthew_Atkinson: I have some updates to add 15:11:41 Matthew_Atkinson: I changed the Hummous to aui- (since that was easiest) 15:11:45 ... we noted a further issue 15:12:04 present+ 15:12:09 ... the mappings of symbol IDs to Symbols do not exist for all the concepts referenced in the Hummous Recipe 15:12:16 present+ 15:12:26 ... Matt & Lisa met this morning and confirmed this issue 15:12:39 ... the extension does enable some control of the mappings 15:13:03 ... We see a way forward 15:13:06 ... hard-code, etc 15:13:18 ... will take some time 15:13:30 ... THe chairs and the committee thank Lisa for her time this morning 15:14:32 LisaSeemanKest: The symbols are loaded in a separate file to enable more symbol choices by end-users 15:14:54 ... one use case, a user has a symbol file on their phone and another file on their computer 15:15:03 ... the symbol file reference should be easily found 15:16:02 Matthew_Atkinson: The extension could support a mapping of all symbols to Bliss, and the Personalization Content module would encourage such mappings 15:16:17 q? 15:16:57 Matthew_Atkinson: To clarify, the "Wikihow Cup of Tea" example works fine 15:17:23 ... The Hummous recipe did not have the proper markup (no aui- markup) 15:18:10 Matthew_Atkinson: Janina to draft the email that we will send to i18n 15:18:27 ... this email should bundle a procedure to allow the i18n folks to run the exatension 15:18:43 ... with a usage stipulation, that the extension is not meant for wide distribution 15:18:58 ... I plan to clarify what is left to complete this week 15:20:12 janina: I will put in the cover letter why the markup changed 15:22:11 LisaSeemanKest: The extension also renders "simplify" 15:22:33 ... along with Ayeleth's github, which is an open script that authors can serve on their page 15:22:49 ... offers a widget (overlay) approach 15:23:10 Matthew_Atkinson: We demo on Ayeleth's script 15:24:48 Lionel_Wolberger: We met with Bruce from Access Board this week and we are going ahead with the plan to mark up the 15:24:50 ... Title: Online Architectural Barriers Act (ABA) Complaint Form 15:25:00 ... URL: https://cts.access-board.gov/formsiq/form.do?form_name=Complaint%20Form 15:25:26 ... which is stored in a git for open access in the ATBCB git 15:25:36 ... https://github.com/atbcb/usab-uswds/tree/master 15:26:12 ... Might Google be interested in marking up something? 15:26:59 agenda? 15:27:19 zakim, next item 15:27:19 agendum 2 -- Defining shortnames for the modules -- taken up [from Lionel_Wolberger] 15:27:57 Personalization: Content Module 15:28:06 Personalization: Help and Support Module 15:28:15 Personalization: Tools Module 15:29:11 LisaSeemanKest: If we rethinkg from a blank slate, the "help and support" is more about alternatives and support 15:29:26 ... there is a bit of ambiguity because the help icon is addressed in the Content Module 15:29:37 ... but alternatives isn't perfect, as symbols are also alternatives 15:29:38 q+ 15:29:48 ... but content is addressed in "help and support" as well 15:30:04 ... not sure these suggested names will help guide a newbie 15:30:22 ... Help and Support is also about content 15:30:39 q+ 15:30:47 ... we may need to lean on the one sentence summary that we have written on the wiki regarding each module 15:30:51 q? 15:31:42 Matthew_Atkinson: The discussion was regarding whether we are providing semantics or alternative content 15:31:56 ... the differentiation between semantics and alternative content seemed significant 15:32:21 ... these short names dont lose anything, and have a consistency, but it's worth thinking it through 15:32:31 ack: Matthew_Atkinson 15:32:59 janina: The fact that we are on the brink of CR, the most important decision is to decide on the scheme, the pattern of these names 15:33:12 ... we don't want to have to rename the modules 15:33:45 ... so we don't have to worry too much about the actual titles of the 2nd and 3rd modules, its the first module we need to nail, as well as the overall scheme 15:34:43 ... I did check the original name, and the name was Personalization Semantics (no concept of three modules was present then) 15:35:20 agenda? 15:36:04 zakim, next item 15:36:04 I see a speaker queue remaining and respectfully decline to close this agendum, Lionel_Wolberger 15:36:19 agenda? 15:36:31 q? 15:36:40 ack Matthew_Atkinson 15:36:52 LisaSeemanKest: When can COGA start brainstorming use cases for the upcoming modules 15:36:52 ack ja 15:36:58 RRSAgent, make minutes 15:36:58 I have made the request to generate https://www.w3.org/2022/01/17-personalization-minutes.html Matthew_Atkinson 15:37:18 +1 15:38:00 scribe: Lionel_Wolberger 15:38:02 RRSAgent, make minutes 15:38:02 I have made the request to generate https://www.w3.org/2022/01/17-personalization-minutes.html Matthew_Atkinson 15:38:10 LisaSeemanKest: Someone from Personalization should give an overview of the module 15:38:37 ... the call is on Thursdays 15:39:21 Lionel chuckles 15:40:13 ... allow the group to associate the conversation with the representative 15:40:33 scribe- Lionel 15:40:43 scribe+ Lionel_Wolberger 15:40:53 RRSAgent, make minutes 15:40:53 I have made the request to generate https://www.w3.org/2022/01/17-personalization-minutes.html Roy 15:41:14 present+ 15:41:35 present+ 15:42:21 What is the role of COGA in curating and bringing our next module to CR 15:42:34 RRSAgent, make minutes 15:42:34 I have made the request to generate https://www.w3.org/2022/01/17-personalization-minutes.html Roy 15:43:35 zakim, next item 15:43:35 agendum 3 -- Planning COGA January meeting on Our Other Two Modules -- taken up [from Lionel_Wolberger] 15:43:39 zakim, next item 15:43:39 agendum 3 was just opened, Lionel_Wolberger 15:43:45 zakim, close item 3 15:43:45 agendum 3, Planning COGA January meeting on Our Other Two Modules, closed 15:43:47 I see 2 items remaining on the agenda; the next one is 15:43:47 4. What is the role of COGA in curating and bringing our next module to CR [from Lionel_Wolberger] 15:43:54 zakim, close item 4 15:43:54 agendum 4, What is the role of COGA in curating and bringing our next module to CR, closed 15:43:56 I see 1 item remaining on the agenda: 15:43:56 5. Is the new W3C Registry Suitable for Bliss Symbol Lookup Functions? [from Lionel_Wolberger] 15:44:14 janina: A note is something a WG says 15:44:24 ... a statement is something the W3C says, not just a WG 15:44:47 ... then there is a formal way to create a registry at w3c.org 15:45:05 ... for example, have an index number and a mapping to bliss symbols 15:45:22 ... and discuss the details of how this registry would be defined (e.g., how many columns) 15:45:29 ... the registry would support an API 15:45:48 ... in the case of the symbols, it would be far more useable than the PDF of symbols 15:45:52 q? 15:46:10 ... we would need others to be in that conversation 15:46:21 ... and might need to consult with someone from Bliss 15:46:44 ... we may need to re-examine the terms surrounding the Bliss symbols 15:48:16 RRSAgent, make minutes 15:48:16 I have made the request to generate https://www.w3.org/2022/01/17-personalization-minutes.html Matthew_Atkinson 15:49:01 present+ LisaSeemanKest 15:49:03 RRSAgent, make minutes 15:49:03 I have made the request to generate https://www.w3.org/2022/01/17-personalization-minutes.html Matthew_Atkinson 15:49:29 present+ janina 15:49:32 RRSAgent, make minutes 15:49:32 I have made the request to generate https://www.w3.org/2022/01/17-personalization-minutes.html Matthew_Atkinson 15:49:41 present+