< draft-kunze-rfc2413bis-06.txt   draft-kunze-rfc2413bis-07.txt >
Internet-Draft: draft-kunze-rfc2413bis-06.txt J. Kunze Internet-Draft: draft-kunze-rfc2413bis-07.txt J. Kunze
Dublin Core Metadata University of California Dublin Core Metadata University of California
Expires 19 August 2007 T. Baker Expires 20 October 2007 T. Baker
Dublin Core Metadata Initiative Dublin Core Metadata Initiative
19 February 2007 20 April 2007
The Dublin Core Metadata Element Set The Dublin Core Metadata Element Set
(http://www.ietf.org/internet-drafts/draft-kunze-rfc2413bis-06.txt) (http://www.ietf.org/internet-drafts/draft-kunze-rfc2413bis-07.txt)
Status of this Document Status of this Document
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 2, line 8 skipping to change at page 2, line 8
The Dublin Core Metadata Workshop Series began in 1995 with an The Dublin Core Metadata Workshop Series began in 1995 with an
invitational workshop which brought together librarians, digital invitational workshop which brought together librarians, digital
library researchers, content experts, and text-markup experts to library researchers, content experts, and text-markup experts to
promote better discovery standards for electronic resources. The promote better discovery standards for electronic resources. The
resulting metadata element set defines fifteen metadata elements for resulting metadata element set defines fifteen metadata elements for
resource description in a cross-disciplinary information environment. resource description in a cross-disciplinary information environment.
This document contains the current text of Dublin Core "Version 1.1". This document contains the current text of Dublin Core "Version 1.1".
Version 1.1 is the basis of ANSI/NISO Z39.85-2001 [Z39.85]. The text Version 1.1 is the basis of ANSI/NISO Z39.85-2001 [Z39.85]. The text
in the present RFC closely follows the text submitted for the 2007 in the present RFC closely follows the text in the 2007 revision of
revision of ANSI/NISO Z39.85, especially sections 2-6 and 10-12. The ANSI/NISO Z39.85, especially sections 2-6 and 10-12. The present RFC
present RFC obsoletes the Internet RFC 2413 [RFC2413], which was the obsoletes the Internet RFC 2413 [RFC2413], which was the first
first published version of the Dublin Core ("Version 1.0"). The main published version of the Dublin Core ("Version 1.0"). The main
differences between the present RFC and RFC 2413 are in the wording differences between the present RFC and RFC 2413 are in the wording
of definitions -- for Contributor and Date (semantically broadened), of definitions -- for Contributor and Date (semantically broadened),
for Relation (clarified), and in general removing redundant for Relation (clarified), and in general removing redundant
references to "the content of" a resource. In addition, the present references to "the content of" a resource. In addition, the present
RFC recommends lowercase element names (consistent with RDF property RFC recommends lowercase element names (consistent with RDF property
types), remains silent about the unrestrictedness of element ordering types), remains silent about the unrestrictedness of element ordering
and repeatability (application profiles being the proper place to and repeatability (application profiles being the proper place to
discuss such topics), and references the current abstract model, discuss such topics), and references the current abstract model,
vocabularies, and namespace policies in which the Dublin Core is vocabularies, and namespace policies in which the Dublin Core is
embedded. embedded.
skipping to change at page 3, line 16 skipping to change at page 3, line 16
context of an application profile which constrains or specifies their context of an application profile which constrains or specifies their
use in accordance with local or community-based requirements and use in accordance with local or community-based requirements and
policies. The specification of such implementation detail is outside policies. The specification of such implementation detail is outside
the scope of this standard. the scope of this standard.
4. Definitions 4. Definitions
DCMI -- the Dublin Core Metadata Initiative, maintenance agency for DCMI -- the Dublin Core Metadata Initiative, maintenance agency for
Dublin Core Metadata Element Set. Dublin Core Metadata Element Set.
Resource -- anything that might be identified (the same definition as
in Internet RFC 3986 and in the DCMI Abstract Model).
Lifecycle of a resource -- a sequence of events that mark the Lifecycle of a resource -- a sequence of events that mark the
development and use of a resource. Some examples of events in a development and use of a resource. Some examples of events in a
lifecycle are: conception of an invention, creation of a draft, lifecycle are: conception of an invention, creation of a draft,
revision of an article, publication of a book, acquisition by a revision of an article, publication of a book, acquisition by a
library, transcription to magnetic disk, migration to optical library, transcription to magnetic disk, migration to optical
storage, translation into English, and derivation of a new work storage, translation into English, and derivation of a new work
(e.g., a movie). (e.g., a movie).
5. The Element Set 5. The Element Set
skipping to change at page 3, line 43 skipping to change at page 3, line 46
The use of element names and URIs in the context of different The use of element names and URIs in the context of different
implementation technologies is explained in DCMI Encoding Guidelines implementation technologies is explained in DCMI Encoding Guidelines
[DCENCOD]. [DCENCOD].
6. The Elements 6. The Elements
Element Name: title Element Name: title
Label: Title Label: Title
Definition: A name given to the resource. Definition: A name given to the resource.
Comment: Typically, Title will be a name by which the resource is
formally known.
Element Name: creator Element Name: creator
Label: Creator Label: Creator
Definition: An entity primarily responsible for making the resource. Definition: An entity primarily responsible for making the resource.
Comment: Examples of a Creator include a person, an organization, Comment: Examples of a Creator include a person, an organization,
or a service. Typically, the name of a Creator should be or a service. Typically, the name of a Creator should be
used to indicate the entity. used to indicate the entity.
Element Name: subject Element Name: subject
Label: Subject Label: Subject
Definition: The topic of the resource. Definition: The topic of the resource.
Comment: Typically, the topic will be represented using Comment: Typically, the subject will be represented using
keywords, key phrases, or classification codes. keywords, key phrases, or classification codes.
Recommended best practice is to use a controlled Recommended best practice is to use a controlled
vocabulary. To describe the spatial or temporal vocabulary. To describe the spatial or temporal
topic of the resource, use the Coverage element. topic of the resource, use the Coverage element.
Element Name: description Element Name: description
Label: Description Label: Description
Definition: An account of the resource. Definition: An account of the resource.
Comment: Description may include but is not limited to: Comment: Description may include but is not limited to:
skipping to change at page 5, line 30 skipping to change at page 5, line 30
Label: Identifier Label: Identifier
Definition: An unambiguous reference to the resource within a given Definition: An unambiguous reference to the resource within a given
context. context.
Comment: Recommended best practice is to identify the Comment: Recommended best practice is to identify the
resource by means of a string conforming resource by means of a string conforming
to a formal identification system. to a formal identification system.
Element Name: source Element Name: source
Label: Source Label: Source
Definition: The resource from which the described resource is Definition: A related resource from which the described resource
derived. is derived.
Comment: The described resource may be derived from the Comment: The described resource may be derived from the
related resource in whole or in part. Recommended related resource in whole or in part. Recommended
best practice is to identify the related resource best practice is to identify the related resource
by means of a string conforming to a formal by means of a string conforming to a formal
identification system. identification system.
Element Name: language Element Name: language
Label: Language Label: Language
Definition: A language of the resource. Definition: A language of the resource.
skipping to change at page 6, line 11 skipping to change at page 6, line 11
Comment: Recommended best practice is to identify the Comment: Recommended best practice is to identify the
related resource by means of a string conforming related resource by means of a string conforming
to a formal identification system. to a formal identification system.
Element Name: coverage Element Name: coverage
Label: Coverage Label: Coverage
Definition: The spatial or temporal topic of the resource, the Definition: The spatial or temporal topic of the resource, the
spatial applicability of the resource, or the spatial applicability of the resource, or the
jurisdiction under which the resource is relevant. jurisdiction under which the resource is relevant.
Comment: Spatial topic may be a named place or a location Comment: Spatial topic and spatial applicability may be a named
specified by its geographic coordinates. Temporal place or a location specified by its geographic
period may be a named period, date, or date range. coordinates. Temporal period may be a named period,
A jurisdiction may be a named administrative entity date, or date range. A jurisdiction may be a named
or a geographic place to which the resource applies. administrative entity or a geographic place to which the
Recommended best practice is to use a controlled resource applies. Recommended best practice is to use a
vocabulary such as the Thesaurus of Geographic Names controlled vocabulary such as the Thesaurus of
[TGN]. Where appropriate, named places or time periods Geographic Names [TGN]. Where appropriate, named places
can be used in preference to numeric identifiers such or time periods can be used in preference to numeric
as sets of coordinates or date ranges. identifiers such as sets of coordinates or date ranges.
Element Name: rights Element Name: rights
Label: Rights Label: Rights
Definition: Information about rights held in and over the resource. Definition: Information about rights held in and over the resource.
Comment: Typically, rights information includes a statement about Comment: Typically, rights information includes a statement about
various property rights associated with the resource, various property rights associated with the resource,
including intellectual property rights. including intellectual property rights.
7. Security Considerations 7. Security Considerations
skipping to change at page 8, line 15 skipping to change at page 8, line 15
11. Appendix A: Further Reading 11. Appendix A: Further Reading
(This appendix is not part of the standard. It is included for (This appendix is not part of the standard. It is included for
information only.) information only.)
Further information about the Dublin Core metadata element set is Further information about the Dublin Core metadata element set is
available at the URL, available at the URL,
http://dublincore.org/ http://dublincore.org/
This web site contains information about workshops, reports, working This Web site contains information about workshops, reports, working
group papers, projects, and new developments concerning the Dublin group papers, projects, and new developments concerning the Dublin
Core Metadata Initiative (DCMI). Core Metadata Initiative (DCMI).
12. Appendix B: Maintenance Agency 12. Appendix B: Maintenance Agency
(This appendix is not part of the standard. It is included for (This appendix is not part of the standard. It is included for
information only.) information only.)
The Dublin Core Metadata Initiative (DCMI) is responsible for the The Dublin Core Metadata Initiative (DCMI) is responsible for the
development, standardization, and promotion of the Dublin Core development, standardization, and promotion of the Dublin Core
skipping to change at page 8, line 44 skipping to change at page 8, line 44
set forth therein, the authors retain all their rights. set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Expires 19 August 2007 Expires 20 October 2007
 End of changes. 12 change blocks. 
24 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/