- From: Dominique Hazael-Massieux via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 21 Jun 2010 13:31:48 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/policy In directory hutz:/tmp/cvs-serv11282 Modified Files: Profile.html Log Message: making second xml code more readable (indent, well-formedness) Index: Profile.html =================================================================== RCS file: /sources/public/2009/dap/policy/Profile.html,v retrieving revision 1.11 retrieving revision 1.12 diff -u -d -r1.11 -r1.12 --- Profile.html 21 Jun 2010 13:29:34 -0000 1.11 +++ Profile.html 21 Jun 2010 13:31:46 -0000 1.12 @@ -990,17 +990,19 @@ </p> <p> Clearly, if the widget is prevented from installing, then it cannot call a device API – these functions are shown as a belt and braces example:</p> - <pre><code> <code><target></code> - <code><subject></code> - <subject-match attr="id" match="http://maliciouswidget1.example.org"> - </subject> - </target> <rule effect="deny"> - <condition combine="or"> - <resource-match attr="widget-install" /> <resource-match - attr="widget-instantiate" /> <resource-match attr="api-feature" match="*" - /> <resource-match attr="dev-cap" match="*" /> </condition> - </rule> - </code></pre> + <pre><code><target> + <subject> + <subject-match attr="id" match="http://maliciouswidget1.example.org"/> + </subject> +</target> +<rule effect="deny"> + <condition combine="or"> + <resource-match attr="widget-install" /> <resource-match + attr="widget-instantiate" /> + <resource-match attr="api-feature" match="*"/> + <resource-match attr="dev-cap" match="*" /> + </condition> +</rule></code></pre> </section> <!-- premium-rate-abuse --> </section> <!-- example policies --> </section>
Received on Monday, 21 June 2010 13:31:52 UTC