Advice on Organization

[Philip J. Nesser II]

I believe that is exactly what will happen.  Try and remember that the
orignal draft is only a few weeks old.  The standards bodies that you refer
to tpyically take months (or years) between revisions.  I don't think a few
weeks between is that bad, especially between the first and second cuts
where there are a lot of changes.  If there are subsequent revs, I expect
they will take shorter periods since more of the material will stay the
same.

--->  Phil



Bob Van Cleef supposedly said:
>
> Kim;
>
> > Then it became clear that there were many that didn't understand
> > other parts of the proposal, so we thought it was wise to take the
> > time to clarify the entire draft.
>
> May I make a suggestion that is radical?
>
> Make the current draft, and each subsequent revision "public."   Include the rationale
> for each change as part of the draft until the final release.  I know that many "flames"
> will result based on incomplete phrasing - but wouldn't it be more profitable to have the
> flames focused on the document itself, instead of other people?
>
> You will never get the wording to the point that everyone will "understand it."  However,
> you can point to the reasons for the changes, as recorded in the "rationale" sections,
> so that others can then suggest different ways of phrasing to achieve the end goal,
> a finished document.
>
> Standards organizations have used this methodolgy for years with positive results.
> Holding the document "until it is ready" only means that it will never get released
> for review...
>
> Bob
> ><>  ><>  ><>  ><>  ><>  ><>  ><>  ><>  ><>  ><>  ><>  ><>  ><>  ><>  ><>
> Bob Van Cleef, Systems Administration                      (408) 734-8100
> MicroUnity Systems Engineering, Inc.                   FAX (408) 734-8177
> 255 Caspian Drive, Sunnyvale, CA 94089-1015       vancleef at microunity.com
>