- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 13 Jan 2011 18:00:52 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/policy-reqs
In directory hutz:/tmp/cvs-serv17729
Modified Files:
Overview.html
Log Message:
reflect changes for publication, e.g. previous version etc
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/policy-reqs/Overview.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -d -r1.56 -r1.57
--- Overview.html 7 Jan 2011 20:26:33 -0000 1.56
+++ Overview.html 13 Jan 2011 18:00:50 -0000 1.57
@@ -38,7 +38,8 @@
{name: "Dominique Hazaël-Massieux", company: "W3C"}
],
// publishDate: "2010-06-29",
- // previousPublishDate: "1977-03-15",
+ previousPublishDate: "2010-06-29",
+ previousMaturity: "NOTE",
edDraftURI: "http://dev.w3.org/2009/dap/policy-reqs/",
// lcEnd: "2009-08-05",
noRecTrack: true,
@@ -48,13 +49,22 @@
</head>
<body>
<section id='abstract'>
- With the emergence of numerous new APIs in Web browsers and runtime engines, the need to control which Web sites and applications can make use of these APIs increases. This document describes use cases and requirements for controlling access to these APIs.
+ With the emergence of numerous new APIs in Web browsers and
+ runtime engines, the need to control which Web sites and
+ applications can make use of these APIs increases. This document
+ describes use cases and requirements for controlling access to
+ these APIs.
</section> <!-- abstract -->
<section id='sotd'>
This document is not normative. The Working Group expects to evolve
this document further and will eventually publish a stable
- version as a Working Group Note.
+ version as a Working Group Note. This version is an update of
+ the previous version of his note, modified to present the material
+ using "user
+ stories" and associating requirements with those use cases. This
+ version also adds informative references and is revised to not
+ assume a specific mechanism to meet the requirements.
</section>
<section id='introduction' class='informative'>
Received on Thursday, 13 January 2011 18:00:54 UTC