WAI-Adapt Task Force Meeting Resolutions
Minutes | Topics | Resolutions
2025
-
15 April: WAI-Adapt Teleconference
- Invitations to the Face to Face - We'll use the list more!
- 11 February: WAI-Adapt Weekly Teleconference
2024
-
12 November: WAI-Adapt Teleconference
- Introduction, logistics, updates as needed - Adapt will tentatively meet either 28-30 April or 4-6 May
-
21 May: WAI-Adapt Teleconference
- Logistics - Next Adapt call will be the 4th of June
- Issue 240 - matatk to respond on issue 240 as discussed
-
2 April: Weekly teleconference
- Meeting minutes - No telecon next Tuesday 9 April
-
16 January: Adapt Task Force Weekly Teleconference
- Introduction, Any Updates? - TF will not meet in teleconference 24 January
- URL Project Vocabulary: Well Known Destination? - We'll use "Well Known Destinations" provisionally as our class category
2023
- 12 December: Adapt Weekly Teleconference
-
13 November: APA WAI-Adapt Task Force Meeting 13 November 2023
- New Meeting Time - Task Force weekly teleconference will move to Tuesday 10AM Boston as of next week Nov 21sat
- Thanksgiving week meeting yes or no? - Adapt TF shall meet next week on 21-November
-
13 February: APA Adapt Task Force Teleconference
- Symbol Module Implementations - The Adapt TF will take on the development of the AAC Registry.
2022
- 19 December: WAI Adapt Task Force Teleconference
- 5 December: Monday 5 Dec 2022 Adapt Task Force Teleconference
- 28 November: WAI Adapt Task Force Teleconference
-
3 October: WAI Adapt Task Force Weekly Meeting Oct 3 2022
- CR updates for new spec focused only on symbols - We will keep the current name of WAI-ADAPT Content Module while we do the first round of edits
-
26 September: WAI Adapt Task Force Teleconference
- CR Next steps - WAI-Adapt will revise its Content Module draft to focus exclusively on AAC Symbols, as these were seen by TAG as most ready for standardization.
- CR Next steps - Moving AAC symbols to CR first also implies we will write a TAG Explainer and a public Explainer expressly for AAC symbols.
- CR Next steps - Move expeditiously to formally request "adapt-" as a reserved prefix from WHAT-WG.
-
11 July: WAI Adapt Task Force Teleconference
- Last items before we request APA to move Module 1 to CR status. Spec content ready? - The WAI-Adapt Task Force requests that APA conduct a Call for Consensus to transition WAI-Adapt Content Module 1.0 (https://w3c.github.io/adapt/content/) to Candidate Recommendation.
- Last items before we request APA to move Module 1 to CR status. Spec content ready? - The WAI-Adapt Task Force requests updated Working Draft publication of the WAI-Adapt Explainer (https://w3c.github.io/adapt/) as a W3C Group Draft Note.
-
27 June: WAI Adapt Task Force Teleconference
- Meeting minutes - The group will not meet next week Monday July 4th. Happy holiday to everyone celebrating!
- 3.6 edit (see git link) (Janina) - We agree to merge the PR 209 affecting the text of 3.6
- 23 May: WAI Adapt Task Force Teleconference
-
9 May: WAI-Adapt
- Roy follow-up, the task of renaming specification docs from Personalization to Adapt, (and adding the caption) - The short name shall be adapt-content
-
2 May: Personalization Task Force Teleconference
- Caption line on WAI-Adapt draft overview https://deploy-preview-8--wai-personalization-standards.netlify.app/personalization/ - The subtitle (the 'tag line') is "Enabling users to personalize content presentation"
- Implications of issue 203 for the data-symbol attribute - https://github.com/w3c/personalization-semantics/issues/203 - Change the cup of tea sample--currently with three symbols in one attribute, to be a cup of tea sample with one symbol in each attribute.
-
11 April: Personalization Task Force Teleconference
- Logistics: Easter/Passover/Ramadan holiday season - We will meet next week as usual, for those members not attending, have a good vacation.
-
10 January: Personalization Task Force Teleconference
- A shortname for the modules. The numbering is confusing. - Group agrees to a title scheme "Personalization * Module" (with other changes to be discussed).
2021
-
28 June: Personalization Task Force Teleconference
- Scheduling, meeting July 5th? - Personalization TF shall not meet on July 5th.
- Editor's note (wiki page): Write the note that points to this page - To delete the current note that appears in 3.1.1 and 3.2.1
- Editor's note (wiki page): Write the note that points to this page - Include the new note language three times, above each relevant attribute. The language is, "The attributes in this section, "action", "destination" and "purpose", had some alternatives discussed. You can find a detailed overview here, [URL].
-
21 June: Personalization Task Force Teleconference
- Editor's note (wiki page) on action-destination-purpose (following Matthew's edit) and name of the wiki page - Document name will be "Review of approaches for Action, Destination, and Purpose"
-
10 May: Personalization Task Force Teleconference
- Meeting minutes - remove true/false from the explainer
-
19 April: Personalization Task Force Teleconference
- Becki drafted a response to i18n issue #144 (no response back) https://github.com/w3c/personalization-semantics/issues/144 - ok to close #144
-
12 April: (MEETING TITLE)
- wording for note for internationalization . see thread at https://lists.w3.org/Archives/Public/public-personalization-tf/2021Apr/0008.html - add a note to our spec - "Note: the use of the language token does not mandate the use of BCP47 values: authors can request that or a simple text string."
- wording for note for internationalization . see thread at https://lists.w3.org/Archives/Public/public-personalization-tf/2021Apr/0008.html - add a note to both the Action and Destination sections - "Note: Some of these token values can apply to both an Action and a Destination. Content authors should choose the appropriate component in context."
-
29 March: Personalization Task Force
- i18n issues 144, 145, 175 - https://github.com/w3c/personalization-semantics/issues/ - We taking Easter Monday off.
-
1 March: Personalization Task Force Weekly Meeting
- ednote https://lists.w3.org/Archives/Public/public-personalization-tf/2021Feb/0021.html - should change that to a hyperlink.
2020
- 7 December: Personalization Task Force Teleconference
-
19 October: Personalization Task Force Teleconference
- review todo list for CR - publish new wd of requirments in TR space
-
14 September: Personalization Task Force Teleconference
- aprouch to what the wg - Request a reserved prefix from WHAT-WG to replace our use of data- in Module 1.
-
22 June: Personalization Task Force Teleconference
- Review introduction - Content Module - dump ed note in 3.4.1
- 27 April: Personalization Task Force Teleconference
2019
-
16 December: Personalization Task Force Teleconference
- explainer https://lists.w3.org/Archives/Public/public-personalization-tf/2019Dec/0012.html - Offer: An advertisement or offer for a product, feature or service, or content that is not essential to the user's current task.
-
26 August: Personalization Task Force Teleconference
- BLISS for licensing but we need to follow up to have a URI that Russell gave us on granting us fair use of the BIC reference numbers. Add that to our spec, as well as the public email he sent us.
- , we should suggest some language for this page, where it says you can use your symbols that you include the BIC numbering as well.
-
5 August: Personalization Task Force Teleconference
- closing item values for the first 3 attributes - changing comment destination to feedback and change help from feedback to status
- closing item values for the first 3 attributes - changing comment destination to feedback and change help from feedback to status
- closing item values for the first 3 attributes - make the action definition for help more specific - opens-in-page-help; difference is that it doesn’t take the user to a new destination. and the destitation is chaged to support with defintion that it goes to support or instructions
- 17 June: Personalization Task Force Teleconference
-
10 June: Personalization Task Force Teleconference
- Missing items on autocomplete (see Charles email) - include the autocomplete that is missing
- 3 June: Personalization Task Force Teleconference
-
15 April: Personalization Task Force Teleconference
- review survey https://www.w3.org/2002/09/wbs/101569/Data-Dash2019/results - do not include alt in the attribute name
- review survey https://www.w3.org/2002/09/wbs/101569/Data-Dash2019/results - data-purpose, data-action, data-destination
- review survey https://www.w3.org/2002/09/wbs/101569/Data-Dash2019/results - do not include alt in the attribute name
- review survey https://www.w3.org/2002/09/wbs/101569/Data-Dash2019/results - data-purpose, data-action, data-destination
2018
-
10 December: SV_MEETING_TITLE
- to two implentiosn support - Janina is not sure about this, but look at this after our charter obligations have been met
-
27 August: Personalization Task Force Weekly Meeting
- https://github.com/w3c/personalization-semantics/wiki/Comparison-of-ways-to-use-vocabulary-in-content - the api discuion is not needed to work out how put vocablary in content
- 11 June: SV_MEETING_TITLE
- 12 March: SV_MEETING_TITLE