- From: Mary Ellen Zurko <Mary_Ellen_Zurko@notesdev.ibm.com>
- Date: Mon, 12 Feb 2007 09:06:50 -0500
- To: hlockhar@bea.com
- Cc: public-wsc-wg@w3.org
- Message-ID: <OF6530CFFE.2E0B6B25-ON85257280.004C5636-85257280.004D8757@LocalDomain>
Thanks Hal. I'm just starting to read these, and I'm struck once again by the personalization conundrum. Patrick et al give a number of design techniques that will drive trust, including offering a personlized service. Yet Schecter et al. report a very small percentage of users will distrust based on the lack of such an indicator. Dhamija et al (and others) point out that users don't notice the lack of something. To the extent the security indicator is in "non chrome", the lack cannot be promoted to an explicit lack indicator. But if it is reported in "chrome", then the "lack" can look like something. The only way to promote site personalization to "chrome" without a protocol change is to do with the browser/UA; not the site itself Mez Mary Ellen Zurko, STSM, IBM Lotus CTO Office (t/l 333-6389) Lotus/WPLC Security Strategy and Patent Innovation Architect "Hal Lockhart" <hlockhar@bea.com> Sent by: public-wsc-wg-request@w3.org 02/08/2007 02:43 PM To <public-wsc-wg@w3.org> cc Subject ACTION-27 Is complete, take a look at NoteWorkshopRecommendations As I said previously, I created a new page under More document structure called NoteWorkshopRecommendations. It has three subsections: RawRecommendations, InScopeandOutofScope and InScopebyCategory. This closes ACTION-27. Hal
Received on Monday, 12 February 2007 14:16:03 UTC