As much as I would like any future standardization process to be open, I think we are stuck with ANSI (at least for the base!) since the community has no real way to recreate the existing standard outside ANSI. Further, having a standard blessed by a recognized standards body is important to the vendors -- "gravitas", visibility, and marketing -- but not critical (in my mind). The really important thing about the standard is that it provides a definition of how some subset(s) of Smalltalk works that is agreed to (and implemented) by all vendors. This can be done with or without a standards body blessing the definition.
<div> </div>
<div>So what are the important things to do w.r.t. standardization:</div>
<ol>
<li>Encourage community participation in the standards activity</li>
<li>Make the resulting standard(s) available to a wide audience</li>
<li>Produce an "errata" to the existing standard to correct the errors that exist in it and clarify areas where it is confusing/inexact</li>
<li>Extend the standard into new areas where agreement can be reached</li></ol>
<div>These goals can be addressed outside ANSI (and, in fact, #1 and #2 can be done better outside ANSI). If we (the community or some subset) decide at the end of the activity that we really want it to be an ANSI standard, then we could go through the costly bureaucratic process of converting the "open" document(s) into ANSI-blessed documents.</div>
<div> </div>
<div>I guess another of my concerns with being tied to ANSI is that we may invest a lot of time and $$ in dealing with ANSI and end up with nothing as a result if the participants lose interest somewhere in the midst of the effort. With an open process, whatever work is done will be available even if no actual standard ever appears.</div>
<div> </div>
<div></div>
<div></div>
<div class="gmail_quote">On Jan 31, 2008 8:50 AM, Bruce Badger <<a href="mailto:bwbadger@gmail.com">bwbadger@gmail.com</a>> wrote:
<div></div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I would be particularly interested to hear the views of the Smalltalk
<div>vendor companies about how they feel about ANSI/INCITS, open process</div>
<div>and all that.</div>
<div></div>
<div>I wonder if the gravitas that would come with working with ANSI (or</div>
<div>perhaps another standards body) is important to them, and if they</div>
<div>think it may be important to their customers or potential customers.</div>
<div></div>
<div>Thanks :-)</div>
<div><font color="#888888"></font></div><font color="#888888">
<div>--</div>
<div>Make the most of your skills - with OpenSkills</div>
<div><a href="http://www.openskills.org/" target="_blank">http://www.openskills.org/</a></div>
<div></div>
<div>_______________________________________________</div>
<div>ANSI-Smalltalk mailing list</div>
<div><a href="mailto:ANSI-Smalltalk@lists.openskills.org">ANSI-Smalltalk@lists.openskills.org</a></div>
<div><a href="http://lists.openskills.org/cgi-bin/mailman/listinfo/ansi-smalltalk" target="_blank">http://lists.openskills.org/cgi-bin/mailman/listinfo/ansi-smalltalk</a></div>
<div></div></font></blockquote></div>
<div></div>
<div clear="all"></div>
<div>-- </div>
<div>John O'Keefe [|], Principal Smalltalk Developer, Instantiations Inc. </div>