ISSUE-14
opt-out |
OPEN |
Opt-out by default |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-15
UI-Alert |
OPEN |
UI to alert the user |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-16
opt in duration |
OPEN |
User should be able to select Once/Session/Always "opt-in" |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-17
client-side logging |
OPEN |
Client-side logging of what information was given to whom |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-19
geo object location |
OPEN |
Location of Geolocation object, window vs navigator |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-20
two callbacks |
OPEN |
Two callbacks: success and error |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-21
position caching |
OPEN |
Cached position information/max-age/lastPosition |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-22
onChange |
OPEN |
onChange vs re-register |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-23
DOM Events |
OPEN |
callback vs DOM Events |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-24
error correction |
OPEN |
onChange and raw position vs. error-corrected position |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-25
revocation |
OPEN |
Revocation of rights to use location |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-26 |
OPEN |
MUST vs SHOULD on privacy/security |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-27
geodetic |
OPEN |
Geodetic system |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-28
elevation |
OPEN |
Elevation issues with WGS84 |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-29 |
OPEN |
What is a position? |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-30 |
OPEN |
Reuse the DOM |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-31
velocity |
OPEN |
Should velocity be included in the API |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-32 |
OPEN |
Should heading be included in the API |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-33 |
OPEN |
Synchronous interface |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-35 |
OPEN |
getCurrentPosition/watchPosition 1 vs 2 calls |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-37 |
OPEN |
Distance threshold option to watchPosition |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-38 |
OPEN |
Multiple watchPositions simultaneously |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-39 |
OPEN |
What to do if there is no altitude information |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-40
error codes |
OPEN |
Error codes |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-41 |
OPEN |
Passing timeout option to getCurrentPosition and watchPosition |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-42 |
OPEN |
timestamp xs:dateTime vs epoch time |
2009-07-20 |
GeoAPI V1 |
0 |
ISSUE-43
proximity |
OPEN |
Proximity interface |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-44 |
OPEN |
watchPosition poorly named |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-45 |
OPEN |
clearWatchAll function |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-47 |
OPEN |
PositionError message values |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-48 |
OPEN |
Error codes symbolic names |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-49 |
OPEN |
Accuracy terminology |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-50 |
OPEN |
"Speed" vs "Velocity" |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-51 |
OPEN |
Should the spec mandate a particular privacy-protection UI & mechanism? |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-52 |
OPEN |
Error code 'UNKNOWN' |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-53 |
OPEN |
Wording for the "Privacy section" |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-54 |
OPEN |
Should the spec contain an API for reverse-geocoding? |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-56 |
OPEN |
GeoPriv proposal to extend the Geolocation API with privacy-fields |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-57 |
OPEN |
Typos |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-58 |
OPEN |
'Life log' use case |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-59 |
OPEN |
Refactor the Position interface and group the geodetic coordinates into a separate sub-interface |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-60 |
OPEN |
TOC strangely numbered |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-61 |
OPEN |
The link to WebIDL does not work |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-63 |
OPEN |
Rename the Geolocation API |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-64 |
OPEN |
Support for barometric and EGM96 altitudes |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-66 |
OPEN |
Meaning of Position.heading attribute |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-68 |
OPEN |
PositionError.message clarification |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-69 |
OPEN |
Drop lastPosition? |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-70 |
OPEN |
Position Logging |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-71 |
OPEN |
Position interface should be refactored to be extendable |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-72 |
OPEN |
Multiple altitude measurements |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-73 |
OPEN |
Getting the user's position vs an arbitrary position |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-75 |
OPEN |
Location providers |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-82 |
OPEN |
"Repeated" vs. "Asynchronous" updates |
2009-07-20 |
GeoAPI V1 |
0 |
| ISSUE-83 |
OPEN |
Define "cached position"? |
2009-07-20 |
GeoAPI V1 |
0 |