Folks,
Attached below is the announcement of the most recent IETF RFC from the
Dublin Core community. This document is the end product of the substantial
efforts of John Kunze, who developed its antecedent, an Internet Draft,
managed the revision of the draft, and its evolution into the present
document.
The Dublin Core community is indebted to John for his substantial efforts in
bringing this important document fruition, and to the many others who
contributed to the evolution of this important convention for expressing
metadata in HTML.
Congratulations and thanks for a job well done, John.
stu
From: RFC Editor <[log in to unmask]>
Date: Tue, 7 Dec 1999 08:44:41 -0800 (PST)
A new Request for Comments is now available in online RFC libraries.
RFC 2731
Title: Encoding Dublin Core Metadata in HTML
Author(s): J. Kunze
Status: Informational
Date: December 1999
Mailbox: [log in to unmask]
Pages: 23
Characters: 42450
Updates/Obsoletes/See Also: None
I-D Tag: draft-kunze-dchtml-02.txt
URL: ftp://ftp.isi.edu/in-notes/rfc2731.txt
The Dublin Core [DC1] is a small set of metadata elements for
describing information resources. This document explains how these
elements are expressed using the META and LINK tags of HTML [HTML4.0].
A sequence of metadata elements embedded in an HTML file is taken to
be a description of that file. Examples illustrate conventions
allowing interoperation with current software that indexes, displays,
and manipulates metadata, such as [SWISH-E], [freeWAIS-sf2.0],
[GLIMPSE], [HARVEST], [ISEARCH], etc., and the Perl [PERL] scripts in
the appendix.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [log in to unmask] Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [log in to unmask]
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [log in to unmask] with the message body
help: ways_to_get_rfcs. For example:
To: [log in to unmask]
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [log in to unmask] Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
[log in to unmask] Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|