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

2009/dap/contacts Overview.html,1.69,1.70 Writer.html,1.1,1.2

From: Richard Tibbett via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 03 Aug 2010 11:30:38 +0000
To: public-dap-commits@w3.org
Message-Id: <E1OgFhe-0005Jd-2l@lionel-hutz.w3.org>
Update of /sources/public/2009/dap/contacts
In directory hutz:/tmp/cvs-serv20419/contacts

Modified Files:
	Overview.html Writer.html 
Log Message:
Updated editor affiliation to Opera Software ASA

Index: Writer.html
===================================================================
RCS file: /sources/public/2009/dap/contacts/Writer.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Writer.html	3 Aug 2010 10:51:35 -0000	1.1
+++ Writer.html	3 Aug 2010 11:30:36 -0000	1.2
@@ -23,7 +23,7 @@
             var respecConfig = {
                 specStatus: "ED",
                 shortName: "contacts-api",
-            editors: [{name: "Richard Tibbett", company: "Invited Expert"}],
+            editors: [{name: "Richard Tibbett", company: "Opera Software ASA"}],
                 //publishDate:  "2010-07-01",
                 // previousPublishDate:  "2010-01-21",
                 edDraftURI: "http://dev.w3.org/2009/dap/contacts/Writer.html",
@@ -254,7 +254,8 @@
           <a>ContactsWriter</a> interface
         </h2>
         <p>
-          The <a>ContactsWriter</a> interface exposes a database collecting contacts information, such that they may be created, updated, and deleted.
+          The <a>ContactsWriter</a> interface exposes a database collecting contacts information, such that they may be created, updated,
+          and deleted.
         </p>
         <dl
          title='[NoInterfaceObject] interface ContactsWriter : Contacts'
@@ -561,7 +562,7 @@
       </section>
     </section>
     <!-- end api description section -->
-     <section
+    <section
      class="informative appendix">
       <h2>
         User Interaction Guidelines
@@ -596,4 +597,5 @@
       </section>
     </section>
   </body>
-</html>
\ No newline at end of file
+</html>
+

Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/contacts/Overview.html,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -d -r1.69 -r1.70
--- Overview.html	3 Aug 2010 11:00:25 -0000	1.69
+++ Overview.html	3 Aug 2010 11:30:35 -0000	1.70
@@ -23,7 +23,7 @@
             var respecConfig = {
                 specStatus: "ED",
                 shortName: "contacts-api",
-            editors: [{name: "Richard Tibbett", company: "Invited Expert"}],
+            editors: [{name: "Richard Tibbett", company: "Opera Software ASA"}],
                 //publishDate:  "2010-07-01",
                 // previousPublishDate:  "2010-01-21",
                 edDraftURI: "http://dev.w3.org/2009/dap/contacts/",
@@ -329,8 +329,8 @@
         </p>
         <p>
           The <a
-           href="#contact-interface"><code>Contact</code></a> interface captures the properties of a contact object.
-          All properties included in this interface have a corresponding definition in [[!POCO-SCHEMA]].
+           href="#contact-interface"><code>Contact</code></a> interface captures the properties of a contact object. All properties
+          included in this interface have a corresponding definition in [[!POCO-SCHEMA]].
         </p>
         <p>
           In addition to the properties defined in this interface, a conforming implementation MUST support both the Singular and Plural
@@ -370,7 +370,7 @@
               See [[[!POCO-SCHEMA]] Section 7.2.1. <code>id</code>] for additional definition of this attribute.
             </p>
           </dd>
-        <dt>
+          <dt>
             attribute DOMString displayName
           </dt>
           <dd>
@@ -1020,8 +1020,8 @@
         </h3>
         <p>
           The <dfn>search qualifier</dfn> provides an application with a way to request the specific subset of <a
-           href="#contact-interface"><code>Contact</code></a> properties it wishes to obtain in any resulting successful callback.
-          The <a>search qualifier</a> is deployed to minimize the data that needs to be shared with an application in order to let that
+           href="#contact-interface"><code>Contact</code></a> properties it wishes to obtain in any resulting successful callback. The
+          <a>search qualifier</a> is deployed to minimize the data that needs to be shared with an application in order to let that
           application fulfill its function on behalf of the user. The <a>search qualifier</a> is included within a <a
            href="#contacts-interface"><code>Contacts</code></a> <a
            href="#widl-Contacts-find">find()</a> operation as the <code>filter</code> parameter.
@@ -1047,8 +1047,8 @@
         </p>
         <p>
           If a provided <a>search qualifier</a> element (<code>filter[x]</code>) does not match a <a
-           href="#contact-interface"><code>Contact</code></a> attribute, <code>filter[x]</code> SHOULD be ignored when
-          executing the current <a
+           href="#contact-interface"><code>Contact</code></a> attribute, <code>filter[x]</code> SHOULD be ignored when executing the
+          current <a
            href="#contacts-interface"><code>Contacts</code></a> <a
            href="#widl-Contacts-find">find()</a> operation.
         </p>
@@ -1058,15 +1058,13 @@
           </h3>
           <p>
             Certain <a
-             href="#contact-interface"><code>Contact</code></a> attributes can be considered complex by the fact that
-            the information they contain is available only through child DOMString-based attributes of a complex Object object.
+             href="#contact-interface"><code>Contact</code></a> attributes can be considered complex by the fact that the information they
+            contain is available only through child DOMString-based attributes of a complex Object object.
           </p>
           <p>
             In such cases, a requesting application MUST be able to request both the full complex <a
-             href="#contact-interface"><code>Contact</code></a> attribute and also be able to request individual parts
-            of a complex <a
-             href="#contact-interface"><code>Contact</code></a> attribute in the <a>search qualifier</a> provided to a
-            <a
+             href="#contact-interface"><code>Contact</code></a> attribute and also be able to request individual parts of a complex <a
+             href="#contact-interface"><code>Contact</code></a> attribute in the <a>search qualifier</a> provided to a <a
              href="#contacts-interface"><code>Contacts</code></a> <a
              href="#widl-Contacts-find">find()</a> operation.
           </p>
@@ -1082,9 +1080,9 @@
           </p>
           <p>
             In the case that a complex <a
-             href="#contact-interface"><code>Contact</code></a> attribute is defined as a sequence or array of complex
-            objects, specific individual attributes can be referenced by using the complex attribute name, a dot (<code>.</code>) character
-            and the individual attribute to be retrieved.
+             href="#contact-interface"><code>Contact</code></a> attribute is defined as a sequence or array of complex objects, specific
+            individual attributes can be referenced by using the complex attribute name, a dot (<code>.</code>) character and the
+            individual attribute to be retrieved.
           </p>
           <p>
             For example, the <code>addresses</code> attribute of <a
@@ -1223,19 +1221,23 @@
             provided values that are matched therein.
           </p>
           <p>
-            All contact searching MUST apply a <dfn>loose-matching policy</dfn> to the <a>search filter</a> provided. If an attribute being searched in a <a
+            All contact searching MUST apply a <dfn>loose-matching policy</dfn> to the <a>search filter</a> provided. If an 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 <code>filter</code> value, that
-            <a
+             href='#contacts-interface'><code>Contacts</code></a> database, is a <a>partial value match</a> of the input
+            <code>filter</code> 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>
-           A conforming implementation MUST only allow the provided <a>search filter</a> to be applied to fields requested in the provided <a>search qualifier</a>. The <code>id</code> attribute MUST always be implicitly searchable from any requesting web application regardless of whether it has been included as part of any provided <a>search qualifier</a>. 
-           For example, if the given <a>search qualifier</a> contains 'name' and 'displayName', then the <a>rules for processing search filters</a> should only be applied to all sub-fields of the <code>name</code> attribute (i.e. <code>name.formatted</code>, <code>name.firstName</code>, <code>name.givenName</code>, <code>name.middleName</code>, <code>name.honorificPrefix</code>, <code>name.honorificSuffix</code>)  and the <code>displayName</code> attribute.
-           
+            A conforming implementation MUST only allow the provided <a>search filter</a> to be applied to fields requested in the provided
+            <a>search qualifier</a>. The <code>id</code> attribute MUST always be implicitly searchable from any requesting web application
+            regardless of whether it has been included as part of any provided <a>search qualifier</a>. For example, if the given <a>search
+            qualifier</a> contains &#39;name&#39; and &#39;displayName&#39;, then the <a>rules for processing search filters</a> should
+            only be applied to all sub-fields of the <code>name</code> attribute (i.e. <code>name.formatted</code>,
+            <code>name.firstName</code>, <code>name.givenName</code>, <code>name.middleName</code>, <code>name.honorificPrefix</code>,
+            <code>name.honorificSuffix</code>) and the <code>displayName</code> attribute.
           </p>
-          
           <p>
             A <dfn>partial value match</dfn> refers to both syntactic and semantic partial matching of an input filter value with a
             corresponding value in the address book and denotes that a corresponding match was found in the address book that begins with,
@@ -1408,7 +1410,8 @@
             </p>
             <ol>
               <li>
-                Using ECMA-262 3rd Edition regular expression syntax and psuedo-code, the <a>search filter</a> provided can be represented as: 
+                Using ECMA-262 3rd Edition regular expression syntax and psuedo-code, the <a>search filter</a> provided can be represented
+                as: 
 <pre>
 ( name.formatted = /&and;.*Robert.*$/i ) &cup; ( phoneNumbers.value = /&and;.*Robert.*$/i ) 
 &cup; ( emails.value = /&and;.*Robert.*$/i ) &cup; ( name.familyName = /&and;.*Robert.*$/i ) 
@@ -1417,13 +1420,16 @@
 &cup; ( phoneNumbers.type = /&and;.*Robert.*$/i ) &cup; ( emails.type = /&and;.*Robert.*$/i )
 &cup; ( id = /&and;.*Robert.*$/i )
 </pre>
-                  <br />
-                  All searches are case-insensitive and apply a <a>loose-matching policy</a> as defined in <a href="#search-filters">Search Filters</a>. 
-                  Search ordering is sorted according to <a>search weights</a> defined in <a href="#search-filters">Search Filters</a> and described in <a href="#search-weights">Appendix B</a>.
-                  <br /><br />
-                  The <code>id</code> attribute is implicitly appended along with any <a>search filter</a> attributes provided, regardless of whether it was provided as a <a>search qualifier</a> from the requesting application, as defined in <a href="#search-filters">Search Filters</a>. 
-                  <br /><br />
-                  
+                <br>
+                 All searches are case-insensitive and apply a <a>loose-matching policy</a> as defined in <a
+                 href="#search-filters">Search Filters</a>. Search ordering is sorted according to <a>search weights</a> defined in <a
+                 href="#search-filters">Search Filters</a> and described in <a
+                 href="#search-weights">Appendix B</a>.<br>
+                <br>
+                 The <code>id</code> attribute is implicitly appended along with any <a>search filter</a> attributes provided, regardless
+                of whether it was provided as a <a>search qualifier</a> from the requesting application, as defined in <a
+                 href="#search-filters">Search Filters</a>.<br>
+                <br>
               </li>
               <li>
                 Return only the valid <a
@@ -1492,11 +1498,12 @@
         <p>
           If an additional find(), save() or remove() operation is called by the current web application before the user has clicked
           &#39;Select&#39; or &#39;Cancel&#39; on the current notification, an error will be invoked with a code of <a
-           href="#widl-ContactError-PERMISSION_DENIED_ERROR"><code>PENDING_OPERATION_ERROR</code></a> if that operation was defined with a non-<code>null</code> <code>errorCB</code> parameter.
+           href="#widl-ContactError-PERMISSION_DENIED_ERROR"><code>PENDING_OPERATION_ERROR</code></a> if that operation was defined with a
+          non-<code>null</code> <code>errorCB</code> parameter.
         </p>
         <p>
-          If the user clicks &#39;Cancel&#39;, the <code>errorCB</code>, if non-<code>null</code> for the current find() operation, will be invoked with an error
-          code of <a
+          If the user clicks &#39;Cancel&#39;, the <code>errorCB</code>, if non-<code>null</code> for the current find() operation, will be
+          invoked with an error code of <a
            href="#widl-ContactError-PERMISSION_DENIED_ERROR"><code>PERMISSION_DENIED_ERROR</code></a>.
         </p>
         <p>
@@ -1518,11 +1525,12 @@
         <p>
           If an additional find(), save() or remove() operation is called by the current web application before the user has clicked
           &#39;Select&#39; or &#39;Cancel&#39; on the current notification, an error will be invoked with a code of <a
-           href="#widl-ContactError-PERMISSION_DENIED_ERROR"><code>PENDING_OPERATION_ERROR</code></a> if that operation was defined with a non-<code>null</code> <code>errorCB</code> parameter.
+           href="#widl-ContactError-PERMISSION_DENIED_ERROR"><code>PENDING_OPERATION_ERROR</code></a> if that operation was defined with a
+          non-<code>null</code> <code>errorCB</code> parameter.
         </p>
         <p>
-          If the user clicks &#39;Cancel&#39;, the <code>errorCB</code>, if non-<code>null</code> for the current find() operation, will be invoked with
-          an error code of <a
+          If the user clicks &#39;Cancel&#39;, the <code>errorCB</code>, if non-<code>null</code> for the current find() operation, will be
+          invoked with an error code of <a
            href="#widl-ContactError-PERMISSION_DENIED_ERROR"><code>PERMISSION_DENIED_ERROR</code></a>.
         </p>
         <p>
@@ -2084,4 +2092,5 @@
       <br>
     </section>
   </body>
-</html>
\ No newline at end of file
+</html>
+
Received on Tuesday, 3 August 2010 11:30:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 August 2010 11:30:40 GMT