– DRAFT –
Personalization Task Force Weekly Meeting

<lisask> regrets, sharon and John

<becky> can someone send me the link to the zoom meeting?

Lisa: talk about live transcript function
… start with introduction

[introduction]

Welcome!

Janina: brief announcement for APA
… next week on the 10th will have a show and tell of media queries

<lisask> Description:

Niklas Schildhauer, a student of mobile media at Stuttgart Media University, in his bachelor thesis has looked into the new “user preference media features”, as proposed for Media Queries Level 5. He examined how these and other candidates for media features, as proposed by the W3C APA working group, could be used to enable user interface personalisation on the web and how web users can benefit from this. He also developed a polyfill script that

makes these media features available for web authors using current web browsers. Furthermore, he designed example webpages that demonstrate how the proposed media features can be used to provide a personalized user experience.

ednote https://lists.w3.org/Archives/Public/public-personalization-tf/2021Feb/0021.html

<CharlesL> Pasted from Zoom Chat: Description:

<CharlesL> Niklas Schildhauer, a student of mobile media at Stuttgart Media University, in his bachelor thesis has looked into the new “user preference media features”, as proposed for Media Queries Level 5. He examined how these and other candidates for media features, as proposed by the W3C APA working group, could be used to enable user interface personalisation on the web and how web users can benefit from this. He also developed a

<CharlesL> polyfill script that makes these media features available for web authors using current web browsers. Furthermore, he designed example webpages that demonstrate how the proposed media features can be used to provide a personalized user experience.

<CharlesL> In a nutshell, his findings are:

<CharlesL> - Two of the new media features in MQ-L5 are already supported by browser manufacturers.

<CharlesL> - The media features prefers-reduced-motion, forced-colors, prefers-contrast and prefers-reduced-transparency were found to be important contributions to web accessibility. People with vestib

<lisask> https://lists.w3.org/Archives/Public/public-personalization-tf/2021Feb/0021.html

<lisask> are we ok with text ?

Lisa: I remembered last week that I had written an editor's note, but it hadn't come off the it hadn't gone into the document. I think I got the permission to main branch

[

> Personalization semantics defines a set of properties and values to

> annotate content. The Personalization Task Force is using the data-* for

> attributes for early implementations and prototypes. Implementers should

> be aware that we intend to replace "data-" with a reserved prefix when it

> is determined.

> See our discussion Prototypes with "data-"

> <https://github.com/w3c/personalization-semantics/wiki/Prototypes-with-data-dash-*-(Take-2)>

> .

]

<Lionel_Wolberger> Proposed to add the HTML spec reference

<Lionel_Wolberger> Personalization semantics defines a set of properties and values to annotate content. The Personalization Task Force is using the data-* (as required by the HTML 5 specification section 3.6.2.2) for attributes for early implementations and prototypes. Implementers should be aware that we intend to replace "data-" with a reserved prefix when it is determined.

<lisask> (it is q+)

Matthew: couldn't find the section 3.6.2.2

<Matthew_Atkinson> https://html.spec.whatwg.org/multipage/dom.html#embedding-custom-non-visible-data-with-the-data-*-attributes

<CharlesL> Looks like it is 3.2.5.7 HTML5.2 vs. 3.6.2.2 WHAT-WG

<Lionel_Wolberger> WHATWG link, Change "3.6.2.2" to "3.2.6.6"

<becky> https://www.w3.org/TR/2021/SPSD-html52-20210128/dom.html#embedding-custom-non-visible-data-with-the-data-attributes

[trying to find the right link from HTML]

<Lionel_Wolberger> W3C link, Change "3.6.2.2" to "3.2.5.7"

Charles: not sure about if we still ok about the title description of "non visible"

<Lionel_Wolberger> Lisa: it doesn't mean the user-agent cannot do something visual with the tag, it means that the meta data is not visible to the user

<lisask> +1 from janina

Janina: We have time to fix our reference if we need to, I good but the bottom line here is that we get a point or into the spec.

<lisask> +1

<CharlesL> +1

<becky> +1

<Lionel_Wolberger> +1

Resolution: should change that to a hyperlink.

<Matthew_Atkinson> +1

Charles: who will do this?

Roy: I would like to

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

<Lionel_Wolberger> The editor's note, as accepted

<Lionel_Wolberger> Personalization semantics defines a set of properties and values to annotate content. The Personalization Task Force is using the data-* (as required by the HTML 5 specification section 3.2.5.7*) for attributes for early implementations and prototypes. Implementers should be aware that we intend to replace "data-" with a reserved prefix when it is determined. [*LINK IS, https://www.w3.org/TR/2021/SPSD-html52-20210[CUT]

<Lionel_Wolberger> Link was truncated, here it is: [*LINK IS, https://www.w3.org/TR/2021/SPSD-html52-20210128/dom.html#embedding-custom-non-visible-data-with-the-data-attributes ]

Lisa: we could wait for another week to resolve 3 issues of John's

Lionel: John did say he's aware that he didn't finish his actions then he thought he could catch up on them today and complete.

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

Roy: will check all links before publication

<lisask> https://w3c.github.io/personalization-semantics/content/

<lisask> EDITOR'S NOTE

<lisask> We intend to incorporate additional terms from the glossary from the Cognitive and Learning Disabilities Accessibility Task Force, when it is ready. If there are non-editorial differences, we will use the term definitions above. See the COGA Glossary.

Lisa: we should go through ED note to see if anything still need be change

going though ed notes (including glossary

Lisa: glossary are in another document(coga)
… I think we should copy them in.

Janina: I think we could add that as reference
… we only need change in one place

<lisask> replace the content inside sect 2 with a include of the coga gloassar

<Matthew_Atkinson> I think the glossary is: https://www.w3.org/TR/coga-usable/#glossary

Janina: But the only problem, the one problem maybe if they have more terms than we need.

<lisask> +1

<janina> +1

<Lionel_Wolberger> +1

<Matthew_Atkinson> +1

<lisask> any objecttions

<becky> +1 to including a reference

Lisa: it's not a huge plus really can glossary that's acceptable

OK

Lisa: include the whole section to goes, including the editors notes and terms.

<lisask> EDITOR'S NOTE

<lisask> Since implementations have not yet been finalized, any examples in this document are illustrative only, and are provided to help in understanding the concept. All examples will be updated once implementation examples are finalized.

<lisask> this one can go

<lisask> any objection

Matthew: the editor's note about the data dash, which we've just agreed to add but it's not in there yet. Do you know where it will go

Lisa: it should go to the Top

Janina: agree with that

Lisa: suggest on bottom of 1.2

Becky: we mention it in Explainer, I guess that's where we would expand
… suggest to put on 1.3

<lisask> 1.3 to put editors note, add a sentece asking for implemtion, let us know ?

<lisask> (part of the anoucment)

Janina: that's part of announcement

<lisask> new ed note fgoes in 1.3

<becky> https://w3c.github.io/personalization-semantics/content/#personalization-semantics-content-module

Charles: that should some issue of W3C respec.js

Matthew: I would employ you at this meeting to ask for horizontal lines but definitely not a vertical ones because that can really make things harder to read.

<lisask> NOTE

<lisask> We may remove this or harmonize with other date time standards.

Lisa: the editors notes in that table, which is coming in its own date time things that we may remove this or harmonize with other date time standards.

<lisask> any object to remove it?

Becky: i18n has comments on something need be harmonized

<lisask> pending johns action

Lisa: John's action

<lisask> no object to removing

Lisa: Bilss one, I think we could leave that

<becky> https://w3c.github.io/personalization-semantics/content/#symbol-explanation

<lisask> Note that the reference numbers are the same references numbers used in Bliss (BCI numbers). Here is a link to the BCI numbers and additional language translations at the time of publication and the copyright licensing from Bliss. For additional updates after publication see our best practices for s

<lisask> tay in

<lisask> any objections

<lisask> (janina agrees - should it be text?

Lisa: I think that's does what it needs to do and should stay in

Janina: I think it's fairly crucial So, actually I'm wondering should, should it be in the text and not in an editor's note.

Becky: I think you're right I don't know that it has to be an editor's note.

<lisask> resolution, move to text as stong text

<lisask> (or note is strong

<lisask> +1

<lisask> any objections

<lisask> [RDFa 1.1 Primer]

<lisask> Reference not found.

<lisask> [SKOS Core Guide]

<lisask> Reference not found.

Lisa: RDF1.1 not found

<CharlesL> https://respec.org/docs/#note