- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Jan 2021 13:50:56 +0000
- To: public-device-apis-log@w3.org
@andycarle, thanks for raising this issue. As @reillyeon noted, feedback on your preferred approach would help us tighten normative language around this attribute's behavior. The introduction section is informative and as such does not impose implementation requirements. We'd need to craft additional normative text to address your issue, which I propose we try to do if there's a significant population of proximity sensors that can only report boolean presence. I believe we should augment the following normative statement for `distance`: >If the physical object is outside the sensing range, the attribute must return null. I think it is probably more aligned with the platform conventions to have that attribute around and specify a special value to indicate this case. Some ideas: We could return null for both "outside the sensing range" and "implementation is unable to provide" cases: >If the physical object is outside the sensing range, the attribute must return null. >If the implementation is unable to provide the distance value, the attribute must return null. If we'd want to differentiate between the two cases change the attribute's type to e.g. `unrestricted double` to be able to return positive Infinity to indicate the former case, e.g.: >If the physical object is outside the sensing range, the attribute must return positive Infinity. >If the implementation is unable to provide the distance value, the attribute must return null. The tradeoff here is we'd loose the symmetrical behavior between `distance` and `near` when outside the sensing range, so I guess suggestions are welcome :-) Luckily there's flexibility for us to adjust the API behavior given the API hasn't yet shipped. Please let us know your thoughts and we'll clarify the spec. It is exciting to see the TC53 work unfold :-) -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/proximity/issues/44#issuecomment-769066046 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 January 2021 13:50:57 UTC