- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 25 Aug 2010 15:23:42 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/features
In directory hutz:/tmp/cvs-serv8914
Modified Files:
Overview.html
Log Message:
add warning regarding use of examples, per ACTION-262. Remove empty
capability sub-sections.
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/features/Overview.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- Overview.html 25 Aug 2010 13:55:04 -0000 1.22
+++ Overview.html 25 Aug 2010 15:23:40 -0000 1.23
@@ -2,17 +2,17 @@
<html>
<head>
<title>Device API Features and Capabilities</title> <meta
- http-equiv='Content-Type'
- content='text/html;charset=utf-8'/> <script src='../ReSpec.js/js/respec.js'
- class='remove'></script> <script class='remove'>
+ http-equiv='Content-Type'
+ content='text/html;charset=utf-8'/> <script src='../ReSpec.js/js/respec.js'
+ class='remove'></script> <script class='remove'>
var respecConfig = { specStatus: "ED",
shortName: "dap-api-features",
[...1698 lines suppressed...]
+ <p class="issue">Define features, capabilities as URIs, strings, both</p>
+ <p class="issue">
+ Features defined according to CRUD, one feature for Create,
+ Read, Update, Delete?
+ </p>
+ <p class="issue">
+ Feature parameters to avoid explosion of capabilities and
+ features? e.g. file open with either read or write
+ parameter.
+ ( see
+ <a href="http://lists.w3.org/Archives/Public/public-device-apis/2009Oct/att-0120/minutes-2009-10-07.html#item03">discussions
+ in minutes of October 7 call</a> )
+ </p>
- </section> <!-- delegated authority issues -->
+ </section> <!-- delegated authority issues -->
-</body>
+ </body>
</html>
Received on Wednesday, 25 August 2010 15:23:43 UTC