- From: Thomas Roessler <tlr@w3.org>
- Date: Fri, 6 Jul 2007 17:54:41 +0200
- To: "Close, Tyler J." <tyler.close@hp.com>
- Cc: public-wsc-wg@w3.org
On 2007-06-13 17:42:12 -0000, Close, Tyler J. wrote: > In general, I prefer to break down systems into distinct > components that can be adopted and used in isolation from other > components. I'm hesitant to do that in this case because the > usability of the petname tool is much enhanced by it's > integration into the PII editor bar. By itself, the petname tool > suffers from the problem of being a chrome indicator, away from > the main browsing activity, and also requires some mechanism to > prevent picture-in-picture attacks. The PII bar without the > petname tool is also vulnerable to certain attacks. Together, I > think they provide a strong defense against all of our in-scope > attacks. I'm worried that if I separate them, each will fail on > its own in usability testing and so leave potential adopters with > the impression that there is no solution here. To have a chance > at good usability testing results, I think I need to keep the two > components paired. Why not write the two up independently, and then add some language to say that these are best used together? (Disclaimer, I haven't yet looked at the latest draft language, so this comment might be as outdated as it is late.) Cheers, -- Thomas Roessler, W3C <tlr@w3.org>
Received on Friday, 6 July 2007 15:54:46 UTC