<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Landon, <br>
<br>
Hmmm, interesting read.<br>
<br>
Didn't offend me at all. It actually hit on a few sweet spots of
interest of mine. One being, that just because everyone else is using
it, doesn't mean it's the right thing to use.<br>
<br>
One thing I will rant at you about though, is you didn't really get to
the heart of providing a solution. I think a good measure of the
problem is that there is a Chicken and Egg scenario to deal with, where
you can't build a (good) standard until you have users of the standard,
and you can't have users until there's a standard to use. Seems like
things need to go back and forth a while between the "user" and "build"
cycles before something (really) good comes of it.<br>
<br>
I'm not sure what to do about the monetary aspects of the Standards
participation. But in the end, they are only successfully implemented
if the developer community implements them.<br>
<br>
I've built my fair share of what I would like to think were good
standards that I thought someone else might benefit from, but I've not
had the time nor resources to promote my ideas and settled with
implementing them within my sphere of influence instead. The OGC
standards that I've used have all provided a measure of improvement to
my systems, they have also increased my user base as well as sources of
data considerably of late. They are however not perfect in many
respects, some on the technical side, as well as some probably being to
subtle to affect the masses.<br>
<br>
I'm in complete alignment with your thinking though related to bad (or
poorly thought out) standards having a stifling affect on innovation.
There have been many times in the recent past where I've wanted to try
some things new and different, only to discover that the standards were
holding me at bay on one point or another.<br>
<br>
It seems like we're at a point where we should try to identify the
shortcomings and run through a "user" and "build" cycle and see what
comes of it. Doesn't need to necessarily be under the direction of the
OGC either. <br>
<br>
All it takes is enough users. <br>
<br>
Bob Basques<br>
<br>
<br>
<br>
Landon Blake wrote:
<blockquote
cite="mid:0D544207876CDA428F17DD7EA448C192873337@bailey.DOMAIN.KSNINC.PVT"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Arial Narrow";
panose-1:2 11 5 6 2 2 2 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Arial Narrow";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Arial Narrow";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--ppd1000033-->
<div class="Section1">
<p class="MsoNormal"><font face="Arial" size="2"><span
style="font-size: 9.5pt; font-family: Arial;">I’m sending this to
GeoWanking and OSGeo discuss, so I
apologize in advance if your inbox gets hit with it twice. :]<o:p></o:p></span></font></p>
<p class="MsoNormal"><font face="Arial" size="2"><span
style="font-size: 9.5pt; font-family: Arial;"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font face="Arial" size="2"><span
style="font-size: 9.5pt; font-family: Arial;">I've written a blog post
on the OpenJUMP blog about some of
the<br>
problems with software standards.<br>
<br>
I imagine this post will make some people upset, but I think it raises<br>
some valid points. I don't think that everyone involved in open source<br>
GIS will agree with me, but I think I identify some problems with the<br>
love of standards that our of particular interest to our community.<br>
(In a way that isn't of interest to those that develop closed-source<br>
GIS programs.)<br>
<br>
At any rate, the post is a long one, so if you do read it give<br>
yourself 5 or 10 minutes. Before you flame me remember that I'm just a<br>
surveyor that has seen too much sun, and that my opinion doesn't count<br>
for a whole lot in the big scheme of things. :]<br>
<br>
You can read the post here:<br>
<br>
<a moz-do-not-send="true" href="http://openjump.blogspot.com/"
target="_blank">http://openjump.blogspot.com/</a><br>
<br>
The Sunburned Surveyor<o:p></o:p></span></font></p>
<p class="MsoNormal"><font face="Arial Narrow" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font face="Arial Narrow" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font face="Arial Narrow" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
</div>
<br>
<br>
<font face="Arial"><font size="1"><strong>Warning:<br>
</strong>Information provided via electronic media is not guaranteed
against defects including translation and transmission errors. If the
reader is not the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is
strictly prohibited. If you have received this information in error,
please notify the sender immediately.</font></font>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Discuss@lists.osgeo.org">Discuss@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/discuss">http://lists.osgeo.org/mailman/listinfo/discuss</a>
</pre>
</blockquote>
</body>
</html>