Tuesday, 31 March 2009
- RE: renaming enableHighAccuracy
- RE: renaming enableHighAccuracy
- RE: renaming enableHighAccuracy
- Re: renaming enableHighAccuracy
- Re: renaming enableHighAccuracy
- Re: api comments
- renaming enableHighAccuracy
- Re: Intended usage notification
- Re: api comments
- RE: api comments
- Re: api comments
- Re: delivering test cases
Monday, 30 March 2009
- RE: api comments
- Re: api comments
- api comments
- RE: Geolication API level 2 - editor's draft
- Re: Geolication API level 2 - editor's draft
- RE: Geolication API level 2 - editor's draft
- Re: PositionOptions.timeout & UserAgent permission
- Re: geolocation privacy statement strawman
Saturday, 28 March 2009
- Re: geolocation privacy statement strawman
- Re: geolocation privacy statement strawman
- Re: Intended usage notification
- Re: Intended usage notification
Friday, 27 March 2009
- Re: ISSUE-4 (privacy-geopriv): GEOPRIV WG proposal for privacy within the API
- Re: Intended usage notification
Thursday, 26 March 2009
- RE: Intended usage notification
- Re: Intended usage notification
- RE: Intended usage notification
- Re: Intended usage notification
- RE: Intended usage notification
- RE: Intended usage notification
- Re: Intended usage notification
- Re: Intended usage notification
- RE: ISSUE-5 (privacy-text): What should the Recommendation state about security and privacy considerations?
- Intended usage notification
- Re: ISSUE-4 (privacy-geopriv): GEOPRIV WG proposal for privacy within the API
- Re: ISSUE-4 (privacy-geopriv): GEOPRIV WG proposal for privacy within the API
- Re: ISSUE-4 (privacy-geopriv): GEOPRIV WG proposal for privacy within the API
- Re: delivering test cases
- ISSUE-5 (privacy-text): What should the Recommendation state about security and privacy considerations?
- Re: ISSUE-4 (privacy-geopriv): GEOPRIV WG proposal for privacy within the API
- ISSUE-4 (privacy-geopriv): GEOPRIV WG proposal for privacy within the API
- Re: delivering test cases
- Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information?
- Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information?
- Opera Geolocation build
- Tracker and other tools
- Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information?
- Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information?
- Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information?
- Re: ISSUE-3 (civic-addressing): Exposing civic addresses in the API
- Re: Geolication API level 2 - editor's draft
- Re: ISSUE-3 (civic-addressing): Exposing civic addresses in the API
- Re: ISSUE-3 (civic-addressing): Exposing civic addresses in the API
Wednesday, 25 March 2009
- RE: geolocation privacy statement strawman
- ISSUE-3 (civic-addressing): Exposing civic addresses in the API
- Re: geolocation privacy statement strawman
- Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information?
- Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information?
- Re: geolocation privacy statement strawman
- Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information?
- ISSUE-2 (privacy): Should the Geolocation API include privacy information?
- Re: Geolication API level 2 - editor's draft
- Re: Geolication API level 2 - editor's draft
- Re: Geolication API level 2 - editor's draft
- Re: geolocation privacy statement strawman
- RE: Geolication API level 2 - editor's draft
- Re: geolocation privacy statement strawman
- Re: FYI: GEOPRIV meeting on thursday
Tuesday, 24 March 2009
Monday, 23 March 2009
Saturday, 21 March 2009
Friday, 20 March 2009
- RE: Geolication API level 2 - editor's draft
- RE: Geolication API level 2 - editor's draft
- Re: Geolication API level 2 - editor's draft
- Re: PositionOptions.timeout & UserAgent permission
- Re: Geolication API level 2 - editor's draft
- Re: Civic Address for V2
Thursday, 19 March 2009
- Re: PositionOptions.timeout & UserAgent permission
- Re: PositionOptions.timeout & UserAgent permission
- Re: PositionOptions.timeout & UserAgent permission
Wednesday, 18 March 2009
- Re: PositionOptions.timeout & UserAgent permission
- Re: PositionOptions.timeout & UserAgent permission
- Re: PositionOptions.timeout & UserAgent permission
- Re: PositionOptions.timeout & UserAgent permission
Tuesday, 17 March 2009
- Re: More on TimeOut, MaximumAge and EnableHighAccuracy
- Re: PositionOptions.timeout & UserAgent permission
- privacy issues
- More on TimeOut, MaximumAge and EnableHighAccuracy
- Re: PositionOptions.timeout & UserAgent permission
Monday, 16 March 2009
- RE: PositionOptions.timeout & UserAgent permission
- Geolication API level 2 - editor's draft
- Re: PositionOptions.timeout & UserAgent permission
Sunday, 15 March 2009
- Re: PositionOptions.timeout & UserAgent permission
- Re: PositionOptions.timeout & UserAgent permission
- PositionOptions.timeout & UserAgent permission
Wednesday, 11 March 2009
Tuesday, 10 March 2009
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Test suite
- Re: geolocation privacy statement strawman
- Re: geolocation privacy statement strawman
- RE: Civic Address for V2
- Re: Civic Address for V2
Monday, 9 March 2009
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- RE: Civic Address for V2
- Re: geolocation privacy statement strawman
- Re: geolocation privacy statement strawman
- Re: geolocation privacy statement strawman
- RE: geolocation privacy statement strawman
Friday, 6 March 2009
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: geolocation privacy statement strawman
- Re: geolocation privacy statement strawman
- geolocation privacy statement strawman
Wednesday, 4 March 2009
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: delivering test cases
- Re: Civic Address for V2
Tuesday, 3 March 2009
- RE: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- RE: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- RE: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- RE: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- delivering test cases
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
- Re: Civic Address for V2
Monday, 2 March 2009
- Re: Civic Address for V2
- Re: Civic Address for V2
- RE: Civic Address for V2
- Re: Civic Address for V2
- RE: Civic Address for V2
- Re: Civic Address for V2
- RE: Civic Address for V2