– DRAFT –
Adapt Weekly Teleconference

<matatk> gb, status

<gb> matatk, the delay is 15, issues are on, names are on, full issues are printed 10 at a time; and the repository is w3c/adapt

<matatk> gb, off

Introduction, Any Updates?

Virtual TPAC

matatk: We have until the end of the month to submit

matatk: For clarity, we have proposed a lightning talk for the AC Breakouts, end of April
… draft proposal submitted
… focus on Well Known Destination, the use case and a demo
… we are exploratory at this stage
… breakout day is 12 March

gb, on

Lionel_Wolberger: Proposing, we commit to the 50m session. Matt to prepare slides, 5 March Adapt meeting for final review prior.

+1

<janina> +1

<russell> +1

<Abhinav> +1

ACTION: matatk: Prepare slides for Breakouts Day session - due 2024-03-05

<gb> Created action #262

ACTION: matatk: Post draft session proposal - due 2024-02-21

<gb> Created action #263

Github actions and PRs

Lionel: https://github.com/w3c/adapt/discussions/256

<gb> Discussion 256 [Accessibility-Meta] How plans for accessibility improvements will be translated? (by abhina-kumar)

Lionel: Look at issue https://github.com/w3c/adapt/discussions/255

<gb> Discussion 255 [Accessibility-Meta] How known issues will be presented? (by abhina-kumar)

Lionel_Wolberger: This is similar to the previous discussed discussion which is about the content about the accessibility statement.
… This is important work, but we'll take it up after at least FPWD for well-known destination.

#251

<gb> Discussion 251 Lifecycle for "well-known URI" updates (by matatk)

matatk: Since our Well Known Destination proposal is essentially allocating a name space
… it is a question, will people be able to turn directly to IANA to assign a Well Known URL in our name space?

<Abhinav> https://en.wikipedia.org/wiki/Well-known_URI#:~:text=A%20well%2Dknown%20URI%20is,well%2Dknown%20locations%20across%20servers.

Abhinav: I visually inspected the current allocated Well Known Destinations in the Wikipedia article and I do not see any "name spaces" allocated there

<Abhinav> https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml

#239

<gb> Pull Request 239 Fix explainer typos (by leo-diehl)

Issue 240 Way Forward

#240

<gb> Issue 240 Could we build symbolic annotations with existing Web standards? (by DuncanMacWeb) [i18n-tracker]

janina: If this is accepted, we'll need to make a new working draft. CfC within APA and then publish an updated CR working draft,

matatk: We can then continue soliciting for implementations.

janina: Actually, this involves updating two specs (symbols module, and registry)

Lionel_Wolberger: Showing the registry, asking questions about the Registry

russell: The existing ID columns could be clarified as being a Bliss ID, e.g. call it Bliss Symbolics ID
… the equivilant Unicode representation of Bliss could also be displayed, but it is not approved yet
… and prior to approval, Unicode does not want the numbers displayed