- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 18 Aug 2010 14:42:06 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/policy-reqs
In directory hutz:/tmp/cvs-serv3561
Modified Files:
Overview.html
Log Message:
update with proposal as agreed on WG teleconference, 18
August. Removed "un-managed" for web browser case.
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/policy-reqs/Overview.html,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -d -r1.41 -r1.42
--- Overview.html 24 Jun 2010 07:07:54 -0000 1.41
+++ Overview.html 18 Aug 2010 14:42:03 -0000 1.42
@@ -1,26 +1,36 @@
<!DOCTYPE html>
<html>
<head>
- <title>Device API Access Control Requirements</title>
+ <title>Device API Access Control Use Cases and Requirements</title>
<meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
- <script src='http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js' class='remove'></script>
+ <script src='http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js' class='remove'></script>
+<!-- <script src='../ReSpec.js/js/respec.js' class='remove'></script> -->
<script class='remove'>
var respecConfig = {
[...1299 lines suppressed...]
+ exhaustive. Alongside the device-API specific examples
+ above, we still
+ need to consider traditional web threats which pose a
+ significant risk
+and lots of other types of attack which should be considered in a
+ formal threat model.
+ </p>
+ </section> <!-- phishing -->
+ </section> <!-- threats -->
+
+ <section class='appendix'>
+ <h2>Acknowledgements</h2>
+ <p>
+ The editors would like to extend special thanks to Nokia, OMTP
+ BONDI, and PhoneGap for providing
+ the foundation of the working group's requirements discussion.
+ </p>
+ </section>
+ </body>
+ </html>
Received on Wednesday, 18 August 2010 14:42:07 UTC