AS ISO 15836.1 pdf download

AS ISO 15836.1 pdf download.Information and documentation—The Dublin Core metadata element set
1  Scope
This document establishes 15 core metadata elements for cross-domain resource description. These terms are part of a larger set of metadata vocabularies maintained by the Dublin Core Metadata Initiative. Properties in the /terms/ namespace are included in ISO 15836-2. This document does not limit what might be a resource. This document does not provide implementation guidelines. However, the elements 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.
3  Terms and definitions
For the purposes of this document, the terms and definitions given in DCAM and the following apply. ISO and IEC maintain terminological databases for use in standardization at the following addresses: — IEC Electropedia: available at http://www.electropedia.org/ — ISO Online browsing platform: available at http://www.iso.org/obp NOTE  In the definitions for elements, the conventions in 3.2 have been used and are explained in notes. 3.1  General terms and definitions 3.1.1 resource thing that might be identified [SOURCE: RFC 3986, DCMI Abstract Model] 3.1.2 lifecycle of a resource sequence of events that mark the development and use of a resource EXAMPLE 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  Naming elements 3.2.1 name token appended to the URI of a DCMI namespace to create the URI of the term EXAMPLE “title” or “creator”. 3.2.2 label descriptive name given an element for human recognition EXAMPLE “Title” or “Creator”. 3.2.3 Uniform Resource Identifier URI compact sequence of characters that identifies an abstract or physical resource. Note 1 to entry: URIs are used to identify terms. [SOURCE: ISO/IEC 12785-1:2009, 3.23] EXAMPLE http://purl.org/dc/elements/1.1/contributor 3.2.4 range class of which a value described by the term is an instance 3.3  Core elements 3.3.1 title name given to the resource Label: Title URI: http://purl.org/dc/elements/1.1/title 3.3.2 creator entity primarily responsible for making the resource Note 1 to entry: Examples of a Creator include a person, an organization, or a service. Label: Creator URI: http://purl.org/dc/ elements/1.1/creator 3.3.3 subject topic of the resource Note 1 to entry: Typically, the subject will be represented using keywords, key phrases, or classification codes. Best practice is to use a controlled vocabulary.3.3.4 description account of the resource Note 1 to entry: 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 Label: Description URI: http://purl.org/dc/elements/1.1/description 3.3.5 publisher entity responsible for making the resource available Note 1 to entry: Examples of a Publisher include a person, an organization, or a service. Label: Publisher URI: http://purl.org/dc/elements/1.1/publisher 3.3.6 contributor entity responsible for making contributions to the resource Note 1 to entry: Examples of a Contributor include a person, an organization, or a service. Label: Contributor URI: http://purl.org/dc/elements/1.1/contributor 3.3.7 date point or period of time associated with an event in the lifecycle of the resource Note 1 to entry: Date may be used to express temporal information at any level of granularity. Best practice is to express the date, time, or period according to ISO standard on representation of dates and times (ISO 8601).3.3.10 identifier compact sequence of characters that establishes the identity of a resource, institution or person alone or in combination with other elements [SOURCE: ISO 8459:2009, 2.27] Note 1 to entry: Best practice is to identify the resource by means of a string conforming to a formal identification system. Label: Identifier URI: http://purl.org/dc/elements/1.1/identifier 3.3.11 source related resource from which the described resource is derived Note 1 to entry: The described resource can be derived from the related resource in whole or in part. Best practice is to identify the related resource by means of a string conforming to a formal identification system. Label: Source URI: http://purl.org/dc/elements/1.1/source