- From: Robin Berjon via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 05 Oct 2009 15:47:00 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/api-reqs
In directory hutz:/tmp/cvs-serv2304/api-reqs
Modified Files:
Overview.html
Log Message:
simplified
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/api-reqs/Overview.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- Overview.html 5 Oct 2009 15:43:47 -0000 1.8
+++ Overview.html 5 Oct 2009 15:46:58 -0000 1.9
@@ -92,12 +92,14 @@
<li>This interface MUST enable (web) applications to register themselves as handlers for a specific media type.</li>
<li>A User Agent MAY provide default handlers for a specific media type.</li>
</ul>
+<!--
<section>
<h2>May be considered in future versions</h2>
<p>
Nothing listed at this time.
</p>
</section>
+-->
</section>
<section>
@@ -176,12 +178,14 @@
We could very easily get bogged down in specifying camera capabilities and format feature variants —
how do we decide which ones are reasonably in?
</p>
+<!--
<section>
<h2>May be considered in future versions</h2>
<p>
Nothing listed at this time.
</p>
</section>
+-->
</section>
<section>
@@ -194,12 +198,14 @@
<li>MUST be able to search for events by type (email, phone, SMS...) as well as by content;</li>
<li>MUST be able to expose relevant metadata about events (start and end time, to and from, etc.).</li>
</ul>
+<!--
<section>
<h2>May be considered in future versions</h2>
<p>
Nothing listed at this time.
</p>
</section>
+-->
</section>
<section>
@@ -223,12 +229,14 @@
<p class='issue'>
Do we need support for groups in v1?
</p>
+<!--
<section>
<h2>May be considered in future versions</h2>
<p>
Nothing listed at this time.
</p>
</section>
+-->
</section>
<section>
@@ -259,12 +267,14 @@
<li>SHOULD provide access to a temporary storage location (a form of /tmp directory);</li>
<li>MUST provide some file system metadata (e.g. size, available space, quota).</li>
</ul>
+<!--
<section>
<h2>May be considered in future versions</h2>
<p>
Nothing listed at this time.
</p>
</section>
+-->
</section>
<section>
@@ -287,12 +297,14 @@
accessing well-known parts of the file system, and if the File System API has a way
of exposing sufficient metadata. This could make for a very simple API.
</p>
+<!--
<section>
<h2>May be considered in future versions</h2>
<p>
Nothing listed at this time.
</p>
</section>
+-->
</section>
<section>
@@ -307,12 +319,14 @@
<li>MUST support setting various envelope fields corresponding to the message type (email, SMS...);</li>
<li>MUST support attaching files when the format allows it.</li>
</ul>
+<!--
<section>
<h2>May be considered in future versions</h2>
<p>
Nothing listed at this time.
</p>
</section>
+-->
</section>
<section>
@@ -343,12 +357,14 @@
<li>MUST enable listing vibration capability;</li>
<li>MUST expose the availability of compass and geolocation capability.</li>
</ul>
+<!--
<section>
<h2>May be considered in future versions</h2>
<p>
Nothing listed at this time.
</p>
</section>
+-->
</section>
<section>
@@ -366,12 +382,14 @@
<p class='issue'>
See the <a href='#calendar'>issues that are part of the Calendar API</a>.
</p>
+<!--
<section>
<h2>May be considered in future versions</h2>
<p>
Nothing listed at this time.
</p>
</section>
+-->
</section>
<section>
@@ -388,12 +406,14 @@
levels, and callbacks.
</li>
</ul>
+<!--
<section>
<h2>May be considered in future versions</h2>
<p>
Nothing listed at this time.
</p>
</section>
+-->
</section>
<section class='appendix'>
Received on Monday, 5 October 2009 15:47:04 UTC