[w3ctag/design-reviews] Requesting a TAG review of Personalization Semantics Explainer and  Module 1 (#476)

Hello TAG!


We are requesting a TAG review of Personalization Semantics Explainer and  Module 1 - Adaptable Content. It contains supporting syntax that provides 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/) 
- [Module 1](https://www.w3.org/TR/personalization-semantics-content-1.0/)
 

Our [wiki](https://github.com/w3c/personalization-semantics/wiki/) and [getting-started page](https://github.com/w3c/personalization-semantics/wiki/Getting-started-with-personalization-semantics).

Security and Privacy self-review: [PING review](https://github.com/w3c/personalization-semantics/issues/131)

GitHub repo: [Repo and issues](https://github.com/w3c/personalization-semantics/issues)

Primary contacts (and their relationship to the specification):

-Charles LaPierre charlesl@benetech.org (Personalization Taskforce  co-facilitator) 
-Lisa Seeman lisa.seeman@zoho.com  (Personalization Taskforce  co-facilitator) 
-Janina Sajka janina@rednote.net (APA chair)

Organization(s)/project(s) driving the specification: Accessible Platform Architectures (APA) Working Group -  Personalization Taskforce   

Key pieces of existing multi-stakeholder review or discussion of this specification: Taskforce discussions and stakeholder discussion (such as [wiki vocabulary-in-content discussion](https://github.com/w3c/personalization-semantics/wiki/Comparison-of-ways-to-use-vocabulary-in-content) and [wiki symbol discussion](https://github.com/w3c/personalization-semantics/wiki/Options-for-symbol).)

External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): Beyond the [discussion in the wiki](https://github.com/w3c/personalization-semantics/wiki/Implementations-of-Semantics) there is also [Easyreading](Easyreading.eu) and  [Firefox alpha](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.

Further details:

  - I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/)
  - Relevant time constraints or deadlines: We would like to go to CR as soon as possible to be able to go to PR to support WCAG 2.2 CR
  - The group where the work on this specification is being done: APA
  - Major unresolved issues with or opposition to this specification: See special considerations: 
  - This work is being funded by: See https://www.w3.org/TR/personalization-semantics-content-1.0/#ack_funders



We'd prefer the TAG provide feedback as (please delete all but the desired option):

  🐛 open issues in our GitHub repo for **each point of feedback**



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/476