Last items before we request APA to move Module 1 to CR status. Spec content ready?
Lionel_Wolberger: focus on going to CR. resolution to ask APA CFC to move Module 1 to CR status. anything blocking that?
janina: don't believe so. pull requests: issue 213 deemed editorial. 212 grammatical.these have been merged
Roy: fix all of the links in the document. references updated before CR. will fix tomorrow
janina: you have a full week to do that. CFC will run for a week
janina: will need a link for CFC, but wait until resolution in this TF
Roy: will create implementation page on WAI website. will someone help to summarize all implementations we have? I can list them on the page
janina: series of things to do. don't need answers today. do have answers for all of them. need to gather data to present. have at least a week.
Lionel_Wolberger: link to which page, Janina?
janina: after we vote the resolution, not before. after we ask APA to do it this is next steps
Lionel_Wolberger: let's do the resolution today
janina: suggest we're ready to do resolution then discuss other items
<janina> DRAFT RESOLUTION: The WAI-Adapt Task Force requests that APA conduct a
<janina> Call for Consensus to transition WAI-Adapt Content Module 1.0
<Lionel_Wolberger> DRAFT RESOLUTION: The WAI-Adapt Task Force requests that APA conduct a Call for Consensus to transition WAI-Adapt Content Module 1.0
<Lionel_Wolberger> DRAFT RESOLUTION: The WAI-Adapt Task Force requests that APA conduct a Call for Consensus to transition WAI-Adapt Content Module 1.0 (https://
RESOLUTION: The WAI-Adapt Task Force requests that APA conduct a Call for Consensus to transition WAI-Adapt Content Module 1.0 (https://
janina: Roy will correct links that point to personalization. these things are grammatical and editorial. those changes can be made at any time. the CFC needs to contain a snapshot of what we voted on. what we vote on itself does not change.
<Lionel_Wolberger> DRAFT RESOLUTION: The WAI-Adapt Task Force requests updated Working Draft publication of an updated W3C Working Draft Note of the WAI-Adapt Explainer (https://
<Roy> W3C Group Draft Note
<Lionel_Wolberger> DRAFT RESOLUTION: The WAI-Adapt Task Force requests updated Working Draft publication of the WAI-Adapt Explainer (https://
RESOLUTION: The WAI-Adapt Task Force requests updated Working Draft publication of the WAI-Adapt Explainer (https://
3.6 edit (see git link) (Janina)
Lionel_Wolberger: believe you've resolved it?
janina: not quite. need to support transition to CR. there's a hyperlink in there we should all look at. demonstrates that this is ready for CR. APA alone cannot solely approve. requires approval from other W3C groups
janina: proposing a wiki. first point is to point to the criteria that we are satisfying. hopefully each that this spec meets will have its own idref so that approval can be simplified.
janina: looking for volunteers to find those
CharlesL: when you change doc name you change links. if we've sent those out the links will be invalid.
janina: Roy knows this is an action item on him
janina: we don't have separate docs for each requirement. can come up with a list to capture all of them.
Roy: can republish this document and classify the features into different modules
Roy: have a section that indicates features for module 1, etc. a simpler approach
<Lionel_Wolberger> Mapping requirements to the Content Module 1.0 is accomplished by this Group Draft Note, https://
janina: going back to list published above, these are steps to move to CR
janina: link I posted specified steps to satisfy in order to go to CR
janina: don't think we have any changes to dependencies (item 2 from list available at above link)
janina: will report on building and deployment of a registry
janina: how will we demonstrate that our implementations will actually work? make content for modules to point to. browser extensions/3rd party will make them work
<Lionel_Wolberger> * Lionel notes again for the record, we are following the bulleted list in 6.3.7. Transitioning to Candidate Recommendation, https://
janina: how we will exit CR and go to next level. we know we have to create content and support user agent implementations
janina: specify deadlines for comments. leave for Michael and Roy to figure out. any disclosures are 28 days, but may be 60. opportunity for people to disclose patents they might have and they won't prevent this spec
janina: wide review. want to point to Lisa for help with this. lots of wide review has been conducted
Lionel_Wolberger: presented at TPAC 2017, I think. also, TPAC 2021.
janina: Lisa would be worth consulting with on this
janina: history goes back many years
Lionel_Wolberger: demonstration and implementation pages. other examples of wide review. clearly quite extensive
<Lionel_Wolberger> Here are the "Wide Review" sentences we just curated
<Lionel_Wolberger> The history on WAI-Adapt goes back 15-20 years and is one of the most researched and inspected specifications in internet history.
CharlesL: I think we also presented in Lisbon as well as Lyons. I thought it was Lisbon we got the feedback at TAG about data dash.
<Lionel_Wolberger> Requirements originated in the first ARIA standard, the list was then refined in COGA, Presented at TPAC Leons (2017) Applications Working Group, at TPAC Lisbon to TAG, TPAC 2021
janina: in hand with not being able to use AUI
<Lionel_Wolberger> Also at CSUN 2022
janina: TAG has reviewed this. important point
<Lionel_Wolberger> demonstration implementations (some funded by the EU) by Ayeleth Seeman and Matthew Atkinson have been demonstrated multiple times.
<Lionel_Wolberger> The access-board.gov.il has agreed to doing a markup based on this content module.
<Roy> TAG: https://
janina: any features at risk? (last item on list). we do not have any. we have one that will require us to republish CR. as soon as it gets CR that's when I open git for permanent prefix