Meeting minutes
<Lionel_Wolberger> present_
Introduction, Any Updates?
matatk: Can attend full call today after all
matatk: And conflicts will only be random--so not regularly this slot
Virtual TPAC submission
matatk: Believe we decided no Wednesday breakouts from Adapt TF
matatk: Arriving Sunday, leaving Saturday
Lionel_Wolberger: Arriving 6AM Monday; leaving late Thursday
janina: Arriving sometime Sunday (from Palm springs); leaving late morning Saturday
matatk: Suggests asking TPAC organizer for any potential ride along
matatk: The APA wiki is up
<matatk> https://
matatk: Notes our conversation with WHAT WG is all Adapt -- both Symbols and WKD
Recruiting
janina: Notes we've yet no IE app from Analou
matatk: Believe she did, but for the wrong group; needs to be APA and wasn't
janina: Yes, unless someone told her APA, she wouldn't have known
matatk: Will resend the link
matatk: It's OK if it waits for her return from holliday
Virtual TPAC submission
Github actions and PRs
matatk: Update on updating our Explainer to expected format
matatk: We have for WKD and need one for Symbols
matatk: Some can come out of the spec and into the Explainer
matatk: I've made an Explainers dir under our repo with a README
matatk: This is the expected organizational structure
matatk: Still need to split out Symbols into its own Explainer--relatively easy task;
matatk: Can even use text from issue 240
matatk: Overall Explainer for Adapt needs to be put into expected format
matatk: Overall should be light because we point to individual Explainers for those details
matatk: When? By TPAC ... We need to point WHAT to this content and have it show up in a form they expect
matatk: Still mulling ...
matatk: Our CR for Symbols ...
matatk: Explainer needs to faithfully map the spec
matatk: Should we write explainer for Unicode? Or match spec
janina: Proposes pulling CR back to WD with a note
matatk: We've had no response; We need actual response to have agreement
matatk: Still Q msg on authoring
janina: Still suggest pull CR to WD and add a Note about status and point to 240
matatk: Agree
russell: We're not yet in Unicode; so can't spec on it because it's not yet in
russell: Like noting alternatives
Russell: We can write to Unicode but also document alternatives so it's all on the table before any implementations
russell: Important that current unicode IDs may change
russell: Until we know we don't know--could be a different block
Symbols: Issue 240 Way Forward
russell: 240 response is written using BCI and not using hex
russell: There will people who will prefer hex and remembering which visual symbol
russell: We should offer that option
<Zakim> matatk, you wanted to discuss representations
matatk: Understood! It's important
matatk: Whatever they think they'l implement is probably what we'll do
matatk: They need to understand composite though
matatk: We should design to make it easy for a parser to understand what representation is being used
matatk: Looking to the future, how do we add more values; i.e. more than one BCI ID
russell: Michael has tried to add every possible symbol into unicode
russell: What will change are the composites; so it is more like English orthography per Janina's concern
russell: There will be additional composites, but not individual code points
matatk: Notes value of attribute not the same as what text is displayed to user
matatk: so not &[values];
russell: For Bliss people, looking at either is fine; but not universal even in AAC world; many do, but not all
<Zakim> matatk, you wanted to discuss authoring considerations and separation of composite values
matatk: Eve if difficult, should be possible to handcraft
matatk: We will need to strongly communicate the composite nature of symbol use in authoring
matatk: to have future potential for future composites, we will need to space separate and comma separate for charac representations, and concepts respectively in the keys
matatk: Just a suggestion
russell: Indicate which kind of ID by how represented?
matatk: comma separation then won't care whether BCI or unicode ...
matatk: Can produce examples ...
<matatk> e.g. adapt-symbol="0x4242, 8857, 0x4444 0x2222, 3856"
matatk: Example has four concepts, first by one char, second by BCI id, third by two chars, and forth by BCI
russell: think I like it
russell: that would work
matatk: Can turn this into an Explainer
russell: Simplifies for talking with people used to thinking this way
matatk: Can see how to write-up in a way that's understandable
Michael and Unicode Incorporation
russell: Paying work has gotten in the way!
russell: Michael is credited some 105 times for unicode contributions
russell: So a matter of time
russell: Google Michael Everson unicode
matatk: Appears to e a Wikipedia on him
russell: We can't do any better--it will happen