W3C home > Mailing lists > Public > public-wsc-wg@w3.org > October 2007

RE: ISSUE-97: Should logotypes be tied to EV certificates? [Techniques]

From: <michael.mccormick@wellsfargo.com>
Date: Wed, 3 Oct 2007 14:22:31 -0500
Message-ID: <9D471E876696BE4DA103E939AE64164D490EF2@msgswbmnmsp17.wellsfargo.com>
To: <tlr@w3.org>, <sysbot+tracker@w3.org>
Cc: <public-wsc-wg@w3.org>, <pbaker@verisign.com>

I like that language but for conformance purposes we need to be
explicit.  For example:

 - subject logo in a AA cert: MUST display in secondary, SHOULD display
in primary
 - community logo in a AA cert: MUST "      "    "    , SHOULD  "
"    "
 - issuer logo in a AA cert: SHOULD  "      "    "    , MAY     "
"    "

 - subject logo in a non-AA cert: MAY display in secondary, SHOULD NOT
display in primary
 - community logo in a non-AA cert: MAY "      "    "    , SHOULD NOT  "
"    "
 - issuer logo in a non-AA cert: MAY  "      "    "    , SHOULD NOT
"       "    "

Related action: Mike & Phill to submit a proposal to CAB Forum regarding
EV logo vetting.

-----Original Message-----
From: public-wsc-wg-request@w3.org [mailto:public-wsc-wg-request@w3.org]
On Behalf Of Thomas Roessler
Sent: Wednesday, October 03, 2007 1:14 PM
To: Web Security Context Working Group Issue Tracker
Cc: public-wsc-wg@w3.org
Subject: Re: ISSUE-97: Should logotypes be tied to EV certificates?
[Techniques]


On 2007-08-08 16:52:59 +0000, Web Security Context Working Group Issue
Tracker wrote:

> Should the display of logotypes associated with certificates be tied 
> to the use of Extended Validation certificates?

The resolution of this issue during today's meeting is that (a) with the
new definition of Augmented Assurance Certificates, and (b)
understanding that nothing in this resolution precludes use of logotypes
in different context -- the language of logotypes in the "identity
signal content" section should continue to condition use of logotypes
upon Augmented Assurance Certificates.

--
Thomas Roessler, W3C  <tlr@w3.org>
Received on Wednesday, 3 October 2007 19:23:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 5 February 2008 03:52:51 GMT