- From: lisa.seeman <lisa.seeman@zoho.com>
- Date: Tue, 11 Feb 2020 10:06:44 +0200
- To: "Charles LaPierre" <charlesl@benetech.org>, "public-personalization-tf" <public-personalization-tf@w3.org>, "Janina Sajka" <janina@rednote.net>
- Message-Id: <17033476cd8.d6f37630138467.4879771919575333397@zoho.com>
Hello TAG! We are requesting a TAG review of Personalization Semantics https://www.w3.org/TR/personalization-semantics-1.0/ and Module 1 https://www.w3.org/TR/personalization-semantics-content-1.0/. It contains supporting syntax that provides the extra information, help, and context. We aim to make web content adaptable for users who function more effectively when content is presented to them in alternative modalities - including people with cognitive & learning disabilities. Explainer: https://www.w3.org/TR/personalization-semantics-1.0/ and Module 1 : https://www.w3.org/TR/personalization-semantics-content-1.0/ https://github.com/w3c/personalization-semantics/wiki and https://github.com/w3c/personalization-semantics/wiki/Getting-started-with-personalization-semantics Security and Privacy self-review: https://github.com/w3c/personalization-semantics/issues/131 GitHub repo (if you prefer feedback filed there): https://github.com/w3c/webrtc-dscp-exp/https://github.com/w3c/personalization-semantics/issues Primary contacts (and their relationship to the specification): Charles LaPierre mailto:charlesl@benetech.org Lisa Seeman lisa.seeman@zoho.com Organization(s)/project(s) driving the specification: The Personalization Task Force of APA WG Key pieces of existing multi-stakeholder review or discussion of this specification: WG discussions External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): Beyond the discussion in the wiki on https://github.com/w3c/personalization-semantics/wiki/Implementations-of-Semantics there is also Ehttps://www.easyreading.eu/ and Firefox https://github.com/w3c/personalization-semantics/issues/128 from our Demo at TPAC 2019 in Japan. Special considerations: We would like advice on porting from the "data-" prefix to a more permanent syntax in CR. Should we suggest a prefix or just plain attributes? Note as more modules are produced we could have a sizable number of attributes. All the best Lisa Seeman http://il.linkedin.com/in/lisaseeman/, https://twitter.com/SeemanLisa
Received on Tuesday, 11 February 2020 08:07:32 UTC