<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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Comic Sans MS";
color:windowtext;
font-weight:normal;
font-style:normal;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">Norman,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">We’re thoroughly entrenched with a OpenSource installation right along side a bunch of commercial products. It’s been very hard for any commercial vendor to even get a leg up in
our office for a number of years now because we’ve got so much stuff already working via OpenSource (and also available to the commercial products.) However, we still don’t have a top level position to over see these things, and there is still splintering
of resources that is taking place.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">Bobb<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<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""> discuss-bounces@lists.osgeo.org [mailto:discuss-bounces@lists.osgeo.org]
<b>On Behalf Of </b>Norman Vine<br>
<b>Sent:</b> Wednesday, October 16, 2013 10:57 AM<br>
<b>To:</b> osgeo-discuss (discuss@lists.osgeo.org)<br>
<b>Subject:</b> Re: [OSGeo-Discuss] Defining a GIO position (or attmepting to . . .)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">disc<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">On Oct 16, 2013, at 11:34 AM, "Basques, Bob (CI-StPaul)" <<a href="mailto:bob.basques@ci.stpaul.mn.us">bob.basques@ci.stpaul.mn.us</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Arnie,<br>
<br>
Vendor lock-in, or rather preventing it, would be a strong second as far as reasons go, but it's not really applicable to describing a positions work items (I don't think) and seems like it might be closer to a policy issue (in my mind).<br>
<br>
Thanks for the feedback.<br>
<br>
Bobb<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Bobb<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I would argue that one needs an OpenSource Reference implementation to <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">vet adherence to any OpenStandard<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In fact I would go even further and say that any new OpenStandard proposal<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">should be accompanied by an OpenSource implementation before acceptance<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">as such<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Norman<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">-----Original Message-----<br>
From: Arnie Shore [mailto:shoreas@<a href="http://gmail.com">gmail.com</a>]<br>
Sent: Wednesday, October 16, 2013 10:04 AM<br>
To: Basques, Bob (CI-StPaul)<br>
Cc: osgeo-discuss (<a href="mailto:discuss@lists.osgeo.org">discuss@lists.osgeo.org</a>)<br>
Subject: Re: [OSGeo-Discuss] Defining a GIO position (or<br>
attmepting to . . .)<br>
<br>
Well, adherence to standards is integral to the issue of<br>
interoperability, a critical project success factor in this<br>
increasingly interconnected world.<br>
<br>
And, there's no motivation for vendor lock-in, since the revenue<br>
protection motivation (usually!) doesn't exist. (I can tell you<br>
re all of the verbiage I've excreted in a prior life justifying<br>
sole-source procurements.)<br>
<br>
Also, possibly important for the devout among us is that the Good<br>
Lord must love standards; She made so many of them!<br>
<br>
AS<br>
<br>
On 10/16/13, Basques, Bob (CI-StPaul)<br>
<<a href="mailto:bob.basques@ci.stpaul.mn.us">bob.basques@ci.stpaul.mn.us</a>> wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">Hi all,<br>
<br>
I wonder if I could get some feedback on the following<o:p></o:p></p>
<p class="MsoNormal">statement, I'm<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">looking for the other side of the argument (I know it's hard to<o:p></o:p></p>
<p class="MsoNormal">put<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">yourself there :c).<br>
<br>
"Open Source software enforces standards" ... <snip /><o:p></o:p></p>
<p class="MsoNormal"><br>
<br>
_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.osgeo.org">Discuss@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/discuss">http://lists.osgeo.org/mailman/listinfo/discuss</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>