<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Chris has the intent right -- I wanted something more iconic that
could be recognizable, distinct from either the existing OpenID or
OAuth brands (though definitely using elements from the former), and
easily dropped into things like presentation decks, websites, etc. I
want something that buttonizes well, and because they are
drastically different protocols, it can't look like the same button
that gets used for OpenID 2.0 today.<br>
<br>
One of the major things I've been doing lately has been trying to
keep people straight on the fact that Connect is a different
protocol than OpenID 2.0 (or earlier), and as such it has very
different usage and security profiles. The use of "OpenID" as a name
for a whole family of protocols including one very widely known
version can cause confusion here. For instance, some of the people
I've talked to have looked at OpenID 2.0, decided it doesn't fit
their use case for a variety of valid reasons, and moved on. Now
coming to the table with Connect, I find that they throw it into the
same "already decided it's bad" bucket as the legacy OpenID 2.0
stack. Will a distinct brand / logo fix this? Not on its own, but I
think it'd help. <br>
<br>
Do I think we should change the name? No, I think that OpenID
Connect makes a lot of sense. But I do think we need a bit more than
words, something overall more distinct for the uses and reasons
given above. <br>
<br>
I understand the hesitation of the OIDF in adopting anything like
this as "official", and I'm fine with the reasoning given for that.
But what are people like me, community members trying to get the
word out, supposed to do when we don't want just plain text? I like
pictures. I like shiny things. Until now, in the absence of any kind
of official iconography, I've been using Chris's dark gray button
from his original post about the OpenID Connect term:<br>
<br>
<a class="moz-txt-link-freetext" href="http://farm5.static.flickr.com/4053/4246318962_f1507a6a7f_o.png">http://farm5.static.flickr.com/4053/4246318962_f1507a6a7f_o.png</a><br>
<br>
But with all that said, because both Chris and a few members of the
WG here have requested, I'll not use this logo generally. Even
though I *really* like it (in concept at least, I think that it
still needs some work in execution). But I'm hoping that this thread
at least gets the right conversations started about this topic that
I think we'll have to address sooner or later.<br>
<br>
-- Justin<br>
<br>
On 04/10/2012 09:52 PM, Chris Messina wrote:
<blockquote
cite="mid:CADsRmeE11Fkhqev4yOAu1UwcMLOyTHrJSWd+u8Tqefm8K1S1zA@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
I also think that this is a bit confusing as it conflates these
brands when really they need to stand on their own.
<div><br>
</div>
<div>OAuth is a very particular brand/community with a different
org structure than the OIDF. If anything, the OpenID Connect
brand should derive from the OpenID logo, rather than from the
OAuth logo, even though there is a technical relationship
between the two.</div>
<div><br>
</div>
<div>I also think that more due consideration/investment should be
given to the OpenID Connect brand — though that's obviously not
in my hands at the moment. I appreciate Justin's efforts here,
but think that this logo misses the mark (pun intended).</div>
<div><br>
</div>
<div>A safer path (IMO) would be to simply use a word mark, like
this:</div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="http://www.flickr.com/photos/factoryjoe/4609980463/">http://www.flickr.com/photos/factoryjoe/4609980463/</a></div>
<div><br>
</div>
<div>…though I understand that there may be a desire to have a
more iconic representation of this technology for use on
stickers and the like… but that, I think, would require
additional design effort here.</div>
<div><br>
</div>
<div>FWIW, my intention was to release the OAuth mark under the "<a
moz-do-not-send="true"
href="http://factoryjoe.com/blog/2006/01/14/the-case-for-community-marks/">community
mark</a>" concept — and let the community enforce its use.
This is different from a copyright license of course… so, if I
do represent the OAuth community, I'd be wary if not opposed to
using this mark in this way.</div>
<div><br>
</div>
<div>Sorry Justin!<br>
<br>
<div class="gmail_quote">On Tue, Apr 10, 2012 at 5:04 PM,
Anthony Nadalin <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:tonynad@microsoft.com">tonynad@microsoft.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">We
should not be promoting this or using this logo as
this can cause OIDF legal issues now</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
Nat Sakimura [mailto:<a moz-do-not-send="true"
href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a>]
<br>
<b>Sent:</b> Tuesday, April 10, 2012 4:59 PM<br>
<b>To:</b> Pam Dingle<br>
<b>Cc:</b> Anthony Nadalin; Mike Jones; Richer,
Justin P.; OpenID ABC Working Group; Chris Messina</span></p>
<div>
<div class="h5"><br>
<b>Subject:</b> Re: [Openid-specs-ab] Branding for
OpenID Connect</div>
</div>
<div>
<div class="h5">
<p class="MsoNormal"> </p>
<p class="MsoNormal">I like the logo. Thank you very
much Justin and Chris. </p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I would send it to the
marketing committee to see what they can come up
with. </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">If I were in the position to
check it, I would first check if it constitute a
derivative mark of the OpenID trademark, and the
copyright and licensing status of the baseline
OAuth graphics. </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">If it is deemed to be
protected under our current trademark, that
would be very good as it would not incur us
additional cost as far as the trademark
registering is concerned. </p>
</div>
<div>
<p class="MsoNormal">If not, the cost issue will
kick in if we want to protect it. My feeling is
that it would be adequately protected under our
current trademark but it needs to be seen. </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">As to the copyright status of
the OAuth graphics is concerned, I understand
that it is CC-BY-SA. </p>
</div>
<div>
<p class="MsoNormal">(<a moz-do-not-send="true"
href="http://wiki.oauth.net/w/page/12238520/Logo"
target="_blank">http://wiki.oauth.net/w/page/12238520/Logo</a>) </p>
</div>
<div>
<p class="MsoNormal">So there does not seem
problem in modifying it like this one. </p>
</div>
<div>
<p class="MsoNormal">The potential problem I see
is that then the connect logo may become
CC-BY-SA as well. </p>
</div>
<div>
<p class="MsoNormal">If that is the case, I am not
sure how the trademark (which is obviously non
SA and ND) and this CC license intersection is
to be dealt with. </p>
</div>
<div>
<p class="MsoNormal">If Chris could license the
baseline graphics to OIDF with CC-BY, then it
may solve the issue, but it needs attorney
consultation. It would not be a big $$. </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">In any case, this is a
valuable community input and IMHO the marketing
committee should look at and make a
recommendation to the board. </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Pam, could you kindly send it
to the marketing committee so that they can deal
with it? </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Best, </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Nat</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">P.S. As far as I have check
in US, JP, Wipo, OAuth is not trademarked, which
I believe is a problem that OAuth community
should deal with. So, for the logo, it is only
the copyright that kicks in, and the copyright
holder I believe is Chris. </p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> </p>
<div>
<p class="MsoNormal">On Wed, Apr 11, 2012 at
4:02 AM, Pam Dingle <<a
moz-do-not-send="true"
href="mailto:pdingle@pingidentity.com"
target="_blank">pdingle@pingidentity.com</a>>
wrote:</p>
<p class="MsoNormal">It is a beautifully made
and distinctive logo. I really like it!
Mike and Tony are right though, we do need to
look at the cost to the foundation that this
could incur. If we choose to protect this
logo, there will be a not insubstantial legal
cost. If we choose not to protect this logo
and it is used anyway, there are also possible
consequences and costs. We need to make a
case to the board as to why that cost is
justified, and make an explicit and informed
branding decision.</p>
<div>
<div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<div>
<p class="MsoNormal"
style="margin-bottom:12.0pt"> </p>
<div>
<p class="MsoNormal">On Tue, Apr 10,
2012 at 11:40 AM, Anthony Nadalin
<<a moz-do-not-send="true"
href="mailto:tonynad@microsoft.com"
target="_blank">tonynad@microsoft.com</a>>
wrote:</p>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">agree</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<div>
<div
style="border:none;border-top:solid
#b5c4df 1.0pt;padding:3.0pt
0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a moz-do-not-send="true"
href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a>
[mailto:<a
moz-do-not-send="true"
href="mailto:openid-specs-ab-bounces@lists.openid.net"
target="_blank">openid-specs-ab-bounces@lists.openid.net</a>]
<b>On Behalf Of </b>Mike
Jones<br>
<b>Sent:</b> Tuesday,
April 10, 2012 11:35 AM<br>
<b>To:</b> Richer, Justin
P.; Nat Sakimura</span></p>
<div>
<div>
<p class="MsoNormal"><br>
<b>Cc:</b> OpenID ABC
Working Group; Chris
Messina<br>
<b>Subject:</b> Re:
[Openid-specs-ab]
Branding for OpenID
Connect</p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060">As
a board member, I believe
that I must object. The
trademark status of the
OAuth logo is unknown.
Combining the OpenID logo
with it could constitute
an act of infringement.</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060">Furthermore,
branding is a big deal.
We shouldn’t be publicly
displaying potential
branding elements until
there’s consensus,
including from the board,
that it’s the right thing
to do, and that the board
is committed to spending
the tens to hundreds of
thousands necessary to
defend a new trademark.</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060">
-- Mike</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060"> </span></p>
<div>
<div
style="border:none;border-top:solid
#b5c4df
1.0pt;padding:3.0pt 0in
0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a
moz-do-not-send="true"
href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a>
<a
moz-do-not-send="true"
href="mailto:[mailto:openid-specs-ab-bounces@lists.openid.net]"
target="_blank">
[mailto:openid-specs-ab-bounces@lists.openid.net]</a> <b>On Behalf Of </b>Richer,
Justin P.<br>
<b>Sent:</b> Tuesday,
April 10, 2012 11:29
AM<br>
<b>To:</b> Nat
Sakimura<br>
<b>Cc:</b> OpenID ABC
Working Group; Chris
Messina<br>
<b>Subject:</b> Re:
[Openid-specs-ab]
Branding for OpenID
Connect</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">OK,
taking the idea a step
further and working with the
shiny-logo file from Chris
Messina (thanks, Chris!),
this is what I've come up
with. It takes the OAuth
logo, replaces the text and
central logo, and adds a
bronze/orange tint to the
shiny bits. Unless the
working group objects
specifically, I'm going to
start using this in at least
my own talks.
</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"> --
Justin</p>
</div>
<div>
<p class="MsoNormal"><img
src="cid:part12.04050500.02060907@mitre.org"
border="0" height="635"
width="846"></p>
<div>
<div>
<p class="MsoNormal">On
Apr 5, 2012, at 6:23
PM, Nat Sakimura
wrote:</p>
</div>
<p class="MsoNormal"
style="margin-bottom:12.0pt"> </p>
<p class="MsoNormal"
style="margin-bottom:12.0pt"><330.gif></p>
<div>
<p class="MsoNormal">On
Fri, Apr 6, 2012 at
1:38 AM, Richer,
Justin P. <<a
moz-do-not-send="true"
href="mailto:jricher@mitre.org" target="_blank">jricher@mitre.org</a>>
wrote:</p>
<div>
<p class="MsoNormal">I
like Nat's idea, but
took it in a
slightly different
direction. This is
just a quick take on
a theme, for fun of
course. But add some
shininess to this
and I think it's
good! :) </p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"> --
Justin</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><OpenID
Connect
Logo.png></p>
</div>
<div>
<div>
<div>
<p
class="MsoNormal"> </p>
<div>
<div>
<p
class="MsoNormal">On
Apr 4, 2012,
at 6:50 PM,
Nat Sakimura
wrote:</p>
</div>
<p
class="MsoNormal"
style="margin-bottom:12.0pt"> </p>
<p
class="MsoNormal">Just
for the sake
of fun...
</p>
<div>
<p
class="MsoNormal"> </p>
</div>
<div>
<p
class="MsoNormal">OpenID
Connect on
OAuth logo. </p>
<div>
<p
class="MsoNormal"> </p>
</div>
<div>
<p
class="MsoNormal"><a
moz-do-not-send="true"
href="http://nat.sakimura.org/wp-content/uploads/2012/03/openid-connect-oauth-logo.png"
target="_blank">http://nat.sakimura.org/wp-content/uploads/2012/03/openid-connect-oauth-logo.png</a></p>
</div>
<div>
<p
class="MsoNormal"> </p>
</div>
<div>
<p
class="MsoNormal">It
is symbolizing
that OpenID
Connect is on
top of OAuth
:-) </p>
</div>
<div>
<p
class="MsoNormal"> </p>
</div>
<div>
<p
class="MsoNormal">Could
not get the
editable
version of the
shiny OAuth
2.0 logo, so
suffice it to
be with this. </p>
</div>
<div>
<p
class="MsoNormal"> </p>
</div>
<div>
<p
class="MsoNormal"
style="margin-bottom:12.0pt">=nat</p>
<div>
<p
class="MsoNormal">On
Thu, Apr 5,
2012 at 6:31
AM, Nat
Sakimura <<a
moz-do-not-send="true" href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a>>
wrote:</p>
<p
class="MsoNormal">Need
to check this
with a patent
lawyer but
including our
trademark
probably will
protect us.
</p>
<div>
<p
class="MsoNormal">FYI,
I just checked
the US filing,
and it is a <span
style="font-size:10.0pt;font-family:"Arial","sans-serif""> STANDARD
CHARACTER MARK
on the string
"OpenID". </span></p>
</div>
<div>
<p
class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">No logo.
Internationally,
the same. In
France and in
Japan, logo is
also
trademarked.
Maybe some
other
countries as
well. </span></p>
</div>
<div>
<p
class="MsoNormal"> </p>
</div>
<div>
<p
class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">So that
bottom line
is, if we want
a logo for
OpenID
Connect, which
I do, we
probably need
to include the
string
"OpenID". </span></p>
</div>
<div>
<p
class="MsoNormal"> </p>
</div>
<div>
<p
class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">The threat
is real. There
already is
somebody
trying to
register
SmartOpenID
internationally. </span></p>
</div>
<div>
<p
class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">We need to
take action,
if it looks
going through,
to defend our
right. </span></p>
</div>
<div>
<p
class="MsoNormal"> </p>
</div>
<div>
<p
class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">FYI, the
trademark
often is a
stronger IPR
claim than the
patent. </span></p>
</div>
<div>
<p
class="MsoNormal"> </p>
</div>
<div>
<p
class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">=nat</span></p>
<div>
<div>
<p
class="MsoNormal"> </p>
<div>
<p
class="MsoNormal">On
Thu, Apr 5,
2012 at 2:54
AM, John
Bradley <<a
moz-do-not-send="true" href="mailto:ve7jtb@ve7jtb.com" target="_blank">ve7jtb@ve7jtb.com</a>>
wrote:</p>
<div>
<p
class="MsoNormal">The
current openID
logo is into
many tens of
thousands and
the costs keep
mounting.
</p>
<div>
<p
class="MsoNormal"> </p>
</div>
<div>
<p
class="MsoNormal">The
problem is
that unless we
register and
defend it,
someone can
take it and
make it
proprietary. </p>
</div>
<div>
<p
class="MsoNormal"> </p>
</div>
<div>
<p
class="MsoNormal">There
may be ways to
have a
derivative
logo that cost
less
incrementally.
I am not an
expert on
this. </p>
</div>
<div>
<p
class="MsoNormal"> </p>
</div>
<div>
<p
class="MsoNormal">I
do however see
the bills.</p>
</div>
<div>
<p
class="MsoNormal"> </p>
</div>
<div>
<p
class="MsoNormal">John
B.
</p>
<div>
<div>
<p
class="MsoNormal"> </p>
<div>
<div>
<p
class="MsoNormal">On
2012-04-04, at
2:49 PM,
Justin Richer
wrote:</p>
</div>
<p
class="MsoNormal"
style="margin-bottom:12.0pt"> </p>
<div>
<p
class="MsoNormal">Really,
for something
like this? How
much has been
spent on the
OAuth logo to
date? I
understand
that the OIDF
may desire to
take ownership
of things like
and make them
official,
trademarked,
and
enforceable.
But what I'm
after is much
lighter than
that:
something
recognizable.<br>
<br>
-- Justin<br>
<br>
On 04/04/2012
01:46 PM, Mike
Jones wrote: </p>
<div>
<p
class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I’ll
just add that
I know that
maintaining a
logo worldwide
is a very
expensive
endeavor,
requiring
dozens of
registrations,
due diligence,
and
enforcement
actions – best
case tens of
thousands of
dollars, but
realistically,
often hundreds
of thousands
of dollars.
Creating a new
brand and logo
is not
something we
should do
lightly.</span></p>
<p
class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p
class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
-- Mike</span></p>
<p
class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<div>
<div
style="border:none;border-top:solid
#b5c4df
1.0pt;padding:3.0pt
0in 0in 0in">
<p
class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a
moz-do-not-send="true"
href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a>
[<a
moz-do-not-send="true"
href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">mailto:openid-specs-ab-bounces@lists.openid.net</a>]
<b>On Behalf
Of </b>Anthony
Nadalin<br>
<b>Sent:</b>
Wednesday,
April 04, 2012
10:11 AM<br>
<b>To:</b>
Justin Richer;
Pam Dingle<br>
<b>Cc:</b> <a
moz-do-not-send="true" href="mailto:openid-specs-ab@lists.openid.net"
target="_blank"><openid-specs-ab@lists.openid.net></a><br>
<b>Subject:</b>
Re:
[Openid-specs-ab]
Branding for
OpenID Connect</span></p>
</div>
</div>
<p
class="MsoNormal"> </p>
<p
class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I
think this is
a matter for
OIDF to take
up sine I
believe they
currently own
the OpenID
logo or are
about to own
that.</span></p>
<p
class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<div>
<div
style="border:none;border-top:solid
#b5c4df
1.0pt;padding:3.0pt
0in 0in 0in">
<p
class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
Justin Richer
<a
moz-do-not-send="true"
href="mailto:[mailto:jricher@mitre.org]" target="_blank">[mailto:jricher@mitre.org]</a>
<br>
<b>Sent:</b>
Wednesday,
April 04, 2012
10:07 AM<br>
<b>To:</b> Pam
Dingle<br>
<b>Cc:</b>
Anthony
Nadalin; <<a
moz-do-not-send="true" href="mailto:openid-specs-ab@lists.openid.net"
target="_blank">openid-specs-ab@lists.openid.net</a>><br>
<b>Subject:</b>
Re:
[Openid-specs-ab]
Branding for
OpenID Connect</span></p>
</div>
</div>
<p
class="MsoNormal"> </p>
<p
class="MsoNormal">Agree
completely
that it should
tie into the
overall
branding of
OpenID, and as
such should
probably
incorporate
the
line/circle/arrow
logo and
standard
OpenID font,
but with
something more
"connecty"
about it.<br>
<br>
-- Justin<br>
<br>
On 04/04/2012
12:53 PM, Pam
Dingle wrote:
</p>
<p
class="MsoNormal"
style="margin-bottom:12.0pt">+1 for something distinctive for OpenID
Connect, but
that doesn't
mean it can't
be related to
our overall
brand.</p>
<div>
<p
class="MsoNormal">On
Wed, Apr 4,
2012 at 12:01
PM, Anthony
Nadalin <<a
moz-do-not-send="true" href="mailto:tonynad@microsoft.com"
target="_blank">tonynad@microsoft.com</a>>
wrote:</p>
<p
class="MsoNormal">I
defer to the
logo gods on
the status of
the current
OpenID logo,
but I'm one
for not
introducing a
new one or a
different one
as it's an
overall OpenID
Brand</p>
<div>
<div>
<p
class="MsoNormal"><br>
-----Original
Message-----<br>
From: <a
moz-do-not-send="true"
href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a>
[mailto:<a
moz-do-not-send="true"
href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a>]
On Behalf Of
Richer, Justin
P.<br>
Sent:
Wednesday,
April 04, 2012
8:50 AM<br>
To: <<a
moz-do-not-send="true"
href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a>><br>
Subject:
[Openid-specs-ab]
Branding for
OpenID Connect<br>
<br>
As I've been
putting more
and more
presentations
together
talking about
OpenID
Connect, I
keep getting
stuck on the
lack of a
distinctive
logo for it.
Particularly
when I want to
distinguish
Connect from
OpenID 2.0 and
its
predecessors,
as they are
quite
different.
OAuth has its
black token,
and OAuth2 has
the shiny
token adapted
from that. The
best that I
could find was
from Chris
Messina's
original blog
post that
introduced us
all to the
terminology of
"OpenID
Connect",
here:<br>
<br>
<a
moz-do-not-send="true"
href="http://factoryjoe.com/blog/2010/01/04/openid-connect/"
target="_blank">http://factoryjoe.com/blog/2010/01/04/openid-connect/</a><br>
<br>
So I'm putting
it to the
group here: is
there a better
or more
official image
to represent
this protocol?
Should there
be?<br>
<br>
-- Justin<br>
_______________________________________________<br>
Openid-specs-ab
mailing list<br>
<a
moz-do-not-send="true"
href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a
moz-do-not-send="true"
href="http://lists.openid.net/mailman/listinfo/openid-specs-ab"
target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Openid-specs-ab
mailing list<br>
<a
moz-do-not-send="true"
href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a
moz-do-not-send="true"
href="http://lists.openid.net/mailman/listinfo/openid-specs-ab"
target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a></p>
</div>
</div>
</div>
<p
class="MsoNormal"><br>
<br
clear="all">
</p>
<div>
<p
class="MsoNormal"> </p>
</div>
<p
class="MsoNormal">--
<br>
<strong><span
style="font-size:9.0pt;font-family:"Tahoma","sans-serif";color:#343634">Pamela
Dingle</span></strong><span
style="font-size:9.0pt;font-family:"Tahoma","sans-serif";color:#343634"> | Sr.
Technical
Architect</span><span
style="font-size:7.5pt;font-family:"Tahoma","sans-serif";color:#2a2a2a"><br>
</span><strong><span
style="font-size:8.5pt;font-family:"Tahoma","sans-serif";color:#343634">Ping</span></strong><strong><span
style="font-size:8.5pt;font-family:"Tahoma","sans-serif";color:#e71939">Identity</span></strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#2a2a2a"> |
<a
moz-do-not-send="true"
href="http://www.pingidentity.com/" target="_blank">www.pingidentity.com</a><br>
- - - - - - -
- - - - - - -
- - - - - - -
- - - - - - -
- - - - - - -
- - - - -<br>
</span><strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#005568">O:</span></strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#2a2a2a"> </span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#343634"><a
moz-do-not-send="true" href="tel:303-999-5890" target="_blank">303-999-5890</a></span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#2a2a2a"> </span><strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#005568">M:</span></strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#2a2a2a"> </span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#343634"><a
moz-do-not-send="true" href="tel:303-999-5890" target="_blank">303-999-5890</a></span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#2a2a2a"><br>
</span><strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#005568">Email:</span></strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#2a2a2a"> <a
moz-do-not-send="true" href="mailto:pdingle@pingidentity.com"
target="_blank">pdingle@pingidentity.com</a><br>
- - - - - - -
- - - - - - -
- - - - - - -
- - - - - - -
- - - - - - -
- - - - -</span></p>
<table
border="0"
cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<td
style="padding:0in
0in 0in 0in"
nowrap="nowrap"
valign="top">
<div>
<p
class="MsoNormal"><strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#005568">Connect
with Ping</span></strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif""><br>
Twitter:
@pingidentity<br>
LinkedIn
Group: Ping's
Identity
Cloud <br>
<a
moz-do-not-send="true"
href="http://Facebook.com/pingidentitypage" target="_blank">Facebook.com/pingidentitypage</a></span></p>
</div>
</td>
<td
style="padding:0in
0in 0in 0in"
nowrap="nowrap"
valign="top">
<div
style="margin-left:15.0pt">
<p
class="MsoNormal"><strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#005568">Connect
with me</span></strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif""><br>
Twitter:
@pamelarosiedee</span></p>
</div>
</td>
</tr>
</tbody>
</table>
<p
class="MsoNormal"> </p>
<p
class="MsoNormal"> </p>
</div>
<p
class="MsoNormal"> </p>
</div>
<p
class="MsoNormal">_______________________________________________<br>
Openid-specs-ab
mailing list<br>
<a
moz-do-not-send="true"
href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a
moz-do-not-send="true"
href="http://lists.openid.net/mailman/listinfo/openid-specs-ab"
target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a></p>
</div>
<p
class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
<p
class="MsoNormal"
style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Openid-specs-ab
mailing list<br>
<a
moz-do-not-send="true"
href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a
moz-do-not-send="true"
href="http://lists.openid.net/mailman/listinfo/openid-specs-ab"
target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a></p>
</div>
<p
class="MsoNormal"><br>
<br
clear="all">
</p>
<div>
<p
class="MsoNormal"> </p>
</div>
<p
class="MsoNormal">--
</p>
</div>
</div>
<p
class="MsoNormal"><span
style="color:#888888">Nat Sakimura (=nat)
</span></p>
<div>
<p
class="MsoNormal"><span
style="color:#888888">Chairman, OpenID Foundation<br>
<a
moz-do-not-send="true"
href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>
@_nat_en</span></p>
</div>
<p
class="MsoNormal"> </p>
</div>
</div>
<p
class="MsoNormal"><br>
<br
clear="all">
</p>
<div>
<p
class="MsoNormal"> </p>
</div>
<p
class="MsoNormal">--
<br>
Nat Sakimura
(=nat) </p>
<div>
<p
class="MsoNormal">Chairman,
OpenID
Foundation<br>
<a
moz-do-not-send="true"
href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>
@_nat_en</p>
</div>
<p
class="MsoNormal"> </p>
</div>
</div>
</div>
<p
class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
</p>
<div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal">--
<br>
Nat Sakimura (=nat) </p>
<div>
<p class="MsoNormal">Chairman,
OpenID Foundation<br>
<a
moz-do-not-send="true"
href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>
@_nat_en</p>
</div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"
style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a moz-do-not-send="true"
href="mailto:Openid-specs-ab@lists.openid.net"
target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a moz-do-not-send="true"
href="http://lists.openid.net/mailman/listinfo/openid-specs-ab"
target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a></p>
</div>
<p class="MsoNormal"><br>
<br clear="all">
</p>
<div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal">-- <br>
<strong><span
style="font-size:9.0pt;font-family:"Tahoma","sans-serif";color:#343634">Pamela
Dingle</span></strong><span
style="font-size:9.0pt;font-family:"Tahoma","sans-serif";color:#343634"> | Sr.
Technical Architect</span><span
style="font-size:7.5pt;font-family:"Tahoma","sans-serif";color:#2a2a2a"><br>
</span><strong><span
style="font-size:8.5pt;font-family:"Tahoma","sans-serif";color:#343634">Ping</span></strong><strong><span
style="font-size:8.5pt;font-family:"Tahoma","sans-serif";color:#e71939">Identity</span></strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#2a2a2a"> |
<a moz-do-not-send="true"
href="http://www.pingidentity.com"
target="_blank">www.pingidentity.com</a><br>
- - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - -
- - - -<br>
</span><strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#005568">O:</span></strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#2a2a2a"> </span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#343634"><a
moz-do-not-send="true"
href="tel:303-999-5890"
target="_blank">303-999-5890</a></span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#2a2a2a"> </span><strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#005568">M:</span></strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#2a2a2a"> </span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#343634"><a
moz-do-not-send="true"
href="tel:303-999-5890"
target="_blank">303-999-5890</a></span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#2a2a2a"><br>
</span><strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#005568">Email:</span></strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#2a2a2a"> <a
moz-do-not-send="true"
href="mailto:pdingle@pingidentity.com"
target="_blank">pdingle@pingidentity.com</a><br>
- - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - -
- - - -</span></p>
<table border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<td style="padding:0in 0in 0in
0in" nowrap="nowrap"
valign="top">
<div>
<p class="MsoNormal"><strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#005568">Connect
with Ping</span></strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif""><br>
<span style="">Twitter:
@pingidentity</span><br>
<span style="">LinkedIn
Group: Ping's Identity
Cloud</span> <br>
<span style="">Facebook.com/pingidentitypage</span></span></p>
</div>
</td>
<td style="padding:0in 0in 0in
0in" nowrap="nowrap"
valign="top">
<div style="margin-left:15.0pt">
<p class="MsoNormal"><strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#005568">Connect
with me</span></strong><span
style="font-size:8.5pt;font-family:"Arial","sans-serif""><br>
<span style="">Twitter:
@pamelarosiedee</span></span></p>
</div>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
</p>
<div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal">-- <br>
Nat Sakimura (=nat)</p>
<div>
<p class="MsoNormal">Chairman, OpenID Foundation<br>
<a moz-do-not-send="true"
href="http://nat.sakimura.org/"
target="_blank">http://nat.sakimura.org/</a><br>
@_nat_en</p>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
Chris Messina<br>
User Experience Designer, Google<br>
<br>
<div><a moz-do-not-send="true" href="http://chrismessina.me"
target="_blank">//chrismessina.me</a> | <a
moz-do-not-send="true"
href="https://plus.google.com/102034052532213921839"
target="_blank">+</a> | <a moz-do-not-send="true"
href="http://twitter.com/chrismessina" target="_blank">@chrismessina</a></div>
<div><br>
</div>
This email is: [ ] shareable [<span
style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(51,51,51)">✔</span>]
ask first [ ] private<br>
</div>
</blockquote>
<br>
</body>
</html>