Thursday, 28 February 2013
- Re: Proposal for a Runtime and Security Model FPWD
- Formal proposal regrading editorial process
- Re: Stepping down as co-chair
- RE: Sockets, was Re: [Raw Socket API]. New version separating UDP and TCP interfaces
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: NFC web connection?
- Re: Stepping down as co-chair
- Stepping down as co-chair
- RE: Contacts API
- Re: Contacts API
Wednesday, 27 February 2013
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: The app: URI scheme
- Re: The app: URI scheme
- Re: .webapps file extension, was Re: Manifest format MIME type
- Re: .webapps file extension, was Re: Manifest format MIME type
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- RE: The app: URI scheme
- Re: [Execution and Security Model] Proposal from Samsung Electronics
Tuesday, 26 February 2013
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: Sockets, was Re: [Raw Socket API]. New version separating UDP and TCP interfaces
- JSON encoding … Re: Manifest format MIME type
- .webapps file extension, was Re: Manifest format MIME type
- Re: Manifest format MIME type
- Re: Manifest format MIME type
- Re: Manifest format MIME type
- Re: Manifest format MIME type
- Re: Manifest format MIME type
- Re: The app: URI scheme
- Manifest format MIME type
- Re: The app: URI scheme
- Re: The app: URI scheme
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- RE: NFC web connection?
- NFC web connection?
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: [Execution and Security Model] Proposal from Samsung Electronics
Monday, 25 February 2013
- RE: Sockets, was Re: [Raw Socket API]. New version separating UDP and TCP interfaces
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: Contributions and editing process with sysapps repository
- Re: question about screen_size in Runtime and Security Model
- Re: The app: URI scheme
- Re: Sockets, was Re: [Raw Socket API]. New version separating UDP and TCP interfaces
- Re: Sockets, was Re: [Raw Socket API]. New version separating UDP and TCP interfaces
- Re: Sockets, was Re: [Raw Socket API]. New version separating UDP and TCP interfaces
- Re: Sockets, was Re: [Raw Socket API]. New version separating UDP and TCP interfaces
- Re: [Raw Socket API]. New version separating UDP and TCP interfaces
Thursday, 21 February 2013
Sunday, 24 February 2013
Saturday, 23 February 2013
- Re: Contributions and editing process with sysapps repository
- Re: Contributions and editing process with sysapps repository
- Re: Contributions and editing process with sysapps repository
Friday, 22 February 2013
- Re: question about screen_size in Runtime and Security Model
- Re: question about screen_size in Runtime and Security Model
- Sockets, was Re: [Raw Socket API]. New version separating UDP and TCP interfaces
- Re: The app: URI scheme
- Re: The app: URI scheme
- Re: The app: URI scheme
- RE: The app: URI scheme
- Re: [Raw Socket API]. New version separating UDP and TCP interfaces
Thursday, 21 February 2013
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: Proposal for a Runtime and Security Model FPWD
- Re: Contributions and editing process with sysapps repository
- RE: [Raw Socket API]. New version separating UDP and TCP interfaces
- Re: Concerns about DOMRequest
- Re: question about screen_size in Runtime and Security Model
- RE: Proposal for a Runtime and Security Model FPWD
- Re: question about screen_size in Runtime and Security Model
- Re: question about screen_size in Runtime and Security Model
- Supporting splash screens
Wednesday, 20 February 2013
- Re: Concerns about DOMRequest
- question about screen_size in Runtime and Security Model
- Re: Contributions and editing process with sysapps repository
- Contributions and editing process with sysapps repository
- Re: Proposal for a Runtime and Security Model FPWD
- Re: Proposal for a Runtime and Security Model FPWD
- Re: Proposal for a Runtime and Security Model FPWD
- Logistics for Madrid face to face and registration
- Re: Concerns about DOMRequest
- Re: Request to make one proposal for execution model and security model
- Re: Concerns about DOMRequest
- Re: Concerns about DOMRequest
- Re: Concerns about DOMRequest
- RE: Proposal for a Runtime and Security Model FPWD
- Re: Concerns about DOMRequest
Tuesday, 19 February 2013
- Re: Concerns about DOMRequest
- Re: Concerns about DOMRequest
- Re: Request to make one proposal for execution model and security model
- Proposal for a Runtime and Security Model FPWD
- Re: Request to make one proposal for execution model and security model
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: The app: URI scheme
- Re: Concerns about DOMRequest
- RE: Request to make one proposal for execution model and security model
- Re: [Raw Socket API]. New version separating UDP and TCP interfaces
Monday, 18 February 2013
- Re: The app: URI scheme
- The app: URI scheme
- Re: Concerns about DOMRequest
- Re: Concerns about DOMRequest
- Re: Concerns about DOMRequest
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: Concerns about DOMRequest
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: Concerns about DOMRequest
- Re: Concerns about DOMRequest
- Re: Concerns about DOMRequest
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- RE: Request to make one proposal for execution model and security model
- RE: [Execution and Security Model] Proposal from Samsung Electronics
- [Raw Socket API]. New version separating UDP and TCP interfaces
- Re: Concerns about DOMRequest
- RE: [Alarm API] Use cases
Sunday, 17 February 2013
Saturday, 16 February 2013
Friday, 15 February 2013
- Re: Concerns about DOMRequest
- Re: [Execution and Security Model] Proposal from Samsung Electronics
- Re: [Alarm API] Waking the system up
- Re: Concerns about DOMRequest
- Re: Concerns about DOMRequest
- Re: [Alarm API] Use cases
- Re: Concerns about DOMRequest
- Re: [Alarm] respectTimezone
- Re: [Alarm API] Waking the system up
- Re: [Alarm API] data … yet another DB?
- Re: [Alarm API] data … yet another DB?
- Re: Concerns about DOMRequest
- Re: [Alarm API] data … yet another DB?
- Re: [Alarm] respectTimezone
- Re: [Alarm API] data … yet another DB?
- RE: Concerns about DOMRequest
- Re: Concerns about DOMRequest
- RE: [Alarm] respectTimezone
- RE: [Alarm API] Object data must be serialisable to JSON
- RE: [Alarm API] Object data must be serialisable to JSON
- Re: [Alarm] respectTimezone
- Re: [Alarm API] data … yet another DB?
- Re: Concerns about DOMRequest
- Re: [Alarm API] Object data must be serialisable to JSON
- RE: Edge Conference - Panel 6: Privileged access
Thursday, 14 February 2013
- Re: Concerns about DOMRequest
- Re: [Alarm API] data … yet another DB?
- Re: [Alarm API] data … yet another DB?
- Re: Edge Conference - Panel 6: Privileged access
- Re: [Alarm API] data … yet another DB?
- Re: [Alarm API] data … yet another DB?
- Re: [Alarm API] data … yet another DB?
- Re: Concerns about DOMRequest
- Re: [Alarm] respectTimezone
- Re: [Alarm API] Waking the system up
- Re: Concerns about DOMRequest
Wednesday, 13 February 2013
- Re: [Alarm API] Waking the system up
- Re: Concerns about DOMRequest
- Re: [Alarm API] data … yet another DB?
- RE: [Alarm API] data … yet another DB?
- Re: [Alarm API] data … yet another DB?
- Re: [Alarm] respectTimezone
- Re: Concerns about DOMRequest
- Re: [Alarm API] data … yet another DB?
- Re: Concerns about DOMRequest
- Re: Concerns about DOMRequest
- Re: Concerns about DOMRequest
- Concerns about DOMRequest
- Re: Request to make one proposal for execution model and security model
- Re: Draft Agenda for upcoming F2F Meeting
- RE: Draft Agenda for upcoming F2F Meeting
- Re: Request to make one proposal for execution model and security model
- RE: Request to make one proposal for execution model and security model
- RE: Draft Agenda for upcoming F2F Meeting
- Re: [Alarm API] Use cases
- RE: Draft Agenda for upcoming F2F Meeting
- Re: [Alarm API] Use cases
- Re: [Alarm API] Use cases
- RE: [Alarm API] Use cases
- Re: [Alarm API] Use cases
Tuesday, 12 February 2013
- Re: [Alarm API] Use cases
- Re: [Alarm API] Use cases
- Re: [Alarm API] Use cases
- RE: [Alarm API] data … yet another DB?
- Edge Conference - Panel 6: Privileged access
- [Alarm API] data … yet another DB?
- Re: [Alarm API] Use cases
- RE: [Alarm API] Use cases
- RE: [Alarm] respectTimezone
Monday, 11 February 2013
- [Alarm API] Object data must be serialisable to JSON
- [Alarm] respectTimezone
- [Alarm API] Use cases
- [Alarm API] Waking the system up
- [Alarm API] Privacy/control concerns
Friday, 8 February 2013
Thursday, 7 February 2013
Wednesday, 6 February 2013
Tuesday, 5 February 2013
- Re: Web Alarms API is now a FPWD
- Web Alarms API is now a FPWD
- Re: Decision of dates and location for the first F2F meeting
Monday, 4 February 2013
- Re: Decision of dates and location for the first F2F meeting
- RE: Decision of dates and location for the first F2F meeting
- Re: Decision of dates and location for the first F2F meeting
- Decision of dates and location for the first F2F meeting
Friday, 1 February 2013
- RE: Draft Agenda for upcoming F2F Meeting
- Re: Draft Agenda for upcoming F2F Meeting
- Re: CfC: publish FPWD of Contacts API; deadline Feb 8
- Draft Agenda for upcoming F2F Meeting
- Re: CfC: publish FPWD of Contacts API; deadline Feb 8
- Re: CfC: publish FPWD of Contacts API; deadline Feb 8
- Re: CfC: publish FPWD of Contacts API; deadline Feb 8
- CfC: publish FPWD of Contacts API; deadline Feb 8
- RE: Contacts API