Re: <inc> in ncsa server

kevin@scic.intel.com (Kevin Altis)
X-Delivered: at request of secret on dxcern.cern.ch
Message-id: <9310081632.AA13025@rs042.scic.intel.com>
X-Sender: kevin@rs042.scic.intel.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 8 Oct 1993 09:29:07 -0800
To: robm@ncsa.uiuc.edu (Rob McCool), Charles Henrich <henrich@crh.cl.msu.edu>,
        www-talk@nxoc01.cern.ch
From: kevin@scic.intel.com (Kevin Altis)
Subject: Re: <inc> in ncsa server
>Exactly. While it doesn't really matter if it's #inc or <inc>, the point is
>that it is not HTML anymore and documents which are plain HTML should not
>have the processing done on them. Also, people should not be encouraged to
>think that <inc> is part of HTML (at least, not the way it is right now,
>since I don't believe there are any <inc> directives for clients).
>
>--Rob

I agree that the current syntax <INC...> etc. is confusing since it isn't
HTML. If it can't be HTML, I have no problem with the concept of
preprocessing and use of #inc or maybe it should be <--pre inc...--> so
that an SGML parser will treat it as a comment. I don't want to see the
power of <INC> disappear though. So now can we have <--pre if then else
...--> ;-)

ka