2009/dap/contacts Overview.html,1.30,1.31

Update of /sources/public/2009/dap/contacts
In directory hutz:/tmp/cvs-serv27734

Modified Files:
	Overview.html 
Log Message:
CORE-DEVICE should be normative


Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/contacts/Overview.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -d -r1.30 -r1.31
--- Overview.html	20 Jan 2010 10:49:41 -0000	1.30
+++ Overview.html	20 Jan 2010 12:27:16 -0000	1.31
@@ -234,7 +234,7 @@
 <p class='issue'>The actual object of which the API will be hanging off is still under discussion (e.g. <code>navigator.service</code> vs from <code>navigator.device</code>); see <a href="http://www.w3.org/2009/dap/track/issues/67">ISSUE-67</a></p>
 				
 				<p>
-					The <a href='#servicecontacts-interface'><code>ServiceContacts</code></a> interface is exposed on the <code>navigator.service</code> object, as defined in [[CORE-DEVICE]]. 
+					The <a href='#servicecontacts-interface'><code>ServiceContacts</code></a> interface is exposed on the <code>navigator.service</code> object, as defined in [[!CORE-DEVICE]]. 
 				</p>
 				
 				<div class='idl' title='Service implements ServiceContacts'></div>
@@ -298,7 +298,7 @@
                     	<p>Find contacts in the address book based on a <a href='#contactproperties-interface'><code>ContactProperties</code></a> object acting as a filter.</p>
 						
 						<p>This method takes two, three or four arguments. When called, it immediately returns 
-						a <code>PendingOp</code> object , as defined in [[CORE-DEVICE]], and then asynchronously starts a <dfn>find contacts process</dfn> defined as follows:</p> 
+						a <code>PendingOp</code> object , as defined in [[!CORE-DEVICE]], and then asynchronously starts a <dfn>find contacts process</dfn> defined as follows:</p> 
 						
 						<p>		
 							<ol>
@@ -387,7 +387,7 @@
 						</p>
 						
 						<p>This method takes one or two arguments. When called, it immediately returns 
-						a <code>PendingOp</code> object , as defined in [[CORE-DEVICE]], and then asynchronously starts a <dfn>save contact process</dfn> defined as follows:</p> 
+						a <code>PendingOp</code> object , as defined in [[!CORE-DEVICE]], and then asynchronously starts a <dfn>save contact process</dfn> defined as follows:</p> 
 
 						<p>		
 							<ol>
@@ -430,7 +430,7 @@
 
 						
 						<p>This method takes one or two arguments. When called, it immediately returns 
-						a <code>PendingOp</code> object , as defined in [[CORE-DEVICE]], and then asynchronously starts a <dfn>remove contact process</dfn> defined as follows:</p>
+						a <code>PendingOp</code> object , as defined in [[!CORE-DEVICE]], and then asynchronously starts a <dfn>remove contact process</dfn> defined as follows:</p>
 						
 						<p>		
 							<ol>
@@ -872,7 +872,7 @@
                    </dd>
                    <dt>const unsigned short PENDING_OPERATION_ERROR = 3</dt>
                    <dd>
-                      If the <code>PendingOp</code> (as defined in [[CORE-DEVICE]]) associated with the requested callback produces an error on <a href="../device/#widl-PendingOp-cancel">cancel()</a>.
+                      If the <code>PendingOp</code> (as defined in [[!CORE-DEVICE]]) associated with the requested callback produces an error on <a href="../device/#widl-PendingOp-cancel">cancel()</a>.
                    </dd>	
                    <dt>const unsigned short IO_ERROR = 4</dt>
                    <dd>

Received on Wednesday, 20 January 2010 12:27:20 UTC