- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 May 2015 12:45:23 +0000
- To: public-device-apis@w3.org
Seems there's consensus that supporting multiple values per sensor is a requirement. There are two proposed options for how expose those: 1. array-based (as is done on Android), 2. using named properties. My preference would go for using named properties as it seems much more Web-y. It's more inline with the best practice of [preferring named constants to numerical ones](http://www.w3.org/TR/api-design/#numerical-constants). I also don't believe either solutions would have a measurable impact on the time it would take to spec a new kind of sensor. Whereas named props require… naming, an array-based solution requires specifying the order if you want any kind of interoperability. **Proposed resolution:** the Generic Sensor API needs to support sensors with multiple values. This should be implementable using domain-specific named properties. -- GitHub Notif of comment by tobie See https://github.com/w3c/sensors/issues/2#issuecomment-100222032
Received on Friday, 8 May 2015 12:45:24 UTC