<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:41054866;
mso-list-type:hybrid;
mso-list-template-ids:582261462 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:500047241;
mso-list-type:hybrid;
mso-list-template-ids:1905044098 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:1624120558;
mso-list-type:hybrid;
mso-list-template-ids:-2027228842 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="Section1">
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">+1,
thanks Dick for driving this forward.</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">I'm
sure that there are lots of things that need to be resolved, but here are some
that seem to be critical at this point, welcome input from others.</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l2 level1 lfo2"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Is
it reasonable to try to integrate OpenID Connect charter into the V.Next WG
charter or do we need separate charters?</span></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l2 level1 lfo2"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Is
it reasonable to not fork the technology and still achieve the charters that
David & Joseph are advocating relative the charter that Nat & John
Bradley are advocating?</span></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l2 level1 lfo2"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">If
the answer to #2 is no, should we be willing to have a comprehensive OpenID
V.Next charter that allows for forking the technology, but manage it all within
the OIDF? </span></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l2 level1 lfo2"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">If
we are willing to allow forking of the technology, how do we minimize the
adverse impact on RPs and end users who may start out with one application or
use case, but then want to expand into others without breaking existing deployments?</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Also,
I know that we use the words "charter, requirements, specifications"
in foundation speak, but for clarity of understanding, I’d suggest we
think in terms of a “product” which is what the market wants from
us. In our case, the product isn’t code per se, but standards and
specifications that deliver functionality and benefits to the RP and end user
in a clear, consistent, reliable, and interoperable way. The best guidance I’ve
seen on moving from concept to product is from Pragmatic Marketing: <a href="http://www.pragmaticmarketing.com">http://www.pragmaticmarketing.com</a></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">As
I think about what we’re trying to accomplish, it seems like what we need
(regardless of what we call it) are the following:</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo3"><span style="font-size:12.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Market
Requirement Document (<a href="http://www.pragmaticmarketing.com/publications/topics/01/0104sj">MRD</a>)
– what needs in the market are we trying to address (easier registration
and login, portable reuse of personal profiles and other metadata, social
publishing across sites, enhanced security, etc.). As Eric and Raj observed at
the last board meeting, it doesn’t seem like we can paint this with a
broad brush. Perhaps there are some baseline requirements across all markets
and applications, but there may be unique requirements by segment (social web,
ecommerce, media & entertainment companies, government, etc.). Seems like
we should first agree on the key markets/applications and corresponding <a href="http://www.pragmaticmarketing.com/publications/magazine/1/4/0310sj/">personas</a>
and <a href="http://en.wikipedia.org/wiki/Use_case">use cases</a> we’re
trying to address with V.Next + OpenID Connect.</span></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo3"><span style="font-size:12.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Product
Requirement Document (<a href="http://en.wikipedia.org/wiki/Product_requirements_document">PRD</a>) –
this is designed to allow people within an organization to understand what a
product should do and how it should work. Key components are:</span></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:
l0 level2 lfo3"><span style="font-size:12.0pt;font-family:
"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Purpose
and scope, from both a technical and business perspective</span></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:
l0 level2 lfo3"><span style="font-size:12.0pt;font-family:
"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Stakeholder
identification</span></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:
l0 level2 lfo3"><span style="font-size:12.0pt;font-family:
"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Market
assessment and target demographics</span></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:
l0 level2 lfo3"><span style="font-size:12.0pt;font-family:
"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Product
overview and use cases</span></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:
l0 level2 lfo3"><span style="font-size:12.0pt;font-family:
"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Requirements,
including</span></p>
<p class="MsoPlainText" style="margin-left:1.5in;text-indent:-.25in;mso-list:
l0 level3 lfo3"><span style="font-size:12.0pt;font-family:
Wingdings"><span style="mso-list:Ignore">§<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">functional
requirements (e.g. what a product should do)</span></p>
<p class="MsoPlainText" style="margin-left:1.5in;text-indent:-.25in;mso-list:
l0 level3 lfo3"><span style="font-size:12.0pt;font-family:
Wingdings"><span style="mso-list:Ignore">§<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">usability
requirements</span></p>
<p class="MsoPlainText" style="margin-left:1.5in;text-indent:-.25in;mso-list:
l0 level3 lfo3"><span style="font-size:12.0pt;font-family:
Wingdings"><span style="mso-list:Ignore">§<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">technical
requirements (e.g. security, network, platform, integration, client)</span></p>
<p class="MsoPlainText" style="margin-left:1.5in;text-indent:-.25in;mso-list:
l0 level3 lfo3"><span style="font-size:12.0pt;font-family:
Wingdings"><span style="mso-list:Ignore">§<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">environmental
requirements</span></p>
<p class="MsoPlainText" style="margin-left:1.5in;text-indent:-.25in;mso-list:
l0 level3 lfo3"><span style="font-size:12.0pt;font-family:
Wingdings"><span style="mso-list:Ignore">§<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">support
requirements</span></p>
<p class="MsoPlainText" style="margin-left:1.5in;text-indent:-.25in;mso-list:
l0 level3 lfo3"><span style="font-size:12.0pt;font-family:
Wingdings"><span style="mso-list:Ignore">§<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">interaction
requirements (e.g. how the software should work with other systems)</span></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:
l0 level2 lfo3"><span style="font-size:12.0pt;font-family:
"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Constraints</span></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:
l0 level2 lfo3"><span style="font-size:12.0pt;font-family:
"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Workflow
plans, timelines and milestones</span></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:
l0 level2 lfo3"><span style="font-size:12.0pt;font-family:
"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Evaluation
plan and performance metrics</span></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo3"><span style="font-size:12.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Functional
Specification (FS) – Seems like only after we have agreement on the MRD
and PRD can we deliver the FS and any corresponding open source libraries, test
suites, deployment guides, etc.</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Maybe
this seems like a lot of work, and it is non-trivial, but unless we agree on
what we’re trying to deliver, for who, and with what benefits, it will be
hard for us to succeed. You wouldn’t typically try to build a house
without architectural designs and construction drawings, and if you did, you
might not get what you thought wanted at the outset.</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">I’m
not advocating that this has to be overly detailed and protracted, but if we
can quickly come to consensus on some of these things, it seems like it will accelerate
our long term progress and reduce a lot of friction along the way. It will
also be invaluable in communicating to RPs and end users what to expect –
not only from V.Next, but w.r.t. the other initiatives like Artifact Binding,
Discovery, Contract Exchange, OAuth 2.0, Portable Contacts, Activity Streams, etc.
and how all these will work together to address market needs. I’d love
to see us publish an MRD and PRD for V.Next (using whatever nomenclature we
think is appropriate) on the OpenID Foundation website to share with the world
on what’s coming.</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""><br>
Welcoming input from others.</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Cheers,</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Brian</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">___________</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Brian
Kissel</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">CEO
- JanRain, Inc.</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""><a href="mailto:bkissel@janrain.com">bkissel@janrain.com</a></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Mobile:
503.342.2668 | Fax: 503.296.5502</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">519
SW 3rd Ave. Suite 600 Portland, OR 97204</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Increase
registrations, engage users, and grow your brand with RPX. Learn more at
<a href="http://www.rpxnow.com">www.rpxnow.com</a></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">-----Original
Message-----<br>
From: <a href="mailto:openid-board-bounces@lists.openid.net">openid-board-bounces@lists.openid.net</a>
[mailto:<a href="mailto:openid-board-bounces@lists.openid.net">openid-board-bounces@lists.openid.net</a>] On Behalf Of Dick Hardt<br>
Sent: Sunday, May 23, 2010 10:05 AM<br>
To: David Recordon; Joseph Smarr; Allen Tom<br>
Cc: <a href="mailto:board@openid.net">board@openid.net</a><br>
Subject: [OpenID board] in-person chat about Connect and v.Next<br>
Importance: High</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">David,
Joseph, Allen</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">As
fellow board members, fellow tech comm members and local residents, I believe
it would be useful for the four of us to get together and hash out these
topics. </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Would
you guys be interested in getting together?</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">If
so, Monday afternoon or evening works for me. Alternatively, how about Friday
afternoon? (I am in Denver for Glucon Tue-Thu)</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">I
could also meet this afternoon or evening (Sunday) -- but that is likely too
short of notice.</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">Somewhere
in SF that is not too loud that serves beer and yummy snacks. My treat!</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">I
think it is everyone's interest that we start rowing together in the OpenID
boat: the community is looking to us for leadership.</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">(If
others feel that could contribute and are able to meet in person, you are more
than welcome to join!)</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">--
Dick</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">_______________________________________________</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif"">board
mailing list</span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""><a href="mailto:board@lists.openid.net">board@lists.openid.net</a></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt;font-family:"Calibri","sans-serif""><a href="http://lists.openid.net/mailman/listinfo/openid-board">http://lists.openid.net/mailman/listinfo/openid-board</a></span></p>
</div>
</body>
</html>