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

Policy - high level principles and requirements

From: Frederick Hirsch <frederick.hirsch@nokia.com>
Date: Tue, 29 Sep 2009 20:07:00 -0400
Message-Id: <FE7A5CBC-A8C6-428B-AE7A-DFDDEBF0FE42@nokia.com>
To: Device APIs and Policy WG <public-device-apis@w3.org>
Cc: Frederick Hirsch <frederick.hirsch@nokia.com>
To help start the policy discussion around requirements I made a quick  
list from the BONDI contribution and some position papers (Nokia,  
Microsoft) of high level principles and requirements.
If we disagree at the high level there isn't much point in the  
associated details. These are at a high level for discussion,  so  
aren't in the form of MUSTs.

One fundamental question is whether we want to support capabilities  
and features or just capabilities.

High Level Principles/Policy requirements

1. Uniform policy framework -  widgets and web applications
- independence of delivery mechanism (BONDI, MS)
- Rich Security Framework With Configurable Access Control Policy
(BONDI)

2. Separation of Security Framework From Policy declaration (BONDI)

3. Declarative policy to enable access control decisions
- Rich Security Framework With Configurable Access Control Policy  
(BONDI)

4. Provide least priviledge for software

5. Enable multiple instantiations of web runtime with independent  
security decisions (Nokia)

6. Able to define device capabilities and make access control decision  
on per-API per-instance basis

7. Able to identify capabilities by URI

8. Able to express capabilities needed by an API

9. Able to determine capabilities supported by device

10. Able to identify an API by URI

11. Able to define a feature as requiring one or more APIs

12 Able to make access control decision on use of feature by a widget  
or web application

13. Able to identify a feature by URI

14. Able to specify features needed by widget or web application

15. Language Independence
     -- Independence of Javascript API Definition - BONDI

16. Support for Javascript required.

17. Able to express policy using XML language

18. Able to have separate policy decision and enforcement points

19. Software isolation

20. Able to associate software with a trusted identity

21 Support identity revocation - out of scope as management?

22. Provide integrity for policy statements and operations

23. Widgets conform to W3C Web Applications specifications, including  
Widget Signature

24 Compatible with HTML 5 security model (need to determine what this  
means in practice and whether feasible)

25. Provide explicit policy controls regarding network access operations


regards, Frederick [ not as chair ]

Frederick Hirsch
Nokia
Received on Wednesday, 30 September 2009 00:07:37 GMT

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