W3C home > Mailing lists > Public > public-dap-commits@w3.org > June 2010

2009/dap/contacts Overview.html,1.54,1.55

From: Richard Tibbett via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 07 Jun 2010 10:15:08 +0000
To: public-dap-commits@w3.org
Message-Id: <E1OLZMK-0000Uc-29@lionel-hutz.w3.org>
Update of /sources/public/2009/dap/contacts
In directory hutz:/tmp/cvs-serv1830/contacts

Modified Files:
	Overview.html 
Log Message:
Minor edit: Switch 'Abstract' and 'Introduction' sections around.

Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/contacts/Overview.html,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -d -r1.54 -r1.55
--- Overview.html	7 Jun 2010 10:12:38 -0000	1.54
+++ Overview.html	7 Jun 2010 10:15:04 -0000	1.55
@@ -42,25 +42,7 @@
     <section
      id='abstract'>
       <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&#39;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 3rd parties users are, more often
-        than not, required to hand over access to their whole address book. Users are implicitly required to trust 3rd 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.
-      </p>
-      <p>
-        This specification defines the concept of a user&#39;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 3rd party applications can
-        access a user&#39;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.
+        The Contacts API defines the high-level interfaces required to provide access to a user&#39;s unified address book.
       </p>
     </section>
     <section
@@ -89,10 +71,28 @@
         Introduction
       </h2>
       <p>
-        The Contacts API defines a high-level interface to provide access to the user&#39;s unified contact information, such as names,
-        addresses and other contact information.
+        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&#39;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 3rd parties users are, more often
+        than not, required to hand over access to their whole address book. Users are implicitly required to trust 3rd 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.
+      </p>
+      <p>
+        This specification defines the concept of a user&#39;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 3rd party applications can
+        access a user&#39;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>
         The API itself is agnostic of any underlying address book sources, data formats and storage.
       </p>
       <section>
Received on Monday, 7 June 2010 10:15:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 June 2010 10:15:15 GMT