Privacy/Reviews/GeolocationAPI: Difference between revisions

Line 92: Line 92:
|-
|-
| location data  
| location data  
| (where stored)
| nsIDOMGeoPositionCoords object stored as an nsCOMPtr property in the request object
|-
| civic addresses
| (where stored)
|}
|}


''TODO: describe "location data" more technically" and identify where the data is stored for entries in the above table.'''
The civic addresses are not stored in this component, and are only retrieved and passed as parameter arguments to/from the third party geocoding API. No actual civic address object is being stored in this component.  The location data stored in this component are provided by the page holding location request and may or may not have been obtained through the other geolocation API.


''Note:'' The civic addresses stored in this component are those retrieved from the third party geocoding API.  The location data stored in this component are provided by the page holding location request and may or may not have been obtained through the other geolocation API.
'''Note:''' "location data" in this context is equivalent to the coordinates interface as described in the W3C Geolocation API documentation here: http://dev.w3.org/geo/api/spec-source.html#coordinates_interface


'''Communication with page requesting location data:'''
'''Communication with page requesting location data:'''
Line 127: Line 124:


''TODO: document the API here -- what are the third party request API call names?  What data (specifically) do we send them and what do they return?'''
''TODO: document the API here -- what are the third party request API call names?  What data (specifically) do we send them and what do they return?'''


===Platform Reverse Geocoding API (3rd-Party)===
===Platform Reverse Geocoding API (3rd-Party)===
4

edits