ISSUE-6: Is enableHighAccuracy the right naming for this attribute? Should we have it at all?

enableHighAccuracy

Is enableHighAccuracy the right naming for this attribute? Should we have it at all?

State:
CLOSED
Product:
GeoAPI V2
Raised by:
Andrei Popescu
Opened on:
2009-04-03
Description:
The following questions about

http://dev.w3.org/geo/api/spec-source.html#high-accuracy

should be clarified:

- is it needed?
- if it is, what is its correct name?

More background to this can be found in these threads:
http://lists.w3.org/Archives/Public/public-geolocation/2009Mar/0160.html
http://lists.w3.org/Archives/Public/public-geolocation/2008Jun/0094.html
http://lists.w3.org/Archives/Public/public-geolocation/2008Jun/0107.html

This was talked about during the F2F meeting:
http://www.w3.org/2008/12/09-geolocation-minutes#item04
Related Actions Items:
No related actions
Related emails:
  1. RE: updated editor's draft of the Geolocation API specification (from [email protected] on 2009-06-11)
  2. Re: updated editor's draft of the Geolocation API specification (from [email protected] on 2009-06-11)
  3. Re: moving to Last Call (from [email protected] on 2009-06-10)
  4. Re: moving to Last Call (from [email protected] on 2009-06-10)
  5. Re: moving to Last Call (from [email protected] on 2009-06-10)
  6. moving to Last Call (from [email protected] on 2009-06-10)
  7. Re: updated editor's draft of the Geolocation API specification (from [email protected] on 2009-06-09)
  8. RE: updated editor's draft of the Geolocation API specification (from [email protected] on 2009-06-09)
  9. Re: updated editor's draft of the Geolocation API specification (from [email protected] on 2009-06-09)
  10. RE: updated editor's draft of the Geolocation API specification (from [email protected] on 2009-06-09)
  11. Re: updated editor's draft of the Geolocation API specification (from [email protected] on 2009-06-09)
  12. Re: updated editor's draft of the Geolocation API specification (from [email protected] on 2009-06-09)
  13. RE: updated editor's draft of the Geolocation API specification (from [email protected] on 2009-06-08)
  14. Re: updated editor's draft of the Geolocation API specification (from [email protected] on 2009-06-08)
  15. Re: updated editor's draft of the Geolocation API specification (from [email protected] on 2009-06-08)
  16. Re: updated editor's draft of the Geolocation API specification (from [email protected] on 2009-06-08)
  17. Re: editor's draft should link to last published draft (from [email protected] on 2009-04-03)
  18. ISSUE-6 (enableHighAccuracy): Is enableHighAccuracy the right naming for this attribute? Should we have it at all? (from [email protected] on 2009-04-03)

Related notes:

This was discussed at the face to face as well:
http://www.w3.org/2008/12/09-geolocation-minutes#item04

Matt Womer, 6 Apr 2009, 21:09:31

Moving this issue to V2. We have discussed this extensively and we agree that the name should be improved. The concrete proposal is detailed here:

http://lists.w3.org/Archives/Public/public-geolocation/2009Apr/0034.html

However, since we have many implementations that have shipped already using "enableHighAccuracy", it is better to keep V1 unmodified and reflecting reality. Else, developers will be reading a spec that is not different to any existing implementation.

We will re-discuss this issue in the context of V2 of the API.

Andrei Popescu, 10 Jun 2009, 11:35:44

We will keep this attribute as is for backwards compatibility with v1.

Lars Erik Bolstad, 4 Nov 2010, 13:41:36

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <[email protected]>.
$Id: 6.html,v 1.1 2017/05/30 09:54:30 carine Exp $