- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 18 Jun 2010 23:34:30 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/policy
In directory hutz:/tmp/cvs-serv6953
Modified Files:
Framework.html
Log Message:
get rid of more links and profile specifics.
Index: Framework.html
===================================================================
RCS file: /sources/public/2009/dap/policy/Framework.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- Framework.html 18 Jun 2010 23:31:46 -0000 1.10
+++ Framework.html 18 Jun 2010 23:34:28 -0000 1.11
@@ -175,7 +175,8 @@
The JavaScript API access control layer controls access
to JavaScript APIs exposed by the web runtime. Each <a href=#feature>feature</a> is
identified uniquely by IRI, and this security layer mediates access to
- features on the basis of that ID, <a href=#api-feature><code>api-feature</code></a>.
+ features on the basis of that
+ ID.
</p>
</section> <!-- API access control layer -->
<section id="device-capability-access-control-layer">
@@ -207,7 +208,7 @@
advertised as being dependencies of the web application.</strong> The access control system must ensure
that only requested features are accessible to the web
application. This requires that the access control system is able to
- control access based on the ID of a Feature, <a href=#api-feature><code>api-feature</code></a>.</p></li>
+ control access based on the ID of a Feature.</p></li>
<li><p><strong>There will not be a direct 1-1 correspondence between JavaScript APIs
and device capabilities.</strong> Although there will be simple JavaScript APIs that
provide access only to a single device capability, it must be expected that
@@ -472,16 +473,8 @@
<li><p>When the application in question attempts an action
(attempts to invoke a JavaScript API, say). This identifies
the <a href=#resource>resource</a> and all
- associated <a href=#resource-attribute>resource attributes</a>
- including <a href=#api-feature><code>api-feature</code></a> and,
- where
- applicable,<code>device-cap</code>
- resource attribute if the action entails use of a device
- capability. Any parameters used by any such device capability
- use, where designated as being security-relevant, are also
- captured within
- a <code>param:name</code>
- resource attribute;</p></li>
+ associated <a href=#resource-attribute>resource attributes</a>.
+</p></li>
<li><p>the <a href=#environment-attribute>environment attributes</a> are also captured;</p></li>
<li><p>the set of resource and environment attribute values
captured is embodied in an <a href=Profile.html#query>access
Received on Friday, 18 June 2010 23:34:31 UTC