<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:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" 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="&#1;" 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: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:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        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:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.PlainTextChar
        {mso-style-name:"Plain Text Char";
        mso-style-priority:99;
        mso-style-link:"Plain Text";
        font-family:"Calibri","sans-serif";}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle21
        {mso-style-type:personal-reply;
        font-family:"Arial","sans-serif";
        font-variant:normal !important;
        text-transform:none;
        position:relative;
        top:0pt;
        mso-text-raise:0pt;
        letter-spacing:0pt;
        text-shadow:none;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;
        vertical-align:baseline;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-NZ" link="blue" vlink="purple">
<div class="Section1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Now the &#8216;other Colin&#8217; has a go</span><span style="font-size:10.0pt;
font-family:Wingdings">J</span><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Not much to add
<span style="background:yellow;mso-highlight:yellow">(in Yellow)</span> but .....
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:
&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang="EN-US" style="font-size:10.0pt;
font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> lc-bounces@kantarainitiative.org [mailto:lc-bounces@kantarainitiative.org]
<b>On Behalf Of </b>Colin Soutar<br>
<b>Sent:</b> Saturday, 16 June 2012 6:00 a.m.<br>
<b>To:</b> 'Heather Flanagan'; 'Kantara Leadership Council Kantara'<br>
<b>Subject:</b> Re: [KI-LC] By-Laws and Operating Procedures<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText"><span lang="EN-CA">Hi Heather -<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">I have some suggestions below for discussion.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">For ease of reference and discussion, I have embedded four suggestions in red font.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">Best regards,<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">Colin<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">Colin Soutar, Ph.D.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">email@colinsoutar.com<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">416 358 1431<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">-----Original Message-----<br>
From: lc-bounces@kantarainitiative.org [mailto:lc-bounces@kantarainitiative.org] On Behalf Of Heather Flanagan<br>
Sent: June-11-12 4:29 PM<br>
To: Kantara Leadership Council Kantara<br>
Subject: Re: [KI-LC] By-Laws and Operating Procedures</span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">And I have a clarification - this does NOT need a vote, this needs consensus (and yes, there's irony in trying to figure that out for the By-Laws and whatnot).<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">So, let's give this until FRIDAY JUNE 15 (that's this Friday) to see if there is any discussion/dissension/suggestions on the LC.&nbsp; If not, we shall consider consensus reached for these suggestions to go to the Board
 of Trustees.&nbsp; If there is a great deal of discussion, then we'll put it on the agenda for the LC call next week.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">-Heather<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">----- Original Message -----<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">From: &quot;Heather Flanagan&quot; &lt;<a href="mailto:hlflanagan@internet2.edu"><span style="color:windowtext;
text-decoration:none">hlflanagan@internet2.edu</span></a>&gt;<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">To: &quot;Kantara Leadership Council Kantara&quot; &lt;<a href="mailto:lc@kantarainitiative.org"><span style="color:windowtext;text-decoration:none">lc@kantarainitiative.org</span></a>&gt;<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">Sent: Monday, June 11, 2012 1:13:27 PM<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">Subject: [KI-LC] By-Laws and Operating Procedures<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">So, final write up on this one from me (completing my current action item for the LC). It is fairly long, but either I contain it all in one thread OR you all get peppered with lots of little emails all requiring your
 input - both methods have issues, so I just picked one.&nbsp;&nbsp; Based on LC mailing list traffic, meeting notes, and one-on-one conversations, the following areas should be brought to the Board for discussion or approval of new text.&nbsp;
<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">Joni, does the LC need to vote on any/all of those before it goes to the BoT?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">-Heather<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">----<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">By-Laws - Subscriber class information needs modification OLD<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">1.19 &quot;Subscriber&quot;<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">means any entity that has completed the necessary application forms, satisfi3d the objective subscriber criteria for the Organization, executed a copy of the Member Agreement (with Subscriber selected), and paid the
 appropriate Subscriber Fee as established by the Board of Trustees.&nbsp; A Subscriber may be an individual, corporation, partnership, join venture, trust, limited liability company, business association, governmental entity or other entity.&nbsp; Subscribers are typically
 those entities that are Certification and Assurance Programs stakeholders.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">NEW (proposed)<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">1.19 &quot;Subscriber&quot;<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">means any entity that has completed the necessary application forms, satisfied the objective subscriber criteria for the Organization, executed a copy of the Member Agreement (with Subscriber selected), and paid the
 appropriate Subscriber Fee as established by the Board of Trustees.&nbsp; A Subscriber may be an individual, corporation, partnership, join venture, trust, limited liability company, business association, governmental entity or other entity.&nbsp; Subscribers are typically
 those entities that are Interoperability Certification and Identity Assurance Accreditation and Approval Programs stakeholders.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">OLD<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">8.3 Subscribers<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">A Subscriber is any entity that has completed the necessary application forms, satisfied the objective subscriber criteria for the Organization, executed a copy of the Member Agreement (with Subscriber selected), and
 paid the appropriate Subscriber Fee as established by the Board of Trustees. A Subscriber may be an individual, corporation, partnership, joint venture, trust, limited liability company, business association, governmental entity or other entity. Subscribers
 are typically those entities that are Certification and Assurance Programs stakeholders.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">NEW (proposed)<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">8.3 Subscribers<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">A Subscriber is any entity that has completed the necessary application forms, satisfied the objective subscriber criteria for the Organization, executed a copy of the Member Agreement (with Subscriber selected), and
 paid the appropriate Subscriber Fee as established by the Board of Trustees. A Subscriber may be an individual, corporation, partnership, joint venture, trust, limited liability company, business association, governmental entity or other entity. Subscribers
 are typically those entities that are Interoperability Certification and Identity Assurance Accreditation and Approval Programs stakeholders.&nbsp; Subscribers would vote only at the WG/DG level and not in all-member votes.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">----<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">By-Laws - IPR and Copyright<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">May want to review whether it is reasonable for KI to continue with the model of WG/DG deciding their own IPR.&nbsp; Perhaps have a base IPR policy explicitly mentioned in the By-laws and allow WG/DG to do something different
 if explained/required?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA" style="font-size:10.0pt;font-family:
&quot;Arial&quot;,&quot;sans-serif&quot;;background:yellow;mso-highlight:yellow">CW: Noting that no-one has commented on this which I find surprising. I guess no comment means the status quo continues
 which I think is more transparent than the baseline/exception alternative.</span><span lang="EN-CA" style="font-size:10.0pt;
font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">----<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">By-Laws - benefits of Membership<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">8.2 &quot;Participants&quot; states that &quot;Participants do not enjoy Member benefits listed in the section above.&quot;&nbsp; Previous section (8.1.2) refers to Trustee benefits and again states &quot;In addition to all Member benefits...&quot;&nbsp;
 But in no prior (or later) section are there explicit Member benefits.&nbsp; Instead, a member is defined as: any entity that has completed the application forms, satisfied the objective membership criteria for the Organization, executed a copy of the Member Agreement,
 and paid the appropriate Membership Fee as established by the Board of Trustees.&nbsp; A Member may be an individual, corporation, partnership, join venture, trust, limited liability company, business association, governmental entity or other entity.
<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">There is a slide deck that is more explicit with regards to Member benefits.&nbsp; Consider the following changes:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">OLD<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">8.1.1 Member<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">A Member is any entity that has completed the application forms, satisfied the objective membership criteria for the Organization, executed a copy of the Member Agreement, and paid the appropriate Membership Fee as
 established by the Board of Trustees.&nbsp; A Member may be an individual, corporation, partnership, join venture, trust, limited liability company, business association, governmental entity or other entity.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">NW (proposed)<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">8.1.1 Member<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">any entity that has completed the application forms, satisfied the objective membership criteria for the Organization, executed a copy of the Member Agreement, and paid the appropriate Membership Fee as established
 by the Board of Trustees.&nbsp; A Member may be an individual, corporation, partnership, join venture, trust, limited liability company, business association, governmental entity or other entity.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">Member benefits include:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">* Access to non-public/confidential drafts through the Kantara Initiative liaison agreements and relationships<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA" style="color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
<span lang="EN-CA" style="color:red">1. I don't recall there being a confidentiality clause in the Kantara membership agreement that is the flow-through of our (Kantara's) obligation to third parties.&nbsp;&nbsp; We may consider adding a &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; clause in the membership
 agreement to this effect.</span><span lang="EN-CA" style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA" style="font-size:10.0pt;font-family:
&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA" style="font-size:10.0pt;font-family:
&quot;Arial&quot;,&quot;sans-serif&quot;;background:yellow;mso-highlight:yellow">CW: I checked the By Laws, Ops and then accessed the BoT Sub Committee page which is not open to the public and concur
 that no confidentiality clauses exists there. It may have shown one on joining up though..</span><span lang="EN-CA" style="font-size:10.0pt;
font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA" style="font-size:10.0pt;font-family:
&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">* Eligibility for positions on the Leadership Council<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA" style="color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
<span lang="EN-CA" style="color:red">2. Is this true for members that are not Officers of an WG/DG?</span><span lang="EN-CA" style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA" style="font-size:10.0pt;font-family:
&quot;Arial&quot;,&quot;sans-serif&quot;;background:yellow;mso-highlight:yellow">CW: I think it is but the practicality is that Officers go forward. Agree that this needs tidying per your suggestion
 below.</span><span lang="EN-CA" style="font-size:10.0pt;
font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">* Listing of Member Logo on web roster<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">* Ability to sponsor Work/Discussion Group formation<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">* Ability to request directed funding without overhead<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">----<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">By-Laws - defining &quot;Stakeholders&quot;<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">Kantara has the concept of stakeholders, often referred to in presentations or discussions.&nbsp; It also came up when discussing the Subscriber class (&quot;One idea floated was that for profile and criteria development stakeholders
 must be at least subscribers (== not non-funding participants)&quot;).&nbsp; Stakeholder is not however defined in the By-Laws nor the Operating Procedures.&nbsp; We should either more clearly define this term OR stop using it.&nbsp; If we want to more clearly define it, one
 possible definition could be (and I hope someone can come up with something better) :<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">NEW<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">&quot;Stakeholder&quot;<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">A Stakeholder is an entity that is affected by the discussions and actions taken by the Kantara Initiative from the working group level through to the Board of Trustees.&nbsp; A Stakeholder may be impacted by one or more
 efforts, discussions, or recommendations produced out of the Kantara Initiative's Members and Participants.&nbsp;&nbsp; A Stakeholder may be an individual, corporation, partnership, join venture, trust, limited liability company, business association, governmental entity
 or other entity.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA" style="font-size:10.0pt;font-family:
&quot;Arial&quot;,&quot;sans-serif&quot;;background:yellow;mso-highlight:yellow">CW: I don&#8217;t favour a new definition for Stakeholder. I think we can use it in presentations to indicate the active
 membership at large and imply the dictionary definition. I agree that &#8220;</span><span lang="EN-CA" style="background:yellow;
mso-highlight:yellow">that for profile and criteria development stakeholders must be at least subscribers (== not non-funding participants)&quot;</span><span lang="EN-CA" style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">----<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">Operating Procedures - WG and DG voting<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">The LC has explicit procedures for handling votes.&nbsp; All-member ballots also have explicit procedures.&nbsp; WG and DG don't, probably because it is expected those groups are to work on consensus as defined in the OP.&nbsp; However,
 those groups DO have to vote: for leadership positions, for decision making when consensus has failed.&nbsp; I suggest we basically copy section 2.6 in to the Working Group and Discussion Group sections, with the following modifications:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">1 - change &quot;LC to &quot;WG&quot; or &quot;DG&quot;<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">2 - IF the Subscriber class is approved by the BoT to have voting priv's in the WG/DG but NOT in the all-member ballots, we need to make that clear both in this new section as well as in the All-Member voting section.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA" style="font-size:10.0pt;font-family:
&quot;Arial&quot;,&quot;sans-serif&quot;;background:yellow;mso-highlight:yellow">CW: Agree with all this</span><span lang="EN-CA" style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">----<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">Operating Procedures - Nominations<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">Procedures for handling nominations to any leadership position are not laid out in the OP.&nbsp; Are there any categories of Members/Participants that are NOT allowed to be nominated in to a position?&nbsp; Should there be a
 minimum nomination period?&nbsp; Can anyone submit a nomination?&nbsp; Need to clarify these things.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA" style="color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
<span lang="EN-CA" style="color:red">3. As per my comment 2 above.</span><span lang="EN-CA" style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA" style="font-size:10.0pt;font-family:
&quot;Arial&quot;,&quot;sans-serif&quot;;background:yellow;mso-highlight:yellow">CW: Agree</span><span lang="EN-CA" style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">----<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">Operating Procedures - role of Secretary Would like to add to the summary report required of each WG Secretary a record of whether quorum was reached.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">Might be useful to mention that a DG MAY nominate a Secretary, and if they do, the Secretary will have similar responsibilities to that of a WG Secretary.&nbsp; If they don't, then the DG Chair is required to fulfill those
 responsibilities.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><span lang="EN-CA" style="color:red">4. I&#8217;d like to suggest that the following text be considered with regards to voting.&nbsp;&nbsp; The changes I have suggested would be generally consistent with operating procedures
 in SDO&#8217;s; would give some notice to the delinquent Participant of the impending action; and would avoid any perception of the ability for members to &#8220;vote hop&#8221;.&nbsp;&nbsp; Even though we have not suffered from this at all, the perception of the ability to attain voting
 rights &#8220;at will&#8221; in light of an &#8220;interesting&#8221; agenda item, I believe would be better removed, and is more respectful of the active body of the membership.
<o:p></o:p></span></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><span lang="EN-CA" style="color:red"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText" style="margin-left:72.0pt"><span lang="EN-CA" style="color:red">3.7<o:p></o:p></span></p>
<p class="MsoPlainText" style="margin-left:72.0pt"><span lang="EN-CA" style="color:red">OLD<o:p></o:p></span></p>
<p class="MsoPlainText" style="margin-left:72.0pt"><span lang="EN-CA" style="color:red">All Participants present at a WG meeting are voting members of the WG. For the purpose of maintaining a reasonable ability to achieve Quorum, any Participant in a WG who
 fails to attend two consecutive meetings of the WG may, at the discretion of the Chair, be re-classified as a non-voting member. Voting member status may be reacquired by attending a meeting of the WG. In the case of an electronic vote of the WG, if the electronic
 vote is initiated while a Participant is in non-voting status, the Participant may not vote in that electronic vote.<o:p></o:p></span></p>
<p class="MsoPlainText" style="margin-left:72.0pt"><span lang="EN-CA" style="color:red"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText" style="margin-left:72.0pt"><span lang="EN-CA" style="color:red">PROPOSED
<o:p></o:p></span></p>
<p class="MsoPlainText" style="margin-left:72.0pt"><span lang="EN-CA" style="color:red">All Participants present at a WG meeting are voting members of the WG, unless they have elected to be non-voting Participants. &nbsp;&nbsp;For the purpose of ensuring an active membership
 base is maintained, &nbsp;any Participant in a WG who fails to attend two consecutive meetings of the WG may, at the discretion of the Chair, be re-classified as a non-voting member. &nbsp;&nbsp;&nbsp;Such re-classification shall be stated in the agenda of the meeting in which
 it takes affect.&nbsp;&nbsp; Voting member status may be re-acquired by attending a meeting of the WG, in which case the voting member status is effective at the conclusion of the meeting.&nbsp;&nbsp; In the case of an electronic vote of the WG, if the electronic vote is initiated
 while a Participant is in non-voting status, the Participant may not vote in that electronic vote.<o:p></o:p></span></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><span lang="EN-CA" style="color:red"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><span lang="EN-CA" style="color:red">If adopted, this revised text would likely be similarly appropriate for clause 2.6 relating to the LC.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA" style="font-size:10.0pt;font-family:
&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA" style="font-size:10.0pt;font-family:
&quot;Arial&quot;,&quot;sans-serif&quot;;background:yellow;mso-highlight:yellow">CW: I sympathise with the intent. I&#8217;m worried that it will affect quorums which are already problematic. Still, I think
 it is worth doing for the reasons Colin S says and teh implication is that the draft Minutes will have to go to electronic vote more often. So the price for the change is a bit more work for the Secretaries.</span><span lang="EN-CA" style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA" style="color:black"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">----<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">Had enough yet? :-)<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">-Heather<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">_______________________________________________<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">LC mailing list<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><a href="mailto:LC@kantarainitiative.org"><span style="color:windowtext;text-decoration:none">LC@kantarainitiative.org</span></a><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><a href="http://kantarainitiative.org/mailman/listinfo/lc"><span style="color:
windowtext;text-decoration:none">http://kantarainitiative.org/mailman/listinfo/lc</span></a><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">_______________________________________________<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA">LC mailing list<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><a href="mailto:LC@kantarainitiative.org"><span style="color:windowtext;text-decoration:none">LC@kantarainitiative.org</span></a><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-CA"><a href="http://kantarainitiative.org/mailman/listinfo/lc"><span style="color:
windowtext;text-decoration:none">http://kantarainitiative.org/mailman/listinfo/lc</span></a><o:p></o:p></span></p>
</div>

====<BR>CAUTION:&nbsp; This email message and any attachments contain 
information that may be confidential and may be LEGALLY PRIVILEGED. If you are 
not the intended recipient, any use, disclosure or copying of this message or 
attachments is strictly prohibited. If you have received this email message in 
error please notify us immediately and erase all copies of the message and 
attachments. Thank you.<BR>====
</body>
</html>