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

Adam Barth

• Re: Devices as Virtual Web Services (Friday, 22 January)
• Re: Devices as Virtual Web Services (Friday, 22 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• Re: Why aren't most devices virtual web services? (Friday, 8 January)

Andrew McMillan

• Re: [calendar] Editor's Draft of Calendar API (Thursday, 28 January)

Anne van Kesteren

• Re: New filesystem/directory API proposal (Saturday, 30 January)
• Re: New filesystem/directory API proposal (Saturday, 30 January)
• Re: Hanging the APIs off navigator.device (Wednesday, 6 January)
• Re: Power API (Re: [sysinfo] draft ready for review) (Tuesday, 5 January)

Anssi Kostiainen

• Re: ISSUE-67: Naming of "device" (Thursday, 14 January)
• Re: [Contacts] couple of comments (Friday, 8 January)
• Re: [contacts] Extending the Contacts.create() method (Friday, 8 January)
• Re: Why aren't most devices virtual web services? (Friday, 8 January)

Arribas, Laura, VF-Group

• RE: Regrets, was: RE: Agenda - Distributed Meeting 2010-01-27 (Wednesday, 27 January)
• Regrets (Wednesday, 13 January)

Arthur Barstow

• Re: Devices as Virtual Web Services (Friday, 22 January)

Arve Bersvendsen

• Re: New filesystem/directory API proposal (Saturday, 30 January)
• Re: New filesystem/directory API proposal (Friday, 29 January)
• Re: New filesystem/directory API proposal (Friday, 29 January)
• Re: New filesystem/directory API proposal (Friday, 29 January)

ashok malhotra

• Re: Why aren't most devices virtual web services? (Friday, 8 January)
• Re: Why aren't most devices virtual web services? (Friday, 8 January)
• Re: W3C TAG position on policy mechanisms for Web APIs and Services (Wednesday, 6 January)

Brian LeRoux

• Re: CfC: Publishing System Information API FPWD (Thursday, 21 January)
• Re: ISSUE-67: Naming of "device" (Thursday, 14 January)
• Re: ISSUE-67: Naming of "device" (Thursday, 14 January)
• Re: Hanging the APIs off navigator.device (Wednesday, 6 January)

Carlos Cardona

• Re: CfC: Publishing System Information API FPWD (Friday, 22 January)

Dave Burke

• Re: <device> proposal (for video conferencing, etc) (Sunday, 10 January)

David Rogers

• RE: Regrets, was: RE: Agenda - Distributed Meeting 2010-01-27 (Wednesday, 27 January)
• RE: Agenda - Distributed Meeting 2010-01-06 (Wednesday, 6 January)
• RE: Camera properties (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• RE: Camera properties (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• RE: <device> proposal (for video conferencing, etc) (Monday, 4 January)

Device APIs and Policy Working Group Issue Tracker

• ISSUE-70 (usecases-in-spec): Should we have use-cases in specifications [APIs â?? General] (Wednesday, 27 January)
• ISSUE-69 (inline-css): ReSpec should always have inlineCSS true [ReSpec] (Wednesday, 20 January)
• ISSUE-68 (respec-idl-indent): confusing indentation of WebIDL blocks in ReSpec [ReSpec] (Monday, 18 January)
• ISSUE-64 (hidingIsHard): "Generic" sensors may permit discovering sensitive information [System Information and Events API] (Wednesday, 6 January)
• ISSUE-63 (encryptedIsMagic): network API: "encrypted" property is meaningless [System Information and Events API] (Wednesday, 6 January)
• ISSUE-62 (respec-changemarkers): Add change markers to respec [ReSpec] (Wednesday, 6 January)

Dion Almaer

• Re: ISSUE-67: Naming of "device" (Monday, 18 January)
• Re: ISSUE-67: Naming of "device" (Friday, 15 January)

Dominique Hazael-Massieux

• Re: [contacts] PutForwards for complex contact attributes (Wednesday, 27 January)
• Past discussions on vCard datamodel for contacts API (ISSUE-71) (Wednesday, 27 January)
• Re: [calendar] Editor's Draft of Calendar API (Wednesday, 27 January)
• URN UUID on Contacts / Calendar ids (Wednesday, 27 January)
• Contacts API published as FPWD (Thursday, 21 January)
• Re: ISSUE-67: Naming of "device" (Thursday, 14 January)
• Re: W3C TAG position on policy mechanisms for Web APIs and Services (Monday, 4 January)

Doug Turner

• Re: ISSUE-67: Naming of "device" (Thursday, 14 January)
• Re: ISSUE-67: Naming of "device" (Thursday, 14 January)
• Re: ISSUE-67: Naming of "device" (Thursday, 14 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• Re: Why aren't most devices virtual web services? (Saturday, 9 January)
• Re: Why aren't most devices virtual web services? (Friday, 8 January)
• Re: Hanging the APIs off navigator.device (Thursday, 7 January)
• Re: Camera properties (Re: [sysinfo] draft ready for review) (Tuesday, 5 January)
• Re: [sysinfo] draft ready for review (Monday, 4 January)

Eric Uhrhane

• Re: New filesystem/directory API proposal (Friday, 29 January)
• Re: New filesystem/directory API proposal (Friday, 29 January)
• New filesystem/directory API proposal (Friday, 29 January)
• New FileWriter proposal (Friday, 29 January)

fabrice.desre@orange-ftgroup.com

• Re: CfC: Publishing Contacts API FPWD (Wednesday, 6 January)

Frederick Hirsch

• Draft minutes 2010-01-27 (Wednesday, 27 January)
• Re: Devices as Virtual Web Services (Wednesday, 27 January)
• Agenda - Distributed Meeting 2010-01-27 (Wednesday, 27 January)
• Re: Devices as Virtual Web Services (Saturday, 23 January)
• Draft minutes 2010-01-20 (Wednesday, 20 January)
• Re: Devices as Virtual Web Services (Wednesday, 20 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• Draft minutes 2010-01-13 (Wednesday, 13 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• Agenda - Distributed Meeting 2010-01-13 (Tuesday, 12 January)
• Re: W3C TAG position on policy mechanisms for Web APIs and Services (Tuesday, 12 January)
• Re: Why aren't most devices virtual web services? (Friday, 8 January)
• Re: W3C TAG position on policy mechanisms for Web APIs and Services (Friday, 8 January)
• Re: W3C TAG position on policy mechanisms for Web APIs and Services (Wednesday, 6 January)
• Draft minutes - 2010-01-06 teleconference (Wednesday, 6 January)

Ian Hickson

• Re: Why aren't most devices virtual web services? (Thursday, 14 January)
• Re: Why aren't most devices virtual web services? (Thursday, 14 January)
• Re: Why aren't most devices virtual web services? (Thursday, 14 January)
• Re: Why aren't most devices virtual web services? (Sunday, 10 January)
• Re: Why aren't most devices virtual web services? (Friday, 8 January)
• Re: Why aren't most devices virtual web services? (Friday, 8 January)
• Re: Why aren't most devices virtual web services? (Friday, 8 January)
• RE: <device> proposal (for video conferencing, etc) (Monday, 4 January)

Ilkka Oksanen

• Re: Why aren't most devices virtual web services? (Thursday, 14 January)
• Re: Why aren't most devices virtual web services? (Monday, 11 January)

Jerry Carter

• Re: ISSUE-67: Naming of "device" (Thursday, 14 January)

John Kemp

• Re: ISSUE-67: Naming of "device" (Friday, 15 January)
• Re: Why aren't most devices virtual web services? (Thursday, 14 January)
• Re: Why aren't most devices virtual web services? (Thursday, 14 January)
• Re: Why aren't most devices virtual web services? (Thursday, 14 January)
• Re: ISSUE-67: Naming of "device" (Thursday, 14 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)

John Morris

• Regrets (Wednesday, 20 January)
• Regrets (Wednesday, 13 January)

Kenton Varda

• Re: Devices as Virtual Web Services (Monday, 25 January)
• Re: Why aren't most devices virtual web services? (Friday, 15 January)
• Re: Why aren't most devices virtual web services? (Thursday, 14 January)
• Re: Why aren't most devices virtual web services? (Thursday, 14 January)
• Re: Why aren't most devices virtual web services? (Monday, 11 January)
• Re: Why aren't most devices virtual web services? (Saturday, 9 January)
• Re: Why aren't most devices virtual web services? (Saturday, 9 January)

Marcin Hanclik

• Regrets, was: RE: Agenda - Distributed Meeting 2010-01-27 (Wednesday, 27 January)
• RE: [contacts] PutForwards for complex contact attributes (Tuesday, 19 January)
• RE: [contacts] PutForwards for complex contact attributes (Tuesday, 19 January)
• RE: ISSUE-67: Naming of "device" (Monday, 18 January)
• RE: Why aren't most devices virtual web services? (Thursday, 14 January)
• RE: ISSUE-67: Naming of "device" (Thursday, 14 January)
• RE: ISSUE-67: Naming of "device" (Thursday, 14 January)
• RE: ISSUE-67: Naming of "device" (Thursday, 14 January)
• RE: ISSUE-67: Naming of "device" (Thursday, 14 January)
• RE: Publishing Contacts API FPWD (Wednesday, 6 January)

Marengo Marco

• Re: Regrets for today's call (Wednesday, 27 January)
• Regrets (Monday, 4 January)

Mark Baker

• Re: Devices as Virtual Web Services (Wednesday, 27 January)

Mark S. Miller

• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• Re: Why aren't most devices virtual web services? (Friday, 8 January)
• Why aren't most devices virtual web services? (Friday, 8 January)

Max Froumentin

• Re: Devices as Virtual Web Services (Thursday, 28 January)
• Re: Publishing System Information API FPWD (Wednesday, 27 January)
• Re: CfC: Publishing System Information API FPWD (Friday, 22 January)
• Re: "encrypted" attribute (Re: CfC: Publishing System Information API FPWD) (Friday, 22 January)
• [sysinfo] draft updated (Thursday, 21 January)
• Re: Devices as Virtual Web Services (Wednesday, 20 January)
• Re: Agenda - Distributed Meeting 2010-01-20 (Wednesday, 20 January)
• Re: [SysInfo] proposal for ACTION-80 - Write to list on properties to drop or simplify (Tuesday, 12 January)
• [Contacts] couple of comments (Thursday, 7 January)
• [SysInfo] proposal for ACTION-80 - Write to list on properties to drop or simplify (Wednesday, 6 January)
• Re: Thermometer API (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• Re: Camera properties (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• Re: Network API (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• Re: Thermometer API (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• Re: CPU API (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• Re: Power API (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• Re: Power API (Re: [sysinfo] draft ready for review) (Tuesday, 5 January)
• Re: [sysinfo] draft ready for review (Tuesday, 5 January)

Niklas Widell

• [messaging] First Editor's Draft of Messaging API (Friday, 22 January)

Nilsson, Claes1

• RE: [sysinfo] SEMC comments (was RE: Publishing System Information API FPWD) (Friday, 29 January)
• [sysinfo] SEMC comments (was RE: Publishing System Information API FPWD) (Friday, 29 January)
• Regrets for today's call (Wednesday, 27 January)
• RE: Publishing System Information API FPWD (Wednesday, 27 January)
• RE: ISSUE-67: Naming of "device" (Monday, 18 January)
• RE: ISSUE-67: Naming of "device" (Friday, 15 January)
• RE: [SysInfo] proposal for ACTION-80 - Write to list on properties to drop or simplify (Tuesday, 12 January)
• RE: [SysInfo] proposal for ACTION-80 - Write to list on properties to drop or simplify (Tuesday, 12 January)
• RE: ACTION-38: "Should issue recommendation on the granularity of the security system" + proposal for a "Secure Credential API" (Tuesday, 12 January)

noah_mendelsohn@us.ibm.com

• RE: A comment on Security and Privacy Implications for Contact APIs (Friday, 29 January)
• A comment on Security and Privacy Implications for Contact APIs (Wednesday, 27 January)
• Re: W3C TAG position on policy mechanisms for Web APIs and Services (Tuesday, 12 January)
• Re: W3C TAG position on policy mechanisms for Web APIs and Services (Wednesday, 6 January)

Paddy Byers

• Re: Devices as Virtual Web Services (Wednesday, 27 January)
• Regrets for today's call (Wednesday, 27 January)
• ACTION-85: BONDI's investigation into LREST vs "conventional" JavaScript APIs (Wednesday, 27 January)
• ACTION-69: Policy use cases (Wednesday, 6 January)

richard.tibbett@orange-ftgroup.com

• RE: A comment on Security and Privacy Implications for Contact APIs (Thursday, 28 January)
• RE: Past discussions on vCard datamodel for contacts API (ISSUE-71) (Thursday, 28 January)
• [calendar] Editor's Draft of Calendar API (Friday, 22 January)
• RE: [contacts] PutForwards for complex contact attributes (Tuesday, 19 January)
• RE: [contacts] PutForwards for complex contact attributes (Tuesday, 19 January)
• RE: ISSUE-67: Naming of "device" (Thursday, 14 January)
• RE: ISSUE-67: Naming of "device" (Thursday, 14 January)
• RE: Why aren't most devices virtual web services? (Wednesday, 13 January)
• RE: [Contacts] couple of comments (Monday, 11 January)
• RE: Hanging the APIs off navigator.device (Monday, 11 January)
• RE: Why aren't most devices virtual web services? (Monday, 11 January)

Robin Berjon

• Re: Devices as Virtual Web Services (Wednesday, 27 January)
• Re: Devices as Virtual Web Services (Wednesday, 27 January)
• Re: Devices as Virtual Web Services (Wednesday, 27 January)
• Re: Devices as Virtual Web Services (Wednesday, 27 January)
• Re: "encrypted" attribute (Re: CfC: Publishing System Information API FPWD) (Thursday, 21 January)
• CfC: Publishing System Information API FPWD (Thursday, 21 January)
• Devices as Virtual Web Services (Wednesday, 20 January)
• Re: Agenda - Distributed Meeting 2010-01-20 (Wednesday, 20 January)
• Agenda - Distributed Meeting 2010-01-20 (Wednesday, 20 January)
• Re: Why aren't most devices virtual web services? (Thursday, 14 January)
• Re: Why aren't most devices virtual web services? (Thursday, 14 January)
• Re: ISSUE-67: Naming of "device" (Thursday, 14 January)
• ISSUE-67: Naming of "device" (Thursday, 14 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• Re: Why aren't most devices virtual web services? (Wednesday, 13 January)
• ACTION-74: Propose options to move forward with Capture (Wednesday, 13 January)
• Re: Hanging the APIs off navigator.device (Thursday, 7 January)
• Re: Publishing Contacts API FPWD (Wednesday, 6 January)
• Re: Hanging the APIs off navigator.device (Wednesday, 6 January)
• Re: CfC: Publishing Contacts API FPWD (Wednesday, 6 January)
• CfC: Publishing Contacts API FPWD (Wednesday, 6 January)

Stewart Brodie

• Re: ISSUE-67: Naming of "device" (Thursday, 14 January)
• Re: Hanging the APIs off navigator.device (Thursday, 7 January)
• Re: Hanging the APIs off navigator.device (Wednesday, 6 January)

Story Henry

• Re: A comment on Security and Privacy Implications for Contact APIs (Wednesday, 27 January)

Suresh Chitturi

• Re: Past discussions on vCard datamodel for contacts API (ISSUE-71) (Sunday, 31 January)
• RE: Past discussions on vCard datamodel for contacts API (ISSUE-71) (Thursday, 28 January)
• Re: ISSUE-67: Naming of "device" (Thursday, 14 January)
• RE: ISSUE-67: Naming of "device" (Thursday, 14 January)
• RE: [Contacts] couple of comments (Monday, 11 January)
• RE: Hanging the APIs off navigator.device (Wednesday, 6 January)
• RE: Publishing Contacts API FPWD (Wednesday, 6 January)
• RE: Publishing Contacts API FPWD (Wednesday, 6 January)

Thomas Roessler

• Re: Publishing System Information API FPWD (Friday, 29 January)
• Re: [sysinfo] SEMC comments (was RE: Publishing System Information API FPWD) (Friday, 29 January)
• Re: Past discussions on vCard datamodel for contacts API (ISSUE-71) (Friday, 29 January)
• Re: Past discussions on vCard datamodel for contacts API (ISSUE-71) (Thursday, 28 January)
• Re: A comment on Security and Privacy Implications for Contact APIs (Wednesday, 27 January)
• Re: [calendar] Editor's Draft of Calendar API (Wednesday, 27 January)
• identifying open issues (Re: CfC: Publishing System Information API FPWD) (Thursday, 21 January)
• "encrypted" attribute (Re: CfC: Publishing System Information API FPWD) (Thursday, 21 January)
• Re: Camera properties (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• Re: Network API (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• Re: Thermometer API (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• Re: CPU API (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• Camera properties (Re: [sysinfo] draft ready for review) (Tuesday, 5 January)
• Video and Audio codecs (Re: [sysinfo] draft ready for review) (Tuesday, 5 January)
• Ambient Light (Re: [sysinfo] draft ready for review) (Tuesday, 5 January)
• Network API (Re: [sysinfo] draft ready for review) (Tuesday, 5 January)
• Thermometer API (Re: [sysinfo] draft ready for review) (Tuesday, 5 January)
• CPU API (Re: [sysinfo] draft ready for review) (Tuesday, 5 January)
• Power API (Re: [sysinfo] draft ready for review) (Tuesday, 5 January)

Tran, Dzung D

• RE: Publishing System Information API FPWD (Friday, 29 January)
• RE: ACTION-85: BONDI's investigation into LREST vs "conventional" JavaScript APIs (Wednesday, 27 January)
• RE: Devices as Virtual Web Services (Tuesday, 26 January)
• RE: ACTION-74: Propose options to move forward with Capture (Wednesday, 20 January)
• RE: [SysInfo] proposal for ACTION-80 - Write to list on properties to drop or simplify (Thursday, 7 January)
• RE: Hanging the APIs off navigator.device (Thursday, 7 January)
• RE: Hanging the APIs off navigator.device (Thursday, 7 January)
• RE: CPU API (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• RE: Ambient Light (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• RE: Power API (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)
• RE: CPU API (Re: [sysinfo] draft ready for review) (Wednesday, 6 January)

Tyler Close

• Re: Why aren't most devices virtual web services? (Thursday, 14 January)

イアンフェッティ

• Re: New filesystem/directory API proposal (Saturday, 30 January)

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