AudubonCore v1.0
→ Information about submission as TDWG standard
→ MRTG Wiki Homepage
→ Current Schema Draft. This version is under internal review as part of the submission to TDWG.
→ Audubon Core Non normative document
→ MRTG Development History
→ MRTG Meeting Notes
→ MRTG Best Practices
→ XML Schema representation of Audubon Core
→ RDF representation of Audubon Core
→ MediaWiki Help
Work in progress: Please do not edit this page while you see this. Expecting to finish by about when open for public comment. Until then consult Bob Morris before editing — BobMorris Last edit of page on: 2011-04-13
This page is Version 1.0 of the normative TDWG Multimedia Resources Metadata Standard, proposed to be designated The TDWG Audubon Core, formerly colloquially known as MRTG. During the TDWG period of public comment, please contribute at V1.0ForPublicComment. In addition you may see MRTG Development History for links to versions that includes the Task Group's comments during development and also the comments and responses to the TDWG internal review. The proposed normative text begins below this line.
If you are unfamiliar with the AudubonCore, please read the MRTG Non normative document before editing this page. It lays out why there is perceived a need for a biodiversity media resource metadata schema, and how we attempt to use existing metadata standards where possible. This page should be largely confined to discussion of what's missing, and what's good or bad about the specifications that are here. Critique of the architecture as a whole should be at MRTG Architecture
- Go here for Discussion of theXML Schema For MRTG. This is obsolete and will be revised for compliance with the normative version when it is approved.
- Go here for Discussion of the MRTG in RDF. This is obsolete and will be revised for compliance with the normative version when it is approved.
- TDWG09 MRTG WORKGROUP REPORT
1 Terminology of this specification
There are many ways to organize metadata specifications, particularly as to the nomenclature of the constituents of the metadata. In this document and the associated non-normative documentation, we will follow closely (sometimes verbatim) a portion of the Dublin Core Metadata Initiative (DCMI) metadata nomenclature as described in Section 2.3 of the DCMI Abstract Model (http://www.dublincore.org/documents/abstract-model/).
- A term is a metadata item that forms part of the description of a multimedia resource.
- A term has a type which is one of "Property" or "Class", We refer to a term of type Property as simply a Property, similarly for Class.
- A value is a resource - the physical, digital or conceptual entity or literal that is associated with a property when a property-value pair is used to describe a resource. Therefore, each value is either a literal value or a non-literal value.
- A literal value is a value which is a literal.
- A non-literal value is a value which is a physical, digital or conceptual entity.
- A literal is an entity which uses a Unicode string as a lexical form, together with an optional language tag or datatype, to denote a resource. In MRTG, the language tag appears as a value assigned to the metadata record.
- A Property is a term that has a value. The datatypes of values are specified in this document. Typically the values are either a member of a fixed set of literals, a URI, a numerical type, free text, or the datatype and values from an external controlled vocabulary referenced in the standard.
- A Class is a term that has a set of Properties. Thus, the values of the properties in this set define what it means for a resource (whether multimedia or not) to be a member of the class.. Typically if M is a resource and C is a class, we say "M is a C". We attempt to minimize the number of classes, because we want to support simple serializations, notably text files such as "Comma Separated Values" (CSV), in which structured representation is cumbersome or impossible.
- A Vocabulary is a set of terms.
- Multimedia Resource is anything that a provider identifies as belonging to one of the possible values of the MRTG Type term and one of the Subtype term values. A mechanism is provided by which providers can supply a privately defined subtype that will not collide with the MRTG defined Subtype values.
- A MRTG record is a set of terms with any property values conforming to this document, and which contain at least the six mandatory terms described below, and which describes a single multimedia resource (possibly including a Collection). One of these, the value of Identifier is a Globally Unique IDentifier (GUID), which may have been assigned to the resource by an external authority or by the provider of the metadata record.
- MRTG terms are devided into two Layers. Those characterised as in the Core Layer, including the six mandatory terms, should be meaningfully handled by all consuming clients applications. Only wholly complete consuming applications need handle those in the Extended Layer'.
Every MRTG term has a plain text Name, a URI, a plain text normative Definition and an optional "Comments" attribute. In addition, a term has an attribute telling whether it is mandatory, one telling whether it is repeatable, and one telling whether it is in the "Core" or "Extended" Layer. The Extended Layer comprises terms likely to only occur for certain media. For example, Date Available will apply only to media that are embargoed, but for which the provider is prepared to make the metadata immediately available. It is strongly recommended that consuming applications be able to meaningfully handle Core terms, and that only wholly complete consuming applications need handle Extended Layer terms. What is meant by "meaningfully handle" is up to implementers of this normative specification. It could be as simple as "gracefully ignore".
URI's for terms conform to the http URI scheme (See, http://en.wikipedia.org/wiki/URI_scheme, http://www.w3.org/TR/uri-clarification/, or http://www.ietf.org/rfc/rfc2396.txt ). Informally, one may understand this as follows: an http URI has the syntax of an http URL, but there is no expectation that putting it in a web browser will result in any information being returned to the browser, and if there is, it may have no relevance. This conformance requirement applies only to the URIs that identify MRTG terms. A few MRTG properties permit values to be taken from another controlled vocabulary chosen by the user. In this case, those values may involve URIs conforming to a scheme given by that external vocabulary, and MRTG is silent on what that scheme is.
Because http URIs are rather lengthy, MRTG documents follow a standard practice of introducing a short abbreviation comprising a "namespace qualifier" and a mnemonic name closely related to the term's Name. The result is known in XML parlance as a qualified name. For example the documentation below for the Identifier term renders its URI as " dcterms:identifier" but hovering over it will reveal that its actual URI is http://dublincore.org/documents/dcmi-terms/#identifier. In fact, most of the URIs for terms borrowed from external vocabularies (about half of them) do in fact resolve to something in relevant documentation for that external standard. Sometimes it is not precise because the documentation is a PDF document and several (different!) URIs might apparently resolve to the same place. Keep in mind that any fortuitous resolution of an http URI is not related to its use as an identifier, no matter how informative that resolution may be. That said, MRTG solicits discussion on the wiki at points where contributors find our association of a MRTG term with that from another standard as misleading or otherwise inappropriate.
2 Media Collections
MRTG metadata can describe either individual multimedia resources or collections of resources. A few, but not many, of the MRTG properties have different values for collections than for individual media. If no such distinction is mentioned, MRTG does not assume one.
3 Management Vocabulary
| Name: | Identifier |
| Normative URI: | dcterms:identifier [1] |
| 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. |
| Comments: | Recommend to follow dwc best practices. 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, and lsid-URI, and a GUID-number). |
| Crosswalk: | DublinCore: dcterms:identifier [1] — XMP: — DarwinCore: — NCD: ncd:collectionId[2] — Morphbank: URL with id — NBII: System ID — K2N: k2n:Resource_ID [3] — MIX2.0: mix2:BasicDigitalObjectInformation/ObjectIdentifier[4] |
| PublicComments: | {{{PublicComments}}} |
| Name: | Type |
| Normative URI: | dcterms:type [1] |
| 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. |
| 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. |
| Crosswalk: | DublinCore: dcterms:type [1] — XMP: — DarwinCore: — NCD: ncd:CollectionType[2] — Morphbank: — NBII: Type — K2N: k2n:Type [3] pro parte — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Subtype |
| Normative URI: |
→ Information about submission as TDWG standard |
| 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.
These values may either be used in their literal form, or with their full namespace, e. g.
→ Information about submission as TDWG standard |
| 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 mrtg namespace (for example, using "http://my.inst.org/namespace/metadata/subtype/repair-manual". Conforming applications may choose to ignore these. |
| Crosswalk: | DublinCore: dcterms:type [1] — XMP: — DarwinCore: — NCD: Collection->collectionType — Morphbank: — NBII: Type Details — K2N: k2n:Type [3] pro parte — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Title |
| Normative URI: | dcterms:title [1] |
| Layer: Core — Required: Yes — 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. |
| Comments: | The title facilitates interactions with humans: e.g. the title 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 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”). |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: dcterms:title [1] — Morphbank: — NBII: Title for media resource, or Collection Title for a collection, for Provider or institution it matches the Name/Roles pair combination — K2N: k2n:Title [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Modified |
| Normative URI: | dcterms:modified [1] |
| 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. |
| Comments: | dcterms:modified [1] permits all modification dates to be recorded, or if only one is recorded, it is assumed to be the latest. |
| Crosswalk: | DublinCore: Same as dcterms:modified [1] — XMP: xmp:ModifyDate[6] — DarwinCore: — NCD: dcterms:modified [1] — Morphbank: — NBII: Date Modified — K2N: k2n:Modified [3] — MIX2.0: mix2:ChangeHistory/ImageProcessing/dateTimeProcessed[4] |
| PublicComments: | {{{PublicComments}}} |
| Name: | Metadata Date |
| Normative URI: | xmp:MetadataDate[6] |
| 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. |
| Comments: | This is not dcterms:modified, which refers to the resource itself rather than its metadata. A use case is incremental harvesting: the holder of metadata who also holds the resources may be receiving metadata more frequently than the underlying resources; thus this date information may help a user harvesting the metadata to decide whether updating is necessary. |
| Crosswalk: | DublinCore: dcterms:modified [1] referring to a "metadata resource". — XMP: xmp:MetadataDate[6]. IPTC Extension 1.0 also provides IPTC Metadata Last Edited = http://iptc.org/std/Iptc4xmpExt/1.0/xmlns/IptcLastEdited [7] - which, however, seem to be limited to modifications of IPTC fields alone. — DarwinCore: — NCD: dcterms:modified [1] Collection->formationPeriod? — Morphbank: BaseObject.dateModified — NBII: Date Record Modified — K2N: k2n:Metadata_Modified [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Metadata Language |
| Normative URI: |
→ Information about submission as TDWG standard |
| 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. |
| Comments: | This is NOT dcterms:language [1], which is about the resource, not the metadata. This 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 MRTG object for each different MetadataLanguage, each such MRTG 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 a MRTG 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 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. |
| Crosswalk: | DublinCore: dcterms:language [1] referring to a "metadata resource". — XMP: — DarwinCore: — NCD: — Morphbank: "English" — NBII: Language of Cataloging — K2N: k2n:Metadata_Language [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Provider Managed ID |
| Normative URI: |
→ Information about submission as TDWG standard |
| 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. |
| 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 the project and help to locate individual data items in the provider's data repositories. It is the provider's decision whether to expose this value or not. |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: ncd:collectionId[2] — Morphbank: id — NBII: NA — K2N: k2n:Resource_ID [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Rating |
| Normative URI: | xmp:Rating[6] |
| 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). |
| 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. |
| Crosswalk: | DublinCore: — XMP: xmp:Rating[6] — DarwinCore: — NCD: — Morphbank: — NBII: NA — K2N: k2n:Rating [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Comments |
| Normative URI: |
→ Information about submission as TDWG standard |
| 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. |
| 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. |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: ncd:note[2] — Morphbank: — NBII: Outside Comments — K2N: not available — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Reviewer |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Extended — Required: No — Repeatable: No | |
| Definition: | If present, then resource is peer-reviewed, even if Reviewers Comments are lacking. The notation of 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). |
| Comments: | Provider is asserting they accept this review as competent. |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: Peer Reviewed (may change our item name to Reviewer) — K2N: k2n:Reviewer_Names [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Reviewer Comments |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Extended — Required: No — Repeatable: Yes | |
| Definition: | Any comment provided by a reviewer with expertise in the subject, as free-form text. |
| 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 false, without asserting a positive identification). There is a separate item “Comments” for text from commenters of unrecorded expertise. |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: PeerReviewerComments — K2N: k2n:Reviewer_Comments [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Date Available |
| Normative URI: | dcterms:available [1] |
| 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. |
| Comments: | A use case is, for example, that metadata, potentially including occurrence records, are published before even before the media are available, which are pending a formal publication elsewhere. |
| Crosswalk: | DublinCore: same as dcterms:available [1] — XMP: — DarwinCore: — NCD: — Morphbank: dateToPublish — NBII: Date Published — K2N: (not supported) — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Accrual Policy |
| Normative URI: | dcterms:accrualPolicy [1] |
| Layer: Extended — Required: No — Repeatable: No | |
| Definition: | A policy governing addition of items to a collection. Examples are planned deliverables and estimate for future changes. |
| Comments: | Although an important management item, the relevance of this to consumers of metadata is limited to specific cases; e. g., where the Accrual Policy specifies that data are available only for a limited period. |
| Crosswalk: | DublinCore: dcterms:accrualPolicy [1] — XMP: — DarwinCore: — NCD: ncd:developmentStatus[2] ? — Morphbank: — NBII: AccrualPolicy — K2N: (not supported) — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
4 Attribution Vocabulary
| Name: | Copyright Owner |
| Normative URI: | xmpRights:Owner[8] |
| Layer: Core — Required: Yes — Repeatable: No | |
| Definition: | The name of the owner of the copyright. 'Unknown' is an acceptable value. |
| Comments: | ALA uses dcterms:publisher [1] for this purpose, but it seems doubtful that the publisher is by necessity the copyright owner. Copyright owner cannot be repeated (only a single owner is possible). |
| Crosswalk: | DublinCore: dcterms:rights [1] or dcterms:rightsHolder [1] — XMP: xmpRights:Owner[8] type bag ProperName, "An unordered array specifying the legal owner(s) of a resource". — Note: IPTC Extension 1.0: also has Copyright Owner, using plus:CopyrightOwner [9] (Problem: Namespace for plus prefix is not given in the IPTC documents, and the plus = http://ns.useplus.org/ldf/vocab/ namespace does not contain a "CopyrightOwner" (but a CopyrightOwnerName, which may be appropriate here...) — DarwinCore: — NCD: — Morphbank: — NBII: contained within Rights Statement = — K2N: k2n:Copyright_Owner [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Copyright Statement |
| Normative URI: | dcterms:rights [1] |
| 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." Do not place just the name of the copyright holder here! |
| Comments: | This expresses rights over the media resource, not over the metadata text. |
| Crosswalk: | DublinCore: dcterms:rights [1] — XMP: related boolean term: xmpRights:Marked[8] type: Boolean, "Indicates that this is a rights-managed resource"; if this is false it indicates a resource in the public domain. — DarwinCore: — NCD: dcterms:rights [1] — Morphbank: — NBII: Rights — K2N: k2n:Copyright_Statement [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | License Statement |
| Normative URI: | xmpRights:UsageTerms[8] |
| 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. |
| 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, in License; “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 Creative Commons!) |
| Crosswalk: | DublinCore: dcterms:rights [1] — XMP: — DarwinCore: — NCD: ncd:usageRestrictions[2] — Morphbank: — NBII: License Statement — K2N: k2n:License Statement [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | License URL |
| Normative URI: | xmpRights:WebStatement[8] |
| 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). |
| 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 MRTG term “Licensing Exception Statement” supports variant-specific licenses. |
| Crosswalk: | DublinCore: dcterms:rights [1] — XMP: xmpRights:WebStatement[8] type: URL, defined as "The location of a web page describing the owner and/or rights statement for this resource." — DarwinCore: — NCD: ncd:usageRestrictions[2] — Morphbank: value is contained in Image.creativeCommons — NBII: License Statement — K2N: k2n:License_URL [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | License Logo URL |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: No | |
| Definition: | A URL providing access to a logo that symbolizes the License. |
| Comments: | The legal responsibility for choosing a correct graphical representation must lie with the provider of metadata and can not be assumed by a service that offers a search or reporting user-interface. Example:  |
| Crosswalk: | DublinCore: dcterms:rights [1] — XMP: — DarwinCore: — NCD: — Morphbank: value is contained in Image.creativeCommons — NBII: NA (added service on top of license statement) — K2N: — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Attribution Statement |
| Normative URI: | http://iptc.org/std/Iptc4xmpExt/1.0/xmlns/CreditLine [7] |
| Layer: Core — Required: No — Repeatable: No | |
| Definition: | free text for "please cite this as…" |
| Crosswalk: | Creative Commons with cc = http://creativecommons.org/ns# currently has the following properties: cc:attributionURL — "The URL to use when attributing this work" and cc:attributionName — "The creator's preferred name to use when attributing this work." — DublinCore: ? — XMP: — DarwinCore: — NCD: — Morphbank: info may be in Image.copyrightText — NBII: Credit line — K2N: k2n:Credit Line [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Attribution Logo URL |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: No | |
| Definition: | The URL of icon or logo image to appear in source attribution. |
| Comments: | Entering this URL into a browser should only result in the icon (not in a webpage including the icon). |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: — Morphbank: User.userLogo — NBII: MODs name/role combination for Contributing Partner - added service on top of name — K2N: k2n:Attribution Link URL [3]. K2N also has object logo, but defined as logo of resource (where a collection or institution is a resource. This does not apply here because of strict limitation to media. — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Attribution Link URL |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: No | |
| Definition: | The URL where information about ownership, attribution, etc. of the resource may be found. |
| 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. |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: Resource identifier — K2N: k2n:Attribution Link URL [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Published Source |
| Normative URI: | dcterms:source [1] |
| Layer: Core — Required: No — Repeatable: Yes | |
| Definition: | An identifiable source from which the described resources was derived. It may be digital, but in any case should be a source for which the originator intended long-term availability. |
| 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: (“digitally-published://ISBN=961-90008-7-0”) if this resource is also described separately in the data exchange. Can be repeatable if a montage of images. |
| Crosswalk: | DublinCore: dcterms:source [1] — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: Source — K2N: k2n:Published_Source [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
5 Agents Vocabulary
| Name: | Creator |
| Normative URI: | dcterms:creator [1] |
| Layer: Core — Required: No — Repeatable: Yes | |
| Definition: | The person or organization responsible for creating the media resource |
| Comments: | * The value may be simple text or
|
| Crosswalk: | Morphbank = Image.photographer — DublinCore: dcterms:creator [1] — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: MODS name/role Creator — K2N: k2n:Creators [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Provider |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: No | |
| Definition: | Person or organization responsible for presenting the media resource. If no separate Metadata Provider is attributed, this attributes also the metadata. |
| 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. |
| Crosswalk: | Derived from ISO NAP Metadata CI_ResponsibleParty — DublinCore: dcterms:creator [1] — XMP: — DarwinCore: (InstitutionCode is closest match) — NCD: — Morphbank: Contributor (Image.userId) — NBII: Mods Name/Role Contributing Partner — K2N: k2n:Service Attribution URI [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Metadata Provider |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: Yes | |
| Definition: | Person or organization originally responsible for |
| 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. |
| Crosswalk: | Derived from ISO NAP Metadata CI_ResponsibleParty — DublinCore: dcterms:creator [1] — XMP: — DarwinCore: — NCD: — Morphbank: morphbank.net — NBII: MODS name/role Metadata Contributor? — K2N: k2n:Metadata Provider [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Metadata Creator |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: Yes | |
| Definition: | Person or organization originally creating the resource metadata record. |
| Crosswalk: | Derived from ISO NAP Metadata CI_ResponsibleParty — DublinCore: dcterms:creator [1] — XMP: — DarwinCore: — NCD: — Morphbank: morphbank.net — NBII: MODS name/role Metadata Contributor? — K2N: k2n:Metadata Provider [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
6 Content Coverage Vocabulary
| Name: | Description |
| Normative URI: | dcterms:description [1] |
| 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 a MRTG 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. |
| 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. |
| Crosswalk: | DublinCore: dcterms:description [1] — XMP: — DarwinCore: — NCD: dcterms:description [1] — Morphbank: description — NBII: Description — K2N: k2n:Description [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Caption |
| Normative URI: |
→ Information about submission as TDWG standard |
| 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). |
| Comments: | Often only one of description or caption is present; choose the concept most appropriate for your metadata. |
| Crosswalk: | DublinCore: dcterms:description [1] — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: NA — K2N: k2n:Caption [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Language |
| Normative URI: | dcterms:language [1] |
| Layer: Core — Required: No — Repeatable: Yes | |
| Definition: | Language(s) of resource itself represented in ISO639-1 or -3 |
| 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-x-taxon" (do not use the incorrect “la” for Latin). If there is no language code available, you must use the ISO extension mechanisms (x-XXX or XXXXXXX, CITE). |
| Crosswalk: | DublinCore: dcterms:language [1] — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: language — K2N: k2n:Language [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
7 Geography Vocabulary
Location created and Location shown are separated in the current version of IPTC, and the metadata working group (MWG 2008) 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 MRTG 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, LocationShown should exclusively refer to the location where a specimen was originally collected (gathering or sampling location). Use LocationCreated to express the location where the media was created (a specimen was digitized).
All geography terms from the DarwinCore version of 12 09 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 dwcterms: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 Acquired
| Name: | Location Shown |
| Normative URI: | http://iptc.org/std/Iptc4xmpExt/1.0/xmlns/LocationShown [7] |
| Layer: Core — Required: No — Repeatable: Yes | |
| Definition: | The location that is shown or the place of the media content, irrespective of the location from which the resource has been created. |
| Crosswalk: | DublinCore: dcterms:coverage [1] — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: — K2N: (K2N is flat and does not support classes) — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | World Region |
| Normative URI: | http://iptc.org/std/Iptc4xmpExt/1.0/xmlns/WorldRegion [7] |
| 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 (to be defined). |
| Comments: | |
| Crosswalk: | DublinCore: dcterms:coverage [1] — XMP: — DarwinCore: dwc:continent[10] or dwc:waterbody[10] or dwc:IslandGroup[10] or dwc:island[10] — NCD: — Morphbank: — NBII: Continent/Ocean — K2N: k2n:World Region [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Country Code |
| Normative URI: | http://iptc.org/std/Iptc4xmpExt/1.0/xmlns/CountryCode [7] |
| 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"). |
| 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. |
| Crosswalk: | DublinCore: dcterms:coverage [1] — XMP: — DarwinCore: dwc:countryCode[10] — NCD: Collection->spatialCoverage? — Morphbank: — NBII: Country? — K2N: k2n:Country_Codes [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Country Name |
| Normative URI: | http://iptc.org/std/Iptc4xmpExt/1.0/xmlns/CountryName [7] |
| Layer: Core — Required: No — Repeatable: Yes | |
| Definition: | This field can be free text, but where possible, the use of http://iptc.org/std/Iptc4xmpExt/1.0/xmlns/CountryCode [7] is preferred. |
| Crosswalk: | DublinCore: dcterms:coverage [1] — XMP: — DarwinCore: dwc:country[10] — NCD: — Morphbank: Locality.country — NBII: Country — K2N: k2n:Country_Names [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Province or State |
| Normative URI: | http://iptc.org/std/Iptc4xmpExt/1.0/xmlns/ProvinceState [7] |
| 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). |
| Crosswalk: | DublinCore: dcterms:coverage [1] — XMP: — DarwinCore: dwc:stateProvince[10] — NCD: Collection->spatialCoverage? — Morphbank: Locality.state — NBII: state or province — K2N: k2n:State_or_Province [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | County or Subprovince |
| Normative URI: | dwc:county[10] |
| Layer: Extended — Required: No — Repeatable: Yes | |
| Definition: | The Counties, subprovinces, or sub-administrative units in which the subjects of the media were located. |
| Crosswalk: | DublinCore: dcterms:coverage [1] — XMP: — DarwinCore: dwc:county[10] — NCD: Collection->spatialCoverage? — Morphbank: Locality.county — NBII: county or subprovince — K2N: k2n:County_or_Subprovince [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | City or Place Name |
| Normative URI: | http://iptc.org/std/Iptc4xmpExt/1.0/xmlns/City [7] |
| 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. |
| Crosswalk: | DublinCore: dcterms:coverage [1] — XMP: — DarwinCore: (no equivalent in DarwinCore seems to exist) — NCD: Collection->spatialCoverage? — Morphbank: — NBII: city or place name — K2N: k2n:City or Place Name [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Sublocation |
| Normative URI: | http://iptc.org/std/Iptc4xmpExt/1.0/xmlns/Sublocation [7] |
| 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. |
| Comments: | We distinguish Locality in the sense of dwc (= 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). |
| Crosswalk: | DublinCore: dcterms:coverage [1] — XMP: — DarwinCore: related to dwc:location[10], but dwc:location may be a complete location, while sublocation is the remainder in a hierarchy — NCD: — Morphbank: — NBII: Locality — K2N: (not supported, compare Location) — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
8 Temporal Coverage Vocabulary
| Name: | Temporal Coverage |
| Normative URI: | dcterms:temporal [1] |
| Layer: Extended — Required: No — Repeatable: No | |
| Definition: | The 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. |
| 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. |
| Crosswalk: | DublinCore: dcterms:temporal [1] — XMP: — DarwinCore: dwc:earliestDateCollected[10] and dwc:latestestDateCollected[10] — NCD: ncd:temporalCoverage[2] — Morphbank: — NBII: Temporal Coverage — K2N: not available yet — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Original Date and Time |
| Normative URI: | xmp:CreateDate[6] |
| 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. |
| Comments: | What is 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.
|
| Crosswalk: | DublinCore: dcterms:date [1] — XMP: — DarwinCore: — NCD: Collection->temporalCoverage? — Morphbank: — NBII: Date Original — K2N: k2n:Original_Creation_Date [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Time of Day |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: No | |
| Definition: | Free text information beyond exact clock times. |
| Comments: | Examples in English: afternoon, twilight. |
| Crosswalk: | DublinCore: dcterms:date [1] — XMP: — DarwinCore: dwc:startTimeOfday[10] and dwc:endTimeOfDay[10] — NCD: — Morphbank: — NBII: Time of Day — K2N: (not available) — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
9 Subject of Resource Vocabulary
| Name: | Physical Setting |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Extended — Required: No — Repeatable: Yes | |
| Definition: | The Setting of the content represented in a medium like images, sounds, movies. 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 artificial setting of (e. g. living organisms in artificial environment: Zoo, Garden, Greenhouse, Laboratory; photographic background or background sound suppression). "Irrelevant" (e. g. background of Museum shots). |
| Comments: | Multiple values may be needed for movies. |
| Crosswalk: | DublinCore: dcterms:subject [1] — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: Nature of Content (in part) — K2N: — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Subject Category |
| Normative URI: | http://iptc.org/std/Iptc4xmpExt/1.0/xmlns/CVterm [7] |
| 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. MRTG-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, to provide the source vocabulary in Subject Category Vocabulary. |
| Comments: | Recommended sets include: tha NASA Global Change Master Directory (GCMD) [11], K2N [12], the BioComplexity Thesaurus[13], and the European Environmental Agency GEneral Multilingual Environmental Thesaurus(GEMET) [14]. The vocabulary may include major taxonomic groups (such as “vertebrates” or “fungi”) or ecosystem terms (“savannah”, “temperate rain forest”, “forest fires”, “aquatic vertebrates”). In the case where the unqualified terms from different vocabularies are homographs, the MRTG recommendation provides an order of preference for assigning terms to specific vocabularies. This includes other formal classifications (published in print or online) such as habitat, fuel, invasive species, agroproductivity, fisheries, migratory species etc. |
| Crosswalk: | DublinCore: dcterms:subject [1] — XMP: — DarwinCore: — NCD: Collection->taxonCoverage? — Morphbank: — NBII: Controlled subject; Formal Classification — K2N: k2n:Subject Category [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Subject Category Vocabulary |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Extended — Required: No — Repeatable: Yes | |
| Definition: | Any vocabulary or formal classification from which terms in Subject Category have been drawn. |
| Comments: | The MRTG 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. |
| Crosswalk: | DublinCore: dcterms:subject [1] — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: Formal Classification Source (plus the BioComplexity Thesaurus) — K2N: not available — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Tag |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: Yes | |
| Definition: | General keywords or tags. |
| Comments: | Tags may be multi-worded phrases. Where scientific names, common names, geographic locations, etc. are separable, these should go into the more specific metadata items provided further below. Examples: "flower diagram". Character or part keywords like "leaf", "flower color" are especially desirable. |
| Crosswalk: | DublinCore: dcterms:subject [1] — XMP: — DarwinCore: — NCD: — Morphbank: View.specimenPart — NBII: Uncontrolled Subject — K2N: k2n:General Keywords [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
10 Taxonomic Coverage Vocabulary
| Name: | Taxon Coverage |
| Normative URI: | ncd:taxonCoverage[2] |
| 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). |
| 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[2], which specifies at the Family level or higher. For collections it is recommended to follow ncd:taxonCoverage[2] to avoid conflicts between a MRTG record and a record arising from NCD. If the resource contains a single taxon, this should be placed in Scientific 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 Name is Quercus alba then Taxon Coverage, if provided at all, should be Quercus. |
| Crosswalk: | DublinCore: dcterms:subject [1] (not coverage!) — XMP: — DarwinCore: — NCD: ncd:taxonCoverage[2] — Morphbank: Specimen.scientificName — NBII: NA — K2N: k2n:Taxonomic Coverage [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Scientific Name |
| Normative URI: | dwc:scientificName[10] |
| Layer: Core — Required: No — Repeatable: Yes | |
| Definition: | Scientific taxon names of organisms represented in the media resource (with date and authorship information if available) of the lowest level taxonomic rank that can be applied. |
| Comments: | The Scientific Name may possibly be a Genus or Family name, if this is the most specific identification available. Where multiple taxa are the subject, multiple names may be given. If possible, add this information here even if the title or caption of the resource already contains scientific names. Where the list of scientific 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, please do not repeat 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 Name = “Abies cf. alba” and Identification Qualifier = “cf.”). |
| Crosswalk: | DublinCore: dcterms:subject [1] — XMP: — DarwinCore: dwc:scientificName[10] — NCD: Collection->taxonCoverage? — Morphbank: Specimen.scientificName — NBII: Scientific Name — K2N: k2n:Scientific Names [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Identification Qualifier |
| Normative URI: | dwc:identificationQualifier[10] |
| 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 about the identification given in Scientific Name. |
| Comments: | Examples: 1) For the determinations “cf. Quercus agrifolia var. oxyadenia”, “Quercus cf. agrifolia var. oxyadenia”, “Quercus agrifolia cf. var. oxyadenia”, Scientific Name would always be “Quercus agrifolia var. oxyadenia”, with Identification Qualifier “cf. genus”, “cf. species” and “cf. var.”, respectively. For discussion of Darwin Core usage see http://code.google.com/p/darwincore/wiki/Identification |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: dwc:identificationQualifier[10] — NCD: — Morphbank: — NBII: — K2N: — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Common Name |
| Normative URI: | dwc:vernacularName[10] |
| 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 in Metadata Language. |
| Comments: | Applicable only if the resource relates to a single taxon. 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);'. |
| Crosswalk: | DublinCore: dcterms:subject [1] — XMP: — DarwinCore: — NCD: ncd:commonNameCoverage[2] — Morphbank: — NBII: Common Name — K2N: k2n:Common Names [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Taxon According To |
| Normative URI: | dwc:taxonAccordingTo[10] |
| 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 from. |
| Comments: | Examples are "ITIS", "Catalogue of Life", "Peterson's guide for birds". |
| Crosswalk: | DublinCore: dcterms:subject [1] — XMP: — DarwinCore: dwc:taxonAccordingTo[10] — NCD: — Morphbank: Tree.nameSource — NBII: Scientific Name Source — K2N: not supported — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Scientific Name GUID |
| Normative URI: | dwc:taxonID[10] |
| Layer: Extended — Required: No — Repeatable: Yes | |
| Definition: | Equivalent to Scientific Name, but using GUIDs such to refer to the taxon names or concepts. |
| Crosswalk: | DublinCore: dcterms:subject [1] — XMP: — DarwinCore: dwc:taxonID[10] — NCD: — Morphbank: Tree.tsn — NBII: TSN — K2N: not supported — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Scientific Name Synonym |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Extended — Required: No — Repeatable: Yes | |
| Definition: | One or several scientific names that are synonyms to the Scientific Name may be provided here. |
| 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 Names are given, the association between synonym and name is not discoverable. |
| Crosswalk: | DublinCore: dcterms:subject [1] — XMP: — DarwinCore: (implemented through record relations and TaxonomicStatus) — NCD: — Morphbank: — NBII: NA — K2N: k2n:Scientific Name Synonyms [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Identified By |
| Normative URI: | dwc:identifiedBy[10] |
| Layer: Extended — Required: No — Repeatable: Yes | |
| Definition: | The name(s) of the person(s) who applied the Scientific Name to the sample. |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: dwc:identifiedBy[10] — NCD: — Morphbank: Specimen.name — NBII: NA — K2N: k2n:Identified By [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Date Identified |
| Normative URI: | dwc:dateIdentified[10] |
| Layer: Extended — Required: No — Repeatable: No | |
| Definition: | The date on which the person(s) given under Identfied By applied a Scientific Name to the resource. |
| Comments: | What happens if there is more than 1 taxon on the media resource? --BobMorris 18:50,30 February 2010 (CEST) |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: dwc:dateIdentified[10] — NCD: — Morphbank: Specimen.dateIdentified — NBII: NA — K2N: not available — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Taxon Count |
| Normative URI: |
→ Information about submission as TDWG standard |
| 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). |
| 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. |
| Crosswalk: | DublinCore: dcterms:subject [1] — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: NA — K2N: k2n:Taxon Count [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Subject Part |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Extended — Required: No — Repeatable: Yes | |
| Definition: | The portion of the organism, environment, etc. shown or particularly well illustrated. |
| Comments: | No formal encoding scheme as yet exists. Examples are "whole body", "head", "flower", "leaf", "canopy" (of a rain forest stand).
|
| Crosswalk: | DublinCore: dcterms:subject [1] — XMP: — DarwinCore: — NCD: — Morphbank: View.specimenPart — NBII: Part of Subject — K2N: k2n:Subject Part [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Subject Sex |
| Normative URI: | dwc:sex[10] |
| 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. |
| Crosswalk: | DublinCore: dcterms:subject [1] — XMP: — DarwinCore: dwc:Sex[10] — NCD: — Morphbank: Specimen.sex, View.sex — NBII: Sex — K2N: k2n:Subject Sex [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Subject Life Stage |
| Normative URI: | dwc:lifeStage[10] |
| 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. |
| Crosswalk: | DublinCore: dcterms:subject [1] — XMP: — DarwinCore: dwc:lifeStage[10] — NCD: — Morphbank: Specimen.developmentalStage, View.developmentalStage — NBII: Stage — K2N: k2n:Subject Life Stage [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Subject Orientation |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Extended — Required: No — Repeatable: No | |
| Definition: | Specific orientiation (= direction, view angle) of the subject represented in the media resource with respect to the acquisition device. |
| Comments: | Examples: "dorsal", "ventral", "frontal", etc. No formal encoding scheme as yet exists. |
| Crosswalk: | DublinCore: dcterms:subject [1] — XMP: — DarwinCore: — NCD: — Morphbank: View.viewAngle — NBII: View of Subject — K2N: k2n:Subject Orientation [3] — MIX2.0: mix2:ImageCaptureMedadata/orientation[4] |
| PublicComments: | {{{PublicComments}}} |
| Name: | Subject Preparation Technique |
| Normative URI: | dwc:preparations[10] |
| Layer: Extended — Required: No — Repeatable: No | |
| Definition: | Free form text describing the techniques used to prepare the subject prior or while creating the media resource. |
| Comments: | Examples for such techniques are: Insect under CO2, cooled to immobility, preservation with ethanol or formaldehyde. See also Resource Creation Technique for technical aspects of digital media object creation. |
| Crosswalk: | DWC= dwc:preparations[10] — DublinCore: — XMP: — DarwinCore: — NCD: — Morphbank: View.imagingPreparationTechnique and maybe Specimen.preparationTechnique — NBII: Comments on Collection; Capture Details — K2N: k2n:Creation Technique [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
11 Resource Creation Vocabulary
| Name: | Location Created |
| Normative URI: | http://iptc.org/std/Iptc4xmpExt/1.0/xmlns/LocationCreated [7] |
| Layer: Core — Required: No — Repeatable: Yes | |
| Definition: | The location at which the media recording instrument was placed when the media was created. |
| 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, MRTG is silent about whether the provided one entails the other. A best practices document for a particular MRTG implementation might address this. |
| Crosswalk: | DublinCore: dcterms:coverage [1] — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: — K2N: (K2N is flat and does not support classes) — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Date and Time Digitized |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Extended — Required: No — Repeatable: No | |
| Definition: | Date the first digital version was created, where different Date and Time Original (e. g. where photographic prints have been scanned). 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. |
| Comments: | This is often not the file creation or modification date. 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, exif GPSDateStamp and GPSTimeStamp may be relevant as these include time-zone information. Compare also MWG (2008), which has best practice on handling time-zone-less EXIF date/time data. |
| Crosswalk: | For digital cameras, this maps to the exif capture date — DublinCore: — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: Date Digital — K2N: k2n:Digitization_Date [3] — MIX2.0: mix2:ImageCaptureMetadata/GeneralCaptureInformation/dateTimeCreated[4] |
| PublicComments: | {{{PublicComments}}} |
| Name: | Capture Device |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Extended — Required: No — Repeatable: No | |
| Definition: | Free form text describing the device or devices used to create the resource. |
| 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)". |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: — Morphbank: View.imagingTechnique — NBII: capture device, capture detail — K2N: — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Resource Creation Technique |
| Normative URI: |
→ Information about submission as TDWG standard |
| 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. |
| 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 expected include changing resolution, cropping, minor sharpening or overall color correction, clearly perceptable modifications (adding arrows or labels, combination or 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. |
| Crosswalk: | DublinCore: dcterms:description [1] — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: Digitization Technique — K2N: replace this — MIX2.0: mix2:ImageCaptureMetadata/methodology[4] |
| PublicComments: | {{{PublicComments}}} |
12 Service Access Point Vocabulary
See Discussion at ServiceAccessPoint especially as to whether Class structure is correct. --BobMorris 04:10, 15 August 2009 (CEST)
12.1 ServiceAccessPoint Class
| Name: | Access Point |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: Yes | |
| Definition: | reference to an instance of a class describing network access to the media resource, or related resources, that the metadata describes. What constitutes a class is dependent on the representation (i.e. XML Schema, RDF, etc.) |
| Comments: | Use with the properties below. In particular, there is little point to having an instance of this class without a value for the Access URL and perhaps the Format. Implementers in specific constraint languages such as XML Schema or OWL may wish to make those two properties mandatory on instances. |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: — K2N: — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
12.2 Service Access Point Properties
| Name: | Access URL |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: No | |
| Definition: | URL of the resource itself. 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. |
| Comments: | For individual resources only. Use this field if only one quality level is available (as it is typical for taxon pages or keys!) Value might point to something offline, such as a published CD, etc. For example, the doi of an published CD would be a suitable |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: — Morphbank: http://www.morphbank.net/?id=XX&imgType=orig — NBII: Resource ID, (QualityLevel)URL — K2N: (QualityLevel)URL — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Format |
| Normative URI: | dcterms:format [1] |
| Layer: Core — Required: No — Repeatable: No | |
| Definition: | The technical format of the resource (file format or physical medium). |
| 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 acceptable: (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. |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: ncd:digitalFormat[2] or ncd:digitalMedium[2] — Morphbank: Image.imageType — NBII: File Format — K2N: (QualityLevel) Format — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Variant |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: Yes | |
| Definition: | What this ServiceAccessPoint provides. Permitted values are "Thumbnail", "Trailer", "Lower Quality", "Medium Quality", "Good Quality", "Best Quality", "Offline" |
| Comments: | *Thumbnail: ServiceAccessPoint provides a thumbnail image, short sound clip, or short movie clip that can be used 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.
|
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: — K2N: — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Extent |
| Normative URI: | dcterms:extent [1] |
| Layer: Extended — Required: No — Repeatable: No | |
| Definition: | The size, dimensions, or duration of the variant of the media resource. |
| 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). |
| Crosswalk: | ORE:Extent — DublinCore: dcterms:extent [1] (refines dcterms:format [1]) — XMP: — DarwinCore: — NCD: — Morphbank: Image.imageWidth, Image.imageHeight — NBII: extent — K2N: (QualityLevel) Extent — MIX2.0: mix2:BasicImageInformation/BasicImageCharacteristics/imageWidth, and imageHeight[4] |
| PublicComments: | {{{PublicComments}}} |
| Name: | Further Information URL |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Extended — Required: No — Repeatable: No | |
| Definition: | The URL of a Web site that provides additional information about (this version of) the media resource |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: — K2N: under consideration — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Licensing Exception Statement |
| Normative URI: |
→ Information about submission as TDWG standard |
| 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 |
| 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 |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: — K2N: under consideration — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Service Expectation |
| Normative URI: |
→ Information about submission as TDWG standard |
| 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. |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: — K2N: Availability — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Variant Description |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Extended — Required: No — Repeatable: No | |
| Definition: | Text that describes this Service Access Point variant |
| Crosswalk: | DublinCore: — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: — K2N: considered detrimental, blurring the distinction between multiple (related) resources and versions of a single resource — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
13 Related Resources Vocabulary
| Name: | ID of Containing Collection |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: No | |
| 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. |
| Crosswalk: | DublinCore: dcterms:relation [1] — XMP: — DarwinCore: — NCD: — Morphbank: URL for collection id, if present — NBII: Other Related Resources (in part) — K2N: k2n:Collection Reference By ID [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Related Resource ID |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Extended — Required: No — Repeatable: No | |
| Definition: | Resource related in ways not specified through a collection.
|
| Crosswalk: | DublinCore: dcterms:relation [1] — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: — K2N: none — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Provider ID |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Extended — Required: No — Repeatable: No | |
| Definition: | A globally unique ID of the provider of the current MRTG metadata record. |
| 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. - |
| Crosswalk: | DublinCore: dcterms:relation [1] — XMP: — DarwinCore: — NCD: ncd:institutionId[2] — Morphbank: URL for group — NBII: see MARC Name/Roles - specific combinations — K2N: k2n:XXX [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Derived From |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: Yes | |
| Definition: | A reference to an original resource from which the current one is derived. |
| 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 repeatedable if a montage of images. |
| Crosswalk: | DublinCore: dcterms:relation [1] — XMP: xmpMM:[15], which however has a special document identifier scheme of document, instance and version IDs. — DarwinCore: — NCD: — Morphbank: — NBII: Source, also Related Media — K2N: k2n:Derived_From [3] — MIX2.0: mix2:ChangeHistory/ImageProcessing/sourceData[4] |
| PublicComments: | {{{PublicComments}}} |
| Name: | Associated Specimen Reference |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: No | |
| Definition: | a reference to a specimen associated with this resource. |
| 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 online available. |
| Crosswalk: | DublinCore: dcterms:relation [1] — XMP: — DarwinCore: — NCD: — Morphbank: Image.specimenId — NBII: Specimen ID — K2N: k2n:XXX [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
| Name: | Associated Observation Reference |
| Normative URI: |
→ Information about submission as TDWG standard |
| Layer: Core — Required: No — Repeatable: No | |
| Definition: | A reference to an observation associated with this resource. |
| Crosswalk: | DublinCore: dcterms:relation [1] — XMP: — DarwinCore: — NCD: — Morphbank: — NBII: Other Related Resources — K2N: k2n:XXX [3] — MIX2.0: |
| PublicComments: | {{{PublicComments}}} |
14 Controlled Vocabularies
In several cases MRTG requires or recommends controlled vocabularies. In addition to being referenced in the respective fields, we provide some links to analyses here.
15 References
- ↑ 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 1.19 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 1.31 1.32 1.33 1.34 1.35 1.36 1.37 1.38 1.39 1.40 1.41 1.42 1.43 1.44 1.45 1.46 1.47 1.48 1.49 1.50 1.51 1.52 1.53 1.54 1.55 1.56 1.57 1.58 1.59 1.60 1.61 1.62 1.63 1.64 1.65 1.66 1.67 1.68 1.69 1.70 1.71 1.72 1.73 1.74 1.75 1.76 1.77 1.78 1.79 dcterms = http://dublincore.org/documents/dcmi-terms/
- ↑ 2.00 2.01 2.02 2.03 2.04 2.05 2.06 2.07 2.08 2.09 2.10 2.11 2.12 2.13 2.14 2.15 ncd = http://rs.tdwg.org/ontology/voc/Collection#
- ↑ 3.00 3.01 3.02 3.03 3.04 3.05 3.06 3.07 3.08 3.09 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 3.20 3.21 3.22 3.23 3.24 3.25 3.26 3.27 3.28 3.29 3.30 3.31 3.32 3.33 3.34 3.35 3.36 3.37 3.38 3.39 3.40 3.41 3.42 3.43 3.44 3.45 3.46 3.47 3.48 3.49 3.50 3.51 k2n = http://www.keytonature.eu/std/metadata/2009/xmlns/ - Note: The namespace is not resolvable, the specification can be found here
- ↑ 4.0 4.1 4.2 4.3 4.4 4.5 4.6 mix2 = http://www.loc.gov/standards/mix/mix20/mix20.xsd --note MIX 2.0 provides an XML Schema provided by the U.S. Library of Congress as a representation of the U.S. ANSI/NISO Z39.87 controlled vocabulary for still images.The text in the MIX 1.0 is designated as the schema corresponding to the Z39.87 PDF document remains a good source for details of the MIX 2.0 elements, which are not substantially different in detail from MIX 1.0
- ↑ 5.00 5.01 5.02 5.03 5.04 5.05 5.06 5.07 5.08 5.09 5.10 5.11 5.12 5.13 5.14 5.15 5.16 5.17 5.18 5.19 5.20 5.21 5.22 5.23 5.24 5.25 5.26 5.27 5.28 5.29 5.30 5.31 5.32 5.33 5.34 5.35 5.36 5.37 mrtg = http://xxx.org/XXX
- ↑ 6.0 6.1 6.2 6.3 6.4 6.5 xmp = http://ns.adobe.com/xap/1.0/, see XMP Specification Part 1, Sec 8.4 XMP does not have an explicit w3c XML-Schema. An "XMP Schema" is actually defined in RDF.
- ↑ 7.00 7.01 7.02 7.03 7.04 7.05 7.06 7.07 7.08 7.09 7.10 7.11 Iptc4xmpExt = http://iptc.org/std/Iptc4xmpExt/1.0/xmlns/ - Note: the namespace is not resolvable; as of 2011-06-25 the specification is available as PDF.
- ↑ 8.0 8.1 8.2 8.3 8.4 8.5 xmpRights = http://ns.adobe.com/xap/1.0/rights/, see XMP Specification Part 1, Sec 8.5
- ↑ plus = ? The correct resolution for the namespace mentioned in the Ipct PDF is not given there, and the namespace http://ns.useplus.org/ldf/vocab/ associated with the plus ns prefix does not have the term like CopyrightOwner in it. This may be a version issue and needs further research.
- ↑ 10.00 10.01 10.02 10.03 10.04 10.05 10.06 10.07 10.08 10.09 10.10 10.11 10.12 10.13 10.14 10.15 10.16 10.17 10.18 10.19 10.20 10.21 10.22 10.23 10.24 10.25 10.26 10.27 10.28 10.29 10.30 10.31 10.32 dwc = http://rs.tdwg.org/dwc/terms/index.htm
- ↑ 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
- ↑ GEMET http://www.eionet.europa.eu/gemet
- ↑ xmpMM = http://ns.adobe.com/xap/1.0/mm/, see PDF, p. 32ff
