- From: Laura Arribas via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 09 Apr 2010 15:17:34 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/policy
In directory hutz:/tmp/cvs-serv6104
Modified Files:
Overview.html
Log Message:
Further changes: images
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/policy/Overview.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- Overview.html 8 Apr 2010 16:22:04 -0000 1.4
+++ Overview.html 9 Apr 2010 15:17:32 -0000 1.5
@@ -174,8 +174,8 @@
terminology is adopted from XACML [[!XACML]] and illustrated below.
</p>
<!-- ILLUSTRATION XACML DATAFLOW -->
- <p><a href="XACMLdataflow.png"><div style="text-align: center;"><img src="XACMLdataflow.png" alt="graphical representation of the XACML data flow" width="600" align="middle"/></a><div class="caption">DAP security model, derived from XACML [[!XACML]] Specification Schema</div>
-</div></p>
+ <div style="text-align:center;"><object type="image/svg+xml" data="XACMLdataflow.svg">
+ <img src="XACMLdataflow.png" alt="graphical representation of the XACML data flow" title="DAP security model, derived from XACML [[!XACML]] Specification Schema" width="500" height="500"/> </object></div>
<p>
The specified functional components are as follows:
<ul>
@@ -255,8 +255,8 @@
Simplistically, each rule is specified by defining a <strong><em><a href=#condition>condition</a></em></strong>, which is a set of statements which must be satisfied in order for that particular rule to apply, and an <strong><em><a href=#effect>effect</a></em></strong> which represents the rule’s outcome – ie whether that rule indicates that the access request should be permitted or not.
</p>
<!-- ILLUSTRATION POLICY LANGUAGE MODEL -->
- <p><a href="languagemodel.png"><div style="text-align: center;"><img src="languagemodel.png" alt="graphical representation of the XACML policy language model" width="250" align="middle"/></a><div class="caption">DAP policy language model, derived from XACML [[!XACML]] Specification Schema</div>
-</div></p>
+ <div style="text-align:center;"><object type="image/svg+xml" data="languagemodel.svg">
+ <img src="languagemodel.png" alt="graphical representation of the XACML policy language model" title="DAP policy language model, derived from XACML [[!XACML]] Specification Schema" width="250" /> </object></div>
</section> <!-- access control policy structure -->
<section id=rule-processing>
<h3>Rule Processing</h3>
@@ -773,7 +773,7 @@
as described in [[!SUSv3]] section 2.13 Pattern Matching Notation
but excluding 2.13.3 Patterns Used for Filename
Expansion. </p> <p class="issue"> XACML MISSING REF ENTRY.http://www.unix.org/single_unix_specification/
- </p> <p>Using this function with a glob
+ </p> <!-- Shell & Utilities Volume of the SUSv3 spec --><p>Using this function with a glob
pattern of “*” (a single asterisk) is a convenient way
to test whether the first input is not an empty bag.
</p>
Received on Friday, 9 April 2010 15:17:36 UTC