So, what do you think of the distinction between normative and informative documents? Could a standard which is not a specification (using your terminology) still be normative?
--- "A. Forrey" <[EMAIL PROTECTED]> wrote: > Consider the idea of a "Standard Practice for Use of M in the System > Life > Cycle" to coin a title for a relevant M standard. Such a documnet if > drafted and approved by the MDC could refer to all other information > systems standards and how they might applying in the various > Processes and > Activities of diffferent MUMPS systems projects. It would not be > a Specification, which is the conclusion many jump to when you speak > "standard". === Gregory Woodhouse <[EMAIL PROTECTED]> "Design quality doesn't ensure success, but design failure can ensure failure." --Kent Beck ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
