Audubon Core dynamic term list
This page provides an overview of the Concepts in Audubon Core, grouped first by collections and then by Layer 1 and Layer 2:
Contents
- 1 Index to concepts (all collections combined)
- 2 Audubon Core Management Vocabulary
- 3 Audubon Core Record-Audubon Core level Service Access Point Vocabulary
- 4 Audubon Core Related Resources Vocabulary
- 5 Audubon Core Resource Creation Vocabulary
- 6 Audubon Core Service Access Point Vocabulary
- 7 Audubon Core Temporal Coverage Vocabulary
Index to concepts (all collections combined)
Audubon Core Management Vocabulary
Concept Name: | ac:hasServiceAccessPoint |
Normative URI | http://rs.tdwg.org/ac/terms/hasServiceAccessPoint |
Label | Service Access Point |
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 section Service Access Point Vocabulary. |
Defined By | http://terms.tdwg.org/wiki/Audubon_Core_Term_List#ac:hasServiceAccessPoint |
Required: No — Repeatable: No | |
Notes: | Audubon Core: Some serializations may flatten the model of service-access points by (a) dropping ac:hasServiceAccessPoint, ac:variant and ac:variantDescription, (b) repeating the properties of the Service Access Point Vocabulary and prefixing them with values of ac:variant. If such a flat serialization is necessary for services, we recommend to select from among terms 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. |
Concept Name: | ac:metadataLanguage |
Normative URI | http://rs.tdwg.org/ac/terms/metadataLanguage |
Label | Metadata Language |
Definition | Language of description and other metadata (but not necessarily of the image itself) represented in ISO639-1 or -3. |
Defined By | http://terms.tdwg.org/wiki/Audubon_Core_Term_List#ac:metadataLanguage |
Required: Yes — Repeatable: No | |
Concept Name: | ac:subtype |
Normative URI | http://rs.tdwg.org/ac/terms/subtype |
Label | Subtype |
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. |
Defined By | http://terms.tdwg.org/wiki/Audubon_Core_Term_List#ac:subtype |
Required: No — Repeatable: No | |
Concept Name: | dcterms:identifier |
Normative URI | http://purl.org/dc/terms/identifier |
Label | Identifier |
Definition | An unambiguous reference to the resource within a given context. |
Defined By | http://dublincore.org/documents/dcmi-terms/#terms-identifier |
Required: No — Repeatable: No | |
Notes: | Dublin Core: Recommended best practice is to identify the resource by means of a string conforming to a formal identification system. Audubon Core: An arbitrary code that is unique for the resource, with the resource being either a provider, collection, or media item. 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 UUID-number).
Required for media collections, No for media resources (but preferred if available). In context of GGBN used as gel image uri. |
Concept Name: | dcterms:title |
Normative URI | http://purl.org/dc/terms/title |
Label | Title |
Definition | A name given to the resource. |
Defined By | http://dublincore.org/documents/dcmi-terms/#terms-title |
Required: No — Repeatable: No | |
Notes: | Dublin Core: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
Audubon Core: 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. It is strongly suggested to provide a title for each media resource. 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”). |
Concept Name: | dcterms:type |
Normative URI | http://purl.org/dc/terms/type |
Label | Type |
Definition | A name given to the resource. |
Defined By | http://dublincore.org/documents/dcmi-terms/#terms-type |
Required: No — Repeatable: No | |
Concept Name: | xmp:MetadataDate |
Normative URI | http://ns.adobe.com/xap/1.0/MetadataDate |
Label | Metadata Date |
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. |
Defined By | http://www.adobe.com/content/dam/Adobe/en/devnet/xmp/pdfs/XMPSpecificationPart1.pdf |
Required: No — Repeatable: No | |
Notes: | Audubon Core: 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.
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. Note: URIs of Adobe XMP terms are not resolvable. Visit XMP Specification Part 1, Sec 8.4 for further documentation. XMP Schema is defined in RDF, not w3c schema. |
Concept Name: | xmp:Rating |
Normative URI | http://ns.adobe.com/xap/1.0/Rating |
Label | Rating |
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 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. |
Defined By | http://www.adobe.com/content/dam/Adobe/en/devnet/xmp/pdfs/XMPSpecificationPart1.pdf |
Required: No — Repeatable: No | |
Notes: | Audubon Core: A rating of the media resources, provided by users or editors, with -1 defining “rejected”, “0” defining “unrated”, and “1” (worst) to “5” (best).
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. Note: URIs of Adobe XMP terms are not resolvable. Visit XMP Specification Part 1, Sec 8.4 for further documentation. XMP Schema is defined in RDF, not w3c schema. |
Concept Name: | ac:comments |
Normative URI | http://rs.tdwg.org/ac/terms/comments |
Label | Comments |
Definition | Any comment provided on the media resource, as free-form text. Best practice would also identify the commenter. |
Defined By | |
Required: No — Repeatable: No | |
Notes: | Audubon Core: 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. |
Concept Name: | ac:providerManagedID |
Normative URI | http://rs.tdwg.org/ac/terms/providerManagedID |
Label | Provider-managed ID |
Definition | A free-form identifier (a simple number, an alphanumeric code, a URL, etc.) that is unique and meaningful primarily for the data provider. |
Defined By | |
Required: No — Repeatable: No | |
Notes: | Audubon Core: 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. |
Concept Name: | ac:reviewer |
Normative URI | http://rs.tdwg.org/ac/terms/reviewer |
Label | Reviewer |
Definition | If present, then resource is peer-reviewed, even if Reviewer 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). |
Defined By | |
Required: No — Repeatable: No | |
Notes: | Audubon Core: Provider is asserting they accept this review as competent. |
Concept Name: | ac:reviewerComments |
Normative URI | http://rs.tdwg.org/ac/terms/reviewerComments |
Label | Reviewer Comments |
Definition | Any comment provided by a reviewer with expertise in the subject, as free-form text. |
Defined By | |
Required: No — Repeatable: No | |
Notes: | Audubon Core: 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. |
Concept Name: | dcterms:available |
Normative URI | http://purl.org/dc/terms/available |
Label | Date Available |
Definition | Date (often a range) that the resource became or will become available. |
Defined By | http://dublincore.org/documents/dcmi-terms/#terms-available |
Required: No — Repeatable: No | |
Notes: | Audubon Core: 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.
|
Concept Name: | dcterms:modified |
Normative URI | http://purl.org/dc/terms/modified |
Label | Modified |
Definition | Date on which the resource was changed. |
Defined By | http://purl.org/dc/terms/ |
Required: No — Repeatable: No | |
Examples | Darwin Core: "1963-03-08T14:07-0600" is 8 Mar 1963 2:07pm in the time zone six hours earlier than UTC, "2009-02-20T08:40Z" is 20 Feb 2009 8:40am UTC, "1809-02-12" is 12 Feb 1809, "1906-06" is Jun 1906, "1971" is just that year, "2007-03-01T13:00:00Z/2008-05-11T15:30:00Z" is the interval between 1 Mar 2007 1pm UTC and 11 May 2008 3:30pm UTC, "2007-11-13/15" is the interval between 13 Nov 2007 and 15 Nov 2007. |
Audubon Core Record-Audubon Core level Service Access Point Vocabulary
- No concept defined yet for this collection.
Audubon Core Related Resources Vocabulary
Concept Name: | ac:associatedObservationReference |
Normative URI | http://rs.tdwg.org/ac/terms/associatedObservationReference |
Label | Associated Observation Reference |
Definition | A reference to an observation associated with this resource. |
Defined By | http://terms.tdwg.org/wiki/Audubon_Core_Term_List#ac:associatedObservationReference |
Required: No — Repeatable: No | |
Concept Name: | ac:associatedSpecimenReference |
Normative URI | http://rs.tdwg.org/ac/terms/associatedSpecimenReference |
Label | Associated Specimen Reference |
Definition | A reference to a specimen associated with this resource. |
Defined By | http://terms.tdwg.org/wiki/Audubon_Core_Term_List#ac:associatedSpecimenReference |
Required: No — Repeatable: No | |
Notes: | Audubon Core: 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. |
Concept Name: | ac:derivedFrom |
Normative URI | http://rs.tdwg.org/ac/terms/derivedFrom |
Label | Derived From |
Definition | A reference to an original resource from which the current one is derived. |
Defined By | http://terms.tdwg.org/wiki/Audubon_Core_Term_List#ac:derivedFrom |
Required: No — Repeatable: No | |
Notes: | Audubon Core: 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. |
Concept Name: | ac:IDofContainingCollection |
Normative URI | http://rs.tdwg.org/ac/terms/IDofContainingCollection |
Label | ID of Containing Collection |
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. |
Defined By | http://terms.tdwg.org/wiki/Audubon_Core_Term_List#ac:IDofContainingCollection |
Required: No — Repeatable: No | |
Notes: | Audubon Core: Repeatable: A media resource may be member of multiple collections |
Concept Name: | ac:providerID |
Normative URI | http://rs.tdwg.org/ac/terms/providerID |
Label | Provider ID |
Definition | A globally unique ID of the provider of the current AC metadata record. |
Defined By | |
Required: No — Repeatable: No | |
Notes: | Audubon Core: 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. |
Concept Name: | ac:relatedResourceID |
Normative URI | http://rs.tdwg.org/ac/terms/relatedResourceID |
Label | Related Resource ID |
Definition | Resource related in ways not specified through a collection, e.g. before-after images; time-lapse series; different orientations/angles of view |
Defined By | |
Required: No — Repeatable: No |
Audubon Core Resource Creation Vocabulary
Concept Name: | Iptc4xmpExt:LocationCreated |
Normative URI | http://iptc.org/std/Iptc4xmpExt/2008-02-29/LocationCreated |
Label | Location Created |
Definition | The location the content of the item was created. |
Defined By | http://www.iptc.org/std/photometadata/specification/IPTC-PhotoMetadata-201007_1.pdf |
Required: No — Repeatable: No | |
Notes: | IPTC Photo Metadata: If the location in the image is different from the location the photo was taken the IPTC Extension property Location Shown in the Image should be used.
Audubon Core: The location at which the media recording instrument was placed when the media was created. 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. Note: URIs of IPTC terms for Adobe XMP terms are not resolvable. Visit IPTC Standard Photo Metadata (July 2010) for further documentation. |
Concept Name: | ac:captureDevice |
Normative URI | http://rs.tdwg.org/ac/terms/captureDevice |
Label | Capture Device |
Definition | Free form text describing the device or devices used to create the resource. |
Defined By | |
Required: No — Repeatable: No | |
Examples | "Canon Supershot 2000", "Makroscan Scanner 2000", "Zeiss Axioscope with Camera IIIu", "SEM (Scanning Electron Microscope)". |
Notes: | Audubon Core: It is best practice to record the device; this may include a combination such as camera plus lens, or camera plus microscope. |
Concept Name: | ac:digitizationDate |
Normative URI | http://rs.tdwg.org/ac/terms/digitizationDate |
Label | Date and Time Digitized |
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. |
Defined By | |
Required: No — Repeatable: No | |
Concept Name: | ac:resourceCreationTechnique |
Normative URI | http://rs.tdwg.org/ac/terms/resourceCreationTechnique |
Label | Resource Creation Technique |
Definition | Information about technical aspects of the creation and digitization process of the resource. This includes modification steps ("retouching") after the initial resource capture. |
Defined By | |
Required: No — Repeatable: No | |
Notes: | Audubon Core: 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 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. |
Concept Name: | ac:subjectOrientation |
Normative URI | http://rs.tdwg.org/ac/terms/subjectOrientation |
Label | Subject Orientation |
Definition | Specific orientation ( = direction, view angle) of the subject represented in the media resource with respect to the acquisition device. |
Defined By | |
Required: No — Repeatable: No | |
Examples | "dorsal", "ventral", "frontal". |
Notes: | Audubon Core: 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. |
Audubon Core Service Access Point Vocabulary
Concept Name: | ac:accessURI |
Normative URI | http://rs.tdwg.org/ac/terms/accessURI |
Label | Access URI |
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. |
Defined By | http://terms.tdwg.org/wiki/Audubon_Core_Term_List#ac:accessURI |
Required: No — Repeatable: No | |
Notes: | 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. |
Concept Name: | ac:variant |
Normative URI | http://rs.tdwg.org/ac/terms/variant |
Label | Variant |
Definition | What this ServiceAccessPoint provides. Suggested values are "Thumbnail", "Trailer", "Lower Quality", "Medium Quality", "Good Quality", "Best Quality", "Offline" |
Defined By | http://terms.tdwg.org/wiki/Audubon_Core_Term_List#ac:variant |
Required: No — Repeatable: No | |
Notes: |
|
Concept Name: | dcterms:format |
Normative URI | http://purl.org/dc/terms/format |
Label | Format |
Definition | The file format, physical medium, or dimensions of the resource. |
Defined By | http://dublincore.org/documents/dcmi-terms/#terms-format |
Required: No — Repeatable: No | |
Notes: | Dublin Core: Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME].
Audubon Core: The technical format of the resource (file format or physical medium). 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. |
Concept Name: | ac:furtherInformationURL |
Normative URI | http://rs.tdwg.org/ac/terms/furtherInformationURL |
Label | Further Information URL |
Definition | The URL of a Web site that provides additional information about (this version of) the media resource |
Defined By | |
Required: No — Repeatable: No | |
Concept Name: | ac:licensingException |
Normative URI | http://rs.tdwg.org/ac/terms/licensingException |
Label | Licensing Exception Statement |
Definition | The licensing statement for this variant of the media resource if different from that given in the License Statement property of the resource. |
Defined By | |
Required: No — Repeatable: No | |
Notes: | Audubon Core: 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 |
Concept Name: | ac:serviceExpectation |
Normative URI | http://rs.tdwg.org/ac/terms/serviceExpectation |
Label | Service Expectation |
Definition | A term that describes what service expectations users may have of the ac: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. |
Defined By | |
Required: No — Repeatable: No | |
Concept Name: | ac:variantDescription |
Normative URI | http://rs.tdwg.org/ac/terms/variantDescription |
Label | Variant Description |
Definition | Text that describes this Service Access Point variant |
Defined By | |
Required: No — Repeatable: No | |
Concept Name: | dcterms:extent |
Normative URI | http://purl.org/dc/terms/extent |
Label | Extent |
Definition | The size or duration of the resource. |
Defined By | http://dublincore.org/documents/dcmi-terms/#terms-extent |
Required: No — Repeatable: No | |
Notes: | Audubon Core: The size, dimensions, or duration of the variant of the media resource. 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). |
Audubon Core Temporal Coverage Vocabulary
Concept Name: | ac:timeOfDay |
Normative URI | http://rs.tdwg.org/ac/terms/timeOfDay |
Label | Time of Day |
Definition | Free text information beyond exact clock times. |
Defined By | http://terms.tdwg.org/wiki/Audubon_Core_Term_List#ac:timeOfDay |
Required: No — Repeatable: No | |
Examples | Audubon Core: Examples in English: afternoon, twilight. |
Concept Name: | xmp:CreateDate |
Normative URI | http://ns.adobe.com/xap/1.0/CreateDate |
Label | Original Date and Time |
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, may make the file-system time arbitrarily different. |
Defined By | http://www.adobe.com/content/dam/Adobe/en/devnet/xmp/pdfs/XMPSpecificationPart1.pdf |
Required: No — Repeatable: No | |
Notes: | Audubon Core: 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.
What constitutes "original" is determined by the metadata author. Example case: 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. Note: URIs of Adobe XMP terms are not resolvable. Visit XMP Specification Part 1, Sec 8.4 for further documentation. XMP Schema is defined in RDF, not w3c schema. |
Concept Name: | dcterms:temporal |
Normative URI | http://purl.org/dc/terms/temporal |
Label | Temporal Coverage |
Definition | Temporal characteristics of the resource. |
Defined By | http://dublincore.org/documents/dcmi-terms/#terms-temporal |
Required: No — Repeatable: No | |
Examples | Audubon Core: Examples in English: "Jurassic", "Elizabethan", "Spring, 1957". 2008-01-01/2008-06-30. |
Notes: | Audubon Core: 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. 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. |