- From: CVS User akostiai <cvsmail@w3.org>
- Date: Wed, 08 Jan 2014 13:32:14 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/calendar
In directory roscoe:/tmp/cvs-serv27333/calendar
Modified Files:
NOTE.html NOTE.src.html
Log Message:
change publishDate to 2013-01-14; add HTML snapshots
--- /sources/public/2009/dap/calendar/NOTE.html 2013/12/30 11:10:58 1.2
+++ /sources/public/2009/dap/calendar/NOTE.html 2014/01/08 13:32:14 1.3
@@ -123,11 +123,11 @@
</p>
<h1 class="title p-name" id="title" property="dcterms:title">Calendar API</h1>
- <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-01-08T22:00:00.000Z" id="w3c-working-group-note-09-january-2014"><abbr title="World Wide Web Consortium">W3C</abbr> Working Group Note <time class="dt-published" datetime="2014-01-09">09 January 2014</time></h2>
+ <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-01-13T22:00:00.000Z" id="w3c-working-group-note-14-january-2014"><abbr title="World Wide Web Consortium">W3C</abbr> Working Group Note <time class="dt-published" datetime="2014-01-14">14 January 2014</time></h2>
<dl>
<dt>This version:</dt>
- <dd><a class="u-url" href="http://www.w3.org/TR/2014/NOTE-calendar-api-20140109/">http://www.w3.org/TR/2014/NOTE-calendar-api-20140109/</a></dd>
+ <dd><a class="u-url" href="http://www.w3.org/TR/2014/NOTE-calendar-api-20140114/">http://www.w3.org/TR/2014/NOTE-calendar-api-20140114/</a></dd>
<dt>Latest published version:</dt>
<dd><a href="http://www.w3.org/TR/calendar-api/">http://www.w3.org/TR/calendar-api/</a></dd>
@@ -199,9 +199,25 @@
</strong>
</p>
<p>
- This is a historical document. The domain covered by this document
- is still within the scope of the Working Group as defined in its
- Charter.
+ The Calendar API was intended to enable API access to a user's calendar
+ information. The
+ <a href="http://www.w3.org/2009/dap/">Device APIs Working Group</a>
+ worked on both the calendar data format and calendar interfaces but
+ then decided to change the approach to enable general Web use both to
+ address security concerns and to enable wider use in a web context. The
+ <a href="http://lists.w3.org/Archives/Public/public-device-apis/2012Sep/0097.html">
+ plan was to learn from developing the Contacts API</a> and apply this
+ work to the Calendar API. The Contacts API was revised to use
+ <a href="http://www.w3.org/TR/web-intents/">Web
+ Intents</a> and then discontinued when Web Intents work was stopped.
+ Subsequently work on the Calendar API was also discontinued following
+ a Working Group
+ <a href="http://lists.w3.org/Archives/Public/public-device-apis/2012Sep/att-0131/minutes-2012-09-26.html#item07">decision</a>.
+ </p>
+ <p>
+ The Charter of the <a href="http://www.w3.org/2009/dap/">Device APIs Working Group</a>
+ continues to include this work as "in scope", so the working group
+ could decide to resume work if warranted by new information.
</p>
<p>
--- /sources/public/2009/dap/calendar/NOTE.src.html 2013/12/31 12:36:24 1.3
+++ /sources/public/2009/dap/calendar/NOTE.src.html 2014/01/08 13:32:14 1.4
@@ -8,7 +8,7 @@
var respecConfig = {
shortName: "calendar-api",
specStatus: "WG-NOTE",
- publishDate: "2014-01-09",
+ publishDate: "2014-01-14",
previousMaturity: "FPWD",
previousPublishDate: "2011-04-19",
editors: [
Received on Wednesday, 8 January 2014 13:32:15 UTC