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

Sunday, 31 January 2010

• Re: Past discussions on vCard datamodel for contacts API (ISSUE-71) Suresh Chitturi

Saturday, 30 January 2010

• Re: New filesystem/directory API proposal Anne van Kesteren
• Re: New filesystem/directory API proposal イアンフェッティ
• Re: New filesystem/directory API proposal Anne van Kesteren
• Re: New filesystem/directory API proposal Arve Bersvendsen

Friday, 29 January 2010

• Re: New filesystem/directory API proposal Eric Uhrhane
• Re: New filesystem/directory API proposal Eric Uhrhane
• Re: New filesystem/directory API proposal Arve Bersvendsen
• Re: New filesystem/directory API proposal Arve Bersvendsen
• Re: New filesystem/directory API proposal Arve Bersvendsen
• New filesystem/directory API proposal Eric Uhrhane
• New FileWriter proposal Eric Uhrhane
• Re: Publishing System Information API FPWD Thomas Roessler
• RE: Publishing System Information API FPWD Tran, Dzung D
• RE: [sysinfo] SEMC comments (was RE: Publishing System Information API FPWD) Nilsson, Claes1
• Re: [sysinfo] SEMC comments (was RE: Publishing System Information API FPWD) Thomas Roessler
• [sysinfo] SEMC comments (was RE: Publishing System Information API FPWD) Nilsson, Claes1
• Re: Past discussions on vCard datamodel for contacts API (ISSUE-71) Thomas Roessler
• RE: A comment on Security and Privacy Implications for Contact APIs noah_mendelsohn@us.ibm.com

Thursday, 28 January 2010

• RE: Past discussions on vCard datamodel for contacts API (ISSUE-71) Suresh Chitturi
• Re: Devices as Virtual Web Services Max Froumentin
• RE: A comment on Security and Privacy Implications for Contact APIs richard.tibbett@orange-ftgroup.com
• Re: [calendar] Editor's Draft of Calendar API Andrew McMillan
• Re: Past discussions on vCard datamodel for contacts API (ISSUE-71) Thomas Roessler
• RE: Past discussions on vCard datamodel for contacts API (ISSUE-71) richard.tibbett@orange-ftgroup.com

Wednesday, 27 January 2010

• Re: A comment on Security and Privacy Implications for Contact APIs Story Henry
• Re: [contacts] PutForwards for complex contact attributes Dominique Hazael-Massieux
• Draft minutes 2010-01-27 Frederick Hirsch
• Re: Devices as Virtual Web Services Mark Baker
• Past discussions on vCard datamodel for contacts API (ISSUE-71) Dominique Hazael-Massieux
• Re: A comment on Security and Privacy Implications for Contact APIs Thomas Roessler
• A comment on Security and Privacy Implications for Contact APIs noah_mendelsohn@us.ibm.com
• Re: Devices as Virtual Web Services Frederick Hirsch
• Re: Devices as Virtual Web Services Robin Berjon
• Re: [calendar] Editor's Draft of Calendar API Thomas Roessler
• Re: Devices as Virtual Web Services Robin Berjon
• Re: Devices as Virtual Web Services Robin Berjon
• RE: Regrets, was: RE: Agenda - Distributed Meeting 2010-01-27 Arribas, Laura, VF-Group
• Re: Devices as Virtual Web Services Robin Berjon
• Re: Publishing System Information API FPWD Max Froumentin
• ISSUE-70 (usecases-in-spec): Should we have use-cases in specifications [APIs — General] Device APIs and Policy Working Group Issue Tracker
• Re: [calendar] Editor's Draft of Calendar API Dominique Hazael-Massieux
• URN UUID on Contacts / Calendar ids Dominique Hazael-Massieux
• Re: Regrets for today's call Marengo Marco
• Regrets for today's call Nilsson, Claes1
• RE: Regrets, was: RE: Agenda - Distributed Meeting 2010-01-27 David Rogers
• Regrets, was: RE: Agenda - Distributed Meeting 2010-01-27 Marcin Hanclik
• RE: Publishing System Information API FPWD Nilsson, Claes1
• Re: Devices as Virtual Web Services Paddy Byers
• RE: ACTION-85: BONDI's investigation into LREST vs "conventional" JavaScript APIs Tran, Dzung D
• Agenda - Distributed Meeting 2010-01-27 Frederick Hirsch
• Regrets for today's call Paddy Byers
• ACTION-85: BONDI's investigation into LREST vs "conventional" JavaScript APIs Paddy Byers

Tuesday, 26 January 2010

• RE: Devices as Virtual Web Services Tran, Dzung D

Monday, 25 January 2010

• Re: Devices as Virtual Web Services Kenton Varda

Saturday, 23 January 2010

• Re: Devices as Virtual Web Services Frederick Hirsch

Friday, 22 January 2010

• [messaging] First Editor's Draft of Messaging API Niklas Widell
• [calendar] Editor's Draft of Calendar API richard.tibbett@orange-ftgroup.com
• Re: Devices as Virtual Web Services Arthur Barstow
• Re: Devices as Virtual Web Services Adam Barth
• Re: Devices as Virtual Web Services Adam Barth
• Re: CfC: Publishing System Information API FPWD Max Froumentin
• Re: "encrypted" attribute (Re: CfC: Publishing System Information API FPWD) Max Froumentin
• Re: CfC: Publishing System Information API FPWD Carlos Cardona

Thursday, 21 January 2010

• Re: CfC: Publishing System Information API FPWD Brian LeRoux
• Contacts API published as FPWD Dominique Hazael-Massieux
• Re: "encrypted" attribute (Re: CfC: Publishing System Information API FPWD) Robin Berjon
• identifying open issues (Re: CfC: Publishing System Information API FPWD) Thomas Roessler
• "encrypted" attribute (Re: CfC: Publishing System Information API FPWD) Thomas Roessler
• CfC: Publishing System Information API FPWD Robin Berjon
• [sysinfo] draft updated Max Froumentin

Wednesday, 20 January 2010

• Re: Devices as Virtual Web Services Max Froumentin
• Draft minutes 2010-01-20 Frederick Hirsch
• Re: Devices as Virtual Web Services Frederick Hirsch
• RE: ACTION-74: Propose options to move forward with Capture Tran, Dzung D
• Devices as Virtual Web Services Robin Berjon
• Regrets John Morris
• Re: Agenda - Distributed Meeting 2010-01-20 Robin Berjon
• Re: Agenda - Distributed Meeting 2010-01-20 Max Froumentin
• Agenda - Distributed Meeting 2010-01-20 Robin Berjon
• ISSUE-69 (inline-css): ReSpec should always have inlineCSS true [ReSpec] Device APIs and Policy Working Group Issue Tracker

Tuesday, 19 January 2010

• RE: [contacts] PutForwards for complex contact attributes Marcin Hanclik
• RE: [contacts] PutForwards for complex contact attributes richard.tibbett@orange-ftgroup.com
• RE: [contacts] PutForwards for complex contact attributes Marcin Hanclik
• RE: [contacts] PutForwards for complex contact attributes richard.tibbett@orange-ftgroup.com

Monday, 18 January 2010

• RE: ISSUE-67: Naming of "device" Marcin Hanclik
• Re: ISSUE-67: Naming of "device" Dion Almaer
• ISSUE-68 (respec-idl-indent): confusing indentation of WebIDL blocks in ReSpec [ReSpec] Device APIs and Policy Working Group Issue Tracker
• RE: ISSUE-67: Naming of "device" Nilsson, Claes1

Friday, 15 January 2010

• Re: ISSUE-67: Naming of "device" John Kemp
• Re: Why aren't most devices virtual web services? Kenton Varda
• Re: ISSUE-67: Naming of "device" Dion Almaer
• RE: ISSUE-67: Naming of "device" Nilsson, Claes1

Thursday, 14 January 2010

• RE: Why aren't most devices virtual web services? Marcin Hanclik
• Re: ISSUE-67: Naming of "device" Suresh Chitturi
• Re: ISSUE-67: Naming of "device" Brian LeRoux
• RE: ISSUE-67: Naming of "device" Marcin Hanclik
• Re: Why aren't most devices virtual web services? Ian Hickson
• Re: ISSUE-67: Naming of "device" Doug Turner
• RE: ISSUE-67: Naming of "device" Marcin Hanclik
• Re: ISSUE-67: Naming of "device" Brian LeRoux
• RE: ISSUE-67: Naming of "device" Marcin Hanclik
• Re: Why aren't most devices virtual web services? Kenton Varda
• Re: Why aren't most devices virtual web services? Ian Hickson
• Re: Why aren't most devices virtual web services? John Kemp
• Re: Why aren't most devices virtual web services? Ian Hickson
• Re: ISSUE-67: Naming of "device" Doug Turner
• RE: ISSUE-67: Naming of "device" richard.tibbett@orange-ftgroup.com
• RE: ISSUE-67: Naming of "device" richard.tibbett@orange-ftgroup.com
• Re: Why aren't most devices virtual web services? John Kemp
• Re: Why aren't most devices virtual web services? Kenton Varda
• Re: ISSUE-67: Naming of "device" Doug Turner
• RE: ISSUE-67: Naming of "device" Suresh Chitturi
• Re: Why aren't most devices virtual web services? John Kemp
• Re: Why aren't most devices virtual web services? Robin Berjon
• Re: ISSUE-67: Naming of "device" Anssi Kostiainen
• Re: ISSUE-67: Naming of "device" Jerry Carter
• Re: ISSUE-67: Naming of "device" Dominique Hazael-Massieux
• Re: ISSUE-67: Naming of "device" Stewart Brodie
• Re: Why aren't most devices virtual web services? Robin Berjon
• Re: ISSUE-67: Naming of "device" Robin Berjon
• Re: ISSUE-67: Naming of "device" John Kemp
• RE: ISSUE-67: Naming of "device" Marcin Hanclik
• ISSUE-67: Naming of "device" Robin Berjon
• Re: Why aren't most devices virtual web services? Ilkka Oksanen
• Re: Why aren't most devices virtual web services? Tyler Close

Wednesday, 13 January 2010

• Re: Why aren't most devices virtual web services? Doug Turner
• Re: Why aren't most devices virtual web services? Frederick Hirsch
• Re: Why aren't most devices virtual web services? Frederick Hirsch
• Re: Why aren't most devices virtual web services? Doug Turner
• Re: Why aren't most devices virtual web services? John Kemp
• Re: Why aren't most devices virtual web services? Doug Turner
• Re: Why aren't most devices virtual web services? Frederick Hirsch
• Re: Why aren't most devices virtual web services? Mark S. Miller
• Draft minutes 2010-01-13 Frederick Hirsch
• Re: Why aren't most devices virtual web services? Frederick Hirsch
• Re: Why aren't most devices virtual web services? Robin Berjon
• Re: Why aren't most devices virtual web services? Frederick Hirsch
• Re: Why aren't most devices virtual web services? John Kemp
• Re: Why aren't most devices virtual web services? Robin Berjon
• Re: Why aren't most devices virtual web services? Frederick Hirsch
• Regrets Arribas, Laura, VF-Group
• Re: Why aren't most devices virtual web services? Robin Berjon
• ACTION-74: Propose options to move forward with Capture Robin Berjon
• RE: Why aren't most devices virtual web services? richard.tibbett@orange-ftgroup.com
• Re: Why aren't most devices virtual web services? Adam Barth
• Regrets John Morris

Tuesday, 12 January 2010

• Agenda - Distributed Meeting 2010-01-13 Frederick Hirsch
• RE: [SysInfo] proposal for ACTION-80 - Write to list on properties to drop or simplify Nilsson, Claes1
• Re: [SysInfo] proposal for ACTION-80 - Write to list on properties to drop or simplify Max Froumentin
• Re: W3C TAG position on policy mechanisms for Web APIs and Services Frederick Hirsch
• RE: [SysInfo] proposal for ACTION-80 - Write to list on properties to drop or simplify Nilsson, Claes1
• RE: ACTION-38: "Should issue recommendation on the granularity of the security system" + proposal for a "Secure Credential API" Nilsson, Claes1
• Re: W3C TAG position on policy mechanisms for Web APIs and Services noah_mendelsohn@us.ibm.com

Monday, 11 January 2010

• Re: Why aren't most devices virtual web services? Kenton Varda
• RE: [Contacts] couple of comments Suresh Chitturi
• RE: [Contacts] couple of comments richard.tibbett@orange-ftgroup.com
• RE: Hanging the APIs off navigator.device richard.tibbett@orange-ftgroup.com
• Re: Why aren't most devices virtual web services? Ilkka Oksanen
• RE: Why aren't most devices virtual web services? richard.tibbett@orange-ftgroup.com

Sunday, 10 January 2010

• Re: <device> proposal (for video conferencing, etc) Dave Burke
• Re: Why aren't most devices virtual web services? Ian Hickson

Saturday, 9 January 2010

• Re: Why aren't most devices virtual web services? Kenton Varda
• Re: Why aren't most devices virtual web services? Doug Turner
• Re: Why aren't most devices virtual web services? Kenton Varda

Friday, 8 January 2010

• Re: Why aren't most devices virtual web services? Ian Hickson
• Re: Why aren't most devices virtual web services? ashok malhotra
• Re: Why aren't most devices virtual web services? Ian Hickson
• Re: Why aren't most devices virtual web services? Ian Hickson
• Re: Why aren't most devices virtual web services? ashok malhotra
• Re: Why aren't most devices virtual web services? Adam Barth
• Re: Why aren't most devices virtual web services? Frederick Hirsch
• Re: W3C TAG position on policy mechanisms for Web APIs and Services Frederick Hirsch
• Re: [Contacts] couple of comments Anssi Kostiainen
• Re: [contacts] Extending the Contacts.create() method Anssi Kostiainen
• Re: Why aren't most devices virtual web services? Anssi Kostiainen
• Re: Why aren't most devices virtual web services? Mark S. Miller
• Re: Why aren't most devices virtual web services? Doug Turner
• Why aren't most devices virtual web services? Mark S. Miller

Thursday, 7 January 2010

• Re: Hanging the APIs off navigator.device Stewart Brodie
• RE: [SysInfo] proposal for ACTION-80 - Write to list on properties to drop or simplify Tran, Dzung D
• RE: Hanging the APIs off navigator.device Tran, Dzung D
• Re: Hanging the APIs off navigator.device Doug Turner
• Re: Hanging the APIs off navigator.device Robin Berjon
• [Contacts] couple of comments Max Froumentin
• RE: Hanging the APIs off navigator.device Tran, Dzung D

Wednesday, 6 January 2010

• Re: Hanging the APIs off navigator.device Brian LeRoux
• Re: Hanging the APIs off navigator.device Anne van Kesteren
• Re: W3C TAG position on policy mechanisms for Web APIs and Services ashok malhotra
• Re: Hanging the APIs off navigator.device Stewart Brodie
• RE: Hanging the APIs off navigator.device Suresh Chitturi
• RE: Publishing Contacts API FPWD Suresh Chitturi
• Re: W3C TAG position on policy mechanisms for Web APIs and Services noah_mendelsohn@us.ibm.com
• [SysInfo] proposal for ACTION-80 - Write to list on properties to drop or simplify Max Froumentin
• Re: Publishing Contacts API FPWD Robin Berjon
• Re: Hanging the APIs off navigator.device Robin Berjon
• RE: Publishing Contacts API FPWD Marcin Hanclik
• Re: CfC: Publishing Contacts API FPWD fabrice.desre@orange-ftgroup.com
• Re: W3C TAG position on policy mechanisms for Web APIs and Services Frederick Hirsch
• RE: Publishing Contacts API FPWD Suresh Chitturi
• Re: CfC: Publishing Contacts API FPWD Robin Berjon
• CfC: Publishing Contacts API FPWD Robin Berjon
• ISSUE-64 (hidingIsHard): "Generic" sensors may permit discovering sensitive information [System Information and Events API] Device APIs and Policy Working Group Issue Tracker
• Draft minutes - 2010-01-06 teleconference Frederick Hirsch
• ISSUE-63 (encryptedIsMagic): network API: "encrypted" property is meaningless [System Information and Events API] Device APIs and Policy Working Group Issue Tracker
• ISSUE-62 (respec-changemarkers): Add change markers to respec [ReSpec] Device APIs and Policy Working Group Issue Tracker
• RE: Agenda - Distributed Meeting 2010-01-06 David Rogers
• RE: CPU API (Re: [sysinfo] draft ready for review) Tran, Dzung D
• ACTION-69: Policy use cases Paddy Byers
• RE: Camera properties (Re: [sysinfo] draft ready for review) David Rogers
• Re: Thermometer API (Re: [sysinfo] draft ready for review) Max Froumentin
• Re: Camera properties (Re: [sysinfo] draft ready for review) Thomas Roessler
• RE: Camera properties (Re: [sysinfo] draft ready for review) David Rogers
• Re: Network API (Re: [sysinfo] draft ready for review) Thomas Roessler
• Re: Camera properties (Re: [sysinfo] draft ready for review) Max Froumentin
• Re: Thermometer API (Re: [sysinfo] draft ready for review) Thomas Roessler
• Re: CPU API (Re: [sysinfo] draft ready for review) Thomas Roessler
• Re: Network API (Re: [sysinfo] draft ready for review) Max Froumentin
• Re: Thermometer API (Re: [sysinfo] draft ready for review) Max Froumentin
• Re: CPU API (Re: [sysinfo] draft ready for review) Max Froumentin
• Re: Power API (Re: [sysinfo] draft ready for review) Max Froumentin
• RE: Ambient Light (Re: [sysinfo] draft ready for review) Tran, Dzung D
• RE: Power API (Re: [sysinfo] draft ready for review) Tran, Dzung D
• RE: CPU API (Re: [sysinfo] draft ready for review) Tran, Dzung D

Tuesday, 5 January 2010

• Re: Camera properties (Re: [sysinfo] draft ready for review) Doug Turner
• Re: Power API (Re: [sysinfo] draft ready for review) Anne van Kesteren
• Re: Power API (Re: [sysinfo] draft ready for review) Max Froumentin
• Camera properties (Re: [sysinfo] draft ready for review) Thomas Roessler
• Video and Audio codecs (Re: [sysinfo] draft ready for review) Thomas Roessler
• Ambient Light (Re: [sysinfo] draft ready for review) Thomas Roessler
• Network API (Re: [sysinfo] draft ready for review) Thomas Roessler
• Thermometer API (Re: [sysinfo] draft ready for review) Thomas Roessler
• CPU API (Re: [sysinfo] draft ready for review) Thomas Roessler
• Power API (Re: [sysinfo] draft ready for review) Thomas Roessler
• Re: [sysinfo] draft ready for review Max Froumentin

Monday, 4 January 2010

• RE: <device> proposal (for video conferencing, etc) Ian Hickson
• Re: [sysinfo] draft ready for review Doug Turner
• RE: <device> proposal (for video conferencing, etc) David Rogers
• Regrets Marengo Marco
• Re: W3C TAG position on policy mechanisms for Web APIs and Services Dominique Hazael-Massieux

Last message date: Sunday, 31 January 2010 10:00:56 UTC