Meeting minutes
Introductions. Updates.
WKD Slides for AC Meeting review
<gb> Pull Request 267 Initial AC2024 slides (by matatk)
Preview link is in the PR, or: https://
Lionel_Wolberger: Feedback:
swap test tube for BETA stamp rather than test tube
highlight in dark mode
well-known destinations - same slide, reveal
*Port* 80
Search icon for other example
14 - Add a title e.g. "variation in terms" title may be needed
14 - Can use two columns
14 - Add the French and Japanese versions of log-in
Could then drop 15
16 (complex design) is good, but maybe not needed
19 not needed
Could show the change-password URL
(as you mentioned)
Can save a slide in the extension part
For next steps, be sure to include all relevant ones
Lionel_Wolberger: Does anyone else have comments on the presentation deck?
<Lionel_Wolberger> +1 great work on the new deck matatk!
WKD Github actions and PRs
Russell: Recap: We can't use the not-yet-ratified code points for 240, but we can make up our own example and add a note to the text drafted with matatk.
Lionel_Wolberger: registry?
Russell: We can state that when the Unicode proposal goes through, the symbols will be displayed using Unicode, which inherently makes the text string available.
… There's a function in every programming language to convert the number to the code point. Or we could publish the code point indexes along with the BCI indexes.
<Lionel_Wolberger> https://
<Lionel_Wolberger> matatk: Suggest we put a code point placeholder, to see what the registry will look like with the new column
matatk: I will find Russell and my latest text; send to Russell to tweak the code points; wordsmith the caveats/notes; post to the Adapt list for consensus; then I will post on 240 when Adapt has consensus.
Lionel_Wolberger: The current registry opens Abstract, Status, Introduction. Then jumps in. I propose we add one more top-level heading ~'Reference ID' where we write 'in the ID column you'll find the Bliss ID. In future we may replace this with another unique ID' - then we're notifying users in this draft.
Russell: Could I suggest something other than 'replace' or people won't use it.
<Lionel_Wolberger> +1 to Russel's suggestion
<Lionel_Wolberger> Lionel_Wolberger: 2. ID (that's the proposed heading)
<Lionel_Wolberger> ... Body to say: The ID column provides a unique identifier to serve as a non-ambiguous key for table lookup. The ID column lists the relevant BCI ID. In future, the Registry may add another ID to facilitate interoperation with other symbol sets.
ACTION: matatk: Find Russell's and my latest text; send to Russell to tweak the code points; wordsmith the caveats/notes; post to the Adapt list for consensus; then post on 240 when Adapt has consensus.
<gb> Created action #268
<Lionel_Wolberger> Lionel_Wolberger: ... in future we may add a Unicode Unique ID as well, allowing end users to use either ID.
Russell: Unicode has already published in their code point space map a section likely for Blissymbolics. But we shouldn't use any proposed numbers, as it would encourage people to use them, and they could change.
Russell: I think it would make it clear if we _do_ mention Unicode.
Russell: Is it the idea that down the road, other symbol sets could use the registry, or get published as part of the registry? In which case they'd have their own IDs.
Lionel: We should discuss this; this is a good point; but we need to discuss that later.
+1 to the sentence (mentioning Unicode, as Russell suggests)
<Russell> +1 to the sentence
matatk: Nobody can use this in the web content sense (yet - hopefully they will soon) but in terms of the registry, as it's out there, we should clearly signpost the plans.
ACTION: matatk: Add IDs section to Registry draft
<gb> Created action #269