Difference between revisions of "Audubon Core"
m (Further extraction from Word doc) |
m (further drafting) |
||
Line 14: | Line 14: | ||
'''Part of TDWG Standard:''' Audubon Core | '''Part of TDWG Standard:''' Audubon Core | ||
− | '''Document Status:''' This document is a [http://www.tdwg.org/fileadmin/tdwg_std_drafts/tdwg_standards_documentation_specification.html#a_3 TDWG Type 3 Non Normative Document]. It is extracted from XXXX, which delves further into the rationale | + | '''Document Status:''' This document is a [http://www.tdwg.org/fileadmin/tdwg_std_drafts/tdwg_standards_documentation_specification.html#a_3 TDWG Type 3 Non Normative Document]. It is extracted from XXXX, which delves further into the rationale of some of the design choices behind the Audubon Core. |
+ | '''See also:''' [https://journals.ku.edu/index.php/jbi/article/view/4117 Discovery and Publishing of Primary Biodiversity Data associated with Multimedia Resources: The Audubon Core Strategies and Approaches.] R. Morris et al., ''Biodiversity Informatics,'' 8, jul. 2013. | ||
==Introduction== | ==Introduction== | ||
The Audubon Core Multimedia Resources Metadata schema (“AC schema”, or simply “AC”) is a set of metadata vocabularies for describing biodiversity-related multimedia resources and collections. The specification is independent of how these vocabularies may be represented for machine use. | The Audubon Core Multimedia Resources Metadata schema (“AC schema”, or simply “AC”) is a set of metadata vocabularies for describing biodiversity-related multimedia resources and collections. The specification is independent of how these vocabularies may be represented for machine use. | ||
+ | |||
Multimedia Resources are digital or physical artifacts which normally comprise more than text. These include pictures, artwork, drawings, photographs, sound, video, animations, presentation materials, and interactive online media including, e.g., identification tools. A multimedia collection is an assemblage of such objects, whether curated or not, and whether electronically accessible or not. For the purposes of this document we regard a collection of multimedia resources itself as a ‘multimedia resource’. Wherever discussion or specification can apply only to a collection or only to a single media resource, we say so explicitly. | Multimedia Resources are digital or physical artifacts which normally comprise more than text. These include pictures, artwork, drawings, photographs, sound, video, animations, presentation materials, and interactive online media including, e.g., identification tools. A multimedia collection is an assemblage of such objects, whether curated or not, and whether electronically accessible or not. For the purposes of this document we regard a collection of multimedia resources itself as a ‘multimedia resource’. Wherever discussion or specification can apply only to a collection or only to a single media resource, we say so explicitly. | ||
Line 28: | Line 30: | ||
Every Audubon Core term has a plain text Name, a URI, and a plain text normative Definition. URIs for terms conform to the http URI scheme. Informally, one may understand this thusly: an http URI has the syntax of an http URL, but there is no expectation that putting it in a web browser will result in any information being returned to the browser, and if it does, the return may have no relevance. | Every Audubon Core term has a plain text Name, a URI, and a plain text normative Definition. URIs for terms conform to the http URI scheme. Informally, one may understand this thusly: an http URI has the syntax of an http URL, but there is no expectation that putting it in a web browser will result in any information being returned to the browser, and if it does, the return may have no relevance. | ||
− | Because http URIs are rather lengthy, AC documents follow a standard practice of introducing a short prefix comprising a "namespace qualifier" separated by a colon from a mnemonic name closely related to the term's Name. The namespace of terms borrowed from other vocabularies is that of the original. The namespace of denovo AC terms is http://rs.tdwg.org/ac/terms/. In the | + | Because http URIs are rather lengthy, AC documents follow a standard practice of introducing a short prefix comprising a "namespace qualifier" separated by a colon from a mnemonic name closely related to the term's Name. The namespace of terms borrowed from other vocabularies is that of the original. The namespace of denovo AC terms is http://rs.tdwg.org/ac/terms/. In the '''[Audubon_Core_Term_List AC Term List]''', each term entry has a row with the term name. Following the practice of the '''[http://rs.tdwg.org/dwc/terms/ Darwin Core terms,]''' this term name is generally an "unqualified name" preceded by a widely accepted prefix designating an abbreviation for the namespace. The result is known as a qualified name. For example the normative wiki documentation for the borrowed term dcterms:identifier has URI http://purl.org/dc/terms/identifier. In this document we will follow the qualified name convention that is established by the wiki rendering. In fact, most of the URIs for terms borrowed from external vocabularies (about half of them) do in fact resolve to something in relevant documentation for that external standard. Sometimes it is not precise because the documentation is a PDF document and several (different!) URIs might apparently resolve to the same place. |
+ | |||
+ | ==Implementations== | ||
+ | The normative'''[[Audubon_Core_Term_List | AC Term List]]''' and '''[[Audubon_Core_Structure| Audubon Core Structure]]''' documents represent a ''data model.'' For actual use of Audubon Core, it is necessary to select an implementation, preferably one with some status designated by [http://www.tdwg.org/ TDWG.] A list of known implementations is at '''[[Audubon Core Implementations]] |
Revision as of 17:35, 15 October 2013
Title: Audubon Core Non Normative Document
Date: October 30, 2013
Abstract: The Audubon Core is a set of vocabularies designed to represent metadata for biodiversity multimedia resources and collections. These vocabularies aim to represent information that will help to determine whether a particular resource or collection will be fit for some particular biodiversity science application before acquiring the media. Among others, the vocabularies address such concerns as the management of the media and collections, descriptions of their content, their taxonomic, geographic, and temporal coverage, and the appropriate ways to retrieve, attribute and reproduce them.
Contributors: Robert A. Morris, Vijay Barve, Mihail Carausu, Vishwas Chavan, Jose Cuadra, Chris Freeland, Gregor Hagedorn, Patrick Leary, Dimitry Mozzherin, Annette Olson, Greg Riccardi, Ivan Teage
Legal: This document is governed by the standard legal, copyright, licensing provisions and disclaimers issued by the Taxonomic Databases Working Group.
Part of TDWG Standard: Audubon Core
Document Status: This document is a TDWG Type 3 Non Normative Document. It is extracted from XXXX, which delves further into the rationale of some of the design choices behind the Audubon Core.
See also: Discovery and Publishing of Primary Biodiversity Data associated with Multimedia Resources: The Audubon Core Strategies and Approaches. R. Morris et al., Biodiversity Informatics, 8, jul. 2013.
Introduction
The Audubon Core Multimedia Resources Metadata schema (“AC schema”, or simply “AC”) is a set of metadata vocabularies for describing biodiversity-related multimedia resources and collections. The specification is independent of how these vocabularies may be represented for machine use.
Multimedia Resources are digital or physical artifacts which normally comprise more than text. These include pictures, artwork, drawings, photographs, sound, video, animations, presentation materials, and interactive online media including, e.g., identification tools. A multimedia collection is an assemblage of such objects, whether curated or not, and whether electronically accessible or not. For the purposes of this document we regard a collection of multimedia resources itself as a ‘multimedia resource’. Wherever discussion or specification can apply only to a collection or only to a single media resource, we say so explicitly.
Multimedia descriptions are digital records that document underlying multimedia resources or collections. AC is focused on biodiversity-related multimedia resources. It shares terminology and concerns with many well-known and important standards for describing access to resources such as Dublin Core(DC), Darwin Core (DwC), the Adobe Extensible Metadata Platform (XMP), the International Press and Telecommunications Council (IPTC), the Metadata Working Group (MWG) schema, the Natural Collections Schema (NCD), and others. Where there is an exact match to the usage of such standards, AC adopts their identifiers and definitions. Many collections of biodiversity multimedia already have descriptions of their media expressed in DwC or DC. By using those vocabularies where suitable, AC particularly intends to make it easy for such collections to reuse their existing descriptions, augmented where necessary by other terms.
Audubon Core Terms
An Audubon Core record is a description, using the Audubon Core terms, of a multimedia resource. Two kinds of terms are specified by AC: record-level terms and access-level terms. Record-level terms apply to the media resource being described. Almost all terms are record-level terms. One such term, serviceAccessPoint plays a special role in helping to retrieve the resource that the record describes. A multimedia resource may have more than one serviceAccessPoint, each of which is described by values of one or more access-level terms. The access-level terms provide such things as a web address at which a digital representation of the resource can be retrieved, the size of such a retrieved object, etc. An Audubon Core record is thus a set of terms that conforms to the normative documents, contains at least the four mandatory terms described below, and which provides metadata that describes a single multimedia resource (possibly including a Collection). It usually includes an identifier that may have been assigned to the resource by an external authority or by the provider of the metadata record.
Every Audubon Core term has a plain text Name, a URI, and a plain text normative Definition. URIs for terms conform to the http URI scheme. Informally, one may understand this thusly: an http URI has the syntax of an http URL, but there is no expectation that putting it in a web browser will result in any information being returned to the browser, and if it does, the return may have no relevance.
Because http URIs are rather lengthy, AC documents follow a standard practice of introducing a short prefix comprising a "namespace qualifier" separated by a colon from a mnemonic name closely related to the term's Name. The namespace of terms borrowed from other vocabularies is that of the original. The namespace of denovo AC terms is http://rs.tdwg.org/ac/terms/. In the [Audubon_Core_Term_List AC Term List], each term entry has a row with the term name. Following the practice of the Darwin Core terms, this term name is generally an "unqualified name" preceded by a widely accepted prefix designating an abbreviation for the namespace. The result is known as a qualified name. For example the normative wiki documentation for the borrowed term dcterms:identifier has URI http://purl.org/dc/terms/identifier. In this document we will follow the qualified name convention that is established by the wiki rendering. In fact, most of the URIs for terms borrowed from external vocabularies (about half of them) do in fact resolve to something in relevant documentation for that external standard. Sometimes it is not precise because the documentation is a PDF document and several (different!) URIs might apparently resolve to the same place.
Implementations
The normative AC Term List and Audubon Core Structure documents represent a data model. For actual use of Audubon Core, it is necessary to select an implementation, preferably one with some status designated by TDWG. A list of known implementations is at Audubon Core Implementations