Re: Comment on DAP Access control requirements and Features and Capabilities document

Looking over this and circulating internally.

-Ian

On Wed, Aug 25, 2010 at 8:34 AM, <Frederick.Hirsch@nokia.com> wrote:

> [this time with link to Features and Capabilities draft]
>
> Ian, Doug
>
> As you know, the W3C Device APIs and Policy WG (DAP) has had a policy
> framework deliverable and we've discussed issues related to this in our F2F
> meeting.
>
> I've updated the Access Control Use Cases and Requirements document to
> reflect these discussions, including the concepts of web browsing,
> installable applications (similar to what was suggested in Ian's privacy
> workshop paper) and delegated authority and policy.
>
> The latest draft is at http://dev.w3.org/2009/dap/policy-reqs/
>
> We have a Call for Consensus out to publish an updated WD of these
> requirements - I want to bring it to your attention, as I believe it
> reflects consideration of your concerns.  Even when published this remains a
> work in progress and feedback and suggestions are welcome.
>
> The WG also elected to defer publication of the policy framework draft, to
> focus first on  a Features and Capabilities (permissions) draft. We have a
> very rough draft  that lists Android permissions (viewed as capabilities),
> comparing them with BONDI features. Our intent is to use these as examples
> to help drive the decisions we make. Do you have any comment on this draft,
> or concrete proposals on how to move it forward?
>
> The latest draft is at http://dev.w3.org/2009/dap/features/
>
> Thanks
>
> regards, Frederick
>
> Frederick Hirsch, Nokia
> Co-Chair, W3C DAP Working Group
>
> For tracker, this should complete ACTION-261
>
>