Comment on -01.1 document structure
Edgar Schwarz (Edgar.Schwarz@de.bosch.com)
Wed, 19 May 1999 11:18:22 +0200 (MESZ)
Date: Wed, 19 May 1999 11:18:22 +0200 (MESZ)
From: Edgar Schwarz <Edgar.Schwarz@de.bosch.com>
To: ietf-dav-versioning@w3.org
In-Reply-To: <9905190837.AA04447@tantalum>
Message-ID: <Pine.GHP.4.05.9905191058300.1092-100000@hpmx15.bk.bosch.de>
Subject: Comment on -01.1 document structure
On Wed, 19 May 1999, Geoffrey M. Clemm wrote:
> I agree with everything Jim says here, and will update the draft with
> the new working for MKRESOURCE that he proposes. As Jim points out, the
> 01.1 draft is primarily for getting agreement on the technical direction,
> but the 02 draft will need all these details nailed down, so the
> earlier the better!
I don't know whether there is some meta standard how a standard document
should be structured.
But nevertheless, when I read the draft I saw some definitions of terms
(data structures, objects) at the beginning. Followed by methods working
on these objects. This is a functional decomposition. Wouldn't it be clearer
to give the objects together with the methods it allows ?
This would make it easier to compare e.g. the subtle differences between
configuration and baseline.
In my experience OO isn't all hype (but also no silver bullet) so I would
try to start it already at this stage. Also there are e.g. OSI standards
which are also (sort of) OO.
Just a thought :-)
I want to close with an old citation by Frederic Brooks from "The Mythical
Man-Month", even it is a bit dated:
"Show me your flowcharts and conceal your tables, and I shall continue to
be mystified. Show me your tables, and I won't usually need your
flowcharts; they will be obvious."
Cheers, Edgar
--
Edgar.Schwarz@de.bosch.com ON/EMS1, 07191/13-3382 Niklaus Wirth:
Privat kann jeder soviel C programmieren oder Videos ansehen wie er mag.
Albert Einstein: Mach es so einfach wie moeglich, aber nicht einfacher.