W3C

– DRAFT –
Adapt Weekly Telecon

10 March 2026

Attendees

Present
Abhinav, Janina_Sajka, Lionel_Wolberger, Matthew_Atkinson, Russell
Regrets
-
Chair
-
Scribe
Lionel_Wolberger, matatk4

Meeting minutes

Breakouts Day 2026

<matatk4> https://github.com/w3c/breakouts-day-2026/issues

<matatk4> lionel: I think this is a great opportunity to evangelize our work (one, other, or both)

<matatk4> Abhinav: We have presented about destinations before, not sure if there's value in another one this time.

<matatk4> ... We don't have major updates after TPAC, apart from providing people with an update.

<matatk4> janina: I think our criteria should be that we don't repeat ourselves, we should be talking about significant advancement, or things being ready to implement. I think we risk not being granted timeslots as readily in future if we repeat ourselves. Not saying we shouldn''t, but agree with Abhinav that we are not that much further ahead than we were

<matatk4> at TPAC.

<matatk4> Russell: Definitely not with symbols.

<matatk4> janina: I think the group mind is we pass on this particular set of breakouts.

<matatk4> lionel: We can't repeat ourselves, but can we publish by then?

<matatk4> janina: It's end of the month, so unlikely.

<matatk4> lionel: Let's take your objection as an impetus to accomplish things.

<matatk4> janina: Dublin (TPAC, October) should be our target.

matatk4: Let's focus on getting implementations before October

Destinations

The story so far: https://github.com/w3c/adapt/issues?q=is%3Aissue%20label%3Aproposed-destination
… Sorted: https://github.com/w3c/adapt/issues?q=is%3Aissue%20label%3Aproposed-destination%20sort%3Aupdated-asc

https://almanac.httparchive.org/en/2025/

specifically, re robots.txt (and maybe sitemaps; not sure yet?) https://almanac.httparchive.org/en/2025/seo

Lionel_Wolberger: We minuted the discussion in the relevant github issues
… we closed home
… we commented on sitemap

Symbols

Russell: Shared some updates re: Bliss unicode
… while there is no immediate date when Bliss unicode will complete, we note that no other symbol set is even proposed for unicode

Janina: The Adapt TF use case seems to be orthogonal to the Bliss Unicode effort
… Adapt's timeline need not be dependent on Bliss Unicode's completion
… then we can progress, and when one day Bliss Unicode is codified, Adapt's method will still be operable

matatk4: Are the proposed Unicode allocations publicly available?

Russell: They are publicly available.

matatk4: Then we can use those in the private use area
… and it is prudent to use PUA as, at some point, the code points would be standardized and codified

Minutes manually created (not a transcript), formatted by scribe.perl version 248 (Mon Oct 27 20:04:16 2025 UTC).

Diagnostics

Maybe present: Janina, matatk4

All speakers: Janina, Lionel_Wolberger, matatk4, Russell

Active on IRC: Abhinav, Lionel_Wolberger, matatk4, Russell