WAI Adapt Task Force Minutes

Minutes | Topics | Resolutions

Resolutions reflect general consensus of participants present in a meeting. They are not formal decisions of the group. Refer to the Decisions page for formal decisions. Context for each resolution is available via its link into the minutes.

• 9 May 2022: 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 2022: 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"
• 2 May 2022: 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 2022: Logistics: Easter/Passover/Ramadan holiday season - We will meet next week as usual, for those members not attending, have a good vacation.
• 10 January 2022: A shortname for the modules. The numbering is confusing. - Group agrees to a title scheme "Personalization * Module" (with other changes to be discussed).
• 28 June 2021: Scheduling, meeting July 5th? - Personalization TF shall not meet on July 5th.
• 28 June 2021: 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
• 28 June 2021: 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 2021: 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"
• 19 April 2021: 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 2021: 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."
• 12 April 2021: 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 2021: i18n issues 144, 145, 175 - https://github.com/w3c/personalization-semantics/issues/ - We taking Easter Monday off.
• 1 March 2021: ednote https://lists.w3.org/Archives/Public/public-personalization-tf/2021Feb/0021.html - should change that to a hyperlink.
• 19 October 2020: review todo list for CR - publish new wd of requirments in TR space
• 14 September 2020: aprouch to what the wg - Request a reserved prefix from WHAT-WG to replace our use of data- in Module 1.
• 22 June 2020: Review introduction - Content Module - dump ed note in 3.4.1
• 27 April 2020: issues from coga - The Task Force believes we've already covered this use-case", close this issue
• 16 December 2019: 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. ... Overlay: Part of an application or content that is displayed over the top of the other content in a secondary window or popup, that blocks user interaction to the parent window. The content of the popup is not essential to the users task and are not intentionally initiated by the user.
• 5 August 2019: closing item values for the first 3 attributes - changing comment destination to feedback and change help from feedback to status
• 5 August 2019: closing item values for the first 3 attributes - changing comment destination to feedback and change help from feedback to status
• 5 August 2019: 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
• 10 June 2019: Missing items on autocomplete (see Charles email) - include the autocomplete that is missing
• 15 April 2019: review survey https://www.w3.org/2002/09/wbs/101569/Data-Dash2019/results - do not include alt in the attribute name
• 15 April 2019: review survey https://www.w3.org/2002/09/wbs/101569/Data-Dash2019/results - data-purpose, data-action, data-destination
• 15 April 2019: review survey https://www.w3.org/2002/09/wbs/101569/Data-Dash2019/results - do not include alt in the attribute name
• 15 April 2019: review survey https://www.w3.org/2002/09/wbs/101569/Data-Dash2019/results - data-purpose, data-action, data-destination
• 10 December 2018: to two implentiosn support - Janina is not sure about this, but look at this after our charter obligations have been met
• 27 August 2018: 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 2018: tools module (If ready) - will separate out the two tables (apologies to Becky) to types of help, accessibility support. Lisa will add an Editor's Note that we are not fully resolved here - this may still be re-merged together or merged with something else

Minutes