- From: Richard Tibbett via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 07 Jun 2010 10:12:41 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/contacts In directory hutz:/tmp/cvs-serv1402/contacts Modified Files: Overview.html Log Message: - 'Introduction' updated. - 'Search Filters' section updated. - 'Security and Privacy' Note agreed by DAP WG added to 'Security and Privacy Considerations' section. Index: Overview.html =================================================================== RCS file: /sources/public/2009/dap/contacts/Overview.html,v retrieving revision 1.53 retrieving revision 1.54 diff -u -d -r1.53 -r1.54 --- Overview.html 6 Jun 2010 14:28:57 -0000 1.53 +++ Overview.html 7 Jun 2010 10:12:38 -0000 1.54 @@ -42,8 +42,25 @@ <section id='abstract'> <p> - This specification defines an <acronym - title="Application Programming Interface">API</acronym> that provides access to a user's unified address book. + 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. + </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'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'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> </section> <section @@ -76,7 +93,7 @@ addresses and other contact information. </p> <p> - The API itself is agnostic of any underlying address book sources and data formats. + The API itself is agnostic of any underlying address book sources, data formats and storage. </p> <section> <h2> @@ -180,7 +197,8 @@ </h2> <p class='note'> - <strong>This section is under development.</strong> + The overall architecture for addressing privacy in DAP is still under construction. As it is finalized, there may be changes made + to this API to reflect requirements or support for privacy-related functionality. </p> <p> The API defined in this specification can be used to create, retrieve, update and remove contact information from a user's @@ -406,11 +424,9 @@ href="#contact-interface"><code>Contact</code></a> objects MUST include all attributes supported by the implementation, regardless of whether these attributes have been assigned a non-<code>null</code> value or a <code>null</code> value. </p> - - <p> - If a - supported attribute has not been assigned a value by the user and/or implementation, then this attribute MUST still be present in - the resulting <a + <p> + If a supported attribute has not been assigned a value by the user and/or implementation, then this attribute MUST still be + present in the resulting <a href="#contact-interface"><code>Contact</code></a> object and MUST have a value of <code>null</code>. </p> <dl @@ -1296,8 +1312,8 @@ </h4> <p class="note"> - Include ContactProperties weights to allow sorting by match relevance. e.g. a 'name' match carries more - relevance than a 'city' match so matching records will be sorted accordingly. + Include ContactProperties weights to allow sorting by match relevance. e.g. a 'name' match carries more relevance than + a 'city' match so matching records will be sorted accordingly. </p> <p class="note"> @@ -1318,18 +1334,17 @@ href="#widl-contacts-find"><code>Contacts.find()</code></a> operation. </p> <p> - All fields within a <a>search filter</a> represent the logical intersection, or <code>∩</code>, of provided values that are - matched within the <a - href="#contacts-interface"><code>Contacts</code></a> database. Fields provided with a <code>null</code> value are considered - to match anything, or <code>*</code>. + A <a>search filter</a> is used to search all the fields of a <a + href="#contacts-interface"><code>Contacts</code></a> database and represents the logical intersection, or <code>∩</code>, + of provided values that are matched therein. </p> <p> - All contact searching MUST apply a loose-matching policy to all <a>search filter</a> attributes provided. If a <a + All contact searching MUST apply a loose-matching policy to the <a>search filter</a> provided. If a <a href='#contactproperties-interface'><code>ContactProperties</code></a> attribute being searched in a <a href='#contact-interface'><code>Contact</code></a> object, stored within the <a - href='#contacts-interface'><code>Contacts</code></a> database, is a <a>partial value match</a> of the input filter value, a <a - href='#contact-interface'><code>Contact</code></a> object representing the contact MUST be returned as part of the resulting + href='#contacts-interface'><code>Contacts</code></a> database, is a <a>partial value match</a> of the input filter value, that <a + href='#contact-interface'><code>Contact</code></a> object MUST be returned as part of the resulting <a href='#contactfindsuccesscb-interface'><code>ContactFindSuccessCB</code></a>. </p> <p> @@ -1346,7 +1361,7 @@ in the <a href="#contacts-interface"><code>Contacts</code></a> database. </p> - <p> + <p> </p> <p> @@ -1362,7 +1377,7 @@ </dt> <dd> Let <var - title="contactsset">contactsset</var> be initially the set of all known contacts in the <a + title="contactsets">contactsets</var> be initially the set of all known contacts in the <a href="#contacts-interface"><code>Contacts</code></a> database. <p> Let <var @@ -1382,13 +1397,16 @@ </li> <li> Let <var - title="partialMatchFound">partialMatchFound</var> be the result of applying the <a>partial matching algorithm</a>, providing <var + title="partialMatchFound">partialMatchFound</var> be the result of applying the <a>partial matching algorithm</a>, + providing <var title="filter">filter</var> and <var title="contactset">contactset</var> as inputs. </li> <li> If <var - title="partialMatchFound">partialMatchFound</var> is <code>true</code>, add <var title="contactset">contactset</var> to <var title="contactsresult">contactsresult</var>. + title="partialMatchFound">partialMatchFound</var> is <code>true</code>, add <var + title="contactset">contactset</var> to <var + title="contactsresult">contactsresult</var>. </li> <li> Go to step 1. @@ -1405,7 +1423,8 @@ </dt> <dd> <p> - Return a <code>null</code> value. + Return <var + title="contactsets">contactsets</var>. </p> </dd> </dl> @@ -1442,11 +1461,12 @@ Let <var title="hasPartialMatch">hasPartialMatch</var> be the boolean result for the comparison of <var title="filter">filter</var> with <var - title="elementvalue">elementvalue</var> in a <a>compatibility caseless</a> manner and with a <a>partial value match</a> policy - applied to both sides of the comparison operation. + title="elementvalue">elementvalue</var> in a <a>compatibility caseless</a> manner and with a <a>partial value match</a> + policy applied to both sides of the comparison operation. </li> <li> - If <var title="hasPartialMatch">hasPartialMatch</var> is <code>true</code>, go to step 5. + If <var + title="hasPartialMatch">hasPartialMatch</var> is <code>true</code>, go to step 5. </li> <li> Go to step 1. @@ -1467,7 +1487,7 @@ </p> </dd> </dl> - <p> + <p> </p> <section> @@ -1515,4 +1535,5 @@ </section> </section> </body> -</html> \ No newline at end of file +</html> +
Received on Monday, 7 June 2010 10:12:45 UTC