<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@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;}
/* 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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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'>These motions all make sense to me – particularly since
creation of the PAPE working group was delayed for so long due to specs council
issues and I’m watching the same play out with the current
proposals. Having been there when we came up with the idea of the specs
council, the idea behind it was for it to provide useful feedback cutting
across the different specifications while proposals were being discussed and to
make a timely recommendation once a proposal was formally submitted – NOT
to be an impediment to the creation of working groups or a hurdle that
proposals had to clear.<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'>Thanks for taking the time to write these up, Nat. They should
make the specs council reality more closely match the intent, and substantially
improve the present situation.<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'> Thanks,<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>
<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"'>
board-bounces@openid.net [mailto:board-bounces@openid.net] <b>On Behalf Of </b>Brian
Kissel<br>
<b>Sent:</b> Thursday, January 15, 2009 9:17 AM<br>
<b>To:</b> board@openid.net<br>
<b>Subject:</b> Re: [OpenID board] Smoothing the OpenID Process<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Nat, thank you for your proactive efforts to help improve the
effectiveness and efficiency of our spec process. As I understand it, the
board needs to vote on your motions, then present to the membership for
approval. I second all four of Nat’s motions below for a vote by
the board.<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'>Hopefully we’ll have the board polling tool working this
week, so look for an email notification for pending board votes on each of these
motions.<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'>If others would like to discuss Nat’s proposals before the
vote, please provide your thoughts to the group.<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:navy'>Cheers,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:navy'><br>
Brian<o:p></o:p></span></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:navy'>==============<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:navy'>Brian Kissel<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:navy'>Cell: 503.866.4424<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:navy'>Fax: 503.296.5502<o:p></o:p></span></b></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"'> board-bounces@openid.net
[mailto:board-bounces@openid.net] <b>On Behalf Of </b>Nat Sakimura<br>
<b>Sent:</b> Thursday, January 15, 2009 12:01 AM<br>
<b>To:</b> board@openid.net<br>
<b>Subject:</b> [OpenID board] Smoothing the OpenID Process<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hi. <br>
<br>
After having worked through PAPE 1.0 spec process, as well as some other spec
proposals, I noticed that there can be several things that we can do to smooth
the process. I think they were worthwhile excercises to find out these
glitches. <br>
<br>
Followings are the proposed motions that I would like the board to consider.
There are two types: one that can take effect immediately, and one that
requires board and membership voting. <br>
<br>
<b>I. For immediate implementation of the current process: </b><br>
<br>
One of the obstacles that we have found during the process was that it was kind
of hard to get the specs council to deliver the recommendation in a timely
fashion. It has seen some improvement recently, but we want to make sure to
continue it. Thus, I would like to propose the following: <o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<b><i>BE IT RESOLVED that the OIDF Committee Liason is directed to act as the
coordinator for the specification council so that specification council create
a recommendation for the membership about a formal working group proposal
within 15 days of the complete proposal being circulated on <a
href="mailto:specs@openid.net" target="_blank">specs@openid.net</a> to comply
to the current OpenID process. </i></b><o:p></o:p></p>
</div>
<p class=MsoNormal><b>II. Improvements of curent porcess</b><br>
<br>
As a longer term solution, I would like to propose the following three motions.
The first two are to make sure the timely and effective response from the specs
council, and the last one is to protect the OpenID(TM) as well as to make it
easier to create a WG so that all the discussion will be done inside the WG and
the output is IPR clean. <o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><i><br>
BE IT RESOLVED that the members of OpenID Foundation board have agreed to amend
the OpenID process document so that should the specifications council not
create a recommendation for the membership about a formal working group
proposal within 15 days of the complete proposal being circulated on <a
href="mailto:specs@openid.net" target="_blank">specs@openid.net</a>, then the
proposal may proceed to a membership vote for approval. </i></b><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><i>BE IT RESOLVED that the
members of OpenID Foundation board have agreed to amend the OpenID process
document so that should specs council members not participate in the discussion
of two consecutive working group proposals, they will be deemed to have
resigned, and new specs council members who are committed to participating in the
process will be appointed to replace them.</i></b><o:p></o:p></p>
</div>
<p class=MsoNormal><b><i>BE IT RESOLVED that the members of OpenID Foundation
board have agreed to amend the OpenID process document to clarify that no draft
may claim OpenID trademark until it is ratified to be an implementor's draft
status or full specification status. </i></b><br>
<br>
Please note that these consitute the core decision for IPR and process, so it
will have to go through the membership vote as well after creating the actual
errata. <br>
<br>
Cheers, <br>
<br>
=nat<br clear=all>
<br>
-- <br>
Nat Sakimura (=nat)<br>
<a href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p>__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3768 (20090115) __________<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p>The message was checked by ESET NOD32 Antivirus.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p>http://www.eset.com<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p>__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3769 (20090115) __________<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p>The message was checked by ESET NOD32 Antivirus.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p>http://www.eset.com<o:p></o:p></p>
</div>
</body>
</html>