2009/dap/system-info Overview.html,1.41,1.42

Update of /sources/public/2009/dap/system-info
In directory hutz:/tmp/cvs-serv25009

Modified Files:
	Overview.html 
Log Message:
-abstract and status
-editorial:  requirements and use cases merged
- privacy section (from Contacts, mutatis mutandis)
- formally defined property and how URI, Name and interface name relate
- extensibiloty section
- sorted out readonly and readwrite attributes


Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/system-info/Overview.html,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -d -r1.41 -r1.42
--- Overview.html	16 Dec 2009 09:32:29 -0000	1.41
+++ Overview.html	16 Dec 2009 13:04:44 -0000	1.42
@@ -23,73 +23,204 @@
   </head>
   <body>
     <section id='abstract'>
-      <p class="issue">Flesh out: A proposal for the Device API and Policy
-(DAP) Working Group's System Information API.</p>
+      <p>This specification defines an API to provide Web applications
+      with access to various properties of the system which they are
+      running on. Specifically, properties pertaining to the device
+      hardware are addressed. Examples include battery status,
+      current network bandwidth. Additionally, some of those
+      properties offer access to the environment around the device,
[...1806 lines suppressed...]
-          and adapts by enabling predictive text to reduce the number of keystrokes that the user
-          needs to enter.</dd>
-          <dt>Application detects the presence of mouse hover events</dt>
-          <dd>A user who regularly visits an online video editing and sharing website on his phone 
-          decides to try a larger project on his laptop computer with an HD home video. He expects
-          to see the same simplified UI, but is pleasantly surprised to find a UI that is more
-          appropriate for the laptop paradigm. However, because the UI is more complex, there
-          is a lot of functionality that he does not know how to use. Fortunately, the application
-          detect that the user is on a system with mouse in/out/hover events, and so it uses those
-          events to familiarize the user with the new functionality.</dd>
-        </dl>
-      </section>
-    </section>
+    <!--************************************* /Requirements ******************************************-->
 
     <!--************************************* Acks ***************************************************-->
-      
     <section class='appendix'>
       <h3>Acknowledgements</h3>
       <p>

Received on Wednesday, 16 December 2009 13:04:58 UTC