Re: The future of meta-indices/libraries?
Dave_Raggett <dsr@hplb.hpl.hp.com>
Errors-To: listmaster@www0.cern.ch
Date: Wed, 16 Mar 1994 10:56:11 --100
Message-id: <9403160951.AA10386@dragget.hpl.hp.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: dsr@hplb.hpl.hp.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Dave_Raggett <dsr@hplb.hpl.hp.com>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: The future of meta-indices/libraries?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 1296
Christian Neuss writes:
> The title comes to mind.. but something with a bit more meaning
> would be better. Well, how about using the group statement to mark
> up special semantics of HTML text? You could have
> <GROUP role="keywords">
> <H2> Keywords: </H2>
> compression, encryption
> </GROUP>
> in the header, or at multiple positions in the text:
Before you start inventing new elements, consider the HTML+ META
element. This was added as a general solution to adding meta
information to HTML documents. This scheme allows wobots to scan
this information efficiently using the HTTP HEAD method.
<!--
Servers should read the document head to generate HTTP headers
corresponding to META elements, e.g. if the document contains:
<meta name="Expires" value="Tue, 04 Dec 1993 21:29:02 GMT">
The server should include the HTTP date format header field:
Expires: Tue, 04 Dec 1993 21:29:02 GMT
Other likely names are "Keywords", "Created", "Owner" (a name)
and "Reply-To" (an email address)
-->
<!ELEMENT META - O EMPTY>
<!ATTLIST META
id ID #IMPLIED -- to allow meta info --
name CDATA #IMPLIED -- HTTP header e.g. "Expires" --
value CDATA #IMPLIED -- associated value -->