Re: Identifying scripts by file extension?

• Mail folder: WWW Talk Jan 94-present
• Next message: Peter Flynn: "Re: <draft-ietf-iiir-html-01.txt, .ps> to be deleted."
• Previous message: Erik Naggum: "Re: <draft-ietf-iiir-html-01.txt, .ps> to be deleted."

Errors-To: listmaster@www0.cern.ch
Date: Tue, 15 Feb 1994 19:58:11 --100
Message-id: <9402151853.AA04421@ulua.hal.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: connolly@hal.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: "Daniel W. Connolly" <connolly@hal.com>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Identifying scripts by file extension? 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 859

In message <m0pWUPM-000436C@ibeam.intel.com>, Kevin Altis writes:
>
>Regarding HyTime compliance: When I don't have to type that junk and when
>my HTML(+) editor remembers all the syntaxes for me, then I'm all for
>HypTime compliance. Until then, HyTime can stay outside in the vaporware
>shed.
>

Thank you for your enlightening and persuasive editorial comments on
the future of building high-integrity Web documents. ;-)

Get a clue. Think ahead a little. Information is too valuable to trust
to hacked systems. We need to get this right. We don't have to build a
whole HyTime system to write HyTime compliant documents. Hacked up
tools are fine, as long as the data is compliant with a well-defined
formalism.  If we develop HyTime compliant docs now, and full-blown
HyTime systems come along, we will have all our valuable information
ready to use.

Dan