- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 17 Jun 2010 21:22:28 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/policy In directory hutz:/tmp/cvs-serv31750 Modified Files: Profile.html Log Message: add references, update title, update abstract and intro (intermediate checkin) Index: Profile.html =================================================================== RCS file: /sources/public/2009/dap/policy/Profile.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -d -r1.4 -r1.5 --- Profile.html 15 Jun 2010 09:46:40 -0000 1.4 +++ Profile.html 17 Jun 2010 21:22:26 -0000 1.5 @@ -1,31 +1,38 @@ <!DOCTYPE html> <html> <head> - <title>Device API Policy Profile: XACML</title> <meta http-equiv='Content-Type' - content='text/html;charset=utf-8'/> <script src='../ReSpec.js/js/respec.js' - class='remove'></script> <script class='remove'> - var respecConfig = { specStatus: "ED", shortName: "policy", - // publishDate: "2009-10-23", previousPublishDate: "1977-03-15", - edDraftURI: "http://dev.w3.org/2009/dap/policy/", - // lcEnd: "2009-08-05", - }; + <title>XACML Policy Profile for Device APIs</title> + <meta http-equiv='Content-Type' + content='text/html;charset=utf-8'/> <script + src='../ReSpec.js/js/respec.js' + class='remove'></script> <script class='remove'> + var respecConfig = { specStatus: "ED", shortName: "policy", + // publishDate: "2009-10-23", previousPublishDate: "1977-03-15", + edDraftURI: "http://dev.w3.org/2009/dap/policy/", + // lcEnd: "2009-08-05", + }; </script> <script src='../common/configPolicy.js' class='remove'></script> - </head> <body> + </head> <body> <section id='abstract'> - This document specifies a policy framework for device APIs. + <p>This document defines a profile of the XACML 2.0 standard to be + used to define access control policies for Device APIs.</p> </section> <!-- abstract --> <section id='introduction'> - <h2>Introduction</h2> <p> - This document is an editors draft and currently does not reflect - consensus of the WG but rather is a starting point for further work. It - is based on input documents and list discussion. - </p> <p> - The policy framework described in this document is intended to be - applicable both to widgets and web applications (web site access to - Device APIs). + <h2>Introduction</h2> + <p> + The Devices API policy framework [[!DAP-POLICY-FRAMEWORK]] + outlines the role and use of policy in the context of Device + APIs. This document provides a profile of XACML 2.0 + enabling such policies to be defined using the XACML + language [[!XACML20]]. This specification does not provide an + overview of XACML as this information is available elsewhere + [[XACML-INTRO]].</p> + <p> + This work is based on the requirements for access + control in Device APIs [[DAP-ACCESS-REQS]]. </p> </section> <!-- introduction --> -<section id="security-model-definition"> + <section id="security-model-definition"> <h2>Security Model Definition</h2> <p> This section defines the formal model underlying the general security framework. This includes definitions of each of the entities involved in the @@ -166,7 +173,7 @@ </p> <p> The result of a rule is determined if and only if its condition has determined value. </p> - </section> <!-- decision --> + </section> <!-- rule --> <section id="condition"> <h3>Condition</h3> <p>The <em>condition</em> of a <em>rule</em> specifies
Received on Thursday, 17 June 2010 21:22:29 UTC