– DRAFT –
WAI-Adapt Teleconference

Introductions. Updates.

Symbols

matatk: Zmall bit to report ...

matatk: Edits to the new Explainer

<matatk> w3c/adapt#323

<gb> Pull Request 323 Symbols explainer post-workshop (by matatk)

janina: Is the question to have one explainer for symbols?

matatk: Yes

janina: Pros and cons?

matatk: Con: Convventionally it's 1:1, we get one explainer for each one spec
… though we are not actually a 'spec'
… so we risk some confusion in having two documents
… Pro: One is the registry (a source of reference) vs how the symbol is encoded

janina: Convention v confusion?

matatk: I am leaning towards having a symbols explainer

Lionel_Wolberger: Proposed new explainer link, https://github.com/w3c/adapt/blob/symbols-explainer-post-workshop/explainers/symbols.md

matatk: The group agrees, to combine into this explainer both the registry and the method
… this could be linked to our 'shop front' as well

janina: I can roost on these Adapt shop front tasks

Russel: Aiming for October for producing the font.

Well Known Destinations

<matatk> w3c/adapt#325

<gb> Pull Request 325 Start drafting the destinations document (by matatk)

Lionel_Wolberger: We reviewed the explainer draft at https://raw.githack.com/w3c/adapt/draft-destinations/destinations/index.html

matatk: I propose listing more requirements, as this is a successful pattern we see in RQTF

<matatk> https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request

__

Abhinav: I have time this week to suggest changes