W3C home > Mailing lists > Public > public-dap-commits@w3.org > July 2011

2009/dap/contacts Overview.html,1.153,1.154

From: Robin Berjon via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 19 Jul 2011 12:20:52 +0000
To: public-dap-commits@w3.org
Message-Id: <E1Qj9IC-0007rS-Q2@lionel-hutz.w3.org>
Update of /sources/public/2009/dap/contacts
In directory hutz:/tmp/cvs-serv30200/contacts

Modified Files:
	Overview.html 
Log Message:
lowercase

Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/contacts/Overview.html,v
retrieving revision 1.153
retrieving revision 1.154
diff -u -d -r1.153 -r1.154
--- Overview.html	19 Jul 2011 12:17:41 -0000	1.153
+++ Overview.html	19 Jul 2011 12:20:50 -0000	1.154
@@ -218,25 +218,25 @@
       <section>
         <h2>Privacy considerations for implementers of the Contacts API</h2>
         <p>
-          A <a class="product-ua" href="#ua">user agent</a> SHOULD NOT provide contact information to Web sites without the express
-          permission of the user. A <a>user agent</a> SHOULD acquire permission from the user, unless
-          they have prearranged trust relationships with users, as described below. The user interface SHOULD
+          A <a class="product-ua" href="#ua">user agent</a> should not provide contact information to Web sites without the express
+          permission of the user. A <a>user agent</a> should acquire permission from the user, unless
+          they have prearranged trust relationships with users, as described below. The user interface should
           include the <a>document base URL</a>. Those permissions that are acquired through the user interface
           and that are preserved beyond the current browsing session (i.e. beyond the time when the <a>browsing
-          context</a> is navigated to another URL) SHOULD be revocable and a <a>user agent</a> SHOULD respect permission revocation.
+          context</a> is navigated to another URL) should be revocable and a <a>user agent</a> should respect permission revocation.
         </p>
         <p>
           Obtaining the user's express permission to access one API method does not imply the user has granted
           permission for the same Web site to access other methods provided by this API, or to access the same
           method with a different set of arguments, as part of the same permission context. If a user has
           expressed permission for an implementation to, e.g. find a set of existing contacts, the implementation
-          SHOULD seek the user's express permission if and when any additional <code>find</code> function is called
+          should seek the user's express permission if and when any additional <code>find</code> function is called
           on this API.
         </p>
         <p>
           A <a>user agent</a> may have prearranged trust relationships that do not require such user
           interfaces. For example, while a Web browser will present a user interface when a Web site performs an
-          address book request, a Widget [[WIDGETS]] runtime MAY have a prearranged, delegated security
+          address book request, a Widget [[WIDGETS]] runtime may have a prearranged, delegated security
           relationship with the user and, as such, a suitable alternative security and privacy mechanism with
           which to authorize the retrieval of contact information.
         </p>
Received on Tuesday, 19 July 2011 12:20:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 12:20:59 GMT