W3C home > Mailing lists > Public > public-usable-authentication@w3.org > August 2008

[fwd] Re: Web Security Context: User Interface Guidelines (from: timeless@gmail.com)

From: Thomas Roessler <tlr@w3.org>
Date: Wed, 6 Aug 2008 18:30:16 +0200
To: public-usable-authentication@w3.org
Cc: timeless@gmail.com
Message-ID: <20080806163016.GW4194@iCoaster.does-not-exist.org>

archiving, with permission
-- 
Thomas Roessler, W3C  <tlr@w3.org>





----- Forwarded message from timeless <timeless@gmail.com> -----

From: timeless <timeless@gmail.com>
To: Thomas Roessler <tlr@w3.org>
Date: Wed, 6 Aug 2008 11:03:00 +0300
Subject: Re: Web Security Context: User Interface Guidelines
Reply-To: timeless@gmail.com
X-Spam-Level: 
X-Bogosity: Unsure, tests=bogofilter, spamicity=0.500000, version=1.1.6

http://www.w3.org/TR/2008/WD-wsc-ui-20080724/

initial spell checking after visual inspection flagged a word is done
by loading the text into data:text/html,<textarea rows=60 cols=85> in
Firefox 3.0.1 (en-US) and just looking for red squiggles.

>     6.1 Identity and Trust Anchor Signalling
>     6.4 Error handling and signalling

google says the web favors signaling 3:1 (Firefox says signalling
isn't a word{).
Wikipedia says:
  signalling (UK spelling) or signaling (US spelling) has the
following meanings:

> [WSC-USECASES] documents the use cases and assumptions that underly this specification.

underlie or underlay

> Mike Beltzner, Joe Steele,Jan Vidar Krey, Maritza Johnson, Rachna Dhamija and Dan Schutzer.

space missing before "Jan"

> It has also benefitted from general public and working group commentary on earlier drafts.

benefited

> This specification also addresses products that might incporate changes to a web

incorporate

> acceptance was caused through a user interaction that happens whlie the user is

while

> those roots embody augmented assurance and can therefore be treated more favourably
> both display the "padlock" security indicator, and a possible "favorite icon"

As an American, I'd expect favorably....

> The identity of the top level resource vouches for the content of all dependant

dependent

=
> This specification addresses Web user agents as one class of product.

typically I expect "class of thing_s_" do you mean "a product class"?`

>    3. What broadly accepted practices are considered sufficient for a trust anchor to be deemed augmented assurance qualified.
> Web user agents MUST establish that a trust anchor is [Definition: AA-qualified ]

use "augmented assurance qualified" or "aa-qualified" but not both :)



----- End forwarded message -----
Received on Wednesday, 6 August 2008 16:30:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:53:16 UTC