public-device-apis@w3.org from February 2010 by date

Sunday, 28 February 2010

• Re: [Powerbox] Q's on the proposal Mark Seaborn
• Proposed text for privacy requirements Frederick Hirsch
• Privacy paper : Privacy Issues of the W3C Geolocation API Frederick Hirsch
• Re: [Powerbox] Fine-grained and non-installed providers Mark Seaborn

Saturday, 27 February 2010

• RE: Bluetooth / NFC APIs 전종홍
• [Powerbox] Fine-grained and non-installed providers Kenton Varda

Friday, 26 February 2010

• Re: Bluetooth / NFC APIs Max Froumentin
• RE: [Powerbox] Q's on the proposal richard.tibbett@orange-ftgroup.com
• RE: Bluetooth / NFC APIs Nilsson, Claes1

Thursday, 25 February 2010

• Re: [Powerbox] Q's on the proposal Mark Seaborn
• Re: [Powerbox] Q's on the proposal Mark Seaborn

Friday, 26 February 2010

• Re: Bluetooth / NFC APIs Max Froumentin
• Re: Bluetooth / NFC APIs Tim Renouf

Thursday, 25 February 2010

• Re: Bluetooth / NFC APIs Nikolai Onken
• RE: Bluetooth / NFC APIs Nilsson, Claes1
• v2 minutes 2010-02-24 Frederick Hirsch
• RE: ACTION-16 for SystemInfo API JOSE MANUEL CANTERA FONSECA
• Re: [Powerbox] Q's on the proposal Anssi Kostiainen

Wednesday, 24 February 2010

• [Powerbox] Q's on the proposal richard.tibbett@orange-ftgroup.com
• RE: Draft minutes 2010-02-24 richard.tibbett@orange-ftgroup.com
• Draft minutes 2010-02-24 Frederick Hirsch
• Re: REST: DAP Web Server to access to local resources Robin Berjon
• RE: [Powerbox] A RESTful proposal for Web enabling devices SULLIVAN, BRYAN L (ATTCINW)
• RE: DAP Activity & WAC 전종홍
• RE: [Powerbox] latest draft (was: Agenda - Distributed Meeting 2010-02-24) richard.tibbett@orange-ftgroup.com
• REST: DAP Web Server to access to local resources Nilsson, Claes1
• Re: [Powerbox] A RESTful proposal for Web enabling devices Robin Berjon
• Re: Contacts API typical use cases and privacy considerations Robin Berjon
• Re: [Powerbox] latest draft (was: Agenda - Distributed Meeting 2010-02-24) Dominique Hazael-Massieux
• Re: DAP Activity & WAC Robin Berjon
• Blast from the past Robin Berjon
• RE: [Powerbox] A RESTful proposal for Web enabling devices David Rogers
• OMTP BONDI 1.1 Approved Release David Rogers
• Re: ACTION-16 for SystemInfo API Max Froumentin
• ACTION-46: Provide input of capability definition and semantics DANIEL JESUS COLOMA BAIGES
• Fwd: Forward: RFC 5546 on iCalendar Transport-Independent Interoperability Protocol (iTIP) Thomas Roessler

Tuesday, 23 February 2010

• [Powerbox] latest draft (was: Agenda - Distributed Meeting 2010-02-24) Tyler Close
• Re: [Powerbox] A RESTful proposal for Web enabling devices Kenton Varda
• Agenda - Distributed Meeting 2010-02-24 Frederick Hirsch
• Re: [Powerbox] A RESTful proposal for Web enabling devices Tyler Close
• ACTION-48: Propose a definition for API access control, and a possible model for policy enforcement Suresh Chitturi
• Re: [Powerbox] A RESTful proposal for Web enabling devices Robin Berjon
• RE: Contacts API typical use cases and privacy considerations richard.tibbett@orange-ftgroup.com
• Updated version of Messaging API available Niklas Widell

Monday, 22 February 2010

• Bluetooth / NFC APIs Nikolai Onken

Tuesday, 23 February 2010

• Re: SystemInfo API Dominique Hazael-Massieux
• RE: ACTION-16 for SystemInfo API Rotan Hanrahan
• Re: ACTION-16 for SystemInfo API Max Froumentin
• RE: Contacts API typical use cases and privacy considerations Dominique Hazael-Massieux
• RE: Contacts API typical use cases and privacy considerations richard.tibbett@orange-ftgroup.com
• RE: Contacts API typical use cases and privacy considerations richard.tibbett@orange-ftgroup.com
• RE: Contacts API typical use cases and privacy considerations richard.tibbett@orange-ftgroup.com
• Re: Contacts API typical use cases and privacy considerations Max Froumentin
• ACTION-16 for SystemInfo API SULLIVAN, BRYAN L (ATTCINW)
• Re: [Powerbox] A RESTful proposal for Web enabling devices Kenton Varda

Monday, 22 February 2010

• RE: Contacts API typical use cases and privacy considerations Dominique Hazael-Massieux

Friday, 19 February 2010

• Re: [Powerbox] A RESTful proposal for Web enabling devices Tyler Close
• Re: [Powerbox] A RESTful proposal for Web enabling devices Dirk Pranke
• [Powerbox] A RESTful proposal for Web enabling devices Tyler Close
• RE: Contacts API typical use cases and privacy considerations richard.tibbett@orange-ftgroup.com
• RE: Contacts API typical use cases and privacy considerations richard.tibbett@orange-ftgroup.com
• RE: Contacts API typical use cases and privacy considerations Dominique Hazael-Massieux
• RE: Contacts API typical use cases and privacy considerations richard.tibbett@orange-ftgroup.com
• RE: Contacts API typical use cases and privacy considerations Dominique Hazael-Massieux
• RE: Contacts API typical use cases and privacy considerations richard.tibbett@orange-ftgroup.com
• RE: Contacts API typical use cases and privacy considerations richard.tibbett@orange-ftgroup.com
• Re: DAP Activity & WAC Arthur Barstow
• Contacts API typical use cases and privacy considerations Dominique Hazael-Massieux
• Re: DAP API Exchange Control (was: RE: A comment on Security and Privacy Implications for Contact APIs) Dominique Hazael-Massieux
• DAP Activity & WAC 전종홍

Thursday, 18 February 2010

• Re: Concrete REST proposal timing and status Mark Baker

Wednesday, 17 February 2010

• Call today cancelled Robin Berjon
• [SysInfo] Status of AI to review SULLIVAN, BRYAN L (ATTCINW)

Tuesday, 16 February 2010

• RE: Regrets, RE: Should we cancel tomorrow? Tran, Dzung D
• Regrets, RE: Should we cancel tomorrow? Paddy Byers
• RE: Should we cancel tomorrow? Nilsson, Claes1
• Regrets, RE: Should we cancel tomorrow? Marcin Hanclik
• Should we cancel tomorrow? Robin Berjon

Monday, 15 February 2010

• Bindings licensing Robin Berjon

Saturday, 13 February 2010

• Concrete REST proposal timing and status Frederick Hirsch

Friday, 12 February 2010

• RE: Sensors simplified (or not) Nilsson, Claes1
• Re: Simple LREST toying Anssi Kostiainen
• Re: Simple LREST toying Anne van Kesteren
• Re: Simple LREST toying Arve Bersvendsen
• Re: Simple LREST toying Frederick Hirsch
• Re: Sensors simplified (or not) Max Froumentin
• Re: Simple LREST toying Anne van Kesteren

Thursday, 11 February 2010

• Re: Simple LREST toying Frederick Hirsch
• RE: Sensors simplified (or not) Tran, Dzung D
• RE: Sensors simplified (or not) Tran, Dzung D
• RE: Sensors simplified (or not) Nilsson, Claes1
• Simple LREST toying Robin Berjon
• Re: Sensors simplified (or not) Max Froumentin
• RE: Sensors simplified (or not) Nilsson, Claes1
• Re: SV: Editor questions Frederick Hirsch
• Re: SV: Editor questions Robin Berjon
• SV: Editor questions Niklas Widell
• Re: Editor questions Robin Berjon
• Re: Sensors simplified (or not) Max Froumentin

Wednesday, 10 February 2010

• RE: Sensors simplified (or not) Tran, Dzung D
• Editor questions Frederick Hirsch
• Approved 3 Feb minutes Frederick Hirsch
• Draft minutes v2 (HTML and text) 2010-02-10 Hirsch Frederick (Nokia-CIC/Boston)
• RE: Devices as Virtual Web Services SULLIVAN, BRYAN L (ATTCINW)
• Draft minutes (HTML) 2010-02-10 Frederick Hirsch
• Sensors simplified (or not) Max Froumentin
• RE: Regrets.... David Rogers
• Re: Next steps for Policy Requirements draft? Suresh Chitturi
• Regrets.... John Morris
• Next steps for Policy Requirements draft? Frederick Hirsch
• Re: Devices as Virtual Web Services Frederick Hirsch
• Re: Devices as Virtual Web Services Robin Berjon
• Re: Devices as Virtual Web Services Robin Berjon
• Re: Devices as Virtual Web Services Thomas Roessler
• RE: Devices as Virtual Web Services Nilsson, Claes1
• Re: Devices as Virtual Web Services Anne van Kesteren
• RE: Devices as Virtual Web Services Nilsson, Claes1
• Re: Devices as Virtual Web Services Thomas Roessler
• RE: Devices as Virtual Web Services Nilsson, Claes1
• Re: Devices as Virtual Web Services Robin Berjon
• Re: Devices as Virtual Web Services Anne van Kesteren
• Re: Devices as Virtual Web Services Thomas Roessler
• Re: Devices as Virtual Web Services Frederick Hirsch
• Re: Devices as Virtual Web Services Ian Hickson
• Re: Devices as Virtual Web Services Frederick Hirsch
• RE: Devices as Virtual Web Services Nilsson, Claes1
• Agenda - Distributed Meeting 2010-02-10 Robin Berjon

Tuesday, 9 February 2010

• RE: [calendar] Draft updated Suresh Chitturi

Monday, 8 February 2010

• ISSUE-75 (respec-non-rectrack): ReSpec should support non-RecTrack override [ReSpec] Device APIs and Policy Working Group Issue Tracker
• ISSUE-74 (respec-multi-prev): ReSpec should support multiple previous versions (e.g. for merged documents) [ReSpec] Device APIs and Policy Working Group Issue Tracker
• Prague F2F questionnaire Robin Berjon

Saturday, 6 February 2010

• File API - readAsText() - newline translation Michael A. Puls II

Thursday, 4 February 2010

• Re: New filesystem/directory API proposal イアンフェッティ
• Re: New filesystem/directory API proposal Arve Bersvendsen
• Re: New filesystem/directory API proposal イアンフェッティ
• Re: New filesystem/directory API proposal Jeremy Orlow
• Re: New filesystem/directory API proposal Arve Bersvendsen
• Re: New filesystem/directory API proposal Eric Uhrhane
• DAP API Exchange Control (was: RE: A comment on Security and Privacy Implications for Contact APIs) richard.tibbett@orange-ftgroup.com
• Re: New filesystem/directory API proposal Anselm R Garbe
• Re: New filesystem/directory API proposal Eric Uhrhane
• Re: New filesystem/directory API proposal Ian Hickson
• Re: New filesystem/directory API proposal Eric Uhrhane

Wednesday, 3 February 2010

• Re: New filesystem/directory API proposal Ian Hickson
• Re: W3C TAG position on policy mechanisms for Web APIs and Services Appelquist, Daniel, VF-Group
• Re: New filesystem/directory API proposal Eric Uhrhane
• Re: New filesystem/directory API proposal Jeremy Orlow
• Re: New FileWriter proposal Eric Uhrhane
• Re: [calendar] Draft updated Andrew McMillan
• Re: A comment on Security and Privacy Implications for Contact APIs noah_mendelsohn@us.ibm.com
• Draft Minutes 2010-02-03 Robin Berjon
• RE: Agenda - Distributed Meeting 2010-02-03 Marcin Hanclik
• Re: New filesystem/directory API proposal Anselm R Garbe
• Re: New FileWriter proposal Robin Berjon
• RE: ISSUE-73 (contacts-security): Security and Privacy Implications for PIM APIs [APIs - General] richard.tibbett@orange-ftgroup.com
• Re: New filesystem/directory API proposal Ian Hickson
• Re: A comment on Security and Privacy Implications for Contact APIs Robin Berjon
• ISSUE-73 (contacts-security): Security and Privacy Implications for PIM APIs [APIs — General] Device APIs and Policy Working Group Issue Tracker
• Re: ACTION-85: BONDI's investigation into LREST vs "conventional" JavaScript APIs Robin Berjon
• Re: ACTION-85: BONDI's investigation into LREST vs "conventional" JavaScript APIs Adam Barth

Tuesday, 2 February 2010

• RE: Agenda - Distributed Meeting 2010-02-03 Suresh Chitturi
• Regrets (was: Agenda - Distributed Meeting 2010-02-03) Paddy Byers
• Writing good specs Robin Berjon
• Workshop on Access Control Application Scenarios Report Robin Berjon
• Agenda - Distributed Meeting 2010-02-03 Robin Berjon
• Re: Publishing System Information API FPWD Max Froumentin
• Re: Devices as Virtual Web Services Arve Bersvendsen
• Re: New filesystem/directory API proposal Eric Uhrhane
• Re: New filesystem/directory API proposal Eric Uhrhane
• Re: New filesystem/directory API proposal Eric Uhrhane

Monday, 1 February 2010

• Re: New filesystem/directory API proposal Ian Hickson
• Re: New filesystem/directory API proposal イアンフェッティ
• Re: New filesystem/directory API proposal Michael Nordman
• RE: Publishing System Information API FPWD Nilsson, Claes1
• [calendar] Draft updated richard.tibbett@orange-ftgroup.com
• Re: Publishing System Information API FPWD Max Froumentin
• Re: [sysinfo] SEMC comments (was RE: Publishing System Information API FPWD) Max Froumentin

Last message date: Sunday, 28 February 2010 19:44:07 UTC