Meeting minutes
<Lionel_Wolberger> regrets Mike B\
CfC for Content Module 1.0 CR Status
Roy: We have the APA decision to go CR, and I've started the process
<Roy> https://
Roy: Tried to get transition in time for ADA anniversary tomorrow, but we are blocked
Roy: Three requests to resolve
<Roy> https://
<Roy> https://
Roy: Director not convinced we've accomplished TAG's requests
Roy: Also overlaps with MQ5 in TAG not clear is resolved
Roy: third issue to list BCI as normative; should be easy to do
Roy: Note currently in PDF but we're planning to move to W3C Registry
Lionel_Wolberger: Looking to review with headings
<Roy> https://
Exit Criteria
<Lionel_Wolberger> URL, https://
Roy: Above is an example from ARIA that we need to have an analog for in our document
Lionel_Wolberger: Happy to help draft
Matthew_Atkinson: Happy to help
Lionel_Wolberger: Example looks good and helpful
TAG Response Resolution
Sharon: Notes TAG closed
Roy: Believed it's because we weren't responding
Roy: Also don't understand
<Roy> Rossen Atanassov
Roy: Suggesting opening request with TAG to review current CR transition draft
[discussion on documenting our response to TAG comments]
<becky> https://
<Sharon> TR Explainer https://
[group digging through various archives]
becky: Appears meeting with TAG was around (or during) TPAC 2021
Sharon: I'll do the forensic research to see what we need yet to do, and what we have to document what's done
<Roy> https://
Documenting BCI reliance is normative
Roy: For now we normatively reference the PDF
Roy: We will add a note pointing out we will replace this with a W3C Registy specification
<Lionel_Wolberger> PDF file's recent name, BCI-AV_2020-03-09_(en+sv+no+fi)+derivations+symbols_8483-27158
<Lionel_Wolberger> Excel format, BCI-AV_2020-03-09_(en+sv+no+fi+hu+de+nl+af+ru+lv+po+fr+es+pt+it+dk)+derivations_8483-27158.xls
lionel: Believe there's an Excel
Janina: We should chase down Excel, and maybe request CSV for now
<Lionel_Wolberger> On the Bliss site, https://
<Lionel_Wolberger> TEXT OF THE LINK: Excel spreadsheet with ID's, glosses, and derivations and without symbols (more manageable)
CharlesL1: Confirms is a downloadable doc
<Lionel_Wolberger> Column AI has the BCI-AV#, and column B has the English label for the symbol
<Lionel_Wolberger> s\AI\A
janina: Suggests comma delimited would be best if they could give it us;
Lionel_Wolberger: Notes the symbols themselves are not in Excel
[several people noting a11y problems with PDF]
Lionel_Wolberger: notes PDF includes a rendering of the symbol, but the Excel does not
Sharon: Notes we don't use the rendering
Lionel_Wolberger: That's correct
Lionel_Wolberger: Agrees the whole point of the spec is that users are facilitated to use their preferred symbols; so the PDF symbols are illustrative but not dispositive
Lionel_Wolberger: We don't rely on that; only on the ID and the concept
Matthew_Atkinson: Suggests we may consider being able to select among symbol sets when we write our registry spec so that people can see what this is about
Matthew_Atkinson: And it could be just part of the table because we're only illustrating
<Lionel_Wolberger> http://
implementation report
Roy: have a draft in our repo
Roy: please check!
roy: We need a report template in order to enter CR; completed it will document our transition to PR