ANSI NISO Z39.85-2012 The Dublin Core Metadata Element Set《都柏林核心元数据集》.pdf

1、 ANSI/NISO Z39.85-2012 ISSN: 1041-5635 The Dublin Core Metadata Element Set Abstract: Defines fifteen metadata elements for resource description in a cross-disciplinary information environment. An American National Standard Developed by the National Information Standards Organization Approved Februa

2、ry 20, 2013 by the American National Standards Institute ANSI/NISO Z39.85-2012 About NISO Standards NISO standards are developed by the Standards Committees of the National Information Standards Organization. The development process is a strenuous one that includes a rigorous peer review of proposed

3、 standards open to each NISO Voting Member and any other interested party. Final approval of the standard involves verification by the American National Standards Institute that its requirements for due process, consensus, and other approval criteria have been met by NISO. Once verified and approved

4、, NISO Standards also become American National Standards. This standard may be revised or withdrawn at any time. For current information on the status of this standard contact the NISO office or visit the NISO website at: www.niso.org Published by NISO 3600 Clipper Mill Road Suite 302 Baltimore, MD

5、21211 www.niso.org Copyright 2013 by the National Information Standards Organization All rights reserved under International and Pan-American Copyright Conventions. For noncommercial purposes only, this publication may be reproduced or transmitted in any form or by any means without prior permission

6、 in writing from the publisher, provided it is reproduced accurately, the source of the material is identified, and the NISO copyright status is acknowledged. All inquiries regarding translations into other languages or commercial reproduction or distribution should be addressed to: NISO, 3600 Clipp

7、er Mill Road, Suite 302, Baltimore, MD 21211. ISSN: 1041-5635 (National information standards series) ISBN-13: 978-1-937522-14-8 ANSI/NISO Z39.85-2012 i Contents Foreword . ii 1 Purpose and Scope 1 2 References 1 3 Definitions . 2 4 The Element Set . 2 5 The Elements 2 Appendix A (informative) Furth

8、er Reading 6 Appendix B (informative) Maintenance Agency 7 ANSI/NISO Z39.85-2012 ii Foreword (This foreword is not part of The Dublin Core Metadata Element Set, ANSI/NISO Z39.85-2012. It is included for information only.) About This Standard The Dublin Core Metadata Element Set is a vocabulary of fi

9、fteen properties for use in resource description. The name “Dublin” is due to its origin at a 1995 invitational workshop in Dublin, Ohio; “core” because its elements are broad and generic, usable for describing a wide range of resources. The fifteen element “Dublin Core” described in this standard i

10、s part of a larger set of metadata vocabularies and technical specifications maintained by the Dublin Core Metadata Initiative (DCMI). The full set of vocabularies, DCMI Metadata Terms DCMI-TERMS, also includes a set of resource classes (including the DCMI Type Vocabulary DCMI-TYPE), vocabulary enco

11、ding schemes, and syntax encoding schemes. The terms in DCMI vocabularies are intended to be used in combination with terms from other, compatible vocabularies in the context of application profiles and on the basis of the DCMI Abstract Model DCAM. In 2006, the DCMI Usage Board undertook an editoria

12、l review of terms in the Dublin Core Metadata Element Set (DCMES) in order to clarify intended semantics and bring the wording of their definitions and usage comments into line with the language of the DCMI Abstract Model DCAM. A set of proposed changes was posted for Public Comment from August 28 t

13、o September 25, 2006. A face-to-face Usage Board meeting in Manzanillo, Mexico, on September 30, 2006 resulted in the publication on December 18, 2006 of a decision text, a response to comments, and revised terms documentation. The current 2012 version of the standard deleted a sentence about the sp

14、atial or temporal topic of the resource from the usage comments for dc:subject. The definitions of Subject and Coverage clearly overlap because a “spatial or temporal topic of the resource” is also a “topic of the resource.” The intent of the dc:subject usage comment was to provide guidance for user

15、s who prefer to use Dublin Core elements in non-overlapping ways. It had, however, been suggested that this comment creates ambiguity, for some readers, about whether the definitions really overlap. This ambiguity was avoided by simply removing the sentence. This revision of the original standard co

16、rresponds to version 1.1 on the Dublin Core Metadata Initiative website that resulted from the editorial review and public comment period described above. All changes made to terms of the Dublin Core Metadata Element Set since 2001 have been reviewed by a DCMI Usage Board in the context of a DCMI Na

17、mespace Policy DCMI-NAMESPACE. The namespace policy describes how DCMI terms are assigned Uniform Resource Identifiers (URIs) and sets limits on the range of editorial changes that may allowably be made to the labels, definitions, and usage comments associated with existing DCMI terms. NISO Voting P

18、ool Members The following organizations were members of the Voting Pool that approved this standard; individuals listed are the voting representatives for the member organization. American Geophysical Union (AGU) Jon Sears American Library Association (ALA) Nancy Kraft American Psychological Associa

19、tion (APA) Janice Fleming American Society for Indexing Judith Gibbs ANSI/NISO Z39.85-2012 iii American Society for Information Science & Technology (ASIS&T) Mark Needleman ARMA International Vicki Wiler Association of Research Libraries (ARL) Julia Blixrud College Center for Library Automation (CCL

20、A) David Brightbill EBSCO Information Services Oliver Pesch Ex Libris, Inc. Mike Dicus Inera Inc. Bruce Rosenblum Innovative Interfaces, Inc. Betsy Graham International DOI Foundation (IDF) Norman Paskin I ITHAKA/JSTOR/Portico Amy Kirchhoff Library of Congress John Zagas Los Alamos National Laborato

21、ry Miriam Blake Lyrasis Peter Murray Minitex Cecelia Boone Music Library Association Mark McKnight National Archives and Records Administration (NARA) Marilyn Redman National Security Agency Kate Dolan Polaris Library Systems Eric Graham Recording Industry Association of America (RIAA) Paul Jessop R

22、inggold, Inc. Donald Chvatal SAGE Publications Richard Fidczuk Society for Technical Communication (STC) Annette Reilly Society of American Archivists (SAA) Kathleen Dow World Scientific Publishing Chi Wai (Rick) Lee NISO Content and Collection Management Topic Committee The following individuals se

23、rved on the Content and Collection Management Topic Committee that approved this standard for ballot: Julia Blixrud (Co-Chair) Association of Research Libraries (ARL) Eva Bolkovac Yale University Library Eric Childress OCLC, Inc. Lettie Conrad SAGE Publications Diane Hillmann Syracuse University Mar

24、jorie Hlava National Federation of Advanced Information Services (NFAIS) Rebecca Kennison Columbia University Betty Landesman (Co-Chair) University of Baltimore, Langsdale Library Rice Majors University of Colorado at Boulder Dorothea Salo University of Wisconsin, Madison Ken Wells Innovative Interf

25、aces, Inc. ANSI/NISO Z39.85-2012 iv NISO Committee AS The following individuals served on the original standard committee that developed the 2001 version of the standard. The current version was revised by the Dublin Core Metadata Initiativethe Maintenance Agency for the standardin lieu of a reaffir

26、mation ballot, in accordance with both NISOs and DCMIs procedures. John Kunze (Chair) University of California / National Library of Medicine Rebecca Guenther Library of Congress Marjorie Hlava Access Innovations, Inc. Clifford Morgan John Wiley & Sons Ltd. John Perkins CIMI Consortium ANSI/NISO Z39

27、.85-2012 1 The Dublin Core Metadata Element Set 1 Purpose and Scope The Dublin Core Metadata Element Set is a standard for cross-domain resource description. As in Internet RFC 3986, Uniform Resource Identifier (URI): Generic Syntax, this specification does not limit the scope of what might be a res

28、ource. The elements described in this standard are typically used in the context of an application profile which constrains or specifies their use in accordance with local or community-based requirements and policies. The specification of such implementation detail is outside the scope of this stand

29、ard. 2 References This standard references the following documents. The bracketed abbreviation is used in the text of this Standard when referring to a specific reference. DCMI Abstract Model. DCAM http:/dublincore.org/documents/abstract-model/ DCMI Encoding Guidelines. DCMI-ENCODINGS http:/dublinco

30、re.org/resources/expressions/ DCMI Metadata Terms. DCMI-TERMS http:/dublincore.org/documents/dcmi-terms/ DCMI Namespace Policy. DCMI-NAMESPACE http:/dublincore.org/documents/dcmi-namespace/ DCMI Type Vocabulary. DCMI-TYPE http:/dublincore.org/documents/dcmi-type-vocabulary/ Date and Time Formats, W3

31、C Note. W3CDTF http:/www.w3.org/TR/NOTE-datetime Getty Thesaurus of Geographic Names. TGN http:/www.getty.edu/research/tools/vocabulary/tgn/index.html MIME Media Types. MIME http:/www.isi.edu/in-notes/iana/assignments/media-types/ Tags for Identifying Languages. RFC 4646 http:/www.ietf.org/rfc/rfc46

32、46.txt Uniform Resource Identifier (URI): Generic Syntax. RFC 3986 http:/www.ietf.org/rfc/rfc3986.txt ANSI/NISO Z39.85-2012 2 3 Definitions The following terms, as used in this standard, have the meanings indicated. Term Definition DCMI the Dublin Core Metadata Initiative, maintenance agency for the

33、 Dublin Core Metadata Element Set Lifecycle of a resource a sequence of events that mark the development and use of a resource Some examples of events in a lifecycle are: conception of an invention, creation of a draft, revision of an article, publication of a book, acquisition by a library, transcr

34、iption to magnetic disk, migration to optical storage, translation into English, and derivation of a new work (e.g., a movie). Resource anything that might be identified (the same definition as in Internet RFC 3986 and in the DCMI Abstract Model) 4 The Element Set In the element descriptions below,

35、each element has a descriptive label (“label”) for human consumption and a unique token (“name”) for use in machine processing. In accordance with the DCMI Namespace Policy DCMI-NAMESPACE, the “name” of an element is appended to a DCMI namespace URI to construct a Uniform Resource Identifier as a gl

36、obally unique identifier for that element. The use of element names and URIs in the context of different implementation technologies is explained in DCMI Encoding Guidelines DCMI-ENCODINGS. 5 The Elements Element Name: title Label: Title Definition: A name given to the resource. Element Name: creato

37、r Label: Creator Definition: An entity primarily responsible for making the resource. Comment: Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity. ANSI/NISO Z39.85-2012 3 Element Name: subject Label: Subject D

38、efinition: The topic of the resource. Comment: Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary. Element Name: description Label: Description Definition: An account of the resource. Comment: D

39、escription may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. Element Name: publisher Label: Publisher Definition: An entity responsible for making the resource available. Comment: Examples of a Publisher include a

40、 person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity. Element Name: contributor Label: Contributor Definition: An entity responsible for making contributions to the resource. Comment: Examples of a Contributor include a person, an organizat

41、ion, or a service. Typically, the name of a Contributor should be used to indicate the entity. Element Name: date Label: Date Definition: A point or period of time associated with an event in the lifecycle of the resource. Comment: Date may be used to express temporal information at any level of gra

42、nularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 W3CDTF. ANSI/NISO Z39.85-2012 4 Element Name: type Label: Type Definition: The nature or genre of the resource. Comment: Recommended best practice is to use a controlled vocabulary such as the DC

43、MI Type Vocabulary DCMITYPE. To describe the file format, physical medium, or dimensions of the resource, use the Format element. Element Name: format Label: Format Definition: The file format, physical medium, or dimensions of the resource. Comment: Examples of dimensions include size and duration.

44、 Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types MIME. Element Name: identifier Label: Identifier Definition: An unambiguous reference to the resource within a given context. Comment: Recommended best practice is to identify the resource by means

45、of a string conforming to a formal identification system. Element Name: source Label: Source Definition: A related resource from which the described resource is derived. Comment: The described resource may be derived from the related resource in whole or in part. Recommended best practice is to iden

46、tify the related resource by means of a string conforming to a formal identification system. Element Name: language Label: Language Definition: A language of the resource. Comment: Recommended best practice is to use a controlled vocabulary such as RFC 4646. ANSI/NISO Z39.85-2012 5 Element Name: rel

47、ation Label: Relation Definition: A related resource. Comment: Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system. Element Name: coverage Label: Coverage Definition: The spatial or temporal topic of the resource, the spatia

48、l applicability of the resource, or the jurisdiction under which the resource is relevant. Comment: Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a n

49、amed administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names TGN. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges. Element Name: rights Label: Rights Definition: Information about rights held in and over the resource. Comment: Typically, rights information includes a statement about various property rights associated with t