Hi Mechtilde, >> Hi Marc, >> >>> The RD has been a project on it's own long before it was adapted to >>> OO.o, as could be read in some announcements. So there must be a website >>> somewhere and on this website there must be documentation. A project of >>> this size will never evolve without any docs. >> How idealistic ... >> >> http://dba.openoffice.org/specifications/index.html, document "Report >> Designer" is everything about the SRD from our side. > > I read the specifications sevaral times. For my opinion it is very > difficult to understand how it should work especially you don't know how > it could work. > > The spcifications are technical documents but no documents where the > user can read how to use it.
Agreed, and I'm not happy with that. To me, it seems our beloved specification process doesn't have a clear (in the sense of: everybody committed to it) idea of who the stakeholder for (aka *reader* of) a specification is. 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). 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]
