SUO: Re: Missing Ingredient
o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o
Jim,
Some thoughts:
The missing ingredient in all of the current starter documents,
as would be obvious to any expert that you might consult from
any field of expertise beyond the hothouse flowers of AI/KR,
is any measure of respect for what is already considered to
be absolutely standard undergraduate textbook knowledge in
any of the affected fields, much less any appreciation of
the methods of inquiry that are necessary to continue
acquiring and updating that knowledge.
Unless and until these defects begin to be seriously addressed
by this working group, the SUO starter documents will continue
to be a joke, if not utterly retched brew, to any responsible
professional from any discipline who tries to review them.
To put it mildly,
Jon Awbrey
o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o
jim.s3@juno.com wrote:
>
> SUO,
>
> There are many ingredients needed to brew a successful standard.
> We have a few ingredients, including some starter documents, a diverse
> group of experts, a charter from an accredited Standards Developing
> Organization (SDO), and a forum to conduct work.
>
> I see the key missing ingredient as: 'A growing number of
> organizations attempting to reuse any of the starter documents, and
> willing to submit suggested changes.'
>
> If we had this ingredient,
>
> 1. The suggested changes would help us improve the documents, and
> also build consensus, assuming these individuals joined the SUO WG.
>
> 2. The improvements would matter to at least one organization
> that is actually building something that needs the improvement. This is
> important, because the quantity of these improvements is hopefully
> feasible to handle, whereas, the quantity of 'improvements for the sake
> of improvement' is infinite and would prevent completion and balloting of
> a document.
>
> 3. As the number of users grows, the document moves closer to a
> market-accepted de facto standard. IEEE approval will not be enough.
> Some level of market adoption must be achieved.
>
> So, how do get organizations to attempt to reuse any of our
> documents? Or, if they are doing so, how do we get them to
> submit their suggested changes?
>
> Any thoughts?
>
> Jim Schoening
o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o