W3C home > Mailing lists > Public > public-dap-commits@w3.org > June 2010

2009/dap/policy Profile.html,1.17,1.18

From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 22 Jun 2010 20:52:32 +0000
To: public-dap-commits@w3.org
Message-Id: <E1ORASO-0000i7-J8@lionel-hutz.w3.org>
Update of /sources/public/2009/dap/policy
In directory hutz:/tmp/cvs-serv2716

Modified Files:
Log Message:
change title, abstract and introduction since this is not an XACML
profile but new markup definition

Index: Profile.html
RCS file: /sources/public/2009/dap/policy/Profile.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- Profile.html	21 Jun 2010 14:29:08 -0000	1.17
+++ Profile.html	22 Jun 2010 20:52:30 -0000	1.18
@@ -1,7 +1,7 @@
 <!DOCTYPE html> 
-    <title>XACML Policy Profile for Device APIs</title>
+    <title>Policy Markup for Device APIs</title>
     <meta http-equiv='Content-Type' 
           content='text/html;charset=utf-8'/> <script
@@ -14,8 +14,8 @@
     </script> <script src='../common/configPolicy.js' class='remove'></script>
     </head> <body>
     <section id='abstract'>
-      <p>This document defines a profile of the XACML 2.0 standard to be
-      used to define access control policies for Device APIs.</p>
+      <p>This document defines policy markup for Device APIs. It is
+      similar to the XACML 2.0 standard, but different.</p>
     </section> <!-- abstract -->
     <section id='introduction'>
@@ -23,27 +23,8 @@
         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]]. Trust and access policies are capable of 
-      representation in a compact XML format (and other formats,
-      including a compact  
-      binary representation if necessary).  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">
-  <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
-  definition of an access control policy, and a definition of the attributes of
-  each entity that are recognised and are required to be supported. This
-  specification uses [[!XACML20]]. </p>
+        APIs. This document defines policy markup similar to XACML
+        2.0, but different  specification is similar to XACML but different [[!XACML20]]. </p>
       <section id="values-and-types">
 	<h3>Values and Types</h3>
 	  <p>Each value in an expression is conceptually a
Received on Tuesday, 22 June 2010 20:52:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:28 UTC