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

2009/dap/policy Framework.html,1.7,1.8

From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 18 Jun 2010 23:23:45 +0000
To: public-dap-commits@w3.org
Message-Id: <E1OPkuX-0001WL-1L@lionel-hutz.w3.org>
Update of /sources/public/2009/dap/policy
In directory hutz:/tmp/cvs-serv5831

Modified Files:
	Framework.html 
Log Message:
fix validation errors


Index: Framework.html
===================================================================
RCS file: /sources/public/2009/dap/policy/Framework.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- Framework.html	18 Jun 2010 23:20:20 -0000	1.7
+++ Framework.html	18 Jun 2010 23:23:42 -0000	1.8
@@ -83,7 +83,7 @@
 <dl>
 <dt>
 <dfn id="feature">feature</dfn></dt>
-<dd> <p> A <dfn id="feature">feature</dfn> is the unit of expression of
+<dd> <p> A feature is the unit of expression of
     dependencies by web applications. (This definition needs clarification).
 </p>
 </dd>
@@ -103,7 +103,7 @@
     An example of a feature IRI would be: TBD </p>
      <div class="issue">
 	<p>Need to define: what constitues a feature, how/where features
-    IRIs are defined, feature IRI examples. See BONDI A&S document,
+    IRIs are defined, feature IRI examples. See BONDI A&amp;S document,
     pages 31 and 32.</p></div> 
 </section>
       <section id="capabilities">
@@ -111,7 +111,7 @@
 <dl>
 <dt>
 <dfn id="device-capability">device capability</dfn>
-<dd> <p> A <dfn id="device-capability">device capability</dfn> is a
+<dd> <p> A device capability is a
     device resource or device functionality
 that may require access control.
 </p>
@@ -275,7 +275,6 @@
       the PAP, although this may be in scope for later phases. The security policy
       itself is not defined by DAP, although a default policy may be recommended by
       DAP at a future stage.</p></div> 
-    </p>
     <p>
       The functionality required in each of these components is
       specified in terms of the following <strong>entities</strong>:
@@ -337,7 +336,7 @@
       access. Resource attributes serve as input of access control
       policies.</p>
 <p>	  The device features or services (e.g. the location module or PIM
-	  database) are the actual <strong><em><a id="resource">resources</a></em></strong> that are being protected, but from
+	  database) are the actual resources that are being protected, but from
 	  the point of view of the security framework these resources
 	  are associated with the API features and device capabilities used to
 	  access them.
@@ -362,7 +361,7 @@
 	  reflects the state of that application at the time an
 	  associated trust domain or access control query is made. The defined
 	  execution phases are listed below. </p> <table
-	  border="1" summary=""> <caption> <dfn
+	  border="1" > <caption> <dfn
 	  id="execution-phases-table">Execution Phases
 	  Table</dfn></caption> <thead> <tr> <th
 	  scope="col">Execution Phase</th> <th
Received on Friday, 18 June 2010 23:23:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 18 June 2010 23:23:46 GMT