14:54:56 RRSAgent has joined #adapt 14:55:01 logging to https://www.w3.org/2022/12/19-adapt-irc 14:55:01 RRSAgent, make logs public 14:55:02 Zakim has joined #adapt 14:55:02 Meeting: WAI Adapt Task Force Teleconference 14:55:02 Date: 19 December 2022 14:55:12 chair: sharon 14:55:16 agenda? 14:55:37 agenda+ Holiday schedule reminder 14:55:52 agenda+ CR status 14:56:10 agenda+ Symbol Module Implementations 14:56:27 agenda+ Autocomplete 14:56:42 agenda+ Recruiting 14:56:47 agenda? 14:57:42 matatk has joined #adapt 15:01:34 Lionel_Wolberger has joined #adapt 15:01:41 present+ 15:01:44 agenda? 15:02:17 present+ 15:02:27 present+ 15:02:33 present+ 15:05:15 scribe: Lionel_Wolberger 15:07:40 zakim, next item 15:07:40 agendum 1 -- Holiday schedule reminder -- taken up [from sharon] 15:08:40 janina: Dec 26 off for Winter Holiday. Jan 2 off, too close to New Years. Jan 9 on, Jan 16 off (MLK) 15:09:50 mike_beganyi has joined #adapt 15:09:55 present+ 15:09:58 zakim, next item 15:09:58 agendum 2 -- CR status -- taken up [from sharon] 15:10:36 becky has joined #adapt 15:10:47 present+ 15:14:01 https://github.com/w3c/adapt/pull/237 15:14:56 janina: We are merging Matthew's PR into the Explainer 15:15:12 janina: Should we publish an updated explainer working draft? 15:15:37 becky: Yes. Major enough changes were made, and updating working drafts is routine. 15:15:48 sharon: This includes all the symbol updates as well, so yes 15:15:48 +1 15:15:49 +1 15:15:57 +1 15:15:59 +1 15:16:03 q? 15:16:38 RESOLVED: Task Force requests publication of Explainer updated working draft 15:16:48 rrsagent, make minutes 15:16:50 I have made the request to generate https://www.w3.org/2022/12/19-adapt-minutes.html Lionel_Wolberger 15:17:10 q? 15:17:24 zakim, next item 15:17:24 agendum 3 -- Symbol Module Implementations -- taken up [from sharon] 15:23:13 Lionel_Wolberger: I was thinking that one implementation could be that, a symbol board user could get an interopable JSON file describing the symbols that were on the board that I learned 15:23:28 ... then I as a patient could have a continuation of my therapuetic surrounding 15:24:49 janina: Consider that current symbol dedicated-devices could also load and render symbols for web pages. 15:25:21 ... if they are increasingly using small device off-the-shelf operating systems, where Web support is built in already 15:32:01 sharon: We had minuted a discussion with a Firefox developer 15:32:11 janina: And Matt's prototyped AAC tool 15:32:56 q? 15:33:34 zakim, next item 15:33:34 agendum 4 -- Autocomplete -- taken up [from sharon] 15:34:20 matatk: This is part of an overall due diligence series, taking a new look at our architecture. 15:36:27 ... There are a few technical details to check against the last version of the spec 15:36:35 ... autcomplete may not work in all our use cases 15:37:33 ... the rules already seemed quite complex, so broadening autocomplete may be out of the question 15:37:37 q+ 15:38:10 ... Critical to check exactly how we are using it 15:38:27 ack Lionel_Wolberger 15:38:46 +1 15:40:09 q+ 15:40:44 +1 to Lionel's idea of doing something structured, and recording the result 15:40:55 Lionel_Wolberger: Sounds like we are embarking on a gap analysis between certain pre-existing standards and our proposed standard. 15:41:07 ... if so, we should summarize any findings, so we can refer to this in future. 15:41:10 ack sharon 15:41:17 ack Lionel_Wolberger 15:41:27 +1 to sharon, Janina, re making the results clear and discoverable. 15:41:36 janina: We need to satisfy TAG that we have thought this through 15:43:52 q+ 15:45:06 q+ 15:45:14 ack Lionel_Wolberger 15:45:35 Lionel_Wolberger: Gap analysis can proceed lightweight as follows: 15:45:44 ... Identify the two HTML elements that you want to compare 15:46:02 Determine the purpose and intended use of each 15:46:12 q? 15:46:13 Lionel_Wolberger: Determine the purpose and intended use of each 15:46:26 ... Compare the structure and content of the two elements 15:46:43 .... Identify any discrepancies or differences between the two elements. These may include differences in structure, content, or functionality. 15:47:04 ... Summarize list of the specific areas where the two elements differ and note any potential impacts or consequences of these differences. 15:47:57 ... look at root cause of any discrepancies or differences that you have identified. 15:48:17 ack matatk 15:49:09 Starting point: https://github.com/w3c/adapt/wiki/Comparison-of-ways-to-use-vocabulary-in-content 15:51:07 matatk: The table, https://github.com/w3c/adapt/wiki/Comparison-of-ways-to-use-vocabulary-in-content, is an ideal starting place for these gap analyses 15:51:14 ... We focus on the delivery mechanism 15:51:18 ... the vocabulary style 15:51:33 ... Then there are cases where we decided that we are going to use an attribute. 15:51:43 ... Then, given that decision that we are committed to using an attribute 15:52:06 ... we have a decision, shall we use a pre-existing attribute or a newly invented attribute 15:52:13 ... @rel was a good example, it was similar to 'destination' 15:52:46 ... this led to discussion of, what is the minimal number of changes that we require of @rel as-is, to make it do what Adapt TF deems needed for the 'next billion' disabled? 15:53:03 ... We certainly have considered all the different vocabularies 15:53:43 ... I suggest we put the results of our Gap Analyses, such as they might be, and add them to the wiki 15:57:34 janina has left #adapt 17:00:43 rrsagent, make minutes 17:00:45 I have made the request to generate https://www.w3.org/2022/12/19-adapt-minutes.html Lionel_Wolberger