2009/dap/docs privacy-license.html,1.1,1.2

Update of /sources/public/2009/dap/docs
In directory hutz:/tmp/cvs-serv518

Modified Files:
	privacy-license.html 
Log Message:
last notes before the week-edn

Index: privacy-license.html
===================================================================
RCS file: /sources/public/2009/dap/docs/privacy-license.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- privacy-license.html	1 Apr 2010 15:52:55 -0000	1.1
+++ privacy-license.html	1 Apr 2010 16:06:05 -0000	1.2
@@ -288,16 +288,41 @@
         <section>
           <h2>Metadata is extracted and shown in the browser chrome</h2>
           <p>
-            The browser detects 
+            The browser acquires the privacy licensing metadata and displays it in the chrome.
           </p>
           <dl>
             <dt>Pros</dt>
             <dd>
-              ...
+              The chrome is trusted.
             </dd>
             <dt>Cons</dt>
             <dd>
-              ...
+              The chrome is already crammed full of stuff. Unlike the other big trust icon for SSL, this
+              is not information that the browser can verify and it is dangerous to give the impression 
+              that it is.
+            </dd>
+          </dl>
+        </section>
+
+        <section>
+          <h2>Non-modal content-invasive indications</h2>
+          <p>
+            The browser acquires the privacy licensing metadata and displays it contextually with the
+            interaction that the user is making. For instance, if the user is filling out a form, the browser
+            provides an indication of whether it matches the user's intended preference. In that case,
+            a large, red tooltip could appear next to the field that the user is filling out stating
+            “This service does not comply with your preferred privacy.” By being in the content it is
+            very user-visible, but does not have chrome-level “trust”; since it is non-modal it doesn't
+            get killed.
+          </p>
+          <dl>
+            <dt>Pros</dt>
+            <dd>
+              Makes the information very available, but without the trust issues implied in chrome.
+            </dd>
+            <dt>Cons</dt>
+            <dd>
+              Designers might hate it. Would need some serious lab testing.
             </dd>
           </dl>
         </section>

Received on Thursday, 1 April 2010 16:06:11 UTC