<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<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:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
p.ClauseLevel1, li.ClauseLevel1, div.ClauseLevel1
{mso-style-name:"Clause Level 1";
margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
text-align:justify;
text-indent:0in;
mso-list:l2 level1 lfo1;
font-size:9.0pt;
font-family:"Verdana","sans-serif";}
p.ClauseLevel2, li.ClauseLevel2, div.ClauseLevel2
{mso-style-name:"Clause Level 2";
margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
text-align:justify;
text-indent:.35in;
mso-list:l2 level2 lfo1;
font-size:9.0pt;
font-family:"Verdana","sans-serif";}
p.ClauseLevel3, li.ClauseLevel3, div.ClauseLevel3
{mso-style-name:"Clause Level 3";
margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
text-align:justify;
text-indent:.7in;
mso-list:l2 level3 lfo1;
font-size:9.0pt;
font-family:"Verdana","sans-serif";}
p.ClauseLevel4, li.ClauseLevel4, div.ClauseLevel4
{mso-style-name:"Clause Level 4";
margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
text-align:justify;
text-indent:1.05in;
mso-list:l2 level4 lfo1;
font-size:9.0pt;
font-family:"Verdana","sans-serif";}
.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:693386956;
mso-list-type:hybrid;
mso-list-template-ids:-1113660758 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 l1
{mso-list-id:2082367152;
mso-list-type:hybrid;
mso-list-template-ids:1520368098 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1: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 l2
{mso-list-id:2120446173;
mso-list-template-ids:2037165994;}
@list l2:level1
{mso-level-style-link:"Clause Level 1";
mso-level-text:%1;
mso-level-tab-stop:.35in;
mso-level-number-position:left;
margin-left:0in;
text-indent:0in;
mso-ansi-font-size:9.0pt;
font-family:"Verdana","sans-serif";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
@list l2:level2
{mso-level-style-link:"Clause Level 2";
mso-level-text:"%1\.%2";
mso-level-tab-stop:.7in;
mso-level-number-position:left;
margin-left:0in;
text-indent:.35in;
mso-ansi-font-size:9.0pt;
font-family:"Verdana","sans-serif";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
@list l2:level3
{mso-level-number-format:alpha-lower;
mso-level-style-link:"Clause Level 3";
mso-level-text:"\(%3\)";
mso-level-tab-stop:1.05in;
mso-level-number-position:left;
margin-left:0in;
text-indent:.7in;
mso-ansi-font-size:9.0pt;
font-family:"Verdana","sans-serif";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
@list l2:level4
{mso-level-number-format:roman-lower;
mso-level-style-link:"Clause Level 4";
mso-level-text:"\(%4\)";
mso-level-tab-stop:1.4in;
mso-level-number-position:left;
margin-left:0in;
text-indent:1.05in;
mso-ansi-font-size:9.0pt;
font-family:"Verdana","sans-serif";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
@list l2:level5
{mso-level-number-format:alpha-lower;
mso-level-text:"\(%5\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;}
@list l2:level6
{mso-level-number-format:roman-lower;
mso-level-text:"\(%6\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.5in;
text-indent:-.25in;}
@list l2:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;}
@list l2:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.0in;
text-indent:-.25in;}
@list l2:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>That’s my understanding of the process as well, David. It
sounds like we may already have consensus on Nat. I hope we choose the
remaining member by consensus as well. I would personally be fine with either
Breno or Joseph for the remaining member. What do others think?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>For reference, the relevant definitions from the process doc are:<o:p></o:p></span></p>
<p class=ClauseLevel2 style='margin-left:.35in;text-indent:0in;mso-list:none'><b>1.5
</b>“<b>Eligible Editors</b>” means, as determined on a given date,
all Editors from current WGs and all other persons who: (a) were WG
Editors at any time in the two years before such date; (b) are alive and
have provided and maintained updated contact information with the OpenID
Foundation; and (c) elect to participate in selection of the
Specifications Council after at least seven days’ email notice.<o:p></o:p></p>
<p class=ClauseLevel2 style='margin-left:.35in;text-indent:0in;mso-list:none'><b>1.8
</b>“<b>Specifications Council</b>” means a group comprised of:
(a) two representatives selected by the Board; and (b) five
representatives selected by the Eligible Editors. The Board may select from
among the current Board members (or other appropriate persons, as determined by
the Board), and the Eligible Editors may select from among themselves (or other
appropriate persons, as the Eligible Editors determine).<o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Here’s a start at an informal list of who the eligible editors
are that should select the remaining specs council member, should we not reach
consensus without a vote or more formal process.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo3'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>From PAPE: David Recordon and I did most of the actual editing
by my recollection, with Johnny Bufu and Jonathan Daugherty also listed as
editors.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo3'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>From UI: Allen Tom, Breno de Medeiros<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo3'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>From CX: Nat Sakimura<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo3'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>From Artifact: Nat Sakimura. Is John Bradley also an editor
too? It’s hard to tell from the spec draft.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo3'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>From Hybrid: Dirk Balfanz, Breno de Medeiros, David Recordon,
Joseph Smarr, Allen Tom<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo3'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>From AX 1.1: Allen Tom, Breno de Medeiros<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I may have missed specs and editors, and if so, others should
speak up.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I believe that the other specs are all older than two years ago
and/or don’t have current working groups, although I wouldn’t be
opposed to including input from editors of the older specs as part of a
consensus-based selection process.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> --
Mike<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>P.S. I added Jonathan Daugherty and John Bradley to this
thread, since they appear to be eligible editors.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<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"'> David Recordon
[mailto:recordond@gmail.com] <br>
<b>Sent:</b> Tuesday, May 25, 2010 9:43 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Allen Tom; Johnny Bufu; openid-specs-council@lists.openid.net; Josh
Hoyt; Dick Hardt; Breno de Medeiros; Nat Sakimura; Joseph Smarr<br>
<b>Subject:</b> Re: Refreshing the OpenID specs council<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Given that the UX Extension was never finalized, I think
everyone is on a level playing field.<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>The Specs Council is made up of two people appointed by the
Board and five by the "Eligible Editors". The Editors are supposed to
select among themselves, but can appoint other appropriate people as well.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I'd recommend adding Nat and Joseph given that the
Hybrid extension has had more deployment than UX and his experience editing
other specifications such as Portable Contacts.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>--David<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
<div>
<p class=MsoNormal>On Tue, May 25, 2010 at 10:26 AM, Mike Jones <<a
href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>>
wrote:<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>At this point, we have affirmative responses from all but
Brad and Josh. I propose that we now invite Breno and Nat to join the
council to replace Brad and Josh.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>I agree that Dirk, Joseph, and John all bring strong
qualifications, but to my knowledge, none have served as OpenID specification
editors, whereas Breno and Nat have.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>Are there any objections to now inviting them to join?</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>
-- Mike</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> <a
href="mailto:openid-specs-council-bounces@lists.openid.net" target="_blank">openid-specs-council-bounces@lists.openid.net</a>
[mailto:<a href="mailto:openid-specs-council-bounces@lists.openid.net"
target="_blank">openid-specs-council-bounces@lists.openid.net</a>] <b>On Behalf
Of </b>Allen Tom<br>
<b>Sent:</b> Sunday, May 23, 2010 6:05 PM<br>
<b>To:</b> David Recordon; Mike Jones<br>
<b>Cc:</b> Johnny Bufu; Brad Fitzpatrick; <a
href="mailto:openid-specs-council@lists.openid.net" target="_blank">openid-specs-council@lists.openid.net</a>;
Josh Hoyt; Dick Hardt<br>
<b>Subject:</b> Re: [OIDFSC] Refreshing the OpenID specs council</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
style='font-size:11.0pt'>Yes, I’d like to remain active on the specs
council.<br>
<br>
In addition to Breno and Nat, I also think that Dirk Balfanz, Joseph Smarr, and
John Bradley would also be really good additions.<br>
<br>
Allen<br>
<br>
<br>
On 5/23/10 5:49 PM, "David Recordon" <<a
href="http://recordond@gmail.com" target="_blank">recordond@gmail.com</a>>
wrote:</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt'>Yes, I will remain active.<br>
<br>
On Sun, May 23, 2010 at 2:46 PM, Dick Hardt <<a
href="http://dick.hardt@gmail.com" target="_blank">dick.hardt@gmail.com</a>>
wrote:</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
style='font-size:11.0pt'>Yes, I will remain active on the specs council.<br>
<br>
On 2010-05-23, at 1:04 PM, Mike Jones wrote:</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt'>As several OpenID working groups are being proposed,
it would be good to ensure that the OpenID specifications council is populated
with people who are currently active in specification development and have the
appropriate expertise. Per <span style='color:blue'>this note <<a
href="http://lists.openid.net/pipermail/openid-board/2008-June/002989.html"
target="_blank">http://lists.openid.net/pipermail/openid-board/2008-June/002989.html</a>>
</span>, the council currently consists of these people, who are subscribed to
the openid-specs-council list with these addresses:<br>
- Allen Tom atom at <span style='color:blue'><a
href="http://yahoo-inc.com" target="_blank">yahoo-inc.com</a> <<a
href="http://yahoo-inc.com" target="_blank">http://yahoo-inc.com</a>> <br>
</span> - Brad Fitzpatrick brad at <span style='color:blue'><a
href="http://danga.com" target="_blank">danga.com</a> <<a
href="http://danga.com" target="_blank">http://danga.com</a>> <br>
</span> - David Recordon recordond at <span style='color:blue'><a
href="http://gmail.com" target="_blank">gmail.com</a> <<a
href="http://gmail.com" target="_blank">http://gmail.com</a>> <br>
</span> - Johnny Bufu johnny.bufu at <span style='color:blue'><a
href="http://gmail.com" target="_blank">gmail.com</a> <<a
href="http://gmail.com" target="_blank">http://gmail.com</a>> <br>
</span> - Josh Hoyt josh at <span style='color:blue'><a
href="http://janrain.com" target="_blank">janrain.com</a> <<a
href="http://janrain.com" target="_blank">http://janrain.com</a>> <br>
</span> - Dick Hardt dick.hardt at <span style='color:blue'><a
href="http://gmail.com" target="_blank">gmail.com</a> <<a
href="http://gmail.com" target="_blank">http://gmail.com</a>> <br>
</span> - Mike Jones michael.jones at <span style='color:blue'><a
href="http://microsoft.com" target="_blank">microsoft.com</a> <<a
href="http://microsoft.com" target="_blank">http://microsoft.com</a>> <br>
</span> <br>
Can each of you who plan to remain active on the specifications council PLEASE
RESPOND affirmatively to this note in the next few days? Otherwise, we
should offer the positions to other spec editors who will be active. Nat
Sakimura is certainly one person who comes to mind, as editor of the CX and
Artifact Binding specifications, and also Breno de Medeiros, who is an editor
for the User Interface Extension.<br>
<br>
To update your subscription to the openid-specs-council list, go to <span
style='color:blue'><a
href="http://lists.openid.net/mailman/listinfo/openid-specs-council"
target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-council</a></span>.<br>
<br>
Thanks,<br>
-- Mike<br>
<br>
As a reminder of the role of the specifications council, here are some of the
relevant passages from the <span style='color:blue'>OpenID Process
document <<a
href="http://openid.net/wordpress-content/uploads/2010/01/OpenID_Process_Document_December_2009_Final_Approved.pdf"
target="_blank">http://openid.net/wordpress-content/uploads/2010/01/OpenID_Process_Document_December_2009_Final_Approved.pdf</a>>
</span>:<br>
<br>
</span><b><span style='font-size:9.0pt'>1.4</span></b><span style='font-size:
9.0pt'> “<b>Editor(s)</b>” means, for a particular
Specification to be developed by a particular WG, the individual Contributor(s)
selected to coordinate development of, and transcription of the work of the WG
for, such Specification, as well as (together with any other Editors for that
WG) to administer WG operation.<br>
</span><br>
<b><span style='font-size:9.0pt'>1.5</span></b><span style='font-size:9.0pt'>
“<b>Eligible Editors</b>” means, as determined on a given date, all
Editors from current WGs and all other persons who: (a) were WG Editors at
any time in the two years before such date; (b) are alive and have
provided and maintained updated contact information with the OpenID Foundation;
and (c) elect to participate in selection of the Specifications Council
after at least seven days’ email notice.<br>
</span><br>
<b><span style='font-size:9.0pt'>1.6</span></b><span style='font-size:9.0pt'>
“<b>Specifications Council</b>” means a group comprised of:
(a) two representatives selected by the Board; and (b) five
representatives selected by the Eligible Editors. The Board may select
from among the current Board members (or other appropriate persons, as
determined by the Board), and the Eligible Editors may select from among
themselves (or other appropriate persons, as the Eligible Editors determine).<br>
</span><br>
<span style='font-size:11.0pt'> <br>
</span><b><span style='font-size:9.0pt'>2 Specifications Council.</span></b><span
style='font-size:9.0pt'> The initial Specifications Council, as of the
date these Processes are adopted, will be comprised of two persons selected by
the Board and five persons selected by the then-current OpenID Authentication
2.0 Specification Editors. The members of the Specifications Council will
serve for two year terms (although one of the initial members selected by the
Board and two of the initial members selected by the Editors of the OpenID
Authentication 2.0 Specification will serve for only a one year term – as
selected by consensus of the Specifications Council – so that
Specifications Council membership terms may be staggered). There are no
“term limits” for Specifications Council membership, and the Board
or Eligible Editors, as applicable, may re-select the same persons to serve for
more than one term (consecutive or otherwise). In the event that a
Specifications Council member failed to participate in the discussion of two
consecutive working group proposals, the member will be deemed to have
resigned, and new specifications council members who are committed to
participating in the process will be appointed to replace the member.<br>
</span><br>
<span style='font-size:11.0pt'> <br>
</span><b><span style='font-size:9.0pt'>4.2 Review.</span></b><span
style='font-size:9.0pt'> The Specifications Council will review each
proposal within 15 days after receipt and promptly provide notice to <span
style='color:blue'><a href="http://specs@openid.net" target="_blank">specs@openid.net</a></span> of
its recommendation to either accept or reject it, together with a brief
statement of the rationale for its recommendation (including any findings or
opinions by the Specifications Council regarding the criteria for rejection in
the following clauses (a)-(d). If a proposal is rejected, it may be modified
and resubmitted. The reasons for rejection will be limited to:<br>
</span><br>
<b><span style='font-size:9.0pt'>(a) </span></b><span
style='font-size:9.0pt'>an incomplete Proposal (i.e., failure to comply with
§4.1);<br>
</span><br>
<b><span style='font-size:9.0pt'>(b) </span></b><span
style='font-size:9.0pt'>a determination that the proposal contravenes the
OpenID community’s purpose;<br>
</span><br>
<b><span style='font-size:9.0pt'>(c) </span></b><span
style='font-size:9.0pt'>a determination that the proposed WG does not have
sufficient support to succeed or to deliver proposed deliverables within
projected completion dates; or<br>
</span><br>
<b><span style='font-size:9.0pt'>(d) </span></b><span
style='font-size:9.0pt'>a determination that the proposal is likely to
cause legal liability for the OIDF or others.<br>
</span><br>
<span style='font-size:9.0pt'>If no recommendation was issued within 15 days
after receipt, the Proposal is deemed to be accepted.<br>
</span><br>
<span style='font-size:9.0pt'>When the Specifications Council rejects the
proposal, the Proposers may submit the Proposal to a vote of the OIDF
membership, in accordance with the voting procedures in §3. When the vote
passes, the proposal is deemed to be accepted. </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</body>
</html>