12:55:36 RRSAgent has joined #adapt 12:55:40 logging to https://www.w3.org/2023/05/01-adapt-irc 12:55:40 RRSAgent, make logs Public 12:55:41 please title this meeting ("meeting: ..."), Lionel_Wolberger 12:55:55 Meeting: Adapt Working Group Weekly Teleconference Monday May 1st 2023 12:56:00 agenda+ A11y4Children follow-ups 12:56:03 agenda+ Issue 240 update, "Could we build symbolic annotations with existing Web standards?" 12:56:05 agenda+ Gap Analysis, https://github.com/w3c/adapt/wiki/Gap-Analysis 12:56:17 agenda+ Review open issues 12:56:19 agenda+ Test to show rendering symbols do not 'break' existing pages 12:56:21 agenda+ Recruiting 12:56:24 agenda+ Registry update 12:56:26 agenda+ Symbol Module Implementations 12:56:29 agenda+ User Agents and Symbols (e.g. Immersive Reader) 13:48:42 Lionel_Wolberger has joined #Adapt 13:48:45 agenda? 13:58:47 Sharon has joined #adapt 14:00:17 matatk has joined #adapt 14:00:38 agenda? 14:05:18 mike_beganyi has joined #adapt 14:05:21 present+ 14:06:27 janina has joined #adapt 14:06:31 present+ 14:06:31 zakim, next item 14:06:31 agendum 1 -- A11y4Children follow-ups -- taken up [from Lionel_Wolberger] 14:06:35 scribe+ 14:06:38 present+ 14:06:39 present+ 14:07:35 Russell has joined #adapt 14:07:40 present+ 14:07:59 present+ 14:08:08 agenda? 14:08:38 rrsagent, make minutes 14:08:40 I have made the request to generate https://www.w3.org/2023/05/01-adapt-minutes.html matatk 14:09:01 zakim, next item 14:09:01 agendum 2 -- Issue 240 update, "Could we build symbolic annotations with existing Web standards?" -- taken up [from Lionel_Wolberger] 14:09:06 zakim, take up item 1 14:09:06 agendum 1 -- A11y4Children follow-ups -- taken up [from Lionel_Wolberger] 14:09:25 Lionel_Wolberger: Notes the document from Web accessibility for Children Community Group 14:09:32 https://docs.google.com/document/d/18CDOklgwNYK2gILIz_IADeU_TiyQW6kuJWfP3Nhfk1c/edit?usp=sharing 14:10:09 Lionel_Wolberger: Finding well formed opinions based on years of experience 14:10:22 Lionel_Wolberger: They address areas I believe we haven't 14:10:34 Lionel_Wolberger: proposing new attributes, etc 14:10:44 q? 14:10:51 Lionel_Wolberger: we'll need to consider how to work with this 14:10:58 q? 14:11:32 matatk: Didn't see it via our archive 14:12:06 matatk: Believe some overlap to COGA, e.g. trauma 14:12:52 matatk: phps our concern is to be careful of how many attributes and not overdo 14:13:05 matatk: think the what rather than the how may be a useful approach? 14:13:26 q? 14:13:38 scribe+ 14:13:55 janina: I've also not read it yet, but +1 to matatk 14:14:23 Lionel_Wolberger: Notes their Google Doc is packed with compelling ideas 14:14:41 Lionel_Wolberger: we'll have to schedule processing this 14:14:43 q? 14:15:37 q+ 14:15:52 q? 14:16:03 Lionel_Wolberger: asking what our next steps should be? 14:16:07 ack mat 14:16:25 matatk: agree we need a bit of time to process this 14:16:27 q+ 14:16:47 matatk: Do we have existing expertise -- is there sufficient staffing to work on it? 14:17:09 matatk: Should note finishing symbols is a priority, but that also gives us a bit of time 14:17:27 agenda? 14:17:44 q+ 14:17:59 matatk: suggests pinging COGA for staffing 14:18:30 matatk: we need to do some expectation management 14:19:26 ack mi 14:19:45 mike_beganyi: agree on collab review and synthesizing priorities 14:21:28 janina: Fine with us consulting COGA on guidance, use cases, etc. but they may not be able to help with the technological/architectural issues. 14:21:47 ... With respect to UDL, I think the question will be: how few tags can we introduce to meet most of the use cases? 14:22:26 ... Are they generalizable in such a way that we can re-organize them on the fly? E.g. in some cases, a H1 may become an H2. I think EPub/DPub would be interested in this (from the conversations we've had). 14:22:48 ... RQTF is happy to work on this [UDL] but they need specific questions from us. 14:23:57 Lionel_Wolberger: re-organizing? 14:24:14 janina: You might have a recipe book; the H1s could be e.g. Chicken, or they could be Soups. 14:24:21 ... Is that where their thinking is? 14:24:33 s/where their/where the CG's/ 14:25:12 Lionel_Wolberger: Will return to this hopefully with some ideas of what next 14:25:40 matatk: agrees 14:26:20 zakim, next item 14:26:20 I see a speaker queue remaining and respectfully decline to close this agendum, Lionel_Wolberger 14:26:24 q? 14:26:26 ack ja 14:26:29 zakim, next item 14:26:29 agendum 2 -- Issue 240 update, "Could we build symbolic annotations with existing Web standards?" -- taken up [from Lionel_Wolberger] 14:26:59 Lionel_Wolberger: issue 240 with over 3K words 14:27:31 Russell: has this grown? Seems there's more there now 14:27:41 Lionel_Wolberger: Perhaps; latest is last week 14:27:45 Russell: I know him 14:28:17 Russell: Doing unicode for BCI; the registrar for the subtag registry in the unicode group 14:29:07 Russell: proposing rather than the BCI ids we use the unicode encoding 14:29:28 Russell: I agree it will be widely used once established 14:30:16 Russell: concern is that it would be using word spellings for ids, not sure that's what we want 14:30:19 q+ 14:30:54 Russell: believe we would want unique ids 14:31:12 q? 14:33:04 Russell: notes that it would be 0x.. + 0x.. something else rather than our ids 14:33:18 russel also bci can change; they're generative 14:33:23 ack ja 14:33:44 Russell: over time what once had meaning ceases to have meaning 14:34:20 Russell: the unique id wouldn't change, though its representation could 14:37:00 q+ 14:37:03 russel somewhat like the same word, different spellingrusselonce unicode is there it wouldn't change, only expanded 14:37:39 Russell: we do have ids for each unicode; but also id for concatinated unicode chars 14:38:05 Russell: puts me still on the fence here 14:38:41 Russell: bci codes are dependent on bci which should persist, but phps an unnecessary dependency 14:39:01 Russell: someone will need to maintain the db 14:39:24 Russell: the symbols aren't self explanatory, so concepts need to be maintained 14:41:18 Lionel_Wolberger: we need a primary key, and the unicode may not quite function that way 14:41:21 ack mat 14:41:27 matatk: very helpful discussion 14:42:01 matatk: not up to date on thread but 3 concerns 14:42:31 matatk: whether unique values are the symbols or the building blocks for the symbols 14:42:35 matatk: understood both 14:42:54 matatk: I've seen symbols get deprecated, changed, etc 14:43:03 matatk: was that accurate? 14:43:39 matatk: we need to know whether we could manage a concatinated set of 0X values 14:43:59 Russell: correct 14:44:32 Russell: some of this is historical to bliss and how contractions, etc, work 14:45:06 The previous standard Russell mentioned: https://en.wikipedia.org/wiki/ISO-IR-169 14:45:43 Russell: notes first was pictographic but then parsed for component parts most of which (but not all) are meaningful on their own -- apparently about 1500 14:46:36 Russell: unicode cannot fully display every bliss construction 14:47:54 Russell: as unicode evolves, though, it will likely do even better at supporting bliss 14:48:47 Russell: the unicode activity is impacting bliss extensions; people consider it as they develop symbol construct 14:49:02 q? 14:50:01 Lionel_Wolberger: let's see what our next action might be on this ... 14:50:14 Lionel_Wolberger: shares the registry screen 14:51:26 Lionel_Wolberger: if we understand 240 as a suggestion to change our primary key 14:52:25 Lionel_Wolberger: if it's pretty much a straight up replacement of ids for unicode values or concatinated unicode values that could be ok 14:52:55 Lionel_Wolberger: looking at an example with "mind" 14:53:04 Russell: great example 14:53:20 24488 drug,mind-altering_drug 14:53:25 Russell: "mind altering drugs" would consist of two values 14:53:41 15471 mind,intellect,reason 14:53:42 Russell: have actually done it that way, as a compound 14:54:06 20518 sport 14:54:18 Russell: similarly "mind sports" 14:54:51 Lionel_Wolberger: thinking the ambiguity and ordering makes unicode a less useful key 14:54:57 Russell: certainly less readable 14:55:50 Proposed response: The topic was discussed at [put offset] 14:56:07 ... we do not find that the unicode spellings will substitute for the ID as we currently use it 14:56:18 ... which constitutes a nonambiguous, unique "Primary Key" 14:56:35 ... in the sense of a Primary Key in SQL and relational database theory 14:56:58 21799 mind_sports 14:57:17 matatk: aren't we already sometimes concatinating? 14:57:38 Russell: sometimes when the same concept is repeated -- 14:58:02 ... we are discussing it, we are not sure that this proposal will substitute for the 'primary key' 14:59:33 zakim, end meeting 14:59:33 As of this point the attendees have been mike_beganyi, janina, Sharon, Lionel_Wolberger, matatk, Russell 14:59:35 RRSAgent, please draft minutes 14:59:36 I have made the request to generate https://www.w3.org/2023/05/01-adapt-minutes.html Zakim 14:59:42 I am happy to have been of service, Lionel_Wolberger; please remember to excuse RRSAgent. Goodbye 14:59:42 Zakim has left #adapt