- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Nov 2021 09:08:36 +0000
- To: public-device-apis-log@w3.org
@reillyeon @rakuco here's one detail I want you to pay attention to in your review: This PR implicitly defines any Generic Sensor-based API as a powerful feature via the "name" reference linking back to ["a powerful feature is identified by its name"](https://www.w3.org/TR/permissions/#dfn-name). A powerful feature is currently defined as follows (emphasis mine): >A powerful feature is a web platform feature (usually an API) for which a user gives express permission before the feature can be used. Access to the feature is determined by the environment settings object by the user having granted permission via UI, or by satisfying some _criteria that is equivalent to a permission grant_. > >https://www.w3.org/TR/permissions/#dfn-powerful-feature A possible issue may arise if the powerful feature definition changes in incompatible ways or if this language is interpreted differently. Technically, Generic Sensor API is not a powerful feature. It can be extended to create a powerful feature or a "powerless" feature. A solution might be to state that for Generic Sensor API the "_criteria that is equivalent to a permission grant_" (this could become a dfn so it could be referenced) is https://pr-preview.s3.amazonaws.com/w3c/sensors/pull/416.html#concepts-can-expose-sensor-readings that allows extension specs to add additional conditions. This also allows implementers to innovate in terms of UX. Thoughts? @marcoscaceres for Permissions API. -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/sensors/pull/416#issuecomment-976304721 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 November 2021 09:08:39 UTC