<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=utf-8"><meta name=Generator content="Microsoft Word 15 (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;}
/* 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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;
color:black;}
span.EmailStyle19
{mso-style-type:personal-compose;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoPlainText>Thanks Klaus,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>One of my previous activities was as co-chair of the Legal Committee of the <a href="http://www.openwebfoundation.org/">Open Web Foundation</a>. This organization prepared a set of agreements for specifications that would/could become software standards. Our objective, as always, was to encourage open source. Take a look at that website. Attorneys for major software companies participated here. Those agreements were adapted for use in W3C Community Groups.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>So I believe I understand the distinction between an "industry software standard" and a mere "specification for software." <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>For elections I want open specifications (under CC licenses is fine, although I prefer the Open Web Foundation agreements because they include patent claims); I want open source software under the GPLv3 and other FOSS licenses; and to the extent you can get companies and government agencies to agree, I want open standards.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Given that VIP is just a specification, and there is no accompanying software yet, why a new OSET license?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> David suspects "that a lot of this code could show up repurposed in the OSET repository - but with an OSET license attribution put on it instead... the same people are involved in both OSET and the VIP code base…” <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Given that the specification is under a CC license, why don't we just copy it and put it into our CAVO repository? Create a derivative work? Create FOSS software under licenses of our choice? I repeat: Who needs a new license? Who needs their additional permission to do this?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>/Larry<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-----Original Message-----<br>From: Klaus-Dieter Naujok [mailto:klaus@illumonus.com] <br>Sent: Monday, September 14, 2015 2:08 PM<br>To: CAVO <cavo@opensource.org><br>Subject: Re: [CAVO] [License-review] OSET Foundation (See Our Draft Statement From Last Night + "?")<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Larry, before answering your specific question, let me clarify where I am coming from regarding Standards and Specifications.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Standards are typically developed according to a specified set of rules and procedures providing consensus amongst many parties, such as national Standards bodies (ANSI, DIN, BSI, ..), and is published by a neutral party, such as ISO, IEC and ITU. While standards have different purposes, they are mostly used as a reference for design or product criteria.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>A specification is typically a company or organization specific document which sets parameters for an item. An example of a specification would be geometric, electrical and other parameters for a specific device a specific manufacturer makes. However, a company (or other entity such as a government) may develop a specification for something such as a device or part which will be purchased. Thus, a specification may be developed for many companies as a requirement by one company (or a few companies) which is applicable to a device or part produced by any company accepting a contract.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> On Sep 14, 2015, at 12:51 PM, Lawrence Rosen <<a href="mailto:lrosen@rosenlaw.com"><span style='color:black;text-decoration:none'>lrosen@rosenlaw.com</span></a>> wrote:<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Klaus, I'm now really confused.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Don't be.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> If VIP isn't a specification for a standard, then is it merely source code for a potential GPLv3 program?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>As stated on GitHub <<a href="https://github.com/votinginfoproject/vip-specification"><span style='color:black;text-decoration:none'>https://github.com/votinginfoproject/vip-specification</span></a>>:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>"Voting Information Project XML Specification - This XML specification defines the relationships among a number of election related elements." <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The owners of this work themselves called it a specification and that is why I made my comment about calling it a Standard.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>As to your question "if VIP isn't a specification for a standard, then is it merely source code for a potential GPLv3 program?” <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Your conclusion is correct, it is a set/collection of code, data, table layouts, scripts, etc., that could be use to create, or be part of, an open source application.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> In what way is it special to OSET?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I don't know, especially as stated by Heather, that "the Foundation is currently in discussions with 11 states on adoption and deployment of its largest code distribution -- the Voter Services Portal -- which includes online voter registration and several other capabilities ready for back-end integration with legacy systems.”<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>David suspects "that a lot of this code could show up repurposed in the OSET repository - but with an OSET license attribution put on it instead... the same people are involved in both OSET and the VIP code base…” <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>If that is the case it would further suggest that the OSET goal by OSET is that any voting applications based/using this code etc, also is being released under the OSET license. If not, why even create their own FOSS license in the first place?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Regards,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Klaus<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>--<o:p></o:p></p><p class=MsoPlainText>Klaus-Dieter Naujok, Chief Executive Officer<o:p></o:p></p><p class=MsoPlainText>Illumonus, LLC - Simplifying eBusiness<o:p></o:p></p><p class=MsoPlainText>Privacy is a Right - not a Privilege!<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p></div></body></html>