- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Jan 2024 13:59:41 +0000
- To: public-geolocation@w3.org
Hidden in the "[DRAFT] Specification review" disclosure element below is the first proposal for the TAG review request. Please peek inside, everyone. I want us to iterate on this as a group before we file to make sure we include all relevant information and frame this request properly. Contributions wanted via comments to e.g.: - Help fill in the blanks - Additional resources we could provide as a reference - Any specific questions we want to ask to help focus attention - Testing story, should we say something about automation? - Can we better explain the relationship to the Generic Sensor API suite of specs? - Anything else? <details> <summary>[DRAFT] Specification review</summary> I'm requesting a TAG review of DeviceOrientation Event Specification. This specification defines several new DOM events that provide information about the physical orientation and motion of a hosting device. - Explainer¹ (minimally containing user needs and example code): This feature has a good [MDN entry](https://developer.mozilla.org/en-US/docs/Web/API/Device_orientation_events) with example code, see also [Motion Sensors Explainer](https://w3c.github.io/motion-sensors/) for an introduction to low-level and high-level motion sensors, key concepts - Specification URL: https://www.w3.org/TR/orientation-event/ - Tests: https://wpt.fyi/results/orientation-event - User research: [url to public summary/results of research] - Security and Privacy self-review²: [[self-review]](https://github.com/w3c/deviceorientation/blob/main/security-privacy-self-assessment.md) - GitHub repo (if you prefer feedback filed there): https://github.com/w3c/deviceorientation/ - Primary contacts (and their relationship to the specification): - Reilly Grant (@reillyeon), Google, editor, co-chair - Raphael Kubo da Costa (@rakuco), Intel, editor - Anssi Kostiainen (@anssiko), Intel, co-chair - Organization(s)/project(s) driving the specification: Google, Intel - Key pieces of existing multi-stakeholder (e.g. developers, implementers, civil society) support, review or discussion of this specification: - Chromium comments: [url] - Mozilla comments: https://github.com/mozilla/standards-positions/issues/NNN - WebKit comments: https://github.com/WebKit/standards-positions/issues/NNN - Etc. - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): Further details: - [x] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/) - Relevant time constraints or deadlines: A new CR Snapshot expected in March 2024. - The group where the work on this specification is currently being done: Devices and Sensors WG - This specification is expect to become a joint deliverable with the WebApps WG to be jointly published by the two groups before it advances to Rec. - Major unresolved issues with or opposition to this specification: None - This work is being funded by: Google, Intel You should also 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. These changes since the previous CR Snapshot from 2016 align the specification with widely available implementations, improve interoperability including testability, and add new features for enhanced privacy protections. This is a high-level API whose low-level API correspondence Orientation Sensor was reviewed by TAG in https://github.com/w3ctag/design-reviews/issues/207 The functional diff is explained in [high-level vs. low-level ](https://www.w3.org/TR/generic-sensor/#high-vs-low-level) and [Orientation Sensor](https://w3c.github.io/orientation-sensor/#intro). 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** </details> Click to unfold ⤴️ Thanks for your contributions! -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/130#issuecomment-1914752227 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 29 January 2024 13:59:44 UTC