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

2009/dap/calendar Overview.html,1.15,1.16

From: Dominique Hazael-Massieux via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 01 Feb 2011 16:22:31 +0000
To: public-dap-commits@w3.org
Message-Id: <E1PkIzv-0004Bt-F4@lionel-hutz.w3.org>
Update of /sources/public/2009/dap/calendar
In directory hutz:/tmp/cvs-serv16093

Modified Files:
	Overview.html 
Log Message:
aligning with contacts api


Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/calendar/Overview.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- Overview.html	11 Jan 2011 15:11:07 -0000	1.15
+++ Overview.html	1 Feb 2011 16:22:29 -0000	1.16
@@ -86,30 +86,7 @@
                <li>A <a href="#calendar-interface"<code>Calendar</code></a> interface, which provides the method needed to access to a user's unified calendar.</li>
                <li>A <a href="#calendarevent-interface"<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>
-            <p>
-              A set of <a href="#security-and-privacy-considerations">Security and Privacy Considerations</a> are presented for the discretion of both 
-              implementors of the Calendar API and recipients of calendaring information (i.e. web pages). This specification provides a set of non-normative 
-              <a href="#user-interaction-guidelines">User Interaction Guidelines</a> demonstrating an example user experience that is compliant with the Security and Privacy Considerations
-              provided herein.
-            </p>
-            <p>
-              This specification also provides normative guidelines for manipulating a user&#39;s unified calendar, to 
-              <a href="#adding-and-updating-calendar-events">add and update calendar events</a>, utilising existing web platform APIs and negating the need for such mechanisms to be 
-              provided as part of a specialized Calendar API.
-            </p>
         </section>
-        <section id='conformance'> 
-            <p> 
-                This specification defines conformance criteria that apply to a single product: the
-                <dfn> 
-                    user agent
-                </dfn> 
-                that implements the interfaces that it contains.
-            </p> 
-			<p>Implementations that use ECMAScript to implement the APIs defined in this specification must implement them in a manner 
-			consistent with the ECMAScript Bindings defined in the Web IDL specification [[!WEBIDL]], as this specification uses that 
-			specification’s terminology.</p> 
-        </section> 
         <section class="informative">
             <h2>Introduction</h2>
             <p>
@@ -118,10 +95,39 @@
 			<p>The API itself is designed to be agnostic of any underlying calendaring service sources.</p>
 	
             <p>
+              A set of <a href="#security-and-privacy-considerations">Security and Privacy Considerations</a> are presented for the discretion of both 
+              implementors of the Calendar API and recipients of calendaring information (i.e. web pages). This specification provides a set of non-normative 
+              <a href="#user-interaction-guidelines">User Interaction Guidelines</a> demonstrating an example user experience that is compliant with the Security and Privacy Considerations
+              provided herein.
+            </p>
+            <p>
+              This specification also provides informative examples illustrating how to   <a href="#adding-and-updating-calendar-events">add and update calendar events</a>, utilising existing web platform APIs.
+            </p>
+
+		<section class="informative">
+            <h2>Scope</h2>
+            <p>
                 The requirements for this set of interfaces are listed in the Device API Requirements
                 document [[DAP-REQS]].
             </p>
-            
+			
+			<p>
+				The API provided in this specification is limited to providing a programmatic way to retrieve Calendar information. 
+			</p>
+			
+			<p>
+				The scope of this specification does not include the ability to attach Contacts to Calendar Events or vice versa. This denotes cross-API dependency and the intention 
+				of this specification is to provide a standalone API for the provision and management of Calendar Event information.
+			</p>
+
+			<p>
+				This specification requires that formatting for 
+				all dates and times be applied according to the definition of <dfn id="dfn-valid-date-or-time-string"><a href="http://dev.w3.org/html5/spec/Overview.html#valid-date-or-time-string">valid date and time string</a></dfn> in [[!HTML5]].
+			</p>
+						
+		</section>
+		<section>
+		  <h2>Usage Example</h2>
                <div
        class="example">
         <p>
@@ -153,6 +159,49 @@
 // ..is equivalent to: navigator.service.calendar(/* parameters */)
 </pre>
       </div>
+</section>      	
+		</section>
+        <section id='conformance'> 
+            <p> 
+                This specification defines conformance criteria that apply to a single product: the
+                <dfn> 
+                    user agent
+                </dfn> 
+                that implements the interfaces that it contains.
+            </p> 
+			<p>Implementations that use ECMAScript to implement the APIs defined in this specification must implement them in a manner 
+			consistent with the ECMAScript Bindings defined in the Web IDL specification [[!WEBIDL]], as this specification uses that 
+			specification’s terminology.</p> 
+		    <section>
+              <h2>
+                Terminology
+              </h2>
+              <p>
+                The terms <dfn>document base URL</dfn>, <dfn>browsing context</dfn>, <dfn
+                 title="event handler attribute">event handler attributes</dfn>, <dfn>event handler event type</dfn>, <dfn>task</dfn>, <dfn>task
+                source</dfn> and <dfn>task queues</dfn> are defined by the HTML5 specification [[!HTML5]].
+              </p>
+              <p>
+                The <a>task source</a> used by this specification is the <dfn><a
+                 href="http://dev.w3.org/2009/dap/device/#the-pendingop-interface">PendingOp</a> task source</dfn>.
+              </p>
+              
+              <p class="note">
+               PendingOp needs updating in [[!CORE-DEVICE]] to show that it is a valid <a>task source</a>.
+              </p>
+              <p>
+                To <dfn>dispatch a <code>success</code> event</dfn> means that an event with the name <code>success</code>, which does
+                not bubble and is not cancelable, and which uses the <code>Event</code> interface, is to be dispatched at the <a
+                 href="#contactfindcb-interface"><code>ContactFindCB</code></a> object.
+              </p>
+              <p>
+                To <dfn>dispatch an <code>error</code> event</dfn> means that an event with the name <code>error</code>, which does
+                not bubble and is not cancelable, and which uses the <code>Event</code> interface, is to be dispatched at the <a
+                 href="#contacterrorcb-interface"><code>ContactErrorCB</code></a> object.
+              </p>
+            </section>
+
+        </section> 
             
            <!--  <section>
                 <h2>Usage Examples</h2>
@@ -252,59 +301,7 @@
 
 
             </section>  -->
-		    <section>
-              <h2>
-                Terminology
-              </h2>
-              <p>
-                The terms <dfn>document base URL</dfn>, <dfn>browsing context</dfn>, <dfn
-                 title="event handler attribute">event handler attributes</dfn>, <dfn>event handler event type</dfn>, <dfn>task</dfn>, <dfn>task
-                source</dfn> and <dfn>task queues</dfn> are defined by the HTML5 specification [[!HTML5]].
-              </p>
-              <p>
-                The <a>task source</a> used by this specification is the <dfn><a
-                 href="http://dev.w3.org/2009/dap/device/#the-pendingop-interface">PendingOp</a> task source</dfn>.
-              </p>
-              
-              <p class="note">
-               PendingOp needs updating in [[!CORE-DEVICE]] to show that it is a valid <a>task source</a>.
-              </p>
-              <p>
-                To <dfn>dispatch a <code>success</code> event</dfn> means that an event with the name <code>success</code>, which does
-                not bubble and is not cancelable, and which uses the <code>Event</code> interface, is to be dispatched at the <a
-                 href="#contactfindcb-interface"><code>ContactFindCB</code></a> object.
-              </p>
-              <p>
-                To <dfn>dispatch an <code>error</code> event</dfn> means that an event with the name <code>error</code>, which does
-                not bubble and is not cancelable, and which uses the <code>Event</code> interface, is to be dispatched at the <a
-                 href="#contacterrorcb-interface"><code>ContactErrorCB</code></a> object.
-              </p>
-            </section>
-      	
-		</section>
 		
-		<section class="informative">
-            <h2>Scope</h2>
-			
-			<p>
-				The API provided in this specification is limited to providing a programmatic way to retrieve Calendar information. 
-			</p>
-			
-			<p>
-				The scope of this specification does not include the ability to attach Contacts to Calendar Events or vice versa. This denotes cross-API dependency and the intention 
-				of this specification is to provide a standalone API for the provision and management of Calendar Event information.
-			</p>
-
-			<p>
-				This specification requires that formatting for 
-				all dates and times be applied according to the defintion of <dfn id="dfn-valid-date-or-time-string">valid date and time string</dfn> in [[!HTML5]].
-			</p>
-			
-			<p class='note'>
-				See: <a href="http://dev.w3.org/html5/spec/Overview.html#valid-date-or-time-string">http://dev.w3.org/html5/spec/Overview.html#valid-date-or-time-string</a>
-			</p>
-						
-		</section>
 
         <section>
             <h2>Security and Privacy Considerations</h2>
@@ -324,7 +321,7 @@
 				removable without the user's express permission.
 			</p>
 								
-			<section>
+			<section class="normative">
 				<h2>Privacy considerations for implementors of the Calendar API</h2>
 				
 				<p>
@@ -351,27 +348,27 @@
 				</p>								
 			</section>
 
-			<section>
+			<section class="informative">
 				<h2>Privacy considerations for recipients of calendar information</h2>
 
 				<p>
-					Recipients MUST only request calendar information when necessary. Recipients MUST only use the calendar information for 
-					the task for which it was provided to them. Recipients MUST dispose of calendar information once that task is completed, 
-					unless expressly permitted to retain it by the user. Recipients MUST also take measures to protect this information 
+					Recipients should take care to only request calendar information when necessary, and only use the calendar information for 
+					the task for which it was provided to them. Recipients are invited to dispose of calendar information once that task is completed, 
+					unless expressly permitted to retain it by the user, and to take measures to protect this information 
 					against unauthorized access. If calendar information is stored, users should be allowed to update and delete this 
 					information.
 				</p>
 				
 				<p>
-					The recipient of calendar information MUST not retransmit the calendar information without the user’s express permission. 
+					The recipient of calendar information should not retransmit the calendar information without the user’s express permission. 
 					Care should be taken when retransmitting and use of encryption is encouraged.
 				</p>
 
 				<p>
-					Recipients MUST clearly and conspicuously disclose the fact that they are collecting calendar data, the purpose for the 
+					Recipients should clearly and conspicuously disclose the fact that they are collecting calendar data, the purpose for the 
 					collection, how long the data is retained, how the data is secured, how the data is shared if it is shared, how users 
 					can access, update and delete the data, and any other choices that users have with respect to the data. This disclosure 
-					MUST include an explanation of any exceptions to the guidelines listed above.
+					should include an explanation of any exceptions to the guidelines listed above.
 				</p>				
 			</section>
 			
@@ -1200,7 +1197,7 @@
 
     </section>
     
-    <section>
+    <section class="informative appendix">
       <h2>Adding and Updating Calendar Events</h2>
       
       <p>
Received on Tuesday, 1 February 2011 16:22:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 1 February 2011 16:22:33 GMT