As per Relevance of the word resource, we have this rfc below:
Network Working Group S.
Request for Comments: 2413 OCLC Online Computer Library Center, Inc
Category: Informational J.
University of California, San
C.
Cornell
M.
Reuters
September 1998
Dublin Core Metadata for Resource
1. Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
2.
The Dublin Core Metadata Workshop Series began in 1995 with
invitational workshop which brought together librarians,
library researchers, content experts, and text-markup experts
promote better discovery standards for electronic resources.
Dublin Core is a 15-element set of descriptors that has emerged
this effort in interdisciplinary and international
building. This is the first of a set of Informational
describing the Dublin Core. Its purpose is to introduce the
Core and to describe the consensus reached on the semantics of
of the 15 elements
3.
Finding relevant information on the World Wide Web has
increasingly problematic due to the explosive growth of
resources. Current Web indexing evolved rapidly to fill the
for resource discovery tools, but that indexing, while useful, is
poor substitute for richer varieties of resource description
An invitational workshop held in March of 1995 brought
librarians, digital library researchers, and text-markup
to address the problem of resource discovery for networked resources
Weibel, et. al. Informational [Page 1]
RFC 2413 Dublin Core Metadata for Resource Discovery September 1998
This activity evolved into a series of related workshops
ancillary activities that have become known collectively as
Dublin Core Metadata Workshop Series
The goals that motivate the Dublin Core effort are
- Simplicity of creation and
- Commonly understood
- Conformance to existing and emerging
- International scope and
-
- Interoperability among collections and indexing
These requirements work at cross purposes to some degree, but all
desirable goals. Much of the effort of the Workshop Series has
directed at minimizing the tensions among these goals
One of the primary deliverables of this effort is a set of
that are judged by the collective participants of these workshops
be the core elements for cross-disciplinary resource discovery.
term "Dublin Core" applies to this core of descriptive elements
Early experience with Dublin Core deployment has made clear the
to support qualification of elements for some applications. Thus,
Dublin Core element may be expressed without qualification (
described in this RFC) or with qualifiers that refine its
(the subject of future RFCs). For the sake of interoperability
simple indexing and discovery tools should be able to ignore
qualifiers provided, while more advanced, semantically richer
should be able to use qualifiers to support more specialized
precise discovery
The broad agreements about syntax and semantics that have
from the workshop series will be expressed in a series
Informational RFCs, of which this document is the first
4. Description of Dublin Core
The following is the reference definition of the Dublin Core
Element Set. Further information about the Dublin Core
Element Set is available at [1]:
http://purl.org/metadata/dublin_
In the element descriptions below, each element has a
name intended to convey a common semantic understanding of
element, as well as a formal single-word label intended to make
syntactic specification of elements simpler for encoding schemes
Weibel, et. al. Informational [Page 2]
RFC 2413 Dublin Core Metadata for Resource Discovery September 1998
Although some environments, such as HTML, are not case-sensitive,
is recommended best practice always to adhere to the case
in the element labels given below to avoid conflicts in the
that the metadata is subsequently extracted or converted to a case
sensitive environment, such as XML (Extensible Markup Language) [2].
Each element is optional and repeatable. Metadata elements
appear in any order. The ordering of multiple occurrences of
same element (e.g., Creator) may have a significance intended by
provider, but ordering is not guaranteed to be preserved in
system
To promote global interoperability, a number of the
descriptions suggest a controlled vocabulary for the
element values. It is assumed that other controlled
will be developed for interoperability within certain local domains
The metadata elements fall into three groups which roughly
the class or scope of information stored in them: (1)
related mainly to the Content of the resource, (2) elements
mainly to the resource when viewed as Intellectual Property, and (3)
elements related mainly to the Instantiation of the resource
Content Intellectual Property
----------- --------------------- -------------
Title Creator
Subject Publisher
Description Contributor
Type Rights
4.1. Title Label: "Title
The name given to the resource, usually by the Creator or Publisher
4.2. Author or Creator Label: "Creator
The person or organization primarily responsible for creating
intellectual content of the resource. For example, authors in
case of written documents, artists, photographers, or illustrators
the case of visual resources
Weibel, et. al. Informational [Page 3]
RFC 2413 Dublin Core Metadata for Resource Discovery September 1998
4.3. Subject and Keywords Label: "Subject
The topic of the resource. Typically, subject will be expressed
keywords or phrases that describe the subject or content of
resource. The use of controlled vocabularies and
classification schemes is encouraged
4.4. Description Label: "Description
A textual description of the content of the resource,
abstracts in the case of document-like objects or
descriptions in the case of visual resources
4.5. Publisher Label: "Publisher
The entity responsible for making the resource available in
present form, such as a publishing house, a university department,
a corporate entity
4.6. Other Contributor Label: "Contributor
A person or organization not specified in a Creator element who
made significant intellectual contributions to the resource but
contribution is secondary to any person or organization specified
a Creator element (for example, editor, transcriber,
illustrator).
4.7. Date Label: "Date
A date associated with the creation or availability of the resource
Recommended best practice is defined in a profile of ISO 8601 [3]
that includes (among others) dates of the forms YYYY and YYYY-MM-DD
In this scheme, for example, the date 1994-11-05 corresponds
November 5, 1994.
4.8. Resource Type Label: "Type
The category of the resource, such as home page, novel, poem,
paper, technical report, essay, dictionary. For the sake
interoperability, Type should be selected from an enumerated
that is currently under development in the workshop series
4.9. Format Label: "Format
The data format and, optionally, dimensions (e.g., size, duration)
the resource. The format is used to identify the software
possibly hardware that might be needed to display or operate
Weibel, et. al. Informational [Page 4]
RFC 2413 Dublin Core Metadata for Resource Discovery September 1998
resource. For the sake of interoperability, the format should
selected from an enumerated list that is currently under
in the workshop series
4.10. Resource Identifier Label: "Identifier
A string or number used to uniquely identify the resource.
for networked resources include URLs and URNs (when implemented).
Other globally-unique identifiers, such as International
Book Numbers (ISBN) or other formal names are also candidates
this element
4.11. Source Label: "Source
Information about a second resource from which the present
is derived. While it is generally recommended that elements
information about the present resource only, this element may
metadata for the second resource when it is considered important
discovery of the present resource
4.12. Language Label: "Language
The language of the intellectual content of the resource
Recommended best practice is defined in RFC 1766 [4].
4.13. Relation Label: "Relation
An identifier of a second resource and its relationship to
present resource. This element is used to express linkages
related resources. For the sake of interoperability,
should be selected from an enumerated list that is currently
development in the workshop series
4.14. Coverage Label: "Coverage
The spatial or temporal characteristics of the intellectual
of the resource. Spatial coverage refers to a physical region (e.g.,
celestial sector) using place names or coordinates (e.g.,
and latitude). Temporal coverage refers to what the resource
about rather than when it was created or made available (the
belonging in the Date element). Temporal coverage is
specified using named time periods (e.g., neolithic) or the
date/time format [3] as recommended for the Date element
Weibel, et. al. Informational [Page 5]
RFC 2413 Dublin Core Metadata for Resource Discovery September 1998
4.15. Rights Management Label: "Rights
A rights management statement, an identifier that links to a
management statement, or an identifier that links to a
providing information about rights management for the resource
5. Security
The Dublin Core element set poses no risk to computers and networks
It poses minimal risk to searchers who obtain incorrect or
information due to careless mapping from rich data descriptions
the simple Dublin Core scheme. No other security concerns are
to be raised by the element description consensus documented here
6.
[1] Further information about the Dublin Core Metadata Element Set
http://purl.org/metadata/dublin_
[2] Extensible Markup Language (XML), http://www.w3.org/TR/REC-
[3] Date and Time Formats (based on ISO 8601), W3C Technical Note
http://www.w3.org/TR/NOTE-
[4] Alvestrand, H., "Tags for the Identification of Languages",
1766, March 1995.
7. Authors'
Stuart L.
OCLC Online Computer Library Center, Inc
Office of
6565 Frantz Rd
Dublin, Ohio, 43017,
Phone: +1 614-764-6081
Fax: +1 614-764-2344
EMail: weibel@oclc.
Weibel, et. al. Informational [Page 6]
RFC 2413 Dublin Core Metadata for Resource Discovery September 1998
John A.
Center for Knowledge
University of California, San
530 Parnassus Ave, Box 0840
San Francisco, CA 94143-0840,
Phone: +1 510-525-8575
Fax: +1 415-476-4653
EMail: jak@ckm.ucsf.
Carl
University Library and Department of Computer
Cornell
Ithaca, NY 14853,
Phone: +1 607-255-6046
Fax: +1 607-255-4428
EMail: lagoze@cs.cornell.
Misha
Reuters
85 Fleet
London EC4P 4AJ,
Phone: +44 171-542-6722
Fax: +44 171-542-8314
EMail: misha.wolf@reuters.
Weibel, et. al. Informational [Page 7]
RFC 2413 Dublin Core Metadata for Resource Discovery September 1998
8. Full Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Weibel, et. al. Informational [Page 8]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
