W3C

– DRAFT –
WAI-Adapt Teleconference

09 Jul 2024

Attendees

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

Meeting minutes

Introduction, Any Updates?

Lionel_Wolberger: Reviews NFB participation; Very interested in what we're doing, esp WKD

Scheduling, Summer is here

Lionel_Wolberger: Regrets next week from Matthew

Lionel_Wolberger: Will be on holliday on the 23rd

janina: Suggest let's return to this at meetings end

TPAC Planning

<matatk> https://www.w3.org/2024/09/TPAC/schedule.html

<matatk> Note: the APA Monday morning meeting is likely to move to a different day to be combined with a different meeting.

janina: The TPAC is California time, but we can bring people in via remote

Russell: I may be interested in attending.

janina: You are an invited expert, there is no charge

janina: Glad to hear you will participate! The fact that corporations are interested in WKD is persuasive

Recruitment

janina: Suggest we recruit at TPAC and in the fall, as we want to recruit when we have a very regular schedule and clear documents to be read

Russell: I spoke with someone who is interested.

Handout for TPAC

Lionel_Wolberger: Lionel to bring more of the symbols one-pager
… consider a one-pager that can express the use case for WKDs

Symbols explainer

Generalizing Symbols

<Zakim> matatk, you wanted to ask about patches, and the EPUB approah

Lionel_Wolberger: We agreed last week to stick to our scope of AAC-type symbols, as they are used in procedures or topic lists
… and perhaps once passed, the idea of translatable/transformable symbols might spread

janina: and people could register themselves

Prioritization

matatk: Would we want to consider prioritization? For example, if a person wants an AAC symbol and an emoji, they could express which has priority
… some sets of symbols are more comprehensive than others
… there is a tricky balance between (a) communication remains dynamic and ever evolving (b) communication relies on shared, hence static understandings

janina: Proposing priotizing our next step: update the documents prior to TPAC
… (a) make a list of the docs 1. AAC spec 2.Registry spec 3.Explainer 4.Home page
… (b) commit to updating them prior TPAC, and log this in the Issue 240

janina: (1) AAC spec is in CR since Vancouver '22
… (2) Registry is in FPWD since 2022 and needs updating in light of Issue 240 discussion
… (3) Explainer need updating in light of Issue 240 discussion.

Lionel_Wolberger: Explainer may benefit from an 'out of scope' section.

janina: I agree to work with Russel on the documents
… we will skip 16th and 23rd July due to regrets, vacations. Next meeting 30 July

WKD Github actions and PRs

Lionel_Wolberger: Take up the issue of multiple services on a single URL

matatk: Security considerations may differ depending which part of the URL tree you are focusing on
… we should review the linksets, Phil Archer suggests we look at RFC 9264, Linksets https://www.rfc-editor.org/rfc/rfc9264.html

<matatk> https://www.w3.org/2024/09/TPAC/schedule.html

<matatk> oops

<matatk> https://lists.w3.org/Archives/Public/public-adapt/2024May/0015.html

Lionel_Wolberger: Abhinav agrees to look at the GS1 linksets and bring to our next meeting a gap analysis or comparison

janina: It's a kind of due dilligence

Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).

Diagnostics

No scribenick or scribe found. Guessed: Lionel_Wolberger

All speakers: janina, Lionel_Wolberger, matatk, Russell

Active on IRC: janina, Lionel_Wolberger, matatk, Russell