W3C home > Mailing lists > Public > public-dap-commits@w3.org > June 2010

2009/dap/privacy-reqs Overview.html,1.23,1.24

From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 23 Jun 2010 18:07:37 +0000
To: public-dap-commits@w3.org
Message-Id: <E1ORUML-000318-SY@lionel-hutz.w3.org>
Update of /sources/public/2009/dap/privacy-reqs
In directory hutz:/tmp/cvs-serv11584

Modified Files:
	Overview.html 
Log Message:
added Alissa and John as editors. Added to sotd re additional work.


Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/privacy-reqs/Overview.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -d -r1.23 -r1.24
--- Overview.html	23 Jun 2010 16:18:33 -0000	1.23
+++ Overview.html	23 Jun 2010 18:07:35 -0000	1.24
@@ -8,10 +8,13 @@
       var respecConfig = {
           specStatus: "ED",
           shortName:            "dap-privacy-reqs",
-            	editors: [{
-    					name: "Frederick Hirsch",
-    					company: "Nokia"
-    				}],
+      editors: [{ name: "Alissa Cooper", 
+      company: "Center for Democracy and Technology", companyURL:
+          "http://www.cdt.org/" }, 
+      { name: "Frederick Hirsch", company: "Nokia", companyURL:
+          "http://www.nokia.com/" },
+      { name: "John Morris", 
+      company: "Center for Democracy and Technology", companyURL: "http://www.cdt.org/" }],
 
 //          publishDate:  "2010-06-29",
           // previousPublishDate:  "1977-03-15",
@@ -29,6 +32,13 @@
       for making device APIs more privacy-friendly. 
     </section> <!-- abstract -->
 
+    <section id='sotd'>
+      This document is expected to be further updated based on both Working
+      Group input and public comments. The Working Group anticipates to
+      eventually publish a stabilized version of this document as a W3C
+      Working Group Note. 
+    </section>
+
     <section id='introduction'>
       <h2>Introduction</h2>
 	<p>Privacy considerations are important to Device APIs, since misuse of information exposed by the APIs can have potentially harmful financial, physical safety, reputational and other impacts. Privacy needs a systemic solution that includes
Received on Wednesday, 23 June 2010 18:07:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 23 June 2010 18:07:39 GMT