Re: <ISINDEX> obsolete?

Tony Sanders <sanders@BSDI.COM>

Mail folder: WWW Talk Apr 94-present
Next message: Ehud Shapiro: "Re: Proposal: WIT over USENET or Mail"
Previous message: Christopher Allen: "FWD: PRESS RELEASE: RSA and EIT Joint Venture"

Errors-To: listmaster@www0.cern.ch
Date: Wed, 15 Jun 1994 04:41:48 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <199406141633.LAA19336@austin.BSDI.COM>
Errors-To: listmaster@www0.cern.ch
Reply-To: sanders@BSDI.COM
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Tony Sanders <sanders@BSDI.COM>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: <ISINDEX> obsolete? 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Organization: Berkeley Software Design, Inc.
Organization: Berkeley Software Design, Inc.

neuss@igd.fhg.de writes:
> belong into HTTP, but it's simply is not a _document_ property. A file is a
> file is a file, whether or not it is inside some index is nothing the author
> should need to consider when writing the file - right? Should we have such
> an element?
You mean like
    Public: TEXTSEARCH

Yes, that's what it's for (just like ``Public: SPACEJUMP'' is to ISMAP).

And I'll again argue that this is the wrong header to put this information.
It should be a seperate header from Public.

Of course, no browsers currently accept this anyway (that I know of).

--sanders