W3C

– DRAFT –
Weekly Teleconference 17-Sep-2024

17 September 2024

Attendees

Present
Abhinav, Annalu, Lionel_Wolberger, matatk
Regrets
Janina
Chair
-
Scribe
matatk, Lionel_Wolberger

Meeting minutes

Introductions. Updates.

TPAC planning

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

<Lionel_Wolberger> matatk: Adapt is meeting Thursday

matatk: The Adapt meeting will occur at a time not conducive to India timezone
… and Lionel will have left TPAC by then

https://w3c.github.io/adapt/presentations/ac2024/ (we could use the top and tail of this to explain what we're trying to do, and how it may look form the user's perspective)

matatk: I suggest I show the AC presentation first, as it is short and very illustrative of the problem statement

Lionel_Wolberger: _1
… +1
… and we will have time Monday to preview the presentation

matatk: Re symbols, we talked previously about showing a demo with the tool, but with appropriate/more representative content in it.

Well Known Destinations

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

matatk: The "how" standards will need slight tweaks to support Adapt's concept of Well Known Destinations
… looking at Linksets, the linkset document is almost like a sitemap, but has links
… its advantage, it is a thing that you can fetch once
… we could place the LInkset at a WKD for the domain, and then we would get the ability to query it directly without having to overtly reference it on every page
… this could work if there are multiple sites on a FQDN

Abhinav: A WKD to fetch all the links in the linkset?

matatk: To deal with sub-sites, there could be one giant linkset that includes all the sub-site linksets
… is it an HTTP header that point to it?

matatk: So there are bandwidth concerns, and options for site hosting.

matatk: There will be expertise to help us with the trade-offs.

Abhinav: The challenge with well-known is that it's sitie-wide.

Abhinav: Concern about getting the response for the entire site.

matatk: Can think of a couple of suggestions - site-wide linkset, or sub-site one - bringing furrther questions re discovery.

Abhinav: Think we can mention these as optional extensions we're considering (in the explainer).

matatk: Wanted to check that I understood, the extension we are after is to have * represent wildcard in the 'base' link, to which the others in the set relate. Allows us to do sub-sites.

Abhinav: That matches my expectations.

matatk: Is this sufficient to present, when filled in?

Abhinav: Yes

Issue 240

Explainer link: https://github.com/w3c/adapt/blob/add-explainers/explainers/symbols.md

Prototype/demo tool (doesn't yet have the right content in it): https://matatk.agrip.org.uk/adaptable-content-authoring-tool/editor/

Annalu: Symbols can be used to give the reader the key concepts
… almost like summarization, putting symbols only on the key words

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

Diagnostics

All speakers: Abhinav, Annalu, Lionel_Wolberger, matatk

Active on IRC: Abhinav, Lionel_Wolberger, matatk