- From: Robin Berjon <robin@berjon.com>
- Date: Mon, 7 Feb 2011 12:39:30 +0100
- To: Bryan Sullivan <blsaws@gmail.com>
- Cc: Dominique Hazael-Massieux <dom@w3.org>, public-device-apis <public-device-apis@w3.org>
Hi, On Feb 2, 2011, at 17:04 , Bryan Sullivan wrote: > - Communication Log API should remain in scope. The working group tried hard and failed to find a way to make this work. We can't keep revisiting the same topics over and over again unless there is new information that was not previously known. The problem that we keep returning to is that we can't find a use case justifying accessing my mailbox from inside my browser. I am not saying that this API isn't useful for a specific class of applications, but we as a group have failed to find it broad applicability. I certainly don't deny that this API could indeed be useful for applications that benefit from a heightened level of trust. But that places it firmly in the trusted silo, and DAP cannot be in the business of producing silo technology. Unless we can find solid use cases and a security model that can make this work in the broad One Web, it is my firm opinion that standardisation of this API would be better conducted in a vertical forum. -- Robin Berjon - http://berjon.com/
Received on Monday, 7 February 2011 11:39:58 UTC