- From: Richard Tibbett via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 10 Nov 2009 20:02:13 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/contacts
In directory hutz:/tmp/cvs-serv1378/contacts
Modified Files:
Overview.html
Log Message:
Updates:
- ContactManager removed. Multiple address books will now be identifed via the productId attribute within Contact objects.
- AddressBook Interface renamed to Contacts
- General editorial updates
- Introduction now non-normative
- API usage examples simplified and updated
- All optional attributes moved to back of method calls.
- Contact interface converted to 1:1 mapping of vCard properties (RFC2426) - initial draft
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/contacts/Overview.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- Overview.html 30 Oct 2009 15:44:04 -0000 1.10
+++ Overview.html 10 Nov 2009 20:02:10 -0000 1.11
@@ -3,8 +3,8 @@
<head>
<title>The Contacts API</title>
<meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
- <script src='../ReSpec.js/js/respec.js' class='remove'>
- </script>
+ <script src='../ReSpec.js/js/respec.js' class='remove'></script>
+ <script src='../ReSpec.js/js/sh_main.min.js' class='remove'></script>
<script class='remove'>
var respecConfig = {
specStatus: "ED",
@@ -20,7 +20,8 @@
[...1796 lines suppressed...]
+ <p><code>ContactFilterOptions</code> can optionally be used to apply filtering and sorting criteria to the result of the Contacts find() method.
<p class='note'>
Do we need to say something about whether contact search matching is loose or strict? Could this be added as a ContactFilterOptions attribute?
</p>
- <p>The <dfn id='rules-for-processing-filter-combinations'>rules for processing filter combinations</dfn> is always provided with one <var title="">input</var> parameter, and its behaviour depends on the type of <var title="">input</var>. The following algorithm demonstrates the conversion of a <a href='#widl-AddressBook-findContacts'>findContacts()</a> filter object to an SQL WHERE query.</p>
+ <p>The <dfn id='rules-for-processing-filter-combinations'>rules for processing filter combinations</dfn> is always provided with one <var title="">input</var> parameter, and its behaviour depends on the type of <var title="">input</var>. The following algorithm demonstrates the conversion of a <a href='#widl-Contacts-find'>find()</a> filter object to an SQL WHERE query.</p>
<dl class=switch>
@@ -1307,7 +1251,7 @@
<p> </p>
- <p>The <a href="#addressbook-interface">AddressBook</a> interface also provides a means to apply predefined options to the resulting contacts that match the given <code>ContactFilter</code>. <code>ContactFilterOptions</code> are an optional <var title''>input</var> to the <a href="#addressbook-interface">AddressBook</a> <a href='#widl-AddressBook-findContacts'>findContacts()</a> method.</p>
+ <p>The <a href="#contacts-interface">Contacts</a> interface also provides a means to apply predefined options to the resulting contacts that match the given <code>ContactFilter</code>. <code>ContactFilterOptions</code> are an optional <var title''>input</var> to the <a href="#contacts-interface">Contacts</a> <a href='#widl-Contacts-find'>find()</a> method.</p>
<p>The <dfn id='rules-for-applying-filter-options'>rules for applying filter options</dfn> are as given in the following algorithm. If the <var title=''>output</var> of this algorithm is not null, then the string value of <var title=''>output</var> MUST be concatenated with the <var title=''>output</var> parameter of <a href='#rules-for-processing-filter-combinations'>rules for processing filter combinations</a> and returned as a single string result. The following algorithm demonstrates the conversion of a passed <code>ContactFilterOptions</code> object to an SQL Pagination query.</p>
Received on Tuesday, 10 November 2009 20:02:14 UTC