- From: Robin Berjon via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 15 Jun 2011 14:43:20 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/contacts
In directory hutz:/tmp/cvs-serv30550
Modified Files:
Overview.html
Log Message:
all changes from Dom's email
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/contacts/Overview.html,v
retrieving revision 1.143
retrieving revision 1.144
diff -u -d -r1.143 -r1.144
--- Overview.html 15 Jun 2011 14:18:43 -0000 1.143
+++ Overview.html 15 Jun 2011 14:43:18 -0000 1.144
@@ -151,15 +151,15 @@
</p>
<pre class="example sh_javascript_dom">
function success (contacts) {
- // do something with resulting contact objects
- for (var i in contacts) alert(contacts[i].name);
- // ...
+ // do something with resulting contact objects
+ for (var i in contacts) alert(contacts[i].name);
+ // ...
}
function error (err) {
- // do something with resulting error
- alert(err.code);
- // ...
+ // do something with resulting error
+ alert(err.code);
+ // ...
}
// Perform an address book search. Obtain the 'name' and 'emails' properties
@@ -292,7 +292,8 @@
Predicting or preventing these situations is inherently difficult. Mitigation and in-depth defensive
measures are an implementation responsibility and not prescribed by this specification. However, in
designing these measures, implementers are advised to enable user awareness of contact sharing, and to
- provide easy access to interfaces that enable revocation of permissions.
+ provide easy access to interfaces that enable revocation of permissions that web applications have to
+ access this API.
</p>
</section>
</section>
@@ -398,7 +399,9 @@
<section>
<h2><a>Contact</a> interface</h2>
<p>
- The <a>Contact</a> interface captures the properties of a contact object.
+ The <a>Contact</a> interface captures the properties of a contact object. All properties included in this
+ interface have a corresponding definition in [[POCO-SCHEMA]], [[RFC2426]] (aka vCard), and [[OMA-CAB]], thereby
+ allowing the API to be supported across implementations supporting these various contact formats.
</p>
<p id="ta-ac" class="product-ua">
All <a>Contact</a> objects MUST include all attributes supported by the implementation, regardless
@@ -476,14 +479,6 @@
This attribute represents one or more organizations associated with this <a>Contact</a>.
</p>
</dd>
- <dt>attribute Date? revision</dt>
- <dd>
- <p>
- This attribute contains the timestamp information associated with this <a>Contact</a>, which
- represents the last known modification time. If no modification time exists, then this object contains the
- timestamp of the object's creation time.
- </p>
- </dd>
<dt>attribute Date? birthday</dt>
<dd>
<p>
@@ -494,21 +489,6 @@
available.
</p>
</dd>
- <dt>attribute DOMString? gender</dt>
- <dd>
- <p>
- This attribute contains the gender of this <a>Contact</a>. This attribute SHOULD have one of the
- following values:
- </p>
- <ul>
- <li>male</li>
- <li>female</li>
- <li>undisclosed</li>
- </ul>
- <p>
- Note however that this attribute MAY contain a value not listed above.
- </p>
- </dd>
<dt>attribute DOMString? note</dt>
<dd>
<p>
@@ -523,7 +503,8 @@
</p>
<p>
The photos MUST be specified in the <code>value</code> attribute of the <a>ContactField</a> object
- either by using a URL to an image resource or base64 encoded string of the image data.
+ by using a URL pointing to an image resource. The <code>data:</code> URI scheme may be used in order
+ to provide inline data.
</p>
<p class="note">
This attribute SHOULD NOT be used to send down arbitrary photos taken by this user,
@@ -550,31 +531,6 @@
"profile".
</p>
</dd>
- <dt>attribute DOMString? timezone</dt>
- <dd>
- <p>
- This attribute represents the time zone of this Contact.
- </p>
- <p>
- It is RECOMMENDED that names from the public-domain Olson database [[TZDB]] will be used as the
- value of this attribute, but this is not a restriction. For example, a value of
- <code>America/New_York</code> indicates the <a>Contact</a> is associated with the variable time zone of
- the New York region of the United States, including daylight saving time offsets experienced in
- that region.
- </p>
- <p>
- It is also possible to use this attribute to express the timezone as a positive or negative
- difference from UTC, in the 24-hour clock, in units of hours and minutes (i.e.
- <code>+hh:mm</code>). For example, a value of <code>+05:30</code> indicates the Contact is
- associated with a fixed time zone of GMT+05:30.
- </p>
- <p class="note">
- Where possible UTC offset values SHOULD NOT be used. The UTC offset varies with
- time - not just because of the usual daylight saving time shifts that occur in may regions, but
- often entire regions will "re-base" their overall offset. The actual offset may be +/- 1 hour (or
- perhaps a little more) than any UTC offset given.
- </p>
- </dd>
</dl>
</section>
@@ -1297,7 +1253,7 @@
<p>
If an additional find() operation is called by the current web application before the user has
clicked 'Select' or 'Cancel' 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
+ <a href="#widl-ContactError-PENDING_OPERATION_ERROR"><code>PENDING_OPERATION_ERROR</code></a> if that
operation was defined with a non-<code>null</code> <code>errorCB</code> parameter.
</p>
@@ -1324,7 +1280,7 @@
<p>
If an additional find() operation is called by the current web application before the user has
clicked 'Select' or 'Cancel' 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
+ <a href="#widl-ContactError-PENDING_OPERATION_ERROR"><code>PENDING_OPERATION_ERROR</code></a> if that
operation was defined with a non-<code>null</code> <code>errorCB</code> parameter.
</p>
@@ -1343,7 +1299,8 @@
<p>
Further to this initial sharing of Contact information, the <a href=
"#security-and-privacy-considerations">Security and Privacy Considerations</a> section expects that the
- user should easily be able to review and revoke permissions to web applications at a later date.
+ user should easily be able to review and revoke access that web applications have to this API
+ at a later time.
</p>
</section>
@@ -1411,7 +1368,7 @@
<p>
If an additional find() operation is called by the current web application before the user has
clicked 'Select' or 'Cancel' 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
+ <a href="#widl-ContactError-PENDING_OPERATION_ERROR"><code>PENDING_OPERATION_ERROR</code></a> if that
operation was defined with a non-<code>null</code> <code>errorCB</code> parameter.
</p>
@@ -1430,7 +1387,8 @@
<p>
Further to this initial sharing of Contact information, the <a href=
"#security-and-privacy-considerations">Security and Privacy Considerations</a> section expects that the
- user should easily be able to review and revoke permissions to web applications at a later date.
+ user should easily be able to review and revoke access that web applications have to this API
+ at a later time.
</p>
</section>
</section>
@@ -1462,7 +1420,7 @@
</p>
<p>
- To handle the saving of a new Contact, a <a>user agent</a> SHOULD register as the default handler for
+ To handle the saving of a new Contact, a <a>user agent</a> should register as the default handler for
any <a>valid Contact resource</a>.
</p>
@@ -1472,19 +1430,16 @@
<ul>
<li><code>text/vcard</code></li>
-
<li><code>text/x-vcard</code></li>
-
<li><code>text/directory</code></li>
-
<li><code>text/directory;profile=vCard</code></li>
</ul>
<p>
- On invocation of a <a>valid Contact resource</a>, the <a>user agent</a> SHOULD, on successful download
+ On invocation of a <a>valid Contact resource</a>, the <a>user agent</a> should, on successful download
of the <a>valid Contact resource</a>, store the given resource in the user's unified address book
according to the <a>rule for storing a Contact resource</a>. As part of this standard download process,
- the <a>user agent</a> MAY present a dialog to the user allowing them to select a different application
+ the <a>user agent</a> may present a dialog to the user allowing them to select a different application
with which to handle the given resource, thereby overriding the use of the unified address book for the
storage of the data contained therein and bypassing the <a>rule for storing a Contact resource</a>.
</p>
@@ -1517,10 +1472,10 @@
</ol>
<p>
- As part of the <a>rule for storing a Contact resource</a>, the <a>user agent</a> MAY provide
+ As part of the <a>rule for storing a Contact resource</a>, the <a>user agent</a> may provide
additional dialogs to the user after successful completion of the download and before the Contact
information is saved to the unified address book, such as to show a preview of the Contact information
- contained therein as it will be stored in the user's unified address book. The user MAY be able to
+ contained therein as it will be stored in the user's unified address book. The user may be able to
override the information provided before accepting the additions and permanently storing the given data
in their unified address book.
</p>
Received on Wednesday, 15 June 2011 14:43:26 UTC