- From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Nov 2023 17:52:57 +0000
- To: public-geolocation@w3.org
Switching the existing tests in WPT to this approach does seem to work, doing this from a spec perspective is a bit tricky. The idea is to be able to say "we only depend on the Automation section", but the Automation section itself references concepts from other parts of the spec. For example, if we were to define a [per-type virtual sensor metadata](https://w3c.github.io/sensors/#per-type-virtual-sensor-metadata) entry for "relative-orientation-euler", we'd need to define a corresponding [virtual sensor type](https://w3c.github.io/sensors/#virtual-sensor-metadata-virtual-sensor-type), which is a [sensor type](https://w3c.github.io/sensors/#sensor-type). A sensor type requires one or more IDL interfaces, powerful feature names and permissions policy tokens. Similarly, if we want to use the "accelerometer" virtual sensor type for Device Motion, it means referencing https://w3c.github.io/accelerometer/#accelerometer-automation, which references the [Accelerometer sensor type](https://w3c.github.io/accelerometer/#accelerometer-sensor-type) that requires the presence of the Accelerometer IDL interface. In practice, this is a lot of spec legalese, but it's hard to ignore when changing this specification. Copying the content from the Generic Sensor spec doesn't fully solve the problem either, as we'd then have conflicting behavior definitions for sensors like accelerometer and gyroscope. -- GitHub Notification of comment by rakuco Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/122#issuecomment-1814956672 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 16 November 2023 17:52:59 UTC