Thursday, 28 February 2013
- RE: Draft minutes 20 February 2013
- Re: Latest Discovery API
- Re: [admin] Relationship of DAP and SysApps deliverables
Wednesday, 27 February 2013
- Summary of Privacy Interest Group (PING) feedback regarding Proximity and Ambient Light APIs
- Re: Latest Discovery API
- [minutes] Draft Minutes DAP 27 February 2013
- Re: [discovery-api] loophole in current getNetworkServices flow
- Re: DAP Network Service Discovery API
- Re: DAP Network Service Discovery API
Monday, 25 February 2013
Tuesday, 26 February 2013
Monday, 25 February 2013
Friday, 22 February 2013
- Re: [proximity, light] Dispatching events at objects (was: Please confirm DAP comment resolution)
- Re: [proximity, light] Dispatching events at objects (was: Please confirm DAP comment resolution)
- Re: [battery] Test suite updated
- Re: [proximity, light] Dispatching events at objects (was: Please confirm DAP comment resolution)
- Re: [battery] Test suite updated
- Re: [proximity, light] Dispatching events at objects (was: Please confirm DAP comment resolution)
- [battery] Test suite updated (was: Editorial changes in Battery Status API)
- Re: [proximity, light] Dispatching events at objects (was: Please confirm DAP comment resolution)
- Re: [proximity, light] Dispatching events at objects (was: Please confirm DAP comment resolution)
Thursday, 21 February 2013
- Re: [proximity, light] Dispatching events at objects (was: Please confirm DAP comment resolution)
- [battery] Editorial: removed legacy DOM-style sections, updated prose
- Re: [proximity, light] Dispatching events at objects (was: Please confirm DAP comment resolution)
Wednesday, 20 February 2013
Tuesday, 19 February 2013
- [discovery-api] Editorial comments
- RE: [discovery-api] Comments A3, A4, A7 (was: [discovery-api] Consolidated comments and questions)
- Agenda - Distributed Meeting 20 February 2013
- Re: [admin] Relationship of DAP and SysApps deliverables
Saturday, 16 February 2013
Thursday, 14 February 2013
- RE: [admin] Relationship of DAP and SysApps deliverables
- Re: Liaison statement from OMA on network efficiency
Tuesday, 12 February 2013
- RE: [discovery-api] Consolidated comments and questions
- RE: [discovery-api] how does serviceavailable function in practice
- RE: [discovery-api] Comments A3, A4, A7 (was: [discovery-api] Consolidated comments and questions)
- Re: Liaison statement from OMA on network efficiency
- RE: Liaison statement from OMA on network efficiency
- Re: Liaison statement from OMA on network efficiency
- RE: Liaison statement from OMA on network efficiency
- Re: Liaison statement from OMA on network efficiency
- Re: [discovery-api] Consolidated comments and questions
- :: Academic MindTrek Conference 2013 :: DEADLINE FOR WORKSHOPS & TUTORIALS 28th APRIL 2013 :: Cf Papers, Posters, Tutorials, Extended Abstracts, Demos, and Workshops
Friday, 8 February 2013
- Re: [discovery-api] how does serviceavailable function in practice
- Re: [discovery-api] Consolidated comments and questions
- Re: [discovery-api] Consolidated comments and questions
- Re: [admin] Relationship of DAP and SysApps deliverables
- Re: [discovery-api] Consolidated comments and questions
- Re: [discovery-api] Comments A3, A4, A7 (was: [discovery-api] Consolidated comments and questions)
- Re: [discovery-api] Consolidated comments and questions
- Re: [discovery-api] Consolidated comments and questions
- Re: [discovery-api] section 8 language describing serviceon/offline
- Re: [discovery-api] Consolidated comments and questions
- Re: [discovery-api] how does serviceavailable function in practice
- Re: Editorial changes in Battery Status API
Thursday, 7 February 2013
- Re: [discovery-api] how does serviceavailable function in practice
- RE: [discovery-api] Consolidated comments and questions
- [discovery-api] Comments A3, A4, A7 (was: [discovery-api] Consolidated comments and questions)
- RE: [discovery-api] Consolidated comments and questions
- RE: [discovery-api] how does serviceavailable function in practice
- [discovery-api] loophole in current getNetworkServices flow
- Editorial changes in Battery Status API
- RE: [admin] Relationship of DAP and SysApps deliverables
- RE: [admin] Relationship of DAP and SysApps deliverables
- [admin] Relationship of DAP and SysApps deliverables
- Re: [discovery-api] how does serviceavailable function in practice
- Re: [discovery-api] how does serviceavailable function in practice
- [discovery-api] how does serviceavailable function in practice
- Re: [discovery-api] Consolidated comments and questions
- Re: [discovery-api] Consolidated comments and questions
- [discovery-api] section 8 language describing serviceon/offline
- Processing data: non-DOM
- RE: Liaison statement from OMA on network efficiency
- Re: [discovery-api] Consolidated comments and questions
Wednesday, 6 February 2013
- Draft minutes teleconference 2013-02-06
- Re: [proximity, light] Dispatching events at objects (was: Please confirm DAP comment resolution)
- RE: Liaison statement from OMA on network efficiency
- Re: [discovery-api] Consolidated comments and questions
- Re: [discovery-api] Consolidated comments and questions
- Re: [discovery-api] Consolidated comments and questions
- Re: [discovery-api] Consolidated comments and questions
- Re: [MediaStream Recording]: MediaStream recording published as FPWD
- Re: [MediaStream Recording]: MediaStream recording published as FPWD
- Re: [discovery-api] Consolidated comments and questions
- Re: [discovery-api] Consolidated comments and questions
- Re: [discovery-api] Consolidated comments and questions
Tuesday, 5 February 2013
- Re: [discovery-api] Consolidated comments and questions
- Re: [discovery-api] Consolidated comments and questions
- Re: [MediaStream Recording]: MediaStream recording published as FPWD
- Agenda - Distributed Meeting 6 February 2013
- Re: [discovery-api] Consolidated comments and questions
- [MediaStream Recording]: MediaStream recording published as FPWD
- Media Capture TF now operating under the new Charter