- From: Dominique Hazael-Massieux via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 05 Jan 2011 14:28:15 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/api-reqs
In directory hutz:/tmp/cvs-serv22246
Modified Files:
Overview.html
Log Message:
editing wrapping; core work on ACTION-281 still needs to be done (and that's a lot)
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/api-reqs/Overview.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- Overview.html 7 Oct 2009 15:37:09 -0000 1.12
+++ Overview.html 5 Jan 2011 14:28:12 -0000 1.13
@@ -6,46 +6,34 @@
<script src='../ReSpec.js/js/respec.js' class='remove'></script>
<script class='remove'>
var respecConfig = {
- specStatus: "WG-NOTE",
+ specStatus: "ED",
shortName: "dap-api-reqs",
- publishDate: "2009-10-08",
- // previousPublishDate: "1977-03-15",
+ // publishDate: "2009-10-08",
+ previousPublishDate: "2009-10-15",
+ previousMaturity: "NOTE",
edDraftURI: "http://dev.w3.org/2009/dap/api-reqs/",
// lcEnd: "2009-08-05",
+ editors: [{name: "Dominique Hazaël-Massieux", company: "W3C"}]
};
</script>
<script src='../common/config.js' class='remove'></script>
- <script class='remove'>
- respecConfig.editors.splice(-1, 0,
- { name: "Bryan Sullivan",
- company: "AT&T",
- companyURL: "http://att.com/" })
- </script>
</head>
<body>
<section id='abstract'>
- These are the requirements for the API work undertaken by the DAP WG, both applying to
- all APIs and to each one individually.
+ This document summarizes the requirements and design decisions for the API work undertaken by the Device APIs and Policy Working Group.
</section>
<section class='informative'>
<h2>Introduction</h2>
- <p>
- The requirements in this document are produced in a high-level, functionally oriented
- fashion in order to provide sufficient ground on which to build without going through
- the full landscape analysis process given that the APIs being produced concern domains
- in which industry experience is already solid.
- </p>
- <p>
- This document is not currently considered to be complete, but rather represents a
- snapshot of the DAP WG's thinking at the time of its publication.
+ <p>In the process of defining the APIs on which the Device APIs and Policy Working Group is chartered to produce, the group has identified a number of requirements that these APIs need to follow, as well as made a number of design decisions.</p>
+ <p>This document summarizes these requirements and design decisions, both to help evaluating the APIs the Working Group produces, and to serve as input to others who would want to write similar APIs.</p>
+ <p>This document is not currently considered to be complete, but rather represents a snapshot of the DAP WG's thinking at the time of its publication.
</p>
</section>
<section>
<h2>Global Requirements</h2>
- <p>
- These requirements apply to all APIs produced by the DAP WG.
+ <p>These requirements apply to all APIs produced by the DAP WG.
</p>
<ul>
<li>APIs MUST be made available in a consistent fashion, hanging off a single access point;</li>
@@ -423,12 +411,5 @@
-->
</section>
- <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, 5 January 2011 14:28:17 UTC