W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2009

RE: Policy and browsers (was Re: Policy work items - request for proposals)

From: DANIEL JESUS COLOMA BAIGES <dcoloma@tid.es>
Date: Wed, 11 Nov 2009 02:01:11 +0100
To: Robin Berjon <robin@robineko.com>, Frederick Hirsch <frederick.hirsch@nokia.com>
Cc: "ifette@google.com" <ifette@google.com>, W3C Device APIs and Policy WG <public-device-apis@w3.org>
Message-id: <4DC093FB1C4D6A4EA398DF8CA531137F1044487C62@EXCLU2K7.hi.inet>
Hi,

  Is there any overlap between the first kind of APIs and the Application Launcher described in the WG charter? 

  My view on the App Launcher API is that it was intended to launch other applications, which is quite similar to what is described in the first API category listed below (e.g. launching the camera application).

Best Regards



> -----Mensaje original-----
> De: public-device-apis-request@w3.org [mailto:public-device-apis-
> request@w3.org] En nombre de Robin Berjon
> Enviado el: lunes, 09 de noviembre de 2009 17:35
> Para: Frederick Hirsch
> CC: ifette@google.com; W3C Device APIs and Policy WG
> Asunto: Re: Policy and browsers (was Re: Policy work items - request for
> proposals)
> 
> On Nov 9, 2009, at 17:27 , Frederick Hirsch wrote:
> > I think we roughly ended up in our F2F discussion with something
> > like you suggest, two classes of APIs:
> >
> > 1. those with implicit  user consent, eg. api that opens camera
> > interface but requires user to press button to take picture, or
> > messaging interface that requires pressing "send" etc
> >
> > 2. those that are wholly programmatic, e.g. message sent without out
> > user interaction, picture taken without user interaction.
> >
> > The second class clearly requires policy controls, the first class
> > might if decision apart from user's is required or further
> > restriction is needed.
> 
> Right, and furthermore there was doubt from some parties as to whether
> the two APIs could be the same. I think that we should work on the
> assumption that they can be, and break that only when it turns out not
> to be possible. In general I think that if we design to the more
> constraining case (there is no policy control) then it'll work for the
> more flexible ones (it might look strange at times - for those cases
> convenience wrappers may help).
> 
> --
> Robin Berjon
>    robineko - hired gun, higher standards
>    http://robineko.com/
> 
> 
> 
> 
Received on Wednesday, 11 November 2009 01:01:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:01 GMT