W3C home > Mailing lists > Public > public-device-apis-log@w3.org > November 2016

Re: [sensors] Exposing secondary values in the SensorReading

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Wed, 16 Nov 2016 21:24:11 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-261076568-1479331449-sysbot+gh@w3.org>

How do we distinguish secondary values that are meaningful to 
developers and enable new use cases from those that don't?

-- 
GitHub Notification of comment by tobie
Please view or discuss this issue at 
https://github.com/w3c/sensors/issues/151#issuecomment-261076568 using
 your GitHub account

Received on Wednesday, 16 November 2016 21:24:17 UTC

This message: [ Message body ]
Next message: Tobie Langel via GitHub: "Re: [sensors] Exposing secondary values in the SensorReading"
Previous message: Rick Waldron via GitHub: "Re: [sensors] Exposing secondary values in the SensorReading"
In reply to: Tobie Langel via GitHub: "[sensors] Exposing secondary values in the SensorReading"
Next in thread: Tobie Langel via GitHub: "Re: [sensors] Exposing secondary values in the SensorReading"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:53 UTC