14:55:11 <RRSAgent> RRSAgent has joined #personalization
14:55:11 <RRSAgent> logging to https://www.w3.org/2021/03/01-personalization-irc
14:56:03 <lisask> agenda+ ednote https://lists.w3.org/Archives/Public/public-personalization-tf/2021Feb/0021.html
14:58:19 <lisask> agenda+ actions from wiki/action   https://github.com/w3c/personalization-semantics/wiki/action
15:00:39 <Lionel_Wolberger> Lionel_Wolberger has joined #personalization
15:01:32 <becky> becky has joined #personalization
15:02:03 <lisask> regrets, sharon and John
15:02:07 <janina> janina has joined #personalization
15:02:10 <Matthew_Atkinson> Matthew_Atkinson has joined #personalization
15:02:16 <janina> present+
15:02:22 <Matthew_Atkinson> present+
15:02:23 <becky> can someone send me the link to the zoom meeting?
15:02:32 <lisask> present+
15:03:00 <lisask> scribe: roy
15:03:19 <CharlesL> CharlesL has joined #personalization
15:03:35 <janina> zakim, who's here?
15:03:35 <Zakim> Present: janina, Matthew_Atkinson, lisask
15:03:37 <CharlesL> rrsagent, make logs public
15:03:37 <Zakim> On IRC I see CharlesL, Matthew_Atkinson, janina, becky, Lionel_Wolberger, RRSAgent, Zakim, lisask, Roy, MichaelC, stevelee, hadleybeeman
15:03:48 <Roy> agenda?
15:03:50 <CharlesL> present+
15:04:04 <Roy> present+
15:04:32 <CharlesL> rrsagent, draft minutes
15:04:32 <RRSAgent> I have made the request to generate https://www.w3.org/2021/03/01-personalization-minutes.html CharlesL
15:05:15 <Roy> Lisa: talk about live transcript function
15:05:28 <Roy> ... start with introduction
15:05:39 <CharlesL> Meeting: Personalization Task Force Weekly Meeting
15:06:07 <CharlesL> chair: lisask
15:06:13 <Roy> [introduction]
15:06:59 <CharlesL> regrets: Sharon, John
15:12:18 <Roy> Welcome!
15:13:20 <Roy> Janina: brief announcement for APA
15:14:20 <Roy> ... next week on the 10th will have a show and tell of @@
15:14:57 <Roy> s/@@/media queries
15:15:29 <lisask> q?
15:16:00 <lisask> Description:
15:16:16 <lisask> lisask has joined #personalization
15:16:21 <Roy> 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
15:16:21 <Roy>  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.
15:17:00 <lisask> q?
15:17:55 <Roy> zakim, next item
15:17:55 <Zakim> agendum 1 -- ednote https://lists.w3.org/Archives/Public/public-personalization-tf/2021Feb/0021.html -- taken up [from lisask]
15:18:05 <CharlesL> Pasted from Zoom Chat: Description:
15:18:05 <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
15:18:05 <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.
15:18:06 <CharlesL> 
15:18:06 <CharlesL> In a nutshell, his findings are:
15:18:06 <CharlesL> 
15:18:07 <CharlesL> -          Two of the new media features in MQ-L5 are already supported by browser manufacturers.
15:18:07 <CharlesL> 
15:18:07 <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
15:18:24 <lisask> https://lists.w3.org/Archives/Public/public-personalization-tf/2021Feb/0021.html
15:18:45 <lisask> are we ok with text ?
15:18:53 <Roy> 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
15:19:23 <Roy> [
15:19:25 <Roy> > Personalization semantics defines a set of properties and values to
15:19:29 <Roy> > annotate content. The Personalization Task Force is using  the data-* for
15:19:29 <Roy> > attributes for early implementations and prototypes.   Implementers should
15:19:29 <Roy> > be aware that we intend to replace  "data-"  with a reserved prefix when it
15:19:29 <Roy> > is determined.
15:19:29 <Roy> > See our discussion Prototypes with "data-"
15:19:30 <Roy> > <https://github.com/w3c/personalization-semantics/wiki/Prototypes-with-data-dash-*-(Take-2)>
15:19:30 <Roy> > .
15:19:34 <Roy> ]
15:20:19 <Lionel_Wolberger> Proposed to add the HTML spec reference
15:20:20 <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.
15:21:22 <Matthew_Atkinson> q
15:21:57 <lisask> (it is q+)
15:22:13 <Roy> Matthew: couldn't find the section 3.6.2.2
15:24:08 <Matthew_Atkinson> https://html.spec.whatwg.org/multipage/dom.html#embedding-custom-non-visible-data-with-the-data-*-attributes
15:24:38 <CharlesL> Looks like it is 3.2.5.7 HTML5.2 vs. 3.6.2.2 WHAT-WG
15:25:02 <Lionel_Wolberger> WHATWG link, Change "3.6.2.2" to "3.2.6.6"
15:25:19 <CharlesL> q+
15:25:26 <becky> https://www.w3.org/TR/2021/SPSD-html52-20210128/dom.html#embedding-custom-non-visible-data-with-the-data-attributes
15:25:28 <Roy> [trying to find the right link from HTML]
15:25:30 <Lionel_Wolberger> W3C link, Change "3.6.2.2" to "3.2.5.7"
15:26:30 <Roy> Charles: not sure about if we still ok about the title description of "non visible"
15:26:45 <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
15:27:28 <lisask> +1 from janina
15:27:29 <Roy> 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.
15:27:30 <lisask> +1
15:27:33 <CharlesL> +1
15:27:34 <becky> +1
15:27:36 <Lionel_Wolberger> +1
15:28:12 <Roy> Resolution:  should change that to a hyperlink.
15:28:20 <lisask> zakim, next item
15:28:20 <Zakim> I see a speaker queue remaining and respectfully decline to close this agendum, lisask
15:28:22 <Matthew_Atkinson> +1
15:28:25 <lisask> q?
15:28:29 <lisask> ack c
15:28:42 <Roy> Charles: who will do this?
15:28:49 <Roy> Roy: I would like to
15:29:14 <lisask> zakim, next item
15:29:14 <Zakim> agendum 2 -- actions from wiki/action   https://github.com/w3c/personalization-semantics/wiki/action -- taken up [from lisask]
15:29:14 <Lionel_Wolberger> The editor's note, as accepted
15:29:15 <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]
15:29:44 <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 ]
15:29:55 <Roy> Lisa: we could wait for another week to resolve 3 issues of John's
15:30:27 <Roy> 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.
15:30:30 <becky> https://github.com/w3c/personalization-semantics/wiki/actions
15:31:57 <Roy> Roy: will check all links before publication
15:32:18 <lisask> https://w3c.github.io/personalization-semantics/content/
15:32:41 <lisask> EDITOR'S NOTE
15:32:41 <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.
15:32:52 <Roy> Lisa: we should go through ED note to see if anything still need be change
15:33:09 <lisask> topic: going though ed notes (including glossary
15:34:08 <Roy> Lisa: glossary are in another document(coga)
15:34:20 <Roy> ... I think we should copy them in.
15:34:43 <Roy> Janina: I think we could add that as reference
15:34:57 <Roy> ... we only need change in one place
15:35:37 <lisask> replace the content inside sect 2 with a include of the coga gloassar
15:36:09 <Matthew_Atkinson> I think the glossary is: https://www.w3.org/TR/coga-usable/#glossary
15:37:04 <Roy> Janina: But the only problem, the one problem maybe if they have more terms than we need.
15:37:09 <lisask> +1
15:37:14 <janina> +1
15:37:16 <Lionel_Wolberger> +1
15:37:17 <Matthew_Atkinson> +1
15:37:20 <lisask> any objecttions
15:37:26 <becky> +1 to including a reference
15:37:30 <Roy> Lisa: it's not a huge plus really can glossary that's acceptable
15:37:40 <Roy> OK
15:38:27 <Roy> Lisa: include the whole section to goes, including the editors notes and terms.
15:38:45 <lisask> EDITOR'S NOTE
15:38:45 <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.
15:39:43 <lisask> this one can go
15:39:48 <lisask> any objection
15:39:58 <lisask> q?
15:40:24 <Roy> 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
15:41:00 <Roy> Lisa: it should go to the Top
15:41:11 <Roy> Janina: agree with that
15:41:53 <Roy> Lisa: suggest on bottom of 1.2
15:42:04 <lisask> q?
15:43:19 <Roy> Becky: we mention it in Explainer,  I guess that's where we would expand
15:43:28 <Roy> ... suggest to put on 1.3
15:43:38 <lisask> 1.3 to put editors note, add a sentece asking for implemtion, let us know ?
15:44:00 <lisask> (part of the anoucment)
15:44:08 <Roy> Janina: that's part of announcement
15:44:16 <lisask> new ed note fgoes in 1.3
15:47:33 <becky> https://w3c.github.io/personalization-semantics/content/#personalization-semantics-content-module
15:49:36 <Matthew_Atkinson> q+
15:50:19 <Roy> Charles: that should some issue of W3C repel.js
15:50:36 <lisask> ack m
15:50:40 <Roy> s/repel.js/respec.js
15:51:11 <Roy> 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.
15:52:24 <lisask> NOTE
15:52:24 <lisask> We may remove this or harmonize with other date time standards.
15:52:55 <Roy> 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.
15:54:03 <lisask> any object to remove it?
15:54:11 <Roy> Becky: i18n has comments on something need be harmonized
15:54:17 <lisask> pending johns action
15:54:22 <Roy> Lisa: John's action
15:54:29 <lisask> no object to removing
15:54:59 <Roy> Lisa: Bilss one, I think we could leave that
15:55:06 <becky> https://w3c.github.io/personalization-semantics/content/#symbol-explanation
15:55:29 <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
15:55:36 <lisask> tay in
15:55:40 <lisask> any objections
15:55:55 <lisask> (janina agrees - should it be text?
15:55:58 <Roy> Lisa: I think that's does what it needs to do and should stay in
15:56:19 <Roy> 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.
15:56:47 <Roy> Becky: I think you're right I don't know that it has to be an editor's note.
15:56:48 <lisask> resolution, move to text as stong text
15:57:12 <lisask> (or note is strong
15:57:15 <lisask> +1
15:57:20 <lisask> any objections
15:58:16 <lisask> [RDFa 1.1 Primer]
15:58:16 <lisask> Reference not found.
15:58:17 <lisask> [SKOS Core Guide]
15:58:18 <lisask> Reference not found.
15:58:19 <Roy> Lisa: RDF1.1 not found
15:58:39 <Roy> RRSAgent, make minutes
15:58:39 <RRSAgent> I have made the request to generate https://www.w3.org/2021/03/01-personalization-minutes.html Roy
15:59:11 <CharlesL> https://respec.org/docs/#note
16:01:00 <lisask>   RRSAgent, make minutes
16:01:00 <RRSAgent> I have made the request to generate https://www.w3.org/2021/03/01-personalization-minutes.html lisask
16:09:57 <CharlesL> CharlesL has left #personalization
18:06:03 <LisaSeemanKest_> LisaSeemanKest_ has joined #personalization
19:36:16 <stevelee> stevelee has joined #personalization