[deviceorientation] Wide review tracker (#130)

anssiko has just created a new issue for https://github.com/w3c/deviceorientation:

== Wide review tracker ==
### About

This is a meta issue to track [wide review](https://www.w3.org/2023/Process-20231103/#wide-review) for the [DeviceOrientation Event Specification](https://www.w3.org/TR/orientation-event/).

An important part of wide review is horizontal review from W3C's [key horizontal groups](https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review) listed below in **horizontal groups** section. Also feedback from **other stakeholders** is equally important. Additional pointers are welcome via comments.

>Legend:
>🔴 Review request not submitted
>🟡 Review request submitted
>🔵 Review feedback received
>🟢 Review closed as completed

### History

The reviews may want to know that...

This spec initially reached CR in August 2016 ([history](https://www.w3.org/standards/history/orientation-event/)) and was [retired in 2017](https://www.w3.org/TR/2017/NOTE-orientation-event-20170530/) due to the Geolocation WG closure. In 2019 DAS WG adopted this spec and during 2019-2024 made substantial interoperability, test automation, privacy and editorial improvements as outlined in the [changes](https://www.w3.org/TR/orientation-event/#changes) section.

A new CR Snapshot publication in expected in Q1'24 if no unresolvable concerns in this wide review are unearthed. We expect to  make this a joint deliverable between the DAS WG and WebApps WG.

### Horizontal groups

🔴 ♿ **Accessibility**

- [ ] Work through <a rel="nofollow" class="external text" href="https://w3c.github.io/apa/fast/checklist.html">this questionnaire</a>
   - [ ] Link to a11y checklist in this repo
- [ ] <a rel="nofollow" class="external text" href="https://github.com/w3c/a11y-request/issues/new/choose">request a review via GitHub</a> from <a rel="nofollow" class="external text" href="https://www.w3.org/WAI/APA/">APA</a>
  - [ ] Link to review request in the w3c/a11y-request repo

🔴 📐 **Architecture**

- [ ] Ask the <a rel="nofollow" class="external text" href="https://www.w3.org/2001/tag/">TAG</a> for review; see <a rel="nofollow" class="external text" href="https://tag.w3.org/workmode/">how to work with the TAG</a>
   - [ ] Link to review request in w3ctag/design-reviews
     - Reusable materials for the review request:
       - Review request https://github.com/w3ctag/design-reviews/issues/207 for the Generic Sensor API + Orientation Sensor
       - Explainer https://w3c.github.io/motion-sensors/
       - Functional diff [high-level (this) vs. low-level (Generic Sensor API)](https://www.w3.org/TR/generic-sensor/#high-vs-low-level) vs. [Orientation Sensor](https://w3c.github.io/orientation-sensor/#intro)
       - Changes since last CR https://www.w3.org/TR/orientation-event/#changes

- [ ] If you are developing javascript APIs you may also want to ask <a rel="nofollow" class="external text" href="mailto:public-script-coord@w3.org">public-script-coord@w3.org</a>, a technical discussion list shared by W3C and ECMA's TC 39
   - [ ] Proposal: No issues related to JS language features that should be brought to TC 39 for consideration.

🔴 🌍 **Internationalisation**

- [ ] Read the <a rel="nofollow" class="external text" href="https://www.w3.org/International/review-request">Request a review</a> page
- [ ] work through the <a rel="nofollow" class="external text" href="https://www.w3.org/International/i18n-drafts/techniques/shortchecklist">Short Checklist</a>
  - [ ] Link to i18n checklist in this repo
- [ ] <a rel="nofollow" class="external text" href="https://github.com/w3c/i18n-request/issues/new/choose">request a review via GitHub</a>
  - [ ] Link to review request in w3c/i18n-request

🔴 🔍 **Privacy**

- [x] Write a "Privacy Considerations" section for your document, taking into account the <a rel="nofollow" class="external text" href="https://www.w3.org/TR/security-privacy-questionnaire/">Self-Review Questionnaire: Security and Privacy</a>, <a rel="nofollow" class="external text" href="https://www.w3.org/TR/fingerprinting-guidance/">Mitigating Browser Fingerprinting in Web Specifications</a>, and <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc6973.html">RFC6973</a>
   - [x] Self-Review Questionnaire PR #126
   - [x] [Spec: Security and privacy considerations](https://www.w3.org/TR/orientation-event/#security-and-privacy)
- [ ] <a rel="nofollow" class="external text" href="https://github.com/w3cping/privacy-request/issues/new/choose">request a review via GitHub</a> from the <a rel="nofollow" class="external text" href="https://www.w3.org/Privacy/">Privacy Interest Group</a>
  - [ ] Link to review request in w3cping/privacy-request repo

🔴 🔒 **Security**
- [x] Write a "Security Considerations" section for your document, taking into account the <a rel="nofollow" class="external text" href="https://www.w3.org/TR/security-privacy-questionnaire/">Self-Review Questionnaire: Security and Privacy</a>
   - [x] [Spec: Security and privacy considerations](https://www.w3.org/TR/orientation-event/#security-and-privacy)
- [ ] <a rel="nofollow" class="external text" href="https://github.com/w3c/security-request/issues/new/choose">request a review via GitHub</a>
  - [ ] Link to review request in w3c/security-request repo

### Other stakeholders

From [who to ask for review](https://www.w3.org/Guide/documentreview/#who_to_ask_for_review):
>Horizontal reviews [...] are only a subset of a full wide review, which must also include other stakeholders including Web developers, technology providers and implementers not active in the Working Group, external groups and standards organizations working on related areas, etc.

Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/130 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 22 January 2024 13:49:09 UTC