Re: Re WIT
miked@CERF.NET (Michael A. Dolan)
Errors-To: listmaster@www0.cern.ch
Date: Tue, 14 Jun 1994 03:02:49 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <199406140043.RAA21543@nic.cerf.net>
Errors-To: listmaster@www0.cern.ch
Reply-To: miked@CERF.NET
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: miked@CERF.NET (Michael A. Dolan)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Re WIT
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Mailer: <Windows Eudora Version 2.0.2>
X-Mailer: <Windows Eudora Version 2.0.2>
Content-Type: text/plain; charset="us-ascii"
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0
Mime-Version: 1.0
At 09:32 PM 6/13/94 +0200, Dan Hinckley wrote:
>Does anyone think it a good idea to come up with a requirements
>document/RFC?
Yes.
>Here goes .. In my voluminous spare time IF no one else is
>already working on such a project, I will volunteer to compile a list of
>requirements, so our implementation ideas can be considered in context.
Here's a few (probably not so easy) ones:
1. Offline composition - unless I missed something, it appears
that one must be connected semi-live to the various WIT forms
in order to have a meaningful session. Of course one could
cut and paste, but...
2. Some sort of heirarchical organization - this seems designed
in, but it might require some human intervention to keep it
rational.
3. An email interface - no matter how its designed there will be
those that can't/won't/don't use it for various reasons. Maybe
a script could be written to handle inbound email, HTML-ize it,
and stuff it into the right place ? This might also solve other
silly requirements such as (1) above.
------------------------------------
Michael A. Dolan - miked@cerfnet.com
TerraByte Technology (619) 445-9070