>Date: Mon, 1 May 1995 09:19:47 -0700 (PDT)
>From: Web4Lib Moderator <listchek@library.berkeley.edu>
>To: web4lib@library.berkeley.edu
>Subject: META tags of HTML 2.0, going away ? (fwd)
>Message-Id: <Pine.OSF.3.90.950501091922.8262B-100000@library.berkeley.edu>
[...]
>Date: Sun, 30 Apr 1995 13:25:08 -0400 (EDT)
>From: "Robert H. Terry" <rhterry@RBSE.Mountain.Net>
>Subject: META tags of HTML 2.0, going away ? (fwd)
>To: web4lib@library.berkeley.edu
[...]
>Is it true that the optional META tags in the Header part of HTML 2.0
>compliant documents are being dropped in HTML 3.0 ? If anyone has
>contacts with the IETF working group members proposing same, I urge them
>to encourage leaving the META tags in 3.0.
>
>Actually, when I get back in the office on Monday, I intend on locating
>some sources and forwarding this posting.
>
>For those of you whom know nothing about these Optional META tags they
>allow for things like:
>
> - Optional Fields, Attributes, Etc., whatever added info one needs
> to include in HTML source code, for things like cataloging.
>
> - These could be Keyword Fields, Abstracts, Etc., any fields one might
> include in the source code for use in documentation or classification.
>
> - BTW the Beta version of Word's Access tool uses these when one elects
> to "save as" HTML. Lycos returns search results with metadata which
> provides needed information for selecting possible resources.
>
> - Locally, our software repository wanted to create a basic item
> description model for our assets and representing it using these
> META tags.
>
> - A catalog of these headers could then be made available on the WWW
> in order to aid potential reusers of the software assets they represent.
>
>What will HTML 2.0 META tags become when 3.0 is the new standard ?
>
>I'll ask here for comment ?
>
>
>Bob Terry
>rhterry@rbse.mountain.net
>Senior Software Engineer/Librarian
>ELSA - A NASA public domain library
My reply:
>Message-Id: <199505031144.AA281291467@lulu.acns.nwu.edu>
>Subject: Re: META tags of HTML 2.0, going away ? (fwd)
>To: web4lib@library.berkeley.edu
>Date: Wed, 3 May 1995 06:44:27 -0500 (CDT)
>From: Albert-Lunde@nwu.edu (Albert Lunde)
[...]
>I am on the HTML working group mailing list, and I don't think
>anyone has discussed dropping <META>, though there was recent
>discussion (in response to a question) of other sorts of markup
>for various meta-information.
>
>The <META> tag is in the latest HTML 2.0 and 3.0 drafts I could
>find online. See: http://www.ics.uci.edu/pub/ietf/html/
>
>To other readers, it may be noted that META was introduced
>at some phase in the development of the HTML 2.0 spec
>and is supposed to allow markup to represent meta-information
>which can correspond to HTTP headers. Few HTTP servers actually
>support returning this meta-information today, but I think
>some indexing tools use <META> markup.
>
>An example from the HTML 3.0 spec:
>
>= =
>If the document contains:
>
><META HTTP-EQUIV=Expires CONTENT="Tue, 04 Dec 1993 21:29:02 GMT">
><META HTTP-EQUIV="Keywords" CONTENT="Nanotechnology, Biochemistry">
><META HTTP-EQUIV="Reply-to" CONTENT="dsr@w3.org (Dave Raggett)">
>
>The server will include the following response headers:
>
>Expires: Tue, 04 Dec 1993 21:29:02 GMT
>Keywords: Nanotechnology, Biochemistry
>Reply-to: dsr@w3.org (Dave Raggett)
>
>= =
>See the specification for more details.
>
>For examples of software actually using META, see MOMSPIDER at:
>
>http://www.ics.uci.edu:80/WebSoft/MOMspider/
>
>and John Franks WN server at:
>
>http://hopf.math.nwu.edu/
>
>--
> Albert Lunde Albert-Lunde@nwu.edu
>
--
Albert Lunde Albert-Lunde@nwu.edu