- From: Steve Block <steveblock@google.com>
- Date: Tue, 15 Feb 2011 18:37:30 +0000
- To: Dean Jackson <dino@apple.com>
- Cc: Andrei Popescu <andreip@google.com>, public-geolocation@w3.org
> The reasoning is that a developer shouldn't really be concerned with calibration. All they really need to know > is the accuracy of the data they are seeing. I disagree. Exposing information about whether the device needs calibrating is important as it allows the web app to ask the user to address this where appropriate. > I believe the feedback has two core parts: to avoid the term calibration, and to give some variance. If you'd like to add information about the accuracy of the data, this seems to be largely orthogonal to concerns about calibration (a correctly calibrated device may still be inaccurate). Trying to combine accuracy and calibration in a single enum seems awkward, particularly if we're to include an 'unknown' value for either or both concepts. Steve -- Google UK Limited Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W 9TQ Registered in England Number: 3977902
Received on Tuesday, 15 February 2011 18:38:00 UTC