public-device-apis@w3.org from November 2009 by date

Monday, 30 November 2009

• Re: [contacts] Comments on editors draft of Contacts API Brian LeRoux
• ACTION-68 - details please! Robin Berjon
• Re: [contacts] Comments on editors draft of Contacts API Robin Berjon
• Re: [contacts] Comments on editors draft of Contacts API Robin Berjon
• Re: Schedule and criteria for FPWD of Contacts API Robin Berjon
• Re: Schedule and criteria for FPWD of Contacts API Robin Berjon
• Re: Schedule and criteria for FPWD of Contacts API Robin Berjon
• [contacts] Contacts API Update richard.tibbett@orange-ftgroup.com
• RE: [contacts] Comments on editors draft of Contacts API richard.tibbett@orange-ftgroup.com
• Re: [SysInfo] Wiki Page and a proposal for the API structure Robin Berjon
• Re: ISSUE-47 (respec-opera): Opera doesn't render ReSpected issues [APIs — General] Robin Berjon
• Re: ISSUE-46 (respec-opera): Opera doesn't render ReSpected issues [APIs — General] Robin Berjon
• Re: ISSUE-45 (ReSpec-ToC-depth): Respec: customize table of content depth [APIs — General] Robin Berjon
• RE: Schedule and criteria for FPWD of Contacts API Suresh Chitturi
• Re: [contacts] Comments on editors draft of Contacts API Brian LeRoux
• Re: [SysInfo] Wiki Page and a proposal for the API structure Max Froumentin
• RE: Schedule and criteria for FPWD of Contacts API richard.tibbett@orange-ftgroup.com
• [contacts] Comments on editors draft of Contacts API Dominique Hazael-Massieux
• Schedule and criteria for FPWD of Contacts API Dominique Hazael-Massieux

Friday, 27 November 2009

• RE: [SysInfo] Wiki Page and a proposal for the API structure JOSE MANUEL CANTERA FONSECA

Thursday, 26 November 2009

• [SysInfo] Wiki Page and a proposal for the API structure Max Froumentin

Wednesday, 25 November 2009

• ISSUE-47 (respec-opera): Opera doesn't render ReSpected issues [APIs — General] Device APIs and Policy Working Group Issue Tracker

Tuesday, 24 November 2009

• ISSUE-46 (respec-opera): Opera doesn't render ReSpected issues [APIs — General] Device APIs and Policy Working Group Issue Tracker
• Re: Camera/Caputre API (was: DAP Roadmap, priorities) Andrei Popescu
• ISSUE-45 (ReSpec-ToC-depth): Respec: customize table of content depth [APIs — General] Device APIs and Policy Working Group Issue Tracker
• Re: Camera/Caputre API (was: DAP Roadmap, priorities) Ian Hickson

Sunday, 22 November 2009

• RE: File writing ponderings (was: Re: Security evaluation of an example DAP policy) Marcin Hanclik

Saturday, 21 November 2009

• Re: File writing ponderings (was: Re: Security evaluation of an example DAP policy) Aaron Boodman
• File writing ponderings (was: Re: Security evaluation of an example DAP policy) Jonas Sicking
• Re: Security evaluation of an example DAP policy Jonas Sicking

Friday, 20 November 2009

• RE: Security evaluation of an example DAP policy Marcin Hanclik
• RE: Security evaluation of an example DAP policy richard.tibbett@orange-ftgroup.com
• Re: Security evaluation of an example DAP policy Robin Berjon
• RE: Camera API requirements Tran, Dzung D
• Re: Security evaluation of an example DAP policy Adam Barth
• Re: Security evaluation of an example DAP policy Robin Berjon
• Re: Security evaluation of an example DAP policy Robin Berjon
• Camera API requirements Nick Lothian
• RE: Security evaluation of an example DAP policy Marcin Hanclik
• Re: Security evaluation of an example DAP policy Frederick Hirsch
• RE: Security evaluation of an example DAP policy Marcin Hanclik
• Re: Security evaluation of an example DAP policy Jeremy Orlow
• Re: Security evaluation of an example DAP policy Frederick Hirsch
• Re: Security evaluation of an example DAP policy Jeremy Orlow
• Re: Security evaluation of an example DAP policy Frederick Hirsch
• RE: Security evaluation of an example DAP policy Marcin Hanclik
• Re: Security evaluation of an example DAP policy Jonas Sicking
• RE: Security evaluation of an example DAP policy Marcin Hanclik
• Re: Security evaluation of an example DAP policy Maciej Stachowiak
• Re: Security evaluation of an example DAP policy Maciej Stachowiak
• Re: Security evaluation of an example DAP policy Jonas Sicking
• RE: Security evaluation of an example DAP policy Marcin Hanclik
• RE: Security evaluation of an example DAP policy Marcin Hanclik

Thursday, 19 November 2009

• Security evaluation of an example DAP policy Adam Barth
• RE: Trying to summarise (was Re: DAP and security) Marcin Hanclik
• RE: Trying to summarise (was Re: DAP and security) Marcin Hanclik
• RE: Trying to summarise (was Re: DAP and security) Marcin Hanclik
• Re: Trying to summarise (was Re: DAP and security) Maciej Stachowiak
• RE: Trying to summarise (was Re: DAP and security) Marcin Hanclik
• Re: Trying to summarise (was Re: DAP and security) Adam Barth
• Re: DAP and security (was: Rename "File API" to "FileReader API"?) Adam Barth
• Re: DAP and security (was: Rename "File API" to "FileReader API"?) Adam Barth
• Re: Trying to summarise (was Re: DAP and security) Robin Berjon
• RE: Draft minutes 2009-11-18 teleconference Dominique Hazael-Massieux
• RE: Draft minutes 2009-11-18 teleconference Nilsson, Claes1
• Re: Trying to summarise (was Re: DAP and security) Jeremy Orlow
• Trying to summarise (was Re: DAP and security) Robin Berjon
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) David Rogers
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) David Rogers
• Re: DAP and security (was: Rename "File API" to "FileReader API"?) Robert O'Callahan
• Re: [FileReader API, ProgressEvents] Design patterns, FileWriter API Robin Berjon
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) David Rogers
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) David Rogers
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) David Rogers
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) David Rogers
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) David Rogers
• RE: [FileReader API, ProgressEvents] Design patterns, FileWriter API Marcin Hanclik
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) Marcin Hanclik
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) Marcin Hanclik
• Re: DAP and security (was: Rename "File API" to "FileReader API"?) Jonas Sicking
• Re: DAP and security (was: Rename "File API" to "FileReader API"?) Robert O'Callahan
• Re: APIs Design patterns Robin Berjon
• Re: DAP and security (was: Rename "File API" to "FileReader API"?) Dominique Hazael-Massieux
• Re: DAP and security (was: Rename "File API" to "FileReader API"?) Robert O'Callahan
• First brick in Policy Framework: Features and Capabilites? Dominique Hazael-Massieux
• RE: APIs Design patterns Marcin Hanclik
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) Marcin Hanclik
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) Marcin Hanclik
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) Marcin Hanclik
• Re: [Device APIs Requirements] Input to Applauncher API Dominique Hazael-Massieux
• Re: APIs Design patterns Dominique Hazael-Massieux
• Re: [Device APIs Requirements] Input to Gallery API Dominique Hazael-Massieux
• Re: [Device APIs Requirements] Input to System Information & Events API Dominique Hazael-Massieux
• APIs Design patterns Dominique Hazael-Massieux
• Re: DAP and security (was: Rename "File API" to "FileReader API"?) Adam Barth
• Re: DAP and security (was: Rename "File API" to "FileReader API"?) Maciej Stachowiak
• Re: DAP and security (was: Rename "File API" to "FileReader API"?) Frederick Hirsch
• Re: [FileReader API, ProgressEvents] Design patterns, FileWriter API Charles McCathieNevile

Wednesday, 18 November 2009

• Re: [FileReader API, ProgressEvents] Design patterns, FileWriter API Arun Ranganathan
• Re: DAP and security (was: Rename "File API" to "FileReader API"?) Jonas Sicking
• Prague F2F 16-18/03 is confirmed Robin Berjon
• RE: DAP Roadmap, priorities 이원석
• ACTION-55 Extract prioritary APIS and put on the group home page Robin Berjon
• ACTION-26 Review MWABP Robin Berjon
• ACTION-56 Create a wiki page for future work on APIs Robin Berjon
• Draft minutes 2009-11-18 teleconference Frederick Hirsch
• RE: Status of DAP Requirements SULLIVAN, BRYAN L (ATTCINW)
• Call cancelled next week (2009-11-25) Robin Berjon
• RE: ACTION-52 Look at markup options for expressing implicit user consent SULLIVAN, BRYAN L (ATTCINW)
• Re: Agenda - Distributed Meeting 2009-11-17 Paddy Byers
• Status of DAP Requirements SULLIVAN, BRYAN L (ATTCINW)
• Re: DAP Roadmap, priorities Frederick Hirsch
• Re: updated home page Frederick Hirsch
• Re: ACTION-52 Look at markup options for expressing implicit user consent Frederick Hirsch
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) SULLIVAN, BRYAN L (ATTCINW)
• Re: Policy and browsers (was Re: Policy work items - request for proposals) Robin Berjon
• Re: DAP Roadmap, priorities Frederick Hirsch
• Re: updated home page Robin Berjon
• Re: DAP Roadmap, priorities Robin Berjon
• Re: updated home page Suresh Chitturi
• Re: DAP Roadmap, priorities Robin Berjon
• Re: Camera/Caputre API (was: DAP Roadmap, priorities) Robin Berjon
• updated home page Frederick Hirsch
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) Marcin Hanclik
• RE: ACTION-52 Look at markup options for expressing implicit user consent SULLIVAN, BRYAN L (ATTCINW)
• ACTION - 47 Provide input on trust model and access control model definitions Arribas, Laura, VF-Group
• Re: DAP Roadmap, priorities Robin Berjon
• Re: ACTION-52 Look at markup options for expressing implicit user consent Robin Berjon
• RE: DAP and security (was: Rename "File API" to "FileReader API"?) David Rogers
• RE: [FileReader API, ProgressEvents] Design patterns, FileWriter API Marcin Hanclik
• Re: DAP and security (was: Rename “File API” to “FileReader API”?) Maciej Stachowiak
• RE: DAP and security (was: Rename “File API” to “FileReader API”?) Marcin Hanclik
• Re: DAP and security (was: Rename “File API” to “FileReader API”?) Marcos Caceres
• Re: [FileReader API, ProgressEvents] Design patterns, FileWriter API Robin Berjon
• Re: Rename “File API” to “FileReader API”? Robin Berjon
• Re: [FileReader API, ProgressEvents] Design patterns, FileWriter API Anne van Kesteren
• Re: [FileReader API, ProgressEvents] Design patterns, FileWriter API Arun Ranganathan

Tuesday, 17 November 2009

• Agenda - Distributed Meeting 2009-11-17 Frederick Hirsch
• ACTION-52 Look at markup options for expressing implicit user consent Max Froumentin
• [FileReader API, ProgressEvents] Design patterns, FileWriter API Marcin Hanclik

Friday, 13 November 2009

• Re: Camera/Capture API Dominique Hazael-Massieux
• Re: Camera/Caputre API Max Froumentin
• RE: DAP Roadmap, priorities Nilsson, Claes1
• Work on Read before/separtely from Write? (was: Rename “File API” to “FileReader API”?) Dominique Hazael-Massieux
• Re: Rename “File API” to “FileReader API”? Arun Ranganathan
• RE: DAP Roadmap, priorities David Rogers

Thursday, 12 November 2009

• Re: ISSUE-8: Requirements for [Camera/Caputre API] Philip Gladstone
• RE: DAP Roadmap, priorities Dominique Hazael-Massieux
• RE: DAP Roadmap, priorities David Rogers
• RE: DAP Roadmap, priorities Tran, Dzung D
• RE: Camera/Caputre API (was: DAP Roadmap, priorities) Tran, Dzung D
• Re: ISSUE-8: Requirements for [Camera/Caputre API] (was: Updated requirements document) Ingmar.Kliche@telekom.de
• RE: DAP Roadmap, priorities Nilsson, Claes1
• RE: DAP Roadmap, priorities Niklas Widell
• Camera/Caputre API (was: DAP Roadmap, priorities) Dominique Hazael-Massieux
• Re: Use Cases and Requirements for Saving Files Securely Charles McCathieNevile
• Summary of Media Annotations WG 5th F2F in Santa Clara Joakim Söderberg
• Re: Use Cases and Requirements for Saving Files Securely Jonas Sicking
• Re: Use Cases and Requirements for Saving Files Securely イアンフェッティ
• Re: Use Cases and Requirements for Saving Files Securely Adam Barth
• Re: Use Cases and Requirements for Saving Files Securely Arve Bersvendsen
• Re: Use Cases and Requirements for Saving Files Securely Jonas Sicking
• Re: ISSUE-44 (apiHanging): What do APIs hang off of? [APIs â General] イアンフェッティ
• Re: Use Cases and Requirements for Saving Files Securely イアンフェッティ
• Re: Use Cases and Requirements for Saving Files Securely Jonas Sicking
• DAP and security (was: Rename “File API” to “FileReader API”?) Dominique Hazael-Massieux
• Re: What does it all hang off of? Dominique Hazael-Massieux
• ISSUE-44 (apiHanging): What do APIs hang off of? [APIs — General] Device APIs and Policy Working Group Issue Tracker
• RE: Contacts API: vCard vs. PoCo Andrew McMillan
• Re: Rename “File API” to “FileReader API”? Eric Uhrhane
• Re: Use Cases and Requirements for Saving Files Securely Eric Uhrhane
• Re: Rename “File API” to “FileReader API”? Maciej Stachowiak
• Re: Use Cases and Requirements for Saving Files Securely Maciej Stachowiak

Wednesday, 11 November 2009

• Re: Rename “File API” to “FileReader API”? Eric Uhrhane
• Re: Use Cases and Requirements for Saving Files Securely Eric Uhrhane
• Re: Policy and browsers (was Re: Policy work items - request for proposals) Doug Turner
• Re: Policy and browsers (was Re: Policy work items - request for proposals) Doug Turner
• Re: Policy and browsers (was Re: Policy work items - request for proposals) Andrei Popescu
• RE: DAP Roadmap, priorities Tran, Dzung D
• RE: Contacts API: vCard vs. PoCo richard.tibbett@orange-ftgroup.com
• RE: Contacts API: vCard vs. PoCo richard.tibbett@orange-ftgroup.com
• RE: Contacts API: vCard vs. PoCo richard.tibbett@orange-ftgroup.com
• Re: Rename “File API” to “FileReader API”? Frederick Hirsch
• RE: DAP Roadmap, priorities Ingmar.Kliche@telekom.de
• RE: Use Cases and Requirements for Saving Files Securely paul.downey@bt.com
• Re: Policy and browsers (was Re: Policy work items - request for proposals) イアンフェッティ
• Re: Use Cases and Requirements for Saving Files Securely Maciej Stachowiak
• Re: Rename “File API” to “FileReader API”? Maciej Stachowiak
• Re: Rename “File API” to “FileReader API”? Arve Bersvendsen
• Re: Use Cases and Requirements for Saving Files Securely Arve Bersvendsen
• Re: Policy and browsers (was Re: Policy work items - request for proposals) イアンフェッティ
• Re: Use Cases and Requirements for Saving Files Securely Charles McCathieNevile
• Re: Use Cases and Requirements for Saving Files Securely Charles McCathieNevile
• Re: Use Cases and Requirements for Saving Files Securely Jonas Sicking
• Re: Policy and browsers (was Re: Policy work items - request for proposals) イアンフェッティ
• RE: Contacts API: vCard vs. PoCo Andrew McMillan
• RE: DAP Roadmap, priorities 이원석
• Re: Use Cases and Requirements for Saving Files Securely Maciej Stachowiak
• RE: Contacts API: vCard vs. PoCo 이강찬
• Re: Rename “File API” to “FileReader API”? Maciej Stachowiak
• RE: Policy and browsers (was Re: Policy work items - request for proposals) DANIEL JESUS COLOMA BAIGES
• RE: DAP Roadmap, priorities 전종홍
• RE: DAP Roadmap, priorities DANIEL JESUS COLOMA BAIGES

Tuesday, 10 November 2009

• Re: Use Cases and Requirements for Saving Files Securely Ian Hickson
• Re: Rename “File API” to “FileReader API”? Ian Hickson
• RE: DAP Roadmap, priorities Suresh Chitturi
• RE: Contacts API: vCard vs. PoCo Suresh Chitturi
• RE: DAP Roadmap, priorities richard.tibbett@orange-ftgroup.com
• Contacts API: vCard vs. PoCo richard.tibbett@orange-ftgroup.com
• Updated Policy Requirements Editors Draft Frederick Hirsch
• Re: Geolocation WG taking up work on Orientation/Acceleration Christian Timmerer (ITEC)
• Re: Use Cases and Requirements for Saving Files Securely Dominique Hazael-Massieux
• RE: DAP Roadmap, priorities Tran, Dzung D
• Re: Rename “File API” to “FileReader API”? Robin Berjon
• Re: Rename “File API” to “FileReader API”? Dominique Hazael-Massieux
• DAP Roadmap, priorities Dominique Hazael-Massieux
• Re: Rename “File API” to “FileReader API”? Maciej Stachowiak
• Re: Rename “File API” to “FileReader API”? Arve Bersvendsen
• Re: Rename “File API” to “FileReader API”? Adam Barth
• Rename “File API” to “FileReader API”? Dominique Hazael-Massieux
• Re: Use Cases and Requirements for Saving Files Securely Maciej Stachowiak

Monday, 9 November 2009

• Re: Use Cases and Requirements for Saving Files Securely Ian Hickson
• Re: Policy and browsers (was Re: Policy work items - request for proposals) Robin Berjon
• Re: Geolocation WG taking up work on Orientation/Acceleration Robin Berjon
• Re: Policy and browsers (was Re: Policy work items - request for proposals) Frederick Hirsch
• Policy and browsers (was Re: Policy work items - request for proposals) Robin Berjon
• Re: Geolocation WG taking up work on Orientation/Acceleration Christian Timmerer (ITEC)
• Geolocation WG taking up work on Orientation/Acceleration Dominique Hazael-Massieux

Thursday, 5 November 2009

• Re: Use Cases and Requirements for Saving Files Securely Eric Uhrhane

Wednesday, 4 November 2009

• Re: Policy work items - request for proposals イアンフェッティ
• Re: Policy work items - request for proposals Frederick Hirsch
• Re: Policy work items - request for proposals イアンフェッティ
• Re: Policy work items - request for proposals Frederick Hirsch
• revised minutes 2009-11-02 DAP F2F day 1 Frederick Hirsch
• Draft DAP minutes 2009-11-03, F2F day 2 Frederick Hirsch

Tuesday, 3 November 2009

• Re: Minor fix to DAP homepage Frederick Hirsch
• draft minutes 2009-11-02 F2f Day1 Frederick Hirsch
• Re: ISSUE-7: Gathering requirements [Calendar API] Andrew McMillan
• Re: ISSUE-7: Gathering requirements [Calendar API] Jere.Kapyaho@nokia.com
• draft proposal for RFID/NFC API 전종홍
• FYI: DAP related workshop in Korea 전종홍
• Updated Nokia policy input Frederick Hirsch
• Use Cases for Policy Interoperability SULLIVAN, BRYAN L (ATTCINW)
• Re: Use Cases and Requirements for Saving Files Securely Jonas Sicking
• Re: Policy work items - request for proposals イアンフェッティ

Monday, 2 November 2009

• RE: Policy work items - request for proposals Suresh Chitturi
• Use Cases and Requirements for Saving Files Securely Doug Schepers
• Policy work items - request for proposals Frederick Hirsch
• OMTP BONDI 1.1 Candidate Release now available David Rogers
• Re: Draft policy requirements Paddy Byers
• Agenda v2, DAP 2-3 Nov 2009 F2f Frederick Hirsch
• RE: [Device APIs Requirements] Input to Gallery API 이원석

Sunday, 1 November 2009

• Re: ISSUE-11: Gathering requirements [FileSystem API] Frederick Hirsch

Monday, 2 November 2009

• Re: Seeking "JIL" APIs [Was: Re: ISSUE-32: Features, Device Capabilities, their identification, and their role in policy] Paddy Byers

Last message date: Monday, 30 November 2009 18:59:19 UTC