<LisaSeemanKest> updates

<LisaSeemanKest> https://www.w3.org/2020/10/26-personalization-minutes.html missing

<LisaSeemanKest> scribe: janina

actions review https://github.com/w3c/personalization-semantics/wiki/actions

ls: Some updates beginning with wd publication--thanks Roy!
... Requirements WD

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/actions

ls: asks whether we respnd to TAG now or wait for content module to be changed

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/actions

<Roy_> https://lists.w3.org/Archives/Public/public-personalization-tf/2020Oct/0015.html

cl: Link to 476 is broken
... actions todo ...

js: Roy posted Becky's draft of response to TAG

<Roy_> https://lists.w3.org/Archives/Public/public-personalization-tf/2020Oct/0015.html

[group looking at the draft]

ls: Link to TAG explainer?

js: yes

ls: Should we note that it's often the site the user is on that's pushing distractions?

[general greement to do so carefully]

<LisaSeemanKest> post 476 responce?

<LisaSeemanKest> this addresses many of the user needs in coga's "content useable" and then a list

js: Suggest Content Usable as: "This module addresses a number of needs exposed by COGA's Content Usable such as:" -- create a list with pointers

ss: have we addressed distraction=sensory question as being supported by MQ5 prefers reduced motion

<CharlesL> From our sortable table : definition of distraction: Non-essential distracting content that includes movement, sound or other forms of sensory feedback. This includes: moving images (videos, animated GIFs,etc.); content that starts automatically or is automatically updating; and elements that change locations or generate audio feedback on the user's system without user interaction.

js: Lisa notes ARIA-Live covers a ticking clock for screen readers, but not for COGA where the constant changing distracts
... Also, the ticking clock is not appropriate for MQ5

cl: looking at explainer, suggests some of this additional explanation to sec 1.2.1
... and microformats would go under 4.2 in the explainer ...

ls: lisa will update Becky's response to TAG wiuth above pointes

<LisaSeemanKest> after we OK the tag response update on the list, can we send to the TAG

<LisaSeemanKest> the responce

<LisaSeemanKest> +1

<LisaSeemanKest> send to michael for sanity check

<CharlesL> +1 (including Michaels Blessing ;)

<Roy> +1

ls: Asks whether we have response on BCI referencing

rr: On scheduled conversation this week

<LisaSeemanKest> https://lists.w3.org/Archives/Public/public-personalization-tf/2020Nov/0000.html

<LisaSeemanKest> One of the main challenges that has not been addressed on the web is transforming content

<LisaSeemanKest> for these varying needs.

[discussion of simplifying language in explainer]

ls: Will make above edits to the explainer in a branch and forward to js for checking

<Roy> https://www.w3.org/2020/10/TPAC/breakout-schedule.html#adaptation

<CharlesL> Meeting: Personalization Task Force Weekly Meeting

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/tatg/TAG/
Present: janina CharlesL Lisa Sharon Roy
Regrets: Becky
Found Scribe: janina
Inferring ScribeNick: janina
Found Date: 02 Nov 2020
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)