Re: Future of meta-indices: site indexing proposal and Perl script
John C. Mallery <jcma@reagan.ai.mit.edu>
Errors-To: listmaster@www0.cern.ch
Date: Tue, 22 Mar 1994 20:29:56 --100
Message-id: <19940322192733.5.JCMA@JEFFERSON.AI.MIT.EDU>
Errors-To: listmaster@www0.cern.ch
Reply-To: jcma@reagan.ai.mit.edu
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: John C. Mallery <jcma@reagan.ai.mit.edu>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Future of meta-indices: site indexing proposal and Perl script
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 979
From: Dave Raggett <dsr@hplb.hpl.hp.com>
> Abstracts are clearly metainformation in the general sense, but they seem,
> to my taste at least, a bit heavy-duty for a HEAD request. (Do we really
> want large HEADs to be routinely larger than small documents?)
HTML+ includes the ABSTRACT element for this. The "Summary" HTTP
header should therefore be reserved for a brief description.
At some point in the future we may wish to extend HTTP
to allow clients to request named portions of the document.
Right now the #ID suffix is interpreted by the client, but there
is now reason why with a suitable HTTP method (e.g. "EXTRACT")
the server couldn't extract the contents of the named container
and send that rather than the entire document.
Dave Raggett
It would be nice if the document fragment could be specified stuff between two
arbitrary points in a document, rather than relying exclusively on everything
to be named.