Work in progress: Page content may be in transition. Please do not edit this page while you see this. Expecting to finish by about about 04:30Z — Gregor Hagedorn.

Last edit of page on: 2012-10-02

See Audubon Core for introductory material on the terminology.

See also the non-normative Audubon Core Term List RDF Version

Title: Audubon Core Term List

Date: TBD. This document is a proposal.

Abstract: The Audubon Core is a set of vocabularies designed to represent metadata for biodiversity multimedia resources and collections. These vocabularies aim to represent information that will help to determine whether a particular resource or collection will be fit for some particular biodiversity science application before acquiring the media. Among others, the vocabularies address such concerns as the management of the media and collections, descriptions of their content, their taxonomic, geographic, and temporal coverage, and the appropriate ways to retrieve, attribute and reproduce them. 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 commentary.

Contributors: Robert A. Morris, Vijay Barve, Mihail Carausu, Vishwas Chavan, José Cuadra, Chris Freeland, Gregor Hagedorn, Patrick Leary, Dimitry Mozzherin, Annette Olson, Greg Riccardi, Ivan Teage

Legal: This document is governed by the standard legal, copyright, licensing provisions and disclaimers issued by the Taxonomic Databases Working Group.

Part of TDWG Standard: TBD

This is a normative document.

An Audubon Core (AC) record is a description, using the Audubon Core vocabularies, of a multimedia resource. Two kinds of terms are specified by this document: record-level terms and access-level terms. Terms under the Record-level Terms section apply to the whole Audubon Core record regardless of the record type. Almost all terms are record-level terms. One such term, hasServiceAccessPoint plays a special role in helping to retrieve the resource that the record describes. Its value is an identifier of a set of more metadata about services that may provide web or other access to a file containing the media. A multimedia resource may describe more than one such service, each of which is described by values of one or more access-level terms, telling such things as a web address at which the resource from which a digital representation of the resource can be retrieved, the size of such a retrieved object, etc.

This document has wiki revision ID 27660 with a permalink http://www.species-id.net/w/index.php?oldid=27660.
The version under consideration by TDWG has permalink http://www.species-id.net/w/index.php?oldid=25834.

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. Common such usage for abbreviations and namespace prefixes are Darwin Core (DwC, dwc:), Dublin Core (DC, dcterms:), Adobe XMP (XMP, xmp:), International Press and Telecomunications Council (IPTC, Iptc4xmpExt:) , and the TDWG Ontologies Natural History Collection class (NCD, ncd:). Hypertext links in the term table entries will bring the reader to appropriate documentation of those organizations.

Namespaces, Prefixes and Term Names

The namespace of terms borrowed from other vocabularies is that of the original. The namespace of denovo AC terms is http://rs.tdwg.org/ac/terms/. In the table of terms, each term entry has a row with the term name. Following the practice of the Darwin Core term list, for borrowed terms this term name is generally an "unqualified name" preceded by a widely accepted prefix designating an abbreviation for the namespace, whereas for denovo AC terms, no such prefix is prepended. It is recommended that implementors who need a namespace prefix for the AC namespace use "ac" wherever feasible.

Vocabulary Indices

Term Index By Name

(See also Index By Label)

Management Vocabulary

Attribution Vocabulary

Agents Vocabulary

Content Coverage Vocabulary

Geography Vocabulary

Temporal Coverage Vocabulary

Subject of Resource Vocabulary

Taxonomic Coverage Vocabulary

Resource Creation Vocabulary

Service Access Point Vocabulary

| hasAccessPoint |

Service Access Point Properties

Related Resources Vocabulary

Term Index By Label

(See also Index By Name)

Management Vocabulary

Attribution Vocabulary

Agents Vocabulary

Content Coverage Vocabulary

Geography Vocabulary

Temporal Coverage Vocabulary

Subject of Resource Vocabulary

Taxonomic Coverage Vocabulary

Resource Creation Vocabulary

Service Access Point Vocabulary

ServiceAccessPoint Class

| Service Access Point |

Service Access Point Properties

Related Resources Vocabulary

Record-level Terms

Management Vocabulary

Term Name: dcterms:identifier
Normative URI:	http://purl.org/dc/terms/identifier
Label	Identifier
	Layer: Core — Required: Yes for media collections, No for media resources (but preferred if available). — Repeatable: Yes
Definition:	An arbitrary code that is unique for the resource, with the resource being either a provider, collection, or media item.
Details	dcterms:identifier
Comments:	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 an http-URL, an lsid-URI, and a GUID-number).
Term Name: dcterms:type
Normative URI:	http://purl.org/dc/terms/type
Label	Type
	Layer: Core — Required: Yes — Repeatable: No
Definition:	Any dcmi type term from http://dublincore.org/documents/dcmi-type-vocabulary/ may be used. Recommended terms are Collection, StillImage, Sound, MovingImage, InteractiveResource, Text. Also recommended are PanAndZoomImage, 3DStillImage, and 3DMovingImage. Values may be used either in their literal form, or with a full namespace (e. g. http://purl.org/dc/dcmitype/StillImage) from a controlled vocabulary.
Details	dcterms:type
Comments:	A Collection should be given type http://purl.org/dc/dcmitype/Collection. If the resource is a Collection, this item does not identify what types of objects it may contain. Following the DC recommendations at http://purl.org/dc/dcmitype/Text, images of text should be marked as Text.
Term Name: subtype
Normative URI:	http://rs.tdwg.org/ac/terms/subtype
Label	Subtype
	Layer: Core — Required: No — Repeatable: Yes
Definition:	Any of Drawing, Painting, Logo, Icon, Illustration, Graphic, Photograph, Animation, Film, SlideShow, DesignPlan, Diagram, Map, MusicalNotation, IdentificationKey, ScannedText, RecordedText, RecordedOrganism, TaxonPage, MultimediaLearningObject, VirtualRealityEnvironment, GlossaryPage. Values may be used either in their literal form, or with a full namespace from a controlled vocabulary.
Details
Comments:	This does not apply to Collection objects. The vocabulary may be extended by users provided they identify the term by a URI which is not in the ac namespace (for example, using "http://my.inst.org/namespace/metadata/subtype/repair-manual"). Conforming applications may choose to ignore these.
Term Name: dcterms:title
Normative URI:	http://purl.org/dc/terms/title
Label	Title
	Layer: Core — Required: No — Repeatable: No
Definition:	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.
Details	dcterms:title
Comments:	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: dcterms:modified
Normative URI:	http://purl.org/dc/terms/modified
Label	Modified
	Layer: Extended — Required: No — Repeatable: Yes
Definition:	Date that the media resource was altered. The date and time must comply with the World Wide Web Consortium (W3C) datetime practice, 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. AC datetime values may also follow 8601:2004 for ranges by separating two IS0 8601 datetime fields by a solidus ("forward slash", '/'). See also the wikipedia IS0 8601 entry for further explanation and examples.
Details	dcterms:modified
Comments:	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 for further explanation and examples.
Term Name: xmp:MetadataDate
Normative URI:	http://ns.adobe.com/xap/1.0/MetadataDate
Label	Metadata Date
	Layer: Core — Required: No — Repeatable: No
Definition:	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, 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. AC datetime values may also follow 8601:2004 for ranges by separating two IS0 8601 datetime fields by a solidus ("forward slash", '/'). See also the wikipedia IS0 8601 entry for further explanation and examples.
Details	Terms for Adobe XMP have URIs that are not resolvable. Instead, visit XMP Specification Part 1, Sec 8.4 for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Comments:	This is not dcterms:modified, which refers to the resource itself rather than its metadata. See also the wikipedia IS0 8601 entry for further explanation and examples.
Term Name: metadataLanguage
Normative URI:	http://rs.tdwg.org/ac/terms/metadataLanguage
Label	Metadata Language
	Layer: Core — Required: Yes — Repeatable: No
Definition:	Language of description and other metadata (but not necessarily of the image itself) represented in ISO639-1 or -3.
Details
Comments:	This is NOT dcterms:language, which is about the resource, not the metadata. Metadata Language is deliberately single-valued, imposing a requirement that multi-lingual metadata be represented as separate, complete, metadata records in which also the language-neutral items appear. Consumers can re-combine records by identity of multimedia Resource IDs (which are highly recommended to supply). In the face of metadata records of several languages for the same resource, this normative document offers no guidance as to how to disambiguate what language applies to what metadata. To disambiguate this, the metadata provider can provide a separate AC object for each different MetadataLanguage, each such AC object referring to the same multimedia resource Identifier. This comes at a cost of repeated data for the "language neutral" metadata items, but the alternative is to have a complex hierarchical structure for an AC object. Nothing in this document would prevent an implementer, e. g. of an XML-Schema representation, from providing a fully hierarchical schema and disambiguating that way. Users of a particular implementation should consult documentation specific for that implementation on this point, but it should always be correct, if convenient, to provide one metadata record per language.
Term Name: providerManagedID
Normative URI:	http://rs.tdwg.org/ac/terms/providerManagedID
Label	Provider-managed ID
	Layer: Extended — Required: No — Repeatable: No
Definition:	A free-form identifier (a simple number, an alphanumeric code, a URL, etc.) that is unique and meaningful primarily for the data provider.
Details
Comments:	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
Label	Rating
	Layer: Core — Required: No — Repeatable: No
Definition:	A rating of the media resources, provided by users or editors, with -1 defining “rejected”, “0” defining “unrated”, and “1” (worst) to “5” (best).
Details	Terms for Adobe XMP have URIs that are not resolvable. Instead, visit XMP Specification Part 1, Sec 8.4 for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF. The Adobe documentation describes this as "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 may be assumed. 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.
Comments:	The origin of the rating is not communicated. It may, e. g., be based on user feedback or on editorial ratings. If Rating is not present, a value of 0 may be assumed.
Term Name: comments
Normative URI:	http://rs.tdwg.org/ac/terms/comments
Label	Comments
	Layer: Extended — Required: No — Repeatable: Yes
Definition:	Any comment provided on the media resource, as free-form text. Best practice would also identify the commenter.
Details
Comments:	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 metadata is false, without asserting a positive identification). There is a separate item for reviewer comments, which is defined more as an expert-level review.
Term Name: reviewer
Normative URI:	http://rs.tdwg.org/ac/terms/reviewer
Label	Reviewer
	Layer: Extended — Required: No — Repeatable: Yes
Definition:	If present, then resource is peer-reviewed, even if Reviewers Comments are lacking. 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).
Details
Comments:	Provider is asserting they accept this review as competent.
Term Name: reviewerComments
Normative URI:	http://rs.tdwg.org/ac/terms/reviewerComments
Label	Reviewer Comments
	Layer: Extended — Required: No — Repeatable: Yes
Definition:	Any comment provided by a reviewer with expertise in the subject, as free-form text.
Details
Comments:	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 metadata is wrong, without asserting a positive identification). There is a separate item “Comments” for text from commenters of unrecorded expertise.
Term Name: dcterms:available
Normative URI:	http://purl.org/dc/terms/available
Label	Date Available
	Layer: Extended — Required: No — Repeatable: No
Definition:	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, 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. AC datetime values may also follow 8601:2004 for ranges by separating two IS0 8601 datetime fields by a solidus ("forward slash", '/'). See also the wikipedia IS0 8601 entry for further explanation and examples.
Details	dcterms:available
Comments:	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 for further explanation and examples.

Attribution Vocabulary

Term Name: dcterms:rights
Normative URI:	http://purl.org/dc/terms/rights
Label	Copyright Statement
	Layer: Core — Required: Yes — Repeatable: No
Definition:	Information about rights held in and over the resource. 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. Examples: “Copyright XY 2008, all rights reserved”, “© 2008 XY Museum” , "Public Domain.", "Copyright unknown" 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 dcterms:rights is not 'Public Domain', appropriate only if the resource is known to be not under copyright.
Details	dcterms:rights
Comments:	This expresses rights over the media resource, not over the metadata text.
Term Name: xmpRights:Owner
Normative URI:	http://ns.adobe.com/xap/1.0/rights/Owner
Label	Copyright Owner
	Layer: Core — Required: No — Repeatable: No
Definition:	A list of the names of the owners of the copyright. 'Unknown' is an acceptable value, but 'Public Domain' is not.
Details	Terms for Adobe XMP have URIs that are not resolvable. Instead, visit XMP Specification Part 1, Sec 8.5 for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Comments:	Some providers use dcterms: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. In this case, omit or leave empty xmpRights:Owner, and put 'Public Domain' in the Copyright Statement (dcterms:rights). Except for 'Public Domain' resources, it is strongly urged that this field be supplied.
Term Name: xmpRights:UsageTerms
Normative URI:	http://ns.adobe.com/xap/1.0/rights/UsageTerms
Label	License Terms
	Layer: Core — Required: No — Repeatable: No
Definition:	The license statement defining how resources may be used. Information on a collection applies to all contained objects unless the object has a different statement.
Details	Terms for Adobe XMP have URIs that are not resolvable. Instead, visit XMP Specification Part 1, Sec 8.5 for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Comments:	Example: "Available under Creative Commons by-nc-sa 2.5 license". This also informs on 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. Note that the medium or low resolution levels of the same image may be available under open access licenses. In general, this term determines the default licensing for the media. License terms for variants of the media available with different licensing are dealt with in the section on Service Access Point Properties
Term Name: xmpRights:WebStatement
Normative URI:	http://ns.adobe.com/xap/1.0/rights/WebStatement
Label	License URL
	Layer: Core — Required: No — Repeatable: No
Definition:	A URL defining or further elaborating on the license statement (e. g., a web page explaining the precise terms of use).
Details	Terms for Adobe XMP have URIs that are not resolvable. Instead, visit XMP Specification Part 1, Sec 8.5 for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Comments:	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/. Where different quality variants (e. g. resolutions of images) are published under different licenses, the AC term “Licensing Exception Statement” supports variant-specific licenses.
Term Name: licenseLogoURL
Normative URI:	http://rs.tdwg.org/ac/terms/licenseLogoURL
Label	License Logo URL
	Layer: Core — Required: No — Repeatable: No
Definition:	A URL providing access to a logo that symbolizes the License.
Details
Comments:	The originating metadata provider is strongly urged to choose a suitable logo as a graphical representation of the licence. Failure to do so may leave downstream aggregators in a difficult position to supply a logo that adequately represents the professional, legal, or social aims of the licensors (license givers). Example: http://i.creativecommons.org/l/by-nc-sa/3.0/us/88x31.png provides access to this:
Term Name: Iptc4xmpExt:CreditLine
Normative URI:	http://iptc.org/std/Iptc4xmpExt/2008-02-29/CreditLine
Label	Attribution Statement
	Layer: Core — Required: No — Repeatable: No
Definition:	free text for "Please cite this as…"
Details	IPTC terms for Adobe XMP have URIs that are not resolvable. Instead, visit IPTC Standard Photo Metadata (July 2010) for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Term Name: attributionLogoURL
Normative URI:	http://rs.tdwg.org/ac/terms/attributionLogoURL
Label	Attribution URL
	Layer: Core — Required: No — Repeatable: No
Definition:	The URL of icon or logo image to appear in source attribution.
Details
Comments:	Entering this URL into a browser should only result in the icon (not in a webpage including the icon).
Term Name: attributionLinkURL
Normative URI:	http://rs.tdwg.org/ac/terms/attributionLinkURL
Label	Attribution Link URL
	Layer: Core — Required: No — Repeatable: No
Definition:	The URL where information about ownership, attribution, etc. of the resource may be found.
Details
Comments:	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: dcterms:source
Normative URI:	http://purl.org/dc/terms/source
Label	Published Source
	Layer: Core — Required: No — Repeatable: Yes
Definition:	An identifiable source from which the described resources was derived.
Details	dcterms:source
Comments:	If image, key, etc. was taken from (i.e. digitized) or was also published in a digital or printed publication. Do not put generally "related" publications in here. This field normally contains a free-form text description; it may be a URI (e.g. “digitally-published://ISBN=961-90008-7-0”) if that URI can be resolved and dereferenced to provide a description of the source resource. Can be repeatable if a montage of images. Information about further provenance beyond the immediate source should be put in the derivedFrom attribute.

Agents Vocabulary

Term Name: dcterms:creator
Normative URI:	http://purl.org/dc/terms/creator
Label	Creator
	Layer: Core — Required: No — Repeatable: Yes
Definition:	The person or organization responsible for creating the media resource.
Details	dcterms:creator
Comments:	The value may be simple text including contact information. Note that the creator need not be the Copyright Owner
Term Name: provider
Normative URI:	http://rs.tdwg.org/ac/terms/provider
Label	Provider
	Layer: Core — Required: No — Repeatable: No
Definition:	Person or organization responsible for presenting the media resource. If no separate Metadata Provider is given, this also attributes the metadata.
Details
Comments:	Media items and Metadata may be served from different institutions, e. g. in the case of aggregators adding user annotations, taxon identifications, or ratings.
Term Name: metadataProvider
Normative URI:	http://rs.tdwg.org/ac/terms/metadataProvider
Label	Metadata Provider
	Layer: Core — Required: No — Repeatable: Yes
Definition:	Person or organization originally responsible for providing the resource metadata record.
Details
Comments:	Media items and Metadata may be served from different institutions, e. g. in the case of aggregators adding user annotations, taxon identifications, or ratings. Compare Provider.
Term Name: metadataCreator
Normative URI:	http://rs.tdwg.org/ac/terms/metadataCreator
Label	Metadata Creator
	Layer: Core — Required: No — Repeatable: Yes
Definition:	Person or organization originally creating the resource metadata record.
Details

Content Coverage Vocabulary

Term Name: dcterms:description
Normative URI:	http://purl.org/dc/terms/description
Label	Description
	Layer: Core — Required: No — Repeatable: No
Definition:	Description of collection or individual resource, containing the Who, What, When, Where and Why as free-form text. This normative document is silent on the nature of formatting in the text. 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.
Details	dcterms:description
Comments:	It optionally allows to present detailed information and will in most cases be shown together with the resource title. If both description and caption (see below) are present, a description is typically displayed instead of the resource, a caption together with the resource. Should be a good proxy for the underlying media resource.
Term Name: caption
Normative URI:	http://rs.tdwg.org/ac/terms/caption
Label	Caption
	Layer: Extended — 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).
Details
Comments:	Often only one of description or caption is present; choose the concept most appropriate for your metadata.
Term Name: dcterms:language
Normative URI:	http://purl.org/dc/terms/language
Label	Language
	Layer: Core — Required: No — Repeatable: Yes
Definition:	Language(s) of resource itself represented in ISO639-1 or -3
Details	dcterms:language
Comments:	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 (ISO code “zxx”). Resources with present but unknown language are to be coded as undetermined (ISO code “und”). Resources only containing scientific organism names should be coded as "zxx-taxon" (do not use the incorrect “la” for Latin). For regional dialects or other special cases, conform to the IETF Best Practices for Tags Identifying Languages.

Geography Vocabulary

Location Created and Location Shown are separated in the current version of IPTC, and the metadata working group (MWG 2010)^[1] also recommends this. We will follow this, to support the expected future increase of automatic GPS based coordinate recording in recording devices. 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 media was created (a specimen was digitized).

All geography terms from the DarwinCore version of 9 Dec 2009 are deemed included in the Core Layer. Specifically, this includes exactly those which are declared by DarwinCore to be in DarwinCore Class Location. 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.

Term Name: Iptc4xmpExt:LocationShown
Normative URI:	http://iptc.org/std/Iptc4xmpExt/2008-02-29/LocationShown
Label	Location Shown
	Layer: Core — Required: No — Repeatable: Yes
Definition:	The location that is depicted the media content, irrespective of the location at which the resource has been created.
Details	IPTC terms for Adobe XMP have URIs that are not resolvable. Instead, visit IPTC Standard Photo Metadata (July 2010) for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Term Name: Iptc4xmpExt:WorldRegion
Normative URI:	http://iptc.org/std/Iptc4xmpExt/2008-02-29/WorldRegion
Label	World Region
	Layer: Core — Required: No — Repeatable: Yes
Definition:	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.
Details	IPTC terms for Adobe XMP have URIs that are not resolvable. Instead, visit IPTC Standard Photo Metadata (July 2010) for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Comments:	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.
Term Name: Iptc4xmpExt:CountryCode
Normative URI:	http://iptc.org/std/Iptc4xmpExt/2008-02-29/CountryCode
Label	Country Code
	Layer: Core — Required: No — Repeatable: Yes
Definition:	The geographic location of the specific entity(ies) documented by the media item, expressed through a constrained vocabulary of countries using 2-letter ISO country code (e. g. "it, si").
Details	IPTC terms for Adobe XMP have URIs that are not resolvable. Instead, visit IPTC Standard Photo Metadata (July 2010) for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Comments:	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). This list may be extended as necessary.
Term Name: Iptc4xmpExt:CountryName
Normative URI:	http://iptc.org/std/Iptc4xmpExt/2008-02-29/CountryName
Label	Country Name
	Layer: Core — Required: No — Repeatable: Yes
Definition:	This field can be free text, but where possible, the use of http://iptc.org/std/Iptc4xmpExt/2008-02-29/CountryCode is preferred.
Details	IPTC terms for Adobe XMP have URIs that are not resolvable. Instead, visit IPTC Standard Photo Metadata (July 2010) for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Term Name: Iptc4xmpExt:ProvinceState
Normative URI:	http://iptc.org/std/Iptc4xmpExt/2008-02-29/ProvinceState
Label	Province or State
	Layer: Core — Required: No — Repeatable: Yes
Definition:	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).
Details	IPTC terms for Adobe XMP have URIs that are not resolvable. Instead, visit IPTC Standard Photo Metadata (July 2010) for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Term Name: Iptc4xmpExt:City
Normative URI:	http://iptc.org/std/Iptc4xmpExt/2008-02-29/City
Label	City or Place Name
	Layer: Extended — Required: No — Repeatable: Yes
Definition:	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.
Details	IPTC terms for Adobe XMP have URIs that are not resolvable. Instead, visit IPTC Standard Photo Metadata (July 2010) for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Term Name: Iptc4xmpExt:Sublocation
Normative URI:	http://iptc.org/std/Iptc4xmpExt/2008-02-29/Sublocation
Label	Sublocation
	Layer: Core — Required: No — Repeatable: Yes
Definition:	Free-form text location details of the location of the subjects, down to the village, forest, or geographic feature etc., below the city or other place name, especially information that could not be found in a gazetteer.
Details	IPTC terms for Adobe XMP have URIs that are not resolvable. Instead, visit IPTC Standard Photo Metadata (July 2010) for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Comments:	We distinguish Locality in the sense of Darwin Core (= a complete description of a locality, with the possible exception of country names etc., which can be separated into dwc:HigherGeography), and Sublocation in the sense of IPTC/XMP, i.e. the further details below a city or other place name, of a free-form text location within a fully hierarchically arranged grouping (earlier IPTC versions used “Location”, but this has been renamed as of 2008).

Temporal Coverage Vocabulary

Term Name: dcterms:temporal
Normative URI:	http://purl.org/dc/terms/temporal
Label	Temporal Coverage
	Layer: Extended — Required: No — Repeatable: No
Definition:	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.
Details	dcterms:temporal
Comments:	Examples in English: "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 Creation 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.
Term Name: xmp:CreateDate
Normative URI:	http://ns.adobe.com/xap/1.0/CreateDate
Label	Original Date and Time
	Layer: Core — Required: No — Repeatable: No
Definition:	The date of the creation for 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, 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. AC datetime values may also follow 8601:2004 for ranges by separating two IS0 8601 datetime fields by a solidus ("forward slash", '/'). See also the wikipedia IS0 8601 entry for further explanation and examples.
Details	Terms for Adobe XMP have URIs that are not resolvable. Instead, visit XMP Specification Part 1, Sec 8.4 for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Comments:	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 for further explanation and examples.
Term Name: timeOfDay
Normative URI:	http://rs.tdwg.org/ac/terms/timeOfDay
Label	Time of Day
	Layer: Core — Required: No — Repeatable: No
Definition:	Free text information beyond exact clock times.
Details
Comments:	Examples in English: afternoon, twilight.

Subject of Resource Vocabulary

Term Name: physicalSetting
Normative URI:	http://rs.tdwg.org/ac/terms/physicalSetting
Label	Physical Setting
	Layer: Extended — 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. Constrained vocabulary of: "Natural" = Unmodified object in a natural setting of unmodified object (e. g. living organisms in their natural environment); "Artificial" = Unmodified object in an artificial environment (e. g. living organisms in an artificial environment such as a zoo, garden, greenhouse, or laboratory).
Details
Comments:	Multiple values may be needed for movies.
Term Name: Iptc4xmpExt:CVterm
Normative URI:	http://iptc.org/std/Iptc4xmpExt/2008-02-29/CVterm
Label	Subject Category
	Layer: Core — Required: No — Repeatable: Yes
Definition:	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 (without a URI). For terms from other vocabularies either a precise URI should be used, or, when providing unqualified terms, metadata should provide the source vocabulary using the Subject Category Vocabulary vocabulary term.
Details	IPTC terms for Adobe XMP have URIs that are not resolvable. Instead, visit IPTC Standard Photo Metadata (July 2010) for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Comments:	Recommended sets include: the NASA Global Change Master Directory (GCMD) ^[2], K2N ^[3], the BioComplexity Thesaurus^[4], the Description Type GBIF Vocabulary ^[5], the TDWG Species Profile Model ^[6], the Pinian Core ^[7] and the European Environmental Agency GEneral Multilingual Environmental Thesaurus(GEMET) ^[8]. 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: subjectCategoryVocabulary
Normative URI:	http://rs.tdwg.org/ac/terms/subjectCategoryVocabulary
Label	Subject Category Vocabulary
	Layer: Extended — Required: No — Repeatable: Yes
Definition:	Any vocabulary or formal classification from which terms in Subject Category have been drawn.
Details
Comments:	The AC recommended vocabularies do not need to be cited here. There is no 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: tag
Normative URI:	http://rs.tdwg.org/ac/terms/tag
Label	Tag
	Layer: Core — Required: No — Repeatable: Yes
Definition:	General keywords or tags.
Details
Comments:	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", "flower color" are especially desirable.

Taxonomic Coverage Vocabulary

Term Name: ncd:taxonCoverage
Normative URI:	http://rs.tdwg.org/ontology/voc/Collection#taxonCoverage
Label	Taxon Coverage
	Layer: Core — 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).
Details	http://rs.tdwg.org/ontology/voc/Collection#taxonCoverage
Comments:	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 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 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:scientificName
Normative URI:	http://rs.tdwg.org/dwc/terms/scientificName
Label	Scientific Taxon Name
	Layer: Core — Required: No — Repeatable: Yes
Definition:	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.
Details	dwc:scientificName
Comments:	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”).
Term Name: dwc:identificationQualifier
Normative URI:	http://rs.tdwg.org/dwc/terms/identificationQualifier
Label	Identification Qualifier
	Layer: Core — Required: No — Repeatable: Yes
Definition:	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 Name.
Details	dwc:identificationQualifier
Comments:	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 Name, some with, some without identification qualifiers, may have to be transferred with "cf." or "aff." qualifiers remaining embedded in the Scientific Taxon Name. For discussion of Darwin Core usage see here. Examples: 1) For the determinations “cf. Quercus agrifolia var. oxyadenia”, “Quercus cf. agrifolia var. oxyadenia”, “Quercus agrifolia cf. var. oxyadenia”, Scientific Taxon Name would always be “Quercus agrifolia var. oxyadenia”, with Identification Qualifier “cf. genus”, “cf. species” and “cf. var.”, respectively.
Term Name: dwc:vernacularName
Normative URI:	http://rs.tdwg.org/dwc/terms/vernacularName
Label	Common Name
	Layer: Core — Required: No — Repeatable: Yes
Definition:	Common (= vernacular) names of the subject in one or several languages. The ISO language name should be given in parentheses after the name if not all names are given by values of the Metadata Language term.
Details	dwc:vernacularName
Comments:	The ISO language codes 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);'.
Term Name: dwc:nameAccordingTo
Normative URI:	http://rs.tdwg.org/dwc/terms/nameAccordingTo
Label	Name According To
	Layer: Extended — Required: No — Repeatable: Yes
Definition:	The taxonomic authority used to apply the name to the taxon, e. g., a book or web service from which the name comes.
Details	dwc:nameAccordingTo
Comments:	Examples are "ITIS", "Catalogue of Life", "Peterson's guide for birds".
Term Name: dwc:scientificNameID
Normative URI:	http://rs.tdwg.org/dwc/terms/scientificNameID
Label	Scientific Name ID
	Layer: Extended — Required: No — Repeatable: Yes
Definition:	An identifier for the nomenclatural (not taxonomic) details of a scientific name.
Details	See dwc:scientificNameID and also the DwC Taxon attributes.
Term Name: scientificNameSynonym
Normative URI:	http://rs.tdwg.org/ac/terms/scientificNameSynonym
Label	Scientific Name Synonym
	Layer: Extended — Required: No — Repeatable: Yes
Definition:	One or several Scientific Taxon Names that are synonyms to the Scientific Taxon Name may be provided here.
Details
Comments:	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 deducedable from the AC record alone.
Term Name: dwc:identifiedBy
Normative URI:	http://rs.tdwg.org/dwc/terms/identifiedBy
Label	Identified By
	Layer: Extended — Required: No — Repeatable: Yes
Definition:	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.
Details	dwc:identifiedBy
Term Name: dwc:dateIdentified
Normative URI:	http://rs.tdwg.org/dwc/terms/dateIdentified
Label	Date Identified
	Layer: Extended — Required: No — Repeatable: No
Definition:	The date on which the person(s) given under Identfied By applied a Scientific Taxon Name to the resource.
Details	dwc:dateIndentified
Term Name: taxonCount
Normative URI:	http://rs.tdwg.org/ac/terms/taxonCount
Label	Taxon Count
	Layer: Core — 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).
Details
Comments:	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. The count should contain only the taxa covered fully or primarily by the resource. 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. This should be a single integer number. 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: subjectPart
Normative URI:	http://rs.tdwg.org/ac/terms/subjectPart
Label	Subject Part
	Layer: Extended — Required: No — Repeatable: Yes
Definition:	The portion of the organism, environment, etc. shown or particularly well illustrated.
Details
Comments:	No formal encoding scheme as yet exists. Examples are "whole body", "head", "flower", "leaf", "canopy" (of a rain forest stand). Several anatomical ontologies are emerging in http://www.obofoundry.org/
Term Name: dwc:sex
Normative URI:	http://rs.tdwg.org/dwc/terms/sex
Label	Subject Sex
	Layer: Extended — Required: No — Repeatable: Yes
Definition:	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.
Details
Term Name: dwc:lifeStage
Normative URI:	http://rs.tdwg.org/dwc/terms/lifeStage
Label	Subject Life Stage
	Layer: Extended — Required: No — Repeatable: Yes
Definition:	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.
Details	dwc:lifeStage
Term Name: subjectOrientation
Normative URI:	http://rs.tdwg.org/ac/terms/subjectOrientation
Label	Subject Orientation
	Layer: Extended — Required: No — Repeatable: Yes
Definition:	Specific orientiation (= direction, view angle) of the subject represented in the media resource with respect to the acquisition device.
Details
Comments:	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: dwc:preparations
Normative URI:	http://rs.tdwg.org/dwc/terms/preparations
Label	Subject Preparation Technique
	Layer: Extended — Required: No — Repeatable: No
Definition:	Free form text describing the techniques used to prepare the subject of the media, prior to or while creating the media resource.
Details	dwc:preparations
Comments:	Examples for such techniques are: Insect under CO₂, cooled to immobility, preservation with ethanol or formaldehyde. See also Resource Creation Technique for technical aspects of digital media object creation.

Resource Creation Vocabulary

Term Name: Iptc4xmpExt:LocationCreated
Normative URI:	http://iptc.org/std/Iptc4xmpExt/2008-02-29/LocationCreated
Label	Location Created
	Layer: Core — Required: No — Repeatable: Yes
Definition:	The location at which the media recording instrument was placed when the media was created.
Details	IPTC terms for Adobe XMP have URIs that are not resolvable. Instead, visit IPTC Standard Photo Metadata (July 2010) for further documentation. Note that XMP does not have an explicit XML-Schema. Rather, an "XMP Schema" is actually defined in RDF.
Comments:	The distinction between 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 Location Shown and Location Created 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: digitizationDate
Normative URI:	http://rs.tdwg.org/ac/terms/digitizationDate
Label	Date and Time Digitized
	Layer: Extended — 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. The date and time must comply with the World Wide Web Consortium (W3C) datetime practice, 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. AC datetime values may also follow 8601:2004 for ranges by separating two IS0 8601 datetime fields by a solidus ("forward slash", '/'). See also the wikipedia IS0 8601 entry for further explanation and examples.
Details
Comments:	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. 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. 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. Compare also MWG (2010)^[1], which has best practice advice on handling time-zone-less EXIF date/time data. See also the wikipedia IS0 8601 entry for further explanation and examples.
Term Name: captureDevice
Normative URI:	http://rs.tdwg.org/ac/terms/captureDevice
Label	Capture Device
	Layer: Extended — Required: No — Repeatable: No
Definition:	Free form text describing the device or devices used to create the resource.
Details
Comments:	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: resourceCreationTechnique
Normative URI:	http://rs.tdwg.org/ac/terms/resourceCreationTechnique
Label	Resource Creation Technique
	Layer: Extended — 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.
Details
Comments:	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 or expected to 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 to users are not necessary to document; examples of such practices include changing resolution, cropping, minor sharpening or overall color correction, and clearly perceptable 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.

Related Resources Vocabulary

Term Name: IDofContainingCollection
Normative URI:	http://rs.tdwg.org/ac/terms/IDofContainingCollection
Label	ID of Containing Collection
	Layer: Core — Required: No — Repeatable: Yes
Definition:	If the resource is contained in a Collection, this field identifies that Collection uniquely. Its form is not specified by this normative document, but is left to implementers of specific implementations.
Details
Comments:	Repeatable: A media resource may be member of multiple collections
Term Name: relatedResourceID
Normative URI:	http://rs.tdwg.org/ac/terms/relatedResourceID
Label	Related Resource ID
	Layer: Extended — 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
Details
Term Name: providerID
Normative URI:	http://rs.tdwg.org/ac/terms/providerID
Label	Provider ID
	Layer: Extended — Required: No — Repeatable: No
Definition:	A globally unique ID of the provider of the current AC metadata record.
Details
Comments:	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: derivedFrom
Normative URI:	http://rs.tdwg.org/ac/terms/derivedFrom
Label	Derived From
	Layer: Core — Required: No — Repeatable: Yes
Definition:	A reference to an original resource from which the current one is derived.
Details
Comments:	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). – Human readable, or doi number, or URL. Simple name of parent for human readable. Can be repeated if a montage of images.
Term Name: associatedSpecimenReference
Normative URI:	http://rs.tdwg.org/ac/terms/associatedSpecimenReference
Label	Associated Specimen Reference
	Layer: Core — Required: No — Repeatable: Yes
Definition:	A reference to a specimen associated with this resource.
Details
Comments:	Supports to find 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 could be a URI identifying a specimen record that is available online.
Term Name: associatedObservationReference
Normative URI:	http://rs.tdwg.org/ac/terms/associatedObservationReference
Label	Associated Observation Reference
	Layer: Core — Required: No — Repeatable: Yes
Definition:	A reference to an observation associated with this resource.
Details

Record-level Service Access Point Vocabulary

Term Name: hasServiceAccessPoint
Normative URI:	http://rs.tdwg.org/ac/terms/hasServiceAccessPoint
Label	Service Access Point
	Layer: Core — Required: No — Repeatable: Yes
Definition:	Reference to an object (the "access point") describing network access to the media resource, or related resource, that the AC metadata describes. What constitutes an object is dependent on the representation (e.g., XML Schema, RDF, etc.), but for full compliance such a representation must provide that any of the terms in the Service Access Point Terms section below can be applied to an access point.
Details	hasServiceAccessPoint is an attribute of the media being described, as are all other AC terms except those in the following section, which are properties of the access point object referenced by the Service Access Point. Depending on the specific model used, the value of hasServiceAccessPoint may be implemented through some form of nesting objects inside other objects, or through a unique identifier pointing to an access point object.
Comments:	Use with the Access Level Terms below. In particular, there is little point to using hasServiceAccessPoint if there is no value for the Access URI and perhaps the dcterms:format. Implementers in specific constraint languages such as XML Schema or RDF may wish to make those two properties mandatory on instances.

Access-level Terms

Access-level Service Access Point Vocabulary

These terms should be applied to a Service Access Point , not to the resource defined by the dcterms:identifier

Term Name: accessURI
Normative URI:	http://rs.tdwg.org/ac/terms/accessURI
Label	Access URI
	Layer: Core — Required: No — Repeatable: No
Definition:	A URI that uniquely identifies a service that provides a representation of the underlying resource. 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.
Details
Comments:	Value might point to something offline, such as a published CD, etc. For example, the doi of an published CD would be a suitable value.
Term Name: dcterms:format
Normative URI:	http://purl.org/dc/terms/format
Label	Format
	Layer: Core — Required: No — Repeatable: No
Definition:	The technical format of the resource (file format or physical medium).
Details	dcterms:format
Comments:	Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME]. This item 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.
Term Name: variant
Normative URI:	http://rs.tdwg.org/ac/terms/variant
Label	Variant
	Layer: Core — Required: No — Repeatable: Yes
Definition:	What this ServiceAccessPoint provides. Suggested values are "Thumbnail", "Trailer", "Lower Quality", "Medium Quality", "Good Quality", "Best Quality", "Offline"
Details
Comments:	Thumbnail: ServiceAccessPoint 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 the preview object. A typical size for a tiny thumbnail image may be 50-100 pixels in the longer dimension. Trailer: ServiceAccessPoint provides video clip preview, in the form of a specifically authored "Trailer", which may provide somewhat different content than the original resource. Lower Quality: ServiceAccessPoint provides a lower quality version of the media resource, suitable e. g. for web sites. Medium Quality: ServiceAccessPoint 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: ServiceAccessPoint 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: ServiceAccessPoint provides the highest available quality of the media resource, whatever its resolution or quality level. Offline: ServiceAccessPoint provides data about an offline resource.
Term Name: dcterms:extent
Normative URI:	http://purl.org/dc/terms/extent
Label	Extent
	Layer: Extended — Required: No — Repeatable: No
Definition:	The size, dimensions, or duration of the variant of the media resource.
Details	dcterms:extent
Comments:	Best practices are: Extent as length/running time should use standard abbreviations of the metadata language (for English "20 s", "54 min"). Extent of images or video may be given as pixel size ("2000 x 1500 px"), or as file size (using kB, kByte, MB, MByte).
Term Name: furtherInformationURL
Normative URI:	http://rs.tdwg.org/ac/terms/furtherInformationURL
Label	Further Information URL
	Layer: Extended — Required: No — Repeatable: No
Definition:	The URL of a Web site that provides additional information about (this version of) the media resource
Details
Term Name: licensingException
Normative URI:	http://rs.tdwg.org/ac/terms/licensingException
Label	Licensing Exception Statement
	Layer: Extended — 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.
Details
Comments:	Required only if this version has different licensing than that of the media resource. E. g. the highest resolution version may be more restricted than lower resolution versions
Term Name: serviceExpectation
Normative URI:	http://rs.tdwg.org/ac/terms/serviceExpectation
Label	Service Expectation
	Layer: Extended — Required: No — Repeatable: No
Definition:	A term that describes what service expectations users may have of the accessURL. 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.
Details
Term Name: variantDescription
Normative URI:	http://rs.tdwg.org/ac/terms/variantDescription
Label	Variant Description
	Layer: Extended — Required: No — Repeatable: No
Definition:	Text that describes this Service Access Point variant
Details

References

↑ ^1.0 ^1.1 (MWG 2010) Metadata Working Group Guidelines for Handling Image Metadata, Version 2.0,November 2010 http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf
↑ NASA Global Change Master Directory http://gcmd.nasa.gov/
↑ Subject Categories defined in Key to Nature: http://www.keytonature.eu/wiki/Subject_Category
↑ BioComplexity Thesaurus http://thesaurus.nbii.gov
↑ GBIF Description Types http://rs.gbif.org/vocabulary/gbif/description_type.xml
↑ Species Profile Model (http://rs.tdwg.org/ontology/voc/SPMInfoItems.rdf
↑ Plinian Core (http://www.gbif.es/plinian/doku.php)
↑ GEMET http://www.eionet.europa.eu/gemet

[MWG2010-1] 1.0 ^1.1 (MWG 2010) Metadata Working Group Guidelines for Handling Image Metadata, Version 2.0,November 2010 http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf

[2] NASA Global Change Master Directory http://gcmd.nasa.gov/

[3] Subject Categories defined in Key to Nature: http://www.keytonature.eu/wiki/Subject_Category

[4] BioComplexity Thesaurus http://thesaurus.nbii.gov

[5] GBIF Description Types http://rs.gbif.org/vocabulary/gbif/description_type.xml

[6] Species Profile Model (http://rs.tdwg.org/ontology/voc/SPMInfoItems.rdf

[7] Plinian Core (http://www.gbif.es/plinian/doku.php)

[8] GEMET http://www.eionet.europa.eu/gemet

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

Audubon Core Term List

Contents

Borrowed Vocabulary

Namespaces, Prefixes and Term Names

Vocabulary Indices

Term Index By Name

Term Index By Label

Record-level Terms

Management Vocabulary

Attribution Vocabulary

Agents Vocabulary

Content Coverage Vocabulary

Geography Vocabulary

Temporal Coverage Vocabulary

Subject of Resource Vocabulary

Taxonomic Coverage Vocabulary

Resource Creation Vocabulary

Related Resources Vocabulary

Record-level Service Access Point Vocabulary

Access-level Terms

Access-level Service Access Point Vocabulary

References

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Tools

Sister projects