- From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Feb 2024 10:26:55 +0000
- To: public-device-apis-log@w3.org
rakuco has just created a new issue for https://github.com/w3c/sensors: == "Connect to sensor" does not take fusion sensors into consideration == https://w3c.github.io/sensors/#concepts-sensors says > In simple cases, a [platform sensor](https://w3c.github.io/sensors/#concept-platform-sensor) corresponds to a single [device sensor](https://w3c.github.io/sensors/#concept-device-sensor), but if the provided [sensor readings](https://w3c.github.io/sensors/#sensor-reading) are a product of [sensor fusion](https://w3c.github.io/sensors/#sensor-fusion) performed in software, the [platform sensor](https://w3c.github.io/sensors/#concept-platform-sensor) corresponds to **a set** of [device sensors](https://w3c.github.io/sensors/#concept-device-sensor) involved in the [sensor fusion](https://w3c.github.io/sensors/#sensor-fusion) process. whereas https://w3c.github.io/sensors/#connect-to-sensor has > If the device has a single [device sensor](https://w3c.github.io/sensors/#concept-device-sensor) which can provide [readings](https://w3c.github.io/sensors/#sensor-reading) for type, then > [...] > If the device has multiple [device sensors](https://w3c.github.io/sensors/#concept-device-sensor) which can provide [readings](https://w3c.github.io/sensors/#sensor-reading) for type, then which essentially assumes there is one device sensor backing a platform sensor. The language needs to be adjusted so that multiple device sensors are accepted and processed accordingly (i.e. `platformSensor` remains null if connecting to all required sensors does not work). Please view or discuss this issue at https://github.com/w3c/sensors/issues/479 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 February 2024 10:26:57 UTC