Re: ISSUE-244: UI conformance criteria for TLS indicator and Identity Signal [wsc-xit]

Some more discussion during today's below-critical-mass meeting led to a slightly different approach for the text in 6.1.

I've updated the text there to work as follows:

- The identity signal is, by definition, in primary UI.  That takes a lot of the complexity out of 6.1.1.
- The issuer (which is really the one thing that isn't displayed consistently) MUST be either in primary chrome, or in something that's easy to get to through the identity signal.

Please review the text ASAP and indicate whether there are any problems with it.
   http://www.w3.org/2006/WSC/drafts/rec/rewrite.html#IdentitySignal

We (Yngve, Mez, I) think that this corresponds well enough with current implementations, but *please* verify.

Thanks,
--
Thomas Roessler, W3C  <tlr@w3.org>







On 23 Feb 2010, at 00:24, Web Security Context Working Group Issue Tracker wrote:

> 
> ISSUE-244: UI conformance criteria for TLS indicator and Identity Signal [wsc-xit]
> 
> http://www.w3.org/2006/WSC/track/issues/244
> 
> Raised by: Thomas Roessler
> On product: wsc-xit
> 
> To clarify the identity signal and TLS indicator language, I propose:
> 
> - identifying the relevant user interface elements in conformance claims
> - changing the consistency requirement to reach the identity signal (XXIX and XXX) to SHOULD
> 
> (both of these changes are included with the current editor's draft)
> 
> We need to review whether XXVIII has sufficient implementation support, given the choice of identity signal UI component made by the various implementers.
> 
> 
> 
>

Received on Wednesday, 24 February 2010 17:57:42 UTC