<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=Windows-1252">
<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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML pr\00E9-formatado Car\00E1cter";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLpr-formatadoCarcter
{mso-style-name:"HTML pr\00E9-formatado Car\00E1cter";
mso-style-priority:99;
mso-style-link:"HTML pr\00E9-formatado";
font-family:"Consolas","serif";
color:black;}
span.EstiloCorreioElectrnico19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
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 bgcolor="white" lang="PT" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Cameron, just to say that for the first time I’m seing good strong arguments that make a clear case, that’s easy to understand and with very low
emotional content…<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks for your tireless work on this.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Duarte
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" 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 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">De:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> Cameron Shorter [mailto:cameron.shorter@gmail.com]
<br>
<b>Enviada:</b> quarta-feira, 22 de Maio de 2013 03:26<br>
<b>Para:</b> standards@lists.osgeo.org; OSGeo Discussions<br>
<b>Assunto:</b> [OSGeo-Discuss] Will OGC’s standards meet government purchasing guidelines?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In what has become the OGC’s most contentious vote to date, OGC members are being asked whether the proposed "Geoservices REST API" should be accepted as an OGC standard. A summary of concerns are listed in an Open Letter from the Open
Source Geospatial Foundation (OSGeo) to the OGC. However, the crux of contentions hinge around the definition of an Open Standard and whether the "Geoservices REST API" qualifies as one.<br>
<br>
<b>When measured against government’s policy drivers of interoperability, fair competition, and economical use of government funds, the evidence is overwhelming. "Geoservices REST API" fails on all accounts.
</b>In fact, we should be questioning why our OGC processes haven’t identified and then addressed these issues much earlier. ....<br>
<br>
The justification is in blog format (as hyperlinks to references don't copy well to some email clients):<br>
<br>
<a href="http://lisasoft.com/blog/will-ogc%E2%80%99s-standards-meet-government-purchasing-guidelines">http://lisasoft.com/blog/will-ogc%E2%80%99s-standards-meet-government-purchasing-guidelines</a><br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Cameron Shorter<o:p></o:p></pre>
<pre>Geospatial Solutions Manager<o:p></o:p></pre>
<pre>Tel: +61 (0)2 8570 5050<o:p></o:p></pre>
<pre>Mob: +61 (0)419 142 254<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Think Globally, Fix Locally<o:p></o:p></pre>
<pre>Geospatial Solutions enhanced with Open Standards and Open Source<o:p></o:p></pre>
<pre><a href="http://www.lisasoft.com">http://www.lisasoft.com</a><o:p></o:p></pre>
</div>
</body>
</html>