public-device-apis@w3.org from July 2014 by author

Artur Lugmayr

• CfP SAME Workshop@NordiCHI - Pervasive & Smart & Media Usability, Interaction, and Technologies (dealdine 15th Nov), Helsinki (Thursday, 10 July)
• CfP ACADEMIC MINDTREK (EXTENDED 10/Aug): Academic MindTrek * GAMES, SOCIAL MEDIA, HCI, PERVASIVE MEDIA, eGOVERNMENT, MEDIA MANAGMENT & BUSINESS, HYBRID MEDIA * (Thursday, 10 July)

cathy.chan@nokia.com

• RE: [battery] Moving Battery API forward, next steps? (Wednesday, 2 July)
• RE: ISSUE-164: Correct default for charging time if unknown in battery (was: [battery] next steps and questions) (Wednesday, 2 July)
• RE: ISSUE-164: Correct default for charging time if unknown in battery (was: [battery] next steps and questions) (Tuesday, 1 July)
• RE: [battery] Moving Battery API forward, next steps? (Tuesday, 1 July)

Charles McCathie Nevile

• Re: Call for potential DAP charter additions - please respond by 7 July 2014 (Thursday, 10 July)
• Re: [webintents] Should DAP revisit WebIntents? (Wednesday, 2 July)
• Re: Call for potential DAP charter additions - please respond by 7 July 2014 (Wednesday, 2 July)

Domenic Denicola

• Re: [battery] Should getBattery() always return the same promise? (Friday, 4 July)
• RE: [battery] getBattery() vs. requestBattery() pattern (Thursday, 3 July)
• RE: [battery] Should getBattery() always return the same promise? (Tuesday, 1 July)
• RE: [battery] getBattery() vs. requestBattery() pattern (Tuesday, 1 July)
• [battery] getBattery() vs. requestBattery() pattern (Tuesday, 1 July)
• RE: [battery] Should getBattery() always return the same promise? (Tuesday, 1 July)

Fabrice Desré

• Re: [battery] Should getBattery() always return the same promise? (Friday, 4 July)

Frederick Hirsch

• [admin] Cancel teleconference 24 July, next teleconference 7 August (Wednesday, 23 July)
• Re: Adding Wake Lock to the charter (Friday, 18 July)
• [admin] Cancel DAP Teleconference 10 July 2014 (Thursday, 10 July)
• [admin] Agenda - DAP Distributed Meeting 10 July 2014 (Wednesday, 9 July)
• Re: ISSUE-164: Correct default for charging time if unknown in battery (was: [battery] next steps and questions) (Wednesday, 2 July)
• Re: [battery] Should getBattery() always return the same promise? (Tuesday, 1 July)

Ilya Bogdanovich

• Re: Call for potential DAP charter additions - please respond by 7 July 2014 (Tuesday, 1 July)

Kostiainen, Anssi

• Re: [battery] getBattery() vs. requestBattery() pattern (Thursday, 3 July)
• Re: [battery] getBattery() vs. requestBattery() pattern (Thursday, 3 July)
• Re: [battery] Moving Battery API forward, next steps? (Thursday, 3 July)
• Re: ISSUE-164: Correct default for charging time if unknown in battery (was: [battery] next steps and questions) (Thursday, 3 July)
• Re: ISSUE-164: Correct default for charging time if unknown in battery (was: [battery] next steps and questions) (Wednesday, 2 July)
• Re: [battery] Moving Battery API forward, next steps? (Wednesday, 2 July)
• Re: ISSUE-164: Correct default for charging time if unknown in battery (was: [battery] next steps and questions) (Tuesday, 1 July)
• Re: [battery] proposed additional edit for attribute defaults (Tuesday, 1 July)
• Re: [battery] Moving Battery API forward, next steps? (Tuesday, 1 July)

Lisa Seacat DeLuca

• Vibration spec and Cordova integration update (Thursday, 24 July)

Marcos

• Re: [battery] Should getBattery() always return the same promise? (Friday, 4 July)
• Re: [battery] Should getBattery() always return the same promise? (Friday, 4 July)

Marcos Caceres

• Re: Adding Wake Lock to the charter (Friday, 18 July)
• Adding Wake Lock to the charter (Friday, 18 July)
• Re: Call for potential DAP charter additions - please respond by 7 July 2014 (Wednesday, 2 July)
• Re: [battery] getBattery() vs. requestBattery() pattern (Wednesday, 2 July)
• Re: Call for potential DAP charter additions - please respond by 7 July 2014 (Wednesday, 2 July)

Michael van Ouwerkerk

• Re: Vibration test update (Re ACTION-701: DAP testing status) (Monday, 14 July)

Mounir Lamouri

• Re: [battery] Should getBattery() always return the same promise? (Friday, 4 July)
• Re: [battery] getBattery() vs. requestBattery() pattern (Thursday, 3 July)
• Re: [battery] getBattery() vs. requestBattery() pattern (Thursday, 3 July)
• Re: [battery] Should getBattery() always return the same promise? (Tuesday, 1 July)
• [battery] Should getBattery() always return the same promise? (Tuesday, 1 July)

Paul Kinlan

• Re: [webintents] Should DAP revisit WebIntents? (Wednesday, 2 July)

Rick Waldron

• Re: [battery] Should getBattery() always return the same promise? (Saturday, 5 July)
• Re: [battery] Should getBattery() always return the same promise? (Friday, 4 July)
• Re: [battery] Should getBattery() always return the same promise? (Friday, 4 July)
• Re: [battery] Should getBattery() always return the same promise? (Friday, 4 July)
• Re: [battery] getBattery() vs. requestBattery() pattern (Thursday, 3 July)
• Re: [battery] Should getBattery() always return the same promise? (Tuesday, 1 July)
• Re: [battery] Should getBattery() always return the same promise? (Tuesday, 1 July)
• Re: [battery] getBattery() vs. requestBattery() pattern (Tuesday, 1 July)
• Re: [battery] Should getBattery() always return the same promise? (Tuesday, 1 July)

Stefan Håkansson LK

• Media Capture TF status update (Wednesday, 2 July)

Tim Volodine

• Re: [battery] Should getBattery() always return the same promise? (Friday, 4 July)

Zhang, Zhiqiang

• RE: Vibration test update (Re ACTION-701: DAP testing status) (Tuesday, 15 July)
• Vibration test update (Re ACTION-701: DAP testing status) (Monday, 14 July)

Last message date: Thursday, 24 July 2014 14:13:59 UTC