- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 02 Oct 2012 20:46:35 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/calendar
In directory hutz:/tmp/cvs-serv19523
Modified Files:
Overview.html
Log Message:
shelve calendar. Change back from WD to ED, add warning note
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/calendar/Overview.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -d -r1.28 -r1.29
--- Overview.html 5 May 2011 16:17:26 -0000 1.28
+++ Overview.html 2 Oct 2012 20:46:33 -0000 1.29
@@ -7,7 +7,7 @@
<script src='../ReSpec.js/js/sh_main.min.js' class='remove'></script>
<script class='remove'>
var respecConfig = {
- specStatus: "FPWD",
+ specStatus: "ED",
shortName: "calendar-api",
editors: [{
name: "Richard Tibbett",
@@ -20,7 +20,7 @@
company: "Research in Motion (RIM)",
companyURL: "http://www.rim.com/"
}],
- publishDate: "2011-04-19",
+ // publishDate: "2011-04-19",
//previousPublishDate: "2011-01-11",
edDraftURI: "http://dev.w3.org/2009/dap/calendar/",
//lcEnd: "2011-08-01",
@@ -75,6 +75,15 @@
</style>
</head>
<body>
+ <p style="background: black; color: white; font: 900 1.2em serif; padding: 0.5em 1em; border: dotted yellow 0.3em;">
+ The Device APIs Working Group is currently not pursuing the approach
+ outlined in this draft, so it should be considered historical.
+ Please treat this document with caution and do not reference it or use
+ it as the basis for implementation. The domain covered by this document is
+ still within the scope of the Working Group as defined in its Charter.
+ The Working Group may pursue an alternative API design that is based on
+ the current Web browser security model.
+ </p>
<section id='abstract'>
<p>
The Calendar API defines the high-level interfaces required to obtain read access to a user's calendaring service.
Received on Tuesday, 2 October 2012 20:46:37 UTC