W3C

– DRAFT –
WAI-Adapt Teleconference

10 Sep 2024

Attendees

Present
Abhinav, janina, Lionel_Wolberger, matatk, Russell
Regrets
-
Chair
Lionel_Wolberger
Scribe
Lionel_Wolberger, matatk

Meeting minutes

Introduction, logistics. Any Updates?

janina: Discussed some TPAC items

matatk: Let's meet next week, correct?

Lionel_Wolberger: Yes, all agree.

Lionel_Wolberger: 24-Sept will be TPAC, no Adapt Meeting
… 1 October follows TPAC, and APA and Adapt TF will take the day off. No meeting.

<janina> https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2024

<janina> Above is the APA TPAC Wiki

Symbols (Issue 240)

matatk: Discussed the options we have regarding the Explainers
… (1) Adapt symbol attribute (2) AAC registry
… for the Adapt symbol attribute, we will see there Bliss ID and Unicode Integer values

janina: Turning to WHAT-WG, we want their buy-in on the decimal integer values

matatk: Its Bliss concept ID (a decimal integer) vs. a Unicode representation (might be a hex representation?)

janina: We can focus on authoring, as this motivates WHAT-WG. Authoring is not our main focus, implementation is
… we want WHAT-WG to picture the authoring scenario, we will stress that this is a minimal burden as we expect only one symbol per line
… we do foresee entire sentences and paragraphs to be marked up with symbols

Lionel_Wolberger: A spice in the stew and not the main course

matatk: A good authoring demo is the prototype we currently have
… but the prototype tool marks up the entire sentence
… we would like to markup only certain words, to aid in visual scanning and navigation

<Lionel_Wolberger> +1

Russell: I agree it's a good idea
… when marking up long texts with many symbols, you would need an expert

janina: 'Ordinary mortals' who can add one symbol per line

matatk: So we will not change the prototype code (no time), we just need a prepared example that suits this 'one symbol per line' use case

Well Known Destinations

janina: Same focus, how to approach WHAT-WG properly

<matatk> Comments welcome: w3c/adapt#261

<gb> Pull Request 261 Add explainers for proposed new specs (by matatk)

<matatk> matatk: Re-structured the Explainer.

https://github.com/w3c/adapt/tree/add-explainers/explainers

<matatk> https://github.com/w3c/adapt/blob/add-explainers/explainers/well-known-destinations.md

<matatk> Abhinav: I will have a look over the next week

<matatk> Abhinav: Would we be OK with a hybrid approach?

matatk: I highlighted what I think are our main technical requirements, and how each proposed approach may meet them.
… Essentially any approach that meets them would be fine with us I think, though I suspect it wouldn't contain both Well-known URIs and Linksets.

Lionel_Wolberger: actions?

matatk: Will put agendas on the calendar.

Minutes manually created (not a transcript), formatted by scribe.perl version 229 (Thu Jul 25 08:38:54 2024 UTC).

Diagnostics

All speakers: janina, Lionel_Wolberger, matatk, Russell

Active on IRC: Abhinav, janina, Lionel_Wolberger, matatk, Russell