Audubon Core Term List
Title: Audubon Core Term List
Date version issued: 2020-08-23
Date created: 2013-10-23
Part of TDWG Standard: http://www.tdwg.org/standards/638
This version: http://rs.tdwg.org/ac/doc/termlist/2020-08-23
Latest version: http://rs.tdwg.org/ac/doc/termlist/
Previous version: http://rs.tdwg.org/ac/doc/termlist/2020-01-27
Replaced by: http://rs.tdwg.org/ac/doc/termlist/2020-10-13
Abstract: The Audubon Core is a set of vocabularies designed to
represent metadata for biodiversity multimedia resources and
collections. It aims 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. This document contains a
list of attributes of each Audubon Core term, including a documentation
name, a specified URI, a recommended English label for user interfaces,
a definition, and some ancillary notes. The version shown here was
adopted by Biodiversity Information Standards / TDWG at the general
meeting in October 2013 and updated in 2020. This document contains normative content that
may not be changed without due process.
Contributors: Robert A. Morris, Gregor Hagedorn, Annette Olson, Steve Baskauf, Vijay Barve, Mihail Carausu, Vishwas Chavan, José Cuadra, Chris Freeland, Patrick Leary, Dimitry Mozzherin, Greg Riccardi, Ivan Teage
Creator: GBIF/TDWG Multimedia Resources Task Group and Audubon Core Maintenance Group
Bibliographic citation: Audubon Core Maintenance Group. 2020. Audubon Core Term List. Biodiversity Information Standards (TDWG). http://rs.tdwg.org/ac/doc/termlist/2020-08-23
1 Introduction
There are four documents included in the Aububon Core Standard. This document provides details about the terms included in the 2020-08-23 version of the Audubon Core vocabulary. The Audubon Core Introduction document provides a brief introduction to the Audubon Core Standard. For information about the structure of Audubon Core, see the Audubon Core Structure document. For a more detailed guide to the use of Audubon Core, see the Audubon Core Guide document.
1.1 Status of the content of this document
Sections 1.3 through 5 are normative, except for Table 1. In Section 7 and its subparts, the values of the Normative URI, Definition, Layer, Required, and Repeatable are normative. The value of Usage (if it exists for a given term) is normative in that it specifies how a borrowed term should be used as part of Audubon Core. The values of Term Name is non-normative, although one can expect that the namespace abbreviation prefix is one commonly used for the term namespace. Labels and the values of all other properties (such as notes) are non-normative.
1.2 RFC 2119 key words
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
1.3 Categories of terms
An Audubon Core (AC) record is a description of a multimedia resource
using the AC vocabularies. Two kinds of terms are specified by this
document: those terms which describe representation-independent aspects
of the media and those which describe representation-dependent aspects.
Most terms are representation-independent, referring to an “abstract
multimedia resource”. One such term, ac:hasServiceAccessPoint
, refers to
or contains representation-dependent service access point metadata
describing a digital representation of the abstract multimedia resource (an instance of the ac:ServiceAccessPoint
class).
These metadata describe such things as a web address at which a digital
representation can be retrieved, and the format, extent, or licenses
that describe a particular such representation. A multimedia resource
may provide several access points for different representations (e.g.,
different resolutions).
2 Borrowed Vocabulary
When terms are borrowed from other vocabularies, AC uses the URIs,
common abbreviations, and namespace prefixes in use in those
vocabularies. The URIs are normative, but abbreviations and namespace
prefixes have no impact except as an aid to reading the documentation.
Table 1. Vocabularies from which terms have been borrowed (non-normative)
Note: URIs for terms in most of these namespaces do not dereference to anything. The authoritative documentation can be obtained by clicking on the vocabulary names in the table.
3 Namespaces, Prefixes and Term Names
The namespace of terms borrowed from other vocabularies is that of the
original. The namespace of de novo AC terms is
http://rs.tdwg.org/ac/terms/
. In the table of terms, each term entry has
a row with the term name. This term name is generally an “unqualified
name” preceded by a widely accepted prefix designating an abbreviation
for the namespace It is RECOMMENDED that implementers who need a
namespace prefix for the AC namespace use ac
. In this web document,
hovering over a term in the Index By Term Name
list below will reveal a complete URL that can be used in other web
documents to link to this document’s treatment of that term, even if
it is from a borrowed vocabulary. It is very important to note that some
vocabularies, e.g those of the
Dublin Core Metadata Initiative (DCMI),
provide versions of the same term in two different namespaces, one
providing for string values and one providing for URIs, even where that
separation is simply a recommendation, not a mandate. See this
DCMI wiki entry
on this topic. For vocabularies where such a practice is in place, we
often follow it and signal a reference in the Notes of our term
descriptions to the sister version of the term. An example is the pair
dc:type and dcterms:type. When such a pair allows repeated instances (e.g. as for dc:source and dcterms:source), particular care may be required in some
implementations of AC, because
some implementations may not provide enough structure to clearly state
the association between the members of a pair in the case of multiple
values of each. This is a special case of the issue treated in the
normative material on Multiplicity and Cardinality in the Audubon Core Structure document.
4 Layers
(The Audubon Core layer property has been deprecated as of 2020-01-27)
5 Literal- vs. URI-valued Terms
Some terms have two versions, one expecting a string literal value and
the other a URI. In these circumstances, the version expecting a string
is named with the suffix “Literal”, e.g. ac:metadataLanguageLiteral
. In
such cases, both forms MAY be provided, but care should be taken to
ensure that the uses reflect the same intent. In case of ambiguity, the
URI version prevails. All terms, including those whether or not with a
specific “Literal” suffix, specify in their definition whether the
required values are strings or URIs.
6 Vocabulary Indices (non-normative)
6.1 Index By Term Name
(See also 6.2 Index By Label)
Management Vocabulary
dcterms:available |
ac:commenter |
ac:commenterLiteral |
ac:comments |
ac:hasServiceAccessPoint |
dcterms:identifier |
xmp:MetadataDate |
ac:metadataLanguage |
ac:metadataLanguageLiteral |
dcterms:modified |
ac:providerManagedID |
xmp:Rating |
ac:reviewer |
ac:reviewerComments |
ac:reviewerLiteral |
ac:subtype |
ac:subtypeLiteral |
dcterms:title |
dc:type |
dcterms:type
Attribution Vocabulary
ac:attributionLinkURL |
ac:attributionLogoURL |
photoshop:Credit |
ac:fundingAttribution |
ac:licenseLogoURL |
xmpRights:Owner |
dc:rights |
dcterms:rights |
dc:source |
dcterms:source |
xmpRights:UsageTerms |
xmpRights:WebStatement
Agents Vocabulary
dc:creator |
dcterms:creator |
ac:metadataCreator |
ac:metadataCreatorLiteral |
ac:metadataProvider |
ac:metadataProviderLiteral |
ac:provider |
ac:providerLiteral
Content Coverage Vocabulary
ac:caption |
Iptc4xmpExt:CVterm |
dcterms:description |
dc:language |
dcterms:language |
ac:physicalSetting |
ac:subjectCategoryVocabulary |
ac:tag
Geography Vocabulary
Iptc4xmpExt:City |
dwc:continent |
dwc:coordinatePrecision |
dwc:coordinateUncertaintyInMeters |
dwc:country |
Iptc4xmpExt:CountryCode |
dwc:countryCode |
Iptc4xmpExt:CountryName |
dwc:county |
dwc:decimalLatitude |
dwc:decimalLongitude |
dwc:footprintSpatialFit |
dwc:footprintSRS |
dwc:footprintWKT |
dwc:geodeticDatum |
dwc:georeferencedBy |
dwc:georeferenceProtocol |
dwc:georeferenceRemarks |
dwc:georeferenceSources |
dwc:georeferenceVerificationStatus |
dwc:higherGeography |
dwc:higherGeographyID |
dwc:island |
dwc:islandGroup |
dwc:locality |
dwc:locationAccordingTo |
dwc:locationID |
dwc:locationRemarks |
Iptc4xmpExt:LocationShown |
dwc:maximumDepthInMeters |
dwc:maximumDistanceAboveSurfaceInMeters |
dwc:maximumElevationInMeters |
dwc:minimumDepthInMeters |
dwc:minimumDistanceAboveSurfaceInMeters |
dwc:minimumElevationInMeters |
dwc:municipality |
dwc:pointRadiusSpatialFit |
Iptc4xmpExt:ProvinceState |
dwc:stateProvince |
Iptc4xmpExt:Sublocation |
dwc:verbatimCoordinates |
dwc:verbatimCoordinateSystem |
dwc:verbatimDepth |
dwc:verbatimElevation |
dwc:verbatimLatitude |
dwc:verbatimLocality |
dwc:verbatimLongitude |
dwc:verbatimSRS |
dwc:waterBody |
Iptc4xmpExt:WorldRegion
Temporal Coverage Vocabulary
xmp:CreateDate |
dcterms:temporal |
ac:timeOfDay
Taxonomic Coverage Vocabulary
dwc:dateIdentified |
dwc:identificationQualifier |
dwc:identifiedBy |
dwc:lifeStage |
dwc:nameAccordingTo |
ac:otherScientificName |
dwc:preparations |
dwc:scientificName |
dwc:scientificNameID |
dwc:sex |
ac:subjectOrientation |
ac:subjectPart |
ac:taxonCount |
ac:taxonCoverage |
dwc:vernacularName
Resource Creation Vocabulary
ac:captureDevice |
ac:digitizationDate |
Iptc4xmpExt:LocationCreated |
ac:resourceCreationTechnique
Related Resources Vocabulary
ac:associatedObservationReference |
ac:associatedSpecimenReference |
ac:derivedFrom |
ac:IDofContainingCollection |
ac:providerID |
ac:relatedResourceID
Service Access Point Vocabulary
ac:accessURI |
dc:format |
dcterms:format |
ac:furtherInformationURL |
ac:hashFunction |
ac:hashValue |
ac:licensingException |
exif:PixelXDimension |
exif:PixelYDimension |
ac:ServiceAccessPoint |
ac:serviceExpectation |
ac:variant |
ac:variantDescription |
ac:variantLiteral
6.2 Index By Label
(See also 6.1 Index By Term Name)
Management Vocabulary
Commenter |
Comments |
Date Available |
Identifier |
Metadata Date |
Metadata Language |
Modified |
Provider-managed ID |
Rating |
Reviewer |
Reviewer Comments |
Service Access Point |
Subtype |
Title |
Type
Attribution Vocabulary
Attribution Link URL |
Attribution URL |
Copyright Owner |
Copyright Statement |
Credit |
Funding |
License Logo URL |
License Terms |
License URL |
Published Source
Agents Vocabulary
Creator |
Metadata Creator |
Metadata Provider |
Provider
Content Coverage Vocabulary
Caption |
Description |
Language |
Physical Setting |
Subject Category |
Subject Category Vocabulary |
Tag
Geography Vocabulary
City or Place Name |
Continent |
Coordinate Precision |
Coordinate Uncertainty In Meters |
Country |
Country Code |
Country Name |
County |
Decimal Latitude |
Decimal Longitude |
Footprint Spatial Fit |
Footprint SRS |
Footprint WKT |
Geodetic Datum |
Georeference Protocol |
Georeference Remarks |
Georeference Sources |
Georeference Verification Status |
Georeferenced By |
Higher Geography |
Higher Geography ID |
Island |
Island Group |
Locality |
Location According To |
Location ID |
Location Remarks |
Location Shown |
Maximum Depth In Meters |
Maximum Distance Above Surface In Meters |
Maximum Elevation In Meters |
Minimum Depth In Meters |
Minimum Distance Above Surface In Meters |
Minimum Elevation In Meters |
Municipality |
Point Radius Spatial Fit |
Province or State |
State Province |
Sublocation |
Verbatim Coordinate System |
Verbatim Coordinates |
Verbatim Depth |
Verbatim Elevation |
Verbatim Latitude |
Verbatim Locality |
Verbatim Longitude |
Verbatim SRS |
Water Body |
World Region
Temporal Coverage Vocabulary
Original Date and Time |
Temporal Coverage |
Time of Day
Taxonomic Coverage Vocabulary
Common Name |
Date Identified |
Identification Qualifier |
Identified By |
Name According To |
Other Scientific Name |
Scientific Name ID |
Scientific Taxon Name |
Subject Life Stage |
Subject Orientation |
Subject Part |
Subject Preparation Technique |
Subject Sex |
Taxon Count |
Taxon Coverage
Resource Creation Vocabulary
Capture Device |
Date and Time Digitized |
Location Created |
Resource Creation Technique
Related Resources Vocabulary
Associated Observation Reference |
Associated Specimen Reference |
Derived From |
ID of Containing Collection |
Provider ID |
Related Resource ID
Service Access Point Vocabulary
Access URI |
Format |
Further Information URL |
Hash |
Hash Function |
Image Height |
Image Width |
Licensing Exception Statement |
Service Access Point Class |
Service Expectation |
Variant |
Variant Description
7 Vocabularies
7.1 Management Vocabulary
Term Name: dcterms:available |
Normative URI |
http://purl.org/dc/terms/available |
Modified |
2020-01-27 |
Term version URI |
http://dublincore.org/usage/terms/history/#available-003 |
Label |
Date Available |
|
Required: No -- Repeatable: No |
Definition |
Date (often a range) that the resource became or will become available. |
Usage |
The date (often a range) that the resource became or will become available. The date and time MUST comply with the World Wide Web Consortium (W3C) datetime practice, https://www.w3.org/TR/NOTE-datetime, which requires that date and time representation correspond to ISO 8601:1998, but with year fields always comprising 4 digits. This makes datetime records compliant with 8601:2004, https://www.iso.org/standard/40874.html. AC datetime values MAY also follow 8601:2004 for ranges by separating two IS0 8601 datetime fields by a solidus ("forward slash", '/'). |
Notes |
A use case is the harvesting of metadata published before the media are available, which are pending a formal publication elsewhere. One important example is the case of metadata that documents an occurrence, which metadata harvesters might exploit without use of the media. See also the wikipedia IS0 8601 entry, https://en.wikipedia.org/wiki/ISO_8601, for further explanation and examples. |
Term Name: ac:commenter |
Normative URI |
http://rs.tdwg.org/ac/terms/commenter |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/commenter-2020-01-27 |
Label |
Commenter |
|
Required: No -- Repeatable: No |
Definition |
A URI denoting a person who created a comment. |
Usage |
Implementers and communities of practice MAY produce restrictions or recommendations on the choice of vocabularies. |
Notes |
See also Reviewer Comments for the distinction between Comments and Reviewer Comments. See also the entry for ac:commenterLiteral and the section Namespaces, Prefixes and Term Names in the Audubon Core Term List document for discussion of the rationale for separate terms taking URI values from those taking Literal values where both are possible. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
Term Name: ac:commenterLiteral |
Normative URI |
http://rs.tdwg.org/ac/terms/commenterLiteral |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/commenterLiteral-2020-01-27 |
Label |
Commenter |
|
Required: No -- Repeatable: No |
Definition |
The name of a person who created a comment, or the literal "anonymous" (= anonymously commented). |
Notes |
See also Reviewer Comments for the distinction between Comments and Reviewer Comments. See also the entry for ac:commenter and the section Namespaces, Prefixes and Term Names in the Audubon Core Term List document for discussion of the rationale for separate terms taking URI values from those taking Literal values where both are possible. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
Term Name: ac:comments |
Normative URI |
http://rs.tdwg.org/ac/terms/comments |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/comments-2020-01-27 |
Label |
Comments |
|
Required: No -- Repeatable: Yes |
Definition |
Any comment provided on the media resource, as free-form text. |
Usage |
Best practice would also identify the commenter. |
Notes |
Comments may refer to the resource itself (e. g., asserting a taxon name or location of a biological subject in an image), or to the relation between resource and associated metadata (e. g., asserting that the taxon name given in the metadata is wrong, without asserting a positive identification). There is a separate item for Reviewer Comments, which is defined more as an expert-level review. Implementers or communities of practice might establish conventions about the meaning of the absence of a commenter, but this specification is silent on that matter. |
Term Name: ac:hasServiceAccessPoint |
Normative URI |
http://rs.tdwg.org/ac/terms/hasServiceAccessPoint |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/hasServiceAccessPoint-2020-01-27 |
Label |
Service Access Point |
|
Required: No -- Repeatable: Yes |
Definition |
In a chosen serialization (RDF, XML Schema, etc.) the potentially multiple service access points (e.g., for different resolutions of an image) might be provided in a referenced or in a nested object. This property identifies one such access point. That is, each of potentially multiple values of hasServiceAccessPoint identifies a set of representation-dependent metadata using the properties defined under the Service Access Point Vocabulary section of the Audubon Core Term List document. |
Notes |
Some serializations may flatten the model of service-access points by (a) dropping ac:hasServiceAccessPoint, ac:variant and ac:variantLiteral, (b) repeating properties from the Service Access Point Vocabulary and prefixing them with values of ac:variantLiteral. If such a flat serialization is necessary for services, we recommend to select from among term names of the form "AB" where "A" is one of thumbnail, trailer, lowerQuality, mediumQuality, goodQuality, bestQuality, offline and "B" is one of AccessURI, Format, Extent, FurtherInformationURL, LicensingException, ServiceExpectation (example: thumbnailAccessURI). Implementers in specific constraint languages such as XML Schema or RDF may wish to make Access URI and perhaps dcterms:format mandatory on instances of the service access point. |
Term Name: dcterms:identifier |
Normative URI |
http://purl.org/dc/terms/identifier |
Modified |
2020-01-27 |
Term version URI |
http://dublincore.org/usage/terms/history/#identifierT-001 |
Label |
Identifier |
|
Required: Yes for media collections, No for media resources (but preferred if available) -- Repeatable: Yes |
Definition |
An unambiguous reference to the resource within a given context. |
Usage |
An arbitrary code that is unique for the resource, with the resource being either a provider, collection, or media item. |
Notes |
Using multiple identifiers implies that they have a same-as relationship, i.e. they all identify the same object (e. g. an object may have all of an http-URL, an lsid-URI, and a UUID). |
Term Name: xmp:MetadataDate |
Normative URI |
http://ns.adobe.com/xap/1.0/MetadataDate |
Modified |
2020-01-27 |
Label |
Metadata Date |
|
Required: No -- Repeatable: No |
Definition |
The date and time that any metadata for this resource was last changed. It should be the same as or more recent than xmp:ModifyDate. |
Usage |
Point in time recording when the last modification to metadata (not necessarily the media object itself) occurred. The date and time MUST comply with the World Wide Web Consortium (W3C) datetime practice, https://www.w3.org/TR/NOTE-datetime, which requires that date and time representation correspond to ISO 8601:1998, but with year fields always comprising 4 digits. This makes datetime records compliant with 8601:2004, https://www.iso.org/standard/40874.html. AC datetime values MAY also follow 8601:2004 for ranges by separating two IS0 8601 datetime fields by a solidus ("forward slash", '/'). |
Notes |
This is not dcterms:modified, which refers to the resource itself rather than its metadata. See also the wikipedia IS0 8601 entry, https://en.wikipedia.org/wiki/ISO_8601, for further explanation and examples. |
Term Name: ac:metadataLanguage |
Normative URI |
http://rs.tdwg.org/ac/terms/metadataLanguage |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/metadataLanguage-2020-01-27 |
Label |
Metadata Language |
|
Required: Yes -- Repeatable: No |
Definition |
The URI of the language of description and other metadata (but not necessarily of the image itself) , from the ISO639-2 list of URIs for ISO 3-letter language codes, http://id.loc.gov/vocabulary/iso639-2. |
Usage |
At least one of ac:metadataLanguage and ac:metadataLanguageLiteral MUST be supplied but, when feasible, supplying both might make the metadata more widely useful. They must specify the same language. In case of ambiguity, ac:metadataLanguage prevails. |
Notes |
This is NOT dcterms:language, which is about the resource, not the metadata. Metadata Language is deliberately single-valued, imposing on unstructured serializations a requirement that multi-lingual metadata be represented as separate, complete, metadata records. Audubon Core requires that each record also contains the language-neutral terms. In the absence of this requirement, metadata consumers would need to know which terms are language-neutral and merge these terms from all provided metadataLanguages into a single record. Metadata consumers may re-combine the information based on the dcterms:identifier that identifies the multimedia resource. Nothing in this document would, however, prevent an implementer, e. g. of an XML-Schema representation, from providing a fully hierarchical schema in which language neutral terms occur only a single time, and only the language-specific terms are repeated in a way that unambigously relates them to a metadata language. In RDF it may be a simple repetition of plain literals associated with a language (e.g., xml:lang attribute in RDF/XML). The language attribute would then be required in Audubon Core and would replace ac:metadataLanguage. |
Term Name: ac:metadataLanguageLiteral |
Normative URI |
http://rs.tdwg.org/ac/terms/metadataLanguageLiteral |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/metadataLanguageLiteral-2020-01-27 |
Label |
Metadata Language |
|
Required: Yes -- Repeatable: No |
Definition |
Language of description and other metadata (but not necessarily of the image itself) represented as an ISO639-2 three letter language code. |
Usage |
ISO639-1 two-letter codes are permitted but deprecated. At least one of ac:metadataLanguage and ac:metadataLanguageLiteral MUST be supplied but, when feasible, supplying both might make the metadata more widely useful. They MUST specify the same language. In case of ambiguity, ac:metadataLanguage prevails. |
Notes |
This is NOT dc:language, which is about the resource, not the metadata. Metadata Language is deliberately single-valued, imposing on unstructured serializations a requirement that multi-lingual metadata be represented as separate, complete, metadata records. Audubon Core requires that each record also contains the language-neutral terms. In the absence of this requirement, metadata consumers would need to know which terms are language-neutral and merge these terms from all provided metadataLanguages into a single record. Metadata consumers may re-combine the information based on the dcterms:identifier that identifies the multimedia resource. Nothing in this document would, however, prevent an implementer, e. g. of an XML-Schema representation, from providing a fully hierarchical schema in which language neutral terms occur only a single time, and only the language-specific terms are repeated in a way that unambigously relates them to a metadata language. In RDF it may be a simple repetition of plain literals associated with a language (e.g., xml:lang attribute in RDF/XML). The language attribute would then be required in Audubon Core and would replace ac:metadataLanguage. |
Term Name: dcterms:modified |
Normative URI |
http://purl.org/dc/terms/modified |
Modified |
2020-01-27 |
Term version URI |
http://dublincore.org/usage/terms/history/#modified-003 |
Label |
Modified |
|
Required: No -- Repeatable: Yes |
Definition |
Date on which the resource was changed. |
Usage |
Date that the media resource was altered. The date and time MUST comply with the World Wide Web Consortium (W3C) datetime practice, https://www.w3.org/TR/NOTE-datetime, which requires that date and time representation correspond to ISO 8601:1998, https://www.iso.org/standard/40874.html, but with year fields always comprising 4 digits. This makes datetime records compliant with 8601:2004. AC datetime values MAY also follow 8601:2004 for ranges by separating two IS0 8601 datetime fields by a solidus ("forward slash", '/'). |
Notes |
dcterms:modified permits all modification dates to be recorded, or if only one is recorded, it is assumed to be the latest. See also the wikipedia IS0 8601 entry, https://en.wikipedia.org/wiki/ISO_8601, for further explanation and examples. |
Term Name: ac:providerManagedID |
Normative URI |
http://rs.tdwg.org/ac/terms/providerManagedID |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/providerManagedID-2020-01-27 |
Label |
Provider-managed ID |
|
Required: No -- Repeatable: No |
Definition |
A free-form identifier (a simple number, an alphanumeric code, a URL, etc.) for the resource that is unique and meaningful primarily for the data provider. |
Notes |
Ideally, this would be a globally unique identifier (GUID), but the provider is encouraged to supply any form of identifier that simplifies communications on resources within their project and helps to locate individual data items in the provider's data repositories. It is the provider's decision whether to expose this value or not. |
Term Name: xmp:Rating |
Normative URI |
http://ns.adobe.com/xap/1.0/Rating |
Modified |
2020-01-27 |
Label |
Rating |
|
Required: No -- Repeatable: No |
Definition |
A user-assigned rating for this file. The value shall be -1 or in the range [0..5], where -1 indicates "rejected" and 0 indicates "unrated". If xmp:Rating is not present, a value of 0 should be assumed. |
Usage |
A rating of the media resources, provided by record originators or editors, with '1' (worst) to '5' (best). Anticipated usage is for a typical 'star rating' UI, with the addition of a notion of rejection. Values MAY be decimal numbers in the permitted range. |
Notes |
The origin of the rating is not communicated. It may, e. g., be based on user feedback or on editorial ratings. By "user-assigned" is meant assigned by the originator or editor of the record using the term. |
Term Name: ac:reviewer |
Normative URI |
http://rs.tdwg.org/ac/terms/reviewer |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/reviewer-2020-01-27 |
Label |
Reviewer |
|
Required: No -- Repeatable: Yes |
Definition |
URI for a reviewer. |
Usage |
If present, then resource is peer-reviewed, even if Reviewer Comments is absent or empty. Its presence tells whether an expert in the subject featured in the media has reviewed the media item or collection and approved its metadata description; MUST display a name or the literal "anonymous" (= anonymously reviewed). |
Notes |
Provider is asserting they accept this review as competent. See also ac:reviewerLiteral and the section Namespaces, Prefixes and Term Names in the Audubon Core Term List document for discussion of the rationale for separate terms taking URI values from those taking Literal values where both are possible. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
Term Name: ac:reviewerComments |
Normative URI |
http://rs.tdwg.org/ac/terms/reviewerComments |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/reviewerComments-2020-01-27 |
Label |
Reviewer Comments |
|
Required: No -- Repeatable: Yes |
Definition |
Any comment provided by a reviewer with expertise in the subject, as free-form text. |
Notes |
Reviewer Comments may refer to the resource itself (e. g., asserting a taxon name or location of a biological subject in an image), or to the relation between resource and associated metadata (e. g., asserting that the taxon name given in the metadata is wrong, without asserting a positive identification). There is a separate item "Comments" for text from commenters of unrecorded expertise. |
Term Name: ac:reviewerLiteral |
Normative URI |
http://rs.tdwg.org/ac/terms/reviewerLiteral |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/reviewerLiteral-2020-01-27 |
Label |
Reviewer |
|
Required: No -- Repeatable: Yes |
Definition |
String providing the name of a reviewer. |
Usage |
If present, then resource is peer-reviewed, even if Reviewer Comments is absent or empty. Its presence tells whether an expert in the subject featured in the media has reviewed the media item or collection and approved its metadata description; MUST display a name or the literal "anonymous" (= anonymously reviewed). |
Notes |
Provider is asserting they accept this review as competent. See also ac:reviewer and the section Namespaces, Prefixes and Term Names in the Audubon Core Term List document for discussion of the rationale for separate terms taking URI values from those taking Literal values where both are possible. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
Term Name: ac:subtype |
Normative URI |
http://rs.tdwg.org/ac/terms/subtype |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/subtype-2020-01-27 |
Label |
Subtype |
|
Required: No -- Repeatable: Yes |
Definition |
Any URI may be used that provides for more specialization than the type. Possible values are community-defined. |
Usage |
The subtype term MUST NOT be applied to Collection objects. However, the Description term in the Content Coverage Vocabulary might add further description to a Collection object. The subtype vocabulary MAY be extended by users provided they identify the term by a URI which is not in the ac namespace. Conforming applications MAY choose to ignore controlled values not issued by Audubon Core. |
Notes |
The following list provides examples of strings from which a community could generate URIs for specializations of dcterms:type for use with ac:subtype: Drawing, Painting, Logo, Icon, Illustration, Graphic, Photograph, Animation, Film, SlideShow, DesignPlan, Diagram, Map, MusicalNotation, IdentificationKey, ScannedText, RecordedText, RecordedOrganism, TaxonPage, MultimediaLearningObject, VirtualRealityEnvironment, GlossaryPage. Communities should define the URI in a namespace of their choosing or devising. For example, "http://my.inst.org/namespace/metadata/subtype/SlideShow"). See ac:subtypeLiteral for usage with strings. |
Term Name: ac:subtypeLiteral |
Normative URI |
http://rs.tdwg.org/ac/terms/subtypeLiteral |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/subtypeLiteral-2020-01-27 |
Label |
Subtype |
|
Required: No -- Repeatable: Yes |
Definition |
The subtype should provide more specialization than the type. Possible values are community-defined. |
Usage |
The subtypeLiteral term MUST NOT be applied to Collection objects. However, the Description term in the Content Coverage Vocabulary might add further description to a Collection object. |
Notes |
The following list provides examples of strings upon which a community could base specializations of dc:type for use with ac:subtypeLiteral: Drawing, Painting, Logo, Icon, Illustration, Graphic, Photograph, Animation, Film, SlideShow, DesignPlan, Diagram, Map, MusicalNotation, IdentificationKey, ScannedText, RecordedText, RecordedOrganism, TaxonPage, MultimediaLearningObject, VirtualRealityEnvironment, GlossaryPage. See ac:subtype for usage with URIs. |
Term Name: dcterms:title |
Normative URI |
http://purl.org/dc/terms/title |
Modified |
2020-01-27 |
Term version URI |
http://dublincore.org/usage/terms/history/#titleT-002 |
Label |
Title |
|
Required: No -- Repeatable: No |
Definition |
A name given to the resource. |
Usage |
Concise title, name, or brief descriptive label of institution, resource collection, or individual resource. This field SHOULD include the complete title with all the subtitles, if any. |
Notes |
It is strongly suggested to provide a title. The title facilitates interactions with humans: e.g., it could be used as display text of hyperlinks or to provide a choice of images in a pick list. The title is therefore highly useful and an effort should be made to provide it where it is not already available. When the resource is a collection without an institutional or official name, but with a thematic content, a descriptive title, e. g. "Urban Ants of New England," would be suitable. In individual media resources depicting taxa, the scientific name or names of taxa often form a good title. Common names in addition to or instead of scientific names are also acceptable. Indications of action or roles captured by the media resource, such as predatory acts, are desirable ("Rattlesnake eating deer mouse", "Pollinators of California Native Plants"). |
Term Name: dc:type |
Normative URI |
http://purl.org/dc/elements/1.1/type |
Modified |
2020-01-27 |
Term version URI |
http://dublincore.org/usage/terms/history/#type-006 |
Label |
Type |
|
Required: Yes -- Repeatable: No |
Definition |
The nature or genre of the resource. |
Usage |
The value of dc:type SHOULD be a term name of any term from the DCMI Type Vocabulary, https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#section-7 RECOMMENDED term names for media items are "Collection", "StillImage", "Sound", "MovingImage", "InteractiveResource", and "Text". A Collection MUST be given a value of "Collection". Following the DC recommendations at http://purl.org/dc/dcmitype/Text, images of text SHOULD be given a value of "Text" for dc:type. A value for at least one of dc:type and dcterms:type MUST be supplied in an Audubon Core record but when feasible, supplying both can make the metadata more widely useful. The values of dc:type and dcterms:type SHOULD designate the same type, but in case of ambiguity dcterms:type prevails. |
Notes |
If the resource is a Collection, this term does not identify what types of objects it may contain. See also the entry for dcterms:type in the Audubon Core term list document and see the DCMI FAQ on DC and DCTERMS Namespaces, https://web.archive.org/web/20171126043657/https://github.com/dcmi/repository/blob/master/mediawiki_wiki/FAQ/DC_and_DCTERMS_Namespaces.md, for discussion of the rationale for terms in two namespaces. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
Term Name: dcterms:type |
Normative URI |
http://purl.org/dc/terms/type |
Modified |
2020-01-27 |
Term version URI |
http://dublincore.org/usage/terms/history/#typeT-001 |
Label |
Type |
|
Required: Yes -- Repeatable: No |
Definition |
The nature or genre of the resource. |
Usage |
The value of dcterms:type SHOULD be an IRI of any term from the DCMI Type Vocabulary, https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#section-7 . In text-based systems (e.g. spreadsheets) the value MUST be an IRI with an unabbreviated namespace. Machine-readable systems MAY use any form of the IRI (e.g. compact URIs; CURIEs) that can be determined to be equivalent to the unabbreviated IRI. RECOMMENDED values for media items are those IRIs whose term names are "Collection", "StillImage", "Sound", "MovingImage", "InteractiveResource", and "Text". A Collection MUST be given a value of http://purl.org/dc/dcmitype/Collection. Following the DC recommendations at http://purl.org/dc/dcmitype/Text, images of text SHOULD be given a value of http://purl.org/dc/dcmitype/Text for dcterms:type. A value for at least one of dc:type and dcterms:type MUST be supplied in an Audubon Core record but when feasible, supplying both can make the metadata more widely useful. The values of dc:type and dcterms:type SHOULD designate the same type, but in case of ambiguity dcterms:type prevails. |
Notes |
If the resource is a Collection, this term does not identify what types of objects it may contain. See also the entry for dc:type in the Audubon Core term list document and see the DCMI FAQ on DC and DCTERMS Namespaces, https://web.archive.org/web/20171126043657/https://github.com/dcmi/repository/blob/master/mediawiki_wiki/FAQ/DC_and_DCTERMS_Namespaces.md, for discussion of the rationale for terms in two namespaces. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
7.2 Attribution Vocabulary
Term Name: ac:attributionLinkURL |
Normative URI |
http://rs.tdwg.org/ac/terms/attributionLinkURL |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/attributionLinkURL-2020-01-27 |
Label |
Attribution Link URL |
|
Required: No -- Repeatable: No |
Definition |
The URL where information about ownership, attribution, etc. of the resource may be found. |
Notes |
This URL may be used in creating a clickable logo. Providers should consider making this link as specific and useful to consumers as possible, e. g., linking to a metadata page of the specific image resource rather than to a generic page describing the owner or provider of a resource. |
Term Name: photoshop:Credit |
Normative URI |
http://ns.adobe.com/photoshop/1.0/Credit |
Modified |
2020-01-27 |
Label |
Credit |
|
Required: No -- Repeatable: No |
Definition |
The credit to person(s) and/or organisation(s) required by the supplier of the item to be used when published. This is a free-text field. |
Usage |
free text for "Please cite this as ..." |
Notes |
IPTC also refers to this generically as a "Credit Line" as it is frequently displayed with the media. |
Term Name: xmpRights:Owner |
Normative URI |
http://ns.adobe.com/xap/1.0/rights/Owner |
Modified |
2020-01-27 |
Label |
Copyright Owner |
|
Required: No -- Repeatable: No |
Definition |
A list of legal owners of the resource. |
Usage |
A list of the names of the owners of the copyright. 'Unknown' is an acceptable value, but 'Public Domain' is not. In that case, omit or leave empty xmpRights:Owner, and put 'Public Domain' in the Copyright Statement (dc:rights). Note: Audubon Core guidelines on value format are less restrictive than is specified in the IPTC guidelines. |
Notes |
Some providers use dc:publisher for this purpose, but it seems doubtful that the publisher is by necessity the copyright owner. 'Public Domain' is not an appropriate value because it denotes something that is not under copyright. Except for 'Public Domain' resources, it is strongly urged that this field be supplied. |
Term Name: dc:rights |
Normative URI |
http://purl.org/dc/elements/1.1/rights |
Modified |
2020-01-27 |
Term version URI |
http://dublincore.org/usage/terms/history/#rights-006 |
Label |
Copyright Statement |
|
Required: Yes -- Repeatable: No |
Definition |
Information about rights held in and over the resource. |
Usage |
A full-text, readable copyright statement, as required by the national legislation of the copyright holder. On collections, this applies to all contained objects, unless the object itself has a different statement. Do not place just the name of the copyright holder(s) here! That belongs in a list in the xmpRights:Owner field, which SHOULD be supplied if dc:rights is not 'Public Domain', which is appropriate only if the resource is known to be not under copyright. At least one of dcterms:rights and dc:rights MUST be supplied but, when feasible, supplying both might make the metadata more widely useful. They MUST specify the same rights. |
Notes |
This expresses rights over the media resource, not over the metadata text. In case of ambiguity, dcterms:rights prevails. See also the entry for dcterms:rights in the Audubon Core Term List document and see the DCMI FAQ on DC and DCTERMS Namespaces, https://web.archive.org/web/20171126043657/https://github.com/dcmi/repository/blob/master/mediawiki_wiki/FAQ/DC_and_DCTERMS_Namespaces.md, for discussion of the rationale for terms in two namespaces. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. Examples: "Copyright XY 2008, all rights reserved", "© 2008 XY Museum", "Public Domain.", "Copyright unknown." |
Term Name: dc:source |
Normative URI |
http://purl.org/dc/elements/1.1/source |
Modified |
2020-01-27 |
Term version URI |
http://dublincore.org/usage/terms/history/#source-006 |
Label |
Published Source |
|
Required: No -- Repeatable: Yes |
Definition |
A related resource from which the described resource is derived. |
Usage |
A string providing an identifiable source from which the described resources was derived. |
Notes |
If the resource was digitized from a non-digital resource, or was also previously published in a digital or printed publication, this describes the original. Do not put generally "related" publications in here. This field normally contains a free-form text description. If a URI is available it should be provided in dcterms:source. Can be repeatable if a montage of images. Information about further provenance beyond the ultimate source should be put in the derivedFrom attribute. See also the entry for dcterms:source in the Audubon Core term list document and see the DCMI FAQ on DC and DCTERMS Namespaces, https://web.archive.org/web/20171126043657/https://github.com/dcmi/repository/blob/master/mediawiki_wiki/FAQ/DC_and_DCTERMS_Namespaces.md, for discussion of the rationale for terms in two namespaces. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions |
Term Name: dcterms:source |
Normative URI |
http://purl.org/dc/terms/source |
Modified |
2020-01-27 |
Term version URI |
http://dublincore.org/usage/terms/history/#sourceT-001 |
Label |
Published Source |
|
Required: No -- Repeatable: Yes |
Definition |
A related resource from which the described resource is derived. |
Usage |
URI for an identifiable source from which the described resources was derived. |
Notes |
If the resource was digitized from a non-digital resource, or was also previously published in a digital or printed publication, this describes the original. If a string is required for this, use dc:source. Do not put generally "related" publications in here. A URI that can be resolved and dereferenced to provide a description of the source resource may also be used here. For example, "http://www.loc.gov/pictures/item/fsa1998021539/PP/" is the address of a web page that provides a description the original negative of a famous picture by the photographer Dorothea Lange and so would be an appropriate value of dcterms:source. The term may be repeatable if a montage of images. Information about further provenance beyond the ultimate source should be put in the derivedFrom attribute. See also the entry for dc:source in the Audubon Core term list document and see the DCMI FAQ on DC and DCTERMS Namespaces, https://web.archive.org/web/20171126043657/https://github.com/dcmi/repository/blob/master/mediawiki_wiki/FAQ/DC_and_DCTERMS_Namespaces.md, for discussion of the rationale for terms in two namespaces. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
Term Name: xmpRights:UsageTerms |
Normative URI |
http://ns.adobe.com/xap/1.0/rights/UsageTerms |
Modified |
2020-01-27 |
Label |
License Terms |
|
Required: No -- Repeatable: No |
Definition |
A collection of text instructions on how a resource can be legally used, given in a variety of languages. |
Usage |
The license statement defining how resources might be used. Information on a collection applies to all contained objects unless the object has a different statement. Where different quality variants (e. g. different resolutions of images) are published under different licenses, the AC term "Licensing Exception Statement" supports variant-specific licenses. Note that the medium or low resolution levels of the same image might be available under open access licenses. |
Notes |
Example: "Available under Creative Commons BY-SA 3.0 license". This also describes the commercial availability of items. Buying an identification tool or media resource is essentially the purchase of an individual license. Examples for such License statements: "Available through bookstores" for a commercially published CD, and "Individual licenses available for purchase" for a high-resolution image. In general, this term determines the default licensing for the media. License terms specific to variants or representations of the media resource (e.g., different resolutions) are dealt within the section on Service Access Point Vocabulary |
Term Name: xmpRights:WebStatement |
Normative URI |
http://ns.adobe.com/xap/1.0/rights/WebStatement |
Modified |
2020-01-27 |
Label |
License URL |
|
Required: No -- Repeatable: No |
Definition |
A Web URL for a statement of the ownership and usage rights for this resource. |
Usage |
A URL defining or further elaborating on the license statement (e. g., a web page explaining the precise terms of use). Where different quality variants (e. g. different resolutions of images) are published under different licenses, the AC term "Licensing Exception Statement" supports variant-specific licenses |
Notes |
The value of this field may provide a complete definition of the terms of use. For Creative Commons, the appropriate value is the URL of the defining Web page for the license. Example: http://creativecommons.org/licenses/by-nc-sa/3.0/us/.. |
7.3 Agents Vocabulary
Term Name: ac:metadataCreator |
Normative URI |
http://rs.tdwg.org/ac/terms/metadataCreator |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/metadataCreator-2020-01-27 |
Label |
Metadata Creator |
|
Required: No -- Repeatable: Yes |
Definition |
A URI representing a person or organization originally creating the resource metadata record. |
Notes |
See also the entry for ac:metadataCreatorLiteral and the section Namespaces, Prefixes and Term Names in the Audubon Core Term List document for discussion of the rationale for separate terms taking URI values from those taking Literal values where both are possible. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
Term Name: ac:metadataCreatorLiteral |
Normative URI |
http://rs.tdwg.org/ac/terms/metadataCreatorLiteral |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/metadataCreatorLiteral-2020-01-27 |
Label |
Metadata Creator |
|
Required: No -- Repeatable: Yes |
Definition |
Name of the person or organization originally creating the resource metadata record. |
Notes |
See also the entry for ac:metadataCreator and the section Namespaces, Prefixes and Term Names in the Audubon Core Term List document for discussion of the rationale for separate terms taking URI values from those taking Literal values where both are possible. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
Term Name: ac:metadataProvider |
Normative URI |
http://rs.tdwg.org/ac/terms/metadataProvider |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/metadataProvider-2020-01-27 |
Label |
Metadata Provider |
|
Required: No -- Repeatable: Yes |
Definition |
URI of person or organization originally responsible for providing the resource metadata record. |
Notes |
Media resources and their metadata may be served from different institutions, e. g. in the case of aggregators adding user annotations, taxon identifications, or ratings. Compare Provider. See also the entry for ac:metadataProviderLiteral and the section Namespaces, Prefixes and Term Names in the Audubon Core Term List document for discussion of the rationale for separate terms taking URI values from those taking Literal values where both are possible. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
Term Name: ac:metadataProviderLiteral |
Normative URI |
http://rs.tdwg.org/ac/terms/metadataProviderLiteral |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/metadataProviderLiteral-2020-01-27 |
Label |
Metadata Provider |
|
Required: No -- Repeatable: Yes |
Definition |
Name of the person or organization originally responsible for providing the resource metadata record. |
Notes |
Media resources and their metadata may be served from different institutions, e. g. in the case of aggregators adding user annotations, taxon identifications, or ratings. Compare Provider. See also the entry for ac:metadataProvider in this document and the section Namespaces, Prefixes and Term Names for discussion of the rationale for separate terms taking URI values from those taking Literal values where both are possible. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
Term Name: ac:provider |
Normative URI |
http://rs.tdwg.org/ac/terms/provider |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/provider-2020-01-27 |
Label |
Provider |
|
Required: No -- Repeatable: No |
Definition |
URI for person or organization responsible for presenting the media resource. |
Usage |
If no separate Metadata Provider is given, this also attributes the metadata. |
Notes |
Media resources and their metadata may be served from different institutions, e. g. in the case of aggregators adding user annotations, taxon identifications, or ratings. See also the entry for ac:providerLiteral and the section Namespaces, Prefixes and Term Names in the Audubon Core Term List document for discussion of the rationale for separate terms taking URI values from those taking Literal values where both are possible. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
Term Name: ac:providerLiteral |
Normative URI |
http://rs.tdwg.org/ac/terms/providerLiteral |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/providerLiteral-2020-01-27 |
Label |
Provider |
|
Required: No -- Repeatable: No |
Definition |
Name of the person or organization responsible for presenting the media resource. |
Usage |
If no separate Metadata Provider is given, this also attributes the metadata. |
Notes |
Media resources and their metadata may be served from different institutions, e. g. in the case of aggregators adding user annotations, taxon identifications, or ratings. See also the entry for ac:provider and the section Namespaces, Prefixes and Term Names in the Audubon Core Term List document for discussion of the rationale for separate terms taking URI values from those taking Literal values where both are possible. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
7.4 Content Coverage Vocabulary
Term Name: ac:caption |
Normative URI |
http://rs.tdwg.org/ac/terms/caption |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/caption-2020-01-27 |
Label |
Caption |
|
Required: No -- Repeatable: No |
Definition |
As alternative or in addition to description, a caption is free-form text to be displayed together with (rather than instead of) a resource that is suitable for captions (especially images). |
Notes |
If both description and caption are present in the metadata, a description is typically displayed instead of the resource, a caption together with the resource. Often only one of description or caption is present; choose the term most appropriate for your metadata. |
Term Name: Iptc4xmpExt:CVterm |
Normative URI |
http://iptc.org/std/Iptc4xmpExt/2008-02-29/CVterm |
Modified |
2020-01-27 |
Label |
Subject Category |
|
Required: No -- Repeatable: Yes |
Definition |
A term to describe the content of the image by a value from a Controlled Vocabulary. |
Usage |
Controlled vocabulary of subjects to support broad classification of media items. Terms from various controlled vocabularies may be used. AC-recommended vocabularies are preferred and MAY be unqualified literals (not a full URI). For terms from other vocabularies either a precise URI SHOULD be used, or, as long as all unqualified terms in all vocabularies are unique, metadata SHOULD provide the source vocabularies using the Subject Category Vocabulary term. The value SHOULD be a string, whose text can also be in the form of a URL. These guidelines on value format are less restrictive than is specified by the IPTC guidelines. |
Notes |
Recommended sets include: the NASA Global Change Master Directory (GCMD; http://gcmd.nasa.gov/), Subject Categories defined in Key to Nature (K2N; http://www.keytonature.eu/wiki/Subject_Category), the BioComplexity Thesaurus; https://www2.usgs.gov/core_science_systems/csas/biocomplexity_thesaurus/, the Description Type GBIF Vocabulary; http://rs.gbif.org/vocabulary/gbif/description_type.xml, the TDWG Species Profile Model; http://rs.tdwg.org/ontology/voc/SPMInfoItems.rdf, the Plinian Core; https://github.com/tdwg/PlinianCore/wiki, the European Environmental Agency GEneral Multilingual Environmental Thesaurus (GEMET; http://www.eionet.europa.eu/gemet), and the Long Term Ecological Research Network Controlled Vocabulary (LTER; http://vocab.lternet.edu/). The vocabulary may include major taxonomic groups (such as "vertebrates" or "fungi") or ecosystem terms ("savannah", "temperate rain forest", "forest fires", "aquatic vertebrates"). Other formal classifications (published in print or online) such as habitat, fuel, invasive species, agroproductivity, fisheries, migratory species etc. are also suitable. |
Term Name: dcterms:description |
Normative URI |
http://purl.org/dc/terms/description |
Modified |
2020-01-27 |
Term version URI |
http://dublincore.org/usage/terms/history/#descriptionT-001 |
Label |
Description |
|
Required: No -- Repeatable: No |
Definition |
An account of the resource. |
Usage |
Description of collection or individual resource, containing the Who, What, When, Where and Why as free-form text. |
Notes |
This property optionally allows the presentation of detailed information and will in most cases be shown together with the resource title. If both a description and a caption are present in the metadata, a description is typically displayed instead of the resource, whereas a caption is displayed together with the resource. The description should aim to be a good proxy for the underlying media resource in cases where only text can be shown, whereas the caption may only make sense when shown together with the media. Often only one of description or caption is present; choose the term most appropriate for your metadata. It is the role of implementers of an AC concrete representation (e.g., an XML Schema, an RDF representation, etc.) to decide and document how formatting advice will be represented in descriptions serialized according to such representations. |
Term Name: dcterms:language |
Normative URI |
http://purl.org/dc/terms/language |
Modified |
2020-01-27 |
Term version URI |
http://dublincore.org/usage/terms/history/#languageT-001 |
Label |
Language |
|
Required: No -- Repeatable: Yes |
Definition |
A language of the resource. |
Usage |
URI from the ISO639-2 list of URIs for ISO 3-letter language codes, http://id.loc.gov/vocabulary/iso639-2. |
Notes |
An image may contain language such as superimposed labels. If an image is of a natural scene or organism, without any language included, the resource is language-neutral with URI http://id.loc.gov/vocabulary/iso639-2/zxx corresponding to ISO ISO639-2 code "zxx". Resources with present but unknown language are to be coded as undetermined, with URI http://id.loc.gov/vocabulary/iso639-2/und corresponding to ISO639-2 code "und". Regional dialects or other special cases should conform to the ISO639-5 Alpha-3 Code for Language Families and Groups, http://id.loc.gov/vocabulary/iso639-5.html, where possible or the IETF Best Practices for Tags Identifying Languages, https://tools.ietf.org/html/rfc5646, where not. See also the entry for dc:language in the Audubon Core term list document and see the DCMI FAQ on DC and DCTERMS Namespaces, https://web.archive.org/web/20171126043657/https://github.com/dcmi/repository/blob/master/mediawiki_wiki/FAQ/DC_and_DCTERMS_Namespaces.md, for discussion of the rationale for terms in two namespaces. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
Term Name: ac:physicalSetting |
Normative URI |
http://rs.tdwg.org/ac/terms/physicalSetting |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/physicalSetting-2020-01-27 |
Label |
Physical Setting |
|
Required: No -- Repeatable: Yes |
Definition |
The setting of the content represented in media such as images, sounds, and movies if the provider deems them relevant. |
Usage |
Constrained vocabulary of: "Natural" = Object in its natural setting of the object (e. g. living organisms in their natural environment); "Artificial" = Object in an artificial environment (e. g. living organisms in an artificial environment such as a zoo, garden, greenhouse, or laboratory); "Edited" = Human media editing of a natural setting or media acquisition with a separate media background such as a photographic backdrop. |
Notes |
Multiple values may be needed for movies or montages. See also ac:resourceCreationTechnique which should be used to describe any modifications to the resource itself. Communities of practice should form best practices for the use of these controlled terms. |
Term Name: ac:subjectCategoryVocabulary |
Normative URI |
http://rs.tdwg.org/ac/terms/subjectCategoryVocabulary |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/subjectCategoryVocabulary-2020-01-27 |
Label |
Subject Category Vocabulary |
|
Required: No -- Repeatable: Yes |
Definition |
Any vocabulary or formal classification from which terms in the Subject Category have been drawn. |
Notes |
The AC recommended vocabularies do not need to be cited here. There is no required linkage between individual Subject Category terms and the vocabulary; the mechanism is intended to support discovery of the normative URI for a term, but not guarantee it. |
Term Name: ac:tag |
Normative URI |
http://rs.tdwg.org/ac/terms/tag |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/tag-2020-01-27 |
Label |
Tag |
|
Required: No -- Repeatable: Yes |
Definition |
General keywords or tags. |
Notes |
Tags may be multi-worded phrases. Where scientific names, common names, geographic locations, etc. are separable, those should go into the more specific coverage metadata items provided further below. Examples: "flower diagram". Character or part keywords like "leaf", or "flower color" are especially desirable. |
7.5 Geography Vocabulary
Note that dwc:locality may be used, but as applied to media this term may be ambiguous as to whether it applies to the location depicted or the location at which the media was created. When disambiguating information is available, it is better to use the terms Location Shown and Location Created. The latter is in the Resource Creation Vocabulary.
Location Created and Location Shown are separated in the current version of IPTC, and the Metadata Working Group (Metadata Working Group Guidelines for Handling Image Metadata, Version 2.0, November 2010) also recommends this. We follow this below in order to support the expected future increase of automatic GPS-based coordinate recording. As a special case, the AC group recommends to change the semantics of Location Shown in the case of biodiversity specimens, where the original location may differ from the current location at which the specimen is held in a collection. In this case, Location Shown should exclusively refer to the location where a specimen was originally collected (gathering or sampling location). Use Location Created to express the location where the resource was created (a specimen was digitized).
Term Name: Iptc4xmpExt:City |
Normative URI |
http://iptc.org/std/Iptc4xmpExt/2008-02-29/City |
Modified |
2020-01-27 |
Label |
City or Place Name |
|
Required: No -- Repeatable: Yes |
Definition |
Name of the city of a location. This element is at the fourth level of a top-down geographical hierarchy. |
Usage |
Optionally, the name of a city or place commonly found in gazetteers (such as a mountain or national park) in which the subjects (e. g., species, habitats, or events) were located. |
Term Name: dwc:continent |
Normative URI |
http://rs.tdwg.org/dwc/terms/continent |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/continent-2017-10-06 |
Label |
Continent |
|
Required: No -- Repeatable: Yes |
Definition |
The name of the continent in which the Location occurs. |
Notes |
Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names. |
Examples |
`Africa`, `Antarctica`, `Asia`, `Europe`, `North America`, `Oceania`, `South America` |
Term Name: dwc:coordinateUncertaintyInMeters |
Normative URI |
http://rs.tdwg.org/dwc/terms/coordinateUncertaintyInMeters |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/coordinateUncertaintyInMeters-2017-10-06 |
Label |
Coordinate Uncertainty In Meters |
|
Required: No -- Repeatable: Yes |
Definition |
The horizontal distance (in meters) from the given decimalLatitude and decimalLongitude describing the smallest circle containing the whole of the Location. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Zero is not a valid value for this term. |
Examples |
`30` (reasonable lower limit of a GPS reading under good conditions if the actual precision was not recorded at the time). `71` (uncertainty for a UTM coordinate having 100 meter precision and a known spatial reference system). |
Term Name: dwc:country |
Normative URI |
http://rs.tdwg.org/dwc/terms/country |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/country-2017-10-06 |
Label |
Country |
|
Required: No -- Repeatable: Yes |
Definition |
The name of the country or major administrative unit in which the Location occurs. |
Notes |
Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names. |
Examples |
`Denmark`, `Colombia`, `España` |
Term Name: Iptc4xmpExt:CountryCode |
Normative URI |
http://iptc.org/std/Iptc4xmpExt/2008-02-29/CountryCode |
Modified |
2020-01-27 |
Label |
Country Code |
|
Required: No -- Repeatable: Yes |
Definition |
The ISO code of a country of a location. This element is at the second level of a top-down geographical hierarchy. |
Usage |
The geographic location of the specific entity or entities documented by the media item, expressed through a constrained vocabulary of countries using 2-letter ISO 3166-1 country code (e. g. "IT, SI"). |
Notes |
Accepted exceptions to be used instead of ISO codes are: "Global", "Marine", "Europe", "N-America", "C-America", "S-America", "Africa", "Asia", "Oceania", ATA = "Antarctica", XEU = "European Union", XAR = "Arctic", "ZZZ" = "Unknown country" (3 letter abbreviations from IPTC codes). |
Term Name: dwc:county |
Normative URI |
http://rs.tdwg.org/dwc/terms/county |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/county-2017-10-06 |
Label |
County |
|
Required: No -- Repeatable: Yes |
Definition |
The full, unabbreviated name of the next smaller administrative region than stateProvince (county, shire, department, etc.) in which the Location occurs. |
Notes |
Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names. |
Examples |
`Missoula`, `Los Lagos`, `Mataró` |
Term Name: dwc:decimalLatitude |
Normative URI |
http://rs.tdwg.org/dwc/terms/decimalLatitude |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/decimalLatitude-2017-10-06 |
Label |
Decimal Latitude |
|
Required: No -- Repeatable: Yes |
Definition |
The geographic latitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are north of the Equator, negative values are south of it. Legal values lie between -90 and 90, inclusive. |
Examples |
`-41.0983423` |
Term Name: dwc:decimalLongitude |
Normative URI |
http://rs.tdwg.org/dwc/terms/decimalLongitude |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/decimalLongitude-2017-10-06 |
Label |
Decimal Longitude |
|
Required: No -- Repeatable: Yes |
Definition |
The geographic longitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are east of the Greenwich Meridian, negative values are west of it. Legal values lie between -180 and 180, inclusive. |
Examples |
`-121.1761111` |
Term Name: dwc:footprintSpatialFit |
Normative URI |
http://rs.tdwg.org/dwc/terms/footprintSpatialFit |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/footprintSpatialFit-2020-08-20 |
Label |
Footprint Spatial Fit |
|
Required: No -- Repeatable: Yes |
Definition |
The ratio of the area of the footprint (footprintWKT) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given footprint does not completely contain the original representation. The footprintSpatialFit is undefined (and should be left empty) if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the footprintSpatialFit is 1. |
Notes |
Detailed explanations with graphical examples can be found in the Georeferencing Best Practices, Chapman and Wieczorek, 2020 (https://doi.org/10.15468/doc-gg7h-s853). |
Examples |
`0`, `1`, `1.5708` |
Term Name: dwc:footprintSRS |
Normative URI |
http://rs.tdwg.org/dwc/terms/footprintSRS |
Modified |
2020-08-23 |
Label |
Footprint SRS |
|
Required: No -- Repeatable: Yes |
Definition |
A Well-Known Text (WKT) representation of the Spatial Reference System (SRS) for the footprintWKT of the Location. Do not use this term to describe the SRS of the decimalLatitude and decimalLongitude, even if it is the same as for the footprintWKT - use the geodeticDatum instead. |
Examples |
`GEOGCS["GCS_WGS_1984", DATUM["D_WGS_1984", SPHEROID["WGS_1984",6378137,298.257223563]], PRIMEM["Greenwich",0], UNIT["Degree",0.0174532925199433]]` (WKT for the standard WGS84 Spatial Reference System EPSG:4326). |
Term Name: dwc:footprintWKT |
Normative URI |
http://rs.tdwg.org/dwc/terms/footprintWKT |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/footprintWKT-2017-10-06 |
Label |
Footprint WKT |
|
Required: No -- Repeatable: Yes |
Definition |
A Well-Known Text (WKT) representation of the shape (footprint, geometry) that defines the Location. A Location may have both a point-radius representation (see decimalLatitude) and a footprint representation, and they may differ from each other. |
Examples |
`POLYGON ((10 20, 11 20, 11 21, 10 21, 10 20))` (the one-degree bounding box with opposite corners at longitude=10, latitude=20 and longitude=11, latitude=21) |
Term Name: dwc:geodeticDatum |
Normative URI |
http://rs.tdwg.org/dwc/terms/geodeticDatum |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/geodeticDatum-2017-10-06 |
Label |
Geodetic Datum |
|
Required: No -- Repeatable: Yes |
Definition |
The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which the geographic coordinates given in decimalLatitude and decimalLongitude as based. |
Notes |
Recommended best practice is to use the EPSG code of the SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value `unknown`. |
Examples |
`EPSG:4326`, `WGS84`, `NAD27`, `Campo Inchauspe`, `European 1950`, `Clarke 1866`, `unknown` |
Term Name: dwc:georeferencedBy |
Normative URI |
http://rs.tdwg.org/dwc/terms/georeferencedBy |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/georeferencedBy-2017-10-06 |
Label |
Georeferenced By |
|
Required: No -- Repeatable: Yes |
Definition |
A list (concatenated and separated) of names of people, groups, or organizations who determined the georeference (spatial representation) for the Location. |
Notes |
Recommended best practice is to separate the values in a list with space vertical bar space (` | `). |
Examples |
`Brad Millen (ROM)`, `Kristina Yamamoto | Janet Fang` |
Term Name: dwc:georeferenceSources |
Normative URI |
http://rs.tdwg.org/dwc/terms/georeferenceSources |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/georeferenceSources-2017-10-06 |
Label |
Georeference Sources |
|
Required: No -- Repeatable: Yes |
Definition |
A list (concatenated and separated) of maps, gazetteers, or other resources used to georeference the Location, described specifically enough to allow anyone in the future to use the same resources. |
Notes |
Recommended best practice is to separate the values in a list with space vertical bar space (` | `). |
Examples |
`https://www.geonames.org/`, `USGS 1:24000 Florence Montana Quad | Terrametrics 2008 on Google Earth`, `GeoLocate` |
Term Name: dwc:higherGeography |
Normative URI |
http://rs.tdwg.org/dwc/terms/higherGeography |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/higherGeography-2017-10-06 |
Label |
Higher Geography |
|
Required: No -- Repeatable: Yes |
Definition |
A list (concatenated and separated) of geographic names less specific than the information captured in the locality term. |
Notes |
Recommended best practice is to separate the values in a list with space vertical bar space (` | `), with terms in order from least specific to most specific. |
Examples |
`North Atlantic Ocean`. `South America | Argentina | Patagonia | Parque Nacional Nahuel Huapi | Neuquén | Los Lagos` (with accompanying values `South America` in continent, `Argentina` in country, `Neuquén` in stateProvince, and `Los Lagos` in county. |
Term Name: dwc:higherGeographyID |
Normative URI |
http://rs.tdwg.org/dwc/terms/higherGeographyID |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/higherGeographyID-2017-10-06 |
Label |
Higher Geography ID |
|
Required: No -- Repeatable: Yes |
Definition |
An identifier for the geographic region within which the Location occurred. |
Notes |
Recommended best practice is to use a persistent identifier from a controlled vocabulary such as the Getty Thesaurus of Geographic Names. |
Examples |
`http://vocab.getty.edu/tgn/1002002` (Antártida e Islas del Atlántico Sur, Territorio Nacional de la Tierra del Fuego, Argentina). |
Term Name: dwc:island |
Normative URI |
http://rs.tdwg.org/dwc/terms/island |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/island-2017-10-06 |
Label |
Island |
|
Required: No -- Repeatable: Yes |
Definition |
The name of the island on or near which the Location occurs. |
Notes |
Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names. |
Examples |
`Nosy Be`, `Bikini Atoll`, `Vancouver`, `Viti Levu`, `Zanzibar` |
Term Name: dwc:locality |
Normative URI |
http://rs.tdwg.org/dwc/terms/locality |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/locality-2017-10-06 |
Label |
Locality |
|
Required: No -- Repeatable: Yes |
Definition |
The specific description of the place. Less specific geographic information can be provided in other geographic terms (higherGeography, continent, country, stateProvince, county, municipality, waterBody, island, islandGroup). This term may contain information modified from the original to correct perceived errors or standardize the description. |
Examples |
`Bariloche, 25 km NNE via Ruta Nacional 40 (=Ruta 237)`. |
Term Name: dwc:locationID |
Normative URI |
http://rs.tdwg.org/dwc/terms/locationID |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/locationID-2017-10-06 |
Label |
Location ID |
|
Required: No -- Repeatable: Yes |
Definition |
An identifier for the set of location information (data associated with dcterms:Location). May be a global unique identifier or an identifier specific to the data set. |
Examples |
`https://opencontext.org/subjects/768A875F-E205-4D0B-DE55-BAB7598D0FD1` |
Term Name: Iptc4xmpExt:LocationShown |
Normative URI |
http://iptc.org/std/Iptc4xmpExt/2008-02-29/LocationShown |
Modified |
2020-01-27 |
Label |
Location Shown |
|
Required: No -- Repeatable: Yes |
Definition |
A location the content of the item is about. For photos that is a location shown in the image. |
Usage |
The location that is depicted the media content, irrespective of the location at which the resource has been created. |
Term Name: dwc:maximumDistanceAboveSurfaceInMeters |
Normative URI |
http://rs.tdwg.org/dwc/terms/maximumDistanceAboveSurfaceInMeters |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/maximumDistanceAboveSurfaceInMeters-2017-10-06 |
Label |
Maximum Distance Above Surface In Meters |
|
Required: No -- Repeatable: Yes |
Definition |
The greater distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation. |
Examples |
`-1.5` (below the surface). `4.2` (above the surface). For a 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation: verbatimElevation: `300m` minimumElevationInMeters: `300`, maximumElevationInMeters: `300`, verbatimDepth: `20m`, minimumDepthInMeters: `20`, maximumDepthInMeters: `20`, minimumDistanceAboveSurfaceInMeters: `0`, maximumDistanceAboveSurfaceInMeters: `-1.5`. |
Term Name: dwc:minimumDistanceAboveSurfaceInMeters |
Normative URI |
http://rs.tdwg.org/dwc/terms/minimumDistanceAboveSurfaceInMeters |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/minimumDistanceAboveSurfaceInMeters-2017-10-06 |
Label |
Minimum Distance Above Surface In Meters |
|
Required: No -- Repeatable: Yes |
Definition |
The lesser distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation. |
Examples |
`-1.5` (below the surface). `4.2` (above the surface). For a 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation: verbatimElevation: `300m` minimumElevationInMeters: `300`, maximumElevationInMeters: `300`, verbatimDepth: `20m`, minimumDepthInMeters: `20`, maximumDepthInMeters: `20`, minimumDistanceAboveSurfaceInMeters: `0`, maximumDistanceAboveSurfaceInMeters: `-1.5`. |
Term Name: dwc:municipality |
Normative URI |
http://rs.tdwg.org/dwc/terms/municipality |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/municipality-2017-10-06 |
Label |
Municipality |
|
Required: No -- Repeatable: Yes |
Definition |
The full, unabbreviated name of the next smaller administrative region than county (city, municipality, etc.) in which the Location occurs. Do not use this term for a nearby named place that does not contain the actual location. |
Notes |
Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names. |
Examples |
`Holzminden`, `Araçatuba`, `Ga-Segonyana` |
Term Name: dwc:pointRadiusSpatialFit |
Normative URI |
http://rs.tdwg.org/dwc/terms/pointRadiusSpatialFit |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/pointRadiusSpatialFit-2020-08-20 |
Label |
Point Radius Spatial Fit |
|
Required: No -- Repeatable: Yes |
Definition |
The ratio of the area of the point-radius (decimalLatitude, decimalLongitude, coordinateUncertaintyInMeters) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given point-radius does not completely contain the original representation. The pointRadiusSpatialFit is undefined (and should be left empty) if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the pointRadiusSpatialFit is 1. |
Notes |
Detailed explanations with graphical examples can be found in the Georeferencing Best Practices, Chapman and Wieczorek, 2020 (https://doi.org/10.15468/doc-gg7h-s853). |
Examples |
`0`, `1`, `1.5708` |
Term Name: Iptc4xmpExt:ProvinceState |
Normative URI |
http://iptc.org/std/Iptc4xmpExt/2008-02-29/ProvinceState |
Modified |
2020-01-27 |
Label |
Province or State |
|
Required: No -- Repeatable: Yes |
Definition |
The name of a subregion of a country - a province or state - of a location. This element is at the third level of a top-down geographical hierarchy. |
Usage |
OPTIONALLY, the geographic unit immediately below the country level (individual states in federal countries, provinces, or other administrative units) in which the subject of the media resource (e. g., species, habitats, or events) were located (if such information is available in separate fields). |
Term Name: dwc:stateProvince |
Normative URI |
http://rs.tdwg.org/dwc/terms/stateProvince |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/stateProvince-2017-10-06 |
Label |
State Province |
|
Required: No -- Repeatable: Yes |
Definition |
The name of the next smaller administrative region than country (state, province, canton, department, region, etc.) in which the Location occurs. |
Notes |
Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names. |
Examples |
`Montana`, `Minas Gerais`, `Córdoba` |
Term Name: Iptc4xmpExt:Sublocation |
Normative URI |
http://iptc.org/std/Iptc4xmpExt/2008-02-29/Sublocation |
Modified |
2020-01-27 |
Label |
Sublocation |
|
Required: No -- Repeatable: Yes |
Definition |
Name of a sublocation. This sublocation name could either be the name of a sublocation to a city or the name of a well known location or (natural) monument outside a city. In the sense of a sublocation to a city this element is at the fifth level of a top-down geographical hierarchy. |
Usage |
Free-form text location details of the location of the subjects, down to the village, forest, or geographic feature etc., below the Iptc4xmpExt:City place name, especially information that could not be found in a gazetteer. |
Term Name: dwc:verbatimCoordinates |
Normative URI |
http://rs.tdwg.org/dwc/terms/verbatimCoordinates |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/verbatimCoordinates-2017-10-06 |
Label |
Verbatim Coordinates |
|
Required: No -- Repeatable: Yes |
Definition |
The verbatim original spatial coordinates of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem. |
Examples |
`41 05 54S 121 05 34W`, `17T 630000 4833400` |
Term Name: dwc:verbatimSRS |
Normative URI |
http://rs.tdwg.org/dwc/terms/verbatimSRS |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/verbatimSRS-2017-10-06 |
Label |
Verbatim SRS |
|
Required: No -- Repeatable: Yes |
Definition |
The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which coordinates given in verbatimLatitude and verbatimLongitude, or verbatimCoordinates are based. |
Notes |
Recommended best practice is to use the EPSG code of the SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value `unknown`. |
Examples |
`unknown`, `EPSG:4326`, `WGS84`, `NAD27`, `Campo Inchauspe`, `European 1950`, `Clarke 1866` |
Term Name: dwc:waterBody |
Normative URI |
http://rs.tdwg.org/dwc/terms/waterBody |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/waterBody-2017-10-06 |
Label |
Water Body |
|
Required: No -- Repeatable: Yes |
Definition |
The name of the water body in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names. |
Notes |
Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names. |
Examples |
`Indian Ocean`, `Baltic Sea`, `Hudson River`, `Lago Nahuel Huapi` |
Term Name: Iptc4xmpExt:WorldRegion |
Normative URI |
http://iptc.org/std/Iptc4xmpExt/2008-02-29/WorldRegion |
Modified |
2020-01-27 |
Label |
World Region |
|
Required: No -- Repeatable: Yes |
Definition |
The name of a world region of a location. This element is at the first (topI) level of a topdown geographical hierarchy. |
Usage |
Name of a world region in some high level classification, such as names for continents, waterbodies, or island groups, whichever is most appropriate. The terms preferably are derived from a controlled vocabulary. |
Notes |
The equivalent DarwinCore fields here forces primary metadata providers to classify world region terms into separate properties for "continent", "waterbody", "islandGroup". By contrast, the Iptc4xmpExt vocabulary only specifies that a World Region is something at the top of a hierarchy of locations. |
7.6 Temporal Coverage Vocabulary
Term Name: xmp:CreateDate |
Normative URI |
http://ns.adobe.com/xap/1.0/CreateDate |
Modified |
2020-01-27 |
Label |
Original Date and Time |
|
Required: No -- Repeatable: No |
Definition |
The date and time the resource was created. For a digital file, this need not match a file-system creation time. For a freshly created resource, it should be close to that time, modulo the time taken to write the file. Later file transfer, copying, and so on, can make the file-system time arbitrarily different. |
Usage |
The date of the creation of the original resource from which the digital media was derived or created. The date and time MUST comply with the World Wide Web Consortium (W3C) datetime practice, https://www.w3.org/TR/NOTE-datetime, which requires that date and time representation correspond to ISO 8601:1998, but with year fields always comprising 4 digits. This makes datetime records compliant with 8601:2004, https://www.iso.org/standard/40874.html. AC datetime values MAY also follow 8601:2004 for ranges by separating two IS0 8601 datetime fields by a solidus ("forward slash", '/'). |
Notes |
What constitutes "original" is determined by the metadata author. Example: Digitization of a photographic slide of a map would normally give the date at which the map was created; however a photographic work of art including the same map as its content may give the date of the original photographic exposure. Imprecise or unknown dates can be represented as ISO dates or ranges. Compare also Date and Time Digitized in the Resource Creation Vocabulary. See also the wikipedia IS0 8601 entry, https://en.wikipedia.org/wiki/ISO_8601, for further explanation and examples. |
Term Name: dcterms:temporal |
Normative URI |
http://purl.org/dc/terms/temporal |
Modified |
2020-01-27 |
Term version URI |
http://dublincore.org/usage/terms/history/#temporal-003 |
Label |
Temporal Coverage |
|
Required: No -- Repeatable: No |
Definition |
Temporal characteristics of the resource. |
Usage |
The coverage (extent or scope) of the content of the resource. Temporal coverage will typically include temporal period (a period label, date, or date range) to which the subjects of the media or media collection relate. If dates are mentioned, they SHOULD follow ISO 8601. When the resource is a Collection, this refers to the temporal coverage of the collection. Following dcterms:temporal, the value MUST be a URI. |
Notes |
See the DCMI User Guide dcterms:temporal entry, https://github.com/dcmi/repository/blob/master/mediawiki_wiki/User_Guide/Publishing_Metadata.md#dctermstemporal, for an example. dc:coverage may be used for string values of temporal coverage, but use the Geography Vocabulary for geographic coverage. String examples for use with dc:coverage include "Jurassic", "Elizabethan", "Spring, 1957". 2008-01-01/2008-06-30. If the resource is video or audio, it refers to the time span, if any, depicted by the resource. For live-media this is closely related to Original Date and Time (Example: the time depicted by a time-lapse video file of organism development), but for media with fictional content it is not. |
7.7 Taxonomic Coverage Vocabulary
Term Name: dwc:dateIdentified |
Normative URI |
http://rs.tdwg.org/dwc/terms/dateIdentified |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/dateIdentified-2020-08-12 |
Label |
Date Identified |
|
Required: No -- Repeatable: No |
Definition |
The date on which the subject was determined as representing the Taxon. |
Usage |
The date on which the person(s) given under Identified By applied a Scientific Taxon Name to the resource. |
Notes |
Recommended best practice is to use a date that conforms to ISO 8601-1:2019. |
Examples |
`1963-03-08T14:07-0600` (8 Mar 1963 at 2:07pm in the time zone six hours earlier than UTC). `2009-02-20T08:40Z` (20 February 2009 8:40am UTC). `2018-08-29T15:19` (3:19pm local time on 29 August 2018). `1809-02-12` (some time during 12 February 1809). `1906-06` (some time in June 1906). `1971` (some time in the year 1971). `2007-03-01T13:00:00Z/2008-05-11T15:30:00Z` (some time during the interval between 1 March 2007 1pm UTC and 11 May 2008 3:30pm UTC). `1900/1909` (some time during the interval between the beginning of the year 1900 and the end of the year 1909). `2007-11-13/15` (some time in the interval between 13 November 2007 and 15 November 2007). |
Term Name: dwc:identificationQualifier |
Normative URI |
http://rs.tdwg.org/dwc/terms/identificationQualifier |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/identificationQualifier-2017-10-06 |
Label |
Identification Qualifier |
|
Required: No -- Repeatable: Yes |
Definition |
A brief phrase or a standard term ("cf.", "aff.") to express the determiner's doubts about the Identification. |
Usage |
A brief phrase or a standard abbreviation ("cf. genus", "cf. species", "cf. var.", "aff. species", etc.) to express the determiner's doubts with respect to a specified taxonomic rank about the identification given in Scientific Taxon Name. |
Notes |
Splitting identification qualification and Scientific Taxon Name into separate fields is recommended practice in cases where only a single taxon name is available, or if the exchange format is able to keep relations between multiple names and identification qualifiers. Where the exchange format only supports simple multiplicities, a media item with multiple Scientific Taxon Names, some with, some without identification qualifiers, may have to be transferred with "cf." or "aff." qualifiers remaining embedded in the Scientific Taxon Name. Example: For the determinations "cf. Fusarium oxysporum f. sp. palmarum", "Fusarium cf. oxysporum f. sp. palmarum", "Fusarium oxysporum cf. f. sp. palmarum" the Scientific Taxon Name would always be "Fusarium oxysporum f. sp. palmarum", with Identification Qualifier "cf. genus", "cf. species" and "cf. f.sp.", respectively. In most cases only the lowest taxon is in doubt, but cases exist where good reasons exist to suspect a specific or even infraspecific determination, without having a save generic identification. |
Examples |
`aff. agrifolia var. oxyadenia` (for `Quercus aff. agrifolia var. oxyadenia` with accompanying values `Quercus` in genus, `agrifolia` in specificEpithet, `oxyadenia` in infraspecificEpithet, and `var.` in taxonRank. `cf. var. oxyadenia` for `Quercus agrifolia cf. var. oxyadenia` with accompanying values `Quercus` in genus, `agrifolia` in specificEpithet, `oxyadenia` in infraspecificEpithet, and `var.` in taxonRank. |
Term Name: dwc:identifiedBy |
Normative URI |
http://rs.tdwg.org/dwc/terms/identifiedBy |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/identifiedBy-2017-10-06 |
Label |
Identified By |
|
Required: No -- Repeatable: Yes |
Definition |
A list (concatenated and separated) of names of people, groups, or organizations who assigned the Taxon to the subject. |
Usage |
The name(s) of the person(s) who applied the Scientific Taxon Name to the media item or the occurrence represented in the media item. |
Notes |
Recommended best practice is to separate the values in a list with space vertical bar space (` | `). |
Examples |
`James L. Patton`, `Theodore Pappenfuss | Robert Macey` |
Term Name: dwc:lifeStage |
Normative URI |
http://rs.tdwg.org/dwc/terms/lifeStage |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/lifeStage-2017-10-06 |
Label |
Subject Life Stage |
|
Required: No -- Repeatable: Yes |
Definition |
The age class or life stage of the biological individual(s) at the time the Occurrence was recorded. |
Usage |
A description of the life-cycle stage of any organisms featured within the media, when relevant to the subject of the media, e. g., larvae, juvenile, adult. |
Notes |
Recommended best practice is to use a controlled vocabulary. |
Examples |
`egg`, `eft`, `juvenile`, `adult` |
Term Name: dwc:nameAccordingTo |
Normative URI |
http://rs.tdwg.org/dwc/terms/nameAccordingTo |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/nameAccordingTo-2017-10-06 |
Label |
Name According To |
|
Required: No -- Repeatable: Yes |
Definition |
The reference to the source in which the specific taxon concept circumscription is defined or implied - traditionally signified by the Latin "sensu" or "sec." (from secundum, meaning "according to"). For taxa that result from identifications, a reference to the keys, monographs, experts and other sources should be given. |
Usage |
The taxonomic authority used to apply the name to the taxon, e. g., a person, book or web service. |
Notes |
Examples are "Flora of North America", "Landrum 1981, Monograph of the Genus Myrceugenia (Myrtaceae)", "Peterson Field Guide to Birds of North America", or "Expert identification by J.Smith". |
Examples |
`McCranie, J. R., D. B. Wake, and L. D. Wilson. 1996. The taxonomic status of Bolitoglossa schmidti, with comments on the biology of the Mesoamerican salamander Bolitoglossa dofleini (Caudata: Plethodontidae). Carib. J. Sci. 32:395-398.`, `Werner Greuter 2008`. `Lilljeborg 1861, Upsala Univ. Arsskrift, Math. Naturvet., pp. 4, 5` |
Term Name: ac:otherScientificName |
Normative URI |
http://rs.tdwg.org/ac/terms/otherScientificName |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/otherScientificName-2020-01-27 |
Label |
Other Scientific Name |
|
Required: No -- Repeatable: Yes |
Definition |
One or several Scientific Taxon Names that are synonyms to the Scientific Taxon Name may be provided here. |
Notes |
The primary purpose of this is in support of resource discovery, not developing a taxonomic synonymy. Misidentification or misspellings may thus be of interest. Where multiple taxa are present in a resource and multiple Scientific Taxon Names are given, the association between synonyms and names may not be deducible from the AC record alone. |
Term Name: dwc:preparations |
Normative URI |
http://rs.tdwg.org/dwc/terms/preparations |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/preparations-2017-10-06 |
Label |
Subject Preparation Technique |
|
Required: No -- Repeatable: No |
Definition |
A list (concatenated and separated) of preparations and preservation methods for a specimen. |
Usage |
Free form text describing the techniques used to prepare the subject of the media, prior to or while creating the media resource. |
Notes |
Examples for such techniques are: Insect under CO2, cooled to immobility, preservation with ethanol or formaldehyde. See also Resource Creation Technique for technical aspects of digital media object creation. |
Term Name: dwc:scientificName |
Normative URI |
http://rs.tdwg.org/dwc/terms/scientificName |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/scientificName-2017-10-06 |
Label |
Scientific Taxon Name |
|
Required: No -- Repeatable: Yes |
Definition |
The full scientific name, with authorship and date information if known. When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the IdentificationQualifier term. |
Usage |
Scientific names of taxa represented in the media resource (with date and name authorship information if available) of the lowest level taxonomic rank that can be applied. |
Notes |
The Scientific Taxon Name may possibly be of a higher rank, e.g., a genus or family name, if this is the most specific identification available. Where multiple taxa are the subject of the media item, multiple names may be given. If possible, add this information here even if the title or caption of the resource already contains scientific taxon names. Where the list of scientific taxon names is impractically large (e.g., media collections or identification tools), the number of taxa should be given in Taxon Count (see below). If possible, avoid repeating the Taxonomic Coverage here. Do not use abbreviated Genus names ("P. vulgaris"). It is recommended to provide author citation to scientific names, to avoid ambiguities in the presence of homonyms (the same name created by different authors for different taxa). Identifier qualifications should be supplied in the Identification Qualifier term rather than here (i. e. "Abies cf. alba" is deprecated, to be replaced with Scientific Taxon Name = "Abies alba" and Identification Qualifier = "cf. species"). |
Examples |
`Coleoptera` (order). `Vespertilionidae` (family). `Manis` (genus). `Ctenomys sociabilis` (genus + specificEpithet). `Ambystoma tigrinum diaboli` (genus + specificEpithet + infraspecificEpithet). `Roptrocerus typographi (Györfi, 1952)` (genus + specificEpithet + scientificNameAuthorship), `Quercus agrifolia var. oxyadenia (Torr.) J.T. Howell` (genus + specificEpithet + taxonRank + infraspecificEpithet + scientificNameAuthorship). |
Term Name: dwc:sex |
Normative URI |
http://rs.tdwg.org/dwc/terms/sex |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/sex-2017-10-06 |
Label |
Subject Sex |
|
Required: No -- Repeatable: Yes |
Definition |
The sex of the biological individual(s) represented in the Occurrence. |
Usage |
A description of the sex of any organisms featured within the media, when relevant to the subject of the media, e. g., male, female, hermaphrodite, dioecious. |
Notes |
Recommended best practice is to use a controlled vocabulary. |
Examples |
`female`, `male`, `hermaphrodite` |
Term Name: ac:subjectOrientation |
Normative URI |
http://rs.tdwg.org/ac/terms/subjectOrientation |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/subjectOrientation-2020-01-27 |
Label |
Subject Orientation |
|
Required: No -- Repeatable: Yes |
Definition |
Specific orientation (= direction, view angle) of the subject represented in the media resource with respect to the acquisition device. |
Notes |
Examples: "dorsal", "ventral", "frontal", etc. No formal encoding scheme as yet exists. The term is repeatable e.g., in the case of a composite image, consisting of a combination of different view orientations. |
Term Name: ac:taxonCount |
Normative URI |
http://rs.tdwg.org/ac/terms/taxonCount |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/taxonCount-2020-01-27 |
Label |
Taxon Count |
|
Required: No -- Repeatable: No |
Definition |
An exact or estimated number of taxa at the lowest applicable taxon rank (usually species or infraspecific) represented by the media resource (item or collection). |
Usage |
The count SHOULD contain only the taxa covered fully or primarily by the resource. This SHOULD be a single integer number. |
Notes |
Primarily intended for resource collections and singular resources dealing with sets of taxa (e. g., identification tools, videos). It is recommended to give an exact or estimated number of specific taxa when a complete list of taxa is not available or practical. For a taxon page and most images this will be "1", i. e. other taxa mentioned on the side or in the background should not be counted. However, sometimes a resource may illustrate an ecological or behavioral entity with multiple species, e. g., a host-pathogen interaction; taxon count would then indicate the known number of species in this interaction. Leave the field empty if you cannot estimate the information (do not enter 0). Additional taxon counts at higher levels (e. g. how many families are covered by a digital Fauna) should be given verbatim in the resource description, not here. |
Term Name: ac:taxonCoverage |
Normative URI |
http://rs.tdwg.org/ac/terms/taxonCoverage |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/taxonCoverage-2020-01-27 |
Label |
Taxon Coverage |
|
Required: No -- Repeatable: No |
Definition |
A higher taxon (e. g., a genus, family, or order) at the level of the genus or higher, that covers all taxa that are the primary subject of the resource (which may be a media item or a collection). |
Notes |
Example: Where the subject of an image is several species of ducks with trees visible in the background, Taxon Coverage would still be Anatidae (and not Biota). Example: "Aves" for a bird key or a bird image collection. Do not add a rank ("Class Aves") in this field. Note that this somewhat expands the usage of ncd:taxonCoverage which, however has not yet been adopted by TDWG, and which specifies at the Family level or higher. For collections it is recommended to follow ncd:taxonCoverage to avoid conflicts between an AC record and a record arising from use of the un-adopted NCD. If the resource contains a single taxon, this should be placed in Scientific Taxon Name. In this case Taxon Coverage may be left empty, but if not, care should be taken that the entries do not conflict. Example: If Scientific Taxon Name is Quercus alba then Taxon Coverage, if provided at all, should be Quercus. |
Term Name: dwc:vernacularName |
Normative URI |
http://rs.tdwg.org/dwc/terms/vernacularName |
Modified |
2020-08-23 |
Term version URI |
http://rs.tdwg.org/dwc/terms/version/vernacularName-2017-10-06 |
Label |
Common Name |
|
Required: No -- Repeatable: Yes |
Definition |
A common or vernacular name. |
Usage |
Common (= vernacular) names of the subject in one or several languages. The ISO 639-1 language code SHOULD be given in parentheses after the name if not all names are given by values of the Metadata Language term. |
Notes |
The ISO language code after the name should be formatted as in the following example: 'abete bianco (it); Tanne (de); White Fir (en)'. If names are known to be male- or female-specific, this may be specified as in: 'ewe (en-female); ram (en-male);'. |
Examples |
`Andean Condor`, `Condor Andino`, `American Eagle`, `Gänsegeier` |
7.8 Resource Creation Vocabulary
Term Name: ac:captureDevice |
Normative URI |
http://rs.tdwg.org/ac/terms/captureDevice |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/captureDevice-2020-01-27 |
Label |
Capture Device |
|
Required: No -- Repeatable: No |
Definition |
Free form text describing the device or devices used to create the resource. |
Notes |
It is best practice to record the device; this may include a combination such as camera plus lens, or camera plus microscope. Examples: "Canon Supershot 2000", "Makroscan Scanner 2000", "Zeiss Axioscope with Camera IIIu", "SEM (Scanning Electron Microscope)". |
Term Name: ac:digitizationDate |
Normative URI |
http://rs.tdwg.org/ac/terms/digitizationDate |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/digitizationDate-2020-01-27 |
Label |
Date and Time Digitized |
|
Required: No -- Repeatable: No |
Definition |
Date the first digital version was created, if different from Original Date and Time found in the Temporal Coverage Vocabulary. |
Usage |
The date and time MUST comply with the World Wide Web Consortium (W3C) datetime practice, https://www.w3.org/TR/NOTE-datetime, which requires that date and time representation correspond to ISO 8601:1998, but with year fields always comprising 4 digits. This makes datetime records compliant with 8601:2004, https://www.iso.org/standard/40874.html. AC datetime values MAY also follow 8601:2004 for ranges by separating two IS0 8601 datetime fields by a solidus ("forward slash", '/'). Use the international (ISO/xml) format yyyy-mm-ddThh:mm (e. g. "2007-12-31" or "2007-12-31T14:59"). Where available, timezone information SHOULD be added. |
Notes |
This is often not the media creation or modification date. For example, if photographic prints have been scanned, the date of that scanning is what this term carries, but Original Date and Time is that depicted in the print. In the case of digital images containing EXIF, whereas the EXIF capture date does not contain time zone information, but EXIF GPSDateStamp and GPSTimeStamp may be relevant as these include time-zone information. See also Metadata Working Group Guidelines for Handling Image Metadata, Version 2.0 (November 2010), https://web.archive.org/web/20180919181934/http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf, which has best practice advice on handling time-zone-less EXIF date/time data. See also the Wikipedia IS0 8601 entry, https://en.wikipedia.org/wiki/ISO_8601, for further explanation and examples. |
Term Name: Iptc4xmpExt:LocationCreated |
Normative URI |
http://iptc.org/std/Iptc4xmpExt/2008-02-29/LocationCreated |
Modified |
2020-01-27 |
Label |
Location Created |
|
Required: No -- Repeatable: Yes |
Definition |
The location the content of the item was created |
Usage |
The location at which the media recording instrument was placed when the media was created. |
Notes |
The distinction between the location shown and created is often irrelevant, and metadata may be assumed to be referring to location shown. It is recommended that the Location Shown field above always be used when known. However, in the case of position data automatically recorded by the instrument (e. g. EXIF GPS data) Location Created should be used to maintain information accuracy. When one but not both of these locations are present, AC is silent about whether the provided one entails the other. A best practices document for a particular AC implementation might address this. |
Term Name: ac:resourceCreationTechnique |
Normative URI |
http://rs.tdwg.org/ac/terms/resourceCreationTechnique |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/resourceCreationTechnique-2020-01-27 |
Label |
Resource Creation Technique |
|
Required: No -- Repeatable: No |
Definition |
Information about technical aspects of the creation and digitization process of the resource. This includes modification steps ("retouching") after the initial resource capture. |
Notes |
Examples: Encoding method or settings, numbers of channels, lighting, audio sampling rate, frames per second, data rate, interlaced or progressive, multiflash lighting, remote control, automatic interval exposure. Annotating whether and how a resource has been modified or edited significantly in ways that are not immediately obvious to, or expected by, consumers is of special significance. Examples for images are: Removing a distracting twig from a picture, moving an object to a different surrounding, changing the color in parts of the image, or blurring the background of an image. Modifications that are standard practice and expected or obvious are not necessary to document; examples of such practices include changing resolution, cropping, minor sharpening or overall color correction, and clearly perceptible modifications (e.g., addition of arrows or labels, or the placement of multiple pictures into a table.) If it is only known that significant modifications were made, but no details are known, a general statement like "Media may have been manipulated to improve appearance" may be appropriate. See also Subject Preparation Technique. |
Term Name: ac:associatedSpecimenReference |
Normative URI |
http://rs.tdwg.org/ac/terms/associatedSpecimenReference |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/associatedSpecimenReference-2020-01-27 |
Label |
Associated Specimen Reference |
|
Required: No -- Repeatable: Yes |
Definition |
A reference to a specimen associated with this resource. |
Notes |
Supports finding a specimen resource, where additional information is available. If several resources relate to the same specimen, these are implicitly related. Examples: for NHM "BM 23974324" for a barcoded or "BM Smith 32" for a non-barcoded specimen; for UNITS: "TSB 28637"; for PMSL: "PMSL-Lepidoptera-2534781". Ideally this may be a URI identifying a specimen record that is available online. |
Term Name: ac:derivedFrom |
Normative URI |
http://rs.tdwg.org/ac/terms/derivedFrom |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/derivedFrom-2020-01-27 |
Label |
Derived From |
|
Required: No -- Repeatable: Yes |
Definition |
A reference to an original resource from which the current one is derived. |
Usage |
Human readable, or doi number, or URL. Simple name of parent for human readable. |
Notes |
Derivation of one resource from another is of special interest for identification tools (e. g. a key from an unpublished data set, as in FRIDA, or a PDA key from a PC or web key) or web services (e. g. a name synonymization service being derived from a specific data set). It may very rarely also be known where one image or sound recording is derived from another (but compare the separate mechanism to be used for quality/resolution levels). Can be repeated if a montage of images. |
Term Name: ac:providerID |
Normative URI |
http://rs.tdwg.org/ac/terms/providerID |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/providerID-2020-01-27 |
Label |
Provider ID |
|
Required: No -- Repeatable: No |
Definition |
A globally unique ID of the provider of the current AC metadata record. |
Notes |
Only to be used if the annotated resource is not a provider itself - this item is for relating the resource to a provider, using an arbitrary code that is unique for a provider, contributing partner, or aggregator, or other roles (potentially defined by MARC, OAI) and by which the media resources are linked to the provider. |
Term Name: ac:relatedResourceID |
Normative URI |
http://rs.tdwg.org/ac/terms/relatedResourceID |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/relatedResourceID-2020-01-27 |
Label |
Related Resource ID |
|
Required: No -- Repeatable: Yes |
Definition |
Resource related in ways not specified through a collection, e.g., before-after images; time-lapse series; different orientations/angles of view |
Notes |
The value references a related media item. Examples of relations are: Images taken in a sequence or defined time series, an exposure or focus series (e.g. for stacking), different framing or views (top, side, bottom) of the same subject, or an overview plus several details. The property makes such related media items discoverable, but does not indicate the nature of this relationship. More specific properties may be defined in a later version of AC. |
7.10 Service Access Point Vocabulary
These terms are representation-dependent metadata, referring to specific digital representations of a resource (e.g., a specific resolution, quality, or format). They are used within whatever a particular AC implementation assigns to the value of ac:hasServiceAccessPoint
, whose label is simply “Service Access Point.” Note that it is possible for an implementation to use syntactic conventions that avoid direct use of ac:hasServiceAccessPoint
, as illustrated in the final example in the section Multiplicity/Cardinality in the Audubon Core Structure document.
Term Name: ac:accessURI |
Normative URI |
http://rs.tdwg.org/ac/terms/accessURI |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/accessURI-2020-01-27 |
Label |
Access URI |
|
Required: No -- Repeatable: No |
Definition |
A URI that uniquely identifies a service that provides a representation of the underlying resource. |
Usage |
If this resource can be acquired by an http request, its http URL SHOULD be given. If not, but it has some URI in another URI scheme, that MAY be given here. |
Notes |
Value might point to something offline, such as a published CD, etc. For example, the doi of a published CD would be a suitable value. |
Term Name: dc:format |
Normative URI |
http://purl.org/dc/elements/1.1/format |
Modified |
2020-01-27 |
Term version URI |
http://dublincore.org/usage/terms/history/#format-007 |
Label |
Format |
|
Required: No -- Repeatable: No |
Definition |
The file format, physical medium, or dimensions of the resource. |
Usage |
A string describing the technical format of the resource (file format or physical medium). |
Notes |
Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME]. This term is recommended for offline digital content. In cases where the provided URL includes a standard file extension from which the format can be inferred, it is permissible to not provide this item. Three types of values are recommended: (a) any MIME type; (b) common file extensions like txt, doc, odf, jpg/jpeg, png, pdf; (c) the following special values: Data-CD, Audio-CD, Video-CD, Data-DVD, Audio-DVD, Video-DVD-PAL, Video-DVD-NTSC, photographic slide, photographic print. Compare Type for the content-type. See also the entry for dcterms:format in the Audubon Core term list document and see the DCMI FAQ on DC and DCTERMS Namespaces, https://web.archive.org/web/20171126043657/https://github.com/dcmi/repository/blob/master/mediawiki_wiki/FAQ/DC_and_DCTERMS_Namespaces.md, for discussion of the rationale for terms in two namespaces. Normal practice is to use the same Label if both are provided. Labels have no effect on information discovery and are only suggestions. |
Term Name: ac:hashValue |
Normative URI |
http://rs.tdwg.org/ac/terms/hashValue |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/hashValue-2020-01-27 |
Label |
Hash |
|
Required: No -- Repeatable: No |
Definition |
The value computed by a hash function applied to the media that will be delivered at the access point. |
Notes |
Best practice is to also specify the hash function by supplying a value of the Hash Function term, using one of the standard literals from the Notes there. |
Term Name: ac:licensingException |
Normative URI |
http://rs.tdwg.org/ac/terms/licensingException |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/licensingException-2020-01-27 |
Label |
Licensing Exception Statement |
|
Required: No -- Repeatable: No |
Definition |
The licensing statement for this variant of the media resource if different from that given in the License Statement property of the resource. |
Notes |
Required only if this version has different licensing than that of the media resource. For example, the highest resolution version may be more restricted than lower resolution versions. |
Term Name: exif:PixelXDimension |
Normative URI |
http://ns.adobe.com/exif/1.0/PixelXDimension |
Modified |
2020-01-27 |
Label |
Image Width |
|
Required: No -- Repeatable: No |
Definition |
Information specific to compressed data. When a compressed file is recorded, the valid width of the meaningful image shall be recorded in this tag, whether or not there is padding data or a restart marker. This tag shall not exist in an uncompressed file. |
Usage |
The width in pixels of the media specified by the access point. Contrary to the definition, in Audubon Core, this term MAY be used with uncompressed files. |
Notes |
Audubon Core uses this term for any image type, including those to which EXIF does not apply and those that are not a compressed file type like JPEG. |
Term Name: exif:PixelYDimension |
Normative URI |
http://ns.adobe.com/exif/1.0/PixelYDimension |
Modified |
2020-01-27 |
Label |
Image Height |
|
Required: No -- Repeatable: No |
Definition |
Information specific to compressed data. When a compressed file is recorded, the valid height of the meaningful image shall be recorded in this tag, whether or not there is padding data or a restart marker. This tag shall not exist in an uncompressed file. |
Usage |
The height in pixels of the media specified by the access point. Contrary to the definition, in Audubon Core, this term MAY be used with uncompressed files. |
Notes |
Audubon Core uses this term for any image type, including those to which EXIF does not apply and those that are not a compressed file type like JPEG. |
Term Name: ac:serviceExpectation |
Normative URI |
http://rs.tdwg.org/ac/terms/serviceExpectation |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/serviceExpectation-2020-01-27 |
Label |
Service Expectation |
|
Required: No -- Repeatable: No |
Definition |
A term that describes what service expectations users may have of the ac:accessURL. |
Notes |
Recommended terms include online (denotes that the URL is expected to deliver the resource), authenticate (denotes that the URL delivers a login or other authentication interface requiring completion before delivery of the resource) published(non digital) (denotes that the URL is the identifier of a non-digital published work, for example a doi.) Communities should develop their own controlled vocabularies for Service Expectations. |
Term Name: ac:variant |
Normative URI |
http://rs.tdwg.org/ac/terms/variant |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/variant-2020-01-27 |
Label |
Variant |
|
Required: No -- Repeatable: Yes |
Definition |
A URI designating what this Service Access Point provides. |
Notes |
Some suggested values are the URIs ac:Thumbnail, ac:Trailer, ac:LowerQuality, ac:MediumQuality, ac:GoodQuality, ac:BestQuality, and ac:Offline. Additional URIs from communities of practice may be introduced. |
Term Name: ac:variantDescription |
Normative URI |
http://rs.tdwg.org/ac/terms/variantDescription |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/variantDescription-2020-01-27 |
Label |
Variant Description |
|
Required: No -- Repeatable: No |
Definition |
Text that describes this Service Access Point variant |
Notes |
Most variants (thumb, low-res, high-res) are self-explanatory and it is best practice to leave this property empty if no special description is needed. It is provided for cases that require additional information (e.g., video shortened instead of simply quality reduced). |
Term Name: ac:variantLiteral |
Normative URI |
http://rs.tdwg.org/ac/terms/variantLiteral |
Modified |
2020-01-27 |
Term version URI |
http://rs.tdwg.org/ac/terms/version/variantLiteral-2020-01-27 |
Label |
Variant |
|
Required: No -- Repeatable: Yes |
Definition |
Text that describes this Service Access Point variant. |
Notes |
This is an alternative to ac:variant where using a string is preferred over a URI. It is best practice to use ac:variant instead of ac:variantLiteral wherever practical. Value may be free text, but it is suggested to consider including terminology based on the following: Thumbnail: Service Access Point provides a thumbnail image, short sound clip, or short movie clip that can be used in addition to the resource to represent the media object, typically at lower quality and higher compression than a preview object. A typical size for a tiny thumbnail image may be 50-100 pixels in the longer dimension. Trailer: Service Access Point provides video clip preview, in the form of a specifically authored "Trailer", which may provide somewhat different content than the original resource. Lower Quality: Service Access Point provides a lower quality version of the media resource, suitable e. g. for web sites. Medium Quality: Service Access Point provides a medium quality version of the media resource, e. g. shortened in duration, or reduced size, using lower resolution or higher compression causing moderate artifacts. Good Quality: Service Access Point provides a good quality version of the media resource intended for resources displayed as primary information; e. g. an image between 800 and 1600 px in width or height. Best Quality: Service Access Point provides the highest available quality of the media resource, whatever its resolution or quality level. Offline: Service Access Point provides data about an offline resource. |