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

2009/dap/contacts Overview.html,1.117,1.118

From: Robin Berjon via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 06 Apr 2011 12:50:03 +0000
To: public-dap-commits@w3.org
Message-Id: <E1Q7SBP-0000lN-UX@lionel-hutz.w3.org>
Update of /sources/public/2009/dap/contacts
In directory hutz:/tmp/cvs-serv2916/contacts

Modified Files:
	Overview.html 
Log Message:
editorials, section 1

Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/contacts/Overview.html,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -d -r1.117 -r1.118
--- Overview.html	6 Apr 2011 12:31:45 -0000	1.117
+++ Overview.html	6 Apr 2011 12:50:01 -0000	1.118
@@ -68,7 +68,7 @@
       IDL wrapping fix
       http://perishablepress.com/press/2010/06/01/wrapping-content/
       */
-      pre {
+      pre.idl {
           white-space: pre;           /* CSS 2.0 */
           white-space: pre-wrap;      /* CSS 2.1 */
           white-space: pre-line;      /* CSS 3.0 */
@@ -84,101 +84,85 @@
   <body>
     <section id='abstract'>
       <p>
-      The Contacts API defines the high-level interfaces required to obtain read access to a user's unified
-      address book.
+        The Contacts API defines the high-level interfaces required to obtain read access to a user's unified
+        address book.
       </p>
-
       <p>
-      This API includes the following key interfaces:
+        This API includes the following key interfaces:
       </p>
-
       <ul>
-        <li>A <a href="#contacts-interface"><code>Contacts</code></a> interface, which provides the method
-        needed to access to a user's unified address book.</li>
-
-        <li>A <a href="#contact-interface"><code>Contact</code></a> interface, which provides the individual
+        <li>A <a>Contacts</a> interface, which provides the method
+        needed to access a user's unified address book.</li>
+        <li>A <a>Contact</a> interface, which captures the individual
         contact information that can be returned following a successful read operation.</li>
       </ul>
     </section>
 
     <section id='sotd'>
       <p>
-      This document represents the early consensus of the group on the scope and features of the proposed
-      Contacts API. Issues and editors note in the document highlight some of the points on which the group is
-      still working and would particularly like to get feedback.
+        This document represents the early consensus of the group on the scope and features of the proposed
+        Contacts API. Issues and editors note in the document highlight some of the points on which the group is
+        still working and would particularly like to get feedback.
       </p>
     </section>
 
     <section class="informative">
       <h2>Introduction</h2>
-
       <p>
-      Every operating system and a large number of web-based service providers have different ways of
-      representing address book information. Most users are required to maintain a plurality of contact lists
-      which leads to multiple copies of address book data. The multiplicity of address books that a user is
-      required to maintain often leads to disjointed and inconsistent information being stored across a user's
-      address book providers.
+        Every operating system and a large number of web-based service providers have different ways of
+        representing address book information. Most users are required to maintain a plurality of contact lists
+        which leads to multiple copies of address book data. This in turn
+        often leads to disjointed and inconsistent information being stored across a user's
+        address book providers.
       </p>
-
       <p>
-      Providing address book information to these service providers means handing over all of your data and
-      trusting these providers with the security and privacy of storing and sharing of your information. When
-      sharing this data with third parties users are, more often than not, required to hand over access to
-      their whole address book. Users are implicitly required to trust third parties with all of their data
-      when, in reality, the user may only wish, or need, to share a subset of their address book information so
-      that an application can fulfill its purpose.
+        When sharing contact data with third parties users are, more often than not, required to hand over access to
+        their whole address book. Users are implicitly required to trust third parties with all of their data
+        when, in reality, the user may only wish, or need, to share a subset of their address book information so
+        that an application can fulfil its purpose.
       </p>
-
       <p>
-      This specification defines the concept of a user's unified address book - where address book data may
-      be sourced from a plurality of sources - both online and locally. This specification then defines the
-      interfaces on which third party applications can access a user's unified address book, with explicit user
-      permission and filtering. The focus of this data sharing is on making the user aware of the data that
-      they will share and putting them at the center of the data sharing process; free to select both the
-      extent to which they share their address book information and the ability to restrict which pieces of
-      information related to which contact gets shared.
+        This specification defines the concept of a user's unified address book - where address book data may
+        be sourced from a plurality of sources - both online and locally. It then defines the
+        interfaces through which third party applications can access a user's unified address book, with explicit user
+        permission and filtering. The focus of this data sharing is on making the user aware of the data that
+        they will share and putting them at the centre of the data sharing process; free to select both the
+        extent to which they share their address book information and the ability to restrict which pieces of
+        information related to which contact gets shared.
       </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 Contacts API and recipients of contact
-      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.
+        A set of <a href="#security-and-privacy-considerations">Security and Privacy Considerations</a> are
+        presented for the discretion of both implementors of the Contacts API and recipients of contact
+        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 described herein.
       </p>
-
       <p>
-      This specification also provides informative examples illustrating how to <a href=
-      "#adding-and-updating-contacts">add and update contact information</a>, utilising existing web platform
-      APIs.
+        This specification also provides informative examples illustrating how to 
+        <a href="#adding-and-updating-contacts">add and update contact information</a>, utilising existing web platform
+        APIs.
       </p>
-
-      <div class="example">
-        <p>
+      <p>
         The following code illustrates how to obtain contact information from a user's address book:
-        </p>
-        <pre class="sh_javascript">
-  function successContactFindCallback(contacts) {
-      // do something with resulting contact objects
-      for (var i in contacts) alert(contacts[i].displayName);
-      // ...
-  }
+      </p>
+      <pre class="example sh_javascript_dom">
+        function success (contacts) {
+          // do something with resulting contact objects
+          for (var i in contacts) alert(contacts[i].displayName);
+          // ...
+        }
 
-  function generalErrorCB(error) {
-      // do something with resulting errors
-      alert(error.code);
-      // ...
-  }
+        function error (err) {
+          // do something with resulting error
+          alert(err.code);
+          // ...
+        }
 
-  // Perform an address book search. Obtain the 'name' and 'emails' properties 
-  // and initially filter the list to Contact records containing 'Bob':
-  navigator.contacts.find( ['name', 'emails'],
-                           successContactFindCallback, 
-                           generalErrorCB,
-                           {filter: 'Bob'} );
-  // ..is equivalent to: navigator.contacts(/* parameters */)
-  </pre>
-      </div>
+        // Perform an address book search. Obtain the 'name' and 'emails' properties 
+        // and initially filter the list to Contact records containing 'Bob':
+        navigator.contacts.find(  ['name', 'emails'], success, error, {filter: 'Bob'} );
+        // ..is equivalent to: navigator.contacts(/* parameters */)
+      </pre>
     </section>
 
     <section id='conformance'>
Received on Wednesday, 6 April 2011 12:50:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 6 April 2011 12:50:05 GMT