- From: Dominique Hazael-Massieux via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 02 Sep 2010 07:23:51 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/policy-reqs
In directory hutz:/tmp/cvs-serv1522
Modified Files:
WD.html
Log Message:
updated sotd
Index: WD.html
===================================================================
RCS file: /sources/public/2009/dap/policy-reqs/WD.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- WD.html 2 Sep 2010 07:20:00 -0000 1.6
+++ WD.html 2 Sep 2010 07:23:49 -0000 1.7
@@ -445,9 +445,10 @@
This document describes Device API Access Control Use Cases and
corresponding Requirements.
</div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
- This document is not normative. The Working Group expects to evolve
+ <p>This document is not normative. The Working Group expects to evolve
this document further and will eventually publish a stable
- version as a Working Group Note.
+ version as a Working Group Note.</p>
+ <p>Since the previous publication, the document has been vastly reorganized, and adds new use cases, in particular focused on enterprise-level policy configurations.</p>
<p>This document was published by the <a href="http://www.w3.org/2009/dap/">Device APIs and Policy Working Group</a> as a Working Group Note. 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 W3C 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 W3C Patent Policy</a>. The group does not expect this document to become a W3C Recommendation. W3C maintains a <a href="http://ww.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 W3C 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="#web-case" class="tocxref"><span class="secno">2. </span>Web Browser and Untrusted Widgets</a><ul class="toc"><li class="tocline"><a href="#web-case-overview" class="tocxref"><span class="secno">2.1 </span>UseCase Overview</a></li><li class="tocline"><a href="#web-case-rqmts" class="tocxref"><span class="secno">2.2 </span>Requirements</a></li><li class="tocline"><a href="#web-issues" class="tocxref"><span class="secno">2.3 </span>Issues</a></li></ul></li><li class="tocline"><a href="#trusted-widget-case" class="tocxref"><span class="secno">3. </span>Trusted Widget or Application</a><ul class="toc"><li class="tocline"><a href="#widget-case-overview" class="tocxref"><span class="secno">3.1 </span>Use Case Overview</a></li><li class="tocline"><a href="#widget-case-rqmts" class="tocxref"><span class="secno">3.2 </span>Requirements</a></li></ul></li><li class="tocline"><a href="#delegated-authority-case" class="tocxref"><span class="secno">4. </span>Delegated Authority</a><ul class="toc"><li class="tocline"><a href="#delegated-authority-case-overview" class="tocxref"><span class="secno">4.1 </span>Use Case Overview</a></li><li class="tocline"><a href="#delegated-authority-case-rqmts" class="tocxref"><span class="secn">4.2 </span>Requirements</a></li><li class="tocline"><a href="#delegated-authority-case-examples" class="tocxref"><span class="secno">4.3 </span>Policy Examples</a></li></ul></li><li class="tocline"><a href="#threats" class="tocxref"><span class="secno">5. </span>Security and Privacy Threats</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="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocref"><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, 2 September 2010 07:23:54 UTC