- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 09 Aug 2010 19:45:50 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/features
In directory hutz:/tmp/cvs-serv17467
Modified Files:
Overview.html
Log Message:
flatten depth of document
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/features/Overview.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -d -r1.11 -r1.12
--- Overview.html 9 Aug 2010 19:36:58 -0000 1.11
+++ Overview.html 9 Aug 2010 19:45:48 -0000 1.12
@@ -32,14 +32,12 @@
Configuration specification [[WIDGETS]] allows a widget runtime engine to grant access only to the specific APIs that the configuration file of the widget listed.</p>
<p>A similar approach is used in the proposed DAP security policy framework [[DAP-ACCESS-REQS]] [[DAP-POLICY-FRAMEWORK]].</p>
<p>To define these specific security rules, the said APIs need to be identifiable, with a specific meaning attached to each of the identifiers — this is the role of this specification.</p>
- </section> <!-- introduction -->
- <section id="features">
- <h2>Features</h2>
<p>A <dfn>feature</dfn> is a reference to a logical item that may require access control.</p>
<p>This document lists features for well-known APIs, identifies them with a string that can be used to build a URI, and defines the meaning of the feature in terms of access control.</p>
<p>
Examples include the ability to read a local file, or to discover
nearby Bluetooth devices, or to send an SMS message. </p>
+ </section> <!-- introduction -->
<section id="identifiers">
<h2>Identifiers</h2>
<p>Each feature defined below is assigned with a string as an identifier.</p>
@@ -515,7 +513,6 @@
</p>
</section>
</section>
- </section>
<section class='conformance'>
<h2>Conformance</h2>
<p>
Received on Monday, 9 August 2010 19:45:52 UTC