Tuesday, 30 June 2009
Friday, 26 June 2009
- Re: ISSUE-12: Discrepancy in how the text talks about the user giving permission [GeoAPI V1]
- ISSUE-13: The IDL is missing [Callback] extened attribute on PositionCallback, PositionErrorCallback and PositionOptions ifaces [GeoAPI V1]
- ISSUE-12: Discrepancy in how the text talks about the user giving permission [GeoAPI V1]
- ISSUE-11: Discrepancy in how the text talks about the user giving permission [GeoAPI V1]
- updated editor's draft of the Geolocation API specification in preparation for the Last Call transition
Thursday, 25 June 2009
Tuesday, 23 June 2009
Monday, 22 June 2009
Sunday, 21 June 2009
Friday, 19 June 2009
- Re: ISSUE-10 Re: Geopriv compromise proposal
- RE: PositionOptions
- Re: ISSUE-10 Re: Geopriv compromise proposal
- Re: PositionOptions
Thursday, 18 June 2009
- Re: ISSUE-10 Re: Geopriv compromise proposal
- Re: ISSUE-10 Re: Geopriv compromise proposal
- Re: ISSUE-10 Re: Geopriv compromise proposal
- Re: ISSUE-10 Re: Geopriv compromise proposal
- Re: ISSUE-10 Re: Geopriv compromise proposal
- ISSUE-10 Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Last call
- ISSUE-10: Should the Geolocation API methods provide an optional parameter of type URI that allows the location requesting service to advertise a policy (P3P or XACML or some other) that applies to the request? [GeoAPI V1]
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- RE: PositionOptions
- Re: PositionOptions
Wednesday, 17 June 2009
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- RE: PositionOptions
- Re: Geopriv compromise proposal
- Re: PositionOptions
Tuesday, 16 June 2009
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- PositionOptions
- Re: Geopriv compromise proposal
Monday, 15 June 2009
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- ISSUE-9 (restricted-access): Restricting API Access [GeoAPI V1]
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Restricting API access
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: [WebIDL] double
- Re: [WebIDL] double
Sunday, 14 June 2009
Saturday, 13 June 2009
Friday, 12 June 2009
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Re: Geopriv compromise proposal
- Geopriv compromise proposal
Thursday, 11 June 2009
- RE: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- ISSUE-8 (Indoor locations): Add civic address field(s) for indoor locations [GeoAPI V2]
Wednesday, 10 June 2009
- Re: moving to Last Call
- Re: Restricting API access
- FW: [WebIDL] double
- Re: WebIDL, optional attributes
- Re: WebIDL, optional attributes
- Re: moving to Last Call
- Re: WebIDL, optional attributes
- Re: moving to Last Call
- Re: moving to Last Call
- RE: WebIDL, optional attributes
- Re: WebIDL, optional attributes
- RE: WebIDL, optional attributes
- RE: WebIDL, optional attributes
- Re: WebIDL, optional attributes
- RE: WebIDL, optional attributes
- Re: WebIDL, optional attributes
- Re: WebIDL, optional attributes
- Re: WebIDL, optional attributes
- moving to Last Call
- Re: WebIDL, optional attributes
- Re: WebIDL, optional attributes
- Re: WebIDL, optional attributes
- Re: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- WebIDL, optional attributes
- Re: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
Tuesday, 9 June 2009
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Fwd: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
Monday, 8 June 2009
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
Friday, 5 June 2009
- Re: Additional security and privacy considerations?
- Re: Additional security and privacy considerations?
- Re: Additional security and privacy considerations?
- Re: Additional security and privacy considerations?
- Re: Additional security and privacy considerations?
- Re: Additional security and privacy considerations?
- Re: Additional security and privacy considerations?
- Re: Additional security and privacy considerations?
- Re: updated editor's draft of the Geolocation API specification
Thursday, 4 June 2009
- Re: updated editor's draft of the Geolocation API specification
- Re: Additional security and privacy considerations?
- Re: updated editor's draft of the Geolocation API specification
- RE: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- Re: updated editor's draft of the Geolocation API specification
- updated editor's draft of the Geolocation API specification
Wednesday, 3 June 2009
- Re: Additional security and privacy considerations?
- Re: Additional security and privacy considerations?