2009/dap/policy-reqs FPWD.html,1.13,1.14

Update of /sources/public/2009/dap/policy-reqs
In directory hutz:/tmp/cvs-serv29957

Modified Files:
	FPWD.html 
Log Message:
removed mention of "doesn't expect" per pubrules


Index: FPWD.html
===================================================================
RCS file: /sources/public/2009/dap/policy-reqs/FPWD.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- FPWD.html	24 Jun 2010 07:20:18 -0000	1.13
+++ FPWD.html	24 Jun 2010 07:21:00 -0000	1.14
@@ -443,7 +443,7 @@
       <p>This is the first public Working Group Note of the Device API Access Control Requirements. This document is expected to be further updated based on both Working Group input and public comments. The Working Group anticipates to
       eventually publish a stabilized version of this document as a <acronym title="World Wide Web Consortium">W3C</acronym>
       Working Group Note.</p>
-    <p>This document was published by the <a href="http://www.w3.org/2009/dap/">Device APIs and Policy Working Group</a>. If you wish to make comments regarding this document, please send them to <a href="mailto:public-device-apis@w3.org">public-device-apis@w3.org</a> (<a href="mailto:public-device-apis-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-device-apis/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Group Note does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. The group does not expec this document to become a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/43696/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></i><li class="tocline"><a href="#definitions" class="tocxref"><span class="secno">2. </span>Definitions</a></li><li class="tocline"><a href="#user-control" class="tocxref"><span class="secno">3. </span>User Managed Access</a><ul class="toc"><li class="tocline"><a href="#use-case-pm1--user-controlled-configuration" class="tocxref"><span class="secno">3.1 </span>Use case PM1: user-controlled configuration</a></li><li class="tocline"><a href="#use-case-pm2--user-delegated-configuration" class="tocxref"><span class="secno">3.2 </span>Use case PM2: user-delegated configuration</a></li><li class="tocline"><a href="#use-case-pi2--portability-of-user-settings" class="tocxref"><span class="secno">3.3 </span>Use case PI2: portability of user settings</a></li><li class="tocline"><a href="#prompts" class="tocxref"><span class="secno">3.4 </span>Prompts</a></li><li class="tocline"><a href="#user-control-rqmts" class="tocxref"><span class="secno">3.5 </span>User Control Requirements</a></li><li class="tocline"><a href="#prtable-policy" class="tocxref"><span class="secno">3.6 </span>Portable Policy</a></li></ul></li><li class="tocline"><a href="#enterprise-managed-access" class="tocxref"><span class="secno">4. </span>Enterprise Managed Access</a><ul class="toc"><li class="tocline"><a href="#use-case-pm3--external-policy-authority" class="tocxref"><span class="secno">4.1 </span>Use case PM3: external policy authority</a></li><li class="tocline"><a href="#use-case-pi1--device-independent-policy-definition" class="tocxref"><span class="secno">4.2 </span>Use case PI1: device-independent policy definition</a></li><li class="tocline"><a href="#use-case-pi3--policy-provisioning-as-part-of-service-deployment" class="tocxref"><span class="secno">4.3 </span>Use case PI3: policy provisioning as part of service deployment</a></li><li class="tocline"><a href="#policy-interoperability" class="tocxref"><span class="secno">4.4 </span>Policy interoperability</a></li><li class="tocline"><a href="#enterprise-requirements" class="tocxref"><spanclass="secno">4.5 </span>Enterprise Requirements</a></li></ul></li><li class="tocline"><a href="#abuse-cases" class="tocxref"><span class="secno">5. </span>Abuse Cases</a><ul class="toc"><li class="tocline"><a href="#premium-rate-abuse" class="tocxref"><span class="secno">5.1 </span>Abuse Case AC1: Premium Rate Abuse</a></li><li class="tocline"><a href="#privacy-breach" class="tocxref"><span class="secno">5.2 </span>Abuse Case AC2: Privacy Breach</a></li><li class="tocline"><a href="#integrity-breach" class="tocxref"><span class="secno">5.3 </span>Abuse Case AC3: Integrity Breach</a></li><li class="tocline"><a href="#phishing" class="tocxref"><span class="secno">5.4 </span>Abuse Case AC4: Phishing</a></li></ul></li><li class="tocline"><a href="#capabilities" class="tocxref"><span class="secno">6. </span>Capabilities</a><ul class="toc"><li class="tocline"><a href="#policy-capability-requirements" class="tocxref"><span class="secno">6.1 </span>Capability Requirements</a></li><li class="tocline"><a href="#issu---features--relationship-to-capabilities--crud" class="tocxref"><span class="secno">6.2 </span>Issue - Features, relationship to capabilities, CRUD</a></li></ul></li><li class="tocline"><a href="#framework" class="tocxref"><span class="secno">7. </span>Security Framework</a><ul class="toc"><li class="tocline"><a href="#framework-rqmts" class="tocxref"><span class="secno">7.1 </span>Security Framework Requirements</a><ul class="toc"><li class="tocline"><a href="#policy-integrity-requirements" class="tocxref"><span class="secno">7.1.1 </span>Policy Integrity Requirements</a></li></ul></li><li class="tocline"><a href="#access-control-requirements" class="tocxref"><span class="secno">7.2 </span>Access Control Requirements</a></li></ul></li><li class="tocline"><a href="#examples-of-statements-or-rules-that-may-be-expressed-in-a-policy" class="tocxref"><span class="secno">8. </span>Examples of statements or rules that may be expressed in a policy</a></li><li class="tocline"><a href="#out-of-scope" class="tocxref><span class="secno">9. </span>Out of Scope</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div> <!-- abstract -->
+    <p>This document was published by the <a href="http://www.w3.org/2009/dap/">Device APIs and Policy Working Group</a>. If you wish to make comments regarding this document, please send them to <a href="mailto:public-device-apis@w3.org">public-device-apis@w3.org</a> (<a href="mailto:public-device-apis-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-device-apis/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Group Note does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wie Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/43696/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#definitions" class="tocxref"><span class="secno">2. </span>Definitions</a></li><li class="toline"><a href="#user-control" class="tocxref"><span class="secno">3. </span>User Managed Access</a><ul class="toc"><li class="tocline"><a href="#use-case-pm1--user-controlled-configuration" class="tocxref"><span class="secno">3.1 </span>Use case PM1: user-controlled configuration</a></li><li class="tocline"><a href="#use-case-pm2--user-delegated-configuration" class="tocxref"><span class="secno">3.2 </span>Use case PM2: user-delegated configuration</a></li><li class="tocline"><a href="#use-case-pi2--portability-of-user-settings" class="tocxref"><span class="secno">3.3 </span>Use case PI2: portability of user settings</a></li><li class="tocline"><a href="#prompts" class="tocxref"><span class="secno">3.4 </span>Prompts</a></li><li class="tocline"><a href="#user-control-rqmts" class="tocxref"><span class="secno">3.5 </span>User Control Requirements</a></li><li class="tocline"><a href="#portable-policy" class="tocxref"><span class="secno">3.6 </span>Portable Policy</a></li></ul></li><li class="tocline"><a href=#enterprise-managed-access" class="tocxref"><span class="secno">4. </span>Enterprise Managed Access</a><ul class="toc"><li class="tocline"><a href="#use-case-pm3--external-policy-authority" class="tocxref"><span class="secno">4.1 </span>Use case PM3: external policy authority</a></li><li class="tocline"><a href="#use-case-pi1--device-independent-policy-definition" class="tocxref"><span class="secno">4.2 </span>Use case PI1: device-independent policy definition</a></li><li class="tocline"><a href="#use-case-pi3--policy-provisioning-as-part-of-service-deployment" class="tocxref"><span class="secno">4.3 </span>Use case PI3: policy provisioning as part of service deployment</a></li><li class="tocline"><a href="#policy-interoperability" class="tocxref"><span class="secno">4.4 </span>Policy interoperability</a></li><li class="tocline"><a href="#enterprise-requirements" class="tocxref"><span class="secno">4.5 </span>Enterprise Requirements</a></li></ul></li><li class="tocline"><a href="#abuse-cases" class="tocxref><span class="secno">5. </span>Abuse Cases</a><ul class="toc"><li class="tocline"><a href="#premium-rate-abuse" class="tocxref"><span class="secno">5.1 </span>Abuse Case AC1: Premium Rate Abuse</a></li><li class="tocline"><a href="#privacy-breach" class="tocxref"><span class="secno">5.2 </span>Abuse Case AC2: Privacy Breach</a></li><li class="tocline"><a href="#integrity-breach" class="tocxref"><span class="secno">5.3 </span>Abuse Case AC3: Integrity Breach</a></li><li class="tocline"><a href="#phishing" class="tocxref"><span class="secno">5.4 </span>Abuse Case AC4: Phishing</a></li></ul></li><li class="tocline"><a href="#capabilities" class="tocxref"><span class="secno">6. </span>Capabilities</a><ul class="toc"><li class="tocline"><a href="#policy-capability-requirements" class="tocxref"><span class="secno">6.1 </span>Capability Requirements</a></li><li class="tocline"><a href="#issue---features--relationship-to-capabilities--crud" class="tocxref"><span class="secno">6.2 </span>Issue - Features, relationshp to capabilities, CRUD</a></li></ul></li><li class="tocline"><a href="#framework" class="tocxref"><span class="secno">7. </span>Security Framework</a><ul class="toc"><li class="tocline"><a href="#framework-rqmts" class="tocxref"><span class="secno">7.1 </span>Security Framework Requirements</a><ul class="toc"><li class="tocline"><a href="#policy-integrity-requirements" class="tocxref"><span class="secno">7.1.1 </span>Policy Integrity Requirements</a></li></ul></li><li class="tocline"><a href="#access-control-requirements" class="tocxref"><span class="secno">7.2 </span>Access Control Requirements</a></li></ul></li><li class="tocline"><a href="#examples-of-statements-or-rules-that-may-be-expressed-in-a-policy" class="tocxref"><span class="secno">8. </span>Examples of statements or rules that may be expressed in a policy</a></li><li class="tocline"><a href="#out-of-scope" class="tocxref"><span class="secno">9. </span>Out of Scope</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span clss="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div> <!-- abstract -->
 
     
 

Received on Thursday, 24 June 2010 07:21:04 UTC