Hi Mechtilde, >> Personally, I think a specification should (also) allow people - without >> the deepest technical knowledge in the matter - to document the end user >> functionality. That is, an average-knowledged database user should be >> able to understand the product from the specification, and grasp enough >> ideas to even document it for others (or help others, that is). > > That is the difference between theory and practice ;-)
and between different different theories :) Well, I can understand other point of views here, too. In fact we have a number of different consumers of specifications (at least somebody who needs to write end-user documentation from it, and somebody who needs to implement it), and perhaps it really is not feasible to (try to) address all those with a single document. Which then would mean we have a gap between the specification writer and the end user, which needs to be filled by somebody. Normally this is the author of the online help. As much as I appreciate what those people are doing (Really, Uwe!), this is a pretty difficult task which perhaps cannot (always) be accomplished by somebody who itself does not have the "deepest technical knowledge in the matter", as I called it (no offense to anybody, in particular not to Uwe :). Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
