W3C home > Mailing lists > Public > public-dap-commits@w3.org > April 2011

2009/dap/calendar FPWD.html,1.4,1.5

From: Dominique Hazael-Massieux via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 15 Apr 2011 14:31:27 +0000
To: public-dap-commits@w3.org
Message-Id: <E1QAk3T-0001mO-Qh@lionel-hutz.w3.org>
Update of /sources/public/2009/dap/calendar
In directory hutz:/tmp/cvs-serv6809

Modified Files:
	FPWD.html 
Log Message:
added customized paragraph


Index: FPWD.html
===================================================================
RCS file: /sources/public/2009/dap/calendar/FPWD.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- FPWD.html	6 Apr 2011 16:11:46 -0000	1.4
+++ FPWD.html	15 Apr 2011 14:31:25 -0000	1.5
@@ -530,7 +530,9 @@
                <li>A <a class="idlType" href="#idl-def-Calendar"><code>Calendar</code></a> interface, which provides the method needed to access to a user's unified calendar.</li>
                <li>A <a class="idlType" href="#idl-def-CalendarEvent"><code>CalendarEvent</code></a> interface, which provides the individual calendar information of type EVENT that may be returned following a successful read operation.</li>
             </ul>
-        </div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p><p>This document was published by the <a href="http://www.w3.org/2009/dap/">Device APIs and Policy Working Group</a> as a First Public Working Draft. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to <a href="mailto:public-device-apis@w3.org">public-device-apis@w3.org</a> (<a href="mailto:public-device-apis-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-device-apis/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/43696/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p></div><div class="section" id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#introduction"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#scope"><span class="secno">1.1 </span>Scope</a></li><li class="tocline"><a class="tocxref" href="#usage-example"><span class="secno">1.2 </span>Usage Example</a></li></ul></li><li class="tocline"><a class="tocxref" href="#conformance"><span class="secno">2. </span>Conformance</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#terminology"><span class="secno">2.1 </span>
+        </div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
+<p>This is the first publication of this document by by the <a href="http://www.w3.org/2009/dap/">Device APIs and Policy Working Group</a> as a  Working Draft. The approach proposed for this API is very similar to the one taken in the <a href="http://www.w3.org/TR/contacts-api/">Contacts API</a>. The known issues in the document are highlighted below, and concern in particular the management of timezones and recurrence.</p>
+<p>This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to <a href="mailto:public-device-apis@w3.org">public-device-apis@w3.org</a> (<a href="mailto:public-device-apis-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-device-apis/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/43696/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p></div><div class="section" id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#introduction"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#scope"><span class="secno">1.1 </span>Scope</a></li><li class="tocline"><a class="tocxref" href="#usage-example"><span class="secno">1.2 </span>Usage Example</a></li></ul></li><li class="tocline"><a class="tocxref" href="#conformance"><span class="secno">2. </span>Conformance</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#terminology"><span class="secno">2.1 </span>
                 Terminology
               </a></li></ul></li><li class="tocline"><a class="tocxref" href="#security-and-privacy-considerations"><span class="secno">3. </span>Security and Privacy Considerations</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#privacy-considerations-for-implementors-of-the-calendar-api"><span class="secno">3.1 </span>Privacy considerations for implementors of the Calendar API</a></li><li class="tocline"><a class="tocxref" href="#privacy-considerations-for-recipients-of-calendar-information"><span class="secno">3.2 </span>Privacy considerations for recipients of calendar information</a></li><li class="tocline"><a class="tocxref" href="#additional-implementation-considerations"><span class="secno">3.3 </span>Additional implementation considerations</a></li></ul></li><li class="tocline"><a class="tocxref" href="#api-description"><span class="secno">4. </span>API Description</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#servicecalendar-interface"><span class="secno">4.1 </span><span class="idlType formerLink idlType"><code>ServiceCalendar</code></span> interface</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#attributes"><span class="secno">4.1.1 </span>Attributes</a></li></ul></li><li class="tocline"><a class="tocxref" href="#calendar-interface"><span class="secno">4.2 </span><span class="idlType formerLink idlType"><code>Calendar</code></span> interface</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#methods"><span class="secno">4.2.1 </span>Methods</a></li></ul></li><li class="tocline"><a class="tocxref" href="#calendarevent-interface"><span class="secno">4.3 </span><span class="idlType formerLink idlType"><code>CalendarEvent</code></span> interface</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#attributes-1"><span class="secno">4.3.1 </span>Attributes</a></li></ul></li><li class="tocline"><a class="tocxref" href="#calendarrepeatrule-interface"><span class="secno">4.4 </span><span class="idlType formerLink idlType"><code>CalendarRepeatRule</code></span> interface</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#attributes-2"><span class="secno">4.4.1 </span>Attributes</a></li></ul></li><li class="tocline"><a class="tocxref" href="#calendarfindoptions-interface"><span class="secno">4.5 </span><span class="idlType formerLink idlType"><code>CalendarFindOptions</code></span> interface</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#attributes-3"><span class="secno">4.5.1 </span>Attributes</a></li></ul></li><li class="tocline"><a class="tocxref" href="#calendareventfilter-interface"><span class="secno">4.6 </span><span class="idlType formerLink idlType"><code>CalendarEventFilter</code></span> interface</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#attributes-4"><span class="secno">4.6.1 </span>Attributes</a></li></ul></li><li class="tocline"><a class="tocxref" href="#calendareventsuccesscb-interface"><span class="secno">4.7 </span><span class="idlType formerLink idlType"><code>CalendarEventSuccessCB</code></span> interface</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#methods-1"><span class="secno">4.7.1 </span>Methods</a></li><li class="tocline"><a class="tocxref" href="#event-handler-attributes"><span class="secno">4.7.2 </span>
                      Event Handler Attributes
@@ -1760,4 +1762,4 @@
 </dd><dt id="bib-FILE-WRITER">[FILE-WRITER]</dt><dd>Eric Uhrhane. <a href="http://dev.w3.org/2009/dap/file-system/file-writer.html"><cite>File Writer API.</cite></a> W3C Working Draft. (Work in progress.) URL: <a href="http://dev.w3.org/2009/dap/file-system/file-writer.html">http://dev.w3.org/2009/dap/file-system/file-writer.html</a> 
 </dd><dt id="bib-NAVIGATOR">[NAVIGATOR]</dt><dd>Ian Hickson, David Hyatt. <a href="http://dev.w3.org/html5/spec/timers.html#navigator"><cite>Navigator interface in HTML5</cite></a>, Editors draft (Work in progress). URL: <a href="http://dev.w3.org/html5/spec/timers.html#navigator">http://dev.w3.org/html5/spec/timers.html#navigator</a> 
 </dd><dt id="bib-RFC5545">[RFC5545]</dt><dd>B. Desruisseaux. <a href="http://www.rfc-editor.org/rfc/rfc5545.txt"><cite>Internet Calendaring and Scheduling Core Object Specification (iCalendar).</cite></a> September 2009. Internet RFC 5545. URL: <a href="http://www.rfc-editor.org/rfc/rfc5545.txt">http://www.rfc-editor.org/rfc/rfc5545.txt</a> 
-</dd></dl></div></div></body></html>
\ No newline at end of file
+</dd></dl></div></div></body></html>
Received on Friday, 15 April 2011 14:31:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 15 April 2011 14:31:32 GMT