ISO 15836-2009

Disclosure to Promote the Right To InformationWhereas the Parliament of India has set out to provide a practical regime of right to information for citizens to secure access to information under the control of public authorities, in order to promote transparency and accountability in the working of every public authority, and whereas the attached publication of the Bureau of Indian Standards is of particular interest to the public, particularly disadvantaged communities and those engaged in the pursuit of education and knowledge, the attached public safety standard is made available to promote the timely dissemination of this information in an accurate manner to the public. इंटरनेट मानक“!ान $ एक न’ भारत का +नम-ण”Satyanarayan Gangaram Pitroda“Invent a New India Using Knowledge”“प0रा1 को छोड न’ 5 तरफ”Jawaharlal Nehru“Step Out From the Old to the New”“जान1 का अ+धकार, जी1 का अ+धकार”Mazdoor Kisan Shakti Sangathan“The Right to Information, The Right to Live”“!ान एक ऐसा खजाना जो कभी च0राया नहB जा सकता है”Bhartṛhari—Nītiśatakam“Knowledge is such a treasure which cannot be stolen”ैIS 15992 (2012): Information and Documentation - The DublinCore Metadata Element Set [MSD 5: Documentation andInformation]Hkkjrh; ekudlwpuk ,oa çys[ku —n MCyhu dksj esVkMkVk ,yhesaV lsVIndian StandardINFORMATION AND DOCUMENTATION —THE DUBLIN CORE METADATA ELEMENT SETICS 35.240.30© BIS 2012September 2012 Price Group 3B U R E A U O F I N D I A N S T A N D A R D SMANAK BHAVAN, 9 BAHADUR SHAH ZAFAR MARGNEW DELHI 110002IS 15992 : 2012ISO 15836 : 2009Documentation and Information Sectional Committee, MSD 5NATIONAL FOREWORDThis Indian Standard which is identical with ISO 15836 : 2009 ‘Information and documentation — TheDublin Core metadata element set’ issued by the International Organization for Standardization (ISO)was adopted by the Bureau of Indian Standards on the recommendation of the Documentation andInformation Sectional Committee and approval of the Management and Systems Division Council.The text of ISO Standard has been approved as suitable for publication as an Indian Standard withoutdeviations. Certain conventions are, however, not identical to those used in Indian Standards. Attentionis particularly drawn to the following:Wherever the words ‘International Standard’ appear referring to this standard, they should beread as ‘Indian Standard’.The technical committee has reviewed the provision of the following International Publications referredin this adopted standard and has decided that it is acceptable for use in conjunction with this standard:International Publication TitleANSI/NISO Z39.85 : 2007 The Dublin Core Metadata Element SetDCAM DCMI Abstract Model(Available at http://dublincore.org/documents/abstract-model/)Technical Corrigendum 1 published in 2009 to the above International Standard, has been given atthe end of this publication.Annex A of this Indian Standard is for information only.IS 15992 : 2012ISO 15836 : 2009iIntroduction The Dublin Core Metadata Element Set is a vocabulary of fifteen properties for use in resource description. The name “Dublin” comes from its original 1995 invitational workshop, which took place 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 International Standard is 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, the DCMI Type Vocabulary [DCMI-TYPE]. 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 bases of the DCMI Abstract Model [DCAM]. In 2006, the DCMI Usage Board undertook an editorial 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 to 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 a revised terms documentation. This revision of the original ANSI/NISO Z39.85 standard that was issued in 2001 corresponds 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 Namespace 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 be already made to the labels, definitions and usage comments associated with existing DCMI terms. IS 15992 : 2012ISO 15836 : 2009ii1 Scope This International Standard establishes a standard for cross-domain resource description, known as the Dublin Core Metadata Element Set. Like RFC 3986, this International Standard does not limit what might be a resource. This International Standard defines the elements 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. However, it does not define implementation detail, which is outside the scope of this International Standard. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ANSI/NISO Z39.85:2007, The Dublin Core Metadata Element Set DCAM, DCMI Abstract Model. Available at http://dublincore.org/documents/abstract-model/ 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions For the purposes of this document, the terms and definitions given in DCAM and the following apply. 3.1.1 resource anything that might be identified [RFC 3986, DCMI Abstract Model] 3.1.2 lifecycle of a resource sequence of events that mark the development and use of a resource EXAMPLES Conception of an invention, creation of a draft, revision of an article, publication of a book, acquisition by a library, transcription to magnetic disk, migration to optical storage, translation into English, and derivation of a new work (e.g. a movie). 3.2 Abbreviated terms DCMI Dublin Core Metadata Initiative IS 15992 : 2012ISO 15836 : 20091Indian StandardINFORMATION AND DOCUMENTATION —THE DUBLIN CORE METADATA ELEMENT SET4 Element set In the element descriptions given in Table 1, each element has a descriptive label (“label”) for human recognition and a unique token (“name”) for use in machine processing. In accordance with the DCMI Namespace Policy [DCMI-NAMESPACE] specified in ANSI/NISO Z39.85:2007, the “name” of an element is appended to a DCMI namespace URI to construct a Uniform Resource Identifier as a globally 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]. Table 1 — Element descriptions Element name Label Definition Remarks title Title name given to the resource creator Creator entity primarily responsible for making the resource Examples of Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity. subject Subject topic of the resource Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary. To describe the spatial or temporal topic of the resource, use the Coverage element. description Description account of the resource Description may include, but is not limited to, an abstract, a table of contents, a graphical representation, or a free-text account of the resource. publisher Publisher entity responsible for making the resource available Examples of Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to identify the entity. contributor Contributor entity responsible for making contributions to the resource Examples of a Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity. date Date point or period of time associated with an event in the lifecycle of the resource Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding schema such as the W3CDTF profile of ISO 8601 [W3CDTF]. type Type nature or genre of the resource Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMI-TYPE]. To describe the file format, physical medium, or dimensions of the resource, use the Format element. format Format file format, physical medium, or dimensions of the resource Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME]. IS 15992 : 2012ISO 15836 : 20092Table 1 (continued) Element name Label Definition Remarks identifier Identifier unambiguous reference to the resource within a given context Recommended best practice is to identify the resource by means of a string conforming to a formal identification system. source Source related resource from which the described resource is derived The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system. language Language language of the resource Recommended best practice is to use a controlled vocabulary such as RFC 4646. relation Relation related resource Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system. coverage Coverage spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant 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 named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Getty 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. rights Rights information about rights held in and over the resource Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights. IS 15992 : 2012ISO 15836 : 20093Annex A (informative) Further information Further information about the Dublin Core Metadata Element Set is available at the URL http://dublincore.org/. This website contains information about workshops, reports, working group papers, projects, and new developments concerning the Dublin Core Metadata Initiative (DCMI). IS 15992 : 2012ISO 15836 : 20094Bibliography [1] ISO 8601, Data elements and interchange formats — Information interchange — Representation of dates and times [2] DCMI-ENCODINGS, DCMI Encoding Guidelines. Available at http://dublincore.org/resources/expressions/ [3] DCMI-TERMS, DCMI Metadata Terms. Available at http://dublincore.org/documents/dcmi-terms/ [4] DCMI-NAMESPACE, DCMI Namespace Policy. Available at http://dublincore.org/documents/dcmi-namespace/ [5] DCMI-TYPE, DCMI Type Vocabulary. Available at http://dublincore.org/documents/dcmi-type-vocabulary/ [6] W3CDTF, Date and Time Formats, W3C Note. Available at http://www.w3.org/TR/NOTE-datetime [7] TGN, Getty Thesaurus of Geographic Names. Available at http://www.getty.edu/research/tools/vocabulary/tgn/index.html [8] MIME, MIME Media Types. Available at http://www.isi.edu/in-notes/iana/assignments/media-types/ [9] RFC 3986, Uniform Resource Identifier (URI): Generic Syntax. Available at http://www.ietf.org/rfc/rfc3986.txt [10] RFC 4646, Tags for identifying languages. Available at http://www.ietf.org/rfc/rfc4545.txt IS 15992 : 2012ISO 15836 : 20095IS 15992 : 2012ISO 15836 : 20096TECHNICAL CORRIGENDUM 1 Technical Corrigendum 1 to ISO 15836:2009 was prepared by Technical Committee ISO/TC 46, Information and documentation, Subcommittee SC 4, Technical interoperability. Page 5, Bibliography, Reference [10] Replace Reference [10] with the following reference so as to correct the hyperlink: [10] RFC 4646, Tags for identifying languages. Available at http://www.ietf.org/rfc/rfc4646.txt Bureau of Indian StandardsBIS is a statutory institution established under the Bureau of Indian Standards Act, 1986 to promoteharmonious development of the activities of standardization, marking and quality certification of goodsand attending to connected matters in the country.CopyrightBIS has the copyright of all its publications. No part of these publications may be reproduced in any formwithout the prior permission in writing of BIS. This does not preclude the free use, in course of imple-menting the standard, of necessary details, such as symbols and sizes, type or grade designations.Enquiries relating to copyright be addressed to the Director (Publications), BIS.Review of Indian StandardsAmendments are issued to standards as the need arises on the basis of comments. Standards are alsoreviewed periodically; a standard along with amendments is reaffirmed when such review indicates thatno changes are needed; if the review indicates that changes are needed, it is taken up for revision. Usersof Indian Standards should ascertain that they are in possession of the latest amendments or edition byreferring to the latest issue of ‘BIS Catalogue’ and ‘Standards: Monthly Additions’.This Indian Standard has been developed from Doc No.: MSD 5 (394).Amendments Issued Since Publication______________________________________________________________________________________Amendment No. Date of Issue Text Affected______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________