This document is a cover page, an entry-level document to the Darwin Core standard. It describes the purpose of the
-standard and orients the reader to the documents that cover specific topics within the standard, such as the quick
-guide to the list of terms.
-
-
-
Contributors:
-
John Wieczorek (MVZ), Markus Döring (GBIF), Renato De Giovanni (CRIA), Tim Robertson (GBIF), Dave Vieglais (KUNHM)
-
-
-
Legal:
-
This document is governed by the standard legal, copyright, licensing provisions and disclaimers issued by the Taxonomic Databases Working Group.
-Audience: This document is an introduction to the Darwin Core standard and is meant to provide the background, reasons,
-and basic information about sharing (either as a publisher or user of) biodiversity information. Further details on specific
-aspects of the standard and its use can be found in the pages shown in the Table of Contents in the upper left of every page or in
-the References section of this page.
-
-What is the Darwin Core?
-
-The Darwin Core is body of standards. It includes
-a glossary of terms (in other contexts these might be called properties,
-elements, fields, columns, attributes, or concepts) intended to facilitate the sharing of information about
-biological diversity by providing reference definitions, examples, and commentaries. The Darwin Core is primarily
-based on taxa, their occurrence in nature as documented by observations, specimens, samples, and related information.
-Included are documents describing how these terms are managed, how the set of terms can be extended for new purposes,
-and how the terms can be used. The normative document for the terms [RDF-NORMATIVE]
-is written in the Resource Description Framework (RDF) and is the definitive resource to understand the term definitions and
-their relationships to each other. The Simple Darwin Core
-[SIMPLEDWC] is a specification for one particular way to use the terms - to
-share data about taxa and their occurrences in a simply structured way - and is probably what is meant if someone
-suggests to "format your data according to the Darwin Core".
-
-
-Motivation: The Darwin Core standard was originally conceived to facilitate the discovery, retrieval, and integration of
-information about modern biological specimens, their spatiotemporal occurrence, and their supporting evidence housed in collections
-(physical or digital). The Darwin Core today is broader in scope and more versatile. It is meant to provide a stable standard reference for
-sharing information on biological diversity. As a glossary of terms, the Darwin Core is meant to provide stable semantic
-definitions with the goal of being maximally reusable in a variety of contexts.
-
-
-Rationale:
-The Darwin Core is based on the standards developed by the Dublin Core Metadata
-Initiative [DCMI] and should be viewed as an extension of the Dublic Core for
-biodiversity information. The purpose of these terms is to facilitate data sharing by providing a well-defined
-standard core vocabulary in a flexible framework to minimize the barriers to adoption and to maximize reusability.
-The terms described in this standard are a part of a larger set of vocabularies
-and technical specifications under development [TDWG-DEV] and
-maintained by Biodiversity Information Standards (TDWG) [TDWG-STANDARDS].
-
-
-Guiding principles: Each term has a definition and commentaries that are meant to promote the consistent use
-of the terms across applications and disciplines. Evolving commentaries that discuss, refine, expand, or translate
-the definitions and examples are referred to through links in the Comments attribute of each term. This means of
-documentation allows the standard to adapt to new purposes without disrupting existing applications.
-There is meant to be a clear separation between the terms defined in this standard and the applications that make use
-of them. For example, though the data types and constraints are not provided in the term definitions, recommendations
-are made about how to restrict the values where appropriate.
-
-
-Content: The standard
-consists of a vocabulary of terms (properties, elements, fields, concepts) [TERMS],
-the policy governing the maintenance of these terms
-[NAMESPACEPOLICY], the decisions that resulted in changes to terms
-[DECISIONS], the complete history of terms including detailed
-attributes [HISTORY], a Generic Darwin Core XML schema
-[TERMSXMLSCHEMA] from which other schemas can be constructed, a Simple
-Darwin Core XML schema
-[SIMPLEXMLSCHEMA] as a complete schema ready for use, a schema to allow
-Darwin Core data transfer in text files [TEXTSCHEMA], and associated reference
-schemas for the construction of more structured content. These pages also describe
-mappings between the current standard and pre-standard historical versions [VERSIONS],
-including mappings [DWCTOABCD] to concepts in the Access to Biological
-Collections Data standard [ABCD].
+
+
Darwin Core
-
-Extension: Though the Darwin Core is insufficient for the needs of all biological
-disciplines, it can be adapted to serve new purposes. The
-Darwin Core can be extended by adding new terms to share additional information. To do so you should be familiar with
-the recommendations and procedures defined in the Darwin Core Namespace Policy
-[NAMESPACEPOLICY]. Basically, before proposing
-a new term, consider the existing terms in this and other compatible standards to determine if the new concept can be
-accommodated by a simple revision of the description and comments for an existing term, without losing the
-existing meaning of that term.
+
+
+
+
Title:
-
-Participation: To receive notification of activity or participate in discussions about Darwin Core,
-join the tdwg-content mailing
-list [TDWG-CONTENT] and set up specific
-feeds in the Darwin Core Project
-[DWC-PROJECT].
-For discussion or commentary on the definition of recommended terms, consult the link inside the Comment section in the
-listing for the term in the Quick Reference Guide [TERMS] or search for the page
-in the Darwin Core Project Wiki [DWC-WIKI].
-Commentary can be added to any term's wiki page. Similarly, the project site can be used for discussion and development
-of application schemas that make use of the Darwin Core.
-
-To make a formal request for a change to or addition of a term to the Darwin Core, read and follow the recommendations in the
-Darwin Core Namespace Policy [NAMESPACEPOLICY].
-For those who wish to construct and submit as a standard any application profile, such as an XML schema, that extends the
-capabilities of the Darwin Core, adding new terms to the Darwin Core vocabulary that don't already exist in a compatible
-vocabulary will be a prerequisite. Consult the
-appropriate guideline, such as the XML Guide [XMLSCHEMAGUIDE], for information about
-the construction of a new application profile. The rules of submission of proposed standards can be found in the
-Biodiversity Information Standards (TDWG) process document [PROCESS].
+
Audience: This document is an introduction to the Darwin Core
+ standard and is meant to provide the background, reasons, and basic
+ information about sharing (either as a publisher or user of) biodiversity
+ information. Further details on specific aspects of the standard and its use
+ can be found in the pages shown in the Table of Contents in the upper left of
+ every page or in the References section of this
+ page.
Darwin Core 1.21 (MaNIS/HerpNet/ORNIS/FishNet2) schema.
-
+
The Darwin Core is body of standards. It includes a glossary of terms (in
+ other contexts these might be called properties, elements, fields, columns,
+ attributes, or concepts) intended to facilitate the sharing of information
+ about biological diversity by providing reference definitions, examples, and
+ commentaries. The Darwin Core is primarily based on taxa, their occurrence in
+ nature as documented by observations, specimens, samples, and related
+ information. Included are documents describing how these terms are managed,
+ how the set of terms can be extended for new purposes, and how the terms can
+ be used. The normative document for the terms [RDF-NORMATIVE] is written in the Resource
+ Description Framework (RDF) and is the definitive resource to understand the
+ term definitions and their relationships to each other. The Simple Darwin
+ Core [SIMPLEDWC] is a
+ specification for one particular way to use the terms - to share data about
+ taxa and their occurrences in a simply structured way - and is probably what
+ is meant if someone suggests to "format your data according to the Darwin
+ Core".
Motivation: The Darwin Core standard was originally conceived to
+ facilitate the discovery, retrieval, and integration of information about
+ modern biological specimens, their spatiotemporal occurrence, and their
+ supporting evidence housed in collections (physical or digital). The Darwin
+ Core today is broader in scope and more versatile. It is meant to provide a
+ stable standard reference for sharing information on biological diversity. As
+ a glossary of terms, the Darwin Core is meant to provide stable semantic
+ definitions with the goal of being maximally reusable in a variety of
+ contexts.
Rationale: The Darwin Core is based on the standards developed by
+ the Dublin Core Metadata Initiative [DCMI] and can be viewed as an extension of the
+ Dublic Core for biodiversity information. The purpose of these terms is to
+ facilitate data sharing by providing a well-defined standard core vocabulary
+ in a flexible framework to minimize the barriers to adoption and to maximize
+ reusability. The terms described in this standard are a part of a larger set
+ of vocabularies and technical specifications under development [TDWG-DEV] and maintained by
+ Biodiversity Information Standards (TDWG) [TDWG-STANDARDS].
Guiding principles: Each term has a definition and commentaries
+ that are meant to promote the consistent use of the terms across applications
+ and disciplines. Evolving commentaries that discuss, refine, expand, or
+ translate the definitions and examples are referred to through links in the
+ Comments attribute of each term. This means of documentation allows
+ the standard to adapt to new purposes without disrupting existing
+ applications. There is meant to be a clear separation between the terms
+ defined in this standard and the applications that make use of them. For
+ example, though the data types and constraints are not provided in the term
+ definitions, recommendations are made about how to restrict the values where
+ appropriate.
Content: The standard consists of a vocabulary of terms
+ (properties, elements, fields, concepts) [TERMS], the policy governing the maintenance of these
+ terms [NAMESPACEPOLICY], the
+ decisions that resulted in changes to terms [DECISIONS], the complete history of
+ terms including detailed attributes [HISTORY], a Generic Darwin Core XML
+ schema [TERMSXMLSCHEMA] from which
+ other schemas can be constructed, a Simple Darwin Core XML schema
+ [SIMPLEXMLSCHEMA] as a complete
+ schema ready for use, a schema to allow Darwin Core data transfer in text
+ files [TEXTSCHEMA], and associated
+ reference schemas for the construction of more structured content. These
+ pages also describe mappings between the current standard and pre-standard
+ historical versions [VERSIONS], including mappings
+ [DWCTOABCD] to concepts in
+ the Access to Biological Collections Data standard [ABCD].
An rdf document for the complete current recommended set of Darwin Core terms. If this link shows a blank page in your browser, use the View Source option to see the RDF document.
-
+
Extension: Though the Darwin Core is insufficient for the needs of
+ all biological disciplines, it can be adapted to serve new purposes. Darwin
+ Core can be extended by adding new terms to share additional information. To
+ do so you should be familiar with the recommendations and procedures defined
+ in the Darwin Core Namespace Policy [NAMESPACEPOLICY]. Basically, before
+ proposing a new term, consider the existing terms in this and other
+ compatible standards to determine if the new concept can be accommodated by a
+ simple revision of the description and comments for an existing term, without
+ losing the existing meaning of that term.
The normative document for the complete history of Darwin Core terms, in RDF. If this link shows a blank page in your browser, use the View Source option to see the RDF document.
-
+
Participation: To receive notification of activity or participate
+ in discussions about Darwin Core, join the tdwg-content mailing list
+ [TDWG-CONTENT] and
+ watch the Darwin Core Project [DWC-PROJECT]. For discussion or commentary
+ on the definition of recommended terms, consult the link inside the
+ Comment section in the listing for the term in the Quick Reference
+ Guide [TERMS] or search for the relevant
+ content in the auxiliaryDarwin Core Documentation [DWC-WIKI].
Simple Darwin Core Text metafile. If this link shows a blank page in your browser, use the View Source option to see the XML document.
-
+
To make a formal request for a change to or addition of a term to the
+ Darwin Core, read and follow the recommendations in the Darwin Core
+ Namespace Policy [NAMESPACEPOLICY]. For those who wish to
+ construct and submit as a standard any application profile, such as an XML
+ schema, that extends the capabilities of the Darwin Core, adding new terms to
+ the Darwin Core vocabulary that don't already exist in a compatible
+ vocabulary will be a prerequisite. Consult the appropriate guideline, such as
+ the XML Guide [XMLGUIDE],
+ for information about the construction of a new application profile. The
+ rules of submission of proposed standards can be found in the Biodiversity
+ Information Standards (TDWG) process document [PROCESS].
An rdf document for the complete current recommended set
+ of Darwin Core terms. If this link shows a blank page in your browser,
+ use the View Source option to see the RDF document.
The normative document for the complete history of Darwin
+ Core terms, in RDF. If this link shows a blank page in your browser, use
+ the View Source option to see the RDF document.
Copyright 2011-2014 -
+ Biodiversity Information Standards - TDWG - Contact Us
+
+
+
+
+
\ No newline at end of file
diff --git a/rdf/dwcterms.rdf b/rdf/dwcterms.rdf
index 85a2d78..162537b 100644
--- a/rdf/dwcterms.rdf
+++ b/rdf/dwcterms.rdf
@@ -1,34 +1,35 @@
-
-
-
-
+
+
+
+
+
+
]>
-
-Darwin Core Recommended Terms
-This document contains a list of Darwin Core terms that have the dwcattributes:status equal to "recommended". For the full normative RDF document of all Darwin Core terms, see dwctermshistory.rdf. To comment on this schema, please create a new issue in http://code.google.com/p/darwincore/issues/
-Biodiversity Information Standards (TDWG)
-2013-10-22
-
-
-
-
-
-
-Accepted Name UsageThe full name, with authorship and date information if known, of the currently valid (zoological) or accepted (botanical) taxon.Example: "Tamias minimus" valid name for "Eutamias minimus"2008-11-192009-09-21recommendednot in ABCD
-Accepted Name Usage IDAn identifier for the name usage (documented meaning of the name according to a source) of the currently valid (zoological) or accepted (botanical) taxon.Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"2009-01-212009-09-21recommendednot in ABCD
-According ToAbstract term to attribute information to a source.2009-01-212009-01-21recommendednot in ABCD
-Associated MediaA list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of media associated with the Occurrence.Example: "http://arctos.database.museum/SpecimenImages/UAMObs/Mamm/2/P7291179.JPG"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/MultimediaObjects
-Associated OccurrencesA list (concatenated and separated) of identifiers of other Occurrence records and their associations to this Occurrence.Example: "sibling of FMNH:Mammal:1234; sibling of FMNH:Mammal:1235"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
-Associated ReferencesA list (concatenated and separated) of identifiers (publication, bibliographic reference, global unique identifier, URI) of literature associated with the Occurrence.Examples: "http://www.sciencemag.org/cgi/content/abstract/322/5899/261", "Christopher J. Conroy, Jennifer L. Neuwald. 2008. Phylogeographic study of the California vole, Microtus californicus Journal of Mammalogy, 89(3):755-767."2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/UnitReferences
-Associated SequencesA list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of genetic sequence information associated with the Occurrence.Example: "GenBank: U34853.1"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Sequences/Sequence/ID-in-Database + constant
-Associated TaxaA list (concatenated and separated) of identifiers or names of taxa and their associations with the Occurrence.Example: "host: Quercus alba"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Synecology/AssociatedTaxa
-Basis of RecordThe specific nature of the data record - a subtype of the dcterms:type. Recommended best practice is to use a controlled vocabulary such as the Darwin Core Type Vocabulary (http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm).Examples: "PreservedSpecimen", "FossilSpecimen", "LivingSpecimen", "HumanObservation", "MachineObservation"2008-11-192009-12-07recommendedDataSets/DataSet/Units/Unit/RecordBasis
-BedThe full name of the lithostratigraphic bed from which the cataloged item was collected.2009-04-242009-07-06recommendednot in ABCD
-BehaviorA description of the behavior shown by the subject at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.Examples: "roosting", "foraging", "running"2009-03-062009-04-24recommendednot in ABCD
-Catalog NumberAn identifier (preferably unique) for the record within the data set or collection.Examples: "2008.1334", "145732a", "145732"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/UnitID
-ClassThe full scientific name of the class in which the taxon is classified.Examples: "Mammalia", "Hepaticopsida"2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
-Collection CodeThe name, acronym, coden, or initialism identifying the collection or data set from which the record was derived.Examples: "Mammals", "Hildebrandt", "eBird"2008-11-192013-10-04recommendedDataSets/DataSet/Units/Unit/SourceID
-Collection IDAn identifier for the collection or dataset from which the record was derived. For physical specimens, the recommended best practice is to use the identifier in a collections registry such as the Biodiversity Collections Index (http://www.biodiversitycollectionsindex.org/).Example: "urn:lsid:biocol.org:col:34818"2008-11-192013-10-04recommendedDataSets/DataSet/Units/Unit/SourceID
-ContinentThe name of the continent in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.Examples: "Africa", "Antarctica", "Asia", "Europe", "North America", "Oceania", "South America"2008-11-192013-10-04recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Continent
-Coordinate PrecisionA decimal representation of the precision of the coordinates given in the decimalLatitude and decimalLongitude.Examples: "0.00001" (normal GPS limit for decimal degrees), "0.000278" (nearest second), "0.01667" (nearest minute), "1.0" (nearest degree)2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/ISOAccuracy or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/AccuracyStatement
-Coordinate Uncertainty In MetersThe horizontal distance (in meters) from the given decimalLatitude and decimalLongitude describing the smallest circle containing the whole of the Location. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Zero is not a valid value for this term.Examples: "30" (reasonable lower limit of a GPS reading under good conditions if the actual precision was not recorded at the time), "71" (uncertainty for a UTM coordinate having 100 meter precision and a known spatial reference system).2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinateErrorDistanceInMeters
-CountryThe name of the country or major administrative unit in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.Examples: "Denmark", "Colombia", "España"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Country/Name
-Country CodeThe standard code for the country in which the Location occurs. Recommended best practice is to use ISO 3166-1-alpha-2 country codes.Examples: "AR" for Argentina, "SV" for El Salvador2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Country/ISO3166Code
-CountyThe full, unabbreviated name of the next smaller administrative region than stateProvince (county, shire, department, etc.) in which the Location occurs.Examples: "Missoula", "Los Lagos", "Mataró"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= County
-Data GeneralizationsActions taken to make the shared data less specific or complete than in its original form. Suggests that alternative data of higher quality may be available on request.Example: "Coordinates generalized from original GPS coordinates to the nearest half degree grid cell"2008-11-192009-04-24recommendednot in ABCD
-Dataset IDAn identifier for the set of data. May be a global unique identifier or an identifier specific to a collection or institution.2008-11-192009-09-11recommendedDataSets/DataSet/DataSetGUID
-Dataset NameThe name identifying the data set from which the record was derived.Examples: "Grinnell Resurvey Mammals", "Lacey Ctenomys Recaptures"2009-09-112009-09-11recommendedDataSets/DataSet/Units/Unit/SourceID
-Date IdentifiedThe date on which the subject was identified as representing the Taxon. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "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.2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
-DayThe integer day of the month on which the Event occurred.Examples: "9", "28"2008-11-192009-04-24recommendedaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Decimal LatitudeThe geographic latitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are north of the Equator, negative values are south of it. Legal values lie between -90 and 90, inclusive.Example: "-41.0983423"2008-11-192009-07-06recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal
-Decimal LongitudeThe geographic longitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are east of the Greenwich Meridian, negative values are west of it. Legal values lie between -180 and 180, inclusive.Example: "-121.1761111"2008-11-192009-07-06recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal
-DispositionThe current state of a specimen with respect to the collection identified in collectionCode or collectionID. Recommended best practice is to use a controlled vocabulary.Examples: "in collection", "missing", "voucher elsewhere", "duplicates elsewhere"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/SpecimenUnit/Disposition
-Darwin Core TypeThe set of classes specified by the Darwin Core Type Vocabulary, used to categorize the nature or genre of the resource.2008-11-192008-11-19recommendednot in ABCD
-Dynamic PropertiesA list (concatenated and separated) of additional measurements, facts, characteristics, or assertions about the record. Meant to provide a mechanism for structured content such as key-value pairs.Examples: "tragusLengthInMeters=0.014; weightInGrams=120", "heightInMeters=1.5", "natureOfID=expert identification; identificationEvidence=cytochrome B sequence", "relativeHumidity=28; airTemperatureInC=22; sampleSizeInKilograms=10", "aspectHeading=277; slopeInDegrees=6", "iucnStatus=vulnerable; taxonDistribution=Neuquen, Argentina"2008-11-192009-04-24recommendednot in ABCD
-Earliest Age Or Lowest StageThe full name of the earliest possible geochronologic age or lowest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Atlantic", "Boreal", "Skullrockian"2009-04-242009-07-06recommendednot in ABCD
-Earliest Eon Or Lowest EonothemThe full name of the earliest possible geochronologic eon or lowest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Phanerozoic", "Proterozoic"2009-04-242009-07-06recommendednot in ABCD
-Earliest Epoch Or Lowest SeriesThe full name of the earliest possible geochronologic epoch or lowest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Holocene", "Pleistocene", "Ibexian Series"2009-04-242009-07-06recommendednot in ABCD
-Earliest Era Or Lowest ErathemThe full name of the earliest possible geochronologic era or lowest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Cenozoic", "Mesozoic"2009-04-242009-07-06recommendednot in ABCD
-Earliest Period Or Lowest SystemThe full name of the earliest possible geochronologic period or lowest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Neogene", "Tertiary", "Quaternary"2009-04-242009-07-06recommendednot in ABCD
-End Day Of YearThe latest ordinal day of the year on which the Event occurred (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366).Examples: "1" (=1 Jan), "366" (=31 Dec), "365" (=30 Dec in a leap year, 31 Dec in a non-leap year)2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberEnd
-Establishment MeansThe process by which the biological individual(s) represented in the Occurrence became established at the location. Recommended best practice is to use a controlled vocabulary.Examples: "native", "introduced", "naturalised", "invasive", "managed"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/EstablishmentMeans
-EventThe category of information pertaining to an event (an action that occurs at a place and during a period of time).2008-11-192009-04-29recommendedDataSets/DataSet/Units/Unit/Gathering
-Event DateThe date-time or interval during which an Event occurred. For occurrences, this is the date-time when the event was recorded. Not suitable for a time in a geological context. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "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.2009-04-242009-07-01recommendedDataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Event IDAn identifier for the set of information associated with an Event (something that occurs at a place and time). May be a global unique identifier or an identifier specific to the data set.2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Code
-Event RemarksComments or notes about the Event.Example: "after the recent rains the river is nearly at flood stage"2009-01-182009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Notes
-Event TimeThe time or interval during which an Event occurred. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "14:07-0600" is 2:07pm in the time zone six hours earlier than UTC, "08:40:21Z" is 8:40:21am UTC, "13:00:00Z/15:30:00Z" is the interval between 1pm UTC and 3:30pm UTC.2009-04-242009-04-24recommendedaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin and DataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
-FamilyThe full scientific name of the family in which the taxon is classified.Examples: "Felidae", "Monocleaceae"2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
-Field NotesOne of a) an indicator of the existence of, b) a reference to (publication, URI), or c) the text of notes taken in the field about the Event.Example: "notes available in Grinnell-Miller Library"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/FieldNotes
-Field NumberAn identifier given to the event in the field. Often serves as a link between field notes and the Event.Example: "RV Sol 87-03-08"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Code
-Footprint Spatial FitThe ratio of the area of the footprint (footprintWKT) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given footprint does not completely contain the original representation. The footprintSpatialFit is undefined (and should be left blank) if the original representation is a point and the given georeference is not that same point. If both the original and the given georeference are the same point, the footprintSpatialFit is 1.Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006 (http://www.gbif.org/prog/digit/Georeferencing).2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/FootprintSpatialFit (ABCD v2.06b)
-Footprint SRSA Well-Known Text (WKT) representation of the Spatial Reference System (SRS) for the footprintWKT of the Location. Do not use this term to describe the SRS of the decimalLatitude and decimalLongitude, even if it is the same as for the footprintWKT - use the geodeticDatum instead.Example: The WKT for the standard WGS84 SRS (EPSG:4326) is "GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137,298.257223563]],PRIMEM["Greenwich",0],UNIT["Degree",0.0174532925199433]]" without the enclosing quotes.2009-07-062009-07-06recommendednot in ABCD
-Footprint WKTA Well-Known Text (WKT) representation of the shape (footprint, geometry) that defines the Location. A Location may have both a point-radius representation (see decimalLatitude) and a footprint representation, and they may differ from each other.Example: the one-degree bounding box with opposite corners at (longitude=10, latitude=20) and (longitude=11, latitude=21) would be expressed in well-known text as POLYGON ((10 20, 11 20, 11 21, 10 21, 10 20))2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/FootprintWKT (ABCD v2.06b)
-FormationThe full name of the lithostratigraphic formation from which the cataloged item was collected.Examples: "Notch Peak Fromation", "House Limestone", "Fillmore Formation"2009-04-242009-07-06recommendednot in ABCD
-GenusThe full scientific name of the genus in which the taxon is classified.Examples: "Puma", "Monoclea"2008-11-192009-08-24recommended{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
-Geodetic DatumThe ellipsoid, geodetic datum, or spatial reference system (SRS) upon which the geographic coordinates given in decimalLatitude and decimalLongitude as based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".Examples: "EPSG:4326", "WGS84", "NAD27", "Campo Inchauspe", "European 1950", "Clarke 1866"2008-11-192009-07-06recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/SpatialDatum
-Geological ContextThe category of information pertaining to a location within a geological context, such as stratigraphy.2009-07-062009-07-06recommendedDataSets/DataSet/Units/Unit/Gathering/Stratigraphy
-Geological Context IDAn identifier for the set of information associated with a GeologicalContext (the location within a geological context, such as stratigraphy). May be a global unique identifier or an identifier specific to the data set.2009-07-062009-07-06recommendednot in ABCD
-Georeferenced ByA list (concatenated and separated) of names of people, groups, or organizations who determined the georeference (spatial representation) for the Location.Examples: "Kristina Yamamoto (MVZ); Janet Fang (MVZ)", "Brad Millen (ROM)"2009-01-212009-04-24recommendednot in ABCD
-Georeferenced DateThe date on which the Location was georeferenced. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "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.2011-10-162011-10-16recommendednot in ABCD
-Georeference ProtocolA description or reference to the methods used to determine the spatial footprint, coordinates, and uncertainties.Examples: "Guide to Best Practices for Georeferencing" (Chapman and Wieczorek, eds. 2006), Global Biodiversity Information Facility.", "MaNIS/HerpNet/ORNIS Georeferencing Guidelines", "Georeferencing Quick Reference Guide"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinateMethod
-Georeference RemarksNotes or comments about the spatial description determination, explaining assumptions made in addition or opposition to the those formalized in the method referred to in georeferenceProtocol.Example: "assumed distance by road (Hwy. 101)"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceRemarks
-Georeference SourcesA list (concatenated and separated) of maps, gazetteers, or other resources used to georeference the Location, described specifically enough to allow anyone in the future to use the same resources.Examples: "USGS 1:24000 Florence Montana Quad; Terrametrics 2008 on Google Earth"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceSources
-Georeference Verification StatusA categorical description of the extent to which the georeference has been verified to represent the best possible spatial description. Recommended best practice is to use a controlled vocabulary.Examples: "requires verification", "verified by collector", "verified by curator".2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceVerificationStatus
-GroupThe full name of the lithostratigraphic group from which the cataloged item was collected.2009-04-242009-07-06recommendednot in ABCD
-HabitatA category or description of the habitat in which the Event occurred.Examples: "oak savanna", "pre-cordilleran steppe"2008-11-192009-05-17recommendedDataSets/DataSet/Units/Unit/Gathering/Biotope/Text
-Higher ClassificationA list (concatenated and separated) of taxa names terminating at the rank immediately superior to the taxon referenced in the taxon record. Recommended best practice is to order the list starting with the highest rank and separating the names for each rank with a semi-colon (";").Example: "Animalia;Chordata;Vertebrata;Mammalia;Theria;Eutheria;Rodentia;Hystricognatha;Hystricognathi;Ctenomyidae;Ctenomyini;Ctenomys"2008-11-192009-08-24recommendednot in ABCD
-Higher GeographyA list (concatenated and separated) of geographic names less specific than the information captured in the locality term.Example: "South America; Argentina; Patagonia; Parque Nacional Nahuel Huapi; Neuquén; Los Lagos" with accompanying values "South America" in Continent, "Argentina" in Country, "Neuquén" in StateProvince, and Los Lagos in County.2008-11-192009-04-24recommended{DataSets/DataSet/Units/Unit/Gathering/LocalityText or DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName}
-Higher Geography IDAn identifier for the geographic region within which the Location occurred. Recommended best practice is to use an persistent identifier from a controlled vocabulary such as the Getty Thesaurus of Geographic Names.Example: "TGN: 1002002" for Prov. Tierra del Fuego, Argentina2009-01-212009-04-24recommendednot in ABCD
-Highest Biostratigraphic ZoneThe full name of the highest possible geological biostratigraphic zone of the stratigraphic horizon from which the cataloged item was collected.2009-04-242009-07-06recommendednot in ABCD
-IdentificationThe category of information pertaining to taxonomic determinations (the assignment of a scientific name).2008-11-192008-11-19recommendedDataSets/DataSet/Units/Unit/Identifications/Identification
-Identification IDAn identifier for the Identification (the body of information associated with the assignment of a scientific name). May be a global unique identifier or an identifier specific to the data set.2008-11-192009-04-24recommendednot in ABCD
-Identification QualifierA brief phrase or a standard term ("cf.", "aff.") to express the determiner's doubts about the Identification.Examples: 1) For the determination "Quercus aff. agrifolia var. oxyadenia", identificationQualifier would be "aff. agrifolia var. oxyadenia" with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank. 2) For the determination "Quercus agrifolia cf. var. oxyadenia", identificationQualifier would be "cf. var. oxyadenia " with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank.2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/IdentificationQualifier
-Identification ReferencesA list (concatenated and separated) of references (publication, global unique identifier, URI) used in the Identification.Example: "Aves del Noroeste Patagonico. Christie et al. 2004."2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/References
-Identification RemarksComments or notes about the Identification.Example: "Distinguished between Anthus correndera and Anthus hellmayri based on the comparative lengths of the uñas."2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/Notes
-Identification Verification StatusA categorical indicator of the extent to which the taxonomic identification has been verified to be correct. Recommended best practice is to use a controlled vocabulary such as that used in HISPID/ABCD.Examples: "0", "4"2011-10-162011-10-16recommendednot in ABCD
-Identified ByA list (concatenated and separated) of names of people, groups, or organizations who assigned the Taxon to the subject.Examples: "James L. Patton", "Theodore Pappenfuss; Robert Macey"2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/Identifiers/IdentifiersText
-Individual CountThe number of individuals represented present at the time of the Occurrence.Examples: "1", "25"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue
-Individual IDAn identifier for an individual or named group of individual organisms represented in the Occurrence. Meant to accommodate resampling of the same individual or group for monitoring purposes. May be a global unique identifier or an identifier specific to a data set.Examples: "U.amer. 44", "Smedley", "Orca J 23"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/NameAtomised/Zoological/NamedIndividual or DataSets/DataSet/Units/Unit/ObservationUnit/ObservationUnitIdentifiers/ObservationUnitIdentifier or DataSets/DataSet/Units/Unit/SpecimenUnit/Accessions/AccessionNumber
-Information WithheldAdditional information that exists, but that has not been shared in the given record.Examples: "location information not given for endangered species", "collector identities withheld", "ask about tissue samples"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/InformationWithheld
-Infraspecific EpithetThe name of the lowest or terminal infraspecific epithet of the scientificName, excluding any rank designation.Examples: "concolor", "oxyadenia", "sayi"2008-11-192009-08-24recommended{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
-Institution CodeThe name (or acronym) in use by the institution having custody of the object(s) or information referred to in the record.Examples: "MVZ", "FMNH", "AKN-CLO", "University of California Museum of Paleontology (UCMP)"2008-11-192013-10-04recommendedDataSets/DataSet/Units/Unit/SourceInstitutionID
-Institution IDAn identifier for the institution having custody of the object(s) or information referred to in the record.2009-09-112013-10-04recommendedDataSets/DataSet/Units/Unit/SourceInstitutionID
-IslandThe name of the island on or near which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.Examples: "Isla Victoria", "Vancouver", "Viti Levu", "Zanzibar"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island
-Island GroupThe name of the island group in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.Examples: "Alexander Archipelago", "Seychelles"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island group
-KingdomThe full scientific name of the kingdom in which the taxon is classified.Examples: "Animalia", "Plantae"2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
-Latest AgeOr Highest StageThe full name of the latest possible geochronologic age or highest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Atlantic", "Boreal", "Skullrockian"2009-04-242009-07-06recommendednot in ABCD
-Latest Eon Or Highest EonothemThe full name of the latest possible geochronologic eon or highest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Phanerozoic", "Proterozoic"2009-04-242009-07-06recommendednot in ABCD
-Latest Epoch Or Highest SeriesThe full name of the latest possible geochronologic epoch or highest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Holocene", "Pleistocene", "Ibexian Series"2009-04-242009-07-06recommendednot in ABCD
-Latest Era Or Highest ErathemThe full name of the latest possible geochronologic era or highest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Cenozoic", "Mesozoic"2009-04-242009-07-06recommendednot in ABCD
-Latest Period Or Highest SystemThe full name of the latest possible geochronologic period or highest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Neogene", "Tertiary", "Quaternary"2009-04-242009-07-06recommendednot in ABCD
-Life StageThe age class or life stage of the biological individual(s) at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.Examples: "egg", "eft", "juvenile", "adult", "2 adults 4 juveniles"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLiveStages/MycologicalLiveStage (Note DwC spec uses ”MycologicalLifeStage” or DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage
-Lithostratigraphic TermsThe combination of all litho-stratigraphic names for the rock from which the cataloged item was collected.2009-04-242009-07-06recommendedDataSets/DataSet/Units/Unit/Gathering/Stratigraphy/LithostratigraphicTerms
-LocalityThe specific description of the place. Less specific geographic information can be provided in other geographic terms (higherGeography, continent, country, stateProvince, county, municipality, waterBody, island, islandGroup). This term may contain information modified from the original to correct perceived errors or standardize the description.Example: "Bariloche, 25 km NNE via Ruta Nacional 40 (=Ruta 237)"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
-Location According ToInformation about the source of this Location information. Could be a publication (gazetteer), institution, or team of individuals.Examples: "Getty Thesaurus of Geographic Names", "GADM"2009-08-242009-08-24recommendednot in ABCD
-Location IDAn identifier for the set of location information (data associated with dcterms:Location). May be a global unique identifier or an identifier specific to the data set.2008-11-192009-04-24recommendednot in ABCD
-Location RemarksComments or notes about the Location.Example: "under water since 2005"2009-01-182009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/AreaDetail
-Lowest Biostratigraphic ZoneThe full name of the lowest possible geological biostratigraphic zone of the stratigraphic horizon from which the cataloged item was collected.2009-04-242009-07-06recommendednot in ABCD
-Material SampleThe category of information pertaining to the physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.2013-03-282013-09-26recommendedDataSets/DataSet/Units/Unit
-Material Sample IDAn identifier for the MaterialSample (as opposed to a particular digital record of the material sample). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the materialSampleID globally unique.2013-03-282013-09-26recommendednot in ABCD
-Maximum Depth In MetersThe greater depth of a range of depth below the local surface, in meters.Example: "200"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue
-Maximum Distance Above Surface In MetersThe greater distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
-Maximum Elevation In MetersThe upper limit of the range of elevation (altitude, usually above sea level), in meters.Example: "200"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue
-Measurement AccuracyThe description of the potential error associated with the measurementValue.Examples: "0.01", "normal distribution with variation of 2 m"2009-01-182009-04-24recommendedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
-Measurement Determined ByA list (concatenated and separated) of names of people, groups, or organizations who determined the value of the MeasurementOrFact.Examples: "Javier de la Torre", "Julie Woodruff; Eileen Lacey"2009-01-232009-04-24recommendedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
-Measurement Determined DateThe date on which the MeasurementOrFact was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "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.2009-01-232009-04-24recommendedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
-Measurement IDAn identifier for the MeasurementOrFact (information pertaining to measurements, facts, characteristics, or assertions). May be a global unique identifier or an identifier specific to the data set.2009-03-062009-04-24recommendednot in ABCD
-Measurement MethodA description of or reference to (publication, URI) the method or protocol used to determine the measurement, fact, characteristic, or assertion.Examples: "minimum convex polygon around burrow entrances" for a home range area, "barometric altimeter" for an elevation2008-11-192009-04-24recommended/DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Method or /DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Method or /DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Method
-Measurement Or FactThe category of information pertaining to measurements, facts, characteristics, or assertions about a resource (instance of data record, such as Occurrence, Taxon, Location, Event).2009-04-242009-04-24recommendedDatasets/Dataset/Units/Unit/MeasurementsOrFacts or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts
-Measurement RemarksComments or notes accompanying the MeasurementOrFact.Example: "tip of tail missing"2008-11-192009-04-24recommendednot in ABCD
-Measurement TypeThe nature of the measurement, fact, characteristic, or assertion. Recommended best practice is to use a controlled vocabulary.Examples: "tail length", "temperature", "trap line length", "survey area", "trap type"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
-Measurement UnitThe units associated with the measurementValue. Recommended best practice is to use the International System of Units (SI).Examples: "mm", "C", "km", "ha"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
-Measurement ValueThe value of the measurement, fact, characteristic, or assertion.Examples: "45", "20", "1", "14.5", "UV-light"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
-MemberThe full name of the lithostratigraphic member from which the cataloged item was collected.Examples: "Lava Dam Member", "Hellnmaria Member"2009-04-242009-07-06recommendednot in ABCD
-Minimum Depth In MetersThe lesser depth of a range of depth below the local surface, in meters.Example: "100"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue
-Minimum Distance Above Surface In MetersThe lesser distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue
-Minimum Elevation In MetersThe lower limit of the range of elevation (altitude, usually above sea level), in meters.Example: "100"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue
-MonthThe ordinal month in which the Event occurred.Examples: "1" (=January), "10" (=October)2008-11-192009-04-24recommendedaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-MunicipalityThe full, unabbreviated name of the next smaller administrative region than county (city, municipality, etc.) in which the Location occurs. Do not use this term for a nearby named place that does not contain the actual location.Examples: "Holzminden"2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
-Name According ToThe reference to the source in which the specific taxon concept circumscription is defined or implied - traditionally signified by the Latin "sensu" or "sec." (from secundum, meaning "according to"). For taxa that result from identifications, a reference to the keys, monographs, experts and other sources should be given.Example: "McCranie, J. R., D. B. Wake, and L. D. Wilson. 1996. The taxonomic status of Bolitoglossa schmidti, with comments on the biology of the Mesoamerican salamander Bolitoglossa dofleini (Caudata: Plethodontidae). Carib. J. Sci. 32:395-398.", "Werner Greuter 2008", "Lilljeborg 1861, Upsala Univ. Arsskrift, Math. Naturvet., pp. 4, 5"2008-11-192009-09-21recommendednot in ABCD
-Name According To IDAn identifier for the source in which the specific taxon concept circumscription is defined or implied. See nameAccordingTo.Example: "doi:10.1016/S0269-915X(97)80026-2"2009-08-242009-09-21recommendednot in ABCD
-Name Published InA reference for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.Examples: "Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "Forel, Auguste, Diagnosies provisoires de quelques espèces nouvelles de fourmis de Madagascar, récoltées par M. Grandidier., Annales de la Societe Entomologique de Belgique, Comptes-rendus des Seances 30, 1886"2008-11-192009-09-21recommendedDataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference/TitleCitation
-Name Published In IDAn identifier for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.Example: "http://hdl.handle.net/10199/7"2009-05-182009-09-21recommendednot in ABCD
-Name Published In YearThe four-digit year in which the scientificName was published.Examples: "1915", "2008"2011-10-162011-10-16recommendednot in ABCD
-Nomenclatural CodeThe nomenclatural code (or codes in the case of an ambiregnal name) under which the scientificName is constructed. Recommended best practice is to use a controlled vocabulary.Examples: "ICBN", "ICZN", "BC", "ICNCP", "BioCode", "ICZN; ICBN"2008-11-192009-09-21recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/Code
-Nomenclatural StatusThe status related to the original publication of the name and its conformance to the relevant rules of nomenclature. It is based essentially on an algorithm according to the business rules of the code. It requires no taxonomic opinion.Examples: "nom. ambig.", "nom. illeg.", "nom. subnud."2009-01-182009-04-24recommended(DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference/TitleCitation)
-pro parte
-OccurrenceThe category of information pertaining to evidence of an occurrence in nature, in a collection, or in a dataset (specimen, observation, etc.).2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit
-Occurrence IDAn identifier for the Occurrence (as opposed to a particular digital record of the occurrence). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the occurrenceID globally unique.For a specimen in the absence of a bona fide global unique identifier, for example, use the form: "urn:catalog:[institutionCode]:[collectionCode]:[catalogNumber]. Examples: "urn:lsid:nhm.ku.edu:Herps:32", "urn:catalog:FMNH:Mammal:145732"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/UnitGUID
-Occurrence RemarksComments or notes about the Occurrence.Example: "found dead on road"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Notes
-Occurrence StatusA statement about the presence or absence of a Taxon at a Location. Recommended best practice is to use a controlled vocabulary.Examples: "present", "absent"2009-09-172009-09-17recommendednot in ABCD
-OrderThe full scientific name of the order in which the taxon is classified.Examples: "Carnivora", "Monocleales"2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
-Original Name UsageThe taxon name, with authorship and date information if known, as it originally appeared when first established under the rules of the associated nomenclaturalCode. The basionym (botany) or basonym (bacteriology) of the scientificName or the senior/earlier homonym for replaced names.Examples: "Pinus abies", "Gasterosteus saltatrix Linnaeus 1768"2008-11-192009-09-21recommendednot in ABCD
-Original Name Usage IDAn identifier for the name usage (documented meaning of the name according to a source) in which the terminal element of the scientificName was originally established under the rules of the associated nomenclaturalCode.Example: "http://species.gbif.org/abies_alba_1753"2009-01-212009-09-21recommendednot in ABCD
-Other Catalog NumbersA list (concatenated and separated) of previous or alternate fully qualified catalog numbers or other human-used identifiers for the same Occurrence, whether in the current or any other data set or collection.Examples: "FMNH:Mammal:1234", "NPS YELLO6778; MBG 33424"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/SpecimenUnit/History/PreviousUnitsText
-Owner Institution CodeThe name (or acronym) in use by the institution having ownership of the object(s) or information referred to in the record.Examples: "NPS", "APN", "InBio"2009-08-242013-10-04recommendednot in ABCD
-Parent Name UsageThe full name, with authorship and date information if known, of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.Examples: "Rubiaceae", "Gruiformes", "Testudinae"2009-08-242009-09-21recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
-Parent Name Usage IDAn identifier for the name usage (documented meaning of the name according to a source) of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"2009-01-212009-09-21recommendednot in ABCD
-PhylumThe full scientific name of the phylum or division in which the taxon is classified.Examples: "Chordata" (phylum), "Bryophyta" (division)2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
-Point Radius Spatial FitThe ratio of the area of the point-radius (decimalLatitude, decimalLongitude, coordinateUncertaintyInMeters) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given point-radius does not completely contain the original representation. The pointRadiusSpatialFit is undefined (and should be left blank) if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the pointRadiusSpatialFit is 1.Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006 (http://www.gbif.org/prog/digit/Georeferencing).2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/PointRadiusSpatialFit
-PreparationsA list (concatenated and separated) of preparations and preservation methods for a specimen.Examples: "skin; skull; skeleton", "whole animal (ETOH); tissue (EDTA)", "fossil", "cast", "photograph", "DNA extract"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/PreparationsText
-Previous IdentificationsA list (concatenated and separated) of previous assignments of names to the Occurrence.Example: "Anthus sp., field ID by G. Iglesias; Anthus correndera, expert ID by C. Cicero 2009-02-12 based on morphology"2008-11-192009-05-18recommendedDataSets/DataSet/Units/Unit/Identifications/Identification with PreferredFlag = false
-Recorded ByA list (concatenated and separated) of names of people, groups, or organizations responsible for recording the original Occurrence. The primary collector or observer, especially one who applies a personal identifier (recordNumber), should be listed first.Example: "Oliver P. Pearson; Anita K. Pearson" where the value in recordNumber "OPP 7101" corresponds to the number for the specimen in the field catalog (collector number) of Oliver P. Pearson.2008-11-192009-05-18recommendedDataSets/DataSet/Units/Unit/Gathering/GatheringAgents/GatheringAgentsText
-Record NumberAn identifier given to the Occurrence at the time it was recorded. Often serves as a link between field notes and an Occurrence record, such as a specimen collector's number.Example: "OPP 7101"2008-11-192009-05-18recommendedDataSets/DataSet/Units/Unit/CollectorsFieldNumber
-Related Resource IDAn identifier for a related resource (the object, rather than the subject of the relationship).2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
-Relationship According ToThe source (person, organization, publication, reference) establishing the relationship between the two resources.Example: "Julie Woodruff"2009-04-242009-04-24recommendednot in ABCD
-Relationship Established DateThe date-time on which the relationship between the two resources was established. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "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.2009-04-242009-04-24recommendednot in ABCD
-Relationship Of ResourceThe relationship of the resource identified by relatedResourceID to the subject (optionally identified by the resourceID). Recommended best practice is to use a controlled vocabulary.Examples: "duplicate of", "mother of", "endoparasite of", "host to", "sibling of", "valid synonym of", "located within"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociationType
-Relationship RemarksComments or notes about the relationship between the two resources.Examples: "mother and offspring collected from the same nest", "pollinator captured in the act"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Associations/UnitAssociation/Comments
-Reproductive ConditionThe reproductive condition of the biological individual(s) represented in the Occurrence. Recommended best practice is to use a controlled vocabulary.Examples" "non-reproductive", "pregnant", "in bloom", "fruit-bearing"2008-11-192009-04-24recommendednot in ABCD
-Resource IDAn identifier for the resource that is the subject of the relationship.2009-04-242009-04-24recommendednot in ABCD
-Resource RelationshipThe category of information pertaining to relationships between resources (instances of data records, such as Occurrences, Taxa, Locations, Events).Resources can be thought of as identifiable records and may include, but need not be limited to Occurrences, Locations, Events, Identifications, or Taxon records.2008-11-192013-09-30recommendedDataSets/DataSet/Units/Unit/Associations
-Resource Relationship IDAn identifier for an instance of relationship between one resource (the subject) and another (relatedResource, the object).2009-01-262009-04-24recommendednot in ABCD
-Sampling EffortThe amount of effort expended during an Event.Examples: "40 trap-nights", "10 observer-hours; 10 km by foot; 30 km by car"2009-08-242009-08-24recommendednot in ABCD
-Sampling ProtocolThe name of, reference to, or description of the method or protocol used during an Event.Examples: "UV light trap", "mist net", "bottom trawl", "ad hoc observation", "point count", "Penguins from space: faecal stains reveal the location of emperor penguin colonies, http://dx.doi.org/10.1111/j.1466-8238.2009.00467.x", "Takats et al. 2001. Guidelines for Nocturnal Owl Monitoring in North America. Beaverhill Bird Observatory and Bird Studies Canada, Edmonton, Alberta. 32 pp.", "http://www.bsc-eoc.org/download/Owl.pdf"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Method
-Scientific NameThe full scientific name, with authorship and date information if known. When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the IdentificationQualifier term.Examples: "Coleoptera" (order), "Vespertilionidae" (family), "Manis" (genus), "Ctenomys sociabilis" (genus + specificEpithet), "Ambystoma tigrinum diaboli" (genus + specificEpithet + infraspecificEpithet), "Roptrocerus typographi (Györfi, 1952)" (genus + specificEpithet + scientificNameAuthorship), "Quercus agrifolia var. oxyadenia (Torr.) J.T. Howell" (genus + specificEpithet + taxonRank + infraspecificEpithet + scientificNameAuthorship)2008-11-192009-09-21recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/FullScientificNameString
-Scientific Name AuthorshipThe authorship information for the scientificName formatted according to the conventions of the applicable nomenclaturalCode.Example: "(Torr.) J.T. Howell", "(Martinovský) Tzvelev", "(Györfi, 1952)"2008-11-192009-04-24recommended{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/ParentheticalAuthorTeamAndYear + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/AuthorTeamAndYear} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeamParenthesis + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeam} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamOriginalAndYear + [= or] DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamParenthesisAndYear}
-Scientific Name IDAn identifier for the nomenclatural (not taxonomic) details of a scientific name.Example: "urn:lsid:ipni.org:names:37829-1:1.3"2008-11-192009-08-24recommendednot in ABCD
-SexThe sex of the biological individual(s) represented in the Occurrence. Recommended best practice is to use a controlled vocabulary.Examples: "female", "hermaphrodite", "8 males, 4 females"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Sex
-Specific EpithetThe name of the first or species epithet of the scientificName.Examples: "concolor", "gottschei"2008-11-192009-04-24recommended{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
-Start Day Of YearThe earliest ordinal day of the year on which the Event occurred (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366).Examples: "1" (=1 Jan), "366" (=31 Dec), "365" (=30 Dec in a leap year, 31 Dec in a non-leap year)2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberBegin
-State ProvinceThe name of the next smaller administrative region than country (state, province, canton, department, region, etc.) in which the Location occurs.Examples: "Montana", "Minas Gerais", "Córdoba"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= State or = Province (etc.)
-SubgenusThe full scientific name of the subgenus in which the taxon is classified. Values should include the genus to avoid homonym confusion.Examples: "Strobus (Pinus)", "Puma (Puma)" "Loligo (Amerigo)", "Hieracium subgen. Pilosella"2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/Subgenus
-TaxonThe category of information pertaining to taxonomic names, taxon name usages, or taxon concepts.2008-11-192009-09-21recommendedno simple equivalent in ABCD
-Taxon Concept IDAn identifier for the taxonomic concept to which the record refers - not for the nomenclatural details of a taxon.Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"2009-04-242009-09-21recommendednot in ABCD
-Taxon IDAn identifier for the set of taxon information (data associated with the Taxon class). May be a global unique identifier or an identifier specific to the data set.Examples: "8fa58e08-08de-4ac1-b69c-1235340b7001", "32567", "http://species.gbif.org/abies_alba_1753", "urn:lsid:gbif.org:usages:32567"2008-11-192009-08-24recommendednot in ABCD
-Taxonomic StatusThe status of the use of the scientificName as a label for a taxon. Requires taxonomic opinion to define the scope of a taxon. Rules of priority then are used to define the taxonomic status of the nomenclature contained in that scope, combined with the experts opinion. It must be linked to a specific taxonomic reference that defines the concept. Recommended best practice is to use a controlled vocabulary.Examples: "invalid", "misapplied", "homotypic synonym", "accepted"2008-11-192009-04-24recommendednot in ABCD
-Taxon RankThe taxonomic rank of the most specific name in the scientificName. Recommended best practice is to use a controlled vocabulary.Examples: "subspecies", "varietas", "forma", "species", "genus"2008-11-192009-09-21recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Rank
-Taxon RemarksComments or notes about the taxon or name.Example: "this name is a misspelling in common use"2008-11-192009-08-24recommendednot in ABCD
-Type StatusA list (concatenated and separated) of nomenclatural types (type status, typified scientific name, publication) applied to the subject.Example: "holotype of Ctenomys sociabilis. Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeText
-Verbatim CoordinatesThe verbatim original spatial coordinates of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.Examples: "41 05 54S 121 05 34W", "17T 630000 4833400"2008-11-192009-07-06recommended{DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinatesText or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesUTM/UTMText}
-Verbatim Coordinate SystemThe spatial coordinate system for the verbatimLatitude and verbatimLongitude or the verbatimCoordinates of the Location. Recommended best practice is to use a controlled vocabulary.Examples: "decimal degrees", "degrees decimal minutes", "degrees minutes seconds", "UTM"2008-11-192009-07-06recommended(partly) DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesGrid/GridCellSystem
-Verbatim DepthThe original description of the depth below the local surface.Example: "100-200 m"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactText
-Verbatim ElevationThe original description of the elevation (altitude, usually above sea level) of the Location.Example: "100-200 m"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactText
-Verbatim EventDateThe verbatim original representation of the date and time information for an Event.Examples: "spring 1910", "Marzo 2002", "1999-03-XX", "17IV1934"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/DateTime/DateText
-Verbatim LatitudeThe verbatim original latitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.Example: "41 05 54.03S"2008-11-192009-07-06recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLatitude
-Verbatim LocalityThe original textual description of the place.Example: "25 km NNE Bariloche por R. Nac. 237"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
-Verbatim LongitudeThe verbatim original longitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.Example: "121d 10' 34" W"2008-11-192009-07-06recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLongitude
-Verbatim SRSThe ellipsoid, geodetic datum, or spatial reference system (SRS) upon which coordinates given in verbatimLatitude and verbatimLongitude, or verbatimCoordinates are based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".Examples: "EPSG:4326", "WGS84", "NAD27", "Campo Inchauspe", "European 1950", "Clarke 1866"2009-07-062009-07-06recommendednot in ABCD
-Verbatim Taxon RankThe taxonomic rank of the most specific name in the scientificName as it appears in the original record.Examples: "Agamospecies", "sub-lesus", "prole", "apomict", "nothogrex", "sp.", "subsp.", "var."2009-07-062009-09-21recommendednot in ABCD
-Vernacular NameA common or vernacular name.Examples: "Andean Condor", "Condor Andino", "American Eagle", "Gänsegeier"2009-07-062009-07-06recommendednot in ABCD
-Water BodyThe name of the water body in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.Examples: "Indian Ocean", "Baltic Sea", "Hudson River"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Water body
-YearThe four-digit year in which the Event occurred, according to the Common Era Calendar.Example: "2008"2008-11-192009-04-24recommendedaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-
-
+
+
+ Accepted Name Usage
+ The full name, with authorship and date information if known, of the currently valid (zoological) or accepted (botanical) taxon.
+ Example: "Tamias minimus" valid name for "Eutamias minimus"
+
+ 2008-11-19
+ 2009-09-21
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Accepted Name Usage ID
+ An identifier for the name usage (documented meaning of the name according to a source) of the currently valid (zoological) or accepted (botanical) taxon.
+ Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"
+
+ 2009-01-21
+ 2009-09-21
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ According To
+ Abstract term to attribute information to a source.
+
+ 2009-01-21
+ 2009-01-21
+
+
+ recommended
+ not in ABCD
+
+
+ Associated Media
+ A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of media associated with the Occurrence.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "http://arctos.database.museum/SpecimenImages/UAMObs/Mamm/2/P7291179.JPG", "http://204.140.246.24/Fish/Collection%20Pictures/10118-00.jpg | http://204.140.246.24/Fish/Collection%20Pictures/10118-00a.jpg".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/MultimediaObjects
+
+
+
+ Associated Occurrences
+ A list (concatenated and separated) of identifiers of other Occurrence records and their associations to this Occurrence.
+ The recommended best practice is to separate the values with a vertical bar (' | ').
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
+
+
+
+ Associated Organisms
+ A list (concatenated and separated) of identifiers of other Organisms and their associations to this Organism.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "sibling of MXA-232", "mother of MXA-231 | mother of MXA-232"
+
+ 2014-10-23
+ 2014-10-23
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Associated References
+ A list (concatenated and separated) of identifiers (publication, bibliographic reference, global unique identifier, URI) of literature associated with the Occurrence.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "http://www.sciencemag.org/cgi/content/abstract/322/5899/261", "Christopher J. Conroy, Jennifer L. Neuwald. 2008. Phylogeographic study of the California vole, Microtus californicus Journal of Mammalogy, 89(3):755-767.", "Steven R. Hoofer and Ronald A. Van Den Bussche. 2001. Phylogenetic Relationships of Plecotine Bats and Allies Based on Mitochondrial Ribosomal Sequences. Journal of Mammalogy 82(1):131-137. | Walker, Faith M., Jeffrey T. Foster, Kevin P. Drees, Carol L. Chambers. 2014. Spotted bat (Euderma maculatum) microsatellite discovery using illumina sequencing. Conservation Genetics Resources.".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/UnitReferences
+
+
+
+ Associated Sequences
+ A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of genetic sequence information associated with the Occurrence.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "http://www.ncbi.nlm.nih.gov/nuccore/U34853.1", "http://www.ncbi.nlm.nih.gov/nuccore/GU328060 | http://www.ncbi.nlm.nih.gov/nuccore/AF326093".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Sequences/Sequence/ID-in-Database + constant
+
+
+
+ Associated Taxa
+ A list (concatenated and separated) of identifiers or names of taxa and their associations with the Occurrence.
+ The recommended best practice is to separate the values with a vertical bar (' | '), and to separate the relationship from the taxon with a colon (':'). Examples: "host: Quercus alba", "parasitoid of:Cyclocephala signaticollis | predator of Apis mellifera".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Gathering/Synecology/AssociatedTaxa
+
+
+
+ Basis of Record
+ The specific nature of the data record.
+ Recommended best practice is to use a controlled vocabulary such as the list of Darwin Core classes. Examples: "PreservedSpecimen", "FossilSpecimen", "LivingSpecimen", "HumanObservation", "MachineObservation"
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/RecordBasis
+
+
+
+ Bed
+ The full name of the lithostratigraphic bed from which the cataloged item was collected.
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Behavior
+ A description of the behavior shown by the subject at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.
+ Examples: "roosting", "foraging", "running"
+
+ 2009-03-06
+ 2009-04-24
+
+
+ recommended
+ not in ABCD
+
+
+
+ Catalog Number
+ An identifier (preferably unique) for the record within the data set or collection.
+ Examples: "2008.1334", "145732a", "145732"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/UnitID
+
+
+
+ Class
+ The full scientific name of the class in which the taxon is classified.
+ Examples: "Mammalia", "Hepaticopsida"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
+
+
+
+ Collection Code
+ The name, acronym, coden, or initialism identifying the collection or data set from which the record was derived.
+ Examples: "Mammals", "Hildebrandt", "eBird"
+
+ 2008-11-19
+ 2013-10-04
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/SourceID
+
+
+
+ Collection ID
+ An identifier for the collection or dataset from which the record was derived.
+ For physical specimens, the recommended best practice is to use an identifier from a collections registry such as the Global Registry of Biodiversity Repositories (http://grbio.org/). Examples: "http://biocol.org/urn:lsid:biocol.org:col:1001", "http://grbio.org/cool/p5fp-c036".
+
+ 2008-11-19
+ 2014-10-23
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/SourceID
+
+
+
+ Continent
+ The name of the continent in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
+ Examples: "Africa", "Antarctica", "Asia", "Europe", "North America", "Oceania", "South America"
+
+ 2008-11-19
+ 2013-10-04
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Continent
+
+
+
+ Coordinate Precision
+ A decimal representation of the precision of the coordinates given in the decimalLatitude and decimalLongitude.
+ Examples: "0.00001" (normal GPS limit for decimal degrees), "0.000278" (nearest second), "0.01667" (nearest minute), "1.0" (nearest degree)
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/ISOAccuracy or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/AccuracyStatement
+
+
+
+ Coordinate Uncertainty In Meters
+ The horizontal distance (in meters) from the given decimalLatitude and decimalLongitude describing the smallest circle containing the whole of the Location. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Zero is not a valid value for this term.
+ Examples: "30" (reasonable lower limit of a GPS reading under good conditions if the actual precision was not recorded at the time), "71" (uncertainty for a UTM coordinate having 100 meter precision and a known spatial reference system).
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinateErrorDistanceInMeters
+
+
+
+ Country
+ The name of the country or major administrative unit in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
+ Examples: "Denmark", "Colombia", "España"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Country/Name
+
+
+
+ Country Code
+ The standard code for the country in which the Location occurs. Recommended best practice is to use ISO 3166-1-alpha-2 country codes.
+ Examples: "AR" for Argentina, "SV" for El Salvador
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Country/ISO3166Code
+
+
+
+ County
+ The full, unabbreviated name of the next smaller administrative region than stateProvince (county, shire, department, etc.) in which the Location occurs.
+ Examples: "Missoula", "Los Lagos", "Mataró"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= County
+
+
+
+ Data Generalizations
+ Actions taken to make the shared data less specific or complete than in its original form. Suggests that alternative data of higher quality may be available on request.
+ Example: "Coordinates generalized from original GPS coordinates to the nearest half degree grid cell"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Dataset ID
+ An identifier for the set of data. May be a global unique identifier or an identifier specific to a collection or institution.
+
+ 2008-11-19
+ 2009-09-11
+
+
+
+
+ recommended
+ DataSets/DataSet/DataSetGUID
+
+
+
+ Dataset Name
+ The name identifying the data set from which the record was derived.
+ Examples: "Grinnell Resurvey Mammals", "Lacey Ctenomys Recaptures"
+
+ 2009-09-11
+ 2009-09-11
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/SourceID
+
+
+
+ Date Identified
+ The date on which the subject was identified as representing the Taxon. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "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.
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
+
+
+
+ Day
+ The integer day of the month on which the Event occurred.
+ Examples: "9", "28"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+
+ Decimal Latitude
+ The geographic latitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are north of the Equator, negative values are south of it. Legal values lie between -90 and 90, inclusive.
+ Example: "-41.0983423"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal
+
+
+
+ Decimal Longitude
+ The geographic longitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are east of the Greenwich Meridian, negative values are west of it. Legal values lie between -180 and 180, inclusive.
+ Example: "-121.1761111"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal
+
+
+
+ Disposition
+ The current state of a specimen with respect to the collection identified in collectionCode or collectionID. Recommended best practice is to use a controlled vocabulary.
+ Examples: "in collection", "missing", "voucher elsewhere", "duplicates elsewhere"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/SpecimenUnit/Disposition
+
+
+
+ Dynamic Properties
+ A list of additional measurements, facts, characteristics, or assertions about the record. Meant to provide a mechanism for structured content.
+ The recommended best practice is to use a key:value encoding schema such as JSON. Examples: "{'heightInMeters':'1.5'}", "{'tragusLengthInMeters':'0.014', 'weightInGrams':'120'}", "{'natureOfID':'expert identification', 'identificationEvidence':'cytochrome B sequence'}", "{'relativeHumidity':'28', 'airTemperatureInCelcius':'22', 'sampleSizeInKilograms':'10'}", "{'aspectHeading':'277', 'slopeInDegrees':'6'}", "{'iucnStatus':'vulnerable', 'taxonDistribution':'Neuquén, Argentina'}".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Earliest Age Or Lowest Stage
+ The full name of the earliest possible geochronologic age or lowest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Atlantic", "Boreal", "Skullrockian"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Earliest Eon Or Lowest Eonothem
+ The full name of the earliest possible geochronologic eon or lowest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Phanerozoic", "Proterozoic"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Earliest Epoch Or Lowest Series
+ The full name of the earliest possible geochronologic epoch or lowest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Holocene", "Pleistocene", "Ibexian Series"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Earliest Era Or Lowest Erathem
+ The full name of the earliest possible geochronologic era or lowest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Cenozoic", "Mesozoic"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Earliest Period Or Lowest System
+ The full name of the earliest possible geochronologic period or lowest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Neogene", "Tertiary", "Quaternary"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ End Day Of Year
+ The latest ordinal day of the year on which the Event occurred (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366).
+ Examples: "1" (=1 Jan), "366" (=31 Dec), "365" (=30 Dec in a leap year, 31 Dec in a non-leap year)
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberEnd
+
+
+
+ Establishment Means
+ The process by which the biological individual(s) represented in the Occurrence became established at the location. Recommended best practice is to use a controlled vocabulary.
+ Examples: "native", "introduced", "naturalised", "invasive", "managed"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/EstablishmentMeans
+
+
+
+ Event
+ An action that occurs at some location during some time.
+ Examples: A specimen collection process. A machine observation.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Gathering
+
+
+ Event Date
+ The date-time or interval during which an Event occurred. For occurrences, this is the date-time when the event was recorded. Not suitable for a time in a geological context. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "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.
+
+ 2009-04-24
+ 2009-07-01
+
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+
+ Event ID
+ An identifier for the set of information associated with an Event (something that occurs at a place and time). May be a global unique identifier or an identifier specific to the data set.
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Code
+
+
+
+ Event Remarks
+ Comments or notes about the Event.
+ Example: "after the recent rains the river is nearly at flood stage"
+
+ 2009-01-18
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Notes
+
+
+
+ Event Time
+ The time or interval during which an Event occurred. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "14:07-0600" is 2:07pm in the time zone six hours earlier than UTC, "08:40:21Z" is 8:40:21am UTC, "13:00:00Z/15:30:00Z" is the interval between 1pm UTC and 3:30pm UTC.
+
+ 2009-04-24
+ 2009-04-24
+
+
+
+
+ recommended
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin and DataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
+
+
+
+ Family
+ The full scientific name of the family in which the taxon is classified.
+ Examples: "Felidae", "Monocleaceae"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
+
+
+
+ Field Notes
+ One of a) an indicator of the existence of, b) a reference to (publication, URI), or c) the text of notes taken in the field about the Event.
+ Example: "notes available in Grinnell-Miller Library"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/FieldNotes
+
+
+
+ Field Number
+ An identifier given to the event in the field. Often serves as a link between field notes and the Event.
+ Example: "RV Sol 87-03-08"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Code
+
+
+
+ Footprint Spatial Fit
+ The ratio of the area of the footprint (footprintWKT) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given footprint does not completely contain the original representation. The footprintSpatialFit is undefined (and should be left blank) if the original representation is a point and the given georeference is not that same point. If both the original and the given georeference are the same point, the footprintSpatialFit is 1.
+ Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/FootprintSpatialFit (ABCD v2.06b)
+
+
+
+ Footprint SRS
+ A Well-Known Text (WKT) representation of the Spatial Reference System (SRS) for the footprintWKT of the Location. Do not use this term to describe the SRS of the decimalLatitude and decimalLongitude, even if it is the same as for the footprintWKT - use the geodeticDatum instead.
+ Example: The WKT for the standard WGS84 SRS (EPSG:4326) is "GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137,298.257223563]],PRIMEM["Greenwich",0],UNIT["Degree",0.0174532925199433]]" without the enclosing quotes.
+
+ 2009-07-06
+ 2009-07-06
+
+
+ recommended
+ not in ABCD
+
+
+
+ Footprint WKT
+ A Well-Known Text (WKT) representation of the shape (footprint, geometry) that defines the Location. A Location may have both a point-radius representation (see decimalLatitude) and a footprint representation, and they may differ from each other.
+ Example: the one-degree bounding box with opposite corners at (longitude=10, latitude=20) and (longitude=11, latitude=21) would be expressed in well-known text as POLYGON ((10 20, 11 20, 11 21, 10 21, 10 20))
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/FootprintWKT (ABCD v2.06b)
+
+
+
+ Formation
+ The full name of the lithostratigraphic formation from which the cataloged item was collected.
+ Examples: "Notch Peak Fromation", "House Limestone", "Fillmore Formation"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Fossil Specimen
+ A preserved specimen that is a fossil.
+
+ 2014-10-23
+ 2014-10-23
+
+
+
+ recommended
+
+ RecordBasisEnum/FossileSpecimen
+
+
+ Genus
+ The full scientific name of the genus in which the taxon is classified.
+ Examples: "Puma", "Monoclea"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
+
+
+
+ Geodetic Datum
+ The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which the geographic coordinates given in decimalLatitude and decimalLongitude as based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".
+ Examples: "EPSG:4326", "WGS84", "NAD27", "Campo Inchauspe", "European 1950", "Clarke 1866"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/SpatialDatum
+
+
+
+ Geological Context
+ Geological information, such as stratigraphy, that qualifies a region or place.
+ Example: A lithostratigraphic layer.
+
+ 2009-07-06
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Gathering/Stratigraphy
+
+
+ Geological Context ID
+ An identifier for the set of information associated with a GeologicalContext (the location within a geological context, such as stratigraphy). May be a global unique identifier or an identifier specific to the data set.
+
+ 2009-07-06
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Georeferenced By
+ A list (concatenated and separated) of names of people, groups, or organizations who determined the georeference (spatial representation) for the Location.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Brad Millen (ROM)", "Kristina Yamamoto (MVZ) | Janet Fang (MVZ)".
+
+ 2009-01-21
+ 2014-10-23
+
+
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Georeferenced Date
+ The date on which the Location was georeferenced. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "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.
+
+ 2011-10-16
+ 2011-10-16
+
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Georeference Protocol
+ A description or reference to the methods used to determine the spatial footprint, coordinates, and uncertainties.
+ Examples: "Guide to Best Practices for Georeferencing. (Chapman and Wieczorek, eds. 2006). Global Biodiversity Information Facility.", "MaNIS/HerpNet/ORNIS Georeferencing Guidelines", "Georeferencing Quick Reference Guide"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinateMethod
+
+
+
+ Georeference Remarks
+ Notes or comments about the spatial description determination, explaining assumptions made in addition or opposition to the those formalized in the method referred to in georeferenceProtocol.
+ Example: "assumed distance by road (Hwy. 101)"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceRemarks
+
+
+
+ Georeference Sources
+ A list (concatenated and separated) of maps, gazetteers, or other resources used to georeference the Location, described specifically enough to allow anyone in the future to use the same resources.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "GeoLocate", "USGS 1:24000 Florence Montana Quad | Terrametrics 2008 on Google Earth".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceSources
+
+
+
+ Georeference Verification Status
+ A categorical description of the extent to which the georeference has been verified to represent the best possible spatial description. Recommended best practice is to use a controlled vocabulary.
+ Examples: "requires verification", "verified by collector", "verified by curator".
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceVerificationStatus
+
+
+
+ Group
+ The full name of the lithostratigraphic group from which the cataloged item was collected.
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Habitat
+ A category or description of the habitat in which the Event occurred.
+ Examples: "oak savanna", "pre-cordilleran steppe"
+
+ 2008-11-19
+ 2009-05-17
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Biotope/Text
+
+
+
+ Higher Classification
+ A list (concatenated and separated) of taxa names terminating at the rank immediately superior to the taxon referenced in the taxon record.
+ The recommended best practice is to separate the values with a vertical bar (' | '), with terms in order from the highest taxonomic rank to the lowest. Examples: "Animalia", "Animalia | Chordata | Vertebrata | Mammalia | Theria | Eutheria | Rodentia | Hystricognatha | Hystricognathi | Ctenomyidae | Ctenomyini | Ctenomys".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Higher Geography
+ A list (concatenated and separated) of geographic names less specific than the information captured in the locality term.
+ The recommended best practice is to separate the values with a vertical bar (' | '), with terms in order from least specific to most specific. Examples: "North Atlantic Ocean", "South America | Argentina | Patagonia | Parque Nacional Nahuel Huapi | Neuquén | Los Lagos" with accompanying values "South America" in Continent, "Argentina" in Country, "Neuquén" in StateProvince, and "Los Lagos" in County.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ {DataSets/DataSet/Units/Unit/Gathering/LocalityText or DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName}
+
+
+
+ Higher Geography ID
+ An identifier for the geographic region within which the Location occurred. Recommended best practice is to use an persistent identifier from a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
+ Example: "TGN: 1002002" for Prov. Tierra del Fuego, Argentina
+
+ 2009-01-21
+ 2009-04-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Highest Biostratigraphic Zone
+ The full name of the highest possible geological biostratigraphic zone of the stratigraphic horizon from which the cataloged item was collected.
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Human Observation
+ An output of a human observation process.
+
+ 2014-10-23
+ 2014-10-23
+
+
+
+ recommended
+
+ RecordBasisEnum/HumanObservation
+
+
+ Identification
+ A taxonomic determination (e.g., the assignment to a taxon).
+ Example: A subspecies determination of an organism.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Identifications/Identification
+
+
+ Identification ID
+ An identifier for the Identification (the body of information associated with the assignment of a scientific name). May be a global unique identifier or an identifier specific to the data set.
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Identification Qualifier
+ A brief phrase or a standard term ("cf.", "aff.") to express the determiner's doubts about the Identification.
+ Examples: 1) For the determination "Quercus aff. agrifolia var. oxyadenia", identificationQualifier would be "aff. agrifolia var. oxyadenia" with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank. 2) For the determination "Quercus agrifolia cf. var. oxyadenia", identificationQualifier would be "cf. var. oxyadenia " with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank.
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/IdentificationQualifier
+
+
+
+ Identification References
+ A list (concatenated and separated) of references (publication, global unique identifier, URI) used in the Identification.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Aves del Noroeste Patagonico. Christie et al. 2004.", "Stebbins, R. Field Guide to Western Reptiles and Amphibians. 3rd Edition. 2003. | Irschick, D.J. and Shaffer, H.B. (1997). ''The polytypic species revisited: Morphological differentiation among tiger salamanders (Ambystoma tigrinum) (Amphibia: Caudata).'' Herpetologica, 53(1), 30-49.".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Identifications/Identification/References
+
+
+
+ Identification Remarks
+ Comments or notes about the Identification.
+ Example: "Distinguished between Anthus correndera and Anthus hellmayri based on the comparative lengths of the uñas."
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Notes
+
+
+
+ Identification Verification Status
+ A categorical indicator of the extent to which the taxonomic identification has been verified to be correct. Recommended best practice is to use a controlled vocabulary such as that used in HISPID/ABCD.
+ Examples: "0", "4"
+
+ 2011-10-16
+ 2011-10-16
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Identified By
+ A list (concatenated and separated) of names of people, groups, or organizations who assigned the Taxon to the subject.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "James L. Patton", "Theodore Pappenfuss | Robert Macey".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Identifiers/IdentifiersText
+
+
+
+ Individual Count
+ The number of individuals represented present at the time of the Occurrence.
+ Examples: "1", "25"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue
+
+
+
+ Information Withheld
+ Additional information that exists, but that has not been shared in the given record.
+ Examples: "location information not given for endangered species", "collector identities withheld", "ask about tissue samples"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/InformationWithheld
+
+
+
+ Infraspecific Epithet
+ The name of the lowest or terminal infraspecific epithet of the scientificName, excluding any rank designation.
+ Examples: "concolor", "oxyadenia", "sayi"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
+
+
+
+ Institution Code
+ The name (or acronym) in use by the institution having custody of the object(s) or information referred to in the record.
+ Examples: "MVZ", "FMNH", "AKN-CLO", "University of California Museum of Paleontology (UCMP)"
+
+ 2008-11-19
+ 2013-10-04
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/SourceInstitutionID
+
+
+
+ Institution ID
+ An identifier for the institution having custody of the object(s) or information referred to in the record.
+ For physical specimens, the recommended best practice is to use an identifier from a collections registry such as the Global Registry of Biodiversity Repositories (http://grbio.org/). Examples: "http://biocol.org/urn:lsid:biocol.org:col:34777", "http://grbio.org/cool/km06-gtbn".
+
+ 2009-09-11
+ 2014-10-23
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/SourceInstitutionID
+
+
+
+ Island
+ The name of the island on or near which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
+ Examples: "Isla Victoria", "Vancouver", "Viti Levu", "Zanzibar"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island
+
+
+
+ Island Group
+ The name of the island group in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
+ Examples: "Alexander Archipelago", "Seychelles"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island group
+
+
+
+ Kingdom
+ The full scientific name of the kingdom in which the taxon is classified.
+ Examples: "Animalia", "Plantae"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
+
+
+
+ Latest AgeOr Highest Stage
+ The full name of the latest possible geochronologic age or highest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Atlantic", "Boreal", "Skullrockian"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Latest Eon Or Highest Eonothem
+ The full name of the latest possible geochronologic eon or highest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Phanerozoic", "Proterozoic"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Latest Epoch Or Highest Series
+ The full name of the latest possible geochronologic epoch or highest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Holocene", "Pleistocene", "Ibexian Series"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Latest Era Or Highest Erathem
+ The full name of the latest possible geochronologic era or highest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Cenozoic", "Mesozoic"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Latest Period Or Highest System
+ The full name of the latest possible geochronologic period or highest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Neogene", "Tertiary", "Quaternary"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Life Stage
+ The age class or life stage of the biological individual(s) at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.
+ Examples: "egg", "eft", "juvenile", "adult", "2 adults 4 juveniles"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLiveStages/MycologicalLiveStage (Note DwC spec uses ”MycologicalLifeStage” or DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage
+
+
+
+ Lithostratigraphic Terms
+ The combination of all litho-stratigraphic names for the rock from which the cataloged item was collected.
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Stratigraphy/LithostratigraphicTerms
+
+
+
+ Living Specimen
+ A specimen that is alive.
+
+ 2014-10-23
+ 2014-10-23
+
+
+
+ recommended
+
+ RecordBasisEnum/LivingSpecimen
+
+
+ Locality
+ The specific description of the place. Less specific geographic information can be provided in other geographic terms (higherGeography, continent, country, stateProvince, county, municipality, waterBody, island, islandGroup). This term may contain information modified from the original to correct perceived errors or standardize the description.
+ Example: "Bariloche, 25 km NNE via Ruta Nacional 40 (=Ruta 237)"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
+
+
+
+ Location According To
+ Information about the source of this Location information. Could be a publication (gazetteer), institution, or team of individuals.
+ Examples: "Getty Thesaurus of Geographic Names", "GADM"
+
+ 2009-08-24
+ 2009-08-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Location ID
+ An identifier for the set of location information (data associated with dcterms:Location). May be a global unique identifier or an identifier specific to the data set.
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Location Remarks
+ Comments or notes about the Location.
+ Example: "under water since 2005"
+
+ 2009-01-18
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/AreaDetail
+
+
+
+ Lowest Biostratigraphic Zone
+ The full name of the lowest possible geological biostratigraphic zone of the stratigraphic horizon from which the cataloged item was collected.
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Machine Observation
+ An output of a machine observation process.
+
+ 2014-10-23
+ 2014-10-23
+
+
+
+ recommended
+
+ RecordBasisEnum/MachineObservation
+
+
+ Material Sample
+ A physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.
+ Examples: A whole organism preserved in a collection. A part of an organism isolated for some purpose. A soil sample. A marine microbial sample.
+
+ 2013-03-28
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit
+
+
+ Material Sample ID
+ An identifier for the MaterialSample (as opposed to a particular digital record of the material sample). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the materialSampleID globally unique.
+
+ 2013-03-28
+ 2013-09-26
+
+
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Maximum Depth In Meters
+ The greater depth of a range of depth below the local surface, in meters.
+ Example: "200"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue
+
+
+
+ Maximum Distance Above Surface In Meters
+ The greater distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.
+ Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
+
+
+
+ Maximum Elevation In Meters
+ The upper limit of the range of elevation (altitude, usually above sea level), in meters.
+ Example: "200"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue
+
+
+
+ Measurement Accuracy
+ The description of the potential error associated with the measurementValue.
+ Examples: "0.01", "normal distribution with variation of 2 m"
+
+ 2009-01-18
+ 2009-04-24
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
+
+
+
+ Measurement Determined By
+ A list (concatenated and separated) of names of people, groups, or organizations who determined the value of the MeasurementOrFact.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Rob Guralnick", "Julie Woodruff | Eileen Lacey".
+
+ 2009-01-23
+ 2014-10-23
+
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
+
+
+
+ Measurement Determined Date
+ The date on which the MeasurementOrFact was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "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.
+
+ 2009-01-23
+ 2009-04-24
+
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
+
+
+
+ Measurement ID
+ An identifier for the MeasurementOrFact (information pertaining to measurements, facts, characteristics, or assertions). May be a global unique identifier or an identifier specific to the data set.
+
+ 2009-03-06
+ 2009-04-24
+
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Measurement Method
+ A description of or reference to (publication, URI) the method or protocol used to determine the measurement, fact, characteristic, or assertion.
+ Examples: "minimum convex polygon around burrow entrances" for a home range area, "barometric altimeter" for an elevation
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ /DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Method or /DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Method or /DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Method
+
+
+
+ Measurement or Fact
+ A measurement of or fact about an rdfs:Resource (http://www.w3.org/2000/01/rdf-schema#Resource).
+ Resources can be thought of as identifiable records or instances of classes and may include, but need not be limited to Occurrences, Organisms, MaterialSamples, Events, Locations, GeologicalContexts, Identifications, or Taxa. Examples: The weight of an organism in grams. The number of placental scars.
+
+ 2009-04-24
+ 2014-10-23
+
+
+
+ recommended
+
+ Datasets/Dataset/Units/Unit/MeasurementsOrFacts or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts
+
+
+ Measurement Remarks
+ Comments or notes accompanying the MeasurementOrFact.
+ Example: "tip of tail missing"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Measurement Type
+ The nature of the measurement, fact, characteristic, or assertion. Recommended best practice is to use a controlled vocabulary.
+ Examples: "tail length", "temperature", "trap line length", "survey area", "trap type"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
+
+
+
+ Measurement Unit
+ The units associated with the measurementValue. Recommended best practice is to use the International System of Units (SI).
+ Examples: "mm", "C", "km", "ha"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
+
+
+
+ Measurement Value
+ The value of the measurement, fact, characteristic, or assertion.
+ Examples: "45", "20", "1", "14.5", "UV-light"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
+
+
+
+ Member
+ The full name of the lithostratigraphic member from which the cataloged item was collected.
+ Examples: "Lava Dam Member", "Hellnmaria Member"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Minimum Depth In Meters
+ The lesser depth of a range of depth below the local surface, in meters.
+ Example: "100"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue
+
+
+
+ Minimum Distance Above Surface In Meters
+ The lesser distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.
+ Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue
+
+
+
+ Minimum Elevation In Meters
+ The lower limit of the range of elevation (altitude, usually above sea level), in meters.
+ Example: "100"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue
+
+
+
+ Month
+ The ordinal month in which the Event occurred.
+ Examples: "1" (=January), "10" (=October)
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+
+ Municipality
+ The full, unabbreviated name of the next smaller administrative region than county (city, municipality, etc.) in which the Location occurs. Do not use this term for a nearby named place that does not contain the actual location.
+ Examples: "Holzminden"
+
+ 2008-11-19
+ 2009-08-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
+
+
+
+ Name According To
+ The reference to the source in which the specific taxon concept circumscription is defined or implied - traditionally signified by the Latin "sensu" or "sec." (from secundum, meaning "according to"). For taxa that result from identifications, a reference to the keys, monographs, experts and other sources should be given.
+ Example: "McCranie, J. R., D. B. Wake, and L. D. Wilson. 1996. The taxonomic status of Bolitoglossa schmidti, with comments on the biology of the Mesoamerican salamander Bolitoglossa dofleini (Caudata: Plethodontidae). Carib. J. Sci. 32:395-398.", "Werner Greuter 2008", "Lilljeborg 1861, Upsala Univ. Arsskrift, Math. Naturvet., pp. 4, 5"
+
+ 2008-11-19
+ 2009-09-21
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Name According To ID
+ An identifier for the source in which the specific taxon concept circumscription is defined or implied. See nameAccordingTo.
+ Example: "doi:10.1016/S0269-915X(97)80026-2"
+
+ 2009-08-24
+ 2009-09-21
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Name Published In
+ A reference for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.
+ Examples: "Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "Forel, Auguste, Diagnosies provisoires de quelques espèces nouvelles de fourmis de Madagascar, récoltées par M. Grandidier., Annales de la Societe Entomologique de Belgique, Comptes-rendus des Seances 30, 1886"
+
+ 2008-11-19
+ 2009-09-21
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference/TitleCitation
+
+
+
+ Name Published In ID
+ An identifier for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.
+ Example: "http://hdl.handle.net/10199/7"
+
+ 2009-05-18
+ 2009-09-21
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Name Published In Year
+ The four-digit year in which the scientificName was published.
+ Examples: "1915", "2008"
+
+ 2011-10-16
+ 2011-10-16
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Nomenclatural Code
+ The nomenclatural code (or codes in the case of an ambiregnal name) under which the scientificName is constructed. Recommended best practice is to use a controlled vocabulary.
+ Examples: "ICBN", "ICZN", "BC", "ICNCP", "BioCode", "ICZN; ICBN"
+
+ 2008-11-19
+ 2009-09-21
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/Code
+
+
+
+ Nomenclatural Status
+ The status related to the original publication of the name and its conformance to the relevant rules of nomenclature. It is based essentially on an algorithm according to the business rules of the code. It requires no taxonomic opinion.
+ Examples: "nom. ambig.", "nom. illeg.", "nom. subnud."
+
+ 2009-01-18
+ 2009-04-24
+
+
+ recommended
+ (DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference/TitleCitation) pro parte
+
+
+
+ Occurrence
+ An existence of an Organism (sensu http://rs.tdwg.org/dwc/terms/Organism) at a particular place at a particular time.
+ Examples: A wolf pack on the shore of Kluane Lake in 1988. A virus in a plant leaf in a the New York Botanical Garden at 15:29 on 2014-10-23. A fungus in Central Park in the summer of 1929.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit
+
+
+ Occurrence ID
+ An identifier for the Occurrence (as opposed to a particular digital record of the occurrence). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the occurrenceID globally unique.
+ For a specimen in the absence of a bona fide global unique identifier, for example, use the form: "urn:catalog:[institutionCode]:[collectionCode]:[catalogNumber]. Examples: "urn:lsid:nhm.ku.edu:Herps:32", "urn:catalog:FMNH:Mammal:145732"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/UnitGUID
+
+
+
+ Occurrence Remarks
+ Comments or notes about the Occurrence.
+ Example: "found dead on road"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Notes
+
+
+
+ Occurrence Status
+ A statement about the presence or absence of a Taxon at a Location. Recommended best practice is to use a controlled vocabulary.
+ Examples: "present", "absent"
+
+ 2009-09-17
+ 2009-09-17
+
+
+ recommended
+ not in ABCD
+
+
+
+ Order
+ The full scientific name of the order in which the taxon is classified.
+ Examples: "Carnivora", "Monocleales"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
+
+
+
+ Organism
+ A particular organism or defined group of organisms considered to be taxonomically homogeneous.
+ Instances of the Organism class are intended to facilitate linking of one or more Identification instances to one or more Occurrence instances. Therefore, things that are typically assigned scientific names (such as viruses, hybrids, and lichens) and aggregates whose occurrences are typically recorded (such as packs, clones, and colonies) are included in the scope of this class.
+
+ 2014-10-23
+ 2014-10-23
+
+
+ recommended
+
+ not in ABCD
+
+
+ Organism ID
+ An identifier for the Organism instance (as opposed to a particular digital record of the Organism). May be a globally unique identifier or an identifier specific to the data set.
+
+ 2014-10-23
+ 2014-10-23
+
+
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Organism Name
+ A textual name or label assigned to an Organism instance.
+ Examples: "Huberta", "Boab Prison Tree", "J pod".
+
+ 2014-10-23
+ 2014-10-23
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Organism Remarks
+ Comments or notes about the Organism instance.
+ Example: "One of a litter of six."
+
+ 2014-10-23
+ 2014-10-23
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Organism Scope
+ A description of the kind of Organism instance. Can be used to indicate whether the Organism instance represents a discrete organism or if it represents a particular type of aggregation. Recommended best practice is to use a controlled vocabulary.
+ This term is not intended to be used to specify a type of taxon. To describe the kind of Organism using a URI object in RDF, use rdf:type (http://www.w3.org/1999/02/22-rdf-syntax-ns#type) instead. Examples: "multicellular organism", "virus", "clone" "pack", "colony".
+
+ 2014-10-23
+ 2014-10-23
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Original Name Usage
+ The taxon name, with authorship and date information if known, as it originally appeared when first established under the rules of the associated nomenclaturalCode. The basionym (botany) or basonym (bacteriology) of the scientificName or the senior/earlier homonym for replaced names.
+ Examples: "Pinus abies", "Gasterosteus saltatrix Linnaeus 1768"
+
+ 2008-11-19
+ 2009-09-21
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Original Name Usage ID
+ An identifier for the name usage (documented meaning of the name according to a source) in which the terminal element of the scientificName was originally established under the rules of the associated nomenclaturalCode.
+ Example: "http://species.gbif.org/abies_alba_1753"
+
+ 2009-01-21
+ 2009-09-21
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Other Catalog Numbers
+ A list (concatenated and separated) of previous or alternate fully qualified catalog numbers or other human-used identifiers for the same Occurrence, whether in the current or any other data set or collection.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "FMNH:Mammal:1234", "NPS YELLO6778 | MBG 33424".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/SpecimenUnit/History/PreviousUnitsText
+
+
+
+ Owner Institution Code
+ The name (or acronym) in use by the institution having ownership of the object(s) or information referred to in the record.
+ Examples: "NPS", "APN", "InBio"
+
+ 2009-08-24
+ 2013-10-04
+
+
+ recommended
+ not in ABCD
+
+
+
+ Parent Name Usage
+ The full name, with authorship and date information if known, of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.
+ Examples: "Rubiaceae", "Gruiformes", "Testudinae"
+
+ 2009-08-24
+ 2009-09-21
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+
+
+
+ Parent Name Usage ID
+ An identifier for the name usage (documented meaning of the name according to a source) of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.
+ Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"
+
+ 2009-01-21
+ 2009-09-21
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Phylum
+ The full scientific name of the phylum or division in which the taxon is classified.
+ Examples: "Chordata" (phylum), "Bryophyta" (division)
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
+
+
+
+ Point Radius Spatial Fit
+ The ratio of the area of the point-radius (decimalLatitude, decimalLongitude, coordinateUncertaintyInMeters) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given point-radius does not completely contain the original representation. The pointRadiusSpatialFit is undefined (and should be left blank) if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the pointRadiusSpatialFit is 1.
+ Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/PointRadiusSpatialFit
+
+
+
+ Preparations
+ A list (concatenated and separated) of preparations and preservation methods for a specimen.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "fossil", "cast", "photograph", "DNA extract", "skin | "skull | skeleton", "whole animal (ETOH) | tissue (EDTA)".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/PreparationsText
+
+
+
+ Preserved Specimen
+ A specimen that has been preserved.
+
+ 2014-10-23
+ 2014-10-23
+
+
+
+ recommended
+
+ RecordBasisEnum/PreservedSpecimen
+
+
+ Previous Identifications
+ A list (concatenated and separated) of previous assignments of names to the Organism.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Chalepidae", "Pinus abies", "Anthus sp., field ID by G. Iglesias | Anthus correndera, expert ID by C. Cicero 2009-02-12 based on morphology".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Identifications/Identification with PreferredFlag = false
+
+
+
+ Recorded By
+ A list (concatenated and separated) of names of people, groups, or organizations responsible for recording the original Occurrence. The primary collector or observer, especially one who applies a personal identifier (recordNumber), should be listed first.
+ The recommended best practice is to separate the values with a vertical bar (' | '). The primary collector or observer, especially one who applies a personal identifier (recordNumber), should be listed first. Examples: "José E. Crespo", "Oliver P. Pearson | Anita K. Pearson" where the value in recordNumber "OPP 7101" corresponds to the number for the specimen in the field catalog (collector number) of Oliver P. Pearson.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Gathering/GatheringAgents/GatheringAgentsText
+
+
+
+ Record Number
+ An identifier given to the Occurrence at the time it was recorded. Often serves as a link between field notes and an Occurrence record, such as a specimen collector's number.
+ Example: "OPP 7101"
+
+ 2008-11-19
+ 2009-05-18
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/CollectorsFieldNumber
+
+
+
+ Related Resource ID
+ An identifier for a related resource (the object, rather than the subject of the relationship).
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
+
+
+
+ Relationship According To
+ The source (person, organization, publication, reference) establishing the relationship between the two resources.
+ Example: "Julie Woodruff"
+
+ 2009-04-24
+ 2009-04-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Relationship Established Date
+ The date-time on which the relationship between the two resources was established. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "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.
+
+ 2009-04-24
+ 2009-04-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Relationship Of Resource
+ The relationship of the resource identified by relatedResourceID to the subject (optionally identified by the resourceID). Recommended best practice is to use a controlled vocabulary.
+ Examples: "duplicate of", "mother of", "endoparasite of", "host to", "sibling of", "valid synonym of", "located within"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociationType
+
+
+
+ Relationship Remarks
+ Comments or notes about the relationship between the two resources.
+ Examples: "mother and offspring collected from the same nest", "pollinator captured in the act"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Associations/UnitAssociation/Comments
+
+
+
+ Reproductive Condition
+ The reproductive condition of the biological individual(s) represented in the Occurrence. Recommended best practice is to use a controlled vocabulary.
+ Examples" "non-reproductive", "pregnant", "in bloom", "fruit-bearing"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ not in ABCD
+
+
+
+ Resource ID
+ An identifier for the resource that is the subject of the relationship.
+
+ 2009-04-24
+ 2009-04-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Resource Relationship
+ A relationship of one rdfs:Resource (http://www.w3.org/2000/01/rdf-schema#Resource) to another.
+ Resources can be thought of as identifiable records or instances of classes and may include, but need not be limited to Occurrences, Organisms, MaterialSamples, Events, Locations, GeologicalContexts, Identifications, or Taxa. Example: An instance of an Organism is the mother of another instance of an Organism.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Associations
+
+
+ Resource Relationship ID
+ An identifier for an instance of relationship between one resource (the subject) and another (relatedResource, the object).
+
+ 2009-01-26
+ 2009-04-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Sampling Effort
+ The amount of effort expended during an Event.
+ Examples: "40 trap-nights", "10 observer-hours; 10 km by foot; 30 km by car"
+
+ 2009-08-24
+ 2009-08-24
+
+
+ recommended
+ not in ABCD
+
+
+
+ Sampling Protocol
+ The name of, reference to, or description of the method or protocol used during an Event.
+ Examples: "UV light trap", "mist net", "bottom trawl", "ad hoc observation", "point count", "Penguins from space: faecal stains reveal the location of emperor penguin colonies, http://dx.doi.org/10.1111/j.1466-8238.2009.00467.x", "Takats et al. 2001. Guidelines for Nocturnal Owl Monitoring in North America. Beaverhill Bird Observatory and Bird Studies Canada, Edmonton, Alberta. 32 pp.", "http://www.bsc-eoc.org/download/Owl.pdf"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Method
+
+
+
+ Scientific Name
+ The full scientific name, with authorship and date information if known. When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the IdentificationQualifier term.
+ Examples: "Coleoptera" (order), "Vespertilionidae" (family), "Manis" (genus), "Ctenomys sociabilis" (genus + specificEpithet), "Ambystoma tigrinum diaboli" (genus + specificEpithet + infraspecificEpithet), "Roptrocerus typographi (Györfi, 1952)" (genus + specificEpithet + scientificNameAuthorship), "Quercus agrifolia var. oxyadenia (Torr.) J.T. Howell" (genus + specificEpithet + taxonRank + infraspecificEpithet + scientificNameAuthorship)
+
+ 2008-11-19
+ 2009-09-21
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/FullScientificNameString
+
+
+
+ Scientific Name Authorship
+ The authorship information for the scientificName formatted according to the conventions of the applicable nomenclaturalCode.
+ Example: "(Torr.) J.T. Howell", "(Martinovský) Tzvelev", "(Györfi, 1952)"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/ParentheticalAuthorTeamAndYear + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/AuthorTeamAndYear} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeamParenthesis + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeam} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamOriginalAndYear + [= or] DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamParenthesisAndYear}
+
+
+
+ Scientific Name ID
+ An identifier for the nomenclatural (not taxonomic) details of a scientific name.
+ Example: "urn:lsid:ipni.org:names:37829-1:1.3"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Sex
+ The sex of the biological individual(s) represented in the Occurrence. Recommended best practice is to use a controlled vocabulary.
+ Examples: "female", "hermaphrodite", "8 males, 4 females"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Sex
+
+
+
+ Specific Epithet
+ The name of the first or species epithet of the scientificName.
+ Examples: "concolor", "gottschei"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
+
+
+
+ Start Day Of Year
+ The earliest ordinal day of the year on which the Event occurred (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366).
+ Examples: "1" (=1 Jan), "366" (=31 Dec), "365" (=30 Dec in a leap year, 31 Dec in a non-leap year)
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberBegin
+
+
+
+ State Province
+ The name of the next smaller administrative region than country (state, province, canton, department, region, etc.) in which the Location occurs.
+ Examples: "Montana", "Minas Gerais", "Córdoba"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= State or = Province (etc.)
+
+
+
+ Subgenus
+ The full scientific name of the subgenus in which the taxon is classified. Values should include the genus to avoid homonym confusion.
+ Examples: "Strobus (Pinus)", "Puma (Puma)" "Loligo (Amerigo)", "Hieracium subgen. Pilosella"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/Subgenus
+
+
+
+ Taxon
+ A group of organisms (sensu http://purl.obolibrary.org/obo/OBI_0100026) considered by taxonomists to form a homogeneous unit.
+ Example: The genus Truncorotaloides as published by Brönnimann et al. in 1953 in the Journal of Paleontology Vol. 27(6) p. 817-820.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ no simple equivalent in ABCD
+
+
+ Taxon Concept ID
+ An identifier for the taxonomic concept to which the record refers - not for the nomenclatural details of a taxon.
+ Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"
+
+ 2009-04-24
+ 2009-09-21
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Taxon ID
+ An identifier for the set of taxon information (data associated with the Taxon class). May be a global unique identifier or an identifier specific to the data set.
+ Examples: "8fa58e08-08de-4ac1-b69c-1235340b7001", "32567", "http://species.gbif.org/abies_alba_1753", "urn:lsid:gbif.org:usages:32567"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Taxonomic Status
+ The status of the use of the scientificName as a label for a taxon. Requires taxonomic opinion to define the scope of a taxon. Rules of priority then are used to define the taxonomic status of the nomenclature contained in that scope, combined with the experts opinion. It must be linked to a specific taxonomic reference that defines the concept. Recommended best practice is to use a controlled vocabulary.
+ Examples: "invalid", "misapplied", "homotypic synonym", "accepted"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ not in ABCD
+
+
+
+ Taxon Rank
+ The taxonomic rank of the most specific name in the scientificName. Recommended best practice is to use a controlled vocabulary.
+ Examples: "subspecies", "varietas", "forma", "species", "genus"
+
+ 2008-11-19
+ 2009-09-21
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Rank
+
+
+
+ Taxon Remarks
+ Comments or notes about the taxon or name.
+ Example: "this name is a misspelling in common use"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Type Status
+ A list (concatenated and separated) of nomenclatural types (type status, typified scientific name, publication) applied to the subject.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "holotype of Ctenomys sociabilis. Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "holotype of Pinus abies | holotype of Picea abies".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeText
+
+
+
+ Verbatim Coordinates
+ The verbatim original spatial coordinates of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
+ Examples: "41 05 54S 121 05 34W", "17T 630000 4833400"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ recommended
+ {DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinatesText or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesUTM/UTMText}
+
+
+
+ Verbatim Coordinate System
+ The spatial coordinate system for the verbatimLatitude and verbatimLongitude or the verbatimCoordinates of the Location. Recommended best practice is to use a controlled vocabulary.
+ Examples: "decimal degrees", "degrees decimal minutes", "degrees minutes seconds", "UTM"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ recommended
+ (partly) DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesGrid/GridCellSystem
+
+
+
+ Verbatim Depth
+ The original description of the depth below the local surface.
+ Example: "100-200 m"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactText
+
+
+
+ Verbatim Elevation
+ The original description of the elevation (altitude, usually above sea level) of the Location.
+ Example: "100-200 m"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactText
+
+
+
+ Verbatim EventDate
+ The verbatim original representation of the date and time information for an Event.
+ Examples: "spring 1910", "Marzo 2002", "1999-03-XX", "17IV1934"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/DateText
+
+
+
+ Verbatim Latitude
+ The verbatim original latitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
+ Example: "41 05 54.03S"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLatitude
+
+
+
+ Verbatim Locality
+ The original textual description of the place.
+ Example: "25 km NNE Bariloche por R. Nac. 237"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
+
+
+
+ Verbatim Longitude
+ The verbatim original longitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
+ Example: "121d 10' 34" W"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLongitude
+
+
+
+ Verbatim SRS
+ The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which coordinates given in verbatimLatitude and verbatimLongitude, or verbatimCoordinates are based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".
+ Examples: "EPSG:4326", "WGS84", "NAD27", "Campo Inchauspe", "European 1950", "Clarke 1866"
+
+ 2009-07-06
+ 2009-07-06
+
+
+ recommended
+ not in ABCD
+
+
+
+ Verbatim Taxon Rank
+ The taxonomic rank of the most specific name in the scientificName as it appears in the original record.
+ Examples: "Agamospecies", "sub-lesus", "prole", "apomict", "nothogrex", "sp.", "subsp.", "var."
+
+ 2009-07-06
+ 2009-09-21
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Vernacular Name
+ A common or vernacular name.
+ Examples: "Andean Condor", "Condor Andino", "American Eagle", "Gänsegeier"
+
+ 2009-07-06
+ 2009-07-06
+
+
+ recommended
+ not in ABCD
+
+
+
+ Water Body
+ The name of the water body in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
+ Examples: "Indian Ocean", "Baltic Sea", "Hudson River"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Water body
+
+
+
+ Year
+ The four-digit year in which the Event occurred, according to the Common Era Calendar.
+ Example: "2008"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+
\ No newline at end of file
diff --git a/rdf/dwctermshistory.rdf b/rdf/dwctermshistory.rdf
index 69a3992..f1950c9 100644
--- a/rdf/dwctermshistory.rdf
+++ b/rdf/dwctermshistory.rdf
@@ -1,34 +1,35 @@
-
-
-
-
+
+
+
+
+
+
]>
-
-Darwin Core Terms Complete History
-This is the normative (Type 1) document for the terms in the Darwin Core standard (http://www.tdwg.org/standards/450/). It contains a list of all versions of all Darwin Core terms. To comment on this schema, please create a new issue in http://code.google.com/p/darwincore/issues/
-Biodiversity Information Standards (TDWG)
-2013-10-22
-
-
-
-
-
-Accepted Name UsageThe full name, with authorship and date information if known, of the currently valid (zoological) or accepted (botanical) taxon.Example: "Tamias minimus" valid name for "Eutamias minimus"2008-11-192009-09-21recommendednot in ABCD
-Accepted Name Usage IDAn identifier for the name usage (documented meaning of the name according to a source) of the currently valid (zoological) or accepted (botanical) taxon.Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"2009-01-212009-09-21recommendednot in ABCD
-Accepted Scientific NameThe currently valid (zoological) or accepted (botanical) name for the scientificName.Example: "Tamias minimus" valid name for "Eutamias minimus"2008-11-192009-07-06supersedednot in ABCD
-Accepted Scientific Name IDA unique identifier for the acceptedScientificName.2009-01-212009-07-06supersedednot in ABCD
-Accepted TaxonThe currently valid (zoological) or accepted (botanical) name for the ScientificName.2008-11-192008-11-19supersedednot in ABCD
-Accepted Taxon IDA global unique identifier for the parent to the AcceptedTaxon.2009-01-212009-01-21supersedednot in ABCD
-Accepted Taxon IDAn identifier for the name of the currently valid (zoological) or accepted (botanical) taxon. See acceptedTaxon.Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"2009-01-212009-08-24supersedednot in ABCD
-Accepted Taxon NameThe currently valid (zoological) or accepted (botanical) name for the scientificName.Example: "Tamias minimus" valid name for "Eutamias minimus"2008-11-192009-04-24supersedednot in ABCD
-Accepted Taxon Name IDA unique identifier for the acceptedTaxonName.2009-01-212009-04-24supersedednot in ABCD
-Access ConstraintsA description of constraints on the use of the data as shared or access to further data that is not shared.Example: "not-for-profit use only".2008-11-192008-11-19supersededDataSets/DataSet/Units/Unit/IPRStatements
-According ToAbstract term to attribute information to a source.2009-01-212009-01-21recommendednot in ABCD
-AccuracyAbstract term to capture error information about a measurement or fact.2009-01-212009-01-21deprecatedDataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
-Age ClassThe age class, reproductive stage, life stage of the biological individual (e.g., juvenile, adult, eft, nymph, etc.).2003-06-172003-06-17superseded{DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLifeStages/MycologicalLifeStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage}
-Associated MediaA list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of media associated with the Occurrence.Example: "http://arctos.database.museum/SpecimenImages/UAMObs/Mamm/2/P7291179.JPG"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/MultimediaObjects
-Associated OccurrencesA list (concatenated and separated) of identifiers of other Occurrence records and their associations to this Occurrence.Example: "sibling of FMNH:Mammal:1234; sibling of FMNH:Mammal:1235"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
-Associated ReferencesA list (concatenated and separated) of identifiers (publication, bibliographic reference, global unique identifier, URI) of literature associated with the Occurrence.Examples: "http://www.sciencemag.org/cgi/content/abstract/322/5899/261", "Christopher J. Conroy, Jennifer L. Neuwald. 2008. Phylogeographic study of the California vole, Microtus californicus Journal of Mammalogy, 89(3):755-767."2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/UnitReferences
-Associated SequencesA list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of genetic sequence information associated with the Occurrence.Example: "GenBank: U34853.1"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Sequences/Sequence/ID-in-Database + constant
-Associated TaxaA list (concatenated and separated) of identifiers or names of taxa and their associations with the Occurrence.Example: "host: Quercus alba"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Synecology/AssociatedTaxa
-AttributesList of additional measurements or characteristics (concatenated and separated) for which there is no existing semantic element, but which the data provider nevertheless feels the desire to share. Examples: "Tragus length: 14mm; Weight: 120g", "Height: 1-1.5 meters tall; flowers yellow; uncommon".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/MeasurementsOrFacts
-Author Year of Scientific NameThe author of the ScientificName and the year of publication, if known. More than one author can be listed in a concatenated string. Should be formatted with parentheses and year according to the conventions of the applicable NomenclaturalCode.2007-04-172007-04-17superseded{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/ParentheticalAuthorTeamAndYear + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/AuthorTeamAndYear} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeamParenthesis + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeam} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamOriginalAndYear + [= or] DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamParenthesisAndYear}
-BasionymThe basionym (botany) or basonym (bacteriology) of the scientificName.Example: "Pinus abies"2008-11-192009-04-24supersedednot in ABCD
-Basionym IDA unique identifier for the basionym (botany) or basonym (bacteriology) of the scientificName.2009-01-212009-04-24supersedednot in ABCD
-Basis of RecordAn abbreviation indicating whether the record represents an observation (O), living organism (L), specimen (S), germplasm/seed (G), etc.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/RecordBasis
-Basis of RecordA description indicating whether the record represents an observation, tissue sample, living organism, voucher specimen, germplasm/seed, genetic information, etc.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/RecordBasis
-Basis of RecordA descriptive term indicating whether the record represents an object or observation. Examples: PreservedSpecimen- A physical object representing one or more organisms, part of organism, or artifact of an organism. synonyms: voucher, collection, lot. FossilSpecimen- A physical object representing one or more fossil organisms, part of fossil organism, or artifact of a fossil organism. LivingSpecimen- An organism removed from its natural occurrence and now living in captivity or cultivation. HumanObservation- A report by a known observer that an organism was present at the place and time. MachineObservation- A report by a monitoring device that an organism was present at the place and time. StillImage- An photograph, drawing, painting. MovingImage- A sequence of still images taken at regular intervals and intended to be played back as a moving image; may include sound. SoundRecording- An audio recording. OtherSpecimen- Any type of specimen not covered by any of the categories above.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/RecordBasis
-Basis of RecordThe specific nature of the data record - a subtype of the dcterms:type. Recommended best practice is to use a controlled vocabulary such as the Darwin Core Type Vocabulary (http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm).Examples: "StillImage", "MovingImage", "Sound", "PreservedSpecimen", FossilSpecimen", LivingSpecimen", "HumanObservation", "MachineObservation"2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/RecordBasis
-Basis of RecordThe specific nature of the data record - a subtype of the dcterms:type. Recommended best practice is to use a controlled vocabulary.Examples: "StillImage", "MovingImage", "Sound", "PreservedSpecimen", FossilSpecimen", LivingSpecimen", "HumanObservation", "MachineObservation"2008-11-192009-09-11supersededDataSets/DataSet/Units/Unit/RecordBasis
-Basis of RecordThe specific nature of the data record - a subtype of the dcterms:type. Recommended best practice is to use a controlled vocabulary such as the Darwin Core Type Vocabulary (http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm).Examples: "PreservedSpecimen", "FossilSpecimen", "LivingSpecimen", "HumanObservation", "MachineObservation"2008-11-192009-12-07recommendedDataSets/DataSet/Units/Unit/RecordBasis
-BedThe full name of the lithostratigraphic bed from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-BedThe full name of the lithostratigraphic bed from which the cataloged item was collected.2009-04-242009-07-06recommendednot in ABCD
-BehaviorA description of the behavior shown by the subject at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.Examples: "roosting", "foraging", "running"2009-03-062009-04-24recommendednot in ABCD
-BinomialThe combination of genus and first (species) epithet of the scientificName.Example: "Ctenomys sociabilis"2008-11-192008-11-19deprecatedDataSets/DataSet/Units/Unit/Gathering/Synecology/AssociatedTaxa/TaxonIdentified/ScientificName/FullScientificNameString
-Bounding BoxThis access point provides a mechanism for performing searches using a bounding box. A Bounding Box element is not typically present in the database, but rather is derived from the Latitude and Longitude columns by the data provider2003-06-132003-06-13supersedednot covered by ABCD
-Bounding BoxThis access point provides a mechanism for performing searches using a bounding box. A Bounding Box element is not typically present in the database, but rather is derived from the DecimalLatitude and DecimalLongitude columns by the data provider.2003-06-172003-06-17supersedednot covered by ABCD
-Catalog NumberA unique alphanumeric value which identifies an individual record within the collection. It is recommended that this value provides a key by which the actual specimen can be identified. If the specimen has several items such as various types of preparation, this value should identify the individual component of the specimen2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/UnitID
-Catalog NumberThe alphanumeric value identifying a record within the collection. It is highly recommended that each record be uniquely identified within a collection by this value. It is also recommended that each record be uniquely identified in a global context by the combination of InstitutionCode, CollectionCode and CatalogNumber.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/UnitID
-Catalog NumberAn identifier (preferably unique) for the record within the data set or collection.Examples: "2008.1334", "145732a", "145732"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/UnitID
-Catalog Number NumericThe CatalogNumber as a numeric value, if applicable. Allows searching on numeric ranges of CatalogNumbers.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/UnitIDNumeric
-Catalog Number NumericThe CatalogNumber as a numeric value, if applicable. This element allows searching on numeric ranges of CatalogNumbers. Example: 145732.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/UnitIDNumeric
-Catalog Number NumericThe numeric value of the catalogNumber, used to facilitate numerical sorting and searching by ranges.2008-11-192008-11-19deprecatedDataSets/DataSet/Units/Unit/UnitIDNumeric
-Catalog Number TextAn alphanumeric value which identifies an individual cataloged item within the collection. It is recommended that this value provides a key by which the individual cataloged item can be identified.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/UnitID
-CitationIndicates how this dataset or record should be attributed if used.2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/IPRStatements/Citations/Citation/Text
-ClassThe class name of the organism2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
-ClassThe phylogenetic class to which the cataloged item belongs.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
-ClassThe name of the class in which the organism is classified.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
-ClassThe name of the class in which the scientificName is classified.Example: "Mammalia"2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
-ClassThe full scientific name of the class in which the taxon is classified.Examples: "Mammalia", "Hepaticopsida"2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
-Collection MethodThe name of, reference to, or brief description of the method or protocol under which the collecting event occurred. Examples: "UV light trap", "mist net", "bottom trawl".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/Method
-Collection CodeA unique alphanumeric value which identifies the collection within the institution2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/SourceID
-Collection CodeA unique alphanumeric value that identifies the collection within the institution in which the item is cataloged. This attribute must contain no spaces.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/SourceID
-Collection CodeThe code (or acronym) identifying the collection within the institution in which the organism record is cataloged.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/SourceID
-Collection CodeThe name (or acronym) identifying the collection or data set from which the record was derived.Examples: "Mammals", "Hildebrandt", "eBird"2008-11-192009-08-24supersededDataSets/DataSet/Units/Unit/SourceID
-Collection CodeThe name, acronym, coden, or initialism identifying the collection or data set from which the record was derived.Examples: "Mammals", "Hildebrandt", "eBird"2008-11-192009-08-24supersededDataSets/DataSet/Units/Unit/SourceID
-Collection CodeThe name, acronym, coden, or initialism identifying the collection or data set from which the record was derived.Examples: "Mammals", "Hildebrandt", "eBird"2008-11-192013-10-04recommendedDataSets/DataSet/Units/Unit/SourceID
-Collection IDAn identifier for the collection or dataset from which the record was derived. For physical specimens, the recommended best practice is to use the identifier in a collections registry such as the Biodiversity Collections Index (http://www.biodiversitycollectionsindex.org/).Example: "urn:lsid:biocol.org:col:34818"2008-11-192009-08-24supersededDataSets/DataSet/Units/Unit/SourceID
-Collection IDAn identifier for the collection or dataset from which the record was derived. For physical specimens, the recommended best practice is to use the identifier in a collections registry such as the Biodiversity Collections Index (http://www.biodiversitycollectionsindex.org/).Example: "urn:lsid:biocol.org:col:34818"2008-11-192013-10-04recommendedDataSets/DataSet/Units/Unit/SourceID
-CollectorThe name(s) of the collector(s) responsible for collection the specimen or taking the observation2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/GatheringAgents/GatheringAgentsText
-CollectorThe name(s) of the collector(s) of the original data for the cataloged item.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/GatheringAgents/GatheringAgentsText
-CollectorThe name(s) (concatenated and separated) of collectors or observers. "LIKE" or "contains" substring query operations are meant to be used with this element to find matching collector names. The primary collector or observer, especially one whose CollectorNumber is also provided, should be listed first. Example: "Oliver P. Pearson, Anita K. Pearson" where the value in CollectorNumber "OPP 7101" corresponds to the number for the specimen in the field catalog (collector number) of Oliver P. Pearson.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/GatheringAgents/GatheringAgentsText
-Collector NumberAn identifying "number" (really a string) applied to specimens (in some disciplines) at the time of collection. Establishes a links different parts/preparations of a single specimen and between field notes and the specimen.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/CollectorsFieldNumber
-Collector NumberAn identifying string applied to the cataloged item at the time of collection. Serves as a link between field notes and the cataloged items.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/CollectorsFieldNumber
-Collector NumberAn identifying string applied to the object or observation at the time of collection. Serves as a link between field notes and the object or observation.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/GatheringAgents/GatheringAgentsText
-ContinentThe full, unabbreviated name of the continent on which the organism was collected or observed.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Continent
-ContinentThe name of the continent in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.Examples: "Africa", "Antarctica", "Asia", "Europe", "North America", "Oceania", "South America"2008-11-192013-10-04recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Continent
-Continent OceanThe continent or ocean from which a specimen was collected.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Continent
-Continent OceanThe full, unabbreviated name of the continent or ocean from which the cataloged item was collected.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Continent
-Coordinate PrecisionAn estimate of how tightly the collecting locality was specified; expressed as a distance, in meters, that corresponds to a radius around the latitude-longitude coordinates. Use NULL where precision is unknown, cannot be estimated, or is not applicable.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/ISOAccuracy or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/AccuracyStatement
-Coordinate PrecisionA decimal representation of the precision of the coordinates given in the decimalLatitude and decimalLongitude.Examples: "0.00001" (normal GPS limit for decimal degrees), "0.000278" (nearest second), "0.01667" (nearest minute), "1.0" (nearest degree)2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/ISOAccuracy or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/AccuracyStatement
-Coordinate Uncertainty In MetersThe upper limit of the distance (in meters) from the given latitude and longitude describing a circle within which the whole of the described locality must lie. Use NULL where the uncertainty is unknown, cannot be estimated, or is not applicable.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinateErrorDistanceInMeters
-Coordinate Uncertainty In MetersThe upper limit of the distance (in meters) from the given DecimalLatitude and DecimalLongitude describing a circle within which the whole of the described locality lies. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Describes the point-radius representation of the location, along with DecimalLatitude, DecimalLongitude, and GeodeticDatum. Zero is not a valid value for this element.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinateErrorDistanceInMeters
-Coordinate Uncertainty In MetersThe horizontal distance (in meters) from the given decimalLatitude and decimalLongitude describing the smallest circle containing the whole of the Location. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Zero is not a valid value for this term.Examples: "30" (reasonable lower limit of a GPS reading under good conditions if the actual precision was not recorded at the time), "71" (uncertainty for a UTM coordinate having 100 meter precision and a known spatial reference system).2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinateErrorDistanceInMeters
-CountryThe country or major political unit from which the specimen was collected. ISO 3166-1 (http://www.din.de/gremien/nas/nabd/iso3166ma/codlstp1/db_en.html) values should be used. Full country names are currently in use. A future recommendation is to use ISO3166-1 two letter codes or the full name when searching2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/Country/Name
-CountryThe full, unabbreviated name of the country or major political unit from which the cataloged item was collected.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/Country/Name
-CountryThe full, unabbreviated name of the country or major political unit in which the organism was collected or observed.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/Country/Name
-CountryThe name of the country or major administrative unit in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.Examples: "Denmark", "Colombia", "España"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Country/Name
-Country CodeThe standard code for the country in which the Location occurs. Recommended best practice is to use ISO 3166-1-alpha-2 country codes.Examples: "AR" for Argentina, "SV" for El Salvador2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Country/ISO3166Code
-CountyThe county (or shire, or next political region smaller than State / Province) from which the specimen was collected2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= County
-CountyThe full, unabbreviated name of the county, shire, or municipality (i.e., the next smaller political region than StateProvince) from which the cataloged item was collected.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= County
-CountyThe full, unabbreviated name of the county, shire, or municipality (i.e., the next smaller political region than StateProvince) in which the organism was collected or observed.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= County
-CountyThe full, unabbreviated name of the next smaller administrative region than stateProvince (county, shire, department, etc.) in which the Location occurs.Examples: "Missoula", "Los Lagos", "Mataró"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= County
-Data GeneralizationsActions taken to make the shared data less specific or complete than in its original form. Suggests that alternative data of higher quality may be available on request.Example: "Coordinates generalized from original GPS coordinates to the nearest half degree grid cell"2008-11-192009-04-24recommendednot in ABCD
-DatasetThe category of information pertaining to a logical set of records.2008-11-192008-11-19deprecatedDataSets/DataSet
-Dataset IDAn identifier for the data set. May be a global unique identifier or an identifier specific to a collection or institution.2008-11-192009-04-24supersededDataSets/DataSet/DataSetGUID
-Dataset IDAn identifier for the set of data. May be a global unique identifier or an identifier specific to a collection or institution.2008-11-192009-09-11recommendedDataSets/DataSet/DataSetGUID
-Dataset NameThe name identifying the data set from which the record was derived.Examples: "Grinnell Resurvey Mammals", "Lacey Ctenomys Recaptures"2009-09-112009-09-11recommendedDataSets/DataSet/Units/Unit/SourceID
-Date IdentifiedThe date-time in the Common Era calendar in which the object or observation was identified as being a member of the taxon given in the ScientificName.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
-Date IdentifiedThe date on which the subject was identified as representing the taxon given in the scientificName. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "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.2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
-Date IdentifiedThe date on which the subject was identified as representing the Taxon. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "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.2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
-Date Last ModifiedISO 8601 compliant stamp indicating the date and time in UTC(GMT) when the record was last modified. Example: the instant "November 5, 1994, 8:15:30 am, US Eastern Standard Time" would be represented as "1994-11-05T13:15:30Z" (see W3C Note on Date and Time Formats - http://www.w3.org/TR/NOTE-datetime). (What to do when this date-time is unknown? Use Date-Time first "published"?)2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/DateLastEdited
-Date Last ModifiedISO 8601 date and time in UTC(GMT) when the record was last modified. Example: "November 5, 1994, 8:15:30 am, US Eastern Standard Time" would be "1994-11-05T13:15:30Z" (see http://www.w3.org/TR/NOTE-datetime).2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/DateLastEdited
-Date Last ModifiedThe last date-time of publication when any of the data for the record were modified from the previous publication of that record. When publishing a record for the first time, use the publication date-time. Returns values as ISO 8601 date and time. (cf. http://www.w3.org/TR/xmlschema-2/#isoformats and http://www.iso.org/iso/en/prods-services/popstds/dateandtime.html Example: November 5, 1994, 8:15:30 am, US Eastern Standard Time” would be “1994-11-05T13:15:30Z”2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/DateLastEdited
-DayThe integer day of the month on which the Event occurred.Examples: "9", "28"2008-11-192009-04-24recommendedaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Day CollectedThe day of the month the specimen was collected from the field. Possible value ranges from 01..31 inclusive2003-06-132003-06-13supersededaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Day CollectedThe two digit day of the month in the Common Era calendar during which the cataloged item was collected from the field.2003-06-172003-06-17supersededaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Day IdentifiedThe day portion of the date when the Collection Item was identified; as two digits [01..31].2003-06-132003-06-13supersededaccessible from DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
-Day IdentifiedThe two digit day of the month in the Common Era calendar during which the cataloged item was identified.2003-06-172003-06-17supersededaccessible from DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
-Day of YearThe ordinal day of the year on which the object or observation was collected (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366). If the EarliestDateCollected and LatestDateCollected do not occur on the same day, do not populate DayOfYear.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberBegin
-Decimal LatitudeThe latitude of the location from which the cataloged item was collected, expressed in decimal degrees.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal
-Decimal LatitudeThe latitude of the geographic center of a location where an event occurred (organism collected, observation made), expressed in decimal degrees. Positive values are North of the Equator, negative values are South of the Equator. Describes the point-radius representation of the location, along with DecimalLongitude, GeodeticDatum, and CoordinateUncertaintyInMeters. Example: -41.09834232007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal
-Decimal LatitudeThe geographic latitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are north of the Equator, negative values are south of it. Legal values lie between -90 and 90, inclusive.Example: "-41.0983423"2008-11-192009-07-06recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal
-Decimal LongitudeThe longitude of the location from which the cataloged item was collected, expressed in decimal degrees.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal
-Decimal LongitudeThe longitude of the geographic center of a location where an event occurred (organism collected, observation made), expressed in decimal degrees. Positive values are East of the Greenwich Meridian, negative values are West of the Greenwich Meridian. Describes the point-radius representation of the location, along with DecimalLatitude, GeodeticDatum, and CoordinateUncertaintyInMeters. Example: -71.09432352007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal
-Decimal LongitudeThe geographic longitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are east of the Greenwich Meridian, negative values are west of it. Legal values lie between -180 and 180, inclusive.Example: "-121.1761111"2008-11-192009-07-06recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal
-Depth RangeFor data sets that have the depth range expressed in one field (e.g. "150-200 m") it can be entered here as free text. Separate, numeric Minimum and Maximum Depth fields are the preferred format; the Depth Range option is included for legacy data sets.2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactText
-DispositionThe current disposition of the cataloged item. Examples: "in collection", "missing", "voucher elsewhere", "duplicates elsewhere".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/SpecimenUnit/Disposition
-DispositionThe current state of a specimen with respect to the collection identified in collectionCode or collectionID. Recommended best practice is to use a controlled vocabulary.Examples: "in collection", "missing", "voucher elsewhere", "duplicates elsewhere"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/SpecimenUnit/Disposition
-Darwin Core TypeThe set of classes specified by the Darwin Core Type Vocabulary, used to categorize the nature or genre of the resource.2008-11-192008-11-19recommendednot in ABCD
-Dynamic PropertiesA list (concatenated and separated) of additional measurements, facts, characteristics, or assertions about the record. Meant to provide a mechanism for structured content such as key-value pairs.Examples: "tragusLengthInMeters=0.014; weightInGrams=120", "heightInMeters=1.5", "natureOfID=expert identification; identificationEvidence=cytochrome B sequence", "relativeHumidity=28; airTemperatureInC=22; sampleSizeInKilograms=10", "aspectHeading=277; slopeInDegrees=6", "iucnStatus=vulnerable; taxonDistribution=Neuquen, Argentina"2008-11-192009-04-24recommendednot in ABCD
-Earliest Age Or Lowest StageThe full name of the earliest possible geochronologic age or lowest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-Earliest Age Or Lowest StageThe full name of the earliest possible geochronologic age or lowest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Atlantic", "Boreal", "Skullrockian"2009-04-242009-07-06recommendednot in ABCD
-Earliest Date CollectedThe earliest date-time (Common Era calendar) in a date-time period during which an organism or group of organisms was collected or observed. If the event is recorded as occurring at a single date-time, populate both EarliestDateCollected and LatestDateCollected with the same value.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Earliest Date CollectedThe earliest date-time in a period during which a event occurred. If the event is recorded as occurring at a single date-time, populate both EarliestDateCollected and LatestDateCollected with the same value. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].2008-11-192008-11-19deprecatedDataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Earliest Eon Or Lowest EonothemThe full name of the earliest possible geochronologic eon or lowest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-Earliest Eon Or Lowest EonothemThe full name of the earliest possible geochronologic eon or lowest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Phanerozoic", "Proterozoic"2009-04-242009-07-06recommendednot in ABCD
-Earliest Epoch Or Lowest SeriesThe full name of the earliest possible geochronologic epoch or lowest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-Earliest Epoch Or Lowest SeriesThe full name of the earliest possible geochronologic epoch or lowest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Holocene", "Pleistocene", "Ibexian Series"2009-04-242009-07-06recommendednot in ABCD
-Earliest Era Or Lowest ErathemThe full name of the earliest possible geochronologic era or lowest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-Earliest Era Or Lowest ErathemThe full name of the earliest possible geochronologic era or lowest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Cenozoic", "Mesozoic"2009-04-242009-07-06recommendednot in ABCD
-Earliest Period Or Lowest SystemThe full name of the earliest possible geochronologic period or lowest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-Earliest Period Or Lowest SystemThe full name of the earliest possible geochronologic period or lowest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Neogene", "Tertiary", "Quaternary"2009-04-242009-07-06recommendednot in ABCD
-End Day CollectedFor samples/observations/record events that were taken over time this gives the end day of the collecting event. Possible value ranges from 01..31 inclusive.2005-07-102005-07-10supersededaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
-End Day Of YearThe latest ordinal day of the year on which the Event occurred (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366).Examples: "1" (=1 Jan), "366" (=31 Dec), "365" (=30 Dec in a leap year, 31 Dec in a non-leap year)2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberEnd
-End Julian DayFor samples/observations/record events that were taken over time this gives the end ordinal day of the year for the collecting event; i.e., the number of days since January 1 of the same year. (January 1 is Julian Day 1.). Should be an integer from one to 365, i.e. of the form (([0-3][0-9][0-9)|([0-9][0-9)|([1-9])).2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberEnd
-End LatitudeFor samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the starting latitude location from which the specimen was collected or in which the sample/observation/record event occurred. This value should be expressed in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/).2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/CoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal with attribute "begin" set to true
-End LongitudeFor samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the starting longitude location from which the specimen was collected. Express in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/).2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/CoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal with attribute "begin" set to true
-End Month CollectedFor samples/observations/record events that were taken over time this gives the end month of the collecting event. Possible values range from 01...12 inclusive.2005-07-102005-07-10supersededaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
-End Time of DayThe time of day when the sampling event ended, expressed as decimal hours from midnight local time. Examples: 0 = midnight, 12.0 = mid-day, 13.5 = 13:302005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/DateTime/TimeOfDayEnd
-End Time of DayThe time of day when the event ended, expressed as decimal hours from midnight, local time.Examples: "12.0" (= noon), "13.5" (= 1:30pm)2008-11-192009-04-24deprecatedDataSets/DataSet/Units/Unit/Gathering/DateTime/TimeOfDayEnd
-End Year CollectedFor samples/observations/record events that were taken over time this gives the end year of the collecting event. The full year should be expressed (e.g. 1972 must be expressed as "1972" not "72"). Must always be a four digit integer.2005-07-102005-07-10supersededaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
-Establishment MeansThe process by which the biological individual(s) represented in the Occurrence became established at the location. Recommended best practice is to use a controlled vocabulary.Examples: "native", "introduced", "naturalised", "invasive", "managed"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/EstablishmentMeans
-EventThe category of information pertaining to an event (an action that occurs at a place and during a period of time).2008-11-192009-04-29recommendedDataSets/DataSet/Units/Unit/Gathering
-Event AttributeContainer class for information about attributes related to a given sampling event.2008-11-192008-11-19supersededDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts
-Event Attribute AccuracyThe description of the error associated with the EventAttributeValue.Example: "0.01", "normal distribution with variation of 2 m"2009-01-182009-01-18supersededDataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
-Event Attribute Determined ByThe agent responsible for having determined the value of the measurement or characteristic of the sampling event.Example: "Robert Hijmans"2009-01-232009-01-23supersededDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
-Event Attribute Determined DateThe date on which the the measurement or characteristic of the sampling event was made.Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].2009-01-232009-01-23supersededDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
-Event Attribute IDAn identifier for the event attribute. May be a global unique identifier or an identifier specific to the data set.2008-11-192008-11-19supersedednot in ABCD
-Event Attribute RemarksComments or notes accompanying the measurement or characteristic of the sampling event.Example: "temperature taken at 15:00"2008-11-192008-11-19supersedednot in ABCD
-Event AttributesA list (concatenated and separated) of additional measurements or characteristics of the Event.Example: "Relative humidity: 28 %; Temperature: 22 C; Sample size: 10 kg"2008-11-192009-04-24deprecatedDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts
-Event Attribute TypeThe nature of the measurement or characteristic of the sampling event. Recommended best practice is to use a controlled vocabulary.Example: "Temperature"2008-11-192008-11-19supersededDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
-Event Attribute UnitThe units for the value of the measurement or characteristic of the sampling event. Recommended best practice is to use International System of Units (SI) units.Example: "C"2008-11-192008-11-19supersededDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
-Event AttributeThe value of the measurement or characteristic of the sampling event.Example: "22"2008-11-192008-11-19supersededDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
-Event DateThe date-time or interval during which an Event occurred. For occurrences, this is the date-time when the event was recorded. Not suitable for a time in a geological context. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "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.2009-04-242009-07-01recommendedDataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Event IDAn identifier for the set of information associated with an Event (something that occurs at a place and time). May be a global unique identifier or an identifier specific to the data set.2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Code
-Event MeasurementThe category of information pertaining to measurements associated with an event.2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts
-Event Measurement AccuracyThe description of the error associated with the EventAttributeValue.Example: "0.01", "normal distribution with variation of 2 m"2009-01-182009-04-24deprecatedDataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
-Event Measurement Determined ByThe agent responsible for having determined the value of the measurement or characteristic of the event.Example: "Robert Hijmans"2009-01-232009-04-24deprecatedDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
-Event Measurement Determined DateThe date on which the the measurement or characteristic of the event was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "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.2009-01-232009-04-24deprecatedDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
-Event Measurement IDAn identifier for the event attribute. May be a global unique identifier or an identifier specific to the data set.2008-11-192009-04-24deprecatednot in ABCD
-Event Measurement RemarksComments or notes accompanying the measurement or characteristic of the event.Example: "temperature taken at 15:00"2008-11-192009-04-24deprecatednot in ABCD
-Event Measurement TypeThe nature of the measurement or characteristic of the event. Recommended best practice is to use a controlled vocabulary.Example: "temperature"2008-11-192009-04-24deprecatedDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
-Event Measurement UnitThe units for the value of the measurement or characteristic of the event. Recommended best practice is to use International System of Units (SI) units.Example: "C"2008-11-192009-04-24deprecatedDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
-Event Measurement ValueThe value of the measurement or characteristic of the event.Example: "22"2008-11-192009-04-24deprecatedDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
-Event RemarksComments or notes about the Event.Example: "after the recent rains the river is nearly at flood stage"2009-01-182009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Notes
-Event TimeThe time or interval during which an Event occurred. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "14:07-0600" is 2:07pm in the time zone six hours earlier than UTC, "08:40:21Z" is 8:40:21am UTC, "13:00:00Z/15:30:00Z" is the interval between 1pm UTC and 3:30pm UTC.2009-04-242009-04-24recommendedaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin and DataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
-FamilyThe family name of the organism2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
-FamilyThe phylogenetic family to which the cataloged item belongs.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
-FamilyThe name of the family in which the organism is classified.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
-FamilyThe name of the family in which the scientificName is classified.Example: "Ctenomyidae"2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
-FamilyThe full scientific name of the family in which the taxon is classified.Examples: "Felidae", "Monocleaceae"2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
-Field NotesA reference to, or flag marking the existence of notes taken in the field for the cataloged item.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/FieldNotes
-Field NotesOne of a) a flag indicating the existence of, b) a reference to (such as a URL or literature citation), or c) the actual free text content of notes taken in the field about the specimen or observation.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/FieldNotes
-Field NotesOne of a) an indicator of the existence of, b) a reference to (publication, URI), or c) the text of notes taken in the field about the Event.Example: "notes available in Grinnell-Miller Library"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/FieldNotes
-Field NumberA "number" (really a string) created at collection time to identify all material that resulted from a collecting event.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/Code
-Field NumberAn identifying string applied to a set of material that resulted from a single collecting event.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/Code
-Field NumberAn identifying string applied to a set of objects or observations resulting from a single collecting event.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/Code
-Field NumberAn identifier given to the event in the field. Often serves as a link between field notes and the Event.Example: "RV Sol 87-03-08"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Code
-Footprint Spatial FitA measure of how well the geometry expressed in the footprint match the original spatial representation, as a ratio of the area of the footprint given to the area of the original spatial representation. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given georeference does not completely contain the original representation. The FootprintSpatialFit is undefined if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the FootprintSpatialFit is 1. Detailed explanations with graphical examples can be found in the Guide to Best Practices for Georeferencing (Chapman and Wieczorek, eds. 2006).2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/FootprintSpatialFit (ABCD v2.06b)
-Footprint Spatial FitThe ratio of the area of the footprint (footprintWKT) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given footprint does not completely contain the original representation. The footprintSpatialFit is undefined (and should be left blank) if the original representation is a point and the given georeference is not that same point. If both the original and the given georeference are the same point, the footprintSpatialFit is 1.Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006 (http://www.gbif.org/prog/digit/Georeferencing).2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/FootprintSpatialFit (ABCD v2.06b)
-Footprint SRSA Well-Known Text (WKT) representation of the Spatial Reference System (SRS) for the footprintWKT of the Location. Do not use this term to describe the SRS of the decimalLatitude and decimalLongitude, even if it is the same as for the footprintWKT - use the geodeticDatum instead.Example: The WKT for the standard WGS84 SRS (EPSG:4326) is "GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137,298.257223563]],PRIMEM["Greenwich",0],UNIT["Degree",0.0174532925199433]]" without the enclosing quotes.2009-07-062009-07-06recommendednot in ABCD
-Footprint WKTA Well-Known Text (WKT; see http://en.wikipedia.org/wiki/Well-known_text) representation of the the shape (footprint, geometry) that defines the location of the occurrence. The same place may have both a point-radius representation (see DecimalLatitude) and a footprint representation, and they may differ from each other for the same occurrence. Example: the one-degree bounding box with opposite corners at (longitude=10, latitude=20) and (longitude=11, latitude=21) would be expressed in well-known text as POLYGON ((10 20, 11 20, 11 21, 10 21, 10 20))2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/FootprintWKT (ABCD v2.06b)
-Footprint WKTA Well-Known Text (WKT) representation of the shape (footprint, geometry) that defines the Location. A Location may have both a point-radius representation (see decimalLatitude) and a footprint representation, and they may differ from each other.Example: the one-degree bounding box with opposite corners at (longitude=10, latitude=20) and (longitude=11, latitude=21) would be expressed in well-known text as POLYGON ((10 20, 11 20, 11 21, 10 21, 10 20))2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/FootprintWKT (ABCD v2.06b)
-FormationThe full name of the lithostratigraphic formation from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-FormationThe full name of the lithostratigraphic formation from which the cataloged item was collected.Examples: "Notch Peak Fromation", "House Limestone", "Fillmore Formation"2009-04-242009-07-06recommendednot in ABCD
-Fossil SpecimenA resource describing a fossilized specimen.2008-11-192008-11-19supersededRecordBasisEnum/FossileSpecimen
-Fossil SpecimenA resource describing a fossilized specimen.2008-11-192011-10-16recommendedRecordBasisEnum/FossileSpecimen
-Gen Bank NumGenBank Accession number.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Sequences/Sequence/ID-in-Database + constant
-Gen Bank NumberGenBank Accession number(s) associated with the biological individual(s) referred to by the cataloged object.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Sequences/Sequence/ID-in-Database + constant
-GeneralizationsActions taken to make the data as shared less specific or complete than in its original form. Suggests that alternative data of highly quality may be available on request.Examples: "Coordinates generalized from original GPS coordinates to the nearest half degree grid cell", "locality information given only to nearest county".2008-11-192008-11-19supersedednot in ABCD
-GenusThe genus name of the organism2003-06-132003-06-13superseded{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
-GenusThe phylogenetic genus to which the cataloged item belongs.2003-06-172003-06-17superseded{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
-GenusThe name of the genus in which the organism is classified.2007-04-172007-04-17superseded{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
-GenusThe name of the genus in which the scientificName is classified.Example: "Quercus"2008-11-192009-04-24superseded{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
-GenusThe full scientific name of the genus in which the taxon is classified.Examples: "Puma", "Monoclea"2008-11-192009-08-24recommended{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
-Geodetic DatumThe geodetic datum to which the latitude and longitude refer. If not known, use "not recorded". This concept should be vocabulary-controlled. Example: "WGS84"2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/SpatialDatum
-Geodetic DatumThe ellipsoid, geodetic datum, or spatial reference system (SRS) upon which the geographic coordinates given in decimalLatitude and decimalLongitude as based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".Examples: "EPSG:4326", "WGS84", "NAD27", "Campo Inchauspe", "European 1950", "Clarke 1866"2008-11-192009-07-06recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/SpatialDatum
-Geological ContextThe category of information pertaining to a location within a geological context, such as stratigraphy.2009-07-062009-07-06recommendedDataSets/DataSet/Units/Unit/Gathering/Stratigraphy
-Geological Context IDAn identifier for the set of information associated with a GeologicalContext (the location within a geological context, such as stratigraphy). May be a global unique identifier or an identifier specific to the data set.2009-07-062009-07-06recommendednot in ABCD
-Georeferenced ByA list (concatenated and separated) of names of people, groups, or organizations who determined the georeference (spatial representation) for the Location.Examples: "Kristina Yamamoto (MVZ); Janet Fang (MVZ)", "Brad Millen (ROM)"2009-01-212009-04-24recommendednot in ABCD
-Georeferenced DateThe date on which the Location was georeferenced. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "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.2011-10-162011-10-16recommendednot in ABCD
-Georeference ProtocolA reference to the methods used for determining the coordinates and uncertainties. Example: "http://manisnet.org/GeorefGuide.html".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinateMethod
-Georeference ProtocolA description or reference to the methods used to determine the spatial footprint, coordinates, and uncertainties.Examples: "Guide to Best Practices for Georeferencing" (Chapman and Wieczorek, eds. 2006), Global Biodiversity Information Facility.", "MaNIS/HerpNet/ORNIS Georeferencing Guidelines", "Georeferencing Quick Reference Guide"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinateMethod
-Georeference RemarksComments about the spatial description determination, explaining assumptions made in addition or opposition to the those formalized in the method referred to in GeoreferenceProtocol.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceRemarks
-Georeference RemarksNotes or comments about the spatial description determination, explaining assumptions made in addition or opposition to the those formalized in the method referred to in georeferenceProtocol.Example: "assumed distance by road (Hwy. 101)"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceRemarks
-Georeference SourcesA list of maps, gazetteers or other resources used to georeference the locality. The content of this concept is meant to be specific enough to allow anyone in the future to use the same resource to georeference the same locality. Examples: "USGS 1:24000 Florence Montana Quad", "Terrametrics 2008 on Google Earth"2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceSources
-Georeference SourcesA list (concatenated and separated) of maps, gazetteers, or other resources used to georeference the Location, described specifically enough to allow anyone in the future to use the same resources.Examples: "USGS 1:24000 Florence Montana Quad; Terrametrics 2008 on Google Earth"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceSources
-Georeference Verification StatusA categorical description of the extent to which the georeference has been verified to represent the location where the specimen or observation was collected. This element should be vocabulary-controlled. Examples: "requires verification", "verified by collector", "verified by curator".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceVerificationStatus
-Georeference Verification StatusA categorical description of the extent to which the georeference has been verified to represent the best possible spatial description. Recommended best practice is to use a controlled vocabulary.Examples: "requires verification", "verified by collector", "verified by curator".2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceVerificationStatus
-Georef MethodA reference to the methods used for determining the coordinates and uncertainties.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinateMethod
-Global Unique IdentifierA Uniform Resource Name (URN) as a unique identifier for the specimen or observation record. In the absence of a persistent global unique identifier, construct one in the form: “[InstitutionCode]:[CollectionCode]: [CatalogNumber]” Examples: 1) urn:lsid:nhm.ku.edu:Herps:32 2) “FMNH:Mammal:145732”2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/UnitGUID
-GML FeatureGeographic Markup Language(GML) description of the feature for representing complex shapes such as lines and polygons, per Open GIS Consortium (OGC) standards - http://www.opengis.net/gml/01-029/GML2.html.2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/GML
-GroupThe full name of the lithostratigraphic group from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-GroupThe full name of the lithostratigraphic group from which the cataloged item was collected.2009-04-242009-07-06recommendednot in ABCD
-HabitatA category or description of the habitat in which the Event occurred.Examples: "oak savanna", "pre-cordilleran steppe"2008-11-192009-05-17recommendedDataSets/DataSet/Units/Unit/Gathering/Biotope/Text
-Higher ClassificationA list (concatenated and separated) of taxa names terminating at the rank immediately superior to the taxon referenced in the taxon record. Recommended best practice is to order the list starting with the highest rank and separating the names for each rank with a semi-colon (";").Example: "Animalia;Chordata;Vertebrata;Mammalia;Theria;Eutheria;Rodentia;Hystricognatha;Hystricognathi;Ctenomyidae;Ctenomyini;Ctenomys"2008-11-192009-08-24recommendednot in ABCD
-Higher GeographyThe combination of all geographic elements less specific than locality. "Like" query operations on this element will search for a substring in any of the higher geography attributes.2003-06-172003-06-17superseded{DataSets/DataSet/Units/Unit/Gathering/LocalityText or DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName}
-Higher GeographyThe names (concatenated and separated) of geographic elements less specific than the information in the Locality element. "LIKE" or "contains" substring query operations are meant to be used with this element to find matching geographic names. This can be useful if it is unclear in which element a name might be found, and in cases where there is no other appropriate geographic element. Example: "South America, Argentina, Patagonia, Parque Nacional Nahuel Huapi, Neuquén, Los Lagos" with accompanying values "South America" in Continent, "Argentina" in Country, "Neuquén" in StateProvince, and Los Lagos in County.2007-04-172007-04-17superseded{DataSets/DataSet/Units/Unit/Gathering/LocalityText or DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName}
-Higher GeographyA list (concatenated and separated) of geographic names less specific than the information captured in the locality term.Example: "South America; Argentina; Patagonia; Parque Nacional Nahuel Huapi; Neuquén; Los Lagos" with accompanying values "South America" in Continent, "Argentina" in Country, "Neuquén" in StateProvince, and Los Lagos in County.2008-11-192009-04-24recommended{DataSets/DataSet/Units/Unit/Gathering/LocalityText or DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName}
-Higher Geography IDAn identifier for the geographic region within which the Location occurred. Recommended best practice is to use an persistent identifier from a controlled vocabulary such as the Getty Thesaurus of Geographic Names.Example: "TGN: 1002002" for Prov. Tierra del Fuego, Argentina2009-01-212009-04-24recommendednot in ABCD
-Higher TaxonThe combination of names of taxonomic ranks less specific than Genus. "Like" query operations on this element will search for a substring in any of the higher taxon attributes.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
-Higher TaxonThe names of taxonomic ranks less specific than SpecificEpithet concatenated and separated. "LIKE" or "contains" substring query operations are meant to be used with this element to find matching higher taxon names. This element may contain the list of scientific names of all of the supra-specific taxa in the classification used to identify (determine) the specimen or observation. Example: "Animalia, Chordata, Vertebrata, Mammalia, Theria, Eutheria, Rodentia, Hystricognatha, Hystricognathi, Ctenomyidae, Ctenomyini, Ctenomys".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
-Higher TaxonA list (concatenated and separated) of the names for the taxonomic ranks less specific than the ScientificName.Example: "Animalia, Chordata, Vertebrata, Mammalia, Theria, Eutheria, Rodentia, Hystricognatha, Hystricognathi, Ctenomyidae, Ctenomyini, Ctenomys".2008-11-192009-01-21supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
-Higher Taxon Concept IDA unique identifier for the taxon concept less specific than that given in the taxonConceptID.2009-04-242009-04-24deprecatednot in ABCD
-Higher Taxon IDA global unique identifier for the parent to the taxon.2009-01-212009-01-21supersedednot in ABCD
-Higher Taxon NameA list (concatenated and separated) of the names for the taxonomic ranks less specific than that given in the scientificName.Example: "Animalia; Chordata; Vertebrata; Mammalia; Theria; Eutheria; Rodentia; Hystricognatha; Hystricognathi; Ctenomyidae; Ctenomyini; Ctenomys"2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
-Higher Taxon Name IDA unique identifier for the name of the next higher rank than the scientificName in a taxonomic classification. See higherTaxonName.2009-01-212009-04-24supersedednot in ABCD
-Highest Biostratigraphic ZoneThe full name of the highest possible geological biostratigraphic zone of the stratigraphic horizon from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-Highest Biostratigraphic ZoneThe full name of the highest possible geological biostratigraphic zone of the stratigraphic horizon from which the cataloged item was collected.2009-04-242009-07-06recommendednot in ABCD
-Horizontal DatumThe horizontal geodetic datum to which the DecimalLatitude and DecimalLongitude refer.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/SpatialDatum
-Human ObservationA resource describing an observation made by one or more people.2008-11-192008-11-19supersededRecordBasisEnum/HumanObservation
-Human ObservationA resource describing an observation made by one or more people.2008-11-192008-11-19recommendedRecordBasisEnum/HumanObservation
-IdentificationThe category of information pertaining to taxonomic determinations (the assignment of a scientific name).2008-11-192008-11-19recommendedDataSets/DataSet/Units/Unit/Identifications/Identification
-Identification AttributesA list (concatenated and separated) of additional measurements, facts, characteristics, or assertions about the Identification.Example: "natureOfID=expert identification; identificationEvidence=cytochrome B sequence"2009-04-242009-04-24deprecatednot in ABCD
-Identification IDAn identifier for the Identification (the body of information associated with the assignment of a scientific name). May be a global unique identifier or an identifier specific to the data set.2008-11-192009-04-24recommendednot in ABCD
-Identification ModifierAdditional information documenting the taxonomic determination of the cataloged item (e.g., "cf.", "aff.", "subspecies in question", etc.).2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/IdentificationQualifier
-Identification QualifierA brief phrase or a standard term ("cf.", "aff.") to qualify the identification of the organism when doubts have arisen as to its taxonomic identity (determination). Examples: 1) For the determination "Quercus aff. agrifolia var. oxyadenia", IdentificationQualifier would be "aff. agrifolia var. oxyadenia" with accompanying values "Quercus" in Genus, "agrifolia" in SpecificEpithet, "oxyadenia" in InfraspecificEpithet, and "var." in InfraspecificRank. 2) For the determination "Quercus agrifolia cf. var. oxyadenia", IdentificationQualifier would be "cf. var. oxyadenia " with accompanying values "Quercus" in Genus, "agrifolia" in SpecificEpithet, "oxyadenia" in InfraspecificEpithet, and "var." in InfraspecificRank.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/IdentificationQualifier
-Identification QualifierA brief phrase or a standard term ("cf.", "aff.") to express the determiner's doubts about the Identification.Examples: 1) For the determination "Quercus aff. agrifolia var. oxyadenia", identificationQualifier would be "aff. agrifolia var. oxyadenia" with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank. 2) For the determination "Quercus agrifolia cf. var. oxyadenia", identificationQualifier would be "cf. var. oxyadenia " with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank.2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/IdentificationQualifier
-Identification ReferencesA list (concatenated and separated) of references (publication, global unique identifier, URI) used in the Identification.Example: "Aves del Noroeste Patagonico. Christie et al. 2004."2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/References
-Identification RemarksComments or notes about the Identification.Example: "Distinguished between Anthus correndera and Anthus hellmayri based on the comparative lengths of the uñas."2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/Notes
-Identification Verification StatusA categorical indicator of the extent to which the taxonomic identification has been verified to be correct. Recommended best practice is to use a controlled vocabulary such as that used in HISPID/ABCD.Examples: "0", "4"2011-10-162011-10-16recommendednot in ABCD
-Identified ByThe name(s) of the person(s) who applied the currently accepted Scientific Name to the Cataloged Item.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Identifications/Identification/Identifiers/IdentifiersText
-Identified ByThe name(s) of the person(s) who applied the currently accepted ScientificName to the cataloged item.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/Identifiers/IdentifiersText
-Identified ByThe name(s) of the person(s) who applied the ScientificName to the object or observation. Example: James L. Patton.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/Identifiers/IdentifiersText
-Identified ByA list (concatenated and separated) of names of people, groups, or organizations who assigned the scientificName.Example: "James L. Patton", "Theodore Pappenfuss; Robert Macey"2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/Identifications/Identification/Identifiers/IdentifiersText
-Identified ByA list (concatenated and separated) of names of people, groups, or organizations who assigned the Taxon to the subject.Examples: "James L. Patton", "Theodore Pappenfuss; Robert Macey"2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/Identifiers/IdentifiersText
-Image URLA Universal Resource Locator reference to digital images associated with the specimen or observation.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/MultimediaObjects
-Individual CountThe number of individuals present in the lot or container. Not an estimate of abundance or density at the collecting locality.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue
-Individual CountThe number of individuals present in the lot or container referred to by the catalog number. Not an estimate of abundance or density at the collecting locality.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue
-Individual CountThe number of individuals present in the lot or container. Not to be used for observations.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue
-Individual CountThe number of individuals represented present at the time of the Occurrence.Examples: "1", "25"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue
-Individual IDAn identifier for an individual or named group of individual organisms represented in the Occurrence. Meant to accommodate resampling of the same individual or group for monitoring purposes. May be a global unique identifier or an identifier specific to a data set.Examples: "U.amer. 44", "Smedley", "Orca J 23"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/NameAtomised/Zoological/NamedIndividual or DataSets/DataSet/Units/Unit/ObservationUnit/ObservationUnitIdentifiers/ObservationUnitIdentifier or DataSets/DataSet/Units/Unit/SpecimenUnit/Accessions/AccessionNumber
-Information WithheldBrief descriptions of additional information that may exist, but that has not been made public. Information about obtaining the withheld information should be sought from the administrative contact identified in the provider resource metadata (curator, collection manager). Examples: "specific locality information given only to nearest county", "ask about tissue samples", "georeferences given only to nearest degree".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/InformationWithheld
-Information WithheldAdditional information that exists, but that has not been shared in the given record.Examples: "location information not given for endangered species", "collector identities withheld", "ask about tissue samples"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/InformationWithheld
-Infraspecific EpithetThe infraspecific epithet of the scientific name applied to the organism.2007-04-172007-04-17superseded{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
-Infraspecific EpithetThe name of the second or subspecies epithet of the scientificName.Example: "oxyadenia"2008-11-192009-04-24superseded{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
-Infraspecific EpithetThe name of the lowest or terminal infraspecific epithet of the scientificName, excluding any rank designation.Examples: "concolor", "oxyadenia", "sayi"2008-11-192009-08-24recommended{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
-Infraspecific RankThe infraspecific rank (subspecies, variety, forma) of the InfraspecificEpithet. Examples: "subsp.", "var.", "forma".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Rank
-Institution CodeA "standard" code identifier that identifies the institution to which the collection belongs. No global registry exists for assigning institutional codes. Use the code that is "standard" in your discipline.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/SourceInstitutionID
-Institution CodeA code that identifies the institution to which the cataloged item belongs. No global registry exists for institutional codes; use the code that is "standard" in your discipline. This attribute must contain no spaces.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/SourceInstitutionID
-Institution CodeThe code (or acronym) identifying the institution administering the collection in which the organism record is cataloged. No global registry exists for institutional codes; use the code that is "standard" at your institution or in your discipline.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/SourceInstitutionID
-Institution CodeThe name (or acronym) in use by the institution having custody of the object(s) or information referred to in the record.Examples: "MVZ", "FMNH", "AKN-CLO"2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/SourceInstitutionID
-Institution CodeThe name (or acronym) in use by the institution having custody of the object(s) or information referred to in the record.Examples: "MVZ", "FMNH", "AKN-CLO", "University of California Museum of Paleontology (UCMP)"2008-11-192009-08-24supersededDataSets/DataSet/Units/Unit/SourceInstitutionID
-Institution CodeThe name (or acronym) in use by the institution having custody of the object(s) or information referred to in the record.Examples: "MVZ", "FMNH", "AKN-CLO", "University of California Museum of Paleontology (UCMP)"2008-11-192013-10-04recommendedDataSets/DataSet/Units/Unit/SourceInstitutionID
-Institution IDAn identifier for the institution having custody of the object(s) or information referred to in the record.2009-09-112013-10-04recommendedDataSets/DataSet/Units/Unit/SourceInstitutionID
-IslandThe full, unabbreviated name of the island from which the cataloged item was collected.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island
-IslandThe full, unabbreviated name of the island on which the organism was collected or observed.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island
-IslandThe name of the island on or near which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.Examples: "Isla Victoria", "Vancouver", "Viti Levu", "Zanzibar"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island
-Island GroupThe full, unabbreviated name of the island group from which the cataloged item was collected.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island group
-Island GroupThe full, unabbreviated name of the island group in which the organism was collected or observed.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island group
-Island GroupThe name of the island group in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.Examples: "Alexander Archipelago", "Seychelles"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island group
-Julian DayThe ordinal day of the year; i.e., the number of days since January 1 of the same year. (January 1 is Julian Day 1.)2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberBegin
-Julian DayThe ordinal day of the year (i.e., the number of days since December 31 of the previous year; January 1 is Julian Day 1) on which the cataloged item was collected. May be derived from the YearCollected, MonthCollected, and DayCollected by the provider.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberBegin
-KingdomThe kingdom to which the organism belongs2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
-KingdomThe phylogenetic kingdom to which the cataloged item belongs.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
-KingdomThe name of the kingdom in which the organism is classified.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
-KingdomThe name of the kingdom in which the scientificName is classified.Example: "Animalia"2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
-KingdomThe full scientific name of the kingdom in which the taxon is classified.Examples: "Animalia", "Plantae"2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
-Latest AgeOr Highest StageThe full name of the latest possible geochronologic age or highest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-Latest AgeOr Highest StageThe full name of the latest possible geochronologic age or highest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Atlantic", "Boreal", "Skullrockian"2009-04-242009-07-06recommendednot in ABCD
-Latest Date CollectedThe latest date-time (Common Era calendar) in a date-time period during which an organism or group of organisms was collected or observed. If the event is recorded as occurring at a single date-time, populate both EarliestDateCollected and LatestDateCollected with the same value.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
-Latest Date CollectedThe latest date-time in a period during which a event occurred. If the event is recorded as occurring at a single date-time, populate both EarliestDateCollected and LatestDateCollected with the same value. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].2008-11-192008-11-19deprecatedDataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
-Latest Eon Or Highest EonothemThe full name of the latest possible geochronologic eon or highest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-Latest Eon Or Highest EonothemThe full name of the latest possible geochronologic eon or highest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Phanerozoic", "Proterozoic"2009-04-242009-07-06recommendednot in ABCD
-Latest Epoch Or Highest SeriesThe full name of the latest possible geochronologic epoch or highest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-Latest Epoch Or Highest SeriesThe full name of the latest possible geochronologic epoch or highest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Holocene", "Pleistocene", "Ibexian Series"2009-04-242009-07-06recommendednot in ABCD
-Latest Era Or Highest ErathemThe full name of the latest possible geochronologic era or highest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-Latest Era Or Highest ErathemThe full name of the latest possible geochronologic era or highest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Cenozoic", "Mesozoic"2009-04-242009-07-06recommendednot in ABCD
-Latest Period Or Highest SystemThe full name of the latest possible geochronologic period or highest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-Latest Period Or Highest SystemThe full name of the latest possible geochronologic period or highest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.Examples: "Neogene", "Tertiary", "Quaternary"2009-04-242009-07-06recommendednot in ABCD
-LatitudeThe latitude of the location from which the specimen was collected. This value should be expressed in decimal degrees with a datum such as WGS-842003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal
-Lat Long CommentsComments about the LatLong determination.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceRemarks
-LifestageIndicates the life stage present. Will require developing a controlled vocabulary. Can include multiple stages for a lot with multiple individuals.2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLiveStages/MycologicalLiveStage (Note DwC spec uses ”MycologicalLifeStage” or DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage
-Life StageThe age class or life stage of the biological individual represented by the catalogued object or observation. Examples: "adult", "mature", "juvenile", "eft", "nymph", "seedling", "seed", "egg"2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLiveStages/MycologicalLiveStage (Note DwC spec uses ”MycologicalLifeStage” or DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage
-Life StageThe age class or life stage of the biological individual(s) at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.Examples: "egg", "eft", "juvenile", "adult", "2 adults 4 juveniles"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLiveStages/MycologicalLiveStage (Note DwC spec uses ”MycologicalLifeStage” or DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage
-Lithostratigraphic TermsThe combination of all litho-stratigraphic names for the rock from which the cataloged item was collected.2005-07-032005-07-03recommendedDataSets/DataSet/Units/Unit/Gathering/Stratigraphy/LithostratigraphicTerms
-Lithostratigraphic TermsThe combination of all litho-stratigraphic names for the rock from which the cataloged item was collected.2009-04-242009-07-06recommendedDataSets/DataSet/Units/Unit/Gathering/Stratigraphy/LithostratigraphicTerms
-Living SpecimenA resource describing a living specimen.2008-11-192008-11-19supersededRecordBasisEnum/LivingSpecimen
-Living SpecimenA resource describing a living specimen.2008-11-192011-10-16recommendedRecordBasisEnum/LivingSpecimen
-LocalityThe locality description (place name plus optionally a displacement from the place name) from which the specimen was collected. Where a displacement from a location is provided, it should be in un-projected units of measurement2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/AreaDetail
-LocalityThe description of the locality from which the cataloged item was collected, sans geographic information provided in other geographic fields.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/AreaDetail
-LocalityThe specific natural language description of the place where the organism was collected or observed. This element need not contain less specific geographic information provided in other geographic elements (HigherGeography, Continent, Country, StateProvince, County, WaterBody, Island, IslandGroup). Though coordinate information can be contained in this concept, these data will be usable analytically only when shared through the concepts of the Geospatial Extension.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/AreaDetail
-LocalityThe specific description of the place. Less specific geographic information can be provided in other geographic terms (higherGeography, continent, country, stateProvince, county, municipality, waterBody, island, islandGroup). This term may contain information modified from the original to correct perceived errors or standardize the description.Example: "Bariloche, 25 km NNE via Ruta Nacional 40 (=Ruta 237)"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
-LocationA resource describing an instance of the Location class.2009-01-232009-04-24recommendednot in ABCD
-Location According ToInformation about the source of this Location information. Could be a publication (gazetteer), institution, or team of individuals.Examples: "Getty Thesaurus of Geographic Names", "GADM"2009-08-242009-08-24recommendednot in ABCD
-Location AttributesA list (concatenated and separated) of additional measurements, facts, characteristics, or assertions about the location.Example: "aspectheading=277; slopeindegrees=6"2009-04-242009-04-24deprecatednot in ABCD
-Location IDAn identifier for the set of location information (data associated with dcterms:Location). May be a global unique identifier or an identifier specific to the data set.2008-11-192009-04-24recommendednot in ABCD
-Location RemarksComments or notes about the Location.Example: "under water since 2005"2009-01-182009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/AreaDetail
-LongitudeThe longitude of the location from which the specimen was collected. This value should be expressed in decimal degrees with a datum such as WGS-842003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal
-Lowest Biostratigraphic ZoneThe full name of the lowest possible geological biostratigraphic zone of the stratigraphic horizon from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-Lowest Biostratigraphic ZoneThe full name of the lowest possible geological biostratigraphic zone of the stratigraphic horizon from which the cataloged item was collected.2009-04-242009-07-06recommendednot in ABCD
-Machine ObservationA resource describing an observation made by a machine.2008-11-192008-11-19supersededRecordBasisEnum/MachineObservation
-Machine ObservationA resource describing an observation made by a machine.2008-11-192008-11-19recommendedRecordBasisEnum/MachineObservation
-Material SampleThe category of information pertaining to the physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.2013-03-282013-09-26recommendedDataSets/DataSet/Units/Unit
-Material SampleA resource describing the physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.2013-03-282013-09-26recommendedDataSets/DataSet/Units/Unit
-Material Sample IDAn identifier for the MaterialSample (as opposed to a particular digital record of the material sample). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the materialSampleID globally unique.2013-03-282013-09-26recommendednot in ABCD
-Maximum DepthThe maximum distance in meters below the surface of the water at which the collection was made; all material collected was at most this deep. Positive below the surface, negative above (e.g. collecting above sea level in tidal areas).2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue
-Maximum Depth In MetersThe maximum distance in meters below the surface of the water at which the collection was made; all material collected was at most this deep. Positive below the surface, negative above (e.g., collecting above sea level in tidal areas).2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue
-Maximum Depth In MetersThe maximum or actual depth at which the collection or observation was made. Use positive values for locations below the surface. Examples: 10 (for a depth of up to 10m). 100 (for a depth between 50m and 100m).2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue
-Maximum Depth In MetersThe greater depth of a range of depth below the local surface, in meters.Example: "200"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue
-Maximum Distance Above Surface In MetersThe greater distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
-Maximum ElevationThe maximum distance in meters above (positive) or below sea level of the collecting locality.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue
-Maximum Elevation In MetersThe maximum distance in meters above (positive) or below sea level of the collecting locality.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue
-Maximum Elevation In MetersThe maximum or actual elevation at which the collection or observation was made. Use negative values for locations below sea level. Examples: Examples: 125 (for an elevation of 100 +- 25 meters). 200 (for an elevation between 100m and 200m).2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue
-Maximum Elevation In MetersThe upper limit of the range of elevation (altitude, usually above sea level), in meters.Example: "200"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue
-Measurement AccuracyThe description of the potential error associated with the measurementValue.Examples: "0.01", "normal distribution with variation of 2 m"2009-01-182009-04-24recommendedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
-Measurement Determined ByA list (concatenated and separated) of names of people, groups, or organizations who determined the value of the MeasurementOrFact.Examples: "Javier de la Torre", "Julie Woodruff; Eileen Lacey"2009-01-232009-04-24recommendedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
-Measurement Determined DateThe date on which the MeasurementOrFact was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "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.2009-01-232009-04-24recommendedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
-Measurement IDAn identifier for the MeasurementOrFact (information pertaining to measurements, facts, characteristics, or assertions). May be a global unique identifier or an identifier specific to the data set.2009-03-062009-04-24recommendednot in ABCD
-Measurement MethodA description of or reference to (publication, URI) the method or protocol used to determine the measurement, fact, characteristic, or assertion.Examples: "minimum convex polygon around burrow entrances" for a home range area, "barometric altimeter" for an elevation2008-11-192009-04-24recommended/DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Method or /DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Method or /DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Method
-Measurement Or FactThe category of information pertaining to measurements, facts, characteristics, or assertions about a resource (instance of data record, such as Occurrence, Taxon, Location, Event).2009-04-242009-04-24recommendedDatasets/Dataset/Units/Unit/MeasurementsOrFacts or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts
-Measurement RemarksComments or notes accompanying the MeasurementOrFact.Example: "tip of tail missing"2008-11-192009-04-24recommendednot in ABCD
-Measurement TypeThe nature of the measurement, fact, characteristic, or assertion. Recommended best practice is to use a controlled vocabulary.Examples: "tail length", "temperature", "trap line length", "survey area", "trap type"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
-Measurement UnitThe units associated with the measurementValue. Recommended best practice is to use the International System of Units (SI).Examples: "mm", "C", "km", "ha"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
-Measurement ValueThe value of the measurement, fact, characteristic, or assertion.Examples: "45", "20", "1", "14.5", "UV-light"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
-MemberThe full name of the lithostratigraphic member from which the cataloged item was collected.2005-07-032005-07-03recommendednot in ABCD
-MemberThe full name of the lithostratigraphic member from which the cataloged item was collected.Examples: "Lava Dam Member", "Hellnmaria Member"2009-04-242009-07-06recommendednot in ABCD
-Minimum DepthThe minimum distance in meters below the surface of the water at which the collection was made; all material collected was at least this deep. Positive below the surface, negative above (e.g. collecting above sea level in tidal areas).2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue
-Minimum Depth In MetersThe minimum distance in meters below the surface of the water at which the collection was made; all material collected was at least this deep. Positive below the surface, negative above (e.g., collecting above sea level in tidal areas).2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue
-Minimum Depth In MetersThe minimum or actual depth at which the collection or observation was made. Use positive values for locations below the surface. Examples: 0 (for a depth of up to 10m). 50 (for a depth between 50m and 100m).2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue
-Minimum Depth In MetersThe lesser depth of a range of depth below the local surface, in meters.Example: "100"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue
-Minimum Distance Above Surface In MetersThe lesser distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue
-Minimum ElevationThe minimum distance in meters above (positive) or below sea level of the collecting locality.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue
-Minimum Elevation In MetersThe minimum distance in meters above (positive) or below sea level of the collecting locality.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue
-Minimum Elevation In MetersThe minimum or actual elevation at which the collection or observation was made. Use negative values for locations below sea level. Examples: 75 (for an elevation of 100 +- 25 meters). 100 (for an elevation between 100m and 200m).2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue
-Minimum Elevation In MetersThe lower limit of the range of elevation (altitude, usually above sea level), in meters.Example: "100"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue
-MonthThe ordinal month in which the Event occurred.Examples: "1" (=January), "10" (=October)2008-11-192009-04-24recommendedaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Month CollectedThe month of year the specimen was collected from the field. Possible values range from 01...12 inclusive2003-06-132003-06-13supersededaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Month CollectedThe two digit month of year in the Common Era calendar during which the cataloged item was collected from the field.2003-06-172003-06-17supersededaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Month IdentifiedThe month portion of the date when the Collection Item was identified; as two digits [01..12].2003-06-132003-06-13supersededaccessible from DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
-Month IdentifiedThe two digit month in the Common Era calendar during which the cataloged item was identified.2003-06-172003-06-17supersededaccessible from DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
-MunicipalityThe full, unabbreviated name of the next smaller administrative region than county (city, municipality, etc.) in which the Location occurs. Do not use this term for a nearby named place that does not contain the actual location.Examples: "Holzminden"2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
-Name According ToThe reference to the source in which the specific taxon concept circumscription is defined or implied - traditionally signified by the Latin "sensu" or "sec." (from secundum, meaning "according to"). For taxa that result from identifications, a reference to the keys, monographs, experts and other sources should be given.Example: "McCranie, J. R., D. B. Wake, and L. D. Wilson. 1996. The taxonomic status of Bolitoglossa schmidti, with comments on the biology of the Mesoamerican salamander Bolitoglossa dofleini (Caudata: Plethodontidae). Carib. J. Sci. 32:395-398.", "Werner Greuter 2008", "Lilljeborg 1861, Upsala Univ. Arsskrift, Math. Naturvet., pp. 4, 5"2008-11-192009-09-21recommendednot in ABCD
-Name According To IDAn identifier for the source in which the specific taxon concept circumscription is defined or implied. See nameAccordingTo.Example: "doi:10.1016/S0269-915X(97)80026-2"2009-08-242009-09-21recommendednot in ABCD
-Name Publication IDA resolvable globally unique identifier for the original publication of the scientificName.Example: "http://hdl.handle.net/10199/7"2009-05-182009-05-18supersedednot in ABCD
-Name Published InA full reference to the original publication of the scientificName.Examples: "Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "Forel, Auguste, Diagnosies provisoires de quelques espèces nouvelles de fourmis de Madagascar, récoltées par M. Grandidier., Annales de la Societe Entomologique de Belgique, Comptes-rendus des Seances 30, 1886"2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference/TitleCitation
-Name Published InA reference for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.Examples: "Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "Forel, Auguste, Diagnosies provisoires de quelques espèces nouvelles de fourmis de Madagascar, récoltées par M. Grandidier., Annales de la Societe Entomologique de Belgique, Comptes-rendus des Seances 30, 1886"2008-11-192009-09-21recommendedDataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference/TitleCitation
-Name Published In IDAn identifier for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.Example: "http://hdl.handle.net/10199/7"2009-05-182009-09-21recommendednot in ABCD
-Name Published In YearThe four-digit year in which the scientificName was published.Examples: "1915", "2008"2011-10-162011-10-16recommendednot in ABCD
-Nomenclatural ChecklistA resource describing a nomenclatural checklist.2009-01-232009-01-23recommendednot in ABCD
-Nomenclatural CodeThe nomenclatural code under which the ScientificName is constructed. Examples: "ICBN", "ICZN", "BC", "ICNCP", "BioCode"2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/Code
-Nomenclatural CodeThe nomenclatural code under which the scientificName is constructed. Recommended best practice is to use a controlled vocabulary.Examples: "ICBN", "ICZN", "BC", "ICNCP", "BioCode"2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/Code
-Nomenclatural CodeThe nomenclatural code (or codes in the case of an ambiregnal name) under which the scientificName is constructed. Recommended best practice is to use a controlled vocabulary.Examples: "ICBN", "ICZN", "BC", "ICNCP", "BioCode", "ICZN; ICBN"2008-11-192009-09-21recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/Code
-Nomenclatural StatusThe status related to the original publication of the name and its conformance to the relevant rules of nomenclature. It is based essentially on an algorithm according to the business rules of the code. It requires no taxonomic opinion.Examples: "nom. ambig.", "nom. illeg.", "nom. subnud."2009-01-182009-04-24recommended(DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference/TitleCitation)
-pro parte
-NotesFree text notes attached to the specimen record2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Notes
-Observed Individual CountThe number of individuals (abundance) found in a collection/record event.2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue + constant
-Observed WeightThe total biomass found in a collection/record event. Expressed as kg.2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue + constant
-OccurrenceA resource describing an instance of the Occurrence class.2008-11-192008-11-19supersedednot in ABCD
-OccurrenceThe category of information pertaining to evidence of an occurrence in nature, in a collection, or in a dataset (specimen, observation, etc.).2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit
-OccurrenceA resource describing an instance of the Occurrence class.2008-11-192011-10-16recommendednot in ABCD
-Occurrence AttributesA list (concatenated and separated) of additional measurements, facts, characteristics, or assertions about the Occurrence.Examples: "Tragus length: 14mm; Weight: 120g", "Height: 1-1.5 meters tall; flowers yellow; uncommon".2008-11-192009-04-24deprecatedDataSets/DataSet/Units/Unit/MeasurementsOrFacts
-Occurrence DetailsA reference (publication, URI) to the most detailed information available about the Occurrence.Example: "http://mvzarctos.berkeley.edu/guid/MVZ:Mamm:165861"2008-11-192011-10-16deprecatedDataSets/DataSet/Units/Unit/RecordURI
-Occurrence IDAn identifier for the Occurrence (as opposed to a particular digital record of the occurrence). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the occurrenceID globally unique.For a specimen in the absence of a bona fide global unique identifier, for example, use the form: "urn:catalog:[institutionCode]:[collectionCode]:[catalogNumber]. Examples: "urn:lsid:nhm.ku.edu:Herps:32", "urn:catalog:FMNH:Mammal:145732"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/UnitGUID
-Occurrence MeasurementThe category of information pertaining to measurements accociated with an occurrence.2008-11-192009-04-24supersededDatasets/Dataset/Units/Unit/MeasurementsOrFacts
-Occurrence Measurement AccuracyThe description of the error associated with the occurrenceAttributeValue.Example: "0.01", "normal distribution with variation of 2 m"2009-01-182009-04-24deprecatedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
-Occurrence Measurement Determined ByThe agent responsible for having determined the value of the measurement or characteristic of the occurrence.Example: "Javier de la Torre"2009-01-232009-04-24deprecatedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy
-Occurrence Measurement Determined DateThe date on which the the measurement or characteristic of the occurrence was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "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.2009-01-232009-04-24deprecatedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime
-Occurrence Measurement IDAn identifier for the occurrence attribute. May be a global unique identifier or an identifier specific to the data set.2009-03-062009-04-24deprecatednot in ABCD
-Occurrence Measurement RemarksComments or notes accompanying the measurement or characteristic of the occurrence.Example: "tip of tail missing"2008-11-192009-04-24deprecatednot in ABCD
-Occurrence Measurement TypeThe nature of the measurement or characteristic of the occurrence. Recommended best practice is to use a controlled vocabulary.Example: "tail length"2008-11-192009-04-24deprecatedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
-Occurrence Measurement UnitThe units for the value of the measurement or characteristic of the occurrence. Recommended best practice is to use International System of Units (SI) units.Example: "mm"2008-11-192009-04-24deprecatedDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
-Occurrence Measurement ValueThe value of the measurement or characteristic of the occurrence.Example: "45"2008-11-192009-04-24deprecatedDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue
-Occurrence RemarksComments or notes about the Occurrence.Example: "found dead on road"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Notes
-Occurrence StatusA statement about the presence or absence of a Taxon at a Location. Recommended best practice is to use a controlled vocabulary.Examples: "present", "absent"2009-09-172009-09-17recommendednot in ABCD
-OrderThe order name of the organism2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
-OrderThe phylogenetic order to which the cataloged item belongs.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
-OrderThe name of the order in which the organism is classified.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
-OrderThe name of the order in which the scientificName is classified.Example: "Rodentia"2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
-OrderThe full scientific name of the order in which the taxon is classified.Examples: "Carnivora", "Monocleales"2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
-Original Coordinate SystemThe name of the system in which the original geographic coordinates were recorded (e.g., "decimal degrees", "degrees minutes seconds", "UTM", etc.).2003-06-172003-06-17superseded(partly) DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesGrid/GridCellSystem
-Original Name UsageThe taxon name, with authorship and date information if known, as it originally appeared when first established under the rules of the associated nomenclaturalCode. The basionym (botany) or basonym (bacteriology) of the scientificName or the senior/earlier homonym for replaced names.Examples: "Pinus abies", "Gasterosteus saltatrix Linnaeus 1768"2008-11-192009-09-21recommendednot in ABCD
-Original Name Usage IDAn identifier for the name usage (documented meaning of the name according to a source) in which the terminal element of the scientificName was originally established under the rules of the associated nomenclaturalCode.Example: "http://species.gbif.org/abies_alba_1753"2009-01-212009-09-21recommendednot in ABCD
-Other Catalog NumbersA list of previous or alternative fully qualified catalog numbers of the cataloged item whether in the current collection or in any other.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/SpecimenUnit/History/PreviousUnitsText
-Other Catalog NumbersA list of previous or alternative fully qualified catalog numbers for the same object or observation, whether in the current collection or in any other.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/SpecimenUnit/History/PreviousUnitsText
-Other Catalog NumbersA list (concatenated and separated) of previous or alternate fully qualified catalog numbers or other human-used identifiers for the same Occurrence, whether in the current or any other data set or collection.Examples: "FMNH:Mammal:1234", "NPS YELLO6778; MBG 33424"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/SpecimenUnit/History/PreviousUnitsText
-Owner Institution CodeThe name (or acronym) in use by the institution having ownership of the object(s) or information referred to in the record.Examples: "NPS", "APN", "InBio"2009-08-242013-10-04recommendednot in ABCD
-Parent Name UsageThe full name, with authorship and date information if known, of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.Examples: "Rubiaceae", "Gruiformes", "Testudinae"2009-08-242009-09-21recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
-Parent Name Usage IDAn identifier for the name usage (documented meaning of the name according to a source) of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"2009-01-212009-09-21recommendednot in ABCD
-PhylumThe phylum (or division) to which the organism belongs2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
-PhylumThe phylogenetic phylum (or division) to which the cataloged item belongs.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
-PhylumThe name of the phylum (or division) in which the organism is classified.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
-PhylumThe name of the phlyum (or division) in which the scientificName is classified.Example: "Chordata"2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
-PhylumThe full scientific name of the phylum or division in which the taxon is classified.Examples: "Chordata" (phylum), "Bryophyta" (division)2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
-Point Radius Spatial FitA measure of how well the circle defined by the coordinates and uncertainty match the original spatial representation, as a ratio of the area of the circle to the area of the original spatial representation. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given georeference does not completely contain the original representation. The PointRadiusSpatialFit is undefined if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the PointRadiusSpatialFit is 1. Detailed explanations with graphical examples can be found in the Guide to Best Practices for Georeferencing (Chapman and Wieczorek, eds. 2006).2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/PointRadiusSpatialFit
-Point Radius Spatial FitThe ratio of the area of the point-radius (decimalLatitude, decimalLongitude, coordinateUncertaintyInMeters) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given point-radius does not completely contain the original representation. The pointRadiusSpatialFit is undefined (and should be left blank) if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the pointRadiusSpatialFit is 1.Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006 (http://www.gbif.org/prog/digit/Georeferencing).2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/PointRadiusSpatialFit
-PreparationsA concatenated list of preparations and preservation methods (skin, skull, skeleton, whole animal (ETOH), slide, etc.) for the cataloged item.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/PreparationsText
-PreparationsA concatenated list of preparations and preservation methods for the object. Examples: "skin", "skull", "skeleton", "whole animal (ETOH)", "tissue (EDTA)".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/PreparationsText
-PreparationsA list (concatenated and separated) of preparations and preservation methods for a specimen.Examples: "skin; skull; skeleton", "whole animal (ETOH); tissue (EDTA)", "fossil", "cast", "photograph", "DNA extract"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/PreparationsText
-Preparation TypeThe type of preparation (skin. slide, etc). Probably best to add this as a record element rather than access point. Should be a list of preparations for a single collection record.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/PreparationsText
-Preserved SpecimenA resource describing a preserved specimen.2008-11-192008-11-19supersededRecordBasisEnum/PreservedSpecimen
-Preserved SpecimenA resource describing a preserved specimen.2008-11-192011-10-16recommendedRecordBasisEnum/PreservedSpecimen
-Previous Catalog NumberThe previous (fully qualified) catalog number of the Cataloged Item if the item earlier identified by another Catalog Number, either in the current catalog or another Institution / catalog. A fully qualified Catalog Number is preceded by Institution Code and Collection Code, with a space separating the each subelement. Referencing a previous Catalog Number does not imply that a record for the referenced item is or is not present in the corresponding catalog, or even that the referenced catalog still exists. This access point is intended to provide a way to retrieve this record by previously used identifier, which may used in the literature. In future versions of this schema this attribute should be set-valued.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/SpecimenUnit/History/PreviousUnitsText
-Previous IdentificationsA list (concatenated and separated) of previous ScientificNames to which the sample was identified.Example: "Anthus correndera".2008-11-192008-11-19supersededDataSets/DataSet/Units/Unit/Identifications/Identification with PreferredFlag = false
-Previous IdentificationsA list (concatenated and separated) of previous assignments of names to the subject.Example: "Anthus sp., field ID by G. Iglesias; Anthus correndera, expert ID by C. Cicero 2009-02-12 based on morphology"2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/Identifications/Identification with PreferredFlag = false
-Previous IdentificationsA list (concatenated and separated) of previous assignments of names to the Occurrence.Example: "Anthus sp., field ID by G. Iglesias; Anthus correndera, expert ID by C. Cicero 2009-02-12 based on morphology"2008-11-192009-05-18recommendedDataSets/DataSet/Units/Unit/Identifications/Identification with PreferredFlag = false
-Recorded ByA list (concatenated and separated) of names of people, groups, or organizations responsible for recording the original Occurrence. The primary collector or observer, especially one who applies a personal identifier (recordNumber), should be listed first.Example: "Oliver P. Pearson; Anita K. Pearson" where the value in recordNumber "OPP 7101" corresponds to the number for the specimen in the field catalog (collector number) of Oliver P. Pearson.2008-11-192009-05-18recommendedDataSets/DataSet/Units/Unit/Gathering/GatheringAgents/GatheringAgentsText
-Record NumberAn identifier given to the Occurrence at the time it was recorded. Often serves as a link between field notes and an Occurrence record, such as a specimen collector's number.Example: "OPP 7101"2008-11-192009-05-18recommendedDataSets/DataSet/Units/Unit/CollectorsFieldNumber
-Record URLGives the web address of the page where more information on this particular record (not on the whole dataset) can be found.2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/RecordURI
-Related Basis of RecordThe nature of the related resource. Recommended best practice is to use the same controlled vocabulary as for basisOfRecord.Example: "PreservedSpecimen"2008-11-192009-01-26deprecatednot in ABCD
-Related Cataloged ItemsThe fully qualified identifier (Institution Code + " " + Collection Code + " " + Catalog Number) of the related Cataloged Item, preceded by the nature of the relationship (e.g., (sibling of) MVZ Mamm 1234).2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
-Related Cataloged ItemsOne or more GlobalUniqueIdentifiers (cf. http://wiki.tdwg.org/twiki/bin/view/DarwinCore/GlobalUniqueIdentifier ) of related objects or observations, optionally preceded by the nature of the relationship. Examples: "(sibling of) URN:catalog:MVZ:Mammal:1234", "(endoparasite of) URN:catalog:FMNH:Bird:41321", "(sheet 2 of 2) URN:WTU:VascularPlants:353087".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
-Related Cataloged ItemThe fully qualified identifier of a related Catalog Item (a reference to another specimen); Institution Code, Collection Code, and Catalog Number of the related Cataloged Item, where a space separates the three subelements.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
-Related InformationFree text references to information not delivered via the conceptual schema, including URLs to specimen details, publications, bibliographic references, etc.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/RecordURI
-Related Resource IDAn identifier for a related resource (the object, rather than the subject of the relationship).2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
-Related Resource TypeThe type of the related resource. Recommended best practice is to use a controlled vocabulary.Examples: "StillImage", "MovingImage", "Sound", PhysicalObject", "PreservedSpecimen", FossilSpecimen", LivingSpecimen", "HumanObservation", "MachineObservation", "Location", "Taxonomy", "NomeclaturalChecklist", "Publication"2008-11-192009-04-24deprecatednot in ABCD
-Relationship According ToThe source (person, organization, publication, reference) establishing the relationship between the two resources.Example: "Julie Woodruff"2009-04-242009-04-24recommendednot in ABCD
-Relationship Established DateThe date-time on which the relationship between the two resources was established. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).Examples: "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.2009-04-242009-04-24recommendednot in ABCD
-Relationship Of ResourceThe relationship of the resource identified by relatedResourceID to the subject (optionally identified by the resourceID). Recommended best practice is to use a controlled vocabulary.Examples: "duplicate of", "mother of", "endoparasite of", "host to", "sibling of", "valid synonym of", "located within"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociationType
-Relationship RemarksComments or notes about the relationship between the two resources.Examples: "mother and offspring collected from the same nest", "pollinator captured in the act"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Associations/UnitAssociation/Comments
-Relationship TypeA named or coded valued that identifies the kind relationship between this Collection Item and the referenced Collection Item. Named values include: "parasite of", "epiphyte on", "progeny of", etc. In future versions of this schema this attribute should be set-valued.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociationType
-RemarksFree text comments accompanying the cataloged item record.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Notes
-RemarksFree text comments accompanying the object or observation record.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Notes
-Reproductive ConditionThe reproductive condition of the biological individual(s) represented in the Occurrence. Recommended best practice is to use a controlled vocabulary.Examples" "non-reproductive", "pregnant", "in bloom", "fruit-bearing"2008-11-192009-04-24recommendednot in ABCD
-Resource IDAn identifier for the resource that is the subject of the relationship.2009-04-242009-04-24recommendednot in ABCD
-Resource RelationshipThe category of information pertaining to relationships between resources (instances of data records, such as Occurrences, Taxa, Locations, Events).Resources can be thought of as identifiable records and may include, but need not be limited to Occurrences, Locations, Events, Identifications, or Taxon records.2008-11-192013-09-30recommendedDataSets/DataSet/Units/Unit/Associations
-Resource Relationship IDAn identifier for an instance of relationship between one resource (the subject) and another (relatedResource, the object).2009-01-262009-04-24recommendednot in ABCD
-SampleContainer class for information about the results of a sampling event (specimen, observation, etc.)2008-11-192008-11-19supersededDataSets/DataSet/Units/Unit
-Sample AttributeContainer class for information about attributes related to a given sample.2008-11-192008-11-19supersededDatasets/Dataset/Units/Unit/MeasurementsOrFacts
-Sample Attribute AccuracyThe description of the error associated with the SampleAttributeValue.Example: "0.01", "normal distribution with variation of 2 m"2009-01-182009-01-18supersededDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
-Sample Attribute Determined ByThe agent responsible for having determined the value of the measurement or characteristic of the sample.Example: "Javier de la Torre"2009-01-232009-01-23supersededDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy
-Sample Attribute Determined DateThe date on which the the measurement or characteristic of the sample was made.Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].2009-01-232009-01-23supersededDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime
-Sample Attribute RemarksComments or notes accompanying the measurement or characteristic of the sample.Example: "tip of tail missing"2008-11-192008-11-19supersedednot in ABCD
-Sample Attribute UnitThe units for the value of the measurement or characteristic of the sample. Recommended best practice is to use International System of Units (SI) units.Example: "mm"2008-11-192008-11-19supersededDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
-Sample Attribute ValueThe value of the measurement or characteristic of the sample.Example: "45"2008-11-192008-11-19supersededDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue
-Sample RemarksComments or notes about the sample or record.Example: "found dead on road"2008-11-192009-01-18supersededDataSets/DataSet/Units/Unit/Notes
-Sample SizeThe size of the sample from which the collection/observation was drawn. It can be a volume (e.g. for a phytoplankton sample), a linear distance (e.g. for a visual transect or net haul), a surface area (e.g. for a benthic core), etc. This field must also include the units, e.g. 200 mfor a transect, or 0.25 m^2 for a benthic grab (use ^ to denote a superscript). Note that When multiple collections/observations are reported from the same physical sample, a code identifying the sample can be placed in the Field_Number field to allow all collections/observations from a single sample to be connected.2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue + constant
-Sample Attribute IDAn identifier for the sampling attribute. May be a global unique identifier or an identifier specific to the data set.2008-11-192008-11-19supersedednot in ABCD
-Sample Attribute TypeThe nature of the measurement or characteristic of the sample. Recommended best practice is to use a controlled vocabulary.Example: "tail length"2008-11-192008-11-19supersededDataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
-Sampling EffortThe amount of effort expended during an Event.Examples: "40 trap-nights", "10 observer-hours; 10 km by foot; 30 km by car"2009-08-242009-08-24recommendednot in ABCD
-Sampling EventContainer class for information about the conditions and methods of acquisition of samples.2008-11-192008-11-19supersededDataSets/DataSet/Units/Unit/Gathering
-Sampling Event AttributesA list (concatenated and separated) of additional measurements or characteristics of the sampling event.Example: "Relative humidity: 28 %; Temperature: 22 C; Sample size: 10 kg"2008-11-192008-11-19supersededDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts
-Sampling Event IDAn identifier for the sampling event. May be a global unique identifier or an identifier specific to the data set.2008-11-192008-11-19supersededDataSets/DataSet/Units/Unit/Gathering/Code
-Sampling Event RemarksComments or notes about the sampling event.Example: "found dead on road"2009-01-182009-01-18supersedednot in ABCD
-Sampling LocationContainer class for information about the location where a sampling event occurred.2008-11-192008-11-19supersededDataSets/DataSet/Units/Unit/Gathering/LocalityText
-Sampling Location IDAn identifier for the sampling location. May be a global unique identifier or an identifier specific to the data set.Example: "MVZ:LocID:12345"2008-11-192008-11-19supersedednot in ABCD
-Sampling Location RemarksComments or notes about the sampling location.Example: "under water since 2005"2009-01-182009-01-18supersededDataSets/DataSet/Units/Unit/Gathering/AreaDetail
-Sampling ProtocolThe name of, reference to, or description of the method or protocol used during an Event.Examples: "UV light trap", "mist net", "bottom trawl", "ad hoc observation", "point count", "Penguins from space: faecal stains reveal the location of emperor penguin colonies, http://dx.doi.org/10.1111/j.1466-8238.2009.00467.x", "Takats et al. 2001. Guidelines for Nocturnal Owl Monitoring in North America. Beaverhill Bird Observatory and Bird Studies Canada, Edmonton, Alberta. 32 pp.", "http://www.bsc-eoc.org/download/Owl.pdf"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Method
-Scientific NameThe full name of lowest level taxon the Cataloged Item can be identified as a member of; includes genus name, specific epithet, and subspecific epithet (zool.) or infraspecific rank abbreviation, and infraspecific epithet (bot.) Use name of suprageneric taxon (e.g., family name) if Cataloged Item cannot be identified to genus, species, or infraspecific taxon.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/FullScientificNameString
-Scientific NameThe full name of lowest level taxon to which the cataloged item can be identified (e.g., genus name, specific epithet, subspecific epithet, etc.).2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/FullScientificNameString
-Scientific NameThe full name of the lowest level taxon to which the organism has been identified in the most recent accepted determination, specified as precisely as possible, including name-author, year or authorship, sensu or sec. (according to or following) author, and indication of uncertainty. Conceptually equivalent to a full taxonomic identification as given by the identifier (verbatim). Does not include the identifier name or date of identification. Examples: "Coleoptera" (an Order), "Vespertilionidae" (a Family), "Manis" (a Genus), "Ctenomys sociabilis" (Genus + SpecificEpithet), "Ambystoma tigrinum diaboli" (Genus + SpecificEpithet + SubspecificEpithet), "Quercus agrifolia var. oxyadenia (Torr.) J.T. Howell" (Genus + SpecificEpithet + InfraspecificRank + InfraspecificEpithet + AuthorYearOfScientificName).2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/FullScientificNameString
-Scientific NameThe taxon name (with date and authorship information if applicable). When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the IdentificationQualifier term.Examples: "Coleoptera" (order), "Vespertilionidae" (family), "Manis" (genus), "Ctenomys sociabilis" (genus + specificEpithet), "Ambystoma tigrinum diaboli" (genus + specificEpithet + infraspecificEpithet), "Quercus agrifolia var. oxyadenia (Torr.) J.T. Howell" (genus + specificEpithet + taxonRank + infraspecificEpithet + scientificNameAuthorship)2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/FullScientificNameString
-Scientific NameThe full scientific name, with authorship and date information if known. When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the IdentificationQualifier term.Examples: "Coleoptera" (order), "Vespertilionidae" (family), "Manis" (genus), "Ctenomys sociabilis" (genus + specificEpithet), "Ambystoma tigrinum diaboli" (genus + specificEpithet + infraspecificEpithet), "Roptrocerus typographi (Györfi, 1952)" (genus + specificEpithet + scientificNameAuthorship), "Quercus agrifolia var. oxyadenia (Torr.) J.T. Howell" (genus + specificEpithet + taxonRank + infraspecificEpithet + scientificNameAuthorship)2008-11-192009-09-21recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/FullScientificNameString
-Scientific Name AuthorThe author of a scientific name. Author string as applied to the accepted name. Can be more than one author (concatenated string). Should be formatted according to the conventions of the applicable taxonomic discipline.2003-06-132003-06-13superseded{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/ParentheticalAuthorTeamAndYear + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/AuthorTeamAndYear} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeamParenthesis + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeam} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamOriginalAndYear + [= or] DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamParenthesisAndYear}
-Scientific Name AuthorThe author of the ScientificName. Can be more than one author in a concatenated string. Should be formatted according to the conventions of the applicable taxonomic discipline.2003-06-172003-06-17superseded{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/ParentheticalAuthorTeamAndYear + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/AuthorTeamAndYear} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeamParenthesis + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeam} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamOriginalAndYear + [= or] DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamParenthesisAndYear}
-Scientific Name AuthorshipThe authorship information for the scientificName formatted according to the conventions of the applicable nomenclaturalCode.Example: "(Torr.) J.T. Howell", "(Martinovský) Tzvelev", "(Györfi, 1952)"2008-11-192009-04-24recommended{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/ParentheticalAuthorTeamAndYear + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/AuthorTeamAndYear} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeamParenthesis + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeam} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamOriginalAndYear + [= or] DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamParenthesisAndYear}
-Scientific Name IDA unique identifier for the scientificName.2008-11-192009-07-06supersedednot in ABCD
-Scientific Name IDAn identifier for the nomenclatural (not taxonomic) details of a scientific name.Example: "urn:lsid:ipni.org:names:37829-1:1.3"2008-11-192009-08-24recommendednot in ABCD
-Scientific Name RankThe taxonomic rank of the most specific name in the scientificName. Recommended best practice is to use a controlled vocabulary.Examples: "subsp.", "var.", "forma", "species", "genus"2008-11-192009-07-06supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Rank
-SexThe sex of a specimen. The domain should be a controlled set of terms (codes) based on community consensus. Proposed values: M=Male; F=Female; H=Hermaphrodite; I=Indeterminate (examined but could not be determined; U=Unkown (not examined); T=Transitional (between sexes; useful for sequential hermaphrodites)2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Sex
-SexThe sex of a cataloged item (e.g., male, female, hermaphrodite, gynandromorph, not recorded, indeterminate, transitional - between sexes, for sequential hermaphrodites).2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Sex
-SexThe sex of the biological individual represented by the cataloged object or observation. Examples: "male", "female", "hermaphrodite", "gynandromorph", "monoecious", "dioecious", "not recorded", "indeterminate", "transitional".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Sex
-SexThe sex of the biological individual(s) represented in the Occurrence. Recommended best practice is to use a controlled vocabulary.Examples: "female", "hermaphrodite", "8 males, 4 females"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Sex
-source material identifiersA unique identifier assigned to a material sample (as defined by http://rs.tdwg.org/dwc/terms/MaterialSampleID, and as opposed to a particular digital record of a material sample) used for extracting nucleic acids, and subsequent sequencing. The identifier can refer either to the original material collected or to any derived sub-samples. The INSDC qualifiers /specimen_voucher, /bio_material, or /culture_collection provide additional context and suggested syntax for this identifier for data submitted to INSDC databases.2013-05-252011-01-26deprecatednot in ABCD
-SourceIndicates who gave the record to the data provider. Can indicate a literature citation, an electronic dataset, etc. Is used to provide credit.2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/IPRStatements/Citations/Citation/Text
-SpeciesThe specific epithet of the organism2003-06-132003-06-13superseded{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
-SpeciesThe phylogenetic specific epithet of the cataloged item.2003-06-172003-06-17superseded{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
-Specific EpithetThe specific epithet of the scientific name applied to the organism.2007-04-172007-04-17superseded{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
-Specific EpithetThe name of the first or species epithet of the scientificName.Examples: "concolor", "gottschei"2008-11-192009-04-24recommended{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
-Start End Coordinate PrecisionAn estimate of how tightly the locality was specified in the Start/End Latitude and Longitude fields; expressed as a distance, in meters, that corresponds to a radius around the latitude-longitude coordinates. Use NULL where precision is unknown, cannot be estimated, or is not applicable.2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/CoordinateErrorDistanceInMeters
-Start Day CollectedFor samples/observations/record events that were taken over time this gives the start day of the collecting event. Possible value ranges from 01..31 inclusive.2005-07-102005-07-10supersededaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Start Day Of YearThe earliest ordinal day of the year on which the Event occurred (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366).Examples: "1" (=1 Jan), "366" (=31 Dec), "365" (=30 Dec in a leap year, 31 Dec in a non-leap year)2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberBegin
-Start Julian DayFor samples/observations/record events that were taken over time this gives the start ordinal day of the year for the collecting event; i.e., the number of days since January 1 of the same year. (January 1 is Julian Day 1.). Should be an integer from one to 365, i.e. of the form (([0-3][0-9][0-9)|([0-9][0-9)|([1-9])).2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberBegin
-Start LatitudeFor samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the starting latitude location from which the specimen was collected or in which the sample/observation/record event occurred. This value should be expressed in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/).2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/CoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal with attribute "begin" set to true
-Start LongitudeFor samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the starting longitude location from which the specimen was collected. Express in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/).2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/CoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal with attribute "begin" set to true
-Start Month CollectedFor samples/observations/record events that were taken over time this gives the start month of the collecting event. Possible values range from 01...12 inclusive.2005-07-102005-07-10supersededaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Start Time of DayThe time of day when the sampling event began, expressed as decimal hours from midnight local time. Examples: 0 = midnight, 12.0 = mid-day, 13.5 = 13:302005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/DateTime/TimeOfDayBegin
-Start Time of DayThe time of day when the event began, expressed as decimal hours from midnight, local time.Examples: "12.0" (= noon), "13.5" (= 1:30pm)2008-11-192009-04-24deprecatedaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Start Year CollectedFor samples/observations/record events that were taken over time this gives the start year of the collecting event. The full year should be expressed (e.g. 1972 must be expressed as "1972" not "72"). Must always be a four digit integer.2005-07-102005-07-10supersededaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-State ProvinceThe state, province or region (i.e. next political region smaller than Country) from which the specimen was collected. There is some suggestion to use the values described in ISO 3166-2 (http://www.iso.ch/cate/d8349.html), however these values are in a continual state of flux and it appears unlikely that an appropriate mechanism (by ISO) will be in place to manage these changes. Hence it is recommended that where possible, the full, unabbreviated name should be used for storing information. The server should optionally handle abbreviations as an access point. Note: this is a recurring theme (country and state) abbreviations. Check the existence of an attribute type to deal with abbreviations from the bib-1 profile2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= State or = Province (etc.)
-State ProvinceThe full, unabbreviated name of the state, province, or region (i.e., the next smaller political region than Country) from which the cataloged item was collected.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= State or = Province (etc.)
-State ProvinceThe full, unabbreviated name of the state, province, or region (i.e., the next smaller political region than Country) in which the organism was collected or observed.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= State or = Province (etc.)
-State ProvinceThe name of the next smaller administrative region than country (state, province, canton, department, region, etc.) in which the Location occurs.Examples: "Montana", "Minas Gerais", "Córdoba"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= State or = Province (etc.)
-SubgenusThe name of the subgenus in which the identified name is classified.2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/Subgenus
-SubgenusThe name of the subgenus in which the scientificName is classified.Example: "Strobus" subgenus of Pinus2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/Subgenus
-SubgenusThe full scientific name of the subgenus in which the taxon is classified. Values should include the genus to avoid homonym confusion.Examples: "Strobus (Pinus)", "Puma (Puma)" "Loligo (Amerigo)", "Hieracium subgen. Pilosella"2008-11-192009-08-24recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/Subgenus
-SubspeciesThe sub-specific epithet of the organism2003-06-132003-06-13superseded{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
-SubspeciesThe phylogenetic subspecific epithet of the cataloged item.2003-06-172003-06-17superseded{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
-TaxonThe category of information pertaining to taxonomic names or concepts.2008-11-192008-11-19supersededno simple equivalent in ABCD
-TaxonA resource describing an instance of the Taxon class.2009-01-232009-04-24recommendednot in ABCD
-TaxonThe category of information pertaining to taxonomic names, taxon name usages, or taxon concepts.2008-11-192009-09-21recommendedno simple equivalent in ABCD
-Taxon According ToInformation about the authorship of this taxon concept which uses the scientificName in their sense (secundum, sensu). Could be a publication (identification key), institution or team of individuals.2008-11-192009-04-24supersedednot in ABCD
-Taxon AttributesA list (concatenated and separated) of additional measurements, facts, characteristics, or assertions about the taxon.Example: "iucnstatus=vulnerable; distribution=Neuquen, Argentina"2009-04-242009-04-24deprecatedDataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/InformalNameString
-Taxon Concept IDA unique identifier for the taxon concept (a circumscription of a taxonName).2009-04-242009-04-24deprecatednot in ABCD
-Taxon Concept IDAn identifier for the taxonomic concept to which the record refers - not for the nomenclatural details of a taxon.Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"2009-04-242009-09-21recommendednot in ABCD
-Taxon IDA global unique identifier for the taxon (name in a classification).2008-11-192008-11-19supersedednot in ABCD
-Taxon IDAn identifier for the set of taxon information (data associated with the Taxon class). May be a global unique identifier or an identifier specific to the data set.Examples: "8fa58e08-08de-4ac1-b69c-1235340b7001", "32567", "http://species.gbif.org/abies_alba_1753", "urn:lsid:gbif.org:usages:32567"2008-11-192009-08-24recommendednot in ABCD
-Taxon Name IDA unique identifier for the scientificName.2008-11-192009-04-24supersedednot in ABCD
-Taxonomic StatusThe status of the use of the scientificName as a label for a taxon. Requires taxonomic opinion to define the scope of a taxon. Rules of priority then are used to define the taxonomic status of the nomenclature contained in that scope, combined with the experts opinion. It must be linked to a specific taxonomic reference that defines the concept. Recommended best practice is to use a controlled vocabulary.Examples: "invalid", "misapplied", "homotypic synonym", "accepted"2008-11-192009-04-24recommendednot in ABCD
-Taxon RankThe taxonomic rank of the most specific name in the scientificName. Recommended best practice is to use a controlled vocabulary.Examples: "subsp.", "var.", "forma", "species", "genus".2008-11-192009-04-24supersededDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Rank
-Taxon RankThe taxonomic rank of the most specific name in the scientificName. Recommended best practice is to use a controlled vocabulary.Examples: "subspecies", "varietas", "forma", "species", "genus"2008-11-192009-09-21recommendedDataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Rank
-Taxon RemarksComments or notes about the taxon.Example: "this name is a misspelling in common use"2008-11-192009-04-24supersedednot in ABCD
-Taxon RemarksComments or notes about the taxon or name.Example: "this name is a misspelling in common use"2008-11-192009-08-24recommendednot in ABCD
-TemperatureThe temperature recorded with the collection/record event. Is assumed to be taken at the collection depth. Expressed in degrees Celsius.2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue + constant
-Time CollectedThe time of day the cataloged item was collected, expressed as decimal hours from midnight, local time (e.g., 12.0 = noon, 13.5 = 1:30pm).2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/DateTime/TimeOfDayBegin
-Time of DayThe time of day a specimen was collected expressed as decimal hours from midnight local time (e.g. 12.0 = mid day, 13.5 = 1:30pm)2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/Gathering/DateTime/TimeOfDayBegin
-Time ZoneIndicates the time zone for the Time of Day measurements.2005-07-102005-07-10supersededDataSets/DataSet/Units/Unit/Gathering/DateTime/TimeZone
-TissuesA concatenated list of tissues and preservation methods (whole (frozen), liver (EDTA), etc.) for the cataloged item.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/PreparationsText
-Type StatusIndicates the kind of nomenclatural type that a specimen represents. (This is incomplete because type status actually describes the relationship between a name and a specimen [or ternary relatiohnship between a specimen, name, and publication].) In particular, the type status may not apply to the name listed in the scientific name, i.e., current identification. In rare cases, a single specimen may be the type of more than one name.2003-06-132003-06-13supersededDataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeText
-Type StatusA list of one or more nomenclatural types that the cataloged item represents (e.g., "holotype of Ctenomys sociabilis. Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388.").2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeText
-Type StatusA list of one or more nomenclatural types (including type status and typified taxonomic name) represented by the object. Example: "holotype of Ctenomys sociabilis. Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeText
-Type StatusA list (concatenated and separated) of nomenclatural types (type status, typified scientific name, publication) applied to the subject.Example: "holotype of Ctenomys sociabilis. Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeText
-Valid Distribution FlagA flag ("true" or "false") that indicates whether the locality information represents a valid distribution occurrence for a specimen. Specimens taken from captivity and showing the captive location should use the value "false".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/ValidDistributionFlag
-Verbatim Collecting DateThe verbatim original representation of the date information for the collecting event.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/DateTime/DateText
-Verbatim Collecting DateThe verbatim original representation of the date (and time) information for the collecting event. Example: "spring 1910".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/DateTime/DateText
-Verbatim CoordinatesA text representation of the coordinate data (Latitude/ Longitude, UTM, TRS, etc.) from its original source if it cannot be separated into its component parts. Example: "470999 1234300".2007-04-172007-04-17superseded{DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinatesText or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesUTM/UTMText}
-Verbatim CoordinatesThe verbatim original spatial coordinates of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.Examples: "41 05 54S 121 05 34W", "17T 630000 4833400"2008-11-192009-07-06recommended{DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinatesText or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesUTM/UTMText}
-Verbatim Coordinate SystemThe name of the system in which the verbatim geographic coordinates were recorded. Examples: "decimal degrees", "degrees minutes seconds", "degrees decimal minutes", "UTM"2007-04-172007-04-17superseded(partly) DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesGrid/GridCellSystem
-Verbatim Coordinate SystemThe spatial coordinate system for the verbatimLatitude and verbatimLongitude or the verbatimCoordinates of the Location. Recommended best practice is to use a controlled vocabulary.Examples: "decimal degrees", "degrees decimal minutes", "degrees minutes seconds", "UTM"2008-11-192009-07-06recommended(partly) DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesGrid/GridCellSystem
-Verbatim DepthA text representation of the Depth in its original format in the source database.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactText
-Verbatim DepthA text representation of the depth in its original format in the source database. Example: "100 to 200 ft below sea level".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactText
-Verbatim DepthThe original description of the depth below the local surface.Example: "100-200 m"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactText
-Verbatim ElevationA text representation of the Elevation in its original format in the source database.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactText
-Verbatim ElevationA text representation of the altitude in its original format in the source database. Example: "1000+- meters".2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactText
-Verbatim ElevationThe original description of the elevation (altitude, usually above sea level) of the Location.Example: "100-200 m"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactText
-Verbatim EventDateThe verbatim original representation of the date and time information for an Event.Examples: "spring 1910", "Marzo 2002", "1999-03-XX", "17IV1934"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/DateTime/DateText
-Verbatim LatitudeA text representation of the Latitude data in its original format in the source database.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLatitude
-Verbatim LatitudeA text representation of the Latitude part of the coordinate data from its original source. Example: 47d09'99"N2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLatitude
-Verbatim LatitudeThe verbatim original latitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.Example: "41 05 54.03S"2008-11-192009-07-06recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLatitude
-Verbatim LocalityThe original textual description of the place.Example: "25 km NNE Bariloche por R. Nac. 237"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
-Verbatim LongitudeA text representation of the Longitude data in its original format in the source database.2003-06-172003-06-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLongitude
-Verbatim LongitudeA text representation of the Longitude part of the coordinate data from its original source. Example: -122.432542007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLongitude
-Verbatim LongitudeThe verbatim original longitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.Example: "121d 10' 34" W"2008-11-192009-07-06recommendedDataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLongitude
-Verbatim Taxon RankThe taxonomic rank of the most specific name in the scientificName as it appears in the original record.Examples: "Agamospecies", "sub-lesus", "prole", "apomict", "nothogrex", "sp.", "subsp.", "var."2009-07-062009-09-21recommendednot in ABCD
-Verbatim Scientific Name RankThe taxonomic rank of the most specific name in the scientificName as it appears in the original record.Examples: "Agamospecies", "sub-lesus", "prole", "apomict", "nothogrex".2009-07-062009-07-06supersedednot in ABCD
-Verbatim SRSThe ellipsoid, geodetic datum, or spatial reference system (SRS) upon which coordinates given in verbatimLatitude and verbatimLongitude, or verbatimCoordinates are based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".Examples: "EPSG:4326", "WGS84", "NAD27", "Campo Inchauspe", "European 1950", "Clarke 1866"2009-07-062009-07-06recommendednot in ABCD
-Vernacular NameA common or vernacular name.Examples: "Andean Condor", "Condor Andino", "American Eagle", "Gänsegeier"2009-07-062009-07-06recommendednot in ABCD
-Water BodyThe full, unabbreviated name of the body of water in or over which the organism was collected or observed.2007-04-172007-04-17supersededDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Water body
-Water BodyThe name of the water body in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.Examples: "Indian Ocean", "Baltic Sea", "Hudson River"2008-11-192009-04-24recommendedDataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Water body
-YearThe four-digit year in which the Event occurred, according to the Common Era Calendar.Example: "2008"2008-11-192009-04-24recommendedaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Year CollectedThe year (expressed as an integer) in which the specimen was collected. The full year should be expressed (e.g. 1972 must be expressed as "1972" not "72"). Must always be a four digit integer [-9999..9999]2003-06-132003-06-13supersededaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Year CollectedThe four digit year in the Common Era calendar in which the cataloged item was collected.2003-06-172003-06-17supersededaccessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
-Year IdentifiedThe year portion of the date when the Collection Item was identified; as four digits [-9999..9999], e.g., 1906, 2002.2003-06-132003-06-13supersededaccessible from DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
-Year IdentifiedThe four digit year in the Common Era calendar in which the cataloged item was identified as having the ScientificName.2003-06-172003-06-17supersededaccessible from DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
-
-
+
+
+ Accepted Name Usage
+ The full name, with authorship and date information if known, of the currently valid (zoological) or accepted (botanical) taxon.
+ Example: "Tamias minimus" valid name for "Eutamias minimus"
+
+ 2008-11-19
+ 2009-09-21
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Accepted Name Usage ID
+ An identifier for the name usage (documented meaning of the name according to a source) of the currently valid (zoological) or accepted (botanical) taxon.
+ Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"
+
+ 2009-01-21
+ 2009-09-21
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Accepted Scientific Name
+ The currently valid (zoological) or accepted (botanical) name for the scientificName.
+ Example: "Tamias minimus" valid name for "Eutamias minimus"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Accepted Scientific Name ID
+ A unique identifier for the acceptedScientificName.
+
+ 2009-01-21
+ 2009-07-06
+
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Accepted Taxon
+ The currently valid (zoological) or accepted (botanical) name for the ScientificName.
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ not in ABCD
+
+
+
+ Accepted Taxon ID
+ A global unique identifier for the parent to the AcceptedTaxon.
+
+ 2009-01-21
+ 2009-01-21
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Accepted Taxon ID
+ An identifier for the name of the currently valid (zoological) or accepted (botanical) taxon. See acceptedTaxon.
+ Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"
+
+ 2009-01-21
+ 2009-08-24
+
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Accepted Taxon Name
+ The currently valid (zoological) or accepted (botanical) name for the scientificName.
+ Example: "Tamias minimus" valid name for "Eutamias minimus"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Accepted Taxon Name ID
+ A unique identifier for the acceptedTaxonName.
+
+ 2009-01-21
+ 2009-04-24
+
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Access Constraints
+ A description of constraints on the use of the data as shared or access to further data that is not shared.
+ Example: "not-for-profit use only".
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/IPRStatements
+
+
+
+ According To
+ Abstract term to attribute information to a source.
+
+ 2009-01-21
+ 2009-01-21
+
+
+ recommended
+ not in ABCD
+
+
+ Accuracy
+ Abstract term to capture error information about a measurement or fact.
+
+ 2009-01-21
+ 2009-01-21
+
+
+ deprecated
+ DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
+
+
+ Age Class
+ The age class, reproductive stage, life stage of the biological individual (e.g., juvenile, adult, eft, nymph, etc.).
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLifeStages/MycologicalLifeStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage}
+
+
+ Associated Media
+ A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of media associated with the Occurrence.
+ Example: "http://arctos.database.museum/SpecimenImages/UAMObs/Mamm/2/P7291179.JPG"
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/MultimediaObjects
+
+
+
+ Associated Media
+ A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of media associated with the Occurrence.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "http://arctos.database.museum/SpecimenImages/UAMObs/Mamm/2/P7291179.JPG", "http://204.140.246.24/Fish/Collection%20Pictures/10118-00.jpg | http://204.140.246.24/Fish/Collection%20Pictures/10118-00a.jpg".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/MultimediaObjects
+
+
+
+ Associated Occurrences
+ A list (concatenated and separated) of identifiers of other Occurrence records and their associations to this Occurrence.
+ Example: "sibling of FMNH:Mammal:1234; sibling of FMNH:Mammal:1235"
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
+
+
+
+ Associated Occurrences
+ A list (concatenated and separated) of identifiers of other Occurrence records and their associations to this Occurrence.
+ The recommended best practice is to separate the values with a vertical bar (' | ').
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
+
+
+
+ Associated Organisms
+ A list (concatenated and separated) of identifiers of other Organisms and their associations to this Organism.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "sibling of MXA-232", "mother of MXA-231 | mother of MXA-232"
+
+ 2014-10-23
+ 2014-10-23
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Associated References
+ A list (concatenated and separated) of identifiers (publication, bibliographic reference, global unique identifier, URI) of literature associated with the Occurrence.
+ Examples: "http://www.sciencemag.org/cgi/content/abstract/322/5899/261", "Christopher J. Conroy, Jennifer L. Neuwald. 2008. Phylogeographic study of the California vole, Microtus californicus Journal of Mammalogy, 89(3):755-767."
+
+ 2008-11-19
+ 2014-10-23
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/UnitReferences
+
+
+
+ Associated References
+ A list (concatenated and separated) of identifiers (publication, bibliographic reference, global unique identifier, URI) of literature associated with the Occurrence.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "http://www.sciencemag.org/cgi/content/abstract/322/5899/261", "Christopher J. Conroy, Jennifer L. Neuwald. 2008. Phylogeographic study of the California vole, Microtus californicus Journal of Mammalogy, 89(3):755-767.", "Steven R. Hoofer and Ronald A. Van Den Bussche. 2001. Phylogenetic Relationships of Plecotine Bats and Allies Based on Mitochondrial Ribosomal Sequences. Journal of Mammalogy 82(1):131-137. | Walker, Faith M., Jeffrey T. Foster, Kevin P. Drees, Carol L. Chambers. 2014. Spotted bat (Euderma maculatum) microsatellite discovery using illumina sequencing. Conservation Genetics Resources.".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/UnitReferences
+
+
+
+ Associated Sequences
+ A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of genetic sequence information associated with the Occurrence.
+ Example: "GenBank: U34853.1"
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/Sequences/Sequence/ID-in-Database + constant
+
+
+
+ Associated Sequences
+ A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of genetic sequence information associated with the Occurrence.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "http://www.ncbi.nlm.nih.gov/nuccore/U34853.1", "http://www.ncbi.nlm.nih.gov/nuccore/GU328060 | http://www.ncbi.nlm.nih.gov/nuccore/AF326093".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Sequences/Sequence/ID-in-Database + constant
+
+
+
+ Associated Taxa
+ A list (concatenated and separated) of identifiers or names of taxa and their associations with the Occurrence.
+ Example: "host: Quercus alba"
+
+ 2008-11-19
+ 2014-10-23
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/Gathering/Synecology/AssociatedTaxa
+
+
+
+ Associated Taxa
+ A list (concatenated and separated) of identifiers or names of taxa and their associations with the Occurrence.
+ The recommended best practice is to separate the values with a vertical bar (' | '), and to separate the relationship from the taxon with a colon (':'). Examples: "host: Quercus alba", "parasitoid of:Cyclocephala signaticollis | predator of Apis mellifera".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Gathering/Synecology/AssociatedTaxa
+
+
+
+ Attributes
+ List of additional measurements or characteristics (concatenated and separated) for which there is no existing semantic element, but which the data provider nevertheless feels the desire to share. Examples: "Tragus length: 14mm; Weight: 120g", "Height: 1-1.5 meters tall; flowers yellow; uncommon".
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts
+
+
+ Author Year of Scientific Name
+ The author of the ScientificName and the year of publication, if known. More than one author can be listed in a concatenated string. Should be formatted with parentheses and year according to the conventions of the applicable NomenclaturalCode.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/ParentheticalAuthorTeamAndYear + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/AuthorTeamAndYear} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeamParenthesis + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeam} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamOriginalAndYear + [= or] DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamParenthesisAndYear}
+
+
+ Basionym
+ The basionym (botany) or basonym (bacteriology) of the scientificName.
+ Example: "Pinus abies"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ superseded
+ not in ABCD
+
+
+
+ Basionym ID
+ A unique identifier for the basionym (botany) or basonym (bacteriology) of the scientificName.
+
+ 2009-01-21
+ 2009-04-24
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Basis of Record
+ An abbreviation indicating whether the record represents an observation (O), living organism (L), specimen (S), germplasm/seed (G), etc.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/RecordBasis
+
+
+ Basis of Record
+ A description indicating whether the record represents an observation, tissue sample, living organism, voucher specimen, germplasm/seed, genetic information, etc.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/RecordBasis
+
+
+ Basis of Record
+ A descriptive term indicating whether the record represents an object or observation. Examples: PreservedSpecimen- A physical object representing one or more organisms, part of organism, or artifact of an organism. synonyms: voucher, collection, lot. FossilSpecimen- A physical object representing one or more fossil organisms, part of fossil organism, or artifact of a fossil organism. LivingSpecimen- An organism removed from its natural occurrence and now living in captivity or cultivation. HumanObservation- A report by a known observer that an organism was present at the place and time. MachineObservation- A report by a monitoring device that an organism was present at the place and time. StillImage- An photograph, drawing, painting. MovingImage- A sequence of still images taken at regular intervals and intended to be played back as a moving image; may include sound. SoundRecording- An audio recording. OtherSpecimen- Any type of specimen not covered by any of the categories above.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/RecordBasis
+
+
+ Basis of Record
+ The specific nature of the data record - a subtype of the dcterms:type. Recommended best practice is to use a controlled vocabulary such as the Darwin Core Type Vocabulary (http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm).
+ Examples: "StillImage", "MovingImage", "Sound", "PreservedSpecimen", FossilSpecimen", LivingSpecimen", "HumanObservation", "MachineObservation"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/RecordBasis
+
+
+
+ Basis of Record
+ The specific nature of the data record - a subtype of the dcterms:type. Recommended best practice is to use a controlled vocabulary.
+ Examples: "StillImage", "MovingImage", "Sound", "PreservedSpecimen", FossilSpecimen", LivingSpecimen", "HumanObservation", "MachineObservation"
+
+ 2008-11-19
+ 2009-09-11
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/RecordBasis
+
+
+
+ Basis of Record
+ The specific nature of the data record. Recommended best practice is to use a controlled vocabulary such as the Darwin Core Type Vocabulary (http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm).
+ Examples: "PreservedSpecimen", "FossilSpecimen", "LivingSpecimen", "HumanObservation", "MachineObservation"
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/RecordBasis
+
+
+
+ Basis of Record
+ The specific nature of the data record.
+ Recommended best practice is to use a controlled vocabulary such as the list of Darwin Core classes. Examples: "PreservedSpecimen", "FossilSpecimen", "LivingSpecimen", "HumanObservation", "MachineObservation"
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/RecordBasis
+
+
+
+ Bed
+ The full name of the lithostratigraphic bed from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Bed
+ The full name of the lithostratigraphic bed from which the cataloged item was collected.
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Behavior
+ A description of the behavior shown by the subject at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.
+ Examples: "roosting", "foraging", "running"
+
+ 2009-03-06
+ 2009-04-24
+
+
+ recommended
+ not in ABCD
+
+
+
+ Binomial
+ The combination of genus and first (species) epithet of the scientificName.
+ Example: "Ctenomys sociabilis"
+
+ 2008-11-19
+ 2008-11-19
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/Gathering/Synecology/AssociatedTaxa/TaxonIdentified/ScientificName/FullScientificNameString
+
+
+
+ Bounding Box
+ This access point provides a mechanism for performing searches using a bounding box. A Bounding Box element is not typically present in the database, but rather is derived from the Latitude and Longitude columns by the data provider
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ not covered by ABCD
+
+
+ Bounding Box
+ This access point provides a mechanism for performing searches using a bounding box. A Bounding Box element is not typically present in the database, but rather is derived from the DecimalLatitude and DecimalLongitude columns by the data provider.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ not covered by ABCD
+
+
+ Catalog Number
+ A unique alphanumeric value which identifies an individual record within the collection. It is recommended that this value provides a key by which the actual specimen can be identified. If the specimen has several items such as various types of preparation, this value should identify the individual component of the specimen
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/UnitID
+
+
+ Catalog Number
+ The alphanumeric value identifying a record within the collection. It is highly recommended that each record be uniquely identified within a collection by this value. It is also recommended that each record be uniquely identified in a global context by the combination of InstitutionCode, CollectionCode and CatalogNumber.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/UnitID
+
+
+ Catalog Number
+ An identifier (preferably unique) for the record within the data set or collection.
+ Examples: "2008.1334", "145732a", "145732"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/UnitID
+
+
+
+ Catalog Number Numeric
+ The CatalogNumber as a numeric value, if applicable. Allows searching on numeric ranges of CatalogNumbers.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/UnitIDNumeric
+
+
+ Catalog Number Numeric
+ The CatalogNumber as a numeric value, if applicable. This element allows searching on numeric ranges of CatalogNumbers. Example: 145732.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/UnitIDNumeric
+
+
+ Catalog Number Numeric
+ The numeric value of the catalogNumber, used to facilitate numerical sorting and searching by ranges.
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/UnitIDNumeric
+
+
+
+ Catalog Number Text
+ An alphanumeric value which identifies an individual cataloged item within the collection. It is recommended that this value provides a key by which the individual cataloged item can be identified.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/UnitID
+
+
+ Citation
+ Indicates how this dataset or record should be attributed if used.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/IPRStatements/Citations/Citation/Text
+
+
+ Class
+ The class name of the organism
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
+
+
+ Class
+ The phylogenetic class to which the cataloged item belongs.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
+
+
+ Class
+ The name of the class in which the organism is classified.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
+
+
+ Class
+ The name of the class in which the scientificName is classified.
+ Example: "Mammalia"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
+
+
+
+ Class
+ The full scientific name of the class in which the taxon is classified.
+ Examples: "Mammalia", "Hepaticopsida"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
+
+
+
+ Collection Method
+ The name of, reference to, or brief description of the method or protocol under which the collecting event occurred. Examples: "UV light trap", "mist net", "bottom trawl".
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Method
+
+
+ Collection Code
+ A unique alphanumeric value which identifies the collection within the institution
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SourceID
+
+
+ Collection Code
+ A unique alphanumeric value that identifies the collection within the institution in which the item is cataloged. This attribute must contain no spaces.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SourceID
+
+
+ Collection Code
+ The code (or acronym) identifying the collection within the institution in which the organism record is cataloged.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SourceID
+
+
+ Collection Code
+ The name (or acronym) identifying the collection or data set from which the record was derived.
+ Examples: "Mammals", "Hildebrandt", "eBird"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SourceID
+
+
+
+ Collection Code
+ The name, acronym, coden, or initialism identifying the collection or data set from which the record was derived.
+ Examples: "Mammals", "Hildebrandt", "eBird"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SourceID
+
+
+
+ Collection Code
+ The name, acronym, coden, or initialism identifying the collection or data set from which the record was derived.
+ Examples: "Mammals", "Hildebrandt", "eBird"
+
+ 2008-11-19
+ 2013-10-04
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/SourceID
+
+
+
+ Collection ID
+ An identifier for the collection or dataset from which the record was derived. For physical specimens, the recommended best practice is to use the identifier in a collections registry such as the Biodiversity Collections Index (http://www.biodiversitycollectionsindex.org/).
+ Example: "urn:lsid:biocol.org:col:34818"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SourceID
+
+
+
+ Collection ID
+ An identifier for the collection or dataset from which the record was derived.
+ For physical specimens, the recommended best practice is to use an identifier from a collections registry such as the Global Registry of Biodiversity Repositories (http://grbio.org/). Examples: "http://biocol.org/urn:lsid:biocol.org:col:1001", "http://grbio.org/cool/p5fp-c036".
+
+ 2008-11-19
+ 2014-10-23
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/SourceID
+
+
+
+ Collector
+ The name(s) of the collector(s) responsible for collection the specimen or taking the observation
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/GatheringAgents/GatheringAgentsText
+
+
+ Collector
+ The name(s) of the collector(s) of the original data for the cataloged item.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/GatheringAgents/GatheringAgentsText
+
+
+ Collector
+ The name(s) (concatenated and separated) of collectors or observers. "LIKE" or "contains" substring query operations are meant to be used with this element to find matching collector names. The primary collector or observer, especially one whose CollectorNumber is also provided, should be listed first. Example: "Oliver P. Pearson, Anita K. Pearson" where the value in CollectorNumber "OPP 7101" corresponds to the number for the specimen in the field catalog (collector number) of Oliver P. Pearson.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/GatheringAgents/GatheringAgentsText
+
+
+ Collector Number
+ An identifying "number" (really a string) applied to specimens (in some disciplines) at the time of collection. Establishes a links different parts/preparations of a single specimen and between field notes and the specimen.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/CollectorsFieldNumber
+
+
+ Collector Number
+ An identifying string applied to the cataloged item at the time of collection. Serves as a link between field notes and the cataloged items.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/CollectorsFieldNumber
+
+
+ Collector Number
+ An identifying string applied to the object or observation at the time of collection. Serves as a link between field notes and the object or observation.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/GatheringAgents/GatheringAgentsText
+
+
+ Continent
+ The full, unabbreviated name of the continent on which the organism was collected or observed.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Continent
+
+
+ Continent
+ The name of the continent in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
+ Examples: "Africa", "Antarctica", "Asia", "Europe", "North America", "Oceania", "South America"
+
+ 2008-11-19
+ 2013-10-04
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Continent
+
+
+
+ Continent Ocean
+ The continent or ocean from which a specimen was collected.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Continent
+
+
+ Continent Ocean
+ The full, unabbreviated name of the continent or ocean from which the cataloged item was collected.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Continent
+
+
+ Coordinate Precision
+ An estimate of how tightly the collecting locality was specified; expressed as a distance, in meters, that corresponds to a radius around the latitude-longitude coordinates. Use NULL where precision is unknown, cannot be estimated, or is not applicable.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/ISOAccuracy or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/AccuracyStatement
+
+
+ Coordinate Precision
+ A decimal representation of the precision of the coordinates given in the decimalLatitude and decimalLongitude.
+ Examples: "0.00001" (normal GPS limit for decimal degrees), "0.000278" (nearest second), "0.01667" (nearest minute), "1.0" (nearest degree)
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/ISOAccuracy or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/AccuracyStatement
+
+
+
+ Coordinate Uncertainty In Meters
+ The upper limit of the distance (in meters) from the given latitude and longitude describing a circle within which the whole of the described locality must lie. Use NULL where the uncertainty is unknown, cannot be estimated, or is not applicable.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinateErrorDistanceInMeters
+
+
+ Coordinate Uncertainty In Meters
+ The upper limit of the distance (in meters) from the given DecimalLatitude and DecimalLongitude describing a circle within which the whole of the described locality lies. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Describes the point-radius representation of the location, along with DecimalLatitude, DecimalLongitude, and GeodeticDatum. Zero is not a valid value for this element.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinateErrorDistanceInMeters
+
+
+ Coordinate Uncertainty In Meters
+ The horizontal distance (in meters) from the given decimalLatitude and decimalLongitude describing the smallest circle containing the whole of the Location. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Zero is not a valid value for this term.
+ Examples: "30" (reasonable lower limit of a GPS reading under good conditions if the actual precision was not recorded at the time), "71" (uncertainty for a UTM coordinate having 100 meter precision and a known spatial reference system).
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinateErrorDistanceInMeters
+
+
+
+ Country
+ The country or major political unit from which the specimen was collected. ISO 3166-1 (http://www.din.de/gremien/nas/nabd/iso3166ma/codlstp1/db_en.html) values should be used. Full country names are currently in use. A future recommendation is to use ISO3166-1 two letter codes or the full name when searching
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Country/Name
+
+
+ Country
+ The full, unabbreviated name of the country or major political unit from which the cataloged item was collected.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Country/Name
+
+
+ Country
+ The full, unabbreviated name of the country or major political unit in which the organism was collected or observed.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Country/Name
+
+
+ Country
+ The name of the country or major administrative unit in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
+ Examples: "Denmark", "Colombia", "España"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Country/Name
+
+
+
+ Country Code
+ The standard code for the country in which the Location occurs. Recommended best practice is to use ISO 3166-1-alpha-2 country codes.
+ Examples: "AR" for Argentina, "SV" for El Salvador
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Country/ISO3166Code
+
+
+
+ County
+ The county (or shire, or next political region smaller than State / Province) from which the specimen was collected
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= County
+
+
+ County
+ The full, unabbreviated name of the county, shire, or municipality (i.e., the next smaller political region than StateProvince) from which the cataloged item was collected.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= County
+
+
+ County
+ The full, unabbreviated name of the county, shire, or municipality (i.e., the next smaller political region than StateProvince) in which the organism was collected or observed.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= County
+
+
+ County
+ The full, unabbreviated name of the next smaller administrative region than stateProvince (county, shire, department, etc.) in which the Location occurs.
+ Examples: "Missoula", "Los Lagos", "Mataró"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= County
+
+
+
+ Data Generalizations
+ Actions taken to make the shared data less specific or complete than in its original form. Suggests that alternative data of higher quality may be available on request.
+ Example: "Coordinates generalized from original GPS coordinates to the nearest half degree grid cell"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Dataset
+ The category of information pertaining to a logical set of records.
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+ deprecated
+ DataSets/DataSet
+
+
+ Dataset ID
+ An identifier for the data set. May be a global unique identifier or an identifier specific to a collection or institution.
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ DataSets/DataSet/DataSetGUID
+
+
+
+ Dataset ID
+ An identifier for the set of data. May be a global unique identifier or an identifier specific to a collection or institution.
+
+ 2008-11-19
+ 2009-09-11
+
+
+
+
+ recommended
+ DataSets/DataSet/DataSetGUID
+
+
+
+ Dataset Name
+ The name identifying the data set from which the record was derived.
+ Examples: "Grinnell Resurvey Mammals", "Lacey Ctenomys Recaptures"
+
+ 2009-09-11
+ 2009-09-11
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/SourceID
+
+
+
+ Date Identified
+ The date-time in the Common Era calendar in which the object or observation was identified as being a member of the taxon given in the ScientificName.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
+
+
+ Date Identified
+ The date on which the subject was identified as representing the taxon given in the scientificName. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "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.
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
+
+
+
+ Date Identified
+ The date on which the subject was identified as representing the Taxon. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "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.
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
+
+
+
+ Date Last Modified
+ ISO 8601 compliant stamp indicating the date and time in UTC(GMT) when the record was last modified. Example: the instant "November 5, 1994, 8:15:30 am, US Eastern Standard Time" would be represented as "1994-11-05T13:15:30Z" (see W3C Note on Date and Time Formats - http://www.w3.org/TR/NOTE-datetime). (What to do when this date-time is unknown? Use Date-Time first "published"?)
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/DateLastEdited
+
+
+ Date Last Modified
+ ISO 8601 date and time in UTC(GMT) when the record was last modified. Example: "November 5, 1994, 8:15:30 am, US Eastern Standard Time" would be "1994-11-05T13:15:30Z" (see http://www.w3.org/TR/NOTE-datetime).
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/DateLastEdited
+
+
+ Date Last Modified
+ The last date-time of publication when any of the data for the record were modified from the previous publication of that record. When publishing a record for the first time, use the publication date-time. Returns values as ISO 8601 date and time. (cf. http://www.w3.org/TR/xmlschema-2/#isoformats and http://www.iso.org/iso/en/prods-services/popstds/dateandtime.html Example: November 5, 1994, 8:15:30 am, US Eastern Standard Time” would be “1994-11-05T13:15:30Z”
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/DateLastEdited
+
+
+ Day
+ The integer day of the month on which the Event occurred.
+ Examples: "9", "28"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+
+ Day Collected
+ The day of the month the specimen was collected from the field. Possible value ranges from 01..31 inclusive
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+ Day Collected
+ The two digit day of the month in the Common Era calendar during which the cataloged item was collected from the field.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+ Day Identified
+ The day portion of the date when the Collection Item was identified; as two digits [01..31].
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
+
+
+ Day Identified
+ The two digit day of the month in the Common Era calendar during which the cataloged item was identified.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
+
+
+ Day of Year
+ The ordinal day of the year on which the object or observation was collected (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366). If the EarliestDateCollected and LatestDateCollected do not occur on the same day, do not populate DayOfYear.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberBegin
+
+
+ Decimal Latitude
+ The latitude of the location from which the cataloged item was collected, expressed in decimal degrees.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal
+
+
+ Decimal Latitude
+ The latitude of the geographic center of a location where an event occurred (organism collected, observation made), expressed in decimal degrees. Positive values are North of the Equator, negative values are South of the Equator. Describes the point-radius representation of the location, along with DecimalLongitude, GeodeticDatum, and CoordinateUncertaintyInMeters. Example: -41.0983423
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal
+
+
+ Decimal Latitude
+ The geographic latitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are north of the Equator, negative values are south of it. Legal values lie between -90 and 90, inclusive.
+ Example: "-41.0983423"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal
+
+
+
+ Decimal Longitude
+ The longitude of the location from which the cataloged item was collected, expressed in decimal degrees.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal
+
+
+ Decimal Longitude
+ The longitude of the geographic center of a location where an event occurred (organism collected, observation made), expressed in decimal degrees. Positive values are East of the Greenwich Meridian, negative values are West of the Greenwich Meridian. Describes the point-radius representation of the location, along with DecimalLatitude, GeodeticDatum, and CoordinateUncertaintyInMeters. Example: -71.0943235
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal
+
+
+ Decimal Longitude
+ The geographic longitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are east of the Greenwich Meridian, negative values are west of it. Legal values lie between -180 and 180, inclusive.
+ Example: "-121.1761111"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal
+
+
+
+ Depth Range
+ For data sets that have the depth range expressed in one field (e.g. "150-200 m") it can be entered here as free text. Separate, numeric Minimum and Maximum Depth fields are the preferred format; the Depth Range option is included for legacy data sets.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactText
+
+
+ Disposition
+ The current disposition of the cataloged item. Examples: "in collection", "missing", "voucher elsewhere", "duplicates elsewhere".
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SpecimenUnit/Disposition
+
+
+ Disposition
+ The current state of a specimen with respect to the collection identified in collectionCode or collectionID. Recommended best practice is to use a controlled vocabulary.
+ Examples: "in collection", "missing", "voucher elsewhere", "duplicates elsewhere"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/SpecimenUnit/Disposition
+
+
+
+ Darwin Core Type
+ The set of classes specified by the Darwin Core Type Vocabulary, used to categorize the nature or genre of the resource.
+
+ 2008-11-19
+ 2014-10-23
+
+
+ deprecated
+ not in ABCD
+
+
+ Dynamic Properties
+ A list (concatenated and separated) of additional measurements, facts, characteristics, or assertions about the record. Meant to provide a mechanism for structured content such as key-value pairs.
+ Examples: "tragusLengthInMeters=0.014; weightInGrams=120", "heightInMeters=1.5", "natureOfID=expert identification; identificationEvidence=cytochrome B sequence", "relativeHumidity=28; airTemperatureInC=22; sampleSizeInKilograms=10", "aspectHeading=277; slopeInDegrees=6", "iucnStatus=vulnerable; taxonDistribution=Neuquen, Argentina"
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ superseded
+
+ not in ABCD
+
+
+
+ Dynamic Properties
+ A list of additional measurements, facts, characteristics, or assertions about the record. Meant to provide a mechanism for structured content.
+ The recommended best practice is to use a key:value encoding schema such as JSON. Examples: "{'heightInMeters':'1.5'}", "{'tragusLengthInMeters':'0.014', 'weightInGrams':'120'}", "{'natureOfID':'expert identification', 'identificationEvidence':'cytochrome B sequence'}", "{'relativeHumidity':'28', 'airTemperatureInCelcius':'22', 'sampleSizeInKilograms':'10'}", "{'aspectHeading':'277', 'slopeInDegrees':'6'}", "{'iucnStatus':'vulnerable', 'taxonDistribution':'Neuquén, Argentina'}".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Earliest Age Or Lowest Stage
+ The full name of the earliest possible geochronologic age or lowest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Earliest Age Or Lowest Stage
+ The full name of the earliest possible geochronologic age or lowest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Atlantic", "Boreal", "Skullrockian"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Earliest Date Collected
+ The earliest date-time (Common Era calendar) in a date-time period during which an organism or group of organisms was collected or observed. If the event is recorded as occurring at a single date-time, populate both EarliestDateCollected and LatestDateCollected with the same value.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+ Earliest Date Collected
+ The earliest date-time in a period during which a event occurred. If the event is recorded as occurring at a single date-time, populate both EarliestDateCollected and LatestDateCollected with the same value. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+
+ Earliest Eon Or Lowest Eonothem
+ The full name of the earliest possible geochronologic eon or lowest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Earliest Eon Or Lowest Eonothem
+ The full name of the earliest possible geochronologic eon or lowest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Phanerozoic", "Proterozoic"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Earliest Epoch Or Lowest Series
+ The full name of the earliest possible geochronologic epoch or lowest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Earliest Epoch Or Lowest Series
+ The full name of the earliest possible geochronologic epoch or lowest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Holocene", "Pleistocene", "Ibexian Series"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Earliest Era Or Lowest Erathem
+ The full name of the earliest possible geochronologic era or lowest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Earliest Era Or Lowest Erathem
+ The full name of the earliest possible geochronologic era or lowest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Cenozoic", "Mesozoic"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Earliest Period Or Lowest System
+ The full name of the earliest possible geochronologic period or lowest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Earliest Period Or Lowest System
+ The full name of the earliest possible geochronologic period or lowest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Neogene", "Tertiary", "Quaternary"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ End Day Collected
+ For samples/observations/record events that were taken over time this gives the end day of the collecting event. Possible value ranges from 01..31 inclusive.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
+
+
+ End Day Of Year
+ The latest ordinal day of the year on which the Event occurred (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366).
+ Examples: "1" (=1 Jan), "366" (=31 Dec), "365" (=30 Dec in a leap year, 31 Dec in a non-leap year)
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberEnd
+
+
+
+ End Julian Day
+ For samples/observations/record events that were taken over time this gives the end ordinal day of the year for the collecting event; i.e., the number of days since January 1 of the same year. (January 1 is Julian Day 1.). Should be an integer from one to 365, i.e. of the form (([0-3][0-9][0-9)|([0-9][0-9)|([1-9])).
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberEnd
+
+
+ End Latitude
+ For samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the starting latitude location from which the specimen was collected or in which the sample/observation/record event occurred. This value should be expressed in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/).
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/CoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal with attribute "begin" set to true
+
+
+ End Longitude
+ For samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the starting longitude location from which the specimen was collected. Express in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/).
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/CoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal with attribute "begin" set to true
+
+
+ End Month Collected
+ For samples/observations/record events that were taken over time this gives the end month of the collecting event. Possible values range from 01...12 inclusive.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
+
+
+ End Time of Day
+ The time of day when the sampling event ended, expressed as decimal hours from midnight local time. Examples: 0 = midnight, 12.0 = mid-day, 13.5 = 13:30
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/TimeOfDayEnd
+
+
+ End Time of Day
+ The time of day when the event ended, expressed as decimal hours from midnight, local time.
+ Examples: "12.0" (= noon), "13.5" (= 1:30pm)
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/TimeOfDayEnd
+
+
+
+ End Year Collected
+ For samples/observations/record events that were taken over time this gives the end year of the collecting event. The full year should be expressed (e.g. 1972 must be expressed as "1972" not "72"). Must always be a four digit integer.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
+
+
+ Establishment Means
+ The process by which the biological individual(s) represented in the Occurrence became established at the location. Recommended best practice is to use a controlled vocabulary.
+ Examples: "native", "introduced", "naturalised", "invasive", "managed"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/EstablishmentMeans
+
+
+
+ Event
+ The category of information pertaining to an event (an action that occurs at a place and during a period of time).
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/Gathering
+
+
+ Event
+ An action that occurs at some location during some time.
+ Examples: A specimen collection process. A machine observation.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Gathering
+
+
+ Event Attribute
+ Container class for information about attributes related to a given sampling event.
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts
+
+
+ Event Attribute Accuracy
+ The description of the error associated with the EventAttributeValue.
+ Example: "0.01", "normal distribution with variation of 2 m"
+
+ 2009-01-18
+ 2009-01-18
+
+
+
+ superseded
+ DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
+
+
+
+ Event Attribute Determined By
+ The agent responsible for having determined the value of the measurement or characteristic of the sampling event.
+ Example: "Robert Hijmans"
+
+ 2009-01-23
+ 2009-01-23
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
+
+
+
+ Event Attribute Determined Date
+ The date on which the the measurement or characteristic of the sampling event was made.
+ Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
+
+ 2009-01-23
+ 2009-01-23
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
+
+
+
+ Event Attribute ID
+ An identifier for the event attribute. May be a global unique identifier or an identifier specific to the data set.
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Event Attribute Remarks
+ Comments or notes accompanying the measurement or characteristic of the sampling event.
+ Example: "temperature taken at 15:00"
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ not in ABCD
+
+
+
+ Event Attributes
+ A list (concatenated and separated) of additional measurements or characteristics of the Event.
+ Example: "Relative humidity: 28 %; Temperature: 22 C; Sample size: 10 kg"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts
+
+
+
+ Event Attribute Type
+ The nature of the measurement or characteristic of the sampling event. Recommended best practice is to use a controlled vocabulary.
+ Example: "Temperature"
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
+
+
+
+ Event Attribute Unit
+ The units for the value of the measurement or characteristic of the sampling event. Recommended best practice is to use International System of Units (SI) units.
+ Example: "C"
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
+
+
+
+ Event Attribute
+ The value of the measurement or characteristic of the sampling event.
+ Example: "22"
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
+
+
+
+ Event Date
+ The date-time or interval during which an Event occurred. For occurrences, this is the date-time when the event was recorded. Not suitable for a time in a geological context. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "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.
+
+ 2009-04-24
+ 2009-07-01
+
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+
+ Event ID
+ An identifier for the set of information associated with an Event (something that occurs at a place and time). May be a global unique identifier or an identifier specific to the data set.
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Code
+
+
+
+ Event Measurement
+ The category of information pertaining to measurements associated with an event.
+
+ 2008-11-19
+ 2009-04-24
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts
+
+
+
+ Event Measurement Accuracy
+ The description of the error associated with the EventAttributeValue.
+ Example: "0.01", "normal distribution with variation of 2 m"
+
+ 2009-01-18
+ 2009-04-24
+
+
+
+
+ deprecated
+ DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
+
+
+
+ Event Measurement Determined By
+ The agent responsible for having determined the value of the measurement or characteristic of the event.
+ Example: "Robert Hijmans"
+
+ 2009-01-23
+ 2009-04-24
+
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
+
+
+
+ Event Measurement Determined Date
+ The date on which the the measurement or characteristic of the event was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "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.
+
+ 2009-01-23
+ 2009-04-24
+
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
+
+
+
+ Event Measurement ID
+ An identifier for the event attribute. May be a global unique identifier or an identifier specific to the data set.
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ deprecated
+ not in ABCD
+
+
+
+ Event Measurement Remarks
+ Comments or notes accompanying the measurement or characteristic of the event.
+ Example: "temperature taken at 15:00"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ deprecated
+ not in ABCD
+
+
+
+ Event Measurement Type
+ The nature of the measurement or characteristic of the event. Recommended best practice is to use a controlled vocabulary.
+ Example: "temperature"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
+
+
+
+ Event Measurement Unit
+ The units for the value of the measurement or characteristic of the event. Recommended best practice is to use International System of Units (SI) units.
+ Example: "C"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
+
+
+
+ Event Measurement Value
+ The value of the measurement or characteristic of the event.
+ Example: "22"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
+
+
+
+ Event Remarks
+ Comments or notes about the Event.
+ Example: "after the recent rains the river is nearly at flood stage"
+
+ 2009-01-18
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Notes
+
+
+
+ Event Time
+ The time or interval during which an Event occurred. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "14:07-0600" is 2:07pm in the time zone six hours earlier than UTC, "08:40:21Z" is 8:40:21am UTC, "13:00:00Z/15:30:00Z" is the interval between 1pm UTC and 3:30pm UTC.
+
+ 2009-04-24
+ 2009-04-24
+
+
+
+
+ recommended
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin and DataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
+
+
+
+ Family
+ The family name of the organism
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
+
+
+ Family
+ The phylogenetic family to which the cataloged item belongs.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
+
+
+ Family
+ The name of the family in which the organism is classified.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
+
+
+ Family
+ The name of the family in which the scientificName is classified.
+ Example: "Ctenomyidae"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
+
+
+
+ Family
+ The full scientific name of the family in which the taxon is classified.
+ Examples: "Felidae", "Monocleaceae"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
+
+
+
+ Field Notes
+ A reference to, or flag marking the existence of notes taken in the field for the cataloged item.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/FieldNotes
+
+
+ Field Notes
+ One of a) a flag indicating the existence of, b) a reference to (such as a URL or literature citation), or c) the actual free text content of notes taken in the field about the specimen or observation.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/FieldNotes
+
+
+ Field Notes
+ One of a) an indicator of the existence of, b) a reference to (publication, URI), or c) the text of notes taken in the field about the Event.
+ Example: "notes available in Grinnell-Miller Library"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/FieldNotes
+
+
+
+ Field Number
+ A "number" (really a string) created at collection time to identify all material that resulted from a collecting event.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Code
+
+
+ Field Number
+ An identifying string applied to a set of material that resulted from a single collecting event.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Code
+
+
+ Field Number
+ An identifying string applied to a set of objects or observations resulting from a single collecting event.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Code
+
+
+ Field Number
+ An identifier given to the event in the field. Often serves as a link between field notes and the Event.
+ Example: "RV Sol 87-03-08"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Code
+
+
+
+ Footprint Spatial Fit
+ A measure of how well the geometry expressed in the footprint match the original spatial representation, as a ratio of the area of the footprint given to the area of the original spatial representation. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given georeference does not completely contain the original representation. The FootprintSpatialFit is undefined if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the FootprintSpatialFit is 1. Detailed explanations with graphical examples can be found in the Guide to Best Practices for Georeferencing (Chapman and Wieczorek, eds. 2006).
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/FootprintSpatialFit (ABCD v2.06b)
+
+
+ Footprint Spatial Fit
+ The ratio of the area of the footprint (footprintWKT) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given footprint does not completely contain the original representation. The footprintSpatialFit is undefined (and should be left blank) if the original representation is a point and the given georeference is not that same point. If both the original and the given georeference are the same point, the footprintSpatialFit is 1.
+ Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/FootprintSpatialFit (ABCD v2.06b)
+
+
+
+ Footprint SRS
+ A Well-Known Text (WKT) representation of the Spatial Reference System (SRS) for the footprintWKT of the Location. Do not use this term to describe the SRS of the decimalLatitude and decimalLongitude, even if it is the same as for the footprintWKT - use the geodeticDatum instead.
+ Example: The WKT for the standard WGS84 SRS (EPSG:4326) is "GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137,298.257223563]],PRIMEM["Greenwich",0],UNIT["Degree",0.0174532925199433]]" without the enclosing quotes.
+
+ 2009-07-06
+ 2009-07-06
+
+
+ recommended
+ not in ABCD
+
+
+
+ Footprint WKT
+ A Well-Known Text (WKT; see http://en.wikipedia.org/wiki/Well-known_text) representation of the the shape (footprint, geometry) that defines the location of the occurrence. The same place may have both a point-radius representation (see DecimalLatitude) and a footprint representation, and they may differ from each other for the same occurrence. Example: the one-degree bounding box with opposite corners at (longitude=10, latitude=20) and (longitude=11, latitude=21) would be expressed in well-known text as POLYGON ((10 20, 11 20, 11 21, 10 21, 10 20))
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/FootprintWKT (ABCD v2.06b)
+
+
+ Footprint WKT
+ A Well-Known Text (WKT) representation of the shape (footprint, geometry) that defines the Location. A Location may have both a point-radius representation (see decimalLatitude) and a footprint representation, and they may differ from each other.
+ Example: the one-degree bounding box with opposite corners at (longitude=10, latitude=20) and (longitude=11, latitude=21) would be expressed in well-known text as POLYGON ((10 20, 11 20, 11 21, 10 21, 10 20))
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/FootprintWKT (ABCD v2.06b)
+
+
+
+ Formation
+ The full name of the lithostratigraphic formation from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Formation
+ The full name of the lithostratigraphic formation from which the cataloged item was collected.
+ Examples: "Notch Peak Fromation", "House Limestone", "Fillmore Formation"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Fossil Specimen
+ A resource describing a fossilized specimen.
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+ superseded
+ RecordBasisEnum/FossileSpecimen
+
+
+ Fossil Specimen
+ A resource describing a fossilized specimen.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ deprecated
+
+ RecordBasisEnum/FossileSpecimen
+
+
+ Fossil Specimen
+ A preserved specimen that is a fossil.
+
+ 2014-10-23
+ 2014-10-23
+
+
+
+ recommended
+
+ RecordBasisEnum/FossileSpecimen
+
+
+ Gen Bank Num
+ GenBank Accession number.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Sequences/Sequence/ID-in-Database + constant
+
+
+ Gen Bank Number
+ GenBank Accession number(s) associated with the biological individual(s) referred to by the cataloged object.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Sequences/Sequence/ID-in-Database + constant
+
+
+ Generalizations
+ Actions taken to make the data as shared less specific or complete than in its original form. Suggests that alternative data of highly quality may be available on request.
+ Examples: "Coordinates generalized from original GPS coordinates to the nearest half degree grid cell", "locality information given only to nearest county".
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ not in ABCD
+
+
+
+ Genus
+ The genus name of the organism
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
+
+
+ Genus
+ The phylogenetic genus to which the cataloged item belongs.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
+
+
+ Genus
+ The name of the genus in which the organism is classified.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
+
+
+ Genus
+ The name of the genus in which the scientificName is classified.
+ Example: "Quercus"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
+
+
+
+ Genus
+ The full scientific name of the genus in which the taxon is classified.
+ Examples: "Puma", "Monoclea"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
+
+
+
+ Geodetic Datum
+ The geodetic datum to which the latitude and longitude refer. If not known, use "not recorded". This concept should be vocabulary-controlled. Example: "WGS84"
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/SpatialDatum
+
+
+ Geodetic Datum
+ The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which the geographic coordinates given in decimalLatitude and decimalLongitude as based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".
+ Examples: "EPSG:4326", "WGS84", "NAD27", "Campo Inchauspe", "European 1950", "Clarke 1866"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/SpatialDatum
+
+
+
+ Geological Context
+ The category of information pertaining to a location within a geological context, such as stratigraphy.
+
+ 2009-07-06
+ 2014-10-23
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/Gathering/Stratigraphy
+
+
+ Geological Context
+ Geological information, such as stratigraphy, that qualifies a region or place.
+ Example: A lithostratigraphic layer.
+
+ 2009-07-06
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Gathering/Stratigraphy
+
+
+ Geological Context ID
+ An identifier for the set of information associated with a GeologicalContext (the location within a geological context, such as stratigraphy). May be a global unique identifier or an identifier specific to the data set.
+
+ 2009-07-06
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Georeferenced By
+ A list (concatenated and separated) of names of people, groups, or organizations who determined the georeference (spatial representation) for the Location.
+ Examples: "Kristina Yamamoto (MVZ); Janet Fang (MVZ)", "Brad Millen (ROM)"
+
+ 2009-01-21
+ 2014-10-23
+
+
+
+ superseded
+
+ not in ABCD
+
+
+
+ Georeferenced By
+ A list (concatenated and separated) of names of people, groups, or organizations who determined the georeference (spatial representation) for the Location.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Brad Millen (ROM)", "Kristina Yamamoto (MVZ) | Janet Fang (MVZ)".
+
+ 2009-01-21
+ 2014-10-23
+
+
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Georeferenced Date
+ The date on which the Location was georeferenced. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "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.
+
+ 2011-10-16
+ 2011-10-16
+
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Georeference Protocol
+ A reference to the methods used for determining the coordinates and uncertainties. Example: "http://manisnet.org/GeorefGuide.html".
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinateMethod
+
+
+ Georeference Protocol
+ A description or reference to the methods used to determine the spatial footprint, coordinates, and uncertainties.
+ Examples: "Guide to Best Practices for Georeferencing. (Chapman and Wieczorek, eds. 2006). Global Biodiversity Information Facility.", "MaNIS/HerpNet/ORNIS Georeferencing Guidelines", "Georeferencing Quick Reference Guide"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinateMethod
+
+
+
+ Georeference Remarks
+ Comments about the spatial description determination, explaining assumptions made in addition or opposition to the those formalized in the method referred to in GeoreferenceProtocol.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceRemarks
+
+
+ Georeference Remarks
+ Notes or comments about the spatial description determination, explaining assumptions made in addition or opposition to the those formalized in the method referred to in georeferenceProtocol.
+ Example: "assumed distance by road (Hwy. 101)"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceRemarks
+
+
+
+ Georeference Sources
+ A list of maps, gazetteers or other resources used to georeference the locality. The content of this concept is meant to be specific enough to allow anyone in the future to use the same resource to georeference the same locality. Examples: "USGS 1:24000 Florence Montana Quad", "Terrametrics 2008 on Google Earth"
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceSources
+
+
+ Georeference Sources
+ A list (concatenated and separated) of maps, gazetteers, or other resources used to georeference the Location, described specifically enough to allow anyone in the future to use the same resources.
+ Examples: "USGS 1:24000 Florence Montana Quad; Terrametrics 2008 on Google Earth"
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceSources
+
+
+
+ Georeference Sources
+ A list (concatenated and separated) of maps, gazetteers, or other resources used to georeference the Location, described specifically enough to allow anyone in the future to use the same resources.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "GeoLocate", "USGS 1:24000 Florence Montana Quad | Terrametrics 2008 on Google Earth".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceSources
+
+
+
+ Georeference Verification Status
+ A categorical description of the extent to which the georeference has been verified to represent the location where the specimen or observation was collected. This element should be vocabulary-controlled. Examples: "requires verification", "verified by collector", "verified by curator".
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceVerificationStatus
+
+
+ Georeference Verification Status
+ A categorical description of the extent to which the georeference has been verified to represent the best possible spatial description. Recommended best practice is to use a controlled vocabulary.
+ Examples: "requires verification", "verified by collector", "verified by curator".
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceVerificationStatus
+
+
+
+ Georef Method
+ A reference to the methods used for determining the coordinates and uncertainties.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinateMethod
+
+
+ Global Unique Identifier
+ A Uniform Resource Name (URN) as a unique identifier for the specimen or observation record. In the absence of a persistent global unique identifier, construct one in the form: “[InstitutionCode]:[CollectionCode]: [CatalogNumber]” Examples: 1) urn:lsid:nhm.ku.edu:Herps:32 2) “FMNH:Mammal:145732”
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/UnitGUID
+
+
+ GML Feature
+ Geographic Markup Language(GML) description of the feature for representing complex shapes such as lines and polygons, per Open GIS Consortium (OGC) standards - http://www.opengis.net/gml/01-029/GML2.html.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/GML
+
+
+ Group
+ The full name of the lithostratigraphic group from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Group
+ The full name of the lithostratigraphic group from which the cataloged item was collected.
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Habitat
+ A category or description of the habitat in which the Event occurred.
+ Examples: "oak savanna", "pre-cordilleran steppe"
+
+ 2008-11-19
+ 2009-05-17
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Biotope/Text
+
+
+
+ Higher Classification
+ A list (concatenated and separated) of taxa names terminating at the rank immediately superior to the taxon referenced in the taxon record. Recommended best practice is to order the list starting with the highest rank and separating the names for each rank with a semi-colon (";").
+ Example: "Animalia;Chordata;Vertebrata;Mammalia;Theria;Eutheria;Rodentia;Hystricognatha;Hystricognathi;Ctenomyidae;Ctenomyini;Ctenomys"
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ superseded
+
+ not in ABCD
+
+
+
+ Higher Classification
+ A list (concatenated and separated) of taxa names terminating at the rank immediately superior to the taxon referenced in the taxon record.
+ The recommended best practice is to separate the values with a vertical bar (' | '), with terms in order from the highest taxonomic rank to the lowest. Examples: "Animalia", "Animalia | Chordata | Vertebrata | Mammalia | Theria | Eutheria | Rodentia | Hystricognatha | Hystricognathi | Ctenomyidae | Ctenomyini | Ctenomys".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Higher Geography
+ The combination of all geographic elements less specific than locality. "Like" query operations on this element will search for a substring in any of the higher geography attributes.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Gathering/LocalityText or DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName}
+
+
+ Higher Geography
+ The names (concatenated and separated) of geographic elements less specific than the information in the Locality element. "LIKE" or "contains" substring query operations are meant to be used with this element to find matching geographic names. This can be useful if it is unclear in which element a name might be found, and in cases where there is no other appropriate geographic element. Example: "South America, Argentina, Patagonia, Parque Nacional Nahuel Huapi, Neuquén, Los Lagos" with accompanying values "South America" in Continent, "Argentina" in Country, "Neuquén" in StateProvince, and Los Lagos in County.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Gathering/LocalityText or DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName}
+
+
+ Higher Geography
+ A list (concatenated and separated) of geographic names less specific than the information captured in the locality term.
+ Example: "South America; Argentina; Patagonia; Parque Nacional Nahuel Huapi; Neuquén; Los Lagos" with accompanying values "South America" in Continent, "Argentina" in Country, "Neuquén" in StateProvince, and Los Lagos in County.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ superseded
+
+ {DataSets/DataSet/Units/Unit/Gathering/LocalityText or DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName}
+
+
+
+ Higher Geography
+ A list (concatenated and separated) of geographic names less specific than the information captured in the locality term.
+ The recommended best practice is to separate the values with a vertical bar (' | '), with terms in order from least specific to most specific. Examples: "North Atlantic Ocean", "South America | Argentina | Patagonia | Parque Nacional Nahuel Huapi | Neuquén | Los Lagos" with accompanying values "South America" in Continent, "Argentina" in Country, "Neuquén" in StateProvince, and "Los Lagos" in County.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ {DataSets/DataSet/Units/Unit/Gathering/LocalityText or DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName}
+
+
+
+ Higher Geography ID
+ An identifier for the geographic region within which the Location occurred. Recommended best practice is to use an persistent identifier from a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
+ Example: "TGN: 1002002" for Prov. Tierra del Fuego, Argentina
+
+ 2009-01-21
+ 2009-04-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Higher Taxon
+ The combination of names of taxonomic ranks less specific than Genus. "Like" query operations on this element will search for a substring in any of the higher taxon attributes.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+
+
+ Higher Taxon
+ The names of taxonomic ranks less specific than SpecificEpithet concatenated and separated. "LIKE" or "contains" substring query operations are meant to be used with this element to find matching higher taxon names. This element may contain the list of scientific names of all of the supra-specific taxa in the classification used to identify (determine) the specimen or observation. Example: "Animalia, Chordata, Vertebrata, Mammalia, Theria, Eutheria, Rodentia, Hystricognatha, Hystricognathi, Ctenomyidae, Ctenomyini, Ctenomys".
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+
+
+ Higher Taxon
+ A list (concatenated and separated) of the names for the taxonomic ranks less specific than the ScientificName.
+ Example: "Animalia, Chordata, Vertebrata, Mammalia, Theria, Eutheria, Rodentia, Hystricognatha, Hystricognathi, Ctenomyidae, Ctenomyini, Ctenomys".
+
+ 2008-11-19
+ 2009-01-21
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+
+
+
+ Higher Taxon Concept ID
+ A unique identifier for the taxon concept less specific than that given in the taxonConceptID.
+
+ 2009-04-24
+ 2009-04-24
+
+
+
+ deprecated
+ not in ABCD
+
+
+
+ Higher Taxon ID
+ A global unique identifier for the parent to the taxon.
+
+ 2009-01-21
+ 2009-01-21
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Higher Taxon Name
+ A list (concatenated and separated) of the names for the taxonomic ranks less specific than that given in the scientificName.
+ Example: "Animalia; Chordata; Vertebrata; Mammalia; Theria; Eutheria; Rodentia; Hystricognatha; Hystricognathi; Ctenomyidae; Ctenomyini; Ctenomys"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+
+
+
+ Higher Taxon Name ID
+ A unique identifier for the name of the next higher rank than the scientificName in a taxonomic classification. See higherTaxonName.
+
+ 2009-01-21
+ 2009-04-24
+
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Highest Biostratigraphic Zone
+ The full name of the highest possible geological biostratigraphic zone of the stratigraphic horizon from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Highest Biostratigraphic Zone
+ The full name of the highest possible geological biostratigraphic zone of the stratigraphic horizon from which the cataloged item was collected.
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Horizontal Datum
+ The horizontal geodetic datum to which the DecimalLatitude and DecimalLongitude refer.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/SpatialDatum
+
+
+ Human Observation
+ A resource describing an observation made by one or more people.
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+ superseded
+ RecordBasisEnum/HumanObservation
+
+
+ Human Observation
+ A resource describing an observation made by one or more people.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ deprecated
+
+ RecordBasisEnum/HumanObservation
+
+
+ Human Observation
+ An output of a human observation process.
+
+ 2014-10-23
+ 2014-10-23
+
+
+
+ recommended
+
+ RecordBasisEnum/HumanObservation
+
+
+ Identification
+ The category of information pertaining to taxonomic determinations (the assignment of a scientific name).
+
+ 2008-11-19
+ 2014-10-23
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/Identifications/Identification
+
+
+ Identification
+ A taxonomic determination (e.g., the assignment to a taxon).
+ Example: A subspecies determination of an organism.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Identifications/Identification
+
+
+ Identification Attributes
+ A list (concatenated and separated) of additional measurements, facts, characteristics, or assertions about the Identification.
+ Example: "natureOfID=expert identification; identificationEvidence=cytochrome B sequence"
+
+ 2009-04-24
+ 2009-04-24
+
+
+ deprecated
+ not in ABCD
+
+
+
+ Identification ID
+ An identifier for the Identification (the body of information associated with the assignment of a scientific name). May be a global unique identifier or an identifier specific to the data set.
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Identification Modifier
+ Additional information documenting the taxonomic determination of the cataloged item (e.g., "cf.", "aff.", "subspecies in question", etc.).
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/IdentificationQualifier
+
+
+ Identification Qualifier
+ A brief phrase or a standard term ("cf.", "aff.") to qualify the identification of the organism when doubts have arisen as to its taxonomic identity (determination). Examples: 1) For the determination "Quercus aff. agrifolia var. oxyadenia", IdentificationQualifier would be "aff. agrifolia var. oxyadenia" with accompanying values "Quercus" in Genus, "agrifolia" in SpecificEpithet, "oxyadenia" in InfraspecificEpithet, and "var." in InfraspecificRank. 2) For the determination "Quercus agrifolia cf. var. oxyadenia", IdentificationQualifier would be "cf. var. oxyadenia " with accompanying values "Quercus" in Genus, "agrifolia" in SpecificEpithet, "oxyadenia" in InfraspecificEpithet, and "var." in InfraspecificRank.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/IdentificationQualifier
+
+
+ Identification Qualifier
+ A brief phrase or a standard term ("cf.", "aff.") to express the determiner's doubts about the Identification.
+ Examples: 1) For the determination "Quercus aff. agrifolia var. oxyadenia", identificationQualifier would be "aff. agrifolia var. oxyadenia" with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank. 2) For the determination "Quercus agrifolia cf. var. oxyadenia", identificationQualifier would be "cf. var. oxyadenia " with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank.
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/IdentificationQualifier
+
+
+
+ Identification References
+ A list (concatenated and separated) of references (publication, global unique identifier, URI) used in the Identification.
+ Example: "Aves del Noroeste Patagonico. Christie et al. 2004."
+
+ 2008-11-19
+ 2014-10-23
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/Identifications/Identification/References
+
+
+
+ Identification References
+ A list (concatenated and separated) of references (publication, global unique identifier, URI) used in the Identification.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Aves del Noroeste Patagonico. Christie et al. 2004.", "Stebbins, R. Field Guide to Western Reptiles and Amphibians. 3rd Edition. 2003. | Irschick, D.J. and Shaffer, H.B. (1997). ''The polytypic species revisited: Morphological differentiation among tiger salamanders (Ambystoma tigrinum) (Amphibia: Caudata).'' Herpetologica, 53(1), 30-49.".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Identifications/Identification/References
+
+
+
+ Identification Remarks
+ Comments or notes about the Identification.
+ Example: "Distinguished between Anthus correndera and Anthus hellmayri based on the comparative lengths of the uñas."
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Notes
+
+
+
+ Identification Verification Status
+ A categorical indicator of the extent to which the taxonomic identification has been verified to be correct. Recommended best practice is to use a controlled vocabulary such as that used in HISPID/ABCD.
+ Examples: "0", "4"
+
+ 2011-10-16
+ 2011-10-16
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Identified By
+ The name(s) of the person(s) who applied the currently accepted Scientific Name to the Cataloged Item.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Identifiers/IdentifiersText
+
+
+ Identified By
+ The name(s) of the person(s) who applied the currently accepted ScientificName to the cataloged item.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Identifiers/IdentifiersText
+
+
+ Identified By
+ The name(s) of the person(s) who applied the ScientificName to the object or observation. Example: James L. Patton.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Identifiers/IdentifiersText
+
+
+ Identified By
+ A list (concatenated and separated) of names of people, groups, or organizations who assigned the scientificName.
+ Example: "James L. Patton", "Theodore Pappenfuss; Robert Macey"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Identifiers/IdentifiersText
+
+
+
+ Identified By
+ A list (concatenated and separated) of names of people, groups, or organizations who assigned the Taxon to the subject.
+ Examples: "James L. Patton", "Theodore Pappenfuss; Robert Macey"
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Identifiers/IdentifiersText
+
+
+
+ Identified By
+ A list (concatenated and separated) of names of people, groups, or organizations who assigned the Taxon to the subject.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "James L. Patton", "Theodore Pappenfuss | Robert Macey".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Identifiers/IdentifiersText
+
+
+
+ Image URL
+ A Universal Resource Locator reference to digital images associated with the specimen or observation.
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/MultimediaObjects
+
+
+ Individual Count
+ The number of individuals present in the lot or container. Not an estimate of abundance or density at the collecting locality.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue
+
+
+ Individual Count
+ The number of individuals present in the lot or container referred to by the catalog number. Not an estimate of abundance or density at the collecting locality.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue
+
+
+ Individual Count
+ The number of individuals present in the lot or container. Not to be used for observations.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue
+
+
+ Individual Count
+ The number of individuals represented present at the time of the Occurrence.
+ Examples: "1", "25"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue
+
+
+
+ Individual ID
+ An identifier for an individual or named group of individual organisms represented in the Occurrence. Meant to accommodate resampling of the same individual or group for monitoring purposes. May be a global unique identifier or an identifier specific to a data set.
+ Examples: "U.amer. 44", "Smedley", "Orca J 23"
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ deprecated
+
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/NameAtomised/Zoological/NamedIndividual or DataSets/DataSet/Units/Unit/ObservationUnit/ObservationUnitIdentifiers/ObservationUnitIdentifier or DataSets/DataSet/Units/Unit/SpecimenUnit/Accessions/AccessionNumber
+
+
+
+ Information Withheld
+ Brief descriptions of additional information that may exist, but that has not been made public. Information about obtaining the withheld information should be sought from the administrative contact identified in the provider resource metadata (curator, collection manager). Examples: "specific locality information given only to nearest county", "ask about tissue samples", "georeferences given only to nearest degree".
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/InformationWithheld
+
+
+ Information Withheld
+ Additional information that exists, but that has not been shared in the given record.
+ Examples: "location information not given for endangered species", "collector identities withheld", "ask about tissue samples"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/InformationWithheld
+
+
+
+ Infraspecific Epithet
+ The infraspecific epithet of the scientific name applied to the organism.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
+
+
+ Infraspecific Epithet
+ The name of the second or subspecies epithet of the scientificName.
+ Example: "oxyadenia"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
+
+
+
+ Infraspecific Epithet
+ The name of the lowest or terminal infraspecific epithet of the scientificName, excluding any rank designation.
+ Examples: "concolor", "oxyadenia", "sayi"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
+
+
+
+ Infraspecific Rank
+ The infraspecific rank (subspecies, variety, forma) of the InfraspecificEpithet. Examples: "subsp.", "var.", "forma".
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Rank
+
+
+ Institution Code
+ A "standard" code identifier that identifies the institution to which the collection belongs. No global registry exists for assigning institutional codes. Use the code that is "standard" in your discipline.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SourceInstitutionID
+
+
+ Institution Code
+ A code that identifies the institution to which the cataloged item belongs. No global registry exists for institutional codes; use the code that is "standard" in your discipline. This attribute must contain no spaces.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SourceInstitutionID
+
+
+ Institution Code
+ The code (or acronym) identifying the institution administering the collection in which the organism record is cataloged. No global registry exists for institutional codes; use the code that is "standard" at your institution or in your discipline.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SourceInstitutionID
+
+
+ Institution Code
+ The name (or acronym) in use by the institution having custody of the object(s) or information referred to in the record.
+ Examples: "MVZ", "FMNH", "AKN-CLO"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SourceInstitutionID
+
+
+
+ Institution Code
+ The name (or acronym) in use by the institution having custody of the object(s) or information referred to in the record.
+ Examples: "MVZ", "FMNH", "AKN-CLO", "University of California Museum of Paleontology (UCMP)"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SourceInstitutionID
+
+
+
+ Institution Code
+ The name (or acronym) in use by the institution having custody of the object(s) or information referred to in the record.
+ Examples: "MVZ", "FMNH", "AKN-CLO", "University of California Museum of Paleontology (UCMP)"
+
+ 2008-11-19
+ 2013-10-04
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/SourceInstitutionID
+
+
+
+ Institution ID
+ An identifier for the institution having custody of the object(s) or information referred to in the record.
+ For physical specimens, the recommended best practice is to use an identifier from a collections registry such as the Global Registry of Biodiversity Repositories (http://grbio.org/). Examples: "http://biocol.org/urn:lsid:biocol.org:col:34777", "http://grbio.org/cool/km06-gtbn".
+
+ 2009-09-11
+ 2014-10-23
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/SourceInstitutionID
+
+
+
+ Island
+ The full, unabbreviated name of the island from which the cataloged item was collected.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island
+
+
+ Island
+ The full, unabbreviated name of the island on which the organism was collected or observed.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island
+
+
+ Island
+ The name of the island on or near which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
+ Examples: "Isla Victoria", "Vancouver", "Viti Levu", "Zanzibar"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island
+
+
+
+ Island Group
+ The full, unabbreviated name of the island group from which the cataloged item was collected.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island group
+
+
+ Island Group
+ The full, unabbreviated name of the island group in which the organism was collected or observed.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island group
+
+
+ Island Group
+ The name of the island group in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
+ Examples: "Alexander Archipelago", "Seychelles"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island group
+
+
+
+ Julian Day
+ The ordinal day of the year; i.e., the number of days since January 1 of the same year. (January 1 is Julian Day 1.)
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberBegin
+
+
+ Julian Day
+ The ordinal day of the year (i.e., the number of days since December 31 of the previous year; January 1 is Julian Day 1) on which the cataloged item was collected. May be derived from the YearCollected, MonthCollected, and DayCollected by the provider.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberBegin
+
+
+ Kingdom
+ The kingdom to which the organism belongs
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
+
+
+ Kingdom
+ The phylogenetic kingdom to which the cataloged item belongs.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
+
+
+ Kingdom
+ The name of the kingdom in which the organism is classified.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
+
+
+ Kingdom
+ The name of the kingdom in which the scientificName is classified.
+ Example: "Animalia"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
+
+
+
+ Kingdom
+ The full scientific name of the kingdom in which the taxon is classified.
+ Examples: "Animalia", "Plantae"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
+
+
+
+ Latest AgeOr Highest Stage
+ The full name of the latest possible geochronologic age or highest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Latest AgeOr Highest Stage
+ The full name of the latest possible geochronologic age or highest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Atlantic", "Boreal", "Skullrockian"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Latest Date Collected
+ The latest date-time (Common Era calendar) in a date-time period during which an organism or group of organisms was collected or observed. If the event is recorded as occurring at a single date-time, populate both EarliestDateCollected and LatestDateCollected with the same value.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
+
+
+ Latest Date Collected
+ The latest date-time in a period during which a event occurred. If the event is recorded as occurring at a single date-time, populate both EarliestDateCollected and LatestDateCollected with the same value. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
+
+
+
+ Latest Eon Or Highest Eonothem
+ The full name of the latest possible geochronologic eon or highest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Latest Eon Or Highest Eonothem
+ The full name of the latest possible geochronologic eon or highest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Phanerozoic", "Proterozoic"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Latest Epoch Or Highest Series
+ The full name of the latest possible geochronologic epoch or highest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Latest Epoch Or Highest Series
+ The full name of the latest possible geochronologic epoch or highest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Holocene", "Pleistocene", "Ibexian Series"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Latest Era Or Highest Erathem
+ The full name of the latest possible geochronologic era or highest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Latest Era Or Highest Erathem
+ The full name of the latest possible geochronologic era or highest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Cenozoic", "Mesozoic"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Latest Period Or Highest System
+ The full name of the latest possible geochronologic period or highest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Latest Period Or Highest System
+ The full name of the latest possible geochronologic period or highest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
+ Examples: "Neogene", "Tertiary", "Quaternary"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Latitude
+ The latitude of the location from which the specimen was collected. This value should be expressed in decimal degrees with a datum such as WGS-84
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal
+
+
+ Lat Long Comments
+ Comments about the LatLong determination.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceRemarks
+
+
+ Lifestage
+ Indicates the life stage present. Will require developing a controlled vocabulary. Can include multiple stages for a lot with multiple individuals.
+
+ 2005-07-10
+ 2005-07-10
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLiveStages/MycologicalLiveStage (Note DwC spec uses ”MycologicalLifeStage” or DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage
+
+
+ Life Stage
+ The age class or life stage of the biological individual represented by the catalogued object or observation. Examples: "adult", "mature", "juvenile", "eft", "nymph", "seedling", "seed", "egg"
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLiveStages/MycologicalLiveStage (Note DwC spec uses ”MycologicalLifeStage” or DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage
+
+
+ Life Stage
+ The age class or life stage of the biological individual(s) at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.
+ Examples: "egg", "eft", "juvenile", "adult", "2 adults 4 juveniles"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLiveStages/MycologicalLiveStage (Note DwC spec uses ”MycologicalLifeStage” or DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage
+
+
+
+ Lithostratigraphic Terms
+ The combination of all litho-stratigraphic names for the rock from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Stratigraphy/LithostratigraphicTerms
+
+
+
+ Lithostratigraphic Terms
+ The combination of all litho-stratigraphic names for the rock from which the cataloged item was collected.
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Stratigraphy/LithostratigraphicTerms
+
+
+
+ Living Specimen
+ A resource describing a living specimen.
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+ superseded
+ RecordBasisEnum/LivingSpecimen
+
+
+ Living Specimen
+ A resource describing a living specimen.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ deprecated
+
+ RecordBasisEnum/LivingSpecimen
+
+
+ Living Specimen
+ A specimen that is alive.
+
+ 2014-10-23
+ 2014-10-23
+
+
+
+ recommended
+
+ RecordBasisEnum/LivingSpecimen
+
+
+ Locality
+ The locality description (place name plus optionally a displacement from the place name) from which the specimen was collected. Where a displacement from a location is provided, it should be in un-projected units of measurement
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/AreaDetail
+
+
+ Locality
+ The description of the locality from which the cataloged item was collected, sans geographic information provided in other geographic fields.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/AreaDetail
+
+
+ Locality
+ The specific natural language description of the place where the organism was collected or observed. This element need not contain less specific geographic information provided in other geographic elements (HigherGeography, Continent, Country, StateProvince, County, WaterBody, Island, IslandGroup). Though coordinate information can be contained in this concept, these data will be usable analytically only when shared through the concepts of the Geospatial Extension.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/AreaDetail
+
+
+ Locality
+ The specific description of the place. Less specific geographic information can be provided in other geographic terms (higherGeography, continent, country, stateProvince, county, municipality, waterBody, island, islandGroup). This term may contain information modified from the original to correct perceived errors or standardize the description.
+ Example: "Bariloche, 25 km NNE via Ruta Nacional 40 (=Ruta 237)"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
+
+
+
+ Location
+ A resource describing an instance of the Location class.
+
+ 2009-01-23
+ 2014-10-23
+
+
+ deprecated
+
+ not in ABCD
+
+
+ Location According To
+ Information about the source of this Location information. Could be a publication (gazetteer), institution, or team of individuals.
+ Examples: "Getty Thesaurus of Geographic Names", "GADM"
+
+ 2009-08-24
+ 2009-08-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Location Attributes
+ A list (concatenated and separated) of additional measurements, facts, characteristics, or assertions about the location.
+ Example: "aspectheading=277; slopeindegrees=6"
+
+ 2009-04-24
+ 2009-04-24
+
+
+ deprecated
+ not in ABCD
+
+
+
+ Location ID
+ An identifier for the set of location information (data associated with dcterms:Location). May be a global unique identifier or an identifier specific to the data set.
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Location Remarks
+ Comments or notes about the Location.
+ Example: "under water since 2005"
+
+ 2009-01-18
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/AreaDetail
+
+
+
+ Longitude
+ The longitude of the location from which the specimen was collected. This value should be expressed in decimal degrees with a datum such as WGS-84
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal
+
+
+ Lowest Biostratigraphic Zone
+ The full name of the lowest possible geological biostratigraphic zone of the stratigraphic horizon from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Lowest Biostratigraphic Zone
+ The full name of the lowest possible geological biostratigraphic zone of the stratigraphic horizon from which the cataloged item was collected.
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Machine Observation
+ A resource describing an observation made by a machine.
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+ superseded
+ RecordBasisEnum/MachineObservation
+
+
+ Machine Observation
+ A resource describing an observation made by a machine.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ deprecated
+
+ RecordBasisEnum/MachineObservation
+
+
+ Machine Observation
+ An output of a machine observation process.
+
+ 2014-10-23
+ 2014-10-23
+
+
+
+ recommended
+
+ RecordBasisEnum/MachineObservation
+
+
+ Material Sample
+ The category of information pertaining to the physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.
+
+ 2013-03-28
+ 2014-10-23
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit
+
+
+ Material Sample
+ A resource describing the physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.
+
+ 2013-03-28
+ 2014-10-23
+
+
+
+ deprecated
+
+ DataSets/DataSet/Units/Unit
+
+
+ Material Sample
+ A physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.
+ Examples: A whole organism preserved in a collection. A part of an organism isolated for some purpose. A soil sample. A marine microbial sample.
+
+ 2013-03-28
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit
+
+
+ Material Sample ID
+ An identifier for the MaterialSample (as opposed to a particular digital record of the material sample). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the materialSampleID globally unique.
+
+ 2013-03-28
+ 2013-09-26
+
+
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Maximum Depth
+ The maximum distance in meters below the surface of the water at which the collection was made; all material collected was at most this deep. Positive below the surface, negative above (e.g. collecting above sea level in tidal areas).
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue
+
+
+ Maximum Depth In Meters
+ The maximum distance in meters below the surface of the water at which the collection was made; all material collected was at most this deep. Positive below the surface, negative above (e.g., collecting above sea level in tidal areas).
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue
+
+
+ Maximum Depth In Meters
+ The maximum or actual depth at which the collection or observation was made. Use positive values for locations below the surface. Examples: 10 (for a depth of up to 10m). 100 (for a depth between 50m and 100m).
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue
+
+
+ Maximum Depth In Meters
+ The greater depth of a range of depth below the local surface, in meters.
+ Example: "200"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue
+
+
+
+ Maximum Distance Above Surface In Meters
+ The greater distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.
+ Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
+
+
+
+ Maximum Elevation
+ The maximum distance in meters above (positive) or below sea level of the collecting locality.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue
+
+
+ Maximum Elevation In Meters
+ The maximum distance in meters above (positive) or below sea level of the collecting locality.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue
+
+
+ Maximum Elevation In Meters
+ The maximum or actual elevation at which the collection or observation was made. Use negative values for locations below sea level. Examples: Examples: 125 (for an elevation of 100 +- 25 meters). 200 (for an elevation between 100m and 200m).
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue
+
+
+ Maximum Elevation In Meters
+ The upper limit of the range of elevation (altitude, usually above sea level), in meters.
+ Example: "200"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue
+
+
+
+ Measurement Accuracy
+ The description of the potential error associated with the measurementValue.
+ Examples: "0.01", "normal distribution with variation of 2 m"
+
+ 2009-01-18
+ 2009-04-24
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
+
+
+
+ Measurement Determined By
+ A list (concatenated and separated) of names of people, groups, or organizations who determined the value of the MeasurementOrFact.
+ Examples: "Javier de la Torre", "Julie Woodruff; Eileen Lacey"
+
+ 2009-01-23
+ 2014-10-23
+
+
+
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
+
+
+
+ Measurement Determined By
+ A list (concatenated and separated) of names of people, groups, or organizations who determined the value of the MeasurementOrFact.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Rob Guralnick", "Julie Woodruff | Eileen Lacey".
+
+ 2009-01-23
+ 2014-10-23
+
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
+
+
+
+ Measurement Determined Date
+ The date on which the MeasurementOrFact was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "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.
+
+ 2009-01-23
+ 2009-04-24
+
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
+
+
+
+ Measurement ID
+ An identifier for the MeasurementOrFact (information pertaining to measurements, facts, characteristics, or assertions). May be a global unique identifier or an identifier specific to the data set.
+
+ 2009-03-06
+ 2009-04-24
+
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Measurement Method
+ A description of or reference to (publication, URI) the method or protocol used to determine the measurement, fact, characteristic, or assertion.
+ Examples: "minimum convex polygon around burrow entrances" for a home range area, "barometric altimeter" for an elevation
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ /DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Method or /DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Method or /DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Method
+
+
+
+ Measurement Or Fact
+ The category of information pertaining to measurements, facts, characteristics, or assertions about a resource (instance of data record, such as Occurrence, Taxon, Location, Event).
+
+ 2009-04-24
+ 2014-10-23
+
+
+
+
+ superseded
+
+ Datasets/Dataset/Units/Unit/MeasurementsOrFacts or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts
+
+
+ Measurement or Fact
+ A measurement of or fact about an rdfs:Resource (http://www.w3.org/2000/01/rdf-schema#Resource).
+ Resources can be thought of as identifiable records or instances of classes and may include, but need not be limited to Occurrences, Organisms, MaterialSamples, Events, Locations, GeologicalContexts, Identifications, or Taxa. Examples: The weight of an organism in grams. The number of placental scars.
+
+ 2009-04-24
+ 2014-10-23
+
+
+
+ recommended
+
+ Datasets/Dataset/Units/Unit/MeasurementsOrFacts or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts
+
+
+ Measurement Remarks
+ Comments or notes accompanying the MeasurementOrFact.
+ Example: "tip of tail missing"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Measurement Type
+ The nature of the measurement, fact, characteristic, or assertion. Recommended best practice is to use a controlled vocabulary.
+ Examples: "tail length", "temperature", "trap line length", "survey area", "trap type"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
+
+
+
+ Measurement Unit
+ The units associated with the measurementValue. Recommended best practice is to use the International System of Units (SI).
+ Examples: "mm", "C", "km", "ha"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
+
+
+
+ Measurement Value
+ The value of the measurement, fact, characteristic, or assertion.
+ Examples: "45", "20", "1", "14.5", "UV-light"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
+
+
+
+ Member
+ The full name of the lithostratigraphic member from which the cataloged item was collected.
+
+ 2005-07-03
+ 2005-07-03
+
+ superseded
+ not in ABCD
+
+
+
+ Member
+ The full name of the lithostratigraphic member from which the cataloged item was collected.
+ Examples: "Lava Dam Member", "Hellnmaria Member"
+
+ 2009-04-24
+ 2009-07-06
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Minimum Depth
+ The minimum distance in meters below the surface of the water at which the collection was made; all material collected was at least this deep. Positive below the surface, negative above (e.g. collecting above sea level in tidal areas).
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue
+
+
+ Minimum Depth In Meters
+ The minimum distance in meters below the surface of the water at which the collection was made; all material collected was at least this deep. Positive below the surface, negative above (e.g., collecting above sea level in tidal areas).
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue
+
+
+ Minimum Depth In Meters
+ The minimum or actual depth at which the collection or observation was made. Use positive values for locations below the surface. Examples: 0 (for a depth of up to 10m). 50 (for a depth between 50m and 100m).
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue
+
+
+ Minimum Depth In Meters
+ The lesser depth of a range of depth below the local surface, in meters.
+ Example: "100"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue
+
+
+
+ Minimum Distance Above Surface In Meters
+ The lesser distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.
+ Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue
+
+
+
+ Minimum Elevation
+ The minimum distance in meters above (positive) or below sea level of the collecting locality.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue
+
+
+ Minimum Elevation In Meters
+ The minimum distance in meters above (positive) or below sea level of the collecting locality.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue
+
+
+ Minimum Elevation In Meters
+ The minimum or actual elevation at which the collection or observation was made. Use negative values for locations below sea level. Examples: 75 (for an elevation of 100 +- 25 meters). 100 (for an elevation between 100m and 200m).
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue
+
+
+ Minimum Elevation In Meters
+ The lower limit of the range of elevation (altitude, usually above sea level), in meters.
+ Example: "100"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue
+
+
+
+ Month
+ The ordinal month in which the Event occurred.
+ Examples: "1" (=January), "10" (=October)
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+
+ Month Collected
+ The month of year the specimen was collected from the field. Possible values range from 01...12 inclusive
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+ Month Collected
+ The two digit month of year in the Common Era calendar during which the cataloged item was collected from the field.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+ Month Identified
+ The month portion of the date when the Collection Item was identified; as two digits [01..12].
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
+
+
+ Month Identified
+ The two digit month in the Common Era calendar during which the cataloged item was identified.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
+
+
+ Municipality
+ The full, unabbreviated name of the next smaller administrative region than county (city, municipality, etc.) in which the Location occurs. Do not use this term for a nearby named place that does not contain the actual location.
+ Examples: "Holzminden"
+
+ 2008-11-19
+ 2009-08-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
+
+
+
+ Name According To
+ The reference to the source in which the specific taxon concept circumscription is defined or implied - traditionally signified by the Latin "sensu" or "sec." (from secundum, meaning "according to"). For taxa that result from identifications, a reference to the keys, monographs, experts and other sources should be given.
+ Example: "McCranie, J. R., D. B. Wake, and L. D. Wilson. 1996. The taxonomic status of Bolitoglossa schmidti, with comments on the biology of the Mesoamerican salamander Bolitoglossa dofleini (Caudata: Plethodontidae). Carib. J. Sci. 32:395-398.", "Werner Greuter 2008", "Lilljeborg 1861, Upsala Univ. Arsskrift, Math. Naturvet., pp. 4, 5"
+
+ 2008-11-19
+ 2009-09-21
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Name According To ID
+ An identifier for the source in which the specific taxon concept circumscription is defined or implied. See nameAccordingTo.
+ Example: "doi:10.1016/S0269-915X(97)80026-2"
+
+ 2009-08-24
+ 2009-09-21
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Name Publication ID
+ A resolvable globally unique identifier for the original publication of the scientificName.
+ Example: "http://hdl.handle.net/10199/7"
+
+ 2009-05-18
+ 2009-05-18
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Name Published In
+ A full reference to the original publication of the scientificName.
+ Examples: "Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "Forel, Auguste, Diagnosies provisoires de quelques espèces nouvelles de fourmis de Madagascar, récoltées par M. Grandidier., Annales de la Societe Entomologique de Belgique, Comptes-rendus des Seances 30, 1886"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference/TitleCitation
+
+
+
+ Name Published In
+ A reference for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.
+ Examples: "Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "Forel, Auguste, Diagnosies provisoires de quelques espèces nouvelles de fourmis de Madagascar, récoltées par M. Grandidier., Annales de la Societe Entomologique de Belgique, Comptes-rendus des Seances 30, 1886"
+
+ 2008-11-19
+ 2009-09-21
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference/TitleCitation
+
+
+
+ Name Published In ID
+ An identifier for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.
+ Example: "http://hdl.handle.net/10199/7"
+
+ 2009-05-18
+ 2009-09-21
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Name Published In Year
+ The four-digit year in which the scientificName was published.
+ Examples: "1915", "2008"
+
+ 2011-10-16
+ 2011-10-16
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Nomenclatural Checklist
+ A resource describing a nomenclatural checklist.
+
+ 2009-01-23
+ 2014-10-23
+
+
+ deprecated
+
+ not in ABCD
+
+
+ Nomenclatural Code
+ The nomenclatural code under which the ScientificName is constructed. Examples: "ICBN", "ICZN", "BC", "ICNCP", "BioCode"
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/Code
+
+
+ Nomenclatural Code
+ The nomenclatural code under which the scientificName is constructed. Recommended best practice is to use a controlled vocabulary.
+ Examples: "ICBN", "ICZN", "BC", "ICNCP", "BioCode"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/Code
+
+
+
+ Nomenclatural Code
+ The nomenclatural code (or codes in the case of an ambiregnal name) under which the scientificName is constructed. Recommended best practice is to use a controlled vocabulary.
+ Examples: "ICBN", "ICZN", "BC", "ICNCP", "BioCode", "ICZN; ICBN"
+
+ 2008-11-19
+ 2009-09-21
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/Code
+
+
+
+ Nomenclatural Status
+ The status related to the original publication of the name and its conformance to the relevant rules of nomenclature. It is based essentially on an algorithm according to the business rules of the code. It requires no taxonomic opinion.
+ Examples: "nom. ambig.", "nom. illeg.", "nom. subnud."
+
+ 2009-01-18
+ 2009-04-24
+
+
+ recommended
+ (DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference/TitleCitation) pro parte
+
+
+
+ Notes
+ Free text notes attached to the specimen record
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Notes
+
+
+ Observed Individual Count
+ The number of individuals (abundance) found in a collection/record event.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue + constant
+
+
+ Observed Weight
+ The total biomass found in a collection/record event. Expressed as kg.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue + constant
+
+
+ Occurrence
+ A resource describing an instance of the Occurrence class.
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+ superseded
+ not in ABCD
+
+
+ Occurrence
+ The category of information pertaining to evidence of an occurrence in nature, in a collection, or in a dataset (specimen, observation, etc.).
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit
+
+
+ Occurrence
+ A resource describing an instance of the Occurrence class.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ deprecated
+
+ not in ABCD
+
+
+ Occurrence
+ An existence of an Organism (sensu http://rs.tdwg.org/dwc/terms/Organism) at a particular place at a particular time.
+ Examples: A wolf pack on the shore of Kluane Lake in 1988. A virus in a plant leaf in a the New York Botanical Garden at 15:29 on 2014-10-23. A fungus in Central Park in the summer of 1929.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit
+
+
+ Occurrence Attributes
+ A list (concatenated and separated) of additional measurements, facts, characteristics, or assertions about the Occurrence.
+ Examples: "Tragus length: 14mm; Weight: 120g", "Height: 1-1.5 meters tall; flowers yellow; uncommon".
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts
+
+
+
+ Occurrence Details
+ A reference (publication, URI) to the most detailed information available about the Occurrence.
+ Example: "http://mvzarctos.berkeley.edu/guid/MVZ:Mamm:165861"
+
+ 2008-11-19
+ 2011-10-16
+
+
+
+ deprecated
+
+ DataSets/DataSet/Units/Unit/RecordURI
+
+
+
+ Occurrence ID
+ An identifier for the Occurrence (as opposed to a particular digital record of the occurrence). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the occurrenceID globally unique.
+ For a specimen in the absence of a bona fide global unique identifier, for example, use the form: "urn:catalog:[institutionCode]:[collectionCode]:[catalogNumber]. Examples: "urn:lsid:nhm.ku.edu:Herps:32", "urn:catalog:FMNH:Mammal:145732"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/UnitGUID
+
+
+
+ Occurrence Measurement
+ The category of information pertaining to measurements accociated with an occurrence.
+
+ 2008-11-19
+ 2009-04-24
+
+
+ superseded
+ Datasets/Dataset/Units/Unit/MeasurementsOrFacts
+
+
+
+ Occurrence Measurement Accuracy
+ The description of the error associated with the occurrenceAttributeValue.
+ Example: "0.01", "normal distribution with variation of 2 m"
+
+ 2009-01-18
+ 2009-04-24
+
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
+
+
+
+ Occurrence Measurement Determined By
+ The agent responsible for having determined the value of the measurement or characteristic of the occurrence.
+ Example: "Javier de la Torre"
+
+ 2009-01-23
+ 2009-04-24
+
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy
+
+
+
+ Occurrence Measurement Determined Date
+ The date on which the the measurement or characteristic of the occurrence was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "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.
+
+ 2009-01-23
+ 2009-04-24
+
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime
+
+
+
+ Occurrence Measurement ID
+ An identifier for the occurrence attribute. May be a global unique identifier or an identifier specific to the data set.
+
+ 2009-03-06
+ 2009-04-24
+
+
+
+
+ deprecated
+ not in ABCD
+
+
+
+ Occurrence Measurement Remarks
+ Comments or notes accompanying the measurement or characteristic of the occurrence.
+ Example: "tip of tail missing"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ deprecated
+ not in ABCD
+
+
+
+ Occurrence Measurement Type
+ The nature of the measurement or characteristic of the occurrence. Recommended best practice is to use a controlled vocabulary.
+ Example: "tail length"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
+
+
+
+ Occurrence Measurement Unit
+ The units for the value of the measurement or characteristic of the occurrence. Recommended best practice is to use International System of Units (SI) units.
+ Example: "mm"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
+
+
+
+ Occurrence Measurement Value
+ The value of the measurement or characteristic of the occurrence.
+ Example: "45"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue
+
+
+
+ Occurrence Remarks
+ Comments or notes about the Occurrence.
+ Example: "found dead on road"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Notes
+
+
+
+ Occurrence Status
+ A statement about the presence or absence of a Taxon at a Location. Recommended best practice is to use a controlled vocabulary.
+ Examples: "present", "absent"
+
+ 2009-09-17
+ 2009-09-17
+
+
+ recommended
+ not in ABCD
+
+
+
+ Order
+ The order name of the organism
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
+
+
+ Order
+ The phylogenetic order to which the cataloged item belongs.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
+
+
+ Order
+ The name of the order in which the organism is classified.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
+
+
+ Order
+ The name of the order in which the scientificName is classified.
+ Example: "Rodentia"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
+
+
+
+ Order
+ The full scientific name of the order in which the taxon is classified.
+ Examples: "Carnivora", "Monocleales"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
+
+
+
+ Organism
+ A particular organism or defined group of organisms considered to be taxonomically homogeneous.
+ Instances of the Organism class are intended to facilitate linking of one or more Identification instances to one or more Occurrence instances. Therefore, things that are typically assigned scientific names (such as viruses, hybrids, and lichens) and aggregates whose occurrences are typically recorded (such as packs, clones, and colonies) are included in the scope of this class.
+
+ 2014-10-23
+ 2014-10-23
+
+
+ recommended
+
+ not in ABCD
+
+
+ Organism ID
+ An identifier for the Organism instance (as opposed to a particular digital record of the Organism). May be a globally unique identifier or an identifier specific to the data set.
+
+ 2014-10-23
+ 2014-10-23
+
+
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Organism Name
+ A textual name or label assigned to an Organism instance.
+ Examples: "Huberta", "Boab Prison Tree", "J pod".
+
+ 2014-10-23
+ 2014-10-23
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Organism Remarks
+ Comments or notes about the Organism instance.
+ Example: "One of a litter of six."
+
+ 2014-10-23
+ 2014-10-23
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Organism Scope
+ A description of the kind of Organism instance. Can be used to indicate whether the Organism instance represents a discrete organism or if it represents a particular type of aggregation. Recommended best practice is to use a controlled vocabulary.
+ This term is not intended to be used to specify a type of taxon. To describe the kind of Organism using a URI object in RDF, use rdf:type (http://www.w3.org/1999/02/22-rdf-syntax-ns#type) instead. Examples: "multicellular organism", "virus", "clone" "pack", "colony".
+
+ 2014-10-23
+ 2014-10-23
+
+
+ recommended
+
+ not in ABCD
+
+
+
+ Original Coordinate System
+ The name of the system in which the original geographic coordinates were recorded (e.g., "decimal degrees", "degrees minutes seconds", "UTM", etc.).
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ (partly) DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesGrid/GridCellSystem
+
+
+ Original Name Usage
+ The taxon name, with authorship and date information if known, as it originally appeared when first established under the rules of the associated nomenclaturalCode. The basionym (botany) or basonym (bacteriology) of the scientificName or the senior/earlier homonym for replaced names.
+ Examples: "Pinus abies", "Gasterosteus saltatrix Linnaeus 1768"
+
+ 2008-11-19
+ 2009-09-21
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Original Name Usage ID
+ An identifier for the name usage (documented meaning of the name according to a source) in which the terminal element of the scientificName was originally established under the rules of the associated nomenclaturalCode.
+ Example: "http://species.gbif.org/abies_alba_1753"
+
+ 2009-01-21
+ 2009-09-21
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Other Catalog Numbers
+ A list of previous or alternative fully qualified catalog numbers of the cataloged item whether in the current collection or in any other.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SpecimenUnit/History/PreviousUnitsText
+
+
+ Other Catalog Numbers
+ A list of previous or alternative fully qualified catalog numbers for the same object or observation, whether in the current collection or in any other.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SpecimenUnit/History/PreviousUnitsText
+
+
+ Other Catalog Numbers
+ A list (concatenated and separated) of previous or alternate fully qualified catalog numbers or other human-used identifiers for the same Occurrence, whether in the current or any other data set or collection.
+ Examples: "FMNH:Mammal:1234", "NPS YELLO6778; MBG 33424"
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/SpecimenUnit/History/PreviousUnitsText
+
+
+
+ Other Catalog Numbers
+ A list (concatenated and separated) of previous or alternate fully qualified catalog numbers or other human-used identifiers for the same Occurrence, whether in the current or any other data set or collection.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "FMNH:Mammal:1234", "NPS YELLO6778 | MBG 33424".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/SpecimenUnit/History/PreviousUnitsText
+
+
+
+ Owner Institution Code
+ The name (or acronym) in use by the institution having ownership of the object(s) or information referred to in the record.
+ Examples: "NPS", "APN", "InBio"
+
+ 2009-08-24
+ 2013-10-04
+
+
+ recommended
+ not in ABCD
+
+
+
+ Parent Name Usage
+ The full name, with authorship and date information if known, of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.
+ Examples: "Rubiaceae", "Gruiformes", "Testudinae"
+
+ 2009-08-24
+ 2009-09-21
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+
+
+
+ Parent Name Usage ID
+ An identifier for the name usage (documented meaning of the name according to a source) of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.
+ Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"
+
+ 2009-01-21
+ 2009-09-21
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Phylum
+ The phylum (or division) to which the organism belongs
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
+
+
+ Phylum
+ The phylogenetic phylum (or division) to which the cataloged item belongs.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
+
+
+ Phylum
+ The name of the phylum (or division) in which the organism is classified.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
+
+
+ Phylum
+ The name of the phlyum (or division) in which the scientificName is classified.
+ Example: "Chordata"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
+
+
+
+ Phylum
+ The full scientific name of the phylum or division in which the taxon is classified.
+ Examples: "Chordata" (phylum), "Bryophyta" (division)
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
+
+
+
+ Point Radius Spatial Fit
+ A measure of how well the circle defined by the coordinates and uncertainty match the original spatial representation, as a ratio of the area of the circle to the area of the original spatial representation. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given georeference does not completely contain the original representation. The PointRadiusSpatialFit is undefined if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the PointRadiusSpatialFit is 1. Detailed explanations with graphical examples can be found in the Guide to Best Practices for Georeferencing (Chapman and Wieczorek, eds. 2006).
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/PointRadiusSpatialFit
+
+
+ Point Radius Spatial Fit
+ The ratio of the area of the point-radius (decimalLatitude, decimalLongitude, coordinateUncertaintyInMeters) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given point-radius does not completely contain the original representation. The pointRadiusSpatialFit is undefined (and should be left blank) if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the pointRadiusSpatialFit is 1.
+ Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/PointRadiusSpatialFit
+
+
+
+ Preparations
+ A concatenated list of preparations and preservation methods (skin, skull, skeleton, whole animal (ETOH), slide, etc.) for the cataloged item.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/PreparationsText
+
+
+ Preparations
+ A concatenated list of preparations and preservation methods for the object. Examples: "skin", "skull", "skeleton", "whole animal (ETOH)", "tissue (EDTA)".
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/PreparationsText
+
+
+ Preparations
+ A list (concatenated and separated) of preparations and preservation methods for a specimen.
+ Examples: "skin; skull; skeleton", "whole animal (ETOH); tissue (EDTA)", "fossil", "cast", "photograph", "DNA extract"
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/PreparationsText
+
+
+
+ Preparations
+ A list (concatenated and separated) of preparations and preservation methods for a specimen.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "fossil", "cast", "photograph", "DNA extract", "skin | "skull | skeleton", "whole animal (ETOH) | tissue (EDTA)".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/PreparationsText
+
+
+
+ Preparation Type
+ The type of preparation (skin. slide, etc). Probably best to add this as a record element rather than access point. Should be a list of preparations for a single collection record.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/PreparationsText
+
+
+ Preserved Specimen
+ A resource describing a preserved specimen.
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+ superseded
+ RecordBasisEnum/PreservedSpecimen
+
+
+ Preserved Specimen
+ A resource describing a preserved specimen.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ deprecated
+
+ RecordBasisEnum/PreservedSpecimen
+
+
+ Preserved Specimen
+ A specimen that has been preserved.
+
+ 2014-10-23
+ 2014-10-23
+
+
+
+ recommended
+
+ RecordBasisEnum/PreservedSpecimen
+
+
+ Previous Catalog Number
+ The previous (fully qualified) catalog number of the Cataloged Item if the item earlier identified by another Catalog Number, either in the current catalog or another Institution / catalog. A fully qualified Catalog Number is preceded by Institution Code and Collection Code, with a space separating the each subelement. Referencing a previous Catalog Number does not imply that a record for the referenced item is or is not present in the corresponding catalog, or even that the referenced catalog still exists. This access point is intended to provide a way to retrieve this record by previously used identifier, which may used in the literature. In future versions of this schema this attribute should be set-valued.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SpecimenUnit/History/PreviousUnitsText
+
+
+ Previous Identifications
+ A list (concatenated and separated) of previous ScientificNames to which the sample was identified.
+ Example: "Anthus correndera".
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification with PreferredFlag = false
+
+
+
+ Previous Identifications
+ A list (concatenated and separated) of previous assignments of names to the subject.
+ Example: "Anthus sp., field ID by G. Iglesias; Anthus correndera, expert ID by C. Cicero 2009-02-12 based on morphology"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification with PreferredFlag = false
+
+
+
+ Previous Identifications
+ A list (concatenated and separated) of previous assignments of names to the Occurrence.
+ Example: "Anthus sp., field ID by G. Iglesias; Anthus correndera, expert ID by C. Cicero 2009-02-12 based on morphology"
+
+ 2008-11-19
+ 2009-05-18
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification with PreferredFlag = false
+
+
+
+ Previous Identifications
+ A list (concatenated and separated) of previous assignments of names to the Organism.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Chalepidae", "Pinus abies", "Anthus sp., field ID by G. Iglesias | Anthus correndera, expert ID by C. Cicero 2009-02-12 based on morphology".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Identifications/Identification with PreferredFlag = false
+
+
+
+ Recorded By
+ A list (concatenated and separated) of names of people, groups, or organizations responsible for recording the original Occurrence. The primary collector or observer, especially one who applies a personal identifier (recordNumber), should be listed first.
+ Example: "Oliver P. Pearson; Anita K. Pearson" where the value in recordNumber "OPP 7101" corresponds to the number for the specimen in the field catalog (collector number) of Oliver P. Pearson.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/Gathering/GatheringAgents/GatheringAgentsText
+
+
+
+ Recorded By
+ A list (concatenated and separated) of names of people, groups, or organizations responsible for recording the original Occurrence. The primary collector or observer, especially one who applies a personal identifier (recordNumber), should be listed first.
+ The recommended best practice is to separate the values with a vertical bar (' | '). The primary collector or observer, especially one who applies a personal identifier (recordNumber), should be listed first. Examples: "José E. Crespo", "Oliver P. Pearson | Anita K. Pearson" where the value in recordNumber "OPP 7101" corresponds to the number for the specimen in the field catalog (collector number) of Oliver P. Pearson.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Gathering/GatheringAgents/GatheringAgentsText
+
+
+
+ Record Number
+ An identifier given to the Occurrence at the time it was recorded. Often serves as a link between field notes and an Occurrence record, such as a specimen collector's number.
+ Example: "OPP 7101"
+
+ 2008-11-19
+ 2009-05-18
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/CollectorsFieldNumber
+
+
+
+ Record URL
+ Gives the web address of the page where more information on this particular record (not on the whole dataset) can be found.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/RecordURI
+
+
+ Related Basis of Record
+ The nature of the related resource. Recommended best practice is to use the same controlled vocabulary as for basisOfRecord.
+ Example: "PreservedSpecimen"
+
+ 2008-11-19
+ 2009-01-26
+
+
+ deprecated
+ not in ABCD
+
+
+
+ Related Cataloged Items
+ The fully qualified identifier (Institution Code + " " + Collection Code + " " + Catalog Number) of the related Cataloged Item, preceded by the nature of the relationship (e.g., (sibling of) MVZ Mamm 1234).
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
+
+
+ Related Cataloged Items
+ One or more GlobalUniqueIdentifiers (cf. http://wiki.tdwg.org/twiki/bin/view/DarwinCore/GlobalUniqueIdentifier ) of related objects or observations, optionally preceded by the nature of the relationship. Examples: "(sibling of) URN:catalog:MVZ:Mammal:1234", "(endoparasite of) URN:catalog:FMNH:Bird:41321", "(sheet 2 of 2) URN:WTU:VascularPlants:353087".
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
+
+
+ Related Cataloged Item
+ The fully qualified identifier of a related Catalog Item (a reference to another specimen); Institution Code, Collection Code, and Catalog Number of the related Cataloged Item, where a space separates the three subelements.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
+
+
+ Related Information
+ Free text references to information not delivered via the conceptual schema, including URLs to specimen details, publications, bibliographic references, etc.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/RecordURI
+
+
+ Related Resource ID
+ An identifier for a related resource (the object, rather than the subject of the relationship).
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
+
+
+
+ Related Resource Type
+ The type of the related resource. Recommended best practice is to use a controlled vocabulary.
+ Examples: "StillImage", "MovingImage", "Sound", PhysicalObject", "PreservedSpecimen", FossilSpecimen", LivingSpecimen", "HumanObservation", "MachineObservation", "Location", "Taxonomy", "NomeclaturalChecklist", "Publication"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ deprecated
+ not in ABCD
+
+
+
+ Relationship According To
+ The source (person, organization, publication, reference) establishing the relationship between the two resources.
+ Example: "Julie Woodruff"
+
+ 2009-04-24
+ 2009-04-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Relationship Established Date
+ The date-time on which the relationship between the two resources was established. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
+ Examples: "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.
+
+ 2009-04-24
+ 2009-04-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Relationship Of Resource
+ The relationship of the resource identified by relatedResourceID to the subject (optionally identified by the resourceID). Recommended best practice is to use a controlled vocabulary.
+ Examples: "duplicate of", "mother of", "endoparasite of", "host to", "sibling of", "valid synonym of", "located within"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociationType
+
+
+
+ Relationship Remarks
+ Comments or notes about the relationship between the two resources.
+ Examples: "mother and offspring collected from the same nest", "pollinator captured in the act"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Associations/UnitAssociation/Comments
+
+
+
+ Relationship Type
+ A named or coded valued that identifies the kind relationship between this Collection Item and the referenced Collection Item. Named values include: "parasite of", "epiphyte on", "progeny of", etc. In future versions of this schema this attribute should be set-valued.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociationType
+
+
+ Remarks
+ Free text comments accompanying the cataloged item record.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Notes
+
+
+ Remarks
+ Free text comments accompanying the object or observation record.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Notes
+
+
+ Reproductive Condition
+ The reproductive condition of the biological individual(s) represented in the Occurrence. Recommended best practice is to use a controlled vocabulary.
+ Examples" "non-reproductive", "pregnant", "in bloom", "fruit-bearing"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ not in ABCD
+
+
+
+ Resource ID
+ An identifier for the resource that is the subject of the relationship.
+
+ 2009-04-24
+ 2009-04-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Resource Relationship
+ The category of information pertaining to relationships between resources (instances of data records, such as Occurrences, Taxa, Locations, Events).
+ Resources can be thought of as identifiable records and may include, but need not be limited to Occurrences, Locations, Events, Identifications, or Taxon records.
+
+ 2008-11-19
+ 2014-10-23
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/Associations
+
+
+ Resource Relationship
+ A relationship of one rdfs:Resource (http://www.w3.org/2000/01/rdf-schema#Resource) to another.
+ Resources can be thought of as identifiable records or instances of classes and may include, but need not be limited to Occurrences, Organisms, MaterialSamples, Events, Locations, GeologicalContexts, Identifications, or Taxa. Example: An instance of an Organism is the mother of another instance of an Organism.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/Associations
+
+
+ Resource Relationship ID
+ An identifier for an instance of relationship between one resource (the subject) and another (relatedResource, the object).
+
+ 2009-01-26
+ 2009-04-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Sample
+ Container class for information about the results of a sampling event (specimen, observation, etc.)
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ DataSets/DataSet/Units/Unit
+
+
+ Sample Attribute
+ Container class for information about attributes related to a given sample.
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ Datasets/Dataset/Units/Unit/MeasurementsOrFacts
+
+
+ Sample Attribute Accuracy
+ The description of the error associated with the SampleAttributeValue.
+ Example: "0.01", "normal distribution with variation of 2 m"
+
+ 2009-01-18
+ 2009-01-18
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
+
+
+
+ Sample Attribute Determined By
+ The agent responsible for having determined the value of the measurement or characteristic of the sample.
+ Example: "Javier de la Torre"
+
+ 2009-01-23
+ 2009-01-23
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy
+
+
+
+ Sample Attribute Determined Date
+ The date on which the the measurement or characteristic of the sample was made.
+ Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
+
+ 2009-01-23
+ 2009-01-23
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime
+
+
+
+ Sample Attribute Remarks
+ Comments or notes accompanying the measurement or characteristic of the sample.
+ Example: "tip of tail missing"
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ not in ABCD
+
+
+
+ Sample Attribute Unit
+ The units for the value of the measurement or characteristic of the sample. Recommended best practice is to use International System of Units (SI) units.
+ Example: "mm"
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
+
+
+
+ Sample Attribute Value
+ The value of the measurement or characteristic of the sample.
+ Example: "45"
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue
+
+
+
+ Sample Remarks
+ Comments or notes about the sample or record.
+ Example: "found dead on road"
+
+ 2008-11-19
+ 2009-01-18
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Notes
+
+
+
+ Sample Size
+ The size of the sample from which the collection/observation was drawn. It can be a volume (e.g. for a phytoplankton sample), a linear distance (e.g. for a visual transect or net haul), a surface area (e.g. for a benthic core), etc. This field must also include the units, e.g. 200 mfor a transect, or 0.25 m^2 for a benthic grab (use ^ to denote a superscript). Note that When multiple collections/observations are reported from the same physical sample, a code identifying the sample can be placed in the Field_Number field to allow all collections/observations from a single sample to be connected.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue + constant
+
+
+ Sample Attribute ID
+ An identifier for the sampling attribute. May be a global unique identifier or an identifier specific to the data set.
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Sample Attribute Type
+ The nature of the measurement or characteristic of the sample. Recommended best practice is to use a controlled vocabulary.
+ Example: "tail length"
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
+
+
+
+ Sampling Effort
+ The amount of effort expended during an Event.
+ Examples: "40 trap-nights", "10 observer-hours; 10 km by foot; 30 km by car"
+
+ 2009-08-24
+ 2009-08-24
+
+
+ recommended
+ not in ABCD
+
+
+
+ Sampling Event
+ Container class for information about the conditions and methods of acquisition of samples.
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering
+
+
+ Sampling Event Attributes
+ A list (concatenated and separated) of additional measurements or characteristics of the sampling event.
+ Example: "Relative humidity: 28 %; Temperature: 22 C; Sample size: 10 kg"
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts
+
+
+
+ Sampling Event ID
+ An identifier for the sampling event. May be a global unique identifier or an identifier specific to the data set.
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Code
+
+
+
+ Sampling Event Remarks
+ Comments or notes about the sampling event.
+ Example: "found dead on road"
+
+ 2009-01-18
+ 2009-01-18
+
+
+ superseded
+ not in ABCD
+
+
+
+ Sampling Location
+ Container class for information about the location where a sampling event occurred.
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/LocalityText
+
+
+ Sampling Location ID
+ An identifier for the sampling location. May be a global unique identifier or an identifier specific to the data set.
+ Example: "MVZ:LocID:12345"
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Sampling Location Remarks
+ Comments or notes about the sampling location.
+ Example: "under water since 2005"
+
+ 2009-01-18
+ 2009-01-18
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/AreaDetail
+
+
+
+ Sampling Protocol
+ The name of, reference to, or description of the method or protocol used during an Event.
+ Examples: "UV light trap", "mist net", "bottom trawl", "ad hoc observation", "point count", "Penguins from space: faecal stains reveal the location of emperor penguin colonies, http://dx.doi.org/10.1111/j.1466-8238.2009.00467.x", "Takats et al. 2001. Guidelines for Nocturnal Owl Monitoring in North America. Beaverhill Bird Observatory and Bird Studies Canada, Edmonton, Alberta. 32 pp.", "http://www.bsc-eoc.org/download/Owl.pdf"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Method
+
+
+
+ Scientific Name
+ The full name of lowest level taxon the Cataloged Item can be identified as a member of; includes genus name, specific epithet, and subspecific epithet (zool.) or infraspecific rank abbreviation, and infraspecific epithet (bot.) Use name of suprageneric taxon (e.g., family name) if Cataloged Item cannot be identified to genus, species, or infraspecific taxon.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/FullScientificNameString
+
+
+ Scientific Name
+ The full name of lowest level taxon to which the cataloged item can be identified (e.g., genus name, specific epithet, subspecific epithet, etc.).
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/FullScientificNameString
+
+
+ Scientific Name
+ The full name of the lowest level taxon to which the organism has been identified in the most recent accepted determination, specified as precisely as possible, including name-author, year or authorship, sensu or sec. (according to or following) author, and indication of uncertainty. Conceptually equivalent to a full taxonomic identification as given by the identifier (verbatim). Does not include the identifier name or date of identification. Examples: "Coleoptera" (an Order), "Vespertilionidae" (a Family), "Manis" (a Genus), "Ctenomys sociabilis" (Genus + SpecificEpithet), "Ambystoma tigrinum diaboli" (Genus + SpecificEpithet + SubspecificEpithet), "Quercus agrifolia var. oxyadenia (Torr.) J.T. Howell" (Genus + SpecificEpithet + InfraspecificRank + InfraspecificEpithet + AuthorYearOfScientificName).
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/FullScientificNameString
+
+
+ Scientific Name
+ The taxon name (with date and authorship information if applicable). When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the IdentificationQualifier term.
+ Examples: "Coleoptera" (order), "Vespertilionidae" (family), "Manis" (genus), "Ctenomys sociabilis" (genus + specificEpithet), "Ambystoma tigrinum diaboli" (genus + specificEpithet + infraspecificEpithet), "Quercus agrifolia var. oxyadenia (Torr.) J.T. Howell" (genus + specificEpithet + taxonRank + infraspecificEpithet + scientificNameAuthorship)
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/FullScientificNameString
+
+
+
+ Scientific Name
+ The full scientific name, with authorship and date information if known. When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the IdentificationQualifier term.
+ Examples: "Coleoptera" (order), "Vespertilionidae" (family), "Manis" (genus), "Ctenomys sociabilis" (genus + specificEpithet), "Ambystoma tigrinum diaboli" (genus + specificEpithet + infraspecificEpithet), "Roptrocerus typographi (Györfi, 1952)" (genus + specificEpithet + scientificNameAuthorship), "Quercus agrifolia var. oxyadenia (Torr.) J.T. Howell" (genus + specificEpithet + taxonRank + infraspecificEpithet + scientificNameAuthorship)
+
+ 2008-11-19
+ 2009-09-21
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/FullScientificNameString
+
+
+
+ Scientific Name Author
+ The author of a scientific name. Author string as applied to the accepted name. Can be more than one author (concatenated string). Should be formatted according to the conventions of the applicable taxonomic discipline.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/ParentheticalAuthorTeamAndYear + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/AuthorTeamAndYear} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeamParenthesis + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeam} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamOriginalAndYear + [= or] DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamParenthesisAndYear}
+
+
+ Scientific Name Author
+ The author of the ScientificName. Can be more than one author in a concatenated string. Should be formatted according to the conventions of the applicable taxonomic discipline.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/ParentheticalAuthorTeamAndYear + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/AuthorTeamAndYear} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeamParenthesis + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeam} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamOriginalAndYear + [= or] DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamParenthesisAndYear}
+
+
+ Scientific Name Authorship
+ The authorship information for the scientificName formatted according to the conventions of the applicable nomenclaturalCode.
+ Example: "(Torr.) J.T. Howell", "(Martinovský) Tzvelev", "(Györfi, 1952)"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/ParentheticalAuthorTeamAndYear + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/AuthorTeamAndYear} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeamParenthesis + DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/AuthorTeam} or {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamOriginalAndYear + [= or] DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/AuthorTeamParenthesisAndYear}
+
+
+
+ Scientific Name ID
+ A unique identifier for the scientificName.
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Scientific Name ID
+ An identifier for the nomenclatural (not taxonomic) details of a scientific name.
+ Example: "urn:lsid:ipni.org:names:37829-1:1.3"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Scientific Name Rank
+ The taxonomic rank of the most specific name in the scientificName. Recommended best practice is to use a controlled vocabulary.
+ Examples: "subsp.", "var.", "forma", "species", "genus"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Rank
+
+
+
+ Sex
+ The sex of a specimen. The domain should be a controlled set of terms (codes) based on community consensus. Proposed values: M=Male; F=Female; H=Hermaphrodite; I=Indeterminate (examined but could not be determined; U=Unkown (not examined); T=Transitional (between sexes; useful for sequential hermaphrodites)
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Sex
+
+
+ Sex
+ The sex of a cataloged item (e.g., male, female, hermaphrodite, gynandromorph, not recorded, indeterminate, transitional - between sexes, for sequential hermaphrodites).
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Sex
+
+
+ Sex
+ The sex of the biological individual represented by the cataloged object or observation. Examples: "male", "female", "hermaphrodite", "gynandromorph", "monoecious", "dioecious", "not recorded", "indeterminate", "transitional".
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Sex
+
+
+ Sex
+ The sex of the biological individual(s) represented in the Occurrence. Recommended best practice is to use a controlled vocabulary.
+ Examples: "female", "hermaphrodite", "8 males, 4 females"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Sex
+
+
+
+ source material identifiers
+ A unique identifier assigned to a material sample (as defined by http://rs.tdwg.org/dwc/terms/MaterialSampleID, and as opposed to a particular digital record of a material sample) used for extracting nucleic acids, and subsequent sequencing. The identifier can refer either to the original material collected or to any derived sub-samples. The INSDC qualifiers /specimen_voucher, /bio_material, or /culture_collection provide additional context and suggested syntax for this identifier for data submitted to INSDC databases.
+
+ 2013-05-25
+ 2011-01-26
+
+
+ deprecated
+ not in ABCD
+
+
+
+ Source
+ Indicates who gave the record to the data provider. Can indicate a literature citation, an electronic dataset, etc. Is used to provide credit.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/IPRStatements/Citations/Citation/Text
+
+
+ Species
+ The specific epithet of the organism
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
+
+
+ Species
+ The phylogenetic specific epithet of the cataloged item.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
+
+
+ Specific Epithet
+ The specific epithet of the scientific name applied to the organism.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
+
+
+ Specific Epithet
+ The name of the first or species epithet of the scientificName.
+ Examples: "concolor", "gottschei"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
+
+
+
+ Start End Coordinate Precision
+ An estimate of how tightly the locality was specified in the Start/End Latitude and Longitude fields; expressed as a distance, in meters, that corresponds to a radius around the latitude-longitude coordinates. Use NULL where precision is unknown, cannot be estimated, or is not applicable.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/CoordinateErrorDistanceInMeters
+
+
+ Start Day Collected
+ For samples/observations/record events that were taken over time this gives the start day of the collecting event. Possible value ranges from 01..31 inclusive.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+ Start Day Of Year
+ The earliest ordinal day of the year on which the Event occurred (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366).
+ Examples: "1" (=1 Jan), "366" (=31 Dec), "365" (=30 Dec in a leap year, 31 Dec in a non-leap year)
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberBegin
+
+
+
+ Start Julian Day
+ For samples/observations/record events that were taken over time this gives the start ordinal day of the year for the collecting event; i.e., the number of days since January 1 of the same year. (January 1 is Julian Day 1.). Should be an integer from one to 365, i.e. of the form (([0-3][0-9][0-9)|([0-9][0-9)|([1-9])).
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberBegin
+
+
+ Start Latitude
+ For samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the starting latitude location from which the specimen was collected or in which the sample/observation/record event occurred. This value should be expressed in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/).
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/CoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal with attribute "begin" set to true
+
+
+ Start Longitude
+ For samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the starting longitude location from which the specimen was collected. Express in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/).
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/CoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal with attribute "begin" set to true
+
+
+ Start Month Collected
+ For samples/observations/record events that were taken over time this gives the start month of the collecting event. Possible values range from 01...12 inclusive.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+ Start Time of Day
+ The time of day when the sampling event began, expressed as decimal hours from midnight local time. Examples: 0 = midnight, 12.0 = mid-day, 13.5 = 13:30
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/TimeOfDayBegin
+
+
+ Start Time of Day
+ The time of day when the event began, expressed as decimal hours from midnight, local time.
+ Examples: "12.0" (= noon), "13.5" (= 1:30pm)
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ deprecated
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+
+ Start Year Collected
+ For samples/observations/record events that were taken over time this gives the start year of the collecting event. The full year should be expressed (e.g. 1972 must be expressed as "1972" not "72"). Must always be a four digit integer.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+ State Province
+ The state, province or region (i.e. next political region smaller than Country) from which the specimen was collected. There is some suggestion to use the values described in ISO 3166-2 (http://www.iso.ch/cate/d8349.html), however these values are in a continual state of flux and it appears unlikely that an appropriate mechanism (by ISO) will be in place to manage these changes. Hence it is recommended that where possible, the full, unabbreviated name should be used for storing information. The server should optionally handle abbreviations as an access point. Note: this is a recurring theme (country and state) abbreviations. Check the existence of an attribute type to deal with abbreviations from the bib-1 profile
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= State or = Province (etc.)
+
+
+ State Province
+ The full, unabbreviated name of the state, province, or region (i.e., the next smaller political region than Country) from which the cataloged item was collected.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= State or = Province (etc.)
+
+
+ State Province
+ The full, unabbreviated name of the state, province, or region (i.e., the next smaller political region than Country) in which the organism was collected or observed.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= State or = Province (etc.)
+
+
+ State Province
+ The name of the next smaller administrative region than country (state, province, canton, department, region, etc.) in which the Location occurs.
+ Examples: "Montana", "Minas Gerais", "Córdoba"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= State or = Province (etc.)
+
+
+
+ Subgenus
+ The name of the subgenus in which the identified name is classified.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/Subgenus
+
+
+ Subgenus
+ The name of the subgenus in which the scientificName is classified.
+ Example: "Strobus" subgenus of Pinus
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/Subgenus
+
+
+
+ Subgenus
+ The full scientific name of the subgenus in which the taxon is classified. Values should include the genus to avoid homonym confusion.
+ Examples: "Strobus (Pinus)", "Puma (Puma)" "Loligo (Amerigo)", "Hieracium subgen. Pilosella"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/Subgenus
+
+
+
+ Subspecies
+ The sub-specific epithet of the organism
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
+
+
+ Subspecies
+ The phylogenetic subspecific epithet of the cataloged item.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
+
+
+ Taxon
+ The category of information pertaining to taxonomic names or concepts.
+
+ 2008-11-19
+ 2008-11-19
+
+
+ superseded
+ no simple equivalent in ABCD
+
+
+ Taxon
+ A resource describing an instance of the Taxon class.
+
+ 2009-01-23
+ 2014-10-23
+
+
+ deprecated
+
+ not in ABCD
+
+
+ Taxon
+ The category of information pertaining to taxonomic names, taxon name usages, or taxon concepts.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ superseded
+
+ no simple equivalent in ABCD
+
+
+ Taxon
+ A group of organisms (sensu http://purl.obolibrary.org/obo/OBI_0100026) considered by taxonomists to form a homogeneous unit.
+ Example: The genus Truncorotaloides as published by Brönnimann et al. in 1953 in the Journal of Paleontology Vol. 27(6) p. 817-820.
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ no simple equivalent in ABCD
+
+
+ Taxon According To
+ Information about the authorship of this taxon concept which uses the scientificName in their sense (secundum, sensu). Could be a publication (identification key), institution or team of individuals.
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Taxon Attributes
+ A list (concatenated and separated) of additional measurements, facts, characteristics, or assertions about the taxon.
+ Example: "iucnstatus=vulnerable; distribution=Neuquen, Argentina"
+
+ 2009-04-24
+ 2009-04-24
+
+
+ deprecated
+ DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/InformalNameString
+
+
+
+ Taxon Concept ID
+ A unique identifier for the taxon concept (a circumscription of a taxonName).
+
+ 2009-04-24
+ 2009-04-24
+
+
+
+ deprecated
+ not in ABCD
+
+
+
+ Taxon Concept ID
+ An identifier for the taxonomic concept to which the record refers - not for the nomenclatural details of a taxon.
+ Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"
+
+ 2009-04-24
+ 2009-09-21
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Taxon ID
+ A global unique identifier for the taxon (name in a classification).
+
+ 2008-11-19
+ 2008-11-19
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Taxon ID
+ An identifier for the set of taxon information (data associated with the Taxon class). May be a global unique identifier or an identifier specific to the data set.
+ Examples: "8fa58e08-08de-4ac1-b69c-1235340b7001", "32567", "http://species.gbif.org/abies_alba_1753", "urn:lsid:gbif.org:usages:32567"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Taxon Name ID
+ A unique identifier for the scientificName.
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+
+ superseded
+ not in ABCD
+
+
+
+ Taxonomic Status
+ The status of the use of the scientificName as a label for a taxon. Requires taxonomic opinion to define the scope of a taxon. Rules of priority then are used to define the taxonomic status of the nomenclature contained in that scope, combined with the experts opinion. It must be linked to a specific taxonomic reference that defines the concept. Recommended best practice is to use a controlled vocabulary.
+ Examples: "invalid", "misapplied", "homotypic synonym", "accepted"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ not in ABCD
+
+
+
+ Taxon Rank
+ The taxonomic rank of the most specific name in the scientificName. Recommended best practice is to use a controlled vocabulary.
+ Examples: "subsp.", "var.", "forma", "species", "genus".
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Rank
+
+
+
+ Taxon Rank
+ The taxonomic rank of the most specific name in the scientificName. Recommended best practice is to use a controlled vocabulary.
+ Examples: "subspecies", "varietas", "forma", "species", "genus"
+
+ 2008-11-19
+ 2009-09-21
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Rank
+
+
+
+ Taxon Remarks
+ Comments or notes about the taxon.
+ Example: "this name is a misspelling in common use"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ superseded
+ not in ABCD
+
+
+
+ Taxon Remarks
+ Comments or notes about the taxon or name.
+ Example: "this name is a misspelling in common use"
+
+ 2008-11-19
+ 2009-08-24
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Temperature
+ The temperature recorded with the collection/record event. Is assumed to be taken at the collection depth. Expressed in degrees Celsius.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue + constant
+
+
+ Time Collected
+ The time of day the cataloged item was collected, expressed as decimal hours from midnight, local time (e.g., 12.0 = noon, 13.5 = 1:30pm).
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/TimeOfDayBegin
+
+
+ Time of Day
+ The time of day a specimen was collected expressed as decimal hours from midnight local time (e.g. 12.0 = mid day, 13.5 = 1:30pm)
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/TimeOfDayBegin
+
+
+ Time Zone
+ Indicates the time zone for the Time of Day measurements.
+
+ 2005-07-10
+ 2005-07-10
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/TimeZone
+
+
+ Tissues
+ A concatenated list of tissues and preservation methods (whole (frozen), liver (EDTA), etc.) for the cataloged item.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/PreparationsText
+
+
+ Type Status
+ Indicates the kind of nomenclatural type that a specimen represents. (This is incomplete because type status actually describes the relationship between a name and a specimen [or ternary relatiohnship between a specimen, name, and publication].) In particular, the type status may not apply to the name listed in the scientific name, i.e., current identification. In rare cases, a single specimen may be the type of more than one name.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeText
+
+
+ Type Status
+ A list of one or more nomenclatural types that the cataloged item represents (e.g., "holotype of Ctenomys sociabilis. Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388.").
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeText
+
+
+ Type Status
+ A list of one or more nomenclatural types (including type status and typified taxonomic name) represented by the object. Example: "holotype of Ctenomys sociabilis. Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388".
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeText
+
+
+ Type Status
+ A list (concatenated and separated) of nomenclatural types (type status, typified scientific name, publication) applied to the subject.
+ Example: "holotype of Ctenomys sociabilis. Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388"
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ superseded
+
+ DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeText
+
+
+
+ Type Status
+ A list (concatenated and separated) of nomenclatural types (type status, typified scientific name, publication) applied to the subject.
+ The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "holotype of Ctenomys sociabilis. Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "holotype of Pinus abies | holotype of Picea abies".
+
+ 2008-11-19
+ 2014-10-23
+
+
+
+ recommended
+
+ DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeText
+
+
+
+ Valid Distribution Flag
+ A flag ("true" or "false") that indicates whether the locality information represents a valid distribution occurrence for a specimen. Specimens taken from captivity and showing the captive location should use the value "false".
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/ValidDistributionFlag
+
+
+ Verbatim Collecting Date
+ The verbatim original representation of the date information for the collecting event.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/DateText
+
+
+ Verbatim Collecting Date
+ The verbatim original representation of the date (and time) information for the collecting event. Example: "spring 1910".
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/DateText
+
+
+ Verbatim Coordinates
+ A text representation of the coordinate data (Latitude/ Longitude, UTM, TRS, etc.) from its original source if it cannot be separated into its component parts. Example: "470999 1234300".
+
+ 2007-04-17
+ 2007-04-17
+
+
+ superseded
+ {DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinatesText or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesUTM/UTMText}
+
+
+ Verbatim Coordinates
+ The verbatim original spatial coordinates of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
+ Examples: "41 05 54S 121 05 34W", "17T 630000 4833400"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ recommended
+ {DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinatesText or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesUTM/UTMText}
+
+
+
+ Verbatim Coordinate System
+ The name of the system in which the verbatim geographic coordinates were recorded. Examples: "decimal degrees", "degrees minutes seconds", "degrees decimal minutes", "UTM"
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ (partly) DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesGrid/GridCellSystem
+
+
+ Verbatim Coordinate System
+ The spatial coordinate system for the verbatimLatitude and verbatimLongitude or the verbatimCoordinates of the Location. Recommended best practice is to use a controlled vocabulary.
+ Examples: "decimal degrees", "degrees decimal minutes", "degrees minutes seconds", "UTM"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ recommended
+ (partly) DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesGrid/GridCellSystem
+
+
+
+ Verbatim Depth
+ A text representation of the Depth in its original format in the source database.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactText
+
+
+ Verbatim Depth
+ A text representation of the depth in its original format in the source database. Example: "100 to 200 ft below sea level".
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactText
+
+
+ Verbatim Depth
+ The original description of the depth below the local surface.
+ Example: "100-200 m"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactText
+
+
+
+ Verbatim Elevation
+ A text representation of the Elevation in its original format in the source database.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactText
+
+
+ Verbatim Elevation
+ A text representation of the altitude in its original format in the source database. Example: "1000+- meters".
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactText
+
+
+ Verbatim Elevation
+ The original description of the elevation (altitude, usually above sea level) of the Location.
+ Example: "100-200 m"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactText
+
+
+
+ Verbatim EventDate
+ The verbatim original representation of the date and time information for an Event.
+ Examples: "spring 1910", "Marzo 2002", "1999-03-XX", "17IV1934"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/DateTime/DateText
+
+
+
+ Verbatim Latitude
+ A text representation of the Latitude data in its original format in the source database.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLatitude
+
+
+ Verbatim Latitude
+ A text representation of the Latitude part of the coordinate data from its original source. Example: 47d09'99"N
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLatitude
+
+
+ Verbatim Latitude
+ The verbatim original latitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
+ Example: "41 05 54.03S"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLatitude
+
+
+
+ Verbatim Locality
+ The original textual description of the place.
+ Example: "25 km NNE Bariloche por R. Nac. 237"
+
+ 2008-11-19
+ 2009-04-24
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
+
+
+
+ Verbatim Longitude
+ A text representation of the Longitude data in its original format in the source database.
+
+ 2003-06-17
+ 2003-06-17
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLongitude
+
+
+ Verbatim Longitude
+ A text representation of the Longitude part of the coordinate data from its original source. Example: -122.43254
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLongitude
+
+
+ Verbatim Longitude
+ The verbatim original longitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
+ Example: "121d 10' 34" W"
+
+ 2008-11-19
+ 2009-07-06
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLongitude
+
+
+
+ Verbatim Taxon Rank
+ The taxonomic rank of the most specific name in the scientificName as it appears in the original record.
+ Examples: "Agamospecies", "sub-lesus", "prole", "apomict", "nothogrex", "sp.", "subsp.", "var."
+
+ 2009-07-06
+ 2009-09-21
+
+
+
+ recommended
+ not in ABCD
+
+
+
+ Verbatim Scientific Name Rank
+ The taxonomic rank of the most specific name in the scientificName as it appears in the original record.
+ Examples: "Agamospecies", "sub-lesus", "prole", "apomict", "nothogrex".
+
+ 2009-07-06
+ 2009-07-06
+
+
+ superseded
+ not in ABCD
+
+
+
+ Verbatim SRS
+ The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which coordinates given in verbatimLatitude and verbatimLongitude, or verbatimCoordinates are based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".
+ Examples: "EPSG:4326", "WGS84", "NAD27", "Campo Inchauspe", "European 1950", "Clarke 1866"
+
+ 2009-07-06
+ 2009-07-06
+
+
+ recommended
+ not in ABCD
+
+
+
+ Vernacular Name
+ A common or vernacular name.
+ Examples: "Andean Condor", "Condor Andino", "American Eagle", "Gänsegeier"
+
+ 2009-07-06
+ 2009-07-06
+
+
+ recommended
+ not in ABCD
+
+
+
+ Water Body
+ The full, unabbreviated name of the body of water in or over which the organism was collected or observed.
+
+ 2007-04-17
+ 2007-04-17
+
+
+
+ superseded
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Water body
+
+
+ Water Body
+ The name of the water body in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
+ Examples: "Indian Ocean", "Baltic Sea", "Hudson River"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Water body
+
+
+
+ Year
+ The four-digit year in which the Event occurred, according to the Common Era Calendar.
+ Example: "2008"
+
+ 2008-11-19
+ 2009-04-24
+
+
+
+ recommended
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+
+ Year Collected
+ The year (expressed as an integer) in which the specimen was collected. The full year should be expressed (e.g. 1972 must be expressed as "1972" not "72"). Must always be a four digit integer [-9999..9999]
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+ Year Collected
+ The four digit year in the Common Era calendar in which the cataloged item was collected.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
+
+
+ Year Identified
+ The year portion of the date when the Collection Item was identified; as four digits [-9999..9999], e.g., 1906, 2002.
+
+ 2003-06-13
+ 2003-06-13
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
+
+
+ Year Identified
+ The four digit year in the Common Era calendar in which the cataloged item was identified as having the ScientificName.
+
+ 2003-06-17
+ 2003-06-17
+
+
+
+ superseded
+ accessible from DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
+
+
\ No newline at end of file
diff --git a/rdf/dwctype.rdf b/rdf/dwctype.rdf
deleted file mode 100644
index 4a34665..0000000
--- a/rdf/dwctype.rdf
+++ /dev/null
@@ -1,74 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-]>
-
-
-Darwin Core Type Terms
-This document contains a list of terms in the Darwin Core Type Vocabulary. For the full normative RDF document of all Darwin Core terms, see dwctermshistory.rdf. To comment on this schema, please create a new issue in http://code.google.com/p/darwincore/issues/
-Biodiversity Information Standards (TDWG)
-2013-10-22
-
-
-
-
-
-
-OccurrenceA resource describing an instance of the Occurrence class.2008-11-192011-10-16recommendednot in ABCD
-LocationA resource describing an instance of the Location class.2009-01-232009-04-24recommendednot in ABCD
-TaxonA resource describing an instance of the Taxon class.2009-01-232009-04-24recommendednot in ABCD
-PreservedSpecimenA resource describing a preserved specimen.2008-11-192011-10-16recommendedRecordBasisEnum/PreservedSpecimen
-FossilSpecimenA resource describing a fossilized specimen.2008-11-192011-10-16recommendedRecordBasisEnum/FossileSpecimen
-LivingSpecimenA resource describing a living specimen.2008-11-192011-10-16recommendedRecordBasisEnum/LivingSpecimen
-HumanObservationA resource describing an observation made by one or more people.2008-11-192008-11-19recommendedRecordBasisEnum/HumanObservation
-MachineObservationA resource describing an observation made by a machine.2008-11-192008-11-19recommendedRecordBasisEnum/MachineObservation
-NomenclaturalChecklistA resource describing a nomenclatural checklist.2009-01-232009-01-23recommendednot in ABCD
-MaterialSampleA resource describing the physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.2013-03-282013-09-26recommendedDataSets/DataSet/Units/Unit
-
-
-
diff --git a/rdf/human-dwctype.xsl b/rdf/human-dwctype.xsl
deleted file mode 100644
index df75c27..0000000
--- a/rdf/human-dwctype.xsl
+++ /dev/null
@@ -1,289 +0,0 @@
-
-
-
-
-
-
- http://code.google.com/p/darwincore/wiki/
-
-
-
- Darwin Core Type Vocabulary
-
-
-
-
-Audience: This document is targeted toward those who wish to use or share information based on the Darwin Core terms using text
-files. It provides technical details on how to construct these files and complementary metadata files that describe their content.
-
-This document provides guidelines for formatting and sharing Darwin Core terms [TERMS] in
-fielded text formats, such as one or more comma separated value (CSV) files. Data conforming to the Simple Darwin Core
-[SIMPLEDWC] (CSV format and having the first row include Darwin Core standard term names)
-can be shared in a single file, while a non-standard text file can be understood using an [XML]
-metafile to describe its contents and formatting.
+
+
Darwin Core Text Guide
-
-
-More complex structure can be shared in multiple related files. The description of content and relationships between files can
-be achieved using the metafile. This guideline makes recommendations for the simple case of a core file, upon which
-Darwin Core records are based, and extensions that are linked to records in that core file. Specifically, extension
-records have a many-to-one relationship with records in the core file. For example, a core file might contain specimen records,
-with one specimen per row in the file, while an extension file contains one or more identifications for those specimens, with one identification per row in the extension file, and with an identifier
-to the specimen for each identification row. This example would allow many identifications to be associated with each specimen.
-
+
-
1.1 Simple Example Metafile Content
-A simple comma separated values (CSV) data file with the following content:
-
+
+
+
+
Title:
+
+
Darwin Core Text Guide
+
+
+
+
Date Issued:
+
+
2009-02-12
+
+
+
+
Date Modified:
+
+
2014-11-08
+
+
+
+
Abstract:
+
+
Guidelines for implementing Darwin Core in Text files.
+
+
+
+
Contributors:
+
+
Tim Robertson (GBIF), Markus Döring (GBIF), John
+ Wieczorek (MVZ), Renato De Giovanni (CRIA), Dave Vieglais
+ (KUNHM)
+
+
+
+
Legal:
+
+
This document is governed by the standard legal, copyright,
+ licensing provisions and disclaimers issued by the Taxonomic
+ Databases Working Group.
Audience: This document is targeted toward
+ those who wish to use or share information based on the Darwin Core terms
+ using text files. It provides technical details on how to construct these
+ files and complementary metadata files that describe their content.
+
+
This document provides guidelines for formatting and sharing Darwin Core
+ terms [TERMS] in fielded text formats,
+ such as one or more comma separated value (CSV) files. Data conforming to the
+ Simple Darwin Core [SIMPLEDWC] (CSV
+ format and having the first row include Darwin Core standard term names) can
+ be shared in a single file, while a non-standard text file can be understood
+ using an [XML] metafile to describe its
+ contents and formatting.
+
+ More complex structure can be shared in multiple related files. The
+ description of content and relationships between files can be achieved using
+ the metafile. This guideline makes recommendations for the simple case of a
+ core file, upon which Darwin Core records are based, and
+ extensions that are linked to records in that core file.
+ Specifically, extension records have a many-to-one relationship with
+ records in the core file. For example, a core file might contain specimen
+ records, with one specimen per row in the file, while an extension file
+ contains one or more identifications for those specimens, with one
+ identification per row in the extension file, and with an identifier to the
+ specimen for each identification row. This example would allow many
+ identifications to be associated with each specimen.
+
+
1.1 Simple Example Metafile Content
A simple comma separated values
+ (CSV) data file with the following content:
+
-Many resources exist on the web describing the advantages of Extensible Markup Language [XML]
-over less structured content such as fielded text. The Darwin Core Text Guide (this document) is not meant to promote
-the use of fielded text over XML for data exchange, but rather to provide recommendations for how to handle such data files when necessary.
-
-Two scenarios that might benefit from the use of fielded text are:
-
-
The transfer of large numbers of Darwin Core records and related data from one database to another.
- Typically databases are very efficient at exporting and importing comma separated text files.
-
The description of legacy data existing in a fielded text format, such that it might be automatically understood and loaded into another system.
- It could be that this system would then serve the data in another format such as XML.
-
-
+
-
-
2. Metafile Content
-
-The text metafile schema [TEXTSCHEMA] provides technical details for the
-structure of a metafile by defining the elements and attributes required to describe the contents and relationships
-between text files. These elements and attributes, with descriptions and specifications for their use in a metafile,
-are described in the following table.
-
+
1.2 XML versus Fielded Text
-
2.1 The <archive> element
-The <archive> element is the container for the list of related files (one core and zero or more extensions). The <archive>
-element has just one attribute, metadata.
-
-
-
-
Attributes
-
Attribute
-
Description
-
Required
-
Default
-
-
-
-
metadata
-
Contains a qualified Uniform Resource Locator (URL) defining the location of a metadata description of the entire archive.
- The format of the metadata is not prescribed, but a standardized format such as Ecological Metadata Language (EML), Federal Geographic Data Committee (FGDC), or ISO 19115 family is recommended.
-
An <archive> must contain exactly one <core> element, representing the data entity (the actual file and its column header mappings to Darwin Core terms) upon which records are based.
- If extensions are being used, each record in the core data must have a unique identifier. The field for this identifier must be specified in an explicit <id> field in order to associate extension records with the core record.
-
An <archive> may define zero or more <extension> elements, each representing an individual extension entity directly related to the core.
-In addition to the general file attributes described below, every extension entity must have an explicit <coreId> field to relate the extension record to a row in the core entity. The extension itself does not have to have a unique ID field and many rows can point to the same core record.
-
-
-
-
-
+
Many resources exist on the web describing the advantages of Extensible
+ Markup Language [XML] over less
+ structured content such as fielded text. The Darwin Core Text Guide
+ (this document) is not meant to promote the use of fielded text over
+ XML for data exchange, but rather to provide recommendations for how to
+ handle such data files when necessary.
+ Two scenarios that might benefit from the use of fielded text
+ are:
- A Unified Resource Identifier (URI) for the term identifying the class of data represented by each row, for example, http://rs.tdwg.org/dwc/terms/Occurrence for Occurrence records or http://rs.tdwg.org/dwc/terms/Taxon for Taxon records.
- Additional classes may be referenced by URI and defined outside the Darwin Core specification.
- The row type defaults to the ambiguous SimpleDarwinRecord.
- For convenience the URIs for classes defined by the Darwin Core are listed below:
-
Specifies the delimiter between fields. Typical values might be "," or "\t" for CSV or Tab files respectively.
-
-
,
-
-
-
linesTerminatedBy
-
Specifies the row separator character.
-
-
\n
-
-
-
fieldsEnclosedBy
-
Specifies the character used to enclose (mark the start and end of) each field.
- CSV files frequently use the double quote character ("), but the default is no enclosing character. Note that a comma separated value file that has commas within the content of any field must have an enclosing character.
-
-
"
-
-
-
-
encoding
-
Specifies the character encoding for the data file.
- The encoding is extremely important, but often ignored. The most frequently used encodings are:
-
-
UTF-8
-
8-bit Unicode Transformation Format.
-
UTF-16
-
16-bit Unicode Transformation Format.
-
ISO-8859-1
-
Commonly known as Latin-1 and a common default on systems configured for a single western European language.
-
Windows-1252
-
Commonly known as WinLatin and a common default of legacy versions of Microsoft Windows based operating systems.
-
-
-
-
UTF-8
-
-
-
ignoreHeaderLines
-
Specifies the number lines to ignore from the beginning of the file. This can be used to ignore files with column headings or preamble comments for example.
-
-
0
-
-
-
dateFormat
-
When verbatim dates are consistent in format, this field can be used to indicate the format represented. It is recommended to use the date, dateTime and time for field formats wherever possible, but where verbatim dates are required, a format may be specified here.
- This should be considered a 'hint' for consumers. It is recommended that consumers support the minimum combinations of DD MM and YYYY with the separators / and -. Examples:
-
<core> or <extension> element must contain one <files> element to locate the data being described.
-
-
-
<id>
-
If extensions are being used, the <core> must contain an <id> element that indicates the identifier for a record.
-
-
-
<coreId>
-
If extensions are being used, the <extension> element must contain a <coreId> element that indicates the column in the extension file that contains the core record identifier (the matching <id> in the core file).
- The files element must contain one or more <location> elements, each defining where a file resides. Each core or extension entity can be composed from one or more files. If an entity has data in more than one file, use the <location> element multiple times, once for each file that makes up the entity.
-
-
-
-
-
Elements
-
Element
-
Description
-
-
-
-
location
-
Specifies the location of the file being described, which may take either of the following forms:
-
-
A web accessible URL such as "http://www.gbif.org/data/specimen.csv" or "ftp://ftp.gbif.org/tim/specimen.txt".
-
A filepath relative to the location of the metafile such as "specimen.txt","./specimen.txt", "data/specimen.txt".
-
-
-
-
-
-
+
+
The transfer of large numbers of Darwin Core records and related data
+ from one database to another. Typically databases are very efficient at
+ exporting and importing comma separated text files.
-The field element is used to specify the location and content of data within a file. There must be one field element for every term
-being shared for the entity, whether explicitly or through the use of a default value for all rows in the file.
-
-
-
-
Attributes
-
Attribute
-
Description
-
Required
-
Default
-
-
-
-
index
-
Specifies the position of the column in the row. The first column has an index of 0, the second column 1, etc.
- If no column index is specified, then the term and the default may be used to define a constant value for all rows.
-
-
-
-
-
term
-
A Unified Resource Identifier (URI) for the term represented by this field.
- For example, a field containing the scientific name would have term="http://rs.tdwg.org/dwc/terms/scientificName".
- Terms outside of the Darwin Core specification may be used, such as those from the Dublin Core Metadata Initative, for example, dcterms:modified would be term="http://purl.org/dc/terms/modified".
-
-
✓
-
-
-
-
default
-
Specifies value to use if one is not supplied for the field in a given row. If no index is supplied, the default can be used to define a constant for all rows for a field that is not in the data file.
-
-
-
-
-
vocabulary
-
A Unified Resource Identifier (URI) for a vocabulary that the source values for this field are based on.
- The URI ideally should resolve to some machine readable definition like SKOS, RDF or at least some simple text or html file
- often found for ISO or RFC standards.
- For example
- http://rs.gbif.org/vocabulary/gbif/nomenclatural_code.xml,
- http://www.ietf.org/rfc/rfc3066.txt
- or http://www.iso.org/iso/list-en1-semic-3.txt
- .
-
-
-
-
-
-
+
The description of legacy data existing in a fielded text
+ format, such that it might be automatically understood and loaded into
+ another system. It could be that this system would then serve the data in
+ another format such as XML.
+
+
+
2. Metafile Content
-
-
3. Implementation Guide
-
3.1 Extension example
-The following example illustrates the use of extensions. In this example there are three files in the archive, all of which
-are located in the same directory as the metafile. The whales.txt file acts as a core file of Taxon records. The whales.txt file
-is extended by two other files, types.txt and distribution.txt. The types.txt file contains records of a type specified in an
-external definition at http://http://rs.gbif.org/terms/1.0/Types and consists of Dublin Core and Darwin Core terms, while the
-distribution.txt file contains records of a type specified at http://http://rs.gbif.org/terms/1.0/Distribution and consists of
-Darwin Core terms plus an additional term for threatStatus. Both extension files are related to the core file by the taxonNameID fields.
-Presumably, this archive contains information about whale species, type specimen records for those species, and lists of countries and
-the threat status for those species.
+
The text metafile schema [TEXTSCHEMA] provides technical details
+ for the structure of a metafile by defining the elements and attributes
+ required to describe the contents and relationships between text files. These
+ elements and attributes, with descriptions and specifications for their use
+ in a metafile, are described in the following table.
+
2.1 The <archive> element
The <archive> element is the
+ container for the list of related files (one core and zero or more
+ extensions). The <archive> element has just one attribute,
+ metadata.
-
-
-
-
+ Attributes
+
+
+
+
+
Attribute
+
+
Description
+
+
Required
+
+
Default
+
+
+
+
+
+
metadata
+
+
Contains a qualified Uniform Resource Locator (URL) defining the
+ location of a metadata description of the entire archive. The format of
+ the metadata is not prescribed, but a standardized format such as
+ Ecological Metadata Language (EML), Federal Geographic Data Committee
+ (FGDC), or ISO 19115 family is recommended.
+ An <archive> must contain exactly one <core> element, representing the data entity
+ (the actual file and its column header mappings to Darwin Core terms)
+ upon which records are based.
+ If extensions are being used, each record in the core data must have
+ a unique identifier. The field for this identifier must be specified
+ in an explicit <id> field in order to associate extension
+ records with the core record.
+
+ An <archive> may define zero or more <extension> elements, each representing an
+ individual extension entity directly related to the core. In addition
+ to the general file attributes described below, every extension
+ entity must have an explicit <coreId> field to relate the
+ extension record to a row in the core entity. The extension itself
+ does not have to have a unique ID field and many rows can point to
+ the same core record.
+
+ A Unified Resource Identifier (URI) for the term identifying the
+ class of data represented by each row, for example,
+ http://rs.tdwg.org/dwc/terms/Occurrence for Occurrence records or
+ http://rs.tdwg.org/dwc/terms/Taxon for Taxon records. Additional
+ classes may be referenced by URI and defined outside the Darwin Core
+ specification. The row type defaults to the ambiguous
+ SimpleDarwinRecord. For convenience the URIs for classes defined by
+ the Darwin Core are listed below:
+
+
Specifies the delimiter between fields. Typical values might be ","
+ or "\t" for CSV or Tab files respectively.
+
+
+
,
+
+
+
+
linesTerminatedBy
+
+
Specifies the row separator character.
+
+
+
\n
+
+
+
+
fieldsEnclosedBy
+
+
Specifies the character used to enclose (mark the start and end of)
+ each field. CSV files frequently use the double quote character
+ ("), but the default is no enclosing character. Note that a comma
+ separated value file that has commas within the content of any field
+ must have an enclosing character.
+
+
+
"
+
+
+
+
encoding
+
+
+ Specifies the character
+ encoding for the data file. The encoding is extremely important,
+ but often ignored. The most frequently used encodings are:
+
+
+
UTF-8
+
+
8-bit Unicode Transformation Format.
+
+
UTF-16
+
+
16-bit Unicode Transformation Format.
+
+
ISO-8859-1
+
+
Commonly known as Latin-1 and a common default on systems
+ configured for a single western European language.
+
+
Windows-1252
+
+
Commonly known as WinLatin and a common default of legacy
+ versions of Microsoft Windows based operating systems.
+
+
+
+
+
UTF-8
+
+
+
+
ignoreHeaderLines
+
+
Specifies the number lines to ignore from the beginning of the
+ file. This can be used to ignore files with column headings or preamble
+ comments for example.
+
+
+
0
+
+
+
+
dateFormat
+
+
+ When verbatim dates are consistent in format, this field can be used
+ to indicate the format represented. It is recommended to use the
+ date, dateTime and time for field formats wherever possible, but
+ where verbatim dates are required, a format may be specified here.
+ This should be considered a 'hint' for consumers. It is recommended
+ that consumers support the minimum combinations of DD MM and YYYY
+ with the separators / and -. Examples:
+
+
+ <core> or <extension> element must contain one <files> element to locate the data being
+ described.
+
+
+
+
+
<id>
+
+
+ If extensions are being used, the <core>
+ must contain an <id> element that indicates the identifier for
+ a record.
+
+
+
+
+
<coreId>
+
+
+ If extensions are being used, the <extension> element must contain a
+ <coreId> element that indicates the column in the extension
+ file that contains the core record identifier (the matching
+ <id> in the core file).
+
The files element must contain one or more <location> elements, each
+ defining where a file resides. Each core or extension entity can be composed
+ from one or more files. If an entity has data in more than one file, use the
+ <location> element multiple times, once for each file that makes up the
+ entity.
+
+ Elements
+
+
+
+
+
Element
+
+
Description
+
+
+
+
+
+
location
+
+
+ Specifies the location of the file being described, which may take
+ either of the following forms:
+
+
+
A web accessible URL such as
+ "http://www.gbif.org/data/specimen.csv" or
+ "ftp://ftp.gbif.org/tim/specimen.txt".
+
+
A filepath relative to the location of the metafile such as
+ "specimen.txt","./specimen.txt", "data/specimen.txt".
The field element is used to specify the location and content
+ of data within a file. There must be one field element for every term being
+ shared for the entity, whether explicitly or through the use of a default
+ value for all rows in the file.
+
+ Attributes
+
+
+
+
+
Attribute
+
+
Description
+
+
Required
+
+
Default
+
+
+
+
+
+
index
+
+
Specifies the position of the column in the row. The first column
+ has an index of 0, the second column 1, etc. If no column index is
+ specified, then the term and the default may be used to define a
+ constant value for all rows.
+
+
+
+
+
+
term
+
+
A Unified Resource Identifier (URI) for the term represented by
+ this field. For example, a field containing the scientific name would
+ have term="http://rs.tdwg.org/dwc/terms/scientificName".
+ Terms outside of the Darwin Core specification may be used, such as
+ those from the Dublin Core Metadata Initative, for example,
+ dcterms:modified would be
+ term="http://purl.org/dc/terms/modified".
+
+
✓
+
+
+
+
+
default
+
+
Specifies value to use if one is not supplied for the field in a
+ given row. If no index is supplied, the default can be used to define a
+ constant for all rows for a field that is not in the data file.
+
+
+
+
+
+
vocabulary
+
+
A Unified Resource Identifier (URI) for a vocabulary that the
+ source values for this field are based on. The URI ideally should
+ resolve to some machine readable definition like SKOS, RDF or at least
+ some simple text or html file often found for ISO or RFC standards. For
+ example http://rs.gbif.org/vocabulary/gbif/nomenclatural_code.xml,
+ http://www.ietf.org/rfc/rfc3066.txt or
+ http://www.iso.org/iso/list-en1-semic-3.txt .
+
+
+
+
+
+
+
+
+
3. Implementation Guide
+
+
3.1 Extension example
The following example illustrates the use of
+ extensions. In this example there are three files in the archive, all of
+ which are located in the same directory as the metafile. The whales.txt file
+ acts as a core file of Taxon records. The whales.txt file is extended by two
+ other files, types.txt and distribution.txt. The types.txt file contains
+ records of a type specified in an external definition at
+ http://http://rs.gbif.org/terms/1.0/Types and consists of Dublin Core and
+ Darwin Core terms, while the distribution.txt file contains records of a type
+ specified at http://http://rs.gbif.org/terms/1.0/Distribution and consists of
+ Darwin Core terms plus an additional term for threatStatus. Both extension
+ files are related to the core file by the taxonNameID fields. Presumably,
+ this archive contains information about whale species, type specimen records
+ for those species, and lists of countries and the threat status for those
+ species.
+
+
<?xml version="1.0" encoding="UTF-8"?>
<archive xmlns="http://rs.tdwg.org/dwc/text/"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xs="http://www.w3.org/2001/XMLSchema"
- xsi:schemaLocation="http://rs.tdwg.org/dwc/text/ http://rs.tdwg.org/dwc/text/tdwg_dwc_text.xsd">
-
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns:xs="http://www.w3.org/2001/XMLSchema"
+ xsi:schemaLocation="http://rs.tdwg.org/dwc/text/ http://rs.tdwg.org/dwc/text/tdwg_dwc_text.xsd">
+
<core encoding="UTF-8" fieldsTerminatedBy="\t" linesTerminatedBy="\n" ignoreHeaderLines="1"
rowType="http://rs.tdwg.org/dwc/terms/Taxon">
<files>
@@ -500,7 +845,7 @@ the threat status for those species.
<field index="4" term="http://rs.tdwg.org/dwc/terms/parentNameUsageID"/>
<field index="5" term="http://rs.tdwg.org/dwc/terms/originalNameUsageID"/>
</core>
-
+
<extension encoding="UTF-8" fieldsTerminatedBy="," linesTerminatedBy="\n" fieldsEnclosedBy='"' ignoreHeaderLines="1"
rowType="http://rs.gbif.org/terms/1.0/Types">
<files>
@@ -513,7 +858,7 @@ the threat status for those species.
<field index="4" term="http://rs.tdwg.org/dwc/terms/institutionCode"/>
<field index="5" term="http://rs.tdwg.org/dwc/terms/typeStatus"/>
</extension>
-
+
<extension encoding="UTF-8" fieldsTerminatedBy="," linesTerminatedBy="\n" fieldsEnclosedBy='"' ignoreHeaderLines="1"
rowType="http://rs.gbif.org/terms/1.0/Distribution">
<files>
@@ -525,17 +870,17 @@ the threat status for those species.
<field index="3" term="http://rs.tdwg.org/dwc/terms/occurrenceStatus"/>
</extension>
</archive>
-
+
-
-
4. Database Example
-
4.1 MySQL
-It is very easy to produce fielded text using the SELECT INTO outfile command from MySQL. The encoding of the
-resulting file will depend on the server variables and collations used, and might need to be modified before
-the operation is done. Note that MySQL will export NULL values as \N by default. Use the IFNULL() function as shown in the following
-example to avoid this.
+
4. Database Example
-
+
4.1 MySQL
It is very easy to produce fielded text using the
+ SELECT INTO outfile command from MySQL. The encoding of the
+ resulting file will depend on the server variables and collations used, and
+ might need to be modified before the operation is done. Note that MySQL will
+ export NULL values as \N by default. Use the IFNULL() function as shown in
+ the following example to avoid this.
+
SELECT
IFNULL(id, ''), IFNULL(scientific_name, ''), IFNULL(count,'')
INTO outfile '/tmp/dwc.txt'
@@ -544,27 +889,32 @@ SELECT
LINES TERMINATED BY '\n'
FROM
dwc;
-
+
-
-
5. Tools
-
For tools and applications, including a Java-based application to read Darwin Core text archives, see the the Darwin Core Tools and Applications Wiki
-page [TOOLS].
+
5. Tools
-
-
-
-
- Copyright 2009 - Biodiversity Information Standards - TDWG - Contact Us
-
For tools and applications, including a Java-based application to read
+ Darwin Core text archives, see the Darwin Core Tools and Applications
+ page [TOOLS].
-Audience: This document is targeted toward those who wish to use or construct application schemas using Darwin Core terms in XML.
-It includes explanations of existing schemas such as the Simple Darwin Core [SIMPLEDWC] and how
-to build new schemas to meet specific models of information.
-
-This document provides guidelines for implementing application schemas based on Darwin Core terms
-[TERMS] using [XML]. The underlying metadata
-model is described (in a syntax neutral way), followed by some specific guidelines for XML implementations. Some guidance
-on the use of non-Darwin Core terms is also provided.
-
-This document does not provide guidelines for encoding Darwin Core in RDF/XML. Nor does it take a position on the
-relative merits of encoding metadata in 'plain' XML rather than RDF/XML. This document provides guidelines in those
-cases where RDF/XML is not considered appropriate.
+
+
Darwin Core XML Guide
-
-
2. Implementation Guide
-
+
-
-
2.1 XML Schema
-Implementors should base their XML applications on XML Schemas
-[XMLSCHEMA] rather than XML DTDs. Approaches
-based on XML Schemas are more flexible and are more easily re-used within other XML applications.
-
-
-
2.2 XML Namespaces
-Implementors should use XML Namespaces
-[XMLNS] to uniquely identify elements.
-Darwin Core namespaces are defined in the Darwin Core Namespace Policy
-[NAMESPACEPOLICY], while Dublin Core namespaces are defined in the
-DCMI Namespace Recommendation [DCMINS].
-
-
-
2.3 Abstract model
-
-The Darwin Core follows the Dublin Core Metadata Initiative Abstract Model [ABSTRACTMODEL]
-except that the Darwin Core record is roughly equivalent to the Dublin Core resource.
-
-
Darwin Core terms are either classes or properties.
-
Each property has at most one class as its domain (describes no more than one class).
-
A Darwin Core record is made up of zero or more classes and one or more properties with their associated values.
-
Each value is a literal string.
-
The values of properties within a Darwin Core record describe that record.
-
A Darwin Core record must include all required properties, if any, and their associated values.
-
-
-
-
-
2.4 Properties and Values
-
The Darwin Core follows the guidelines for expressing Dublin Core metadata using XML
-[DCMIXMLGUIDE] except in that
-Darwin Core implementors should encode properties as XML elements and values
-as the content of those elements instead of having each property contain a value representation and its associated value.
-The name of the XML element should be an XML qualified name (QName), which associates the value given in the Term name
-attribute in the Darwin Core Terms recommendation
-[TERMS] with the appropriate namespace name. For example, use
-
The Darwin Core follows the guidelines for expressing Dublin Core metadata
+ using XML [DCMIXMLGUIDE] except in that
+ Darwin Core implementors should encode properties as XML elements
+ and values as the content of those elements instead of having each
+ property contain a value representation and its associated value. The name of
+ the XML element should be an XML qualified name (QName), which associates the
+ value given in the Term name attribute in the Darwin Core Terms
+ recommendation [TERMS] with the appropriate
+ namespace name. For example, use
-Elements for which the value is null should be omitted from the document or explicitly coded using the
-attribute xsi:nil="true".
-
<dwc:locality xsi:nil="true"/>
-Do not use an empty string - an element with no content:
-
<dwc:locality></dwc:locality>
+
-
-
-
-
2.6 Simple Darwin Core
-
-The Simple Darwin Core [SIMPLEXMLSCHEMA] most closely models the "flat" nature of many data sets. It
-is a ready-made schema for sharing information with no structure beyond properties of a record (equivalent to fields in a table, or columns
-in a spreadsheet). It is meant to accommodate all properties except those that require further structure to be meaningful
-(auxilliary terms in the classes ResourceRelationship and
-MeasurementOrFact. The schema has no required terms and no term is repeated within a given
-record. Refer to the Simple Darwin Core page [SIMPLEDWC]
-for the rationale behind this schema.
-
-Occurrence, Taxon, Event, and Location records can be constructed using an appropriate
-values of dcterms:type (which is controlled by the Dublin Core Type Vocabulary
-[DCMI-TYPE]) to describe the Class that is the root of the record. Use the
-basisOfRecord (having a separate controlled vocabulary, Darwin Core Type Vocabulary
-[DWC-TYPE]) to describe the specific type of
-record (various types of specimens, media, taxon records, etc.).
-
-Following is a brief example of an XML document for a single specimen complying with the Simple Darwin Core Schema
-[SIMPLEXMLSCHEMA]. The Simple Darwin Core XML example document
-[SIMPLEXMLEXAMPLE] (if this link shows a blank page in
-your browser, use the View Source option to see the XML document) shows
-detail for a single record having a more complete set of elements.
+
-
<?xml version="1.0"?>
+
2.6 Simple Darwin Core
+
+
The Simple Darwin Core [SIMPLEXMLSCHEMA] most closely models
+ the "flat" nature of many data sets. It is a ready-made schema for sharing
+ information with no structure beyond properties of a record
+ (equivalent to fields in a table, or columns in a spreadsheet). It is meant
+ to accommodate all properties except those that require further structure to
+ be meaningful (auxilliary terms in the classes ResourceRelationship and MeasurementOrFact. The schema has no
+ required terms and no term is repeated within a given record. Refer
+ to the Simple Darwin Core page [SIMPLEDWC] for the rationale behind this
+ schema.
+
+
The term dcterms:type (which is
+ controlled by the Dublin Core Type Vocabulary [DCMI-TYPE]),
+ gives the basic category of object (PhysicalObject, StillImage, MovingImage,
+ Sound, or Text) the record is about. The term basisOfRecord, which has a controlled
+ vocabulary distinct from that of dcterms:type, shows the name of the
+ Darwin Core class (e.g., LivingSpecimen, PreservedSpecimen, FossilSpecimen,
+ HumanObservation, MachineObservation, Taxon) the record is about.
+
+
Following is a brief example of an XML document for a single specimen
+ complying with the Simple Darwin Core Schema [SIMPLEXMLSCHEMA]. The Simple Darwin
+ Core XML example document [SIMPLEXMLEXAMPLE] (if this
+ link shows a blank page in your browser, use the View Source option to see
+ the XML document) shows detail for a single record having a more complete set
+ of elements.
+
+<?xml version="1.0"?>
<dwr:SimpleDarwinRecordSet
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://rs.tdwg.org/dwc/xsd/simpledarwincore/ http://rs.tdwg.org/dwc/xsd/tdwg_dwc_simple.xsd"
@@ -290,42 +492,57 @@ detail for a single record having a more complete set of elements.
<dwc:locality>25 km al NNE de Bariloche por Ruta 40 (=237)</dwc:locality>
</dwr:SimpleDarwinRecord>
</dwr:SimpleDarwinRecordSet>
-
-
+
-
-
-
2.7 Classes and Containment
-
-Many Darwin Core terms (properties) are defined as being associated with another term (a class).
-For example, scientificName and
-Taxon are both Darwin Core terms, and scientificName is associated with the Taxon class.
-When constructing schemas that take advantage of classes in structures, implementors are encouraged to maintain the
-property/class relationships defined by the terms whenever possible (refer to the Class attribute of the term as
-given in the Quick Reference Guide [TERMS]). To promote reuse, Darwin Core provides
-a set of xml schemas to use as the basis of additional schemas:
-
-
[TERMSXMLSCHEMA] - property term definitions as typed global
-elements and named groups for all terms for a given class to be referenced. The schema makes use of substitution
-groups anyClass, anyProperty, anyIdentifier and anyXYZTerm for each class, e.g. anyTaxonTerm. This is the schema
-upon which the Simple Darwin Core XML Schema
-[SIMPLEXMLSCHEMA] is based.
-
-
[CLASSTERMSXMLSCHEMA] - class term definitions as typed global
-elements with subelements referencing all corresponding property terms via their substitution group.
-
-
-
-It is encouraged to use classes in a normalized way to avoid deep nesting. A Darwin Core Tools and Applications wiki page
-[TOOLS] has been created as an index to example schemas
-for the purpose of community discussions and development.
+
-An XML schema [CLASSXMLSCHEMA] is provided to freely mix any Darwin
-Core Class in a global list and allow them to reference each other using the respective class
-identifier terms. Following is an example of using normalized classes to represent two related specimen occurrences
-(one of which has had a second identification) at one location following this class-based schema. Note that you can
-reuse the location definition here by referring to it via locationID:
-
+
2.7 Classes and Containment
+
+
Many Darwin Core terms (properties) are defined as being associated
+ with another term (a class). For example, scientificName and Taxon are both Darwin Core terms, but
+ scientificName is a property associated with the Taxon class.
+ When constructing schemas that take advantage of classes in structures,
+ implementors are encouraged to maintain the property/class relationships
+ defined by the terms whenever possible (refer to the Class attribute
+ of the term as given in the Quick Reference Guide [TERMS]) or the attribute
+ dwcattributes:organizedInClass in the term declaration in the dcterms.rdf file. To promote reuse, Darwin
+ Core provides a set of xml schemas to use as the basis of additional
+ schemas:
+
+
+
[TERMSXMLSCHEMA] -
+ property term definitions as typed global elements and named groups for all
+ terms for a given class to be referenced. The schema makes use of
+ substitution groups anyClass, anyProperty, anyIdentifier and anyXYZTerm for
+ each class, e.g. anyTaxonTerm. This is the schema upon which the Simple
+ Darwin Core XML Schema [SIMPLEXMLSCHEMA] is based.
+
+
+
[CLASSTERMSXMLSCHEMA] - class
+ term definitions as typed global elements with subelements referencing all
+ corresponding property terms via their substitution group.
+
+
+
+
It is encouraged to use classes in a normalized way to avoid deep nesting.
+ A Darwin Core Tools and Applications wiki page [TOOLS]
+ has been created as an index to example schemas for the purpose of community
+ discussions and development. An XML schema [CLASSXMLSCHEMA] is provided to freely
+ mix any Darwin Core Class in a global list and allow them to reference each
+ other using the respective class identifier terms. Following is an example of
+ using normalized classes to represent two related specimen occurrences (one
+ of which has had a second identification) at one location following this
+ class-based schema. Note that you can reuse the location definition here by
+ referring to it via locationID:
+
<?xml version="1.0"?>
<dwr:DarwinRecordSet
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -343,8 +560,6 @@ reuse the location definition here by referring to it via locationID:
<dwc:Occurrence>
<dcterms:type>PhysicalObject</dcterms:type>
<dcterms:modified>2009-02-12T12:43:31</dcterms:modified>
- <dcterms:rightsHolder>Museum of Vertebrate Zoology</dcterms:rightsHolder>
- <dcterms:rights>Creative Commons License</dcterms:rights>
<dwc:institutionCode>MVZ</dwc:institutionCode>
<dwc:collectionCode>Mammals</dwc:collectionCode>
<dwc:occurrenceID>urn:catalog:MVZ:Mammals:14523</dwc:occurrenceID>
@@ -392,8 +607,6 @@ reuse the location definition here by referring to it via locationID:
<dwc:Occurrence>
<dcterms:type>PhysicalObject</dcterms:type>
<dcterms:modified>2009-02-12T12:43:31</dcterms:modified>
- <dcterms:rightsHolder>Museum of Vertebrate Zoology</dcterms:rightsHolder>
- <dcterms:rights>Creative Commons License</dcterms:rights>
<dwc:institutionCode>MVZ</dwc:institutionCode>
<dwc:collectionCode>Mammals</dwc:collectionCode>
<dwc:occurrenceID>urn:catalog:MVZ:Mammals:14524</dwc:occurrenceID>
@@ -420,11 +633,11 @@ reuse the location definition here by referring to it via locationID:
<dwc:relationshipOfResource>mother of</dwc:relationshipOfResource>
</dwc:ResourceRelationship>
</dwr:DarwinRecordSet>
-
-
-Here is different example demonstrating area count observations for events on two different days at one location.
-Note that we omit the identification class here as there is not identification related data and link via the taxonID directly:
-
+
Here is different example demonstrating area count observations for
+events on two different days at one location. Note that we omit the
+identification class here as there is not identification related data and link
+via the taxonID directly:
+
<?xml version="1.0"?>
<dwr:DarwinRecordSet
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -453,8 +666,6 @@ Note that we omit the identification class here as there is not identification r
<dwc:occurrenceID>urn:catalog:AUDCLO:EBIRD:OBS64515288</dwc:occurrenceID>
<dcterms:type>Event</dcterms:type>
<dcterms:modified>2009-02-17T07:33:04Z</dcterms:modified>
- <dcterms:rightsHolder>Avian Knowledge Network</dcterms:rightsHolder>
- <dcterms:rights>Creative Commons License</dcterms:rights>
<dwc:institutionCode>AUDCLO</dwc:institutionCode>
<dwc:collectionCode>EBIRD</dwc:collectionCode>
<dwc:basisOfRecord>HumanObservation</dwc:basisOfRecord>
@@ -473,8 +684,6 @@ Note that we omit the identification class here as there is not identification r
<dwc:occurrenceID>urn:catalog:AUDCLO:EBIRD:OBS64515286</dwc:occurrenceID>
<dcterms:type>Event</dcterms:type>
<dcterms:modified>2009-02-17T07:33:04Z</dcterms:modified>
- <dcterms:rightsHolder>Avian Knowledge Network</dcterms:rightsHolder>
- <dcterms:rights>Creative Commons License</dcterms:rights>
<dwc:institutionCode>AUDCLO</dwc:institutionCode>
<dwc:collectionCode>EBIRD</dwc:collectionCode>
<dwc:basisOfRecord>HumanObservation</dwc:basisOfRecord>
@@ -499,8 +708,6 @@ Note that we omit the identification class here as there is not identification r
<dwc:occurrenceID>urn:catalog:AUDCLO:EBIRD:OBS64515333</dwc:occurrenceID>
<dcterms:type>Event</dcterms:type>
<dcterms:modified>2009-02-17T07:33:04Z</dcterms:modified>
- <dcterms:rightsHolder>Avian Knowledge Network</dcterms:rightsHolder>
- <dcterms:rights>Creative Commons License</dcterms:rights>
<dwc:institutionCode>AUDCLO</dwc:institutionCode>
<dwc:collectionCode>EBIRD</dwc:collectionCode>
<dwc:basisOfRecord>HumanObservation</dwc:basisOfRecord>
@@ -512,8 +719,6 @@ Note that we omit the identification class here as there is not identification r
<dwc:occurrenceID>urn:catalog:AUDCLO:EBIRD:OBS64515331</dwc:occurrenceID>
<dcterms:type>Event</dcterms:type>
<dcterms:modified>2009-02-17T07:33:04Z</dcterms:modified>
- <dcterms:rightsHolder>Avian Knowledge Network</dcterms:rightsHolder>
- <dcterms:rights>Creative Commons License</dcterms:rights>
<dwc:institutionCode>AUDCLO</dwc:institutionCode>
<dwc:collectionCode>EBIRD</dwc:collectionCode>
<dwc:basisOfRecord>HumanObservation</dwc:basisOfRecord>
@@ -523,22 +728,24 @@ Note that we omit the identification class here as there is not identification r
</dwc:Occurrence>
</dwr:DarwinRecordSet>
-Audience: This document is targeted toward those who wish to understand the reasoning behind changes (or rejections of proposed
-changes) to the Darwin Core terms.
-
-From time to time changes are proposed to Darwin Core terms through the process described in the Term Change Policy
-section of the Darwin Core Namespace Policy [NAMESPACEPOLICY]. This document shows the outcome of
-decisions based on officially proposed changes.
+
The recommended controlled vocabulary for dcterms:type was changed from a vocabulary of Darwin Core Classes (Occurrence, Taxon, Location, Event) to the DCMI type vocabulary (PhysicalObject, Event, StillImage, MovingImage, Sound, Text, Dataset) to be consistent with the standard use of that term.
The recommended controlled vocabulary for basisOfRecord remains the Darwin Core Type Vocabulary, but the Dublin Core classes StillImage, MovingImage, and Sound were removed from that list as these are to be used as vocabulary for the dcterms:type term.
The Dublin Core type vocabulary values StillImage, MovingImage, and Sound have not been added to the list of valid values for Darwin Core type vocabulary pending further insights from the RDF Interest Group about how best to manage basisOfRecord when a record can be "about" more than one subject.
The recommendation to add alias as an attribute of Darwin Core terms was rejected as being an application-specific recommendation without sufficiently demonstrated community need.
The label for all terms have been changed to words in English rather than lower camel case term names. This will facilitate discovery with search engines and is consistent with Dublin Core.
The subclasses for Darwin Core type vocabulary have been removed. These were seen as too constraining when considering biodiversity information in the context of linked data.
The term Darwin Core term dwc:occurrenceDetails has been deprecated in favor of a new record-level term from the Dublin Core - dcterms:references, which is broader in meaning than the deprecated term.
Audience: This document is targeted toward
+ those who wish to understand the reasoning behind changes (or rejections of
+ proposed changes) to the Darwin Core terms.
+
+
From time to time changes are proposed to Darwin Core terms through the
+ process described in the Term Change Policy section of the Darwin Core
+ Namespace Policy [NAMESPACEPOLICY]. This document shows the
+ outcome of decisions based on officially proposed changes.
The recommended controlled vocabulary for dcterms:type was changed
+ from a vocabulary of Darwin Core Classes (Occurrence, Taxon, Location,
+ Event) to the DCMI type vocabulary (PhysicalObject, Event, StillImage,
+ MovingImage, Sound, Text, Dataset) to be consistent with the standard
+ use of that term.
The recommended controlled vocabulary for basisOfRecord remains the
+ Darwin Core Type Vocabulary, but the Dublin Core classes StillImage,
+ MovingImage, and Sound were removed from that list as these are to be
+ used as vocabulary for the dcterms:type term.
The Dublin Core type vocabulary values StillImage, MovingImage, and
+ Sound have not been added to the list of valid values for Darwin Core
+ type vocabulary pending further insights from the RDF Interest Group
+ about how best to manage basisOfRecord when a record can be "about"
+ more than one subject.
The recommendation to add alias as an attribute of Darwin Core
+ terms was rejected as being an application-specific recommendation
+ without sufficiently demonstrated community need.
The label for all terms have been changed to words in English
+ rather than lower camel case term names. This will facilitate discovery
+ with search engines and is consistent with Dublin Core.
The subclasses for Darwin Core type vocabulary have been removed.
+ These were seen as too constraining when considering biodiversity
+ information in the context of linked data.
The term Darwin Core term dwc:occurrenceDetails has been deprecated
+ in favor of a new record-level term from the Dublin Core -
+ dcterms:references, which is broader in meaning than the deprecated
+ term.
Added class term Organism with associated properties organismID,
+ organismName, organismScope, organismRemarks, and associatedOrganisms.
+ Associated terms previousIdentifications and associatedOccurrences with
+ the new Organism class. Removed the individualID term.
Deprecated the Darwin Core Type Vocabulary
+ (http://rs.tdwg.org/dwc/dwctype) in favor of the corresponding terms in
+ the dwc namespace (http://rs.tdwg.org/dwc/terms). Added terms
+ PreservedSpecimen, LivingSpecimen, FossilSpecimen, MachineObservation,
+ and HumanObservation to the Darwin Core namespace
+ (http://rs.tdwg.org/dwc/terms).
Added comments recommending list value separation with ' | ' for
+ terms that can be constructed from concatenated lists. Added comment
+ recommending that dynamicProperties be populated with JSON.
Deprecated the Dublin Core rights term in favor of the Dublin Core
+ license term, which is how rights was being promoted since it was first
+ recommended for use in Darwin Core.
This document is a quick reference for mappings between elements in pre-standard Darwin Core
-versions and the Access to Biological Collections Data [ABCD] schema. For complete historical Darwin Core
-term information, including version changes and details on pre-standard terms, see [HISTORY].
-For a quick reference guide to the current recommended Darwin Core terms, see [TERMS].
-
-
-
Contributors:
-
John Wieczorek (MVZ), Éamonn Ó Tuama (GBIF), Andrea Hahn (GBIF), Jörg Holetschek (BGBM)
-
-
-
Legal:
-
This document is governed by the standard legal, copyright, licensing provisions and disclaimers issued by the Taxonomic Databases Working Group.
-Audience: This document is targeted toward those who wish to understand how the Darwin Core terms are related to the structure
-of the Access to Biological Collections Data [ABCD] schema.
-
-Before becoming a TDWG standard, the Darwin Core was instantiated and deployed in many different
-application profiles, all of them based on XML schema. In this document the openly developed and
-widely used versions of the Darwin Core ([CLASSIC],
-[MANIS],
-[OBIS],
-[DRAFT14],
-[CURATORIAL],
-[GEOSPATIAL]) are each compared (mapped conceptually) to the
-Access to Biological Collections Data [ABCD] schema. Each historical
-version is mapped in a separate table and can be referenced quickly from the index in Mappings section.
-Each element in each Darwin Core versions is mapped to the one or more xpath designations of the equivalent element(s) in
-the most current version of ABCD.
+
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Genus
-
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstE
-
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Sec
-
DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/ISOAccuracy or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/AccuracyStatement
2.3 Darwin Core 1.21 (MaNIS/HerpNet/ORNIS/FishNet2)
-
-
Darwin Core 1.21 Element
ABCD xpath
+
+ This document is a quick reference for mappings between
+ elements in pre-standard Darwin Core versions and the Access
+ to Biological Collections Data [ABCD] schema. For
+ complete historical Darwin Core term information, including
+ version changes and details on pre-standard terms, see
+ [HISTORY]. For a quick reference
+ guide to the current recommended Darwin Core terms, see
+ [TERMS].
+
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Genus
-
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstE
-
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Sec
-
{DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLifeStages/MycologicalLifeStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage}
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Genus
-
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstE
-
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Sec
-
{DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinatesText or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesUTM/UTMText}
{DataSets/DataSet/Units/Unit/Owner/Organisation/Name/Representation/Text or DataSets/DataSet/Units/Unit/Owner/Person/FullName or DataSets/DataSet/Metadata/Owners/Owner/Organisation/Name/Representation/Text or DataSets/DataSet/Metadata/Owners/Owner/Person/FullName}
{DataSets/DataSet/Units/Unit/RecordURI or Datasets/Dataset/Units/Unit/UnitReferences/UnitReferences or Datasets/Dataset/Units/Unit/SourceReference or Datasets/Dataset/Units/Unit/Identifications/Identification/References/Reference or Datasets/Dataset/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference or MeasurementOrFact/MeasurementOrFactAtomised/MeasurementOrFactReference}
DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/NameAtomised/Zoological/NamedIndividual or DataSets/DataSet/Units/Unit/ObservationUnit/ObservationUnitIdentifiers/ObservationUnitIdentifier or DataSets/DataSet/Units/Unit/SpecimenUnit/Accessions/AccessionNumber
DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLiveStages/MycologicalLiveStage (Note DwC spec uses ”MycologicalLifeStage” or DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage
{DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinatesText or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesUTM/UTMText}
DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/ISOAccuracy or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/AccuracyStatement
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
/DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Method or /DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Method or /DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Method
Audience: This document is targeted toward
+ those who wish to understand how the Darwin Core terms are related to the
+ structure of the Access to Biological Collections Data [ABCD] schema.
-
\ No newline at end of file
+
Before becoming a TDWG standard, the Darwin Core was instantiated and
+ deployed in many different application profiles, all of them based on XML
+ schema. In this document the openly developed and widely used versions of the
+ Darwin Core ([CLASSIC],
+ [MANIS],
+ [OBIS], [DRAFT14], [CURATORIAL], [GEOSPATIAL]) are each
+ compared (mapped conceptually) to the Access to Biological Collections Data
+ [ABCD] schema. Each
+ historical version is mapped in a separate table and can be referenced
+ quickly from the index in Mappings section. Each
+ element in each Darwin Core versions is mapped to the one or more xpath
+ designations of the equivalent element(s) in the most current version of
+ ABCD.
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
+ {DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage
+ or
+ DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLifeStages/MycologicalLifeStage
+ or
+ DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage}
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
+ {DataSets/DataSet/Units/Unit/Owner/Organisation/Name/Representation/Text
+ or DataSets/DataSet/Units/Unit/Owner/Person/FullName or
+ DataSets/DataSet/Metadata/Owners/Owner/Organisation/Name/Representation/Text
+ or DataSets/DataSet/Metadata/Owners/Owner/Person/FullName}
{DataSets/DataSet/Units/Unit/RecordURI or
+ Datasets/Dataset/Units/Unit/UnitReferences/UnitReferences or
+ Datasets/Dataset/Units/Unit/SourceReference or
+ Datasets/Dataset/Units/Unit/Identifications/Identification/References/Reference
+ or
+ Datasets/Dataset/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference
+ or
+ MeasurementOrFact/MeasurementOrFactAtomised/MeasurementOrFactReference}
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
+ with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial
+ or
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial
+ or
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial
+ or
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet
+ or
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet
+ or
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
+ {DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet
+ or
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet
+ or
+ DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
+ (DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference/TitleCitation)
+ pro parte
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue
+ or
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue
+ or
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue
+ or
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
+ or
+ DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy
+ or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy
+ or
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy
+ or
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
+ DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime
+ or
+ DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime
+ or
+ DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
+ /DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Method
+ or
+ /DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Method
+ or
+ /DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Method
This document is an authoritative specification of all terms in all of their historical versions as maintained by the
-Darwin Core Task Group. While this document is useful for complete information and for tracking changes in the status
-and attributes of terms over time, most users will need just the latest information, which is held in the document
-"Darwin Core Terms: A quick reference guide" [TERMS].
-
-
-
Contributors:
-
John Wieczorek (MVZ), Markus Döring (GBIF), Renato De Giovanni (CRIA), Tim Robertson (GBIF), Dave Vieglais (KUNHM)
-
-
-
Legal:
-
This document is governed by the standard legal, copyright, licensing provisions and disclaimers issued by the Taxonomic Databases Working Group.
-Audience: This document is targeted toward those who wish to understand the complete specification of the Darwin Core terms and
-their histories. Most users will not need the comprehensive historical detail presented here and should instead consult the document
-Darwin Core Terms: A quick reference guide [TERMS], for the most current basic information on
-recommended terms. Users who want the authoritative specification of the terms should consult the full Resource Description Framework
-[RDF] document.
-
-This document serves as a complete alphabetically ordered reference for all terms associated with the Darwin Core, including
-historical versions (Classic, MaNIS, OBIS, Draft Standard 1.4, Curatorial extension, Geospatial extension, Paleontology extension)
-prior to having a standard.
-
-Users interested in mappings from historical
-versions to the current standard may consult the document Darwin Core Versions
-[VERSIONS]. Users interested in mappings
-between the current recommended terms and the most recent schema for Access to Biological
-Collections Data should consult the document Darwin Core to ABCD Mapping
-[DWCTOABCD]. Mappings between historical versions and ABCD 2.06
-[ABCD] are contained in this document.
-
-
-
2. The Terms: Definitions
-
Following is the complete list of term attributes and their definitions:
-
-
-
-
-
-
Term Name:
-
The name by which the latest version of the term is commonly known.
-
-
-
Identifier:
-
The unique identifier for the latest version of the term.
-
-
-
Namespace:
-
The namespace (Darwin Core, Dublin Core) within which the term is defined. The combination of the namespace and the version make a unique identifier for the term.
-
-
-
Label:
-
The commonly used label for the term.
-
-
-
Definition:
-
A description of the nature of the content of the term.
-
-
-
Comment:
-
Further commentary about the usage of the term, with examples and a reference to further information.
-
-
-
Type of Term:
-
The category (property, class, vocabulary encoding scheme, or datatype - syntax encoding scheme) to which the term belongs.
-
-
-
Refines:
-
The name of a term of which this term is a refined (more specialized) version.
-
-
-
Status:
-
The status of the term - deprecated (not recommended for use), superseded (not recommended for use - replaced by
-the term or terms shown in the Is Replaced By column), or recommended (ready for use).
-
-
-
Date Issued:
-
Date on which the term was first published.
-
-
-
Date Modified:
-
Date on which the term was last changed in any way that would change its meaning or use.
-
-
-
Member Of:
-
The Class of which this term is a member.
-
-
-
Has Domain:
-
A Class of which a resource described by the term is a property.
-
-
-
Has Range:
-
A Class of which a value described by the term is an instance.
-
-
-
Decision:
-
The reference to the published decision that resulted in the current version of the term.
-
-
-
Version:
-
The identifier for the specific version of the term.
-
-
-
Replaces:
-
The identifier of the previous version of the term.
-
-
-
Is Replaced By:
-
The identifier of the next newer version of the term.
-
-
-
Class:
-
The primary category of terms (Class) that this term describes.
-
-
-
ABCD 2.06:
-
The xpath(s) to the equivalent concept(s) in the Access to Biological Collections Data schema version 2.06.
+ This document is an authoritative specification of all
+ terms in all of their historical versions as maintained by
+ the Darwin Core Task Group. While this document is useful
+ for complete information and for tracking changes in the
+ status and attributes of terms over time, most users will
+ need just the latest information, which is held in the
+ document "Darwin Core Terms: A quick reference
+ guide" [TERMS].
+
+
+
+
+
Contributors:
+
+
John Wieczorek (MVZ), Markus Döring (GBIF), Renato De
+ Giovanni (CRIA), Tim Robertson (GBIF), Dave Vieglais
+ (KUNHM)
+
+
+
+
Legal:
+
+
This document is governed by the standard legal,
+ copyright, licensing provisions and disclaimers issued by the
+ Taxonomic Databases Working Group.
Audience: This document is targeted toward
+ those who wish to understand the complete specification of the Darwin Core
+ terms and their histories. Most users will not need the comprehensive
+ historical detail presented here and should instead consult the document
+ Darwin Core Terms: A quick reference guide [TERMS], for the most current basic information on
+ recommended terms. Users who want the authoritative specification of the
+ terms should consult the full Resource Description Framework [RDF] document.
+
+
This document serves as a complete alphabetically ordered reference for
+ all terms associated with the Darwin Core, including historical versions
+ (Classic, MaNIS, OBIS, Draft Standard 1.4, Curatorial extension, Geospatial
+ extension, Paleontology extension) prior to having a standard.
+
+
Users interested in mappings from historical versions to the current
+ standard may consult the document Darwin Core Versions [VERSIONS]. Users interested in mappings between
+ the current recommended terms and the most recent schema for Access to
+ Biological Collections Data should consult the document Darwin Core
+ to ABCD Mapping [DWCTOABCD].
+ Mappings between historical versions and ABCD 2.06 [ABCD] are contained in this
+ document.
+
+
+
2. The Terms: Definitions
+
+
Following is the complete list of term attributes and their
+ definitions:
+
+
+
+
+
+
+
Term Name:
+
+
The name by which the latest version of the term is
+ commonly known.
+
+
+
+
Identifier:
+
+
The unique identifier for the latest version of the
+ term.
+
+
+
+
Namespace:
+
+
The namespace (Darwin Core, Dublin Core) within which
+ the term is defined. The combination of the namespace and the version
+ make a unique identifier for the term.
+
+
+
+
Label:
+
+
The commonly used label for the term.
+
+
+
+
Definition:
+
+
A description of the nature of the content of the
+ term.
+
+
+
+
Comment:
+
+
Further commentary about the usage of the term, with
+ examples and a reference to further information.
+
+
+
+
Type of Term:
+
+
The category (property, class, vocabulary encoding
+ scheme, or datatype - syntax encoding scheme) to which the term
+ belongs.
+
+
+
+
Refines:
+
+
The name of a term of which this term is a refined
+ (more specialized) version.
+
+
+
+
Status:
+
+
The status of the term - deprecated (not recommended
+ for use), superseded (not recommended for use - replaced by the term
+ or terms shown in the Is Replaced By column), or recommended
+ (ready for use).
+
+
+
+
Date Issued:
+
+
Date on which the term was first published.
+
+
+
+
Date Modified:
+
+
Date on which the term was last changed in any way
+ that would change its meaning or use.
+
+
+
+
Member Of:
+
+
The Class of which this term is a member.
+
+
+
+
Has Domain:
+
+
A Class of which a resource described by the term is
+ a property.
+
+
+
+
Has Range:
+
+
A Class of which a value described by the term is an
+ instance.
+
+
+
+
Decision:
+
+
The reference to the published decision that resulted
+ in the current version of the term.
+
+
+
+
Version:
+
+
The identifier for the specific version of the
+ term.
+
+
+
+
Replaces:
+
+
The identifier of the previous version of the
+ term.
+
+
+
+
Is Replaced By:
+
+
The identifier of the next newer version of the
+ term.
+
+
+
+
Class:
+
+
The primary category of terms (Class) that this term
+ describes.
+
+
+
+
ABCD 2.06:
+
+
The xpath(s) to the equivalent concept(s) in the
+ Access to Biological Collections Data schema version 2.06.
An identifier for the name usage (documented meaning of the name according to a source) of the currently valid (zoological) or accepted (botanical) taxon.
DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
An identifier for the name usage (documented meaning of the name according to a source) of the currently valid (zoological) or accepted (botanical) taxon.
DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
{DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLifeStages/MycologicalLifeStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage}
A list (concatenated and separated) of identifiers (publication, bibliographic reference, global unique identifier, URI) of literature associated with the Occurrence.
Comment:
Examples: "http://www.sciencemag.org/cgi/content/abstract/322/5899/261", "Christopher J. Conroy, Jennifer L. Neuwald. 2008. Phylogeographic study of the California vole, Microtus californicus Journal of Mammalogy, 89(3):755-767.". For discussion see http://code.google.com/p/darwincore/wiki/Occurrence
A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of genetic sequence information associated with the Occurrence.
A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of media associated with the Occurrence.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "http://arctos.database.museum/SpecimenImages/UAMObs/Mamm/2/P7291179.JPG", "http://204.140.246.24/Fish/Collection%20Pictures/10118-00.jpg | http://204.140.246.24/Fish/Collection%20Pictures/10118-00a.jpg". For discussion see http://terms.tdwg.org/wiki/dwc:associatedMedia
A list (concatenated and separated) of identifiers of other Organisms and their associations to this Organism.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "sibling of MXA-232", "mother of MXA-231 | mother of MXA-232". For discussion see http://terms.tdwg.org/wiki/dwc:associatedOrganisms
A list (concatenated and separated) of identifiers (publication, bibliographic reference, global unique identifier, URI) of literature associated with the Occurrence.
Comment:
Examples: "http://www.sciencemag.org/cgi/content/abstract/322/5899/261", "Christopher J. Conroy, Jennifer L. Neuwald. 2008. Phylogeographic study of the California vole, Microtus californicus Journal of Mammalogy, 89(3):755-767."
A list (concatenated and separated) of identifiers (publication, bibliographic reference, global unique identifier, URI) of literature associated with the Occurrence.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "http://www.sciencemag.org/cgi/content/abstract/322/5899/261", "Christopher J. Conroy, Jennifer L. Neuwald. 2008. Phylogeographic study of the California vole, Microtus californicus Journal of Mammalogy, 89(3):755-767.", "Steven R. Hoofer and Ronald A. Van Den Bussche. 2001. Phylogenetic Relationships of Plecotine Bats and Allies Based on Mitochondrial Ribosomal Sequences. Journal of Mammalogy 82(1):131-137. | Walker, Faith M., Jeffrey T. Foster, Kevin P. Drees, Carol L. Chambers. 2014. Spotted bat (Euderma maculatum) microsatellite discovery using illumina sequencing. Conservation Genetics Resources.". For discussion see http://terms.tdwg.org/wiki/dwc:associatedReferences
A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of genetic sequence information associated with the Occurrence.
A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of genetic sequence information associated with the Occurrence.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "http://www.ncbi.nlm.nih.gov/nuccore/U34853.1", "http://www.ncbi.nlm.nih.gov/nuccore/GU328060 | http://www.ncbi.nlm.nih.gov/nuccore/AF326093". For discussion see http://terms.tdwg.org/wiki/dwc:associatedSequences
A list (concatenated and separated) of identifiers or names of taxa and their associations with the Occurrence.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '), and to separate the relationship from the taxon with a colon (':'). Examples: "host: Quercus alba", "parasitoid of:Cyclocephala signaticollis | predator of Apis mellifera". For discussion see http://terms.tdwg.org/wiki/dwc:associatedTaxa
List of additional measurements or characteristics (concatenated and separated) for which there is no existing semantic element, but which the data provider nevertheless feels the desire to share. Examples: "Tragus length: 14mm; Weight: 120g", "Height: 1-1.5 meters tall; flowers yellow; uncommon".
The author of the ScientificName and the year of publication, if known. More than one author can be listed in a concatenated string. Should be formatted with parentheses and year according to the conventions of the applicable NomenclaturalCode.
A description indicating whether the record represents an observation, tissue sample, living organism, voucher specimen, germplasm/seed, genetic information, etc.
A descriptive term indicating whether the record represents an object or observation. Examples: PreservedSpecimen- A physical object representing one or more organisms, part of organism, or artifact of an organism. synonyms: voucher, collection, lot. FossilSpecimen- A physical object representing one or more fossil organisms, part of fossil organism, or artifact of a fossil organism. LivingSpecimen- An organism removed from its natural occurrence and now living in captivity or cultivation. HumanObservation- A report by a known observer that an organism was present at the place and time. MachineObservation- A report by a monitoring device that an organism was present at the place and time. StillImage- An photograph, drawing, painting. MovingImage- A sequence of still images taken at regular intervals and intended to be played back as a moving image; may include sound. SoundRecording- An audio recording. OtherSpecimen- Any type of specimen not covered by any of the categories above.
The specific nature of the data record - a subtype of the dcterms:type. Recommended best practice is to use a controlled vocabulary such as the Darwin Core Type Vocabulary (http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm).
The specific nature of the data record - a subtype of the dcterms:type. Recommended best practice is to use a controlled vocabulary such as the Darwin Core Type Vocabulary (http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm).
A description of the behavior shown by the subject at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.
The specific nature of the data record - a subtype of the dcterms:type. Recommended best practice is to use a controlled vocabulary such as the Darwin Core Type Vocabulary (http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm).
Recommended best practice is to use a controlled vocabulary such as the list of Darwin Core classes. Examples: "PreservedSpecimen", "FossilSpecimen", "LivingSpecimen", "HumanObservation", "MachineObservation". For discussion see http://terms.tdwg.org/wiki/dwc:basisOfRecord
A description of the behavior shown by the subject at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.
This access point provides a mechanism for performing searches using a bounding box. A Bounding Box element is not typically present in the database, but rather is derived from the Latitude and Longitude columns by the data provider
This access point provides a mechanism for performing searches using a bounding box. A Bounding Box element is not typically present in the database, but rather is derived from the DecimalLatitude and DecimalLongitude columns by the data provider.
A unique alphanumeric value which identifies an individual record within the collection. It is recommended that this value provides a key by which the actual specimen can be identified. If the specimen has several items such as various types of preparation, this value should identify the individual component of the specimen
The alphanumeric value identifying a record within the collection. It is highly recommended that each record be uniquely identified within a collection by this value. It is also recommended that each record be uniquely identified in a global context by the combination of InstitutionCode, CollectionCode and CatalogNumber.
An alphanumeric value which identifies an individual cataloged item within the collection. It is recommended that this value provides a key by which the individual cataloged item can be identified.
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
The name of, reference to, or brief description of the method or protocol under which the collecting event occurred. Examples: "UV light trap", "mist net", "bottom trawl".
A unique alphanumeric value that identifies the collection within the institution in which the item is cataloged. This attribute must contain no spaces.
An identifier for the collection or dataset from which the record was derived. For physical specimens, the recommended best practice is to use the identifier in a collections registry such as the Biodiversity Collections Index (http://www.biodiversitycollectionsindex.org/).
An identifier for the collection or dataset from which the record was derived. For physical specimens, the recommended best practice is to use the identifier in a collections registry such as the Biodiversity Collections Index (http://www.biodiversitycollectionsindex.org/).
An identifier for the collection or dataset from which the record was derived. For physical specimens, the recommended best practice is to use the identifier in a collections registry such as the Biodiversity Collections Index (http://www.biodiversitycollectionsindex.org/).
The name(s) (concatenated and separated) of collectors or observers. "LIKE" or "contains" substring query operations are meant to be used with this element to find matching collector names. The primary collector or observer, especially one whose CollectorNumber is also provided, should be listed first. Example: "Oliver P. Pearson, Anita K. Pearson" where the value in CollectorNumber "OPP 7101" corresponds to the number for the specimen in the field catalog (collector number) of Oliver P. Pearson.
An identifying string applied to the object or observation at the time of collection. Serves as a link between field notes and the object or observation.
The name of the continent in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The name of the continent in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
An estimate of how tightly the collecting locality was specified; expressed as a distance, in meters, that corresponds to a radius around the latitude-longitude coordinates. Use NULL where precision is unknown, cannot be estimated, or is not applicable.
DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/ISOAccuracy or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/AccuracyStatement
DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/ISOAccuracy or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/AccuracyStatement
DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/ISOAccuracy or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/AccuracyStatement
The upper limit of the distance (in meters) from the given latitude and longitude describing a circle within which the whole of the described locality must lie. Use NULL where the uncertainty is unknown, cannot be estimated, or is not applicable.
The upper limit of the distance (in meters) from the given DecimalLatitude and DecimalLongitude describing a circle within which the whole of the described locality lies. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Describes the point-radius representation of the location, along with DecimalLatitude, DecimalLongitude, and GeodeticDatum. Zero is not a valid value for this element.
The horizontal distance (in meters) from the given decimalLatitude and decimalLongitude describing the smallest circle containing the whole of the Location. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Zero is not a valid value for this term.
Comment:
Examples: "30" (reasonable lower limit of a GPS reading under good conditions if the actual precision was not recorded at the time), "71" (uncertainty for a UTM coordinate having 100 meter precision and a known spatial reference system). For discussion see http://code.google.com/p/darwincore/wiki/Location
The horizontal distance (in meters) from the given decimalLatitude and decimalLongitude describing the smallest circle containing the whole of the Location. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Zero is not a valid value for this term.
Comment:
Examples: "30" (reasonable lower limit of a GPS reading under good conditions if the actual precision was not recorded at the time), "71" (uncertainty for a UTM coordinate having 100 meter precision and a known spatial reference system). For discussion see http://terms.tdwg.org/wiki/dwc:coordinateUncertaintyInMeters
The name of the country or major administrative unit in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The name of the country or major administrative unit in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The full, unabbreviated name of the county, shire, or municipality (i.e., the next smaller political region than StateProvince) from which the cataloged item was collected.
The full, unabbreviated name of the county, shire, or municipality (i.e., the next smaller political region than StateProvince) in which the organism was collected or observed.
The full, unabbreviated name of the next smaller administrative region than stateProvince (county, shire, department, etc.) in which the Location occurs.
Actions taken to make the shared data less specific or complete than in its original form. Suggests that alternative data of higher quality may be available on request.
The full, unabbreviated name of the next smaller administrative region than stateProvince (county, shire, department, etc.) in which the Location occurs.
Actions taken to make the shared data less specific or complete than in its original form. Suggests that alternative data of higher quality may be available on request.
The date on which the subject was identified as representing the taxon given in the scientificName. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://code.google.com/p/darwincore/wiki/Identification
The date on which the subject was identified as representing the Taxon. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://code.google.com/p/darwincore/wiki/Identification
The date on which the subject was identified as representing the taxon given in the scientificName. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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.
The date on which the subject was identified as representing the Taxon. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://terms.tdwg.org/wiki/dwc:dateIdentified
ISO 8601 compliant stamp indicating the date and time in UTC(GMT) when the record was last modified. Example: the instant "November 5, 1994, 8:15:30 am, US Eastern Standard Time" would be represented as "1994-11-05T13:15:30Z" (see W3C Note on Date and Time Formats - http://www.w3.org/TR/NOTE-datetime). (What to do when this date-time is unknown? Use Date-Time first "published"?)
ISO 8601 date and time in UTC(GMT) when the record was last modified. Example: "November 5, 1994, 8:15:30 am, US Eastern Standard Time" would be "1994-11-05T13:15:30Z" (see http://www.w3.org/TR/NOTE-datetime).
The last date-time of publication when any of the data for the record were modified from the previous publication of that record. When publishing a record for the first time, use the publication date-time. Returns values as ISO 8601 date and time. (cf. http://www.w3.org/TR/xmlschema-2/#isoformats and http://www.iso.org/iso/en/prods-services/popstds/dateandtime.html Example: November 5, 1994, 8:15:30 am, US Eastern Standard Time” would be “1994-11-05T13:15:30Z”
The ordinal day of the year on which the object or observation was collected (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366). If the EarliestDateCollected and LatestDateCollected do not occur on the same day, do not populate DayOfYear.
A series of visual representations imparting an impression of motion when shown in succession.
Comment:
Examples include animations, movies, television programs, videos, zoetropes, or visual output from a simulation. Instances of the type Moving Image must also be describable as instances of the broader type Image. For discussion see http://code.google.com/p/darwincore/wiki/DwCTypeVocabulary
A resource describing a static visual representation.
Comment:
Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials. Instances of the type Still Image must also be describable as instances of the broader type Image. For discussion see http://code.google.com/p/darwincore/wiki/DwCTypeVocabulary
Information about who can access the resource or an indication of its security status. Access Rights may include information regarding access or restrictions based on privacy, security, or other policies.
A bibliographic reference for the resource as a statement indicating how this record should be cited (attributed) when used. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.
Comment:
Examples: "Ctenomys sociabilis (MVZ 165861)" for a specimen, "Oliver P. Pearson. 1985. Los tuco-tucos (genera Ctenomys) de los Parques Nacionales Lanin y Nahuel Huapi, Argentina Historia Natural, 5(37):337-343." for a Taxon. For discussion see http://code.google.com/p/darwincore/wiki/RecordLevelTerms
The most recent date-time on which the resource was changed. For Darwin Core, recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://code.google.com/p/darwincore/wiki/RecordLevelTerms
A related resource that is referenced, cited, or otherwise pointed to by the described resource.
Comment:
Examples: "http://mvzarctos.berkeley.edu/guid/MVZ:Mamm:165861"; "http://www.catalogueoflife.org/annual-checklist/show_species_details.php?record_id=6197868". For discussion see http://code.google.com/p/darwincore/wiki/RecordLevelTerms
{DataSets/DataSet/Units/Unit/RecordURI or Datasets/Dataset/Units/Unit/UnitReferences/UnitReferences or Datasets/Dataset/Units/Unit/SourceReference or Datasets/Dataset/Units/Unit/Identifications/Identification/References/Reference or Datasets/Dataset/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference or MeasurementOrFact/MeasurementOrFactAtomised/MeasurementOrFactReference}
Information about rights held in and over the resource. Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights.
{DataSets/DataSet/Units/Unit/Owner/Organisation/Name/Representation/Text or DataSets/DataSet/Units/Unit/Owner/Person/FullName or DataSets/DataSet/Metadata/Owners/Owner/Organisation/Name/Representation/Text or DataSets/DataSet/Metadata/Owners/Owner/Person/FullName}
A series of visual representations imparting an impression of motion when shown in succession.
Comment:
Examples include animations, movies, television programs, videos, zoetropes, or visual output from a simulation. Instances of the type Moving Image must also be describable as instances of the broader type Image.
A resource describing a static visual representation.
Comment:
Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials. Instances of the type Still Image must also be describable as instances of the broader type Image.
Information about who can access the resource or an indication of its security status. Access Rights may include information regarding access or restrictions based on privacy, security, or other policies.
A bibliographic reference for the resource as a statement indicating how this record should be cited (attributed) when used. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.
Comment:
Examples: "Ctenomys sociabilis (MVZ 165861)" for a specimen, "Oliver P. Pearson. 1985. Los tuco-tucos (genera Ctenomys) de los Parques Nacionales Lanin y Nahuel Huapi, Argentina Historia Natural, 5(37):337-343." for a Taxon. For discussion see http://terms.tdwg.org/wiki/dwc:bibliographicCitation
A legal document giving official permission to do something with the resource.
Comment:
Examples: "http://creativecommons.org/publicdomain/zero/1.0/legalcode", "http://creativecommons.org/licenses/by/4.0/legalcode". For discussion see http://terms.tdwg.org/wiki/dwc:license
The most recent date-time on which the resource was changed. For Darwin Core, recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://terms.tdwg.org/wiki/dwc:modified
A related resource that is referenced, cited, or otherwise pointed to by the described resource.
Comment:
Examples: "http://mvzarctos.berkeley.edu/guid/MVZ:Mamm:165861"; "http://www.catalogueoflife.org/annual-checklist/show_species_details.php?record_id=6197868". For discussion see http://terms.tdwg.org/wiki/dwc:references
{DataSets/DataSet/Units/Unit/RecordURI or Datasets/Dataset/Units/Unit/UnitReferences/UnitReferences or Datasets/Dataset/Units/Unit/SourceReference or Datasets/Dataset/Units/Unit/Identifications/Identification/References/Reference or Datasets/Dataset/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference or MeasurementOrFact/MeasurementOrFactAtomised/MeasurementOrFactReference}
Information about rights held in and over the resource. Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights.
{DataSets/DataSet/Units/Unit/Owner/Organisation/Name/Representation/Text or DataSets/DataSet/Units/Unit/Owner/Person/FullName or DataSets/DataSet/Metadata/Owners/Owner/Organisation/Name/Representation/Text or DataSets/DataSet/Metadata/Owners/Owner/Person/FullName}
The latitude of the geographic center of a location where an event occurred (organism collected, observation made), expressed in decimal degrees. Positive values are North of the Equator, negative values are South of the Equator. Describes the point-radius representation of the location, along with DecimalLongitude, GeodeticDatum, and CoordinateUncertaintyInMeters. Example: -41.0983423
The geographic latitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are north of the Equator, negative values are south of it. Legal values lie between -90 and 90, inclusive.
The geographic latitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are north of the Equator, negative values are south of it. Legal values lie between -90 and 90, inclusive.
The longitude of the geographic center of a location where an event occurred (organism collected, observation made), expressed in decimal degrees. Positive values are East of the Greenwich Meridian, negative values are West of the Greenwich Meridian. Describes the point-radius representation of the location, along with DecimalLatitude, GeodeticDatum, and CoordinateUncertaintyInMeters. Example: -71.0943235
The geographic longitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are east of the Greenwich Meridian, negative values are west of it. Legal values lie between -180 and 180, inclusive.
The geographic longitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are east of the Greenwich Meridian, negative values are west of it. Legal values lie between -180 and 180, inclusive.
For data sets that have the depth range expressed in one field (e.g. "150-200 m") it can be entered here as free text. Separate, numeric Minimum and Maximum Depth fields are the preferred format; the Depth Range option is included for legacy data sets.
The current state of a specimen with respect to the collection identified in collectionCode or collectionID. Recommended best practice is to use a controlled vocabulary.
A list (concatenated and separated) of additional measurements, facts, characteristics, or assertions about the record. Meant to provide a mechanism for structured content such as key-value pairs.
Comment:
Examples: "tragusLengthInMeters=0.014; weightInGrams=120", "heightInMeters=1.5", "natureOfID=expert identification; identificationEvidence=cytochrome B sequence", "relativeHumidity=28; airTemperatureInC=22; sampleSizeInKilograms=10", "aspectHeading=277; slopeInDegrees=6", "iucnStatus=vulnerable; taxonDistribution=Neuquen, Argentina". For discussion see http://code.google.com/p/darwincore/wiki/RecordLevelTerms
The full name of the earliest possible geochronologic age or lowest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic age or lowest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
The current state of a specimen with respect to the collection identified in collectionCode or collectionID. Recommended best practice is to use a controlled vocabulary.
A list (concatenated and separated) of additional measurements, facts, characteristics, or assertions about the record. Meant to provide a mechanism for structured content such as key-value pairs.
A list of additional measurements, facts, characteristics, or assertions about the record. Meant to provide a mechanism for structured content.
Comment:
The recommended best practice is to use a key:value encoding schema such as JSON. Examples: "{'heightInMeters':'1.5'}", "{'tragusLengthInMeters':'0.014', 'weightInGrams':'120'}", "{'natureOfID':'expert identification', 'identificationEvidence':'cytochrome B sequence'}", "{'relativeHumidity':'28', 'airTemperatureInCelcius':'22', 'sampleSizeInKilograms':'10'}", "{'aspectHeading':'277', 'slopeInDegrees':'6'}", "{'iucnStatus':'vulnerable', 'taxonDistribution':'Neuquén, Argentina'}". For discussion see http://terms.tdwg.org/wiki/dwc:dynamicProperties
The full name of the earliest possible geochronologic age or lowest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic age or lowest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
The earliest date-time (Common Era calendar) in a date-time period during which an organism or group of organisms was collected or observed. If the event is recorded as occurring at a single date-time, populate both EarliestDateCollected and LatestDateCollected with the same value.
The earliest date-time in a period during which a event occurred. If the event is recorded as occurring at a single date-time, populate both EarliestDateCollected and LatestDateCollected with the same value. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
The full name of the earliest possible geochronologic eon or lowest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic eon or lowest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic epoch or lowest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic epoch or lowest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic era or lowest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic era or lowest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic period or lowest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic period or lowest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
The earliest date-time in a period during which a event occurred. If the event is recorded as occurring at a single date-time, populate both EarliestDateCollected and LatestDateCollected with the same value. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
The full name of the earliest possible geochronologic eon or lowest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic eon or lowest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic epoch or lowest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic epoch or lowest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic era or lowest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic era or lowest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic period or lowest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic period or lowest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
For samples/observations/record events that were taken over time this gives the end day of the collecting event. Possible value ranges from 01..31 inclusive.
For samples/observations/record events that were taken over time this gives the end ordinal day of the year for the collecting event; i.e., the number of days since January 1 of the same year. (January 1 is Julian Day 1.). Should be an integer from one to 365, i.e. of the form (([0-3][0-9][0-9)|([0-9][0-9)|([1-9])).
For samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the starting latitude location from which the specimen was collected or in which the sample/observation/record event occurred. This value should be expressed in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/) this indicates the starting latitude location from which the specimen was collected or in which the sample/observation/record event occurred. This value should be expressed in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/).
For samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the starting longitude location from which the specimen was collected. Express in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/) this indicates the starting longitude location from which the specimen was collected. Express in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/).
For samples/observations/record events that were taken over time this gives the end month of the collecting event. Possible values range from 01...12 inclusive.
The time of day when the sampling event ended, expressed as decimal hours from midnight local time. Examples: 0 = midnight, 12.0 = mid-day, 13.5 = 13:30
For samples/observations/record events that were taken over time this gives the end year of the collecting event. The full year should be expressed (e.g. 1972 must be expressed as "1972" not "72"). Must always be a four digit integer.
The process by which the biological individual(s) represented in the Occurrence became established at the location. Recommended best practice is to use a controlled vocabulary.
A non-persistent, time-based occurrence. For Darwin Core, a resource describing an instance of the Event class.
Comment:
Metadata for an event provides descriptive information that is the basis for discovery of the purpose, location, duration, and responsible agents associated with an event. For discussion see http://code.google.com/p/darwincore/wiki/DwCTypeVocabulary
DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
The units for the value of the measurement or characteristic of the sampling event. Recommended best practice is to use International System of Units (SI) units.
DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
The date-time or interval during which an Event occurred. For occurrences, this is the date-time when the event was recorded. Not suitable for a time in a geological context. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://code.google.com/p/darwincore/wiki/Event
An identifier for the set of information associated with an Event (something that occurs at a place and time). May be a global unique identifier or an identifier specific to the data set.
DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
The date on which the the measurement or characteristic of the event was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
The units for the value of the measurement or characteristic of the event. Recommended best practice is to use International System of Units (SI) units.
DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
The time or interval during which an Event occurred. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "14:07-0600" is 2:07pm in the time zone six hours earlier than UTC, "08:40:21Z" is 8:40:21am UTC, "13:00:00Z/15:30:00Z" is the interval between 1pm UTC and 3:30pm UTC. For discussion see http://code.google.com/p/darwincore/wiki/Event
The process by which the biological individual(s) represented in the Occurrence became established at the location. Recommended best practice is to use a controlled vocabulary.
A non-persistent, time-based occurrence. For Darwin Core, a resource describing an instance of the Event class.
Comment:
Metadata for an event provides descriptive information that is the basis for discovery of the purpose, location, duration, and responsible agents associated with an event.
DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
The date on which the the measurement or characteristic of the sampling event was made.
Comment:
Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
The units for the value of the measurement or characteristic of the sampling event. Recommended best practice is to use International System of Units (SI) units.
DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
The date-time or interval during which an Event occurred. For occurrences, this is the date-time when the event was recorded. Not suitable for a time in a geological context. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://terms.tdwg.org/wiki/dwc:eventDate
An identifier for the set of information associated with an Event (something that occurs at a place and time). May be a global unique identifier or an identifier specific to the data set.
DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
The date on which the the measurement or characteristic of the event was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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.
DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
The units for the value of the measurement or characteristic of the event. Recommended best practice is to use International System of Units (SI) units.
DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
The time or interval during which an Event occurred. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "14:07-0600" is 2:07pm in the time zone six hours earlier than UTC, "08:40:21Z" is 8:40:21am UTC, "13:00:00Z/15:30:00Z" is the interval between 1pm UTC and 3:30pm UTC. For discussion see http://terms.tdwg.org/wiki/dwc:eventTime
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
One of a) a flag indicating the existence of, b) a reference to (such as a URL or literature citation), or c) the actual free text content of notes taken in the field about the specimen or observation.
A measure of how well the geometry expressed in the footprint match the original spatial representation, as a ratio of the area of the footprint given to the area of the original spatial representation. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given georeference does not completely contain the original representation. The FootprintSpatialFit is undefined if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the FootprintSpatialFit is 1. Detailed explanations with graphical examples can be found in the Guide to Best Practices for Georeferencing (Chapman and Wieczorek, eds. 2006).
The ratio of the area of the footprint (footprintWKT) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given footprint does not completely contain the original representation. The footprintSpatialFit is undefined (and should be left blank) if the original representation is a point and the given georeference is not that same point. If both the original and the given georeference are the same point, the footprintSpatialFit is 1.
A Well-Known Text (WKT) representation of the Spatial Reference System (SRS) for the footprintWKT of the Location. Do not use this term to describe the SRS of the decimalLatitude and decimalLongitude, even if it is the same as for the footprintWKT - use the geodeticDatum instead.
Comment:
Example: The WKT for the standard WGS84 SRS (EPSG:4326) is "GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137,298.257223563]],PRIMEM["Greenwich",0],UNIT["Degree",0.0174532925199433]]" without the enclosing quotes. For discussion see http://code.google.com/p/darwincore/wiki/Location
The ratio of the area of the footprint (footprintWKT) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given footprint does not completely contain the original representation. The footprintSpatialFit is undefined (and should be left blank) if the original representation is a point and the given georeference is not that same point. If both the original and the given georeference are the same point, the footprintSpatialFit is 1.
Comment:
Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006. For discussion see http://terms.tdwg.org/wiki/dwc:footprintSpatialFit
A Well-Known Text (WKT) representation of the Spatial Reference System (SRS) for the footprintWKT of the Location. Do not use this term to describe the SRS of the decimalLatitude and decimalLongitude, even if it is the same as for the footprintWKT - use the geodeticDatum instead.
Comment:
Example: The WKT for the standard WGS84 SRS (EPSG:4326) is "GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137,298.257223563]],PRIMEM["Greenwich",0],UNIT["Degree",0.0174532925199433]]" without the enclosing quotes. For discussion see http://terms.tdwg.org/wiki/dwc:footprintSRS
A Well-Known Text (WKT; see http://en.wikipedia.org/wiki/Well-known_text) representation of the the shape (footprint, geometry) that defines the location of the occurrence. The same place may have both a point-radius representation (see DecimalLatitude) and a footprint representation, and they may differ from each other for the same occurrence. Example: the one-degree bounding box with opposite corners at (longitude=10, latitude=20) and (longitude=11, latitude=21) would be expressed in well-known text as POLYGON ((10 20, 11 20, 11 21, 10 21, 10 20))
A Well-Known Text (WKT) representation of the shape (footprint, geometry) that defines the Location. A Location may have both a point-radius representation (see decimalLatitude) and a footprint representation, and they may differ from each other.
Comment:
Example: the one-degree bounding box with opposite corners at (longitude=10, latitude=20) and (longitude=11, latitude=21) would be expressed in well-known text as POLYGON ((10 20, 11 20, 11 21, 10 21, 10 20)). For discussion see http://code.google.com/p/darwincore/wiki/Location
A Well-Known Text (WKT) representation of the shape (footprint, geometry) that defines the Location. A Location may have both a point-radius representation (see decimalLatitude) and a footprint representation, and they may differ from each other.
Comment:
Example: the one-degree bounding box with opposite corners at (longitude=10, latitude=20) and (longitude=11, latitude=21) would be expressed in well-known text as POLYGON ((10 20, 11 20, 11 21, 10 21, 10 20)). For discussion see http://terms.tdwg.org/wiki/dwc:footprintWKT
Actions taken to make the data as shared less specific or complete than in its original form. Suggests that alternative data of highly quality may be available on request.
Actions taken to make the data as shared less specific or complete than in its original form. Suggests that alternative data of highly quality may be available on request.
Comment:
Examples: "Coordinates generalized from original GPS coordinates to the nearest half degree grid cell", "locality information given only to nearest county".
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Viral/GenusOrMonomial or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial}
The geodetic datum to which the latitude and longitude refer. If not known, use "not recorded". This concept should be vocabulary-controlled. Example: "WGS84"
The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which the geographic coordinates given in decimalLatitude and decimalLongitude as based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".
An identifier for the set of information associated with a GeologicalContext (the location within a geological context, such as stratigraphy). May be a global unique identifier or an identifier specific to the data set.
A list (concatenated and separated) of names of people, groups, or organizations who determined the georeference (spatial representation) for the Location.
The date on which the Location was georeferenced. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://code.google.com/p/darwincore/wiki/Location
The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which the geographic coordinates given in decimalLatitude and decimalLongitude as based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".
An identifier for the set of information associated with a GeologicalContext (the location within a geological context, such as stratigraphy). May be a global unique identifier or an identifier specific to the data set.
A list (concatenated and separated) of names of people, groups, or organizations who determined the georeference (spatial representation) for the Location.
A list (concatenated and separated) of names of people, groups, or organizations who determined the georeference (spatial representation) for the Location.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Brad Millen (ROM)", "Kristina Yamamoto (MVZ) | Janet Fang (MVZ)". For discussion see http://terms.tdwg.org/wiki/dwc:georeferencedBy
The date on which the Location was georeferenced. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://terms.tdwg.org/wiki/dwc:georeferencedDate
A description or reference to the methods used to determine the spatial footprint, coordinates, and uncertainties.
Comment:
Examples: "Guide to Best Practices for Georeferencing" (Chapman and Wieczorek, eds. 2006), Global Biodiversity Information Facility.", "MaNIS/HerpNet/ORNIS Georeferencing Guidelines", "Georeferencing Quick Reference Guide". For discussion see http://code.google.com/p/darwincore/wiki/Location
A description or reference to the methods used to determine the spatial footprint, coordinates, and uncertainties.
Comment:
Examples: "Guide to Best Practices for Georeferencing. (Chapman and Wieczorek, eds. 2006). Global Biodiversity Information Facility.", "MaNIS/HerpNet/ORNIS Georeferencing Guidelines", "Georeferencing Quick Reference Guide". For discussion see http://terms.tdwg.org/wiki/dwc:georeferenceProtocol
Comments about the spatial description determination, explaining assumptions made in addition or opposition to the those formalized in the method referred to in GeoreferenceProtocol.
Notes or comments about the spatial description determination, explaining assumptions made in addition or opposition to the those formalized in the method referred to in georeferenceProtocol.
Notes or comments about the spatial description determination, explaining assumptions made in addition or opposition to the those formalized in the method referred to in georeferenceProtocol.
A list of maps, gazetteers or other resources used to georeference the locality. The content of this concept is meant to be specific enough to allow anyone in the future to use the same resource to georeference the same locality. Examples: "USGS 1:24000 Florence Montana Quad", "Terrametrics 2008 on Google Earth"
A list (concatenated and separated) of maps, gazetteers, or other resources used to georeference the Location, described specifically enough to allow anyone in the future to use the same resources.
A list (concatenated and separated) of maps, gazetteers, or other resources used to georeference the Location, described specifically enough to allow anyone in the future to use the same resources.
Comment:
Examples: "USGS 1:24000 Florence Montana Quad; Terrametrics 2008 on Google Earth"
A list (concatenated and separated) of maps, gazetteers, or other resources used to georeference the Location, described specifically enough to allow anyone in the future to use the same resources.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "GeoLocate", "USGS 1:24000 Florence Montana Quad | Terrametrics 2008 on Google Earth". For discussion see http://terms.tdwg.org/wiki/dwc:georeferenceSources
A categorical description of the extent to which the georeference has been verified to represent the location where the specimen or observation was collected. This element should be vocabulary-controlled. Examples: "requires verification", "verified by collector", "verified by curator".
A categorical description of the extent to which the georeference has been verified to represent the best possible spatial description. Recommended best practice is to use a controlled vocabulary.
A categorical description of the extent to which the georeference has been verified to represent the best possible spatial description. Recommended best practice is to use a controlled vocabulary.
A Uniform Resource Name (URN) as a unique identifier for the specimen or observation record. In the absence of a persistent global unique identifier, construct one in the form: “[InstitutionCode]:[CollectionCode]: [CatalogNumber]” Examples: 1) urn:lsid:nhm.ku.edu:Herps:32 2) “FMNH:Mammal:145732”
Geographic Markup Language(GML) description of the feature for representing complex shapes such as lines and polygons, per Open GIS Consortium (OGC) standards - http://www.opengis.net/gml/01-029/GML2.html.
A list (concatenated and separated) of taxa names terminating at the rank immediately superior to the taxon referenced in the taxon record. Recommended best practice is to order the list starting with the highest rank and separating the names for each rank with a semi-colon (";").
Comment:
Example: "Animalia;Chordata;Vertebrata;Mammalia;Theria;Eutheria;Rodentia;Hystricognatha;Hystricognathi;Ctenomyidae;Ctenomyini;Ctenomys". For discussion see http://code.google.com/p/darwincore/wiki/Taxon
A list (concatenated and separated) of taxa names terminating at the rank immediately superior to the taxon referenced in the taxon record. Recommended best practice is to order the list starting with the highest rank and separating the names for each rank with a semi-colon (";").
A list (concatenated and separated) of taxa names terminating at the rank immediately superior to the taxon referenced in the taxon record.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '), with terms in order from the highest taxonomic rank to the lowest. Examples: "Animalia", "Animalia | Chordata | Vertebrata | Mammalia | Theria | Eutheria | Rodentia | Hystricognatha | Hystricognathi | Ctenomyidae | Ctenomyini | Ctenomys". For discussion see http://terms.tdwg.org/wiki/dwc:higherClassification
The combination of all geographic elements less specific than locality. "Like" query operations on this element will search for a substring in any of the higher geography attributes.
The names (concatenated and separated) of geographic elements less specific than the information in the Locality element. "LIKE" or "contains" substring query operations are meant to be used with this element to find matching geographic names. This can be useful if it is unclear in which element a name might be found, and in cases where there is no other appropriate geographic element. Example: "South America, Argentina, Patagonia, Parque Nacional Nahuel Huapi, Neuquén, Los Lagos" with accompanying values "South America" in Continent, "Argentina" in Country, "Neuquén" in StateProvince, and Los Lagos in County.
A list (concatenated and separated) of geographic names less specific than the information captured in the locality term.
Comment:
Example: "South America; Argentina; Patagonia; Parque Nacional Nahuel Huapi; Neuquén; Los Lagos" with accompanying values "South America" in Continent, "Argentina" in Country, "Neuquén" in StateProvince, and Los Lagos in County. For discussion see http://code.google.com/p/darwincore/wiki/Location
An identifier for the geographic region within which the Location occurred. Recommended best practice is to use an persistent identifier from a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
A list (concatenated and separated) of geographic names less specific than the information captured in the locality term.
Comment:
Example: "South America; Argentina; Patagonia; Parque Nacional Nahuel Huapi; Neuquén; Los Lagos" with accompanying values "South America" in Continent, "Argentina" in Country, "Neuquén" in StateProvince, and Los Lagos in County.
A list (concatenated and separated) of geographic names less specific than the information captured in the locality term.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '), with terms in order from least specific to most specific. Examples: "North Atlantic Ocean", "South America | Argentina | Patagonia | Parque Nacional Nahuel Huapi | Neuquén | Los Lagos" with accompanying values "South America" in Continent, "Argentina" in Country, "Neuquén" in StateProvince, and "Los Lagos" in County. For discussion see http://terms.tdwg.org/wiki/dwc:higherGeography
An identifier for the geographic region within which the Location occurred. Recommended best practice is to use an persistent identifier from a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The combination of names of taxonomic ranks less specific than Genus. "Like" query operations on this element will search for a substring in any of the higher taxon attributes.
The names of taxonomic ranks less specific than SpecificEpithet concatenated and separated. "LIKE" or "contains" substring query operations are meant to be used with this element to find matching higher taxon names. This element may contain the list of scientific names of all of the supra-specific taxa in the classification used to identify (determine) the specimen or observation. Example: "Animalia, Chordata, Vertebrata, Mammalia, Theria, Eutheria, Rodentia, Hystricognatha, Hystricognathi, Ctenomyidae, Ctenomyini, Ctenomys".
An identifier for the Identification (the body of information associated with the assignment of a scientific name). May be a global unique identifier or an identifier specific to the data set.
An identifier for the Identification (the body of information associated with the assignment of a scientific name). May be a global unique identifier or an identifier specific to the data set.
A brief phrase or a standard term ("cf.", "aff.") to qualify the identification of the organism when doubts have arisen as to its taxonomic identity (determination). Examples: 1) For the determination "Quercus aff. agrifolia var. oxyadenia", IdentificationQualifier would be "aff. agrifolia var. oxyadenia" with accompanying values "Quercus" in Genus, "agrifolia" in SpecificEpithet, "oxyadenia" in InfraspecificEpithet, and "var." in InfraspecificRank. 2) For the determination "Quercus agrifolia cf. var. oxyadenia", IdentificationQualifier would be "cf. var. oxyadenia " with accompanying values "Quercus" in Genus, "agrifolia" in SpecificEpithet, "oxyadenia" in InfraspecificEpithet, and "var." in InfraspecificRank.
A brief phrase or a standard term ("cf.", "aff.") to express the determiner's doubts about the Identification.
Comment:
Examples: 1) For the determination "Quercus aff. agrifolia var. oxyadenia", identificationQualifier would be "aff. agrifolia var. oxyadenia" with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank. 2) For the determination "Quercus agrifolia cf. var. oxyadenia", identificationQualifier would be "cf. var. oxyadenia " with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank. For discussion see http://code.google.com/p/darwincore/wiki/Identification
A categorical indicator of the extent to which the taxonomic identification has been verified to be correct. Recommended best practice is to use a controlled vocabulary such as that used in HISPID/ABCD.
A brief phrase or a standard term ("cf.", "aff.") to express the determiner's doubts about the Identification.
Comment:
Examples: 1) For the determination "Quercus aff. agrifolia var. oxyadenia", identificationQualifier would be "aff. agrifolia var. oxyadenia" with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank. 2) For the determination "Quercus agrifolia cf. var. oxyadenia", identificationQualifier would be "cf. var. oxyadenia " with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank. For discussion see http://terms.tdwg.org/wiki/dwc:identificationQualifier
A list (concatenated and separated) of references (publication, global unique identifier, URI) used in the Identification.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Aves del Noroeste Patagonico. Christie et al. 2004.", "Stebbins, R. Field Guide to Western Reptiles and Amphibians. 3rd Edition. 2003. | Irschick, D.J. and Shaffer, H.B. (1997). ''The polytypic species revisited: Morphological differentiation among tiger salamanders (Ambystoma tigrinum) (Amphibia: Caudata).'' Herpetologica, 53(1), 30-49.". For discussion see http://terms.tdwg.org/wiki/dwc:identificationReferences
A categorical indicator of the extent to which the taxonomic identification has been verified to be correct. Recommended best practice is to use a controlled vocabulary such as that used in HISPID/ABCD.
A list (concatenated and separated) of names of people, groups, or organizations who assigned the Taxon to the subject.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "James L. Patton", "Theodore Pappenfuss | Robert Macey". For discussion see http://terms.tdwg.org/wiki/dwc:identifiedBy
The number of individuals present in the lot or container referred to by the catalog number. Not an estimate of abundance or density at the collecting locality.
An identifier for an individual or named group of individual organisms represented in the Occurrence. Meant to accommodate resampling of the same individual or group for monitoring purposes. May be a global unique identifier or an identifier specific to a data set.
DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/NameAtomised/Zoological/NamedIndividual or DataSets/DataSet/Units/Unit/ObservationUnit/ObservationUnitIdentifiers/ObservationUnitIdentifier or DataSets/DataSet/Units/Unit/SpecimenUnit/Accessions/AccessionNumber
An identifier for an individual or named group of individual organisms represented in the Occurrence. Meant to accommodate resampling of the same individual or group for monitoring purposes. May be a global unique identifier or an identifier specific to a data set.
DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/NameAtomised/Zoological/NamedIndividual or DataSets/DataSet/Units/Unit/ObservationUnit/ObservationUnitIdentifiers/ObservationUnitIdentifier or DataSets/DataSet/Units/Unit/SpecimenUnit/Accessions/AccessionNumber
Brief descriptions of additional information that may exist, but that has not been made public. Information about obtaining the withheld information should be sought from the administrative contact identified in the provider resource metadata (curator, collection manager). Examples: "specific locality information given only to nearest county", "ask about tissue samples", "georeferences given only to nearest degree".
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
A "standard" code identifier that identifies the institution to which the collection belongs. No global registry exists for assigning institutional codes. Use the code that is "standard" in your discipline.
A code that identifies the institution to which the cataloged item belongs. No global registry exists for institutional codes; use the code that is "standard" in your discipline. This attribute must contain no spaces.
The code (or acronym) identifying the institution administering the collection in which the organism record is cataloged. No global registry exists for institutional codes; use the code that is "standard" at your institution or in your discipline.
The name of the island on or near which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The name of the island on or near which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The name of the island group in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The name of the island group in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The ordinal day of the year (i.e., the number of days since December 31 of the previous year; January 1 is Julian Day 1) on which the cataloged item was collected. May be derived from the YearCollected, MonthCollected, and DayCollected by the provider.
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
The full name of the latest possible geochronologic age or highest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic age or highest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
The full name of the latest possible geochronologic age or highest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic age or highest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
The latest date-time (Common Era calendar) in a date-time period during which an organism or group of organisms was collected or observed. If the event is recorded as occurring at a single date-time, populate both EarliestDateCollected and LatestDateCollected with the same value.
The latest date-time in a period during which a event occurred. If the event is recorded as occurring at a single date-time, populate both EarliestDateCollected and LatestDateCollected with the same value. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
The full name of the latest possible geochronologic eon or highest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic eon or highest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic epoch or highest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic epoch or highest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic era or highest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic era or highest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic period or highest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic period or highest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
The latest date-time in a period during which a event occurred. If the event is recorded as occurring at a single date-time, populate both EarliestDateCollected and LatestDateCollected with the same value. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
The full name of the latest possible geochronologic eon or highest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic eon or highest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic epoch or highest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic epoch or highest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic era or highest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic era or highest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic period or highest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic period or highest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLiveStages/MycologicalLiveStage (Note DwC spec uses ”MycologicalLifeStage” or DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage
The age class or life stage of the biological individual represented by the catalogued object or observation. Examples: "adult", "mature", "juvenile", "eft", "nymph", "seedling", "seed", "egg"
DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLiveStages/MycologicalLiveStage (Note DwC spec uses ”MycologicalLifeStage” or DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage
The age class or life stage of the biological individual(s) at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.
DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLiveStages/MycologicalLiveStage (Note DwC spec uses ”MycologicalLifeStage” or DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage
The age class or life stage of the biological individual(s) at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.
DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalSexualStage or DataSets/DataSet/Units/Unit/MycologicalUnit/MycologicalLiveStages/MycologicalLiveStage (Note DwC spec uses ”MycologicalLifeStage” or DataSets/DataSet/Units/Unit/ZoologicalUnit/PhasesOrStages/PhaseOrStage
The locality description (place name plus optionally a displacement from the place name) from which the specimen was collected. Where a displacement from a location is provided, it should be in un-projected units of measurement
The specific natural language description of the place where the organism was collected or observed. This element need not contain less specific geographic information provided in other geographic elements (HigherGeography, Continent, Country, StateProvince, County, WaterBody, Island, IslandGroup). Though coordinate information can be contained in this concept, these data will be usable analytically only when shared through the concepts of the Geospatial Extension.
The specific description of the place. Less specific geographic information can be provided in other geographic terms (higherGeography, continent, country, stateProvince, county, municipality, waterBody, island, islandGroup). This term may contain information modified from the original to correct perceived errors or standardize the description.
An identifier for the set of location information (data associated with dcterms:Location). May be a global unique identifier or an identifier specific to the data set.
The specific description of the place. Less specific geographic information can be provided in other geographic terms (higherGeography, continent, country, stateProvince, county, municipality, waterBody, island, islandGroup). This term may contain information modified from the original to correct perceived errors or standardize the description.
An identifier for the set of location information (data associated with dcterms:Location). May be a global unique identifier or an identifier specific to the data set.
The category of information pertaining to the physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.
A resource describing the physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.
An identifier for the MaterialSample (as opposed to a particular digital record of the material sample). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the materialSampleID globally unique.
The category of information pertaining to the physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.
A resource describing the physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.
A physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.
Comment:
Examples: A whole organism preserved in a collection. A part of an organism isolated for some purpose. A soil sample. A marine microbial sample. For discussion see http://terms.tdwg.org/wiki/dwc:MaterialSample
An identifier for the MaterialSample (as opposed to a particular digital record of the material sample). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the materialSampleID globally unique.
The maximum distance in meters below the surface of the water at which the collection was made; all material collected was at most this deep. Positive below the surface, negative above (e.g. collecting above sea level in tidal areas).
The maximum distance in meters below the surface of the water at which the collection was made; all material collected was at most this deep. Positive below the surface, negative above (e.g., collecting above sea level in tidal areas).
The maximum or actual depth at which the collection or observation was made. Use positive values for locations below the surface. Examples: 10 (for a depth of up to 10m). 100 (for a depth between 50m and 100m).
The greater distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.
Comment:
Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5". For discussion see http://code.google.com/p/darwincore/wiki/Location
The greater distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.
Comment:
Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5". For discussion see http://terms.tdwg.org/wiki/dwc:maximumDistanceAboveSurfaceInMeters
The maximum or actual elevation at which the collection or observation was made. Use negative values for locations below sea level. Examples: Examples: 125 (for an elevation of 100 +- 25 meters). 200 (for an elevation between 100m and 200m).
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
The date on which the MeasurementOrFact was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://code.google.com/p/darwincore/wiki/MeasurementOrFact
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
An identifier for the MeasurementOrFact (information pertaining to measurements, facts, characteristics, or assertions). May be a global unique identifier or an identifier specific to the data set.
/DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Method or /DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Method or /DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Method
The category of information pertaining to measurements, facts, characteristics, or assertions about a resource (instance of data record, such as Occurrence, Taxon, Location, Event).
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Aspect/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Accuracy or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Accuracy
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
A list (concatenated and separated) of names of people, groups, or organizations who determined the value of the MeasurementOrFact.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Rob Guralnick", "Julie Woodruff | Eileen Lacey". For discussion see http://terms.tdwg.org/wiki/dwc:measurementDeterminedBy
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasuredBy
The date on which the MeasurementOrFact was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://terms.tdwg.org/wiki/dwc:measurementDeterminedDate
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/MeasurementDateTime
An identifier for the MeasurementOrFact (information pertaining to measurements, facts, characteristics, or assertions). May be a global unique identifier or an identifier specific to the data set.
/DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Method or /DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/Method or /DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/Method
The category of information pertaining to measurements, facts, characteristics, or assertions about a resource (instance of data record, such as Occurrence, Taxon, Location, Event).
Resources can be thought of as identifiable records or instances of classes and may include, but need not be limited to Occurrences, Organisms, MaterialSamples, Events, Locations, GeologicalContexts, Identifications, or Taxa. Examples: The weight of an organism in grams. The number of placental scars. For discussion see http://terms.tdwg.org/wiki/dwc:MeasurementOrFact
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts/MeasurementOrFactAtomised/UpperValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
The minimum distance in meters below the surface of the water at which the collection was made; all material collected was at least this deep. Positive below the surface, negative above (e.g. collecting above sea level in tidal areas).
The minimum distance in meters below the surface of the water at which the collection was made; all material collected was at least this deep. Positive below the surface, negative above (e.g., collecting above sea level in tidal areas).
The minimum or actual depth at which the collection or observation was made. Use positive values for locations below the surface. Examples: 0 (for a depth of up to 10m). 50 (for a depth between 50m and 100m).
The lesser distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.
Comment:
Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5". For discussion see http://code.google.com/p/darwincore/wiki/Location
The lesser distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.
Comment:
Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5". For discussion see http://terms.tdwg.org/wiki/dwc:minimumDistanceAboveSurfaceInMeters
The minimum or actual elevation at which the collection or observation was made. Use negative values for locations below sea level. Examples: 75 (for an elevation of 100 +- 25 meters). 100 (for an elevation between 100m and 200m).
The full, unabbreviated name of the next smaller administrative region than county (city, municipality, etc.) in which the Location occurs. Do not use this term for a nearby named place that does not contain the actual location.
The reference to the source in which the specific taxon concept circumscription is defined or implied - traditionally signified by the Latin "sensu" or "sec." (from secundum, meaning "according to"). For taxa that result from identifications, a reference to the keys, monographs, experts and other sources should be given.
Comment:
Example: "McCranie, J. R., D. B. Wake, and L. D. Wilson. 1996. The taxonomic status of Bolitoglossa schmidti, with comments on the biology of the Mesoamerican salamander Bolitoglossa dofleini (Caudata: Plethodontidae). Carib. J. Sci. 32:395-398.", "Werner Greuter 2008", "Lilljeborg 1861, Upsala Univ. Arsskrift, Math. Naturvet., pp. 4, 5". For discussion see http://code.google.com/p/darwincore/wiki/Taxon
A full reference to the original publication of the scientificName.
Comment:
Examples: "Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "Forel, Auguste, Diagnosies provisoires de quelques espèces nouvelles de fourmis de Madagascar, récoltées par M. Grandidier., Annales de la Societe Entomologique de Belgique, Comptes-rendus des Seances 30, 1886". For discussion see http://code.google.com/p/darwincore/wiki/Taxon
A reference for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.
Comment:
Examples: "Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "Forel, Auguste, Diagnosies provisoires de quelques espèces nouvelles de fourmis de Madagascar, récoltées par M. Grandidier., Annales de la Societe Entomologique de Belgique, Comptes-rendus des Seances 30, 1886". For discussion see http://code.google.com/p/darwincore/wiki/Taxon
The full, unabbreviated name of the next smaller administrative region than county (city, municipality, etc.) in which the Location occurs. Do not use this term for a nearby named place that does not contain the actual location.
The reference to the source in which the specific taxon concept circumscription is defined or implied - traditionally signified by the Latin "sensu" or "sec." (from secundum, meaning "according to"). For taxa that result from identifications, a reference to the keys, monographs, experts and other sources should be given.
Comment:
Example: "McCranie, J. R., D. B. Wake, and L. D. Wilson. 1996. The taxonomic status of Bolitoglossa schmidti, with comments on the biology of the Mesoamerican salamander Bolitoglossa dofleini (Caudata: Plethodontidae). Carib. J. Sci. 32:395-398.", "Werner Greuter 2008", "Lilljeborg 1861, Upsala Univ. Arsskrift, Math. Naturvet., pp. 4, 5". For discussion see http://terms.tdwg.org/wiki/dwc:nameAccordingTo
A full reference to the original publication of the scientificName.
Comment:
Examples: "Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "Forel, Auguste, Diagnosies provisoires de quelques espèces nouvelles de fourmis de Madagascar, récoltées par M. Grandidier., Annales de la Societe Entomologique de Belgique, Comptes-rendus des Seances 30, 1886"
A reference for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.
Comment:
Examples: "Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "Forel, Auguste, Diagnosies provisoires de quelques espèces nouvelles de fourmis de Madagascar, récoltées par M. Grandidier., Annales de la Societe Entomologique de Belgique, Comptes-rendus des Seances 30, 1886". For discussion see http://terms.tdwg.org/wiki/dwc:namePublishedIn
The nomenclatural code (or codes in the case of an ambiregnal name) under which the scientificName is constructed. Recommended best practice is to use a controlled vocabulary.
The status related to the original publication of the name and its conformance to the relevant rules of nomenclature. It is based essentially on an algorithm according to the business rules of the code. It requires no taxonomic opinion.
The nomenclatural code (or codes in the case of an ambiregnal name) under which the scientificName is constructed. Recommended best practice is to use a controlled vocabulary.
The status related to the original publication of the name and its conformance to the relevant rules of nomenclature. It is based essentially on an algorithm according to the business rules of the code. It requires no taxonomic opinion.
An identifier for the Occurrence (as opposed to a particular digital record of the occurrence). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the occurrenceID globally unique.
Comment:
For a specimen in the absence of a bona fide global unique identifier, for example, use the form: "urn:catalog:[institutionCode]:[collectionCode]:[catalogNumber]. Examples: "urn:lsid:nhm.ku.edu:Herps:32", "urn:catalog:FMNH:Mammal:145732". For discussion see http://code.google.com/p/darwincore/wiki/Occurrence
The date on which the the measurement or characteristic of the occurrence was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
The units for the value of the measurement or characteristic of the occurrence. Recommended best practice is to use International System of Units (SI) units.
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue
An existence of an Organism (sensu http://rs.tdwg.org/dwc/terms/Organism) at a particular place at a particular time.
Comment:
Examples: A wolf pack on the shore of Kluane Lake in 1988. A virus in a plant leaf in a the New York Botanical Garden at 15:29 on 2014-10-23. A fungus in Central Park in the summer of 1929. For discussion see http://terms.tdwg.org/wiki/dwc:Occurrence
An identifier for the Occurrence (as opposed to a particular digital record of the occurrence). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the occurrenceID globally unique.
Comment:
For a specimen in the absence of a bona fide global unique identifier, for example, use the form: "urn:catalog:[institutionCode]:[collectionCode]:[catalogNumber]. Examples: "urn:lsid:nhm.ku.edu:Herps:32", "urn:catalog:FMNH:Mammal:145732". For discussion see http://terms.tdwg.org/wiki/dwc:occurrenceID
The date on which the the measurement or characteristic of the occurrence was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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.
The units for the value of the measurement or characteristic of the occurrence. Recommended best practice is to use International System of Units (SI) units.
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
A particular organism or defined group of organisms considered to be taxonomically homogeneous.
Comment:
Instances of the Organism class are intended to facilitate linking of one or more Identification instances to one or more Occurrence instances. Therefore, things that are typically assigned scientific names (such as viruses, hybrids, and lichens) and aggregates whose occurrences are typically recorded (such as packs, clones, and colonies) are included in the scope of this class. For discussion see http://terms.tdwg.org/wiki/dwc:Organism
An identifier for the Organism instance (as opposed to a particular digital record of the Organism). May be a globally unique identifier or an identifier specific to the data set.
A description of the kind of Organism instance. Can be used to indicate whether the Organism instance represents a discrete organism or if it represents a particular type of aggregation. Recommended best practice is to use a controlled vocabulary.
The taxon name, with authorship and date information if known, as it originally appeared when first established under the rules of the associated nomenclaturalCode. The basionym (botany) or basonym (bacteriology) of the scientificName or the senior/earlier homonym for replaced names.
An identifier for the name usage (documented meaning of the name according to a source) in which the terminal element of the scientificName was originally established under the rules of the associated nomenclaturalCode.
The taxon name, with authorship and date information if known, as it originally appeared when first established under the rules of the associated nomenclaturalCode. The basionym (botany) or basonym (bacteriology) of the scientificName or the senior/earlier homonym for replaced names.
An identifier for the name usage (documented meaning of the name according to a source) in which the terminal element of the scientificName was originally established under the rules of the associated nomenclaturalCode.
A list of previous or alternative fully qualified catalog numbers for the same object or observation, whether in the current collection or in any other.
A list (concatenated and separated) of previous or alternate fully qualified catalog numbers or other human-used identifiers for the same Occurrence, whether in the current or any other data set or collection.
The full name, with authorship and date information if known, of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.
An identifier for the name usage (documented meaning of the name according to a source) of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.
A list (concatenated and separated) of previous or alternate fully qualified catalog numbers or other human-used identifiers for the same Occurrence, whether in the current or any other data set or collection.
A list (concatenated and separated) of previous or alternate fully qualified catalog numbers or other human-used identifiers for the same Occurrence, whether in the current or any other data set or collection.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "FMNH:Mammal:1234", "NPS YELLO6778 | MBG 33424". For discussion see http://terms.tdwg.org/wiki/dwc:otherCatalogNumbers
The full name, with authorship and date information if known, of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.
An identifier for the name usage (documented meaning of the name according to a source) of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
A measure of how well the circle defined by the coordinates and uncertainty match the original spatial representation, as a ratio of the area of the circle to the area of the original spatial representation. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given georeference does not completely contain the original representation. The PointRadiusSpatialFit is undefined if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the PointRadiusSpatialFit is 1. Detailed explanations with graphical examples can be found in the Guide to Best Practices for Georeferencing (Chapman and Wieczorek, eds. 2006).
The ratio of the area of the point-radius (decimalLatitude, decimalLongitude, coordinateUncertaintyInMeters) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given point-radius does not completely contain the original representation. The pointRadiusSpatialFit is undefined (and should be left blank) if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the pointRadiusSpatialFit is 1.
The ratio of the area of the point-radius (decimalLatitude, decimalLongitude, coordinateUncertaintyInMeters) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given point-radius does not completely contain the original representation. The pointRadiusSpatialFit is undefined (and should be left blank) if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the pointRadiusSpatialFit is 1.
Comment:
Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006. For discussion see http://terms.tdwg.org/wiki/dwc:pointRadiusSpatialFit
A concatenated list of preparations and preservation methods for the object. Examples: "skin", "skull", "skeleton", "whole animal (ETOH)", "tissue (EDTA)".
A list (concatenated and separated) of preparations and preservation methods for a specimen.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "fossil", "cast", "photograph", "DNA extract", "skin | "skull | skeleton", "whole animal (ETOH) | tissue (EDTA)". For discussion see http://terms.tdwg.org/wiki/dwc:preparations
The type of preparation (skin. slide, etc). Probably best to add this as a record element rather than access point. Should be a list of preparations for a single collection record.
The previous (fully qualified) catalog number of the Cataloged Item if the item earlier identified by another Catalog Number, either in the current catalog or another Institution / catalog. A fully qualified Catalog Number is preceded by Institution Code and Collection Code, with a space separating the each subelement. Referencing a previous Catalog Number does not imply that a record for the referenced item is or is not present in the corresponding catalog, or even that the referenced catalog still exists. This access point is intended to provide a way to retrieve this record by previously used identifier, which may used in the literature. In future versions of this schema this attribute should be set-valued.
A list (concatenated and separated) of names of people, groups, or organizations responsible for recording the original Occurrence. The primary collector or observer, especially one who applies a personal identifier (recordNumber), should be listed first.
Comment:
Example: "Oliver P. Pearson; Anita K. Pearson" where the value in recordNumber "OPP 7101" corresponds to the number for the specimen in the field catalog (collector number) of Oliver P. Pearson. For discussion see http://code.google.com/p/darwincore/wiki/Occurrence
An identifier given to the Occurrence at the time it was recorded. Often serves as a link between field notes and an Occurrence record, such as a specimen collector's number.
A list (concatenated and separated) of previous assignments of names to the Organism.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Chalepidae", "Pinus abies", "Anthus sp., field ID by G. Iglesias | Anthus correndera, expert ID by C. Cicero 2009-02-12 based on morphology". For discussion see http://terms.tdwg.org/wiki/dwc:previousIdentifications
A list (concatenated and separated) of names of people, groups, or organizations responsible for recording the original Occurrence. The primary collector or observer, especially one who applies a personal identifier (recordNumber), should be listed first.
Comment:
Example: "Oliver P. Pearson; Anita K. Pearson" where the value in recordNumber "OPP 7101" corresponds to the number for the specimen in the field catalog (collector number) of Oliver P. Pearson.
A list (concatenated and separated) of names of people, groups, or organizations responsible for recording the original Occurrence. The primary collector or observer, especially one who applies a personal identifier (recordNumber), should be listed first.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). The primary collector or observer, especially one who applies a personal identifier (recordNumber), should be listed first. Examples: "José E. Crespo", "Oliver P. Pearson | Anita K. Pearson" where the value in recordNumber "OPP 7101" corresponds to the number for the specimen in the field catalog (collector number) of Oliver P. Pearson. For discussion see http://terms.tdwg.org/wiki/dwc:recordedBy
An identifier given to the Occurrence at the time it was recorded. Often serves as a link between field notes and an Occurrence record, such as a specimen collector's number.
The fully qualified identifier (Institution Code + " " + Collection Code + " " + Catalog Number) of the related Cataloged Item, preceded by the nature of the relationship (e.g., (sibling of) MVZ Mamm 1234).
One or more GlobalUniqueIdentifiers (cf. http://wiki.tdwg.org/twiki/bin/view/DarwinCore/GlobalUniqueIdentifier ) of related objects or observations, optionally preceded by the nature of the relationship. Examples: "(sibling of) URN:catalog:MVZ:Mammal:1234", "(endoparasite of) URN:catalog:FMNH:Bird:41321", "(sheet 2 of 2) URN:WTU:VascularPlants:353087".
The fully qualified identifier of a related Catalog Item (a reference to another specimen); Institution Code, Collection Code, and Catalog Number of the related Cataloged Item, where a space separates the three subelements.
Free text references to information not delivered via the conceptual schema, including URLs to specimen details, publications, bibliographic references, etc.
The date-time on which the relationship between the two resources was established. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://code.google.com/p/darwincore/wiki/ResourceRelationship
The relationship of the resource identified by relatedResourceID to the subject (optionally identified by the resourceID). Recommended best practice is to use a controlled vocabulary.
The date-time on which the relationship between the two resources was established. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://terms.tdwg.org/wiki/dwc:relationshipEstablishedDate
The relationship of the resource identified by relatedResourceID to the subject (optionally identified by the resourceID). Recommended best practice is to use a controlled vocabulary.
A named or coded valued that identifies the kind relationship between this Collection Item and the referenced Collection Item. Named values include: "parasite of", "epiphyte on", "progeny of", etc. In future versions of this schema this attribute should be set-valued.
The units for the value of the measurement or characteristic of the sample. Recommended best practice is to use International System of Units (SI) units.
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue
The category of information pertaining to relationships between resources (instances of data records, such as Occurrences, Taxa, Locations, Events).
Comment:
Resources can be thought of as identifiable records and may include, but need not be limited to Occurrences, Locations, Events, Identifications, or Taxon records.
Resources can be thought of as identifiable records or instances of classes and may include, but need not be limited to Occurrences, Organisms, MaterialSamples, Events, Locations, GeologicalContexts, Identifications, or Taxa. Example: An instance of an Organism is the mother of another instance of an Organism. For discussion see http://terms.tdwg.org/wiki/dwc:ResourceRelationship
The date on which the the measurement or characteristic of the sample was made.
Comment:
Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
The units for the value of the measurement or characteristic of the sample. Recommended best practice is to use International System of Units (SI) units.
DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue or DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UpperValue
The size of the sample from which the collection/observation was drawn. It can be a volume (e.g. for a phytoplankton sample), a linear distance (e.g. for a visual transect or net haul), a surface area (e.g. for a benthic core), etc. This field must also include the units, e.g. 200 mfor a transect, or 0.25 m^2 for a benthic grab (use ^ to denote a superscript). Note that When multiple collections/observations are reported from the same physical sample, a code identifying the sample can be placed in the Field_Number field to allow all collections/observations from a single sample to be connected.
The name of, reference to, or description of the method or protocol used during an Event.
Comment:
Examples: "UV light trap", "mist net", "bottom trawl", "ad hoc observation", "point count", "Penguins from space: faecal stains reveal the location of emperor penguin colonies, http://dx.doi.org/10.1111/j.1466-8238.2009.00467.x", "Takats et al. 2001. Guidelines for Nocturnal Owl Monitoring in North America. Beaverhill Bird Observatory and Bird Studies Canada, Edmonton, Alberta. 32 pp.", "http://www.bsc-eoc.org/download/Owl.pdf". For discussion see http://code.google.com/p/darwincore/wiki/Event
The name of, reference to, or description of the method or protocol used during an Event.
Comment:
Examples: "UV light trap", "mist net", "bottom trawl", "ad hoc observation", "point count", "Penguins from space: faecal stains reveal the location of emperor penguin colonies, http://dx.doi.org/10.1111/j.1466-8238.2009.00467.x", "Takats et al. 2001. Guidelines for Nocturnal Owl Monitoring in North America. Beaverhill Bird Observatory and Bird Studies Canada, Edmonton, Alberta. 32 pp.", "http://www.bsc-eoc.org/download/Owl.pdf". For discussion see http://terms.tdwg.org/wiki/dwc:samplingProtocol
The full name of lowest level taxon the Cataloged Item can be identified as a member of; includes genus name, specific epithet, and subspecific epithet (zool.) or infraspecific rank abbreviation, and infraspecific epithet (bot.) Use name of suprageneric taxon (e.g., family name) if Cataloged Item cannot be identified to genus, species, or infraspecific taxon.
The full name of the lowest level taxon to which the organism has been identified in the most recent accepted determination, specified as precisely as possible, including name-author, year or authorship, sensu or sec. (according to or following) author, and indication of uncertainty. Conceptually equivalent to a full taxonomic identification as given by the identifier (verbatim). Does not include the identifier name or date of identification. Examples: "Coleoptera" (an Order), "Vespertilionidae" (a Family), "Manis" (a Genus), "Ctenomys sociabilis" (Genus + SpecificEpithet), "Ambystoma tigrinum diaboli" (Genus + SpecificEpithet + SubspecificEpithet), "Quercus agrifolia var. oxyadenia (Torr.) J.T. Howell" (Genus + SpecificEpithet + InfraspecificRank + InfraspecificEpithet + AuthorYearOfScientificName).
The taxon name (with date and authorship information if applicable). When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the IdentificationQualifier term.
The full scientific name, with authorship and date information if known. When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the IdentificationQualifier term.
The taxon name (with date and authorship information if applicable). When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the IdentificationQualifier term.
The full scientific name, with authorship and date information if known. When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the IdentificationQualifier term.
The author of a scientific name. Author string as applied to the accepted name. Can be more than one author (concatenated string). Should be formatted according to the conventions of the applicable taxonomic discipline.
The author of the ScientificName. Can be more than one author in a concatenated string. Should be formatted according to the conventions of the applicable taxonomic discipline.
The sex of a specimen. The domain should be a controlled set of terms (codes) based on community consensus. Proposed values: M=Male; F=Female; H=Hermaphrodite; I=Indeterminate (examined but could not be determined; U=Unkown (not examined); T=Transitional (between sexes; useful for sequential hermaphrodites)
The sex of a cataloged item (e.g., male, female, hermaphrodite, gynandromorph, not recorded, indeterminate, transitional - between sexes, for sequential hermaphrodites).
The sex of the biological individual represented by the cataloged object or observation. Examples: "male", "female", "hermaphrodite", "gynandromorph", "monoecious", "dioecious", "not recorded", "indeterminate", "transitional".
A unique identifier assigned to a material sample (as defined by http://rs.tdwg.org/dwc/terms/MaterialSampleID, and as opposed to a particular digital record of a material sample) used for extracting nucleic acids, and subsequent sequencing. The identifier can refer either to the original material collected or to any derived sub-samples. The INSDC qualifiers /specimen_voucher, /bio_material, or /culture_collection provide additional context and suggested syntax for this identifier for data submitted to INSDC databases.
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SpeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/FirstEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SpeciesEpithet}
An estimate of how tightly the locality was specified in the Start/End Latitude and Longitude fields; expressed as a distance, in meters, that corresponds to a radius around the latitude-longitude coordinates. Use NULL where precision is unknown, cannot be estimated, or is not applicable.
For samples/observations/record events that were taken over time this gives the start day of the collecting event. Possible value ranges from 01..31 inclusive.
The earliest ordinal day of the year on which the Event occurred (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366).
The earliest ordinal day of the year on which the Event occurred (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366).
For samples/observations/record events that were taken over time this gives the start ordinal day of the year for the collecting event; i.e., the number of days since January 1 of the same year. (January 1 is Julian Day 1.). Should be an integer from one to 365, i.e. of the form (([0-3][0-9][0-9)|([0-9][0-9)|([1-9])).
For samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the starting latitude location from which the specimen was collected or in which the sample/observation/record event occurred. This value should be expressed in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/) this indicates the starting latitude location from which the specimen was collected or in which the sample/observation/record event occurred. This value should be expressed in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/).
For samples/observations/record events better represented as line features rather than point features (e.g. extended trawls or transects) this indicates the starting longitude location from which the specimen was collected. Express in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/) this indicates the starting longitude location from which the specimen was collected. Express in decimal degrees (East & North = +; West & South = -). GPS-derived data must use the WGS 84 geodetic reference system (http://www.wgs84.com/).
For samples/observations/record events that were taken over time this gives the start month of the collecting event. Possible values range from 01...12 inclusive.
The time of day when the sampling event began, expressed as decimal hours from midnight local time. Examples: 0 = midnight, 12.0 = mid-day, 13.5 = 13:30
For samples/observations/record events that were taken over time this gives the start year of the collecting event. The full year should be expressed (e.g. 1972 must be expressed as "1972" not "72"). Must always be a four digit integer.
The full, unabbreviated name of the state, province, or region (i.e., the next smaller political region than Country) from which the cataloged item was collected.
The full, unabbreviated name of the state, province, or region (i.e., the next smaller political region than Country) in which the organism was collected or observed.
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
{DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Bacterial/SubspeciesEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/SecondEpithet or DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/SubspeciesEpithet}
Information about the authorship of this taxon concept which uses the scientificName in their sense (secundum, sensu). Could be a publication (identification key), institution or team of individuals.
An identifier for the set of taxon information (data associated with the Taxon class). May be a global unique identifier or an identifier specific to the data set.
Comment:
Examples: "8fa58e08-08de-4ac1-b69c-1235340b7001", "32567", "http://species.gbif.org/abies_alba_1753", "urn:lsid:gbif.org:usages:32567". For discussion see http://code.google.com/p/darwincore/wiki/Taxon
The status of the use of the scientificName as a label for a taxon. Requires taxonomic opinion to define the scope of a taxon. Rules of priority then are used to define the taxonomic status of the nomenclature contained in that scope, combined with the experts opinion. It must be linked to a specific taxonomic reference that defines the concept. Recommended best practice is to use a controlled vocabulary.
A group of organisms (sensu http://purl.obolibrary.org/obo/OBI_0100026) considered by taxonomists to form a homogeneous unit.
Comment:
Example: The genus Truncorotaloides as published by Brönnimann et al. in 1953 in the Journal of Paleontology Vol. 27(6) p. 817-820. For discussion see http://terms.tdwg.org/wiki/dwc:Taxon
Information about the authorship of this taxon concept which uses the scientificName in their sense (secundum, sensu). Could be a publication (identification key), institution or team of individuals.
An identifier for the set of taxon information (data associated with the Taxon class). May be a global unique identifier or an identifier specific to the data set.
Comment:
Examples: "8fa58e08-08de-4ac1-b69c-1235340b7001", "32567", "http://species.gbif.org/abies_alba_1753", "urn:lsid:gbif.org:usages:32567". For discussion see http://terms.tdwg.org/wiki/dwc:taxonID
The status of the use of the scientificName as a label for a taxon. Requires taxonomic opinion to define the scope of a taxon. Rules of priority then are used to define the taxonomic status of the nomenclature contained in that scope, combined with the experts opinion. It must be linked to a specific taxonomic reference that defines the concept. Recommended best practice is to use a controlled vocabulary.
Indicates the kind of nomenclatural type that a specimen represents. (This is incomplete because type status actually describes the relationship between a name and a specimen [or ternary relatiohnship between a specimen, name, and publication].) In particular, the type status may not apply to the name listed in the scientific name, i.e., current identification. In rare cases, a single specimen may be the type of more than one name.
A list of one or more nomenclatural types that the cataloged item represents (e.g., "holotype of Ctenomys sociabilis. Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388.").
A list of one or more nomenclatural types (including type status and typified taxonomic name) represented by the object. Example: "holotype of Ctenomys sociabilis. Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388".
A list (concatenated and separated) of nomenclatural types (type status, typified scientific name, publication) applied to the subject.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "holotype of Ctenomys sociabilis. Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "holotype of Pinus abies | holotype of Picea abies". For discussion see http://terms.tdwg.org/wiki/dwc:typeStatus
A flag ("true" or "false") that indicates whether the locality information represents a valid distribution occurrence for a specimen. Specimens taken from captivity and showing the captive location should use the value "false".
A text representation of the coordinate data (Latitude/ Longitude, UTM, TRS, etc.) from its original source if it cannot be separated into its component parts. Example: "470999 1234300".
{DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinatesText or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesUTM/UTMText}
The verbatim original spatial coordinates of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
{DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinatesText or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesUTM/UTMText}
The verbatim original spatial coordinates of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
{DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinatesText or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesUTM/UTMText}
The name of the system in which the verbatim geographic coordinates were recorded. Examples: "decimal degrees", "degrees minutes seconds", "degrees decimal minutes", "UTM"
The spatial coordinate system for the verbatimLatitude and verbatimLongitude or the verbatimCoordinates of the Location. Recommended best practice is to use a controlled vocabulary.
The spatial coordinate system for the verbatimLatitude and verbatimLongitude or the verbatimCoordinates of the Location. Recommended best practice is to use a controlled vocabulary.
The verbatim original latitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
The verbatim original latitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
The verbatim original longitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which coordinates given in verbatimLatitude and verbatimLongitude, or verbatimCoordinates are based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".
The verbatim original longitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which coordinates given in verbatimLatitude and verbatimLongitude, or verbatimCoordinates are based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".
The name of the water body in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The name of the water body in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The year (expressed as an integer) in which the specimen was collected. The full year should be expressed (e.g. 1972 must be expressed as "1972" not "72"). Must always be a four digit integer [-9999..9999]
This document is a quick reference for mappings between elements in pre-standard Darwin Core
-versions and the current Darwin Core terms. For complete historical
-term information, including version changes and details on pre-standard terms, see [HISTORY].
-For a quick reference guide to the current recommended Darwin Core terms, see [TERMS].
-
-
-
Contributors:
-
John Wieczorek (MVZ), Markus Döring (GBIF), Renato De Giovanni (CRIA), Tim Robertson (GBIF), Dave Vieglais (KUNHM)
-
-
-
Legal:
-
This document is governed by the standard legal, copyright, licensing provisions and disclaimers issued by the Taxonomic Databases Working Group.
-Audience: This document is targeted toward those who wish to understand how the standard Darwin Core terms are related to
-previously used Darwin Core schemas.
-
-Before becoming a TDWG standard, the Darwin Core was instantiated and deployed in many different
-application profiles, all of them based on XML schema. The openly developed and widely used versions
-of the Darwin Core ([CLASSIC],
-[MANIS],
-[OBIS],
-[DRAFT14],
-[CURATORIAL],
-[GEOSPATIAL]),
-[PALEO])
-are each compared (mapped conceptually) to the
-current recommended Darwin Core terms [TERMS] in this document. Each historical version is
-mapped in a separate table and can be referenced quickly from the Mappings section below.
+
2.3 Darwin Core 1.21 (MaNIS/HerpNet/ORNIS/FishNet2)
-
-
Darwin Core 1.21 Element
Recommended Term
+
+ This document is a quick reference for mappings between
+ elements in pre-standard Darwin Core versions and the current
+ Darwin Core terms. For complete historical term information,
+ including version changes and details on pre-standard terms,
+ see [HISTORY]. For a quick
+ reference guide to the current recommended Darwin Core terms,
+ see [TERMS].
+
Audience: This document is targeted toward
+ those who wish to understand how the standard Darwin Core terms are related
+ to previously used Darwin Core schemas.
+
+
Before becoming a TDWG standard, the Darwin Core was instantiated and
+ deployed in many different application profiles, all of them based on XML
+ schema. The openly developed and widely used versions of the Darwin Core
+ ([CLASSIC],
+ [MANIS],
+ [OBIS], [DRAFT14], [CURATORIAL], [GEOSPATIAL]), [PALEO])
+ are each compared (mapped conceptually) to the current recommended Darwin
+ Core terms [TERMS] in this document. Each
+ historical version is mapped in a separate table and can be referenced
+ quickly from the Mappings section below.
This document is a quick reference for all recommended Darwin Core terms. For complete historical
-term information, including version changes and pre-standard terms, see [HISTORY].
-For a comparative table of elements from pre-standard versions of Darwin Core to the current
-terms in the standard, see [VERSIONS].
-
-
-
-
Contributors:
-
John Wieczorek (MVZ), Markus Döring (GBIF), Renato De Giovanni (CRIA), Tim Robertson (GBIF), Dave Vieglais (KUNHM)
-
-
-
Legal:
-
This document is governed by the standard legal, copyright, licensing provisions and disclaimers issued by the Taxonomic Databases Working Group.
-Audience: This document is targeted toward those who need a reference (lists and definitions) to the essential information
-about the current recommended Darwin Core terms.
-
-This quick guide provides a list of all current terms of the Darwin core. The terms are
-organized by categories (in bold) in the index. The categories correspond to Darwin Core terms that are
-classes (terms that have other terms to describe them). The terms that describe a given class
-(the class properties) appear in the list immediately below the name of the category in the index. The index provides
-links to the term descriptions in the table below the index.
-
-Names that begin with dcterms: are terms managed by the Dublin Core Metadata Initiative
-[DCMI], which are reproduced here and which may include a description and
-comments adapted for the biodiversity community. The original definition of such terms can be found by following the link
-given in the Details section for the term.
-
-Terms under the Record-level Terms section apply to the whole record regardless of the record type. For example, a record for a
-camera trap bird sighting would fall into the Dublin Core dcterms:type category StillImage and at the same time into the
-Darwin Core basisOfRecord category MachineObservation - a particular type of Occurrence, so the value of
-dcterms:type term for the record would be "StillImage" and the value of the basisOfRecord term would be
-"MachineObservation" to show which kind of Occurrence record it is. All of the rest of the record-level terms would apply
-to the Occurrence record.
-
-
The terms found under the Auxiliary Terms section
-can only be meaningfully implemented in an application that supports relational
-structures. For example, none of the auxiliary terms will be found in the specification of the Simple Darwin
-Core [SIMPLEDWC], which is "flat" in structure.
+
-The table below contains the term information essential for most users. The complete documentation for each term
-can be found by following the link in the Details section of the description. The link takes you to the appropriate
-entry in the Complete History [HISTORY] document. The definitions for the fields describing each term are:
+
The table below contains the term information
+ essential for most users. The complete documentation for each term can be
+ found by following the link in the Detailssection of the description.
+ The link takes you to the appropriate entry in the Complete
+ History[HISTORY] document. The
+ definitions for the fields describing each term are:
+
+
+
+
+
Term Name:
+
+
The name by which the latest version of the term is
+ commonly known.
+
+
+
+
Identifier:
+
+
The unique identifier for the latest version of the
+ term.
+
+
+
+
Class:
+
+
The primary category of terms (Class) that this term
+ describes.
+
+
+
+
Definition:
+
+
A description of the nature of the content of the
+ term.
+
+
+
+
Comment:
+
+
Further commentary about the usage of the term, with
+ examples and a reference to further information.
+
+
+
+
Details:
+
+
A link to the complete information about the term,
+ including access to its history.
The category of information pertaining to the physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.
The category of information pertaining to measurements, facts, characteristics, or assertions about a resource (instance of data record, such as Occurrence, Taxon, Location, Event).
The most recent date-time on which the resource was changed. For Darwin Core, recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://code.google.com/p/darwincore/wiki/RecordLevelTerms
Information about rights held in and over the resource. Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights.
Information about who can access the resource or an indication of its security status. Access Rights may include information regarding access or restrictions based on privacy, security, or other policies.
A bibliographic reference for the resource as a statement indicating how this record should be cited (attributed) when used. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.
Comment:
Examples: "Ctenomys sociabilis (MVZ 165861)" for a specimen, "Oliver P. Pearson. 1985. Los tuco-tucos (genera Ctenomys) de los Parques Nacionales Lanin y Nahuel Huapi, Argentina Historia Natural, 5(37):337-343." for a Taxon. For discussion see http://code.google.com/p/darwincore/wiki/RecordLevelTerms
A related resource that is referenced, cited, or otherwise pointed to by the described resource.
Comment:
Examples: "http://mvzarctos.berkeley.edu/guid/MVZ:Mamm:165861"; "http://www.catalogueoflife.org/annual-checklist/show_species_details.php?record_id=6197868". For discussion see http://code.google.com/p/darwincore/wiki/RecordLevelTerms
An identifier for the collection or dataset from which the record was derived. For physical specimens, the recommended best practice is to use the identifier in a collections registry such as the Biodiversity Collections Index (http://www.biodiversitycollectionsindex.org/).
The specific nature of the data record - a subtype of the dcterms:type. Recommended best practice is to use a controlled vocabulary such as the Darwin Core Type Vocabulary (http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm).
Actions taken to make the shared data less specific or complete than in its original form. Suggests that alternative data of higher quality may be available on request.
A list (concatenated and separated) of additional measurements, facts, characteristics, or assertions about the record. Meant to provide a mechanism for structured content such as key-value pairs.
Comment:
Examples: "tragusLengthInMeters=0.014; weightInGrams=120", "heightInMeters=1.5", "natureOfID=expert identification; identificationEvidence=cytochrome B sequence", "relativeHumidity=28; airTemperatureInC=22; sampleSizeInKilograms=10", "aspectHeading=277; slopeInDegrees=6", "iucnStatus=vulnerable; taxonDistribution=Neuquen, Argentina". For discussion see http://code.google.com/p/darwincore/wiki/RecordLevelTerms
An identifier for the Occurrence (as opposed to a particular digital record of the occurrence). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the occurrenceID globally unique.
Comment:
For a specimen in the absence of a bona fide global unique identifier, for example, use the form: "urn:catalog:[institutionCode]:[collectionCode]:[catalogNumber]. Examples: "urn:lsid:nhm.ku.edu:Herps:32", "urn:catalog:FMNH:Mammal:145732". For discussion see http://code.google.com/p/darwincore/wiki/Occurrence
An identifier given to the Occurrence at the time it was recorded. Often serves as a link between field notes and an Occurrence record, such as a specimen collector's number.
A list (concatenated and separated) of names of people, groups, or organizations responsible for recording the original Occurrence. The primary collector or observer, especially one who applies a personal identifier (recordNumber), should be listed first.
Comment:
Example: "Oliver P. Pearson; Anita K. Pearson" where the value in recordNumber "OPP 7101" corresponds to the number for the specimen in the field catalog (collector number) of Oliver P. Pearson. For discussion see http://code.google.com/p/darwincore/wiki/Occurrence
An identifier for an individual or named group of individual organisms represented in the Occurrence. Meant to accommodate resampling of the same individual or group for monitoring purposes. May be a global unique identifier or an identifier specific to a data set.
The age class or life stage of the biological individual(s) at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.
A description of the behavior shown by the subject at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.
The process by which the biological individual(s) represented in the Occurrence became established at the location. Recommended best practice is to use a controlled vocabulary.
The current state of a specimen with respect to the collection identified in collectionCode or collectionID. Recommended best practice is to use a controlled vocabulary.
A list (concatenated and separated) of previous or alternate fully qualified catalog numbers or other human-used identifiers for the same Occurrence, whether in the current or any other data set or collection.
A list (concatenated and separated) of identifiers (publication, bibliographic reference, global unique identifier, URI) of literature associated with the Occurrence.
Comment:
Examples: "http://www.sciencemag.org/cgi/content/abstract/322/5899/261", "Christopher J. Conroy, Jennifer L. Neuwald. 2008. Phylogeographic study of the California vole, Microtus californicus Journal of Mammalogy, 89(3):755-767.". For discussion see http://code.google.com/p/darwincore/wiki/Occurrence
A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of genetic sequence information associated with the Occurrence.
An identifier for the MaterialSample (as opposed to a particular digital record of the material sample). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the materialSampleID globally unique.
An identifier for the set of information associated with an Event (something that occurs at a place and time). May be a global unique identifier or an identifier specific to the data set.
The name of, reference to, or description of the method or protocol used during an Event.
Comment:
Examples: "UV light trap", "mist net", "bottom trawl", "ad hoc observation", "point count", "Penguins from space: faecal stains reveal the location of emperor penguin colonies, http://dx.doi.org/10.1111/j.1466-8238.2009.00467.x", "Takats et al. 2001. Guidelines for Nocturnal Owl Monitoring in North America. Beaverhill Bird Observatory and Bird Studies Canada, Edmonton, Alberta. 32 pp.", "http://www.bsc-eoc.org/download/Owl.pdf". For discussion see http://code.google.com/p/darwincore/wiki/Event
The date-time or interval during which an Event occurred. For occurrences, this is the date-time when the event was recorded. Not suitable for a time in a geological context. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://code.google.com/p/darwincore/wiki/Event
The time or interval during which an Event occurred. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "14:07-0600" is 2:07pm in the time zone six hours earlier than UTC, "08:40:21Z" is 8:40:21am UTC, "13:00:00Z/15:30:00Z" is the interval between 1pm UTC and 3:30pm UTC. For discussion see http://code.google.com/p/darwincore/wiki/Event
The earliest ordinal day of the year on which the Event occurred (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366).
An identifier for the set of location information (data associated with dcterms:Location). May be a global unique identifier or an identifier specific to the data set.
An identifier for the geographic region within which the Location occurred. Recommended best practice is to use an persistent identifier from a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
A list (concatenated and separated) of geographic names less specific than the information captured in the locality term.
Comment:
Example: "South America; Argentina; Patagonia; Parque Nacional Nahuel Huapi; Neuquén; Los Lagos" with accompanying values "South America" in Continent, "Argentina" in Country, "Neuquén" in StateProvince, and Los Lagos in County. For discussion see http://code.google.com/p/darwincore/wiki/Location
The name of the continent in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The name of the water body in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The name of the island group in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The name of the island on or near which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The name of the country or major administrative unit in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The full, unabbreviated name of the next smaller administrative region than stateProvince (county, shire, department, etc.) in which the Location occurs.
The full, unabbreviated name of the next smaller administrative region than county (city, municipality, etc.) in which the Location occurs. Do not use this term for a nearby named place that does not contain the actual location.
The specific description of the place. Less specific geographic information can be provided in other geographic terms (higherGeography, continent, country, stateProvince, county, municipality, waterBody, island, islandGroup). This term may contain information modified from the original to correct perceived errors or standardize the description.
The lesser distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.
Comment:
Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5". For discussion see http://code.google.com/p/darwincore/wiki/Location
The greater distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.
Comment:
Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5". For discussion see http://code.google.com/p/darwincore/wiki/Location
The verbatim original spatial coordinates of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
The verbatim original latitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
The verbatim original longitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
The spatial coordinate system for the verbatimLatitude and verbatimLongitude or the verbatimCoordinates of the Location. Recommended best practice is to use a controlled vocabulary.
The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which coordinates given in verbatimLatitude and verbatimLongitude, or verbatimCoordinates are based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".
The geographic latitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are north of the Equator, negative values are south of it. Legal values lie between -90 and 90, inclusive.
The geographic longitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are east of the Greenwich Meridian, negative values are west of it. Legal values lie between -180 and 180, inclusive.
The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which the geographic coordinates given in decimalLatitude and decimalLongitude as based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".
The horizontal distance (in meters) from the given decimalLatitude and decimalLongitude describing the smallest circle containing the whole of the Location. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Zero is not a valid value for this term.
Comment:
Examples: "30" (reasonable lower limit of a GPS reading under good conditions if the actual precision was not recorded at the time), "71" (uncertainty for a UTM coordinate having 100 meter precision and a known spatial reference system). For discussion see http://code.google.com/p/darwincore/wiki/Location
The ratio of the area of the point-radius (decimalLatitude, decimalLongitude, coordinateUncertaintyInMeters) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given point-radius does not completely contain the original representation. The pointRadiusSpatialFit is undefined (and should be left blank) if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the pointRadiusSpatialFit is 1.
A Well-Known Text (WKT) representation of the shape (footprint, geometry) that defines the Location. A Location may have both a point-radius representation (see decimalLatitude) and a footprint representation, and they may differ from each other.
Comment:
Example: the one-degree bounding box with opposite corners at (longitude=10, latitude=20) and (longitude=11, latitude=21) would be expressed in well-known text as POLYGON ((10 20, 11 20, 11 21, 10 21, 10 20)). For discussion see http://code.google.com/p/darwincore/wiki/Location
A Well-Known Text (WKT) representation of the Spatial Reference System (SRS) for the footprintWKT of the Location. Do not use this term to describe the SRS of the decimalLatitude and decimalLongitude, even if it is the same as for the footprintWKT - use the geodeticDatum instead.
Comment:
Example: The WKT for the standard WGS84 SRS (EPSG:4326) is "GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137,298.257223563]],PRIMEM["Greenwich",0],UNIT["Degree",0.0174532925199433]]" without the enclosing quotes. For discussion see http://code.google.com/p/darwincore/wiki/Location
The ratio of the area of the footprint (footprintWKT) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given footprint does not completely contain the original representation. The footprintSpatialFit is undefined (and should be left blank) if the original representation is a point and the given georeference is not that same point. If both the original and the given georeference are the same point, the footprintSpatialFit is 1.
A list (concatenated and separated) of names of people, groups, or organizations who determined the georeference (spatial representation) for the Location.
The date on which the Location was georeferenced. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://code.google.com/p/darwincore/wiki/Location
A description or reference to the methods used to determine the spatial footprint, coordinates, and uncertainties.
Comment:
Examples: "Guide to Best Practices for Georeferencing" (Chapman and Wieczorek, eds. 2006), Global Biodiversity Information Facility.", "MaNIS/HerpNet/ORNIS Georeferencing Guidelines", "Georeferencing Quick Reference Guide". For discussion see http://code.google.com/p/darwincore/wiki/Location
A list (concatenated and separated) of maps, gazetteers, or other resources used to georeference the Location, described specifically enough to allow anyone in the future to use the same resources.
A categorical description of the extent to which the georeference has been verified to represent the best possible spatial description. Recommended best practice is to use a controlled vocabulary.
Notes or comments about the spatial description determination, explaining assumptions made in addition or opposition to the those formalized in the method referred to in georeferenceProtocol.
An identifier for the set of information associated with a GeologicalContext (the location within a geological context, such as stratigraphy). May be a global unique identifier or an identifier specific to the data set.
The full name of the earliest possible geochronologic eon or lowest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic eon or highest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic era or lowest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic era or highest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic period or lowest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic period or highest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic epoch or lowest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic epoch or highest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic age or lowest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic age or highest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
An identifier for the Identification (the body of information associated with the assignment of a scientific name). May be a global unique identifier or an identifier specific to the data set.
The date on which the subject was identified as representing the Taxon. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://code.google.com/p/darwincore/wiki/Identification
A categorical indicator of the extent to which the taxonomic identification has been verified to be correct. Recommended best practice is to use a controlled vocabulary such as that used in HISPID/ABCD.
A brief phrase or a standard term ("cf.", "aff.") to express the determiner's doubts about the Identification.
Comment:
Examples: 1) For the determination "Quercus aff. agrifolia var. oxyadenia", identificationQualifier would be "aff. agrifolia var. oxyadenia" with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank. 2) For the determination "Quercus agrifolia cf. var. oxyadenia", identificationQualifier would be "cf. var. oxyadenia " with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank. For discussion see http://code.google.com/p/darwincore/wiki/Identification
An identifier for the set of taxon information (data associated with the Taxon class). May be a global unique identifier or an identifier specific to the data set.
Comment:
Examples: "8fa58e08-08de-4ac1-b69c-1235340b7001", "32567", "http://species.gbif.org/abies_alba_1753", "urn:lsid:gbif.org:usages:32567". For discussion see http://code.google.com/p/darwincore/wiki/Taxon
An identifier for the name usage (documented meaning of the name according to a source) of the currently valid (zoological) or accepted (botanical) taxon.
An identifier for the name usage (documented meaning of the name according to a source) of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.
An identifier for the name usage (documented meaning of the name according to a source) in which the terminal element of the scientificName was originally established under the rules of the associated nomenclaturalCode.
The full scientific name, with authorship and date information if known. When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the IdentificationQualifier term.
The full name, with authorship and date information if known, of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.
The taxon name, with authorship and date information if known, as it originally appeared when first established under the rules of the associated nomenclaturalCode. The basionym (botany) or basonym (bacteriology) of the scientificName or the senior/earlier homonym for replaced names.
The reference to the source in which the specific taxon concept circumscription is defined or implied - traditionally signified by the Latin "sensu" or "sec." (from secundum, meaning "according to"). For taxa that result from identifications, a reference to the keys, monographs, experts and other sources should be given.
Comment:
Example: "McCranie, J. R., D. B. Wake, and L. D. Wilson. 1996. The taxonomic status of Bolitoglossa schmidti, with comments on the biology of the Mesoamerican salamander Bolitoglossa dofleini (Caudata: Plethodontidae). Carib. J. Sci. 32:395-398.", "Werner Greuter 2008", "Lilljeborg 1861, Upsala Univ. Arsskrift, Math. Naturvet., pp. 4, 5". For discussion see http://code.google.com/p/darwincore/wiki/Taxon
A reference for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.
Comment:
Examples: "Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "Forel, Auguste, Diagnosies provisoires de quelques espèces nouvelles de fourmis de Madagascar, récoltées par M. Grandidier., Annales de la Societe Entomologique de Belgique, Comptes-rendus des Seances 30, 1886". For discussion see http://code.google.com/p/darwincore/wiki/Taxon
A list (concatenated and separated) of taxa names terminating at the rank immediately superior to the taxon referenced in the taxon record. Recommended best practice is to order the list starting with the highest rank and separating the names for each rank with a semi-colon (";").
Comment:
Example: "Animalia;Chordata;Vertebrata;Mammalia;Theria;Eutheria;Rodentia;Hystricognatha;Hystricognathi;Ctenomyidae;Ctenomyini;Ctenomys". For discussion see http://code.google.com/p/darwincore/wiki/Taxon
The nomenclatural code (or codes in the case of an ambiregnal name) under which the scientificName is constructed. Recommended best practice is to use a controlled vocabulary.
The status of the use of the scientificName as a label for a taxon. Requires taxonomic opinion to define the scope of a taxon. Rules of priority then are used to define the taxonomic status of the nomenclature contained in that scope, combined with the experts opinion. It must be linked to a specific taxonomic reference that defines the concept. Recommended best practice is to use a controlled vocabulary.
The status related to the original publication of the name and its conformance to the relevant rules of nomenclature. It is based essentially on an algorithm according to the business rules of the code. It requires no taxonomic opinion.
The relationship of the resource identified by relatedResourceID to the subject (optionally identified by the resourceID). Recommended best practice is to use a controlled vocabulary.
The date-time on which the relationship between the two resources was established. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://code.google.com/p/darwincore/wiki/ResourceRelationship
An identifier for the MeasurementOrFact (information pertaining to measurements, facts, characteristics, or assertions). May be a global unique identifier or an identifier specific to the data set.
The date on which the MeasurementOrFact was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://code.google.com/p/darwincore/wiki/MeasurementOrFact
An existence of an Organism (sensu http://rs.tdwg.org/dwc/terms/Organism) at a particular place at a particular time.
Comment:
Examples: A wolf pack on the shore of Kluane Lake in 1988. A virus in a plant leaf in a the New York Botanical Garden at 15:29 on 2014-10-23. A fungus in Central Park in the summer of 1929. For discussion see http://terms.tdwg.org/wiki/dwc:Occurrence
A particular organism or defined group of organisms considered to be taxonomically homogeneous.
Comment:
Instances of the Organism class are intended to facilitate linking of one or more Identification instances to one or more Occurrence instances. Therefore, things that are typically assigned scientific names (such as viruses, hybrids, and lichens) and aggregates whose occurrences are typically recorded (such as packs, clones, and colonies) are included in the scope of this class. For discussion see http://terms.tdwg.org/wiki/dwc:Organism
A physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.
Comment:
Examples: A whole organism preserved in a collection. A part of an organism isolated for some purpose. A soil sample. A marine microbial sample. For discussion see http://terms.tdwg.org/wiki/dwc:MaterialSample
A group of organisms (sensu http://purl.obolibrary.org/obo/OBI_0100026) considered by taxonomists to form a homogeneous unit.
Comment:
Example: The genus Truncorotaloides as published by Brönnimann et al. in 1953 in the Journal of Paleontology Vol. 27(6) p. 817-820. For discussion see http://terms.tdwg.org/wiki/dwc:Taxon
Resources can be thought of as identifiable records or instances of classes and may include, but need not be limited to Occurrences, Organisms, MaterialSamples, Events, Locations, GeologicalContexts, Identifications, or Taxa. Examples: The weight of an organism in grams. The number of placental scars. For discussion see http://terms.tdwg.org/wiki/dwc:MeasurementOrFact
Resources can be thought of as identifiable records or instances of classes and may include, but need not be limited to Occurrences, Organisms, MaterialSamples, Events, Locations, GeologicalContexts, Identifications, or Taxa. Example: An instance of an Organism is the mother of another instance of an Organism. For discussion see http://terms.tdwg.org/wiki/dwc:ResourceRelationship
The most recent date-time on which the resource was changed. For Darwin Core, recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://terms.tdwg.org/wiki/dwc:modified
A legal document giving official permission to do something with the resource.
Comment:
Examples: "http://creativecommons.org/publicdomain/zero/1.0/legalcode", "http://creativecommons.org/licenses/by/4.0/legalcode". For discussion see http://terms.tdwg.org/wiki/dwc:license
Information about who can access the resource or an indication of its security status. Access Rights may include information regarding access or restrictions based on privacy, security, or other policies.
A bibliographic reference for the resource as a statement indicating how this record should be cited (attributed) when used. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.
Comment:
Examples: "Ctenomys sociabilis (MVZ 165861)" for a specimen, "Oliver P. Pearson. 1985. Los tuco-tucos (genera Ctenomys) de los Parques Nacionales Lanin y Nahuel Huapi, Argentina Historia Natural, 5(37):337-343." for a Taxon. For discussion see http://terms.tdwg.org/wiki/dwc:bibliographicCitation
A related resource that is referenced, cited, or otherwise pointed to by the described resource.
Comment:
Examples: "http://mvzarctos.berkeley.edu/guid/MVZ:Mamm:165861"; "http://www.catalogueoflife.org/annual-checklist/show_species_details.php?record_id=6197868". For discussion see http://terms.tdwg.org/wiki/dwc:references
Recommended best practice is to use a controlled vocabulary such as the list of Darwin Core classes. Examples: "PreservedSpecimen", "FossilSpecimen", "LivingSpecimen", "HumanObservation", "MachineObservation". For discussion see http://terms.tdwg.org/wiki/dwc:basisOfRecord
Actions taken to make the shared data less specific or complete than in its original form. Suggests that alternative data of higher quality may be available on request.
A list of additional measurements, facts, characteristics, or assertions about the record. Meant to provide a mechanism for structured content.
Comment:
The recommended best practice is to use a key:value encoding schema such as JSON. Examples: "{'heightInMeters':'1.5'}", "{'tragusLengthInMeters':'0.014', 'weightInGrams':'120'}", "{'natureOfID':'expert identification', 'identificationEvidence':'cytochrome B sequence'}", "{'relativeHumidity':'28', 'airTemperatureInCelcius':'22', 'sampleSizeInKilograms':'10'}", "{'aspectHeading':'277', 'slopeInDegrees':'6'}", "{'iucnStatus':'vulnerable', 'taxonDistribution':'Neuquén, Argentina'}". For discussion see http://terms.tdwg.org/wiki/dwc:dynamicProperties
An identifier for the Occurrence (as opposed to a particular digital record of the occurrence). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the occurrenceID globally unique.
Comment:
For a specimen in the absence of a bona fide global unique identifier, for example, use the form: "urn:catalog:[institutionCode]:[collectionCode]:[catalogNumber]. Examples: "urn:lsid:nhm.ku.edu:Herps:32", "urn:catalog:FMNH:Mammal:145732". For discussion see http://terms.tdwg.org/wiki/dwc:occurrenceID
An identifier given to the Occurrence at the time it was recorded. Often serves as a link between field notes and an Occurrence record, such as a specimen collector's number.
A list (concatenated and separated) of names of people, groups, or organizations responsible for recording the original Occurrence. The primary collector or observer, especially one who applies a personal identifier (recordNumber), should be listed first.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). The primary collector or observer, especially one who applies a personal identifier (recordNumber), should be listed first. Examples: "José E. Crespo", "Oliver P. Pearson | Anita K. Pearson" where the value in recordNumber "OPP 7101" corresponds to the number for the specimen in the field catalog (collector number) of Oliver P. Pearson. For discussion see http://terms.tdwg.org/wiki/dwc:recordedBy
The age class or life stage of the biological individual(s) at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.
A description of the behavior shown by the subject at the time the Occurrence was recorded. Recommended best practice is to use a controlled vocabulary.
The process by which the biological individual(s) represented in the Occurrence became established at the location. Recommended best practice is to use a controlled vocabulary.
A list (concatenated and separated) of preparations and preservation methods for a specimen.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "fossil", "cast", "photograph", "DNA extract", "skin | "skull | skeleton", "whole animal (ETOH) | tissue (EDTA)". For discussion see http://terms.tdwg.org/wiki/dwc:preparations
The current state of a specimen with respect to the collection identified in collectionCode or collectionID. Recommended best practice is to use a controlled vocabulary.
A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of media associated with the Occurrence.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "http://arctos.database.museum/SpecimenImages/UAMObs/Mamm/2/P7291179.JPG", "http://204.140.246.24/Fish/Collection%20Pictures/10118-00.jpg | http://204.140.246.24/Fish/Collection%20Pictures/10118-00a.jpg". For discussion see http://terms.tdwg.org/wiki/dwc:associatedMedia
A list (concatenated and separated) of identifiers (publication, bibliographic reference, global unique identifier, URI) of literature associated with the Occurrence.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "http://www.sciencemag.org/cgi/content/abstract/322/5899/261", "Christopher J. Conroy, Jennifer L. Neuwald. 2008. Phylogeographic study of the California vole, Microtus californicus Journal of Mammalogy, 89(3):755-767.", "Steven R. Hoofer and Ronald A. Van Den Bussche. 2001. Phylogenetic Relationships of Plecotine Bats and Allies Based on Mitochondrial Ribosomal Sequences. Journal of Mammalogy 82(1):131-137. | Walker, Faith M., Jeffrey T. Foster, Kevin P. Drees, Carol L. Chambers. 2014. Spotted bat (Euderma maculatum) microsatellite discovery using illumina sequencing. Conservation Genetics Resources.". For discussion see http://terms.tdwg.org/wiki/dwc:associatedReferences
A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of genetic sequence information associated with the Occurrence.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "http://www.ncbi.nlm.nih.gov/nuccore/U34853.1", "http://www.ncbi.nlm.nih.gov/nuccore/GU328060 | http://www.ncbi.nlm.nih.gov/nuccore/AF326093". For discussion see http://terms.tdwg.org/wiki/dwc:associatedSequences
A list (concatenated and separated) of identifiers or names of taxa and their associations with the Occurrence.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '), and to separate the relationship from the taxon with a colon (':'). Examples: "host: Quercus alba", "parasitoid of:Cyclocephala signaticollis | predator of Apis mellifera". For discussion see http://terms.tdwg.org/wiki/dwc:associatedTaxa
A list (concatenated and separated) of previous or alternate fully qualified catalog numbers or other human-used identifiers for the same Occurrence, whether in the current or any other data set or collection.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "FMNH:Mammal:1234", "NPS YELLO6778 | MBG 33424". For discussion see http://terms.tdwg.org/wiki/dwc:otherCatalogNumbers
An identifier for the Organism instance (as opposed to a particular digital record of the Organism). May be a globally unique identifier or an identifier specific to the data set.
A description of the kind of Organism instance. Can be used to indicate whether the Organism instance represents a discrete organism or if it represents a particular type of aggregation. Recommended best practice is to use a controlled vocabulary.
A list (concatenated and separated) of identifiers of other Organisms and their associations to this Organism.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "sibling of MXA-232", "mother of MXA-231 | mother of MXA-232". For discussion see http://terms.tdwg.org/wiki/dwc:associatedOrganisms
A list (concatenated and separated) of previous assignments of names to the Organism.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Chalepidae", "Pinus abies", "Anthus sp., field ID by G. Iglesias | Anthus correndera, expert ID by C. Cicero 2009-02-12 based on morphology". For discussion see http://terms.tdwg.org/wiki/dwc:previousIdentifications
An identifier for the MaterialSample (as opposed to a particular digital record of the material sample). In the absence of a persistent global unique identifier, construct one from a combination of identifiers in the record that will most closely make the materialSampleID globally unique.
An identifier for the set of information associated with an Event (something that occurs at a place and time). May be a global unique identifier or an identifier specific to the data set.
The date-time or interval during which an Event occurred. For occurrences, this is the date-time when the event was recorded. Not suitable for a time in a geological context. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://terms.tdwg.org/wiki/dwc:eventDate
The time or interval during which an Event occurred. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "14:07-0600" is 2:07pm in the time zone six hours earlier than UTC, "08:40:21Z" is 8:40:21am UTC, "13:00:00Z/15:30:00Z" is the interval between 1pm UTC and 3:30pm UTC. For discussion see http://terms.tdwg.org/wiki/dwc:eventTime
The earliest ordinal day of the year on which the Event occurred (1 for January 1, 365 for December 31, except in a leap year, in which case it is 366).
The name of, reference to, or description of the method or protocol used during an Event.
Comment:
Examples: "UV light trap", "mist net", "bottom trawl", "ad hoc observation", "point count", "Penguins from space: faecal stains reveal the location of emperor penguin colonies, http://dx.doi.org/10.1111/j.1466-8238.2009.00467.x", "Takats et al. 2001. Guidelines for Nocturnal Owl Monitoring in North America. Beaverhill Bird Observatory and Bird Studies Canada, Edmonton, Alberta. 32 pp.", "http://www.bsc-eoc.org/download/Owl.pdf". For discussion see http://terms.tdwg.org/wiki/dwc:samplingProtocol
An identifier for the set of location information (data associated with dcterms:Location). May be a global unique identifier or an identifier specific to the data set.
An identifier for the geographic region within which the Location occurred. Recommended best practice is to use an persistent identifier from a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
A list (concatenated and separated) of geographic names less specific than the information captured in the locality term.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '), with terms in order from least specific to most specific. Examples: "North Atlantic Ocean", "South America | Argentina | Patagonia | Parque Nacional Nahuel Huapi | Neuquén | Los Lagos" with accompanying values "South America" in Continent, "Argentina" in Country, "Neuquén" in StateProvince, and "Los Lagos" in County. For discussion see http://terms.tdwg.org/wiki/dwc:higherGeography
The name of the continent in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The name of the water body in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The name of the island group in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The name of the island on or near which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The name of the country or major administrative unit in which the Location occurs. Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.
The full, unabbreviated name of the next smaller administrative region than stateProvince (county, shire, department, etc.) in which the Location occurs.
The full, unabbreviated name of the next smaller administrative region than county (city, municipality, etc.) in which the Location occurs. Do not use this term for a nearby named place that does not contain the actual location.
The specific description of the place. Less specific geographic information can be provided in other geographic terms (higherGeography, continent, country, stateProvince, county, municipality, waterBody, island, islandGroup). This term may contain information modified from the original to correct perceived errors or standardize the description.
The lesser distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.
Comment:
Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5". For discussion see http://terms.tdwg.org/wiki/dwc:minimumDistanceAboveSurfaceInMeters
The greater distance in a range of distance from a reference surface in the vertical direction, in meters. Use positive values for locations above the surface, negative values for locations below. If depth measures are given, the reference surface is the location given by the depth, otherwise the reference surface is the location given by the elevation.
Comment:
Example: 1.5 meter sediment core from the bottom of a lake (at depth 20m) at 300m elevation; VerbatimElevation: "300m" MinimumElevationInMeters: "300", MaximumElevationInMeters: "300", VerbatimDepth: "20m", MinimumDepthInMeters: "20", MaximumDepthInMeters: "20", minimumDistanceAboveSurfaceInMeters: "0", maximumDistanceAboveSurfaceInMeters: "-1.5". For discussion see http://terms.tdwg.org/wiki/dwc:maximumDistanceAboveSurfaceInMeters
The geographic latitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are north of the Equator, negative values are south of it. Legal values lie between -90 and 90, inclusive.
The geographic longitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are east of the Greenwich Meridian, negative values are west of it. Legal values lie between -180 and 180, inclusive.
The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which the geographic coordinates given in decimalLatitude and decimalLongitude as based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".
The horizontal distance (in meters) from the given decimalLatitude and decimalLongitude describing the smallest circle containing the whole of the Location. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Zero is not a valid value for this term.
Comment:
Examples: "30" (reasonable lower limit of a GPS reading under good conditions if the actual precision was not recorded at the time), "71" (uncertainty for a UTM coordinate having 100 meter precision and a known spatial reference system). For discussion see http://terms.tdwg.org/wiki/dwc:coordinateUncertaintyInMeters
The ratio of the area of the point-radius (decimalLatitude, decimalLongitude, coordinateUncertaintyInMeters) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given point-radius does not completely contain the original representation. The pointRadiusSpatialFit is undefined (and should be left blank) if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the pointRadiusSpatialFit is 1.
Comment:
Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006. For discussion see http://terms.tdwg.org/wiki/dwc:pointRadiusSpatialFit
The verbatim original spatial coordinates of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
The verbatim original latitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
The verbatim original longitude of the Location. The coordinate ellipsoid, geodeticDatum, or full Spatial Reference System (SRS) for these coordinates should be stored in verbatimSRS and the coordinate system should be stored in verbatimCoordinateSystem.
The spatial coordinate system for the verbatimLatitude and verbatimLongitude or the verbatimCoordinates of the Location. Recommended best practice is to use a controlled vocabulary.
The ellipsoid, geodetic datum, or spatial reference system (SRS) upon which coordinates given in verbatimLatitude and verbatimLongitude, or verbatimCoordinates are based. Recommended best practice is use the EPSG code as a controlled vocabulary to provide an SRS, if known. Otherwise use a controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value "unknown".
A Well-Known Text (WKT) representation of the shape (footprint, geometry) that defines the Location. A Location may have both a point-radius representation (see decimalLatitude) and a footprint representation, and they may differ from each other.
Comment:
Example: the one-degree bounding box with opposite corners at (longitude=10, latitude=20) and (longitude=11, latitude=21) would be expressed in well-known text as POLYGON ((10 20, 11 20, 11 21, 10 21, 10 20)). For discussion see http://terms.tdwg.org/wiki/dwc:footprintWKT
A Well-Known Text (WKT) representation of the Spatial Reference System (SRS) for the footprintWKT of the Location. Do not use this term to describe the SRS of the decimalLatitude and decimalLongitude, even if it is the same as for the footprintWKT - use the geodeticDatum instead.
Comment:
Example: The WKT for the standard WGS84 SRS (EPSG:4326) is "GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137,298.257223563]],PRIMEM["Greenwich",0],UNIT["Degree",0.0174532925199433]]" without the enclosing quotes. For discussion see http://terms.tdwg.org/wiki/dwc:footprintSRS
The ratio of the area of the footprint (footprintWKT) to the area of the true (original, or most specific) spatial representation of the Location. Legal values are 0, greater than or equal to 1, or undefined. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given footprint does not completely contain the original representation. The footprintSpatialFit is undefined (and should be left blank) if the original representation is a point and the given georeference is not that same point. If both the original and the given georeference are the same point, the footprintSpatialFit is 1.
Comment:
Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006. For discussion see http://terms.tdwg.org/wiki/dwc:footprintSpatialFit
A list (concatenated and separated) of names of people, groups, or organizations who determined the georeference (spatial representation) for the Location.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Brad Millen (ROM)", "Kristina Yamamoto (MVZ) | Janet Fang (MVZ)". For discussion see http://terms.tdwg.org/wiki/dwc:georeferencedBy
The date on which the Location was georeferenced. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://terms.tdwg.org/wiki/dwc:georeferencedDate
A description or reference to the methods used to determine the spatial footprint, coordinates, and uncertainties.
Comment:
Examples: "Guide to Best Practices for Georeferencing. (Chapman and Wieczorek, eds. 2006). Global Biodiversity Information Facility.", "MaNIS/HerpNet/ORNIS Georeferencing Guidelines", "Georeferencing Quick Reference Guide". For discussion see http://terms.tdwg.org/wiki/dwc:georeferenceProtocol
A list (concatenated and separated) of maps, gazetteers, or other resources used to georeference the Location, described specifically enough to allow anyone in the future to use the same resources.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "GeoLocate", "USGS 1:24000 Florence Montana Quad | Terrametrics 2008 on Google Earth". For discussion see http://terms.tdwg.org/wiki/dwc:georeferenceSources
A categorical description of the extent to which the georeference has been verified to represent the best possible spatial description. Recommended best practice is to use a controlled vocabulary.
Notes or comments about the spatial description determination, explaining assumptions made in addition or opposition to the those formalized in the method referred to in georeferenceProtocol.
An identifier for the set of information associated with a GeologicalContext (the location within a geological context, such as stratigraphy). May be a global unique identifier or an identifier specific to the data set.
The full name of the earliest possible geochronologic eon or lowest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic eon or highest chrono-stratigraphic eonothem or the informal name ("Precambrian") attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic era or lowest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic era or highest chronostratigraphic erathem attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic period or lowest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic period or highest chronostratigraphic system attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic epoch or lowest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic epoch or highest chronostratigraphic series attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the earliest possible geochronologic age or lowest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
The full name of the latest possible geochronologic age or highest chronostratigraphic stage attributable to the stratigraphic horizon from which the cataloged item was collected.
An identifier for the Identification (the body of information associated with the assignment of a scientific name). May be a global unique identifier or an identifier specific to the data set.
A brief phrase or a standard term ("cf.", "aff.") to express the determiner's doubts about the Identification.
Comment:
Examples: 1) For the determination "Quercus aff. agrifolia var. oxyadenia", identificationQualifier would be "aff. agrifolia var. oxyadenia" with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank. 2) For the determination "Quercus agrifolia cf. var. oxyadenia", identificationQualifier would be "cf. var. oxyadenia " with accompanying values "Quercus" in genus, "agrifolia" in specificEpithet, "oxyadenia" in infraspecificEpithet, and "var." in rank. For discussion see http://terms.tdwg.org/wiki/dwc:identificationQualifier
A list (concatenated and separated) of nomenclatural types (type status, typified scientific name, publication) applied to the subject.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "holotype of Ctenomys sociabilis. Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "holotype of Pinus abies | holotype of Picea abies". For discussion see http://terms.tdwg.org/wiki/dwc:typeStatus
A list (concatenated and separated) of names of people, groups, or organizations who assigned the Taxon to the subject.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "James L. Patton", "Theodore Pappenfuss | Robert Macey". For discussion see http://terms.tdwg.org/wiki/dwc:identifiedBy
The date on which the subject was identified as representing the Taxon. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://terms.tdwg.org/wiki/dwc:dateIdentified
A list (concatenated and separated) of references (publication, global unique identifier, URI) used in the Identification.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Aves del Noroeste Patagonico. Christie et al. 2004.", "Stebbins, R. Field Guide to Western Reptiles and Amphibians. 3rd Edition. 2003. | Irschick, D.J. and Shaffer, H.B. (1997). ''The polytypic species revisited: Morphological differentiation among tiger salamanders (Ambystoma tigrinum) (Amphibia: Caudata).'' Herpetologica, 53(1), 30-49.". For discussion see http://terms.tdwg.org/wiki/dwc:identificationReferences
A categorical indicator of the extent to which the taxonomic identification has been verified to be correct. Recommended best practice is to use a controlled vocabulary such as that used in HISPID/ABCD.
An identifier for the set of taxon information (data associated with the Taxon class). May be a global unique identifier or an identifier specific to the data set.
Comment:
Examples: "8fa58e08-08de-4ac1-b69c-1235340b7001", "32567", "http://species.gbif.org/abies_alba_1753", "urn:lsid:gbif.org:usages:32567". For discussion see http://terms.tdwg.org/wiki/dwc:taxonID
An identifier for the name usage (documented meaning of the name according to a source) of the currently valid (zoological) or accepted (botanical) taxon.
An identifier for the name usage (documented meaning of the name according to a source) of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.
An identifier for the name usage (documented meaning of the name according to a source) in which the terminal element of the scientificName was originally established under the rules of the associated nomenclaturalCode.
The full scientific name, with authorship and date information if known. When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the IdentificationQualifier term.
The full name, with authorship and date information if known, of the direct, most proximate higher-rank parent taxon (in a classification) of the most specific element of the scientificName.
The taxon name, with authorship and date information if known, as it originally appeared when first established under the rules of the associated nomenclaturalCode. The basionym (botany) or basonym (bacteriology) of the scientificName or the senior/earlier homonym for replaced names.
The reference to the source in which the specific taxon concept circumscription is defined or implied - traditionally signified by the Latin "sensu" or "sec." (from secundum, meaning "according to"). For taxa that result from identifications, a reference to the keys, monographs, experts and other sources should be given.
Comment:
Example: "McCranie, J. R., D. B. Wake, and L. D. Wilson. 1996. The taxonomic status of Bolitoglossa schmidti, with comments on the biology of the Mesoamerican salamander Bolitoglossa dofleini (Caudata: Plethodontidae). Carib. J. Sci. 32:395-398.", "Werner Greuter 2008", "Lilljeborg 1861, Upsala Univ. Arsskrift, Math. Naturvet., pp. 4, 5". For discussion see http://terms.tdwg.org/wiki/dwc:nameAccordingTo
A reference for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.
Comment:
Examples: "Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388", "Forel, Auguste, Diagnosies provisoires de quelques espèces nouvelles de fourmis de Madagascar, récoltées par M. Grandidier., Annales de la Societe Entomologique de Belgique, Comptes-rendus des Seances 30, 1886". For discussion see http://terms.tdwg.org/wiki/dwc:namePublishedIn
A list (concatenated and separated) of taxa names terminating at the rank immediately superior to the taxon referenced in the taxon record.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '), with terms in order from the highest taxonomic rank to the lowest. Examples: "Animalia", "Animalia | Chordata | Vertebrata | Mammalia | Theria | Eutheria | Rodentia | Hystricognatha | Hystricognathi | Ctenomyidae | Ctenomyini | Ctenomys". For discussion see http://terms.tdwg.org/wiki/dwc:higherClassification
The nomenclatural code (or codes in the case of an ambiregnal name) under which the scientificName is constructed. Recommended best practice is to use a controlled vocabulary.
The status of the use of the scientificName as a label for a taxon. Requires taxonomic opinion to define the scope of a taxon. Rules of priority then are used to define the taxonomic status of the nomenclature contained in that scope, combined with the experts opinion. It must be linked to a specific taxonomic reference that defines the concept. Recommended best practice is to use a controlled vocabulary.
The status related to the original publication of the name and its conformance to the relevant rules of nomenclature. It is based essentially on an algorithm according to the business rules of the code. It requires no taxonomic opinion.
An identifier for the MeasurementOrFact (information pertaining to measurements, facts, characteristics, or assertions). May be a global unique identifier or an identifier specific to the data set.
A list (concatenated and separated) of names of people, groups, or organizations who determined the value of the MeasurementOrFact.
Comment:
The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Rob Guralnick", "Julie Woodruff | Eileen Lacey". For discussion see http://terms.tdwg.org/wiki/dwc:measurementDeterminedBy
The date on which the MeasurementOrFact was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://terms.tdwg.org/wiki/dwc:measurementDeterminedDate
The relationship of the resource identified by relatedResourceID to the subject (optionally identified by the resourceID). Recommended best practice is to use a controlled vocabulary.
The date-time on which the relationship between the two resources was established. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
Comment:
Examples: "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. For discussion see http://terms.tdwg.org/wiki/dwc:relationshipEstablishedDate
-All terms in the Darwin Core must be assigned a unique Uniform Resource Identifier (URI). For convenience, the term URIs that are
-assigned and managed by the Darwin Core Task Group are grouped into collections known as Darwin
-Core namespaces. This document describes how term URIs are allocated by the Darwin Core Task Group
-and the policies associated with Darwin Core namespaces.
-
-
-
-
Contributors:
-
John Wieczorek (MVZ), Markus Döring (GBIF), Renato De Giovanni (CRIA), Tim Robertson (GBIF), Dave Vieglais (KUNHM)
-
-
-
Legal:
-
This document is governed by the standard legal, copyright, licensing provisions and disclaimers issued by the Taxonomic Databases Working Group.
-Audience: This document is targeted toward those who want to make changes to the Darwin Core, either by refining terms that already
-exist or by adding new terms to increase the capabilities of the standard.
-
-This document and the policies contained herein are modeled on the Dublin Core Metadata Initiative
-Namespace Policy [DCMINAMESPACEPOLICY].
-All terms in the Darwin Core must be identified with a unique Uniform Resource Identifier (URI). For convenience, the term URIs are
-grouped into collections known as Darwin
-Core namespaces. This document describes the policies associated with Darwin Core namespaces and how term
-URIs are allocated by the Darwin Core Task Group
-[DWC-TASK].
+
+
Darwin Core Namespace Policy
-
-
2. Namespace URIs
+
+
+
+
Title:
-
The Darwin Core namespace URI for the collection of all Darwin Core properties, classes, and encoding schemes is:
+
Darwin Core Namespace Policy
+
-
http://rs.tdwg.org/dwc/terms/
-
+
+
Date Issued:
-
The Darwin Core namespace URI for the collection of classes in the Darwin Core Type Vocabulary
-[DWC-TYPE] is:
+
2009-02-12
+
-
http://rs.tdwg.org/dwc/dwctype/
-
+
+
Date Modified:
-
All future Darwin Core namespace URIs (additional Darwin Core controlled vocabularies for example) will conform to
-this pattern:
+
2014-11-08
+
-
http://rs.tdwg.org/dwc/namespace_label/
-
+
+
Abstract:
-
The term identifier for the current (recommended) version of a term is a URI based on the namespace and the term name
-without version information. Some example Darwin Core term identifiers follow:
+
All terms in the Darwin Core must be assigned a unique
+ Uniform Resource Identifier (URI). For convenience, the term
+ URIs that are assigned and managed by the Darwin Core Task
+ Group are grouped into collections known as Darwin Core
+ namespaces. This document describes how term URIs are allocated
+ by the Darwin Core Task Group and the policies associated with
+ Darwin Core namespaces.
+
-
http://rs.tdwg.org/dwc/terms/scientificName
-
+
+
Contributors:
-
is the Darwin Core term identifier for the scientificName property.
+
John Wieczorek (MVZ), Markus Döring (GBIF), Renato De
+ Giovanni (CRIA), Tim Robertson (GBIF), Dave Vieglais
+ (KUNHM)
Changes to Darwin Core terms or term declarations will occur from time to time for a variety of reasons.
-Such changes have varying implications for Darwin Core term URIs and Darwin Core namespaces. The classes of
-changes are identified and explained in the following sections along with examples and associated implications.
+
+
Creator:
-
Any change to Darwin Core terms or term declarations will result
-in an update to the versioning information carried in the Darwin Core recommendation and/or
-Darwin Core term declaration associated with that term. Specifically, a new version
-of the term will be created with appropriate information in the Version, Replaces, and
-DateModified attributes of the new term, and with the identifying version information of the
-new term in the Is Replaced By attribute of the term being updated.
+
Darwin Core Task Group
+
-
3.1. Minor editorial errata
+
+
Identifier:
-
Errors of spelling, punctuation, or other clerical mistakes discovered in Darwin Core recommendations and/or
-Darwin Core term declarations will be corrected without a comment period, following notification to the TDWG
-Architecture Group [TDWG-TAG], as long as, in
-the judgment of the TDWG Architecture Group, there are no implications for negative impact on users or applications that rely
-on those Darwin Core term declarations. Minor editorial changes of this type will result in no changes to Darwin
-Core term URIs, will not undergo a request for comments, and will not result in a decision
-[DECISIONS].
+
Errors of substance discovered in Darwin Core recommendations and/or Darwin Core
-term declarations will trigger public notification of the correction to the Darwin Core mailing
-list [TDWG-CONTENT].
-Errors that, in the judgment of the TDWG Architecture Group, compromise the immediate usefulness or
-accuracy of systems based on Darwin Core will be corrected immediately (for example, an incorrect
-URL to a resource external to Darwin Core). Others will be corrected following a 30-day public
-comment period to assure that changes do not adversely effect systems or applications which rely on
-the Darwin Core namespace infrastructure. Substantive editorial changes of this type will
-result in no changes to Darwin Core term URIs, and will not result in a decision
-[DECISIONS].
+
Changes of definitions within Darwin Core recommendations and/or Darwin Core term
-declarations will be reflected in the affected Darwin Core recommendation and/or
-Darwin Core term declaration. Semantic changes of this type will
-undergo a request for comments, and will result in a decision
-[DECISIONS]. If, in the judgment of the TDWG Architecture Group, such
-changes of meaning are likely to have substantial impact on either machine processing of
-Darwin Core terms or the functional semantics of the terms, then these changes
-will be reflected in a change of URI for the Darwin Core term or terms in question.
-The URIs for any new Darwin Core namespaces resulting from such changes will conform to
-the Darwin Core namespace URI pattern defined above.
+
Requests for semantic changes to a term should be made to the Technical Architecture Group
-[TDWG-TAG], and should consist of a complete list of attributes to be changed
-along with a statement of justification for the changes.
+
+
Document Status:
-
3.4. Addition of Darwin Core term declarations to existing Darwin Core namespaces
+
Current Standard
+
+
+
+
+
+
+
+
-
New terms may be added to existing Darwin Core namespaces based on
-public demand. Addition of terms to existing Darwin Core namespaces will not trigger
-changes in Darwin Core Namespace URIs. Additional term requests that have been determined by the Technical Architecture
-Group to have merit will undergo a request for comments and will not result in a decision
-[DECISIONS].
+
1. Introduction
Audience: This document is targeted toward
+ those who want to make changes to the Darwin Core, either by refining terms
+ that already exist or by adding new terms to increase the capabilities of the
+ standard.
-
Requests for additional terms should be made to the Technical Architecture Group
-[TDWG-TAG], and should consist of a complete list of
-attributes as given in the term definitions section of the Darwin Core Terms Complete History [HISTORY] along
-with a statement of justification for the new term, including an explanation of why no existing term will suffice.
+
This document and the policies contained herein are modeled on the
+ Dublin Core Metadata Initiative Namespace Policy [DCMINAMESPACEPOLICY].
+ All terms in the Darwin Core must be identified with a unique Uniform
+ Resource Identifier (URI). For convenience, the term URIs are grouped into
+ collections known as Darwin Core namespaces. This document describes
+ the policies associated with Darwin Core namespaces and how term URIs are
+ allocated by the Darwin Core Task Group [DWC-TASK].
-
-
4. Persistence Policy
-
-TDWG recognizes that people and applications depend on the persistence of formal documents and machine processable schemas
-that have been made publicly available. In particular, the stability of Darwin Core term URIs and Darwin Core
-namespace URIs is critical to interoperability over time. Thus, the wide promulgation of this set of URIs
-dictates that they be maintained to support legacy applications that have adopted them.
+
2. Namespace URIs
-
-
-
-
- Copyright 2009-2013 - Biodiversity Information Standards - TDWG - Contact Us
-
The Darwin Core namespace URI for the collection of all Darwin Core
+ properties, classes, and encoding schemes is:
+
+http://rs.tdwg.org/dwc/terms/
+
-
-
-
+
The term identifier for the current (recommended) version of a term is a
+ URI based on the namespace and the term name without version information.
+ Some example Darwin Core term identifiers follow:
+
+http://rs.tdwg.org/dwc/terms/scientificName
+
-
\ No newline at end of file
+
is the Darwin Core term identifier for the scientificName property,
+ while
is the Darwin Core term identifier for the MachineObservation
+ class.
+
+
All Darwin Core identifiers will dereference to a Darwin Core term
+ declaration for the identified term.
+
+
3. Term Change Policy
+
+
Changes to Darwin Core recommendations or term declarations will occur
+ from time to time for a variety of reasons. Changes have varying implications
+ for the decision making process and for versioning Darwin Core documents and
+ term URIs. The types of changes and appropriate processes are identified and
+ explained in the following sections.
+
+
Reporting issues: In all cases the proposed change should be
+ reported to the Technical Architecture Group [TDWG-TAG] and the outcome of the
+ proposal should be announced on the Darwin Core mailing list [TDWG-CONTENT].
+
+
Decisions: In cases where an Executive decision is required,the
+ Technical Architecture Group will conduct a minimum 30-day public
+ comment period on the Darwin Core mailing list [TDWG-CONTENT],
+ during which the proposal can be refined based on discussion in an effort to
+ reach consensus (no dissenting opinion expressed publicly on the mailing list
+ for 30 days from the most recent iteration). If a consensus is reached, the
+ proposal will be presented by the Technical Architecture Group to the
+ Executive Committee for a decision [DECISIONS] within 30 days.
+
+
Versions: In cases where a decision requires a version change, the
+ attributes Status (recommended, superseded, or deprecated), Date
+ Issued, Date Modified, Decision, Version,
+ Replaces, and Is Replaced By will be modified in the affected
+ terms as appropriate.
+
+
3.1. Minor editorial errata
+
+
An error in spelling, punctuation, grammar, or other clerical mistake
+ discovered in a Darwin Core recommendation or term declaration may be
+ corrected without a public comment period or Executive Decision. Minor
+ editorial changes of this type do not require a version change for the
+ affected term and/or documents.
+
+
3.2. Substantive editorial errata
+
+
A substantive error is one that compromises the usefulness or accuracy of
+ systems based on Darwin Core. Those that are unequivocal (for example, an
+ incorrect URI or reference) may be treated as minor editorial errata (Section
+ 3.1).
+
+
Otherwise, the Technical Architecture Group will conduct a public
+ comment period and seek an Executive decision to find a solution that
+ minimizes adverse effects on existing applications. Changes of this nature
+ require a version change for the affected term and/or documents.
+
+
3.3. Semantic changes to Darwin Core terms
+
+
Darwin Core terms may be changed based on public demand and consensus. A
+ request to the Technical Architecture Group for a term change should
+ consist of proposed values for the complete list of attributes given in the
+ term definitions section of the Darwin Core Terms Complete History
+ [HISTORY] along with a statement of
+ justification for the change.
+
+
Term changes that are likely to have substantial functional impact on
+ human understanding or machine processing will posted for public commentary
+ and an Executive decision. Changes of this nature require a version change
+ for the affected term and/or documents.
+
+
3.4. Addition of Darwin Core terms
+
+
New terms may be added to the Darwin Core namespaces based on public
+ demand and consensus. A request to the Technical Architecture Group
+ [TDWG-TAG] for a new term should
+ consist of proposed values for the complete list of attributes given in the
+ term definitions section of the Darwin Core Terms Complete History
+ [HISTORY] along with a statement of
+ justification for the new term, including an explanation of why no existing
+ term will suffice.
+
+
New term proposals will be posted for public commentary and an Executive
+ decision. Changes of this nature require a version change for the affected
+ term and/or documents.
+
+
4. Persistence Policy
+
+
TDWG recognizes that people and applications depend on the persistence of
+ formal documents and machine processable schemas that have been made publicly
+ available. In particular, the stability of Darwin Core term URIs and Darwin
+ Core namespace URIs is critical to interoperability over time. Thus, the wide
+ promulgation of this set of URIs dictates that they be maintained to support
+ legacy applications that have adopted them.
-Audience: This document is targeted toward those who want to share biodiversity information using the simplest methods
-and structure - the Simple Darwin Core. It explains the uses and limitations of this structure and how to expand upon it.
-
-
-
1.1 What is Simple Darwin Core?
-The Simple Darwin Core is a predefined subset of the terms that have common use across a wide variety of biodiversity
-applications. The terms used in the Simple Darwin Core are those that are found at the cross-section of taxonomic names,
-places, and events that document biological occurrences on the planet. The two driving principles are simplicity and
-flexibility.
+
+
Simple Darwin Core
-
-
1.2 What makes it simple?
-The Simple Darwin Core is simple in that it assumes (and allows) no structure beyond the concept of rows and columns,
-which might be thought of as attributes and their values, or fields and records. The words field and record will be
-used throughout the rest of the document to refer to the two dimensions of the Simple Darwin Core structure. Think
-of the term names as the field names. In other words, a Simple Darwin Core record could be captured in a spreadsheet
-or in a single database table.
+
+
+
+
Title:
-
-
1.3 What makes it flexible?
-The Simple Darwin Core has minimal restrictions on which fields are required (none).
-You might argue that there should be more required fields, that there isn't anything useful you can do without them. That
-is partially true. A record with no fields in it wouldn't be very interesting, but there is a difference between
-requiring that there be a field in a record and requiring that a particular field be in all records.
-By having no required field restriction, the Simple Darwin Core can be used to share any
-meaningful combination of fields - for example, to share "just names", or "just places", or
-observations of individuals detected in the wild at a given place and time following a method (an occurrence). This
-flexibility promotes the reuse of the terms and sharing mechanisms for a wide variety of services.
-
+
Simple Darwin Core
+
-
-
1.4 Are there any rules?
-There are just a few general guiding principles on how to make the best use of the Simple Darwin Core:
-
-
Any Darwin Core term name can be used as a field name.
Use the dcterms:type field to say what Dublin Core type
-(PhysicalObject, StillImage, MovingImage, Sound) the record represents, if possible.
-
Use the basisOfRecord field to say what Darwin Core type
-(PreservedSpecimen, FossilSpecimen, LivingSpecimen, HumanObservation, MachineObservation, NomenclaturalChecklist, Taxon, Occurrence, MaterialSample, Location, Event) the record represents.
-
Populate fields with data that match the definition of the field.
-
Use the controlled vocabulary for the values of fields that recommend them.
If data are shared in lower quality than the original, use dataGeneralizations
-to say so.
-
+
+
Date Issued:
-Every field in the Simple Darwin Core may appear either once or not at all in a single record -
-otherwise how could you distinguish one scientificName field from another one? Think of a database table. It
-will not allow you to have the same name for two different fields. Because of this design restriction (lack of flexibility
-for the sake of simplicity), the auxiliary fields from the
-ResourceRelationship and
-MeasurementOrFact classes are of somewhat limited utility here -
-you could only share one MeasurementOrFact and one ResourceRelationship per record. You might argue then that there
-is no way to share information that requires related structures, such as a history of identifications of a specimen.
-That is mostly true. The only recourse within the Simple Darwin Core is to force the data into one of the catch all
-"list" terms such as
-dynamicProperties,
-otherCatalogNumbers,
-previousIdentifications,
-associatedMedia,
-associatedReferences,
-associatedOccurrences,
-associatedSequences,
-associatedTaxa,
-higherGeography,
-and
-higherClassification.
-For cases where rich data require rich (non-simple) structure, the Simple Darwin Core is not suitable. Instead, use
-a more capable structure such as the Access to Biological Collections Data schema
-[ABCD], or the
-Generic Darwin Core [GENERICXMLSCHEMA], or another schema built from the
-Darwin Core terms to suit the use of the data in a particular context. See the Darwin Core XML Guide
-[XMLSCHEMAGUIDE] for examples and
-references to model schemas.
-
-There is a difference between
-having data in a field and requiring that field to have a value from among a legal set of values.
-The Darwin Core is simple in that it has minimal restrictions on the contents of fields. The term descriptions give
-recommendations about the use of controlled vocabularies wherever appropriate. Data contributors are encouraged to
-follow these recommendations as well as possible. You might argue that having no restrictions will promote "dirty"
-data (data of low quality or dubious value). Consider the simple axiom "It's not what you have, but what you do with
-it that matters." If data restrictions were in place at the fundamental level, then
-a record having any non-compliant data in any of its fields could not be shared via the standard. Not only would there be
-a dearth of shared data in that case (or an unused standard), but also there would be no way to use the standard to
-build shared data cleaning tools to actually improve the situation, nor to use data services to look up alternative
-representations (language translations, for example) to serve a broader audience. The rest is up to how the records
-will be used - in other words, it is up to applications to enforce further restrictions if appropriate, and it is up
-to the stakeholders of those applications to decide what the restrictions will be for the purpose the application is
-trying to serve.
+
2009-04-21
+
-
-
1.5 How do I use Simple Darwin Core?
-The Darwin Core is simple in that data "complying with" the Simple Darwin Core can be easily shared in a variety of
-ways, including, but not limited to, text files and xml documents. Equivalent ways of sharing the same data are described
-in the sections Simple Darwin Core as Text and
-Simple Darwin Core as XML.
-
-What you need to do as a contributor of data via the Simple Darwin Core depends on the requirements of the ones
-who are going to consume those data. For example, if you have a collaborator who wants to share data via the
-Simple Darwin Core, then it may be sufficient to create a spreadsheet that contains column headers matching
-as many of the Darwin Core term names as you are both interested in sharing - just to be sure you both understand
-the meaning of the fields you share, and therefore hopefully something about their content. You might create a
-table in a database using the Simple Darwin Core as
-a model (if it met all of your needs), and then connect that database with services for sharing via the web. You
-might use that same database (or spreadsheet) to export a comma-separated value (CSV) file for upload into a
-hosted service that could serve the data on your behalf. Or you might use that same file to upload into a service
-that would allow you to add value (such as a georeference) or quality (with a data cleaning tool), or to see your
-data in the context of other shared data.
+
+
Date Modified:
-
-
1.5.1 Simple Darwin Core as Text
-The Text Guide [TEXTGUIDE] describes how to construct and format a text
-file using a simplified subset of the Fielded Text [FIELDEDTEXT]
-specification, which allows the contributor to describe the contents of a text file, or set of text files (related
-or not) through a separate configuration file (called a metafile). The metafile allows the contributor to communicate
-the structure of the content of the file or files and any relationships between them. Though it is good practice to
-describe a Simple Darwin Core file with such a metafile, it isn't strictly necessary if the file follows the
-CSV file specification and the first line of the file contains the field names. A Fielded Text metafile for
-any text file based on the Simple Darwin Core can be created by customizing the example metafile
-[SIMPLEMETAFILE] (if this link shows a blank page
-in your browser, use the View Source option to see the XML document), which includes references to all Darwin Core terms.
-Refer to the comments in the file itself as well as the metafile specification in the Text Guide
-[TEXTGUIDE] for more information.
+
2014-11-08
+
-
-
1.5.2 Simple Darwin Core as XML
-The XML Guide [XMLSCHEMAGUIDE] describes how to construct XML schemas to share
-data based on Darwin Core terms. Looking at the Simple Darwin Core XML Schema
-[SIMPLEXMLSCHEMA] using the XML Guide as a reference
-you will be able to see that the schema supports the notion of a SimpleDarwinRecord, which is just a grouping of up
-to one of each of the Darwin Core terms that are Properties (not Classes and not Type Vocabulary terms). The following example
-shows a SimpleDarwinRecordSet containing one SimpleDarwinRecord for a Taxon:
+
+
Abstract:
-
+
This document is a reference for the Simple Darwin Core
+ standard.
+
+
+
+
Contributors:
+
+
John Wieczorek (MVZ), Markus Döring (GBIF), Renato De
+ Giovanni (CRIA), Tim Robertson (GBIF), Dave Vieglais
+ (KUNHM)
+
+
+
+
Legal:
+
+
This document is governed by the standard legal, copyright,
+ licensing provisions and disclaimers issued by the Taxonomic
+ Databases Working Group.
Audience: This document is targeted toward those who want to share
+ biodiversity information using the simplest methods and structure - the
+ Simple Darwin Core. It explains the uses and limitations of this
+ structure and how to expand upon it.
+
+
+
+
1.1 What is Simple Darwin Core?
The Simple Darwin Core is a
+ predefined subset of the terms that have common use across a wide variety of
+ biodiversity applications. The terms used in the Simple Darwin Core
+ are those that are found at the cross-section of taxonomic names, places, and
+ events that document biological occurrences on the planet. The two driving
+ principles are simplicity and flexibility.
+
+
1.2 What makes it simple?
The Simple Darwin Core is simple in
+ that it assumes (and allows) no structure beyond the concept of rows and
+ columns, which might be thought of as attributes and their values, or fields
+ and records. The words field and record will be used throughout the rest of
+ the document to refer to the two dimensions of the Simple Darwin Core
+ structure. Think of the term names as the field names. In other words, a
+ Simple Darwin Core record could be captured in a spreadsheet or in a
+ single database table.
+
+
1.3 What makes it flexible?
The Simple Darwin Core has minimal
+ restrictions on which fields are required (none). You might argue that there
+ should be more required fields, that there isn't anything useful you can do
+ without them. That is partially true. A record with no fields in it wouldn't
+ be very interesting, but there is a difference between requiring that there
+ be a field in a record and requiring that a particular field be in all
+ records. By having no required field restriction, the Simple Darwin
+ Core can be used to share any meaningful combination of fields - for
+ example, to share "just names", or "just places", or observations of
+ individuals detected in the wild at a given place and time following a method
+ (an occurrence). This flexibility promotes the reuse of the terms and sharing
+ mechanisms for a wide variety of services.
+
+
+
+
1.4 Are there any rules?
There are just a few general guiding
+ principles on how to make the best use of the Simple Darwin Core:
+
+
+
Any Darwin Core term name can be used as a field name.
Use the dcterms:type field to
+ provide the name of the what Dublin Core type class(PhysicalObject,
+ StillImage, MovingImage, Sound, Text) the record represents.
+
+
+
Use the basisOfRecord field to
+ provide the name of the most specific Darwin Core class (LivingSpecimen,
+ PreservedSpecimen, FossilSpecimen, MaterialSample, HumanObservation,
+ MachineObservation, Event, Occurrence, Taxon, Identification, Organism,
+ Location, GeologicalContext, MeasurementOrFact, ResourceRelationship) the
+ record represents.
+
+
+
Populate fields with data that match the definition of the field.
+
+
Use the controlled vocabulary for the values of fields that recommend
+ them.
There is a difference between having data in a field and requiring that
+ field to have a value from among a legal set of values. The Darwin Core is
+ simple in that it has minimal restrictions on the contents of fields. The
+ term comments give recommendations about the use of controlled vocabularies
+ and how to structure content wherever appropriate. Data contributors are
+ encouraged to follow these recommendations as well as possible. You might
+ argue that having no restrictions will promote "dirty" data (data of low
+ quality or dubious value). Consider the simple axiom "It's not what you have,
+ but what you do with it that matters." If data restrictions were in place at
+ the fundamental level, then a record having any non-compliant data in any of
+ its fields could not be shared via the standard. Not only would there be a
+ dearth of shared data in that case (or an unused standard), but also there
+ would be no way to use the standard to build shared data cleaning tools to
+ actually improve the situation, nor to use data services to look up
+ alternative representations (language translations, for example) to serve a
+ broader audience. The rest is up to how the records will be used - in other
+ words, it is up to applications to enforce further restrictions if
+ appropriate, and it is up to the stakeholders of those applications to decide
+ what the restrictions will be for the purpose the application is trying to
+ serve.
+
+
1.5 How do I use Simple Darwin Core?
The Darwin Core is simple in
+ that data "complying with" the Simple Darwin Core can be easily shared
+ in a variety of ways, including, but not limited to, text files and xml
+ documents. Equivalent ways of sharing the same data are described in the
+ sections Simple Darwin Core as Text and
+ Simple Darwin Core as XML.
+
+
What you need to do as a contributor of data via the Simple Darwin
+ Core depends on the requirements of the ones who are going to consume
+ those data. For example, if you have a collaborator who wants to share data
+ via the Simple Darwin Core, then it may be sufficient to create a
+ spreadsheet that contains column headers matching as many of the Darwin Core
+ term names as you are both interested in sharing - just to be sure you both
+ understand the meaning of the fields you share, and therefore hopefully
+ something about their content. You might create a table in a database using
+ the Simple Darwin Core as a model (if it met all of your needs), and
+ then connect that database with services for sharing via the web. You might
+ use that same database (or spreadsheet) to export a comma-separated value
+ (CSV) file for upload into a hosted service that could serve the data on your
+ behalf. Or you might use that same file to upload into a service that would
+ allow you to add value (such as a georeference) or quality (with a data
+ cleaning tool), or to see your data in the context of other shared data.
+
+
+
1.5.1 Simple Darwin Core as Text
The Text Guide [TEXTGUIDE] describes how to construct and
+ format a text file using a simplified subset of the Fielded Text
+ [FIELDEDTEXT] specification, which
+ allows the contributor to describe the contents of a text file, or set of
+ text files (related or not) through a separate configuration file (called a
+ metafile). The metafile allows the contributor to communicate the structure
+ of the content of the file or files and any relationships between them.
+ Though it is good practice to describe a Simple Darwin Core file with
+ such a metafile, it isn't strictly necessary if the file follows the CSV file
+ specification and the first line of the file contains the field names. A
+ Fielded Text metafile for any text file based on the Simple Darwin
+ Core can be created by customizing the example metafile [SIMPLEMETAFILE]
+ (if this link shows a blank page in your browser, use the View Source option
+ to see the XML document), which includes references to all Darwin Core terms.
+ Refer to the comments in the file itself as well as the metafile
+ specification in the Text Guide [TEXTGUIDE] for more information.
+
+
1.5.2 Simple Darwin Core as XML
The XML Guide [XMLGUIDE] describes how to construct XML
+ schemas to share data based on Darwin Core terms. Looking at the Simple
+ Darwin Core XML Schema [SIMPLEXMLSCHEMA] using the XML
+ Guide as a reference you will be able to see that the schema supports the
+ notion of a SimpleDarwinRecord, which is just a grouping of up to one
+ of each of the Darwin Core terms that are Properties (not
+ Classes). The following example shows a SimpleDarwinRecordSet
+ containing one SimpleDarwinRecord for a Taxon:
+
<?xml version="1.0" encoding="UTF-8"?>
<SimpleDarwinRecordSet
xmlns="http://rs.tdwg.org/dwc/xsd/simpledarwincore/"
@@ -313,32 +508,42 @@ shows a SimpleDarwinRecordSet containing one SimpleDarwinRecord fo
</SimpleDarwinRecord>
</SimpleDarwinRecordSet>
-
-The SimpleDarwinRecord acts as a Class in
-implementation, because all of the terms belong to it. The Simple Darwin Core schema has just one other level of
-structure, the SimpleDarwinRecordSet, which is a grouping of one or more SimpleDarwinRecords. The
-SimpleDarwinRecordSet acts as a Class to define a data set during implementation.
-
-
1.6 Doing More with Simple Darwin Core
-Sooner or later you may want to share more information than the Simple Darwin Core seems to allow. For example, you
-and your colleagues might decide that it would be useful to have a standard way to exchange additional information relevant
-to questions in Conservation. How would you do it?
-
-One way would be to try to "overload" existing terms by using them to hold information other than what was intended
-based on the definition of the terms. Please don't do this.
-If an existing term has close to the same meaning as one you want to use, but just doesn't quite fit because of the
-way the definition is worded, it would be better to request an amendment to the term definition so that it will be
-clear for your community how to use it. You can request such a change by submitting an issue
-in the Darwin Core Project [DWC-PROJECT].
-
-Another way to get more out of the Darwin Core without adding a term is to "payload" the
-dynamicProperties term as shown in the example below, to contain a list
-of key-value pairs. The keys in this case would act as new unofficial terms. This is perfectly legal, since it doesn't
-compromise the meaning of the term. Some of the weaknesses of payloading are that it is prone to errors, inconsistencies,
-and lack of stable or well-defined semantics. Still, this might be a reasonable way to at least allow you to share all of
-your data, even if there might be problems with people using it reliably.
-
+
The SimpleDarwinRecord acts as a Class in implementation,
+ because all of the terms are properties of it. The Simple Darwin Core
+ schema has just one other level of structure, the
+ SimpleDarwinRecordSet, which is a grouping of one or more
+ SimpleDarwinRecords. The SimpleDarwinRecordSet acts as a
+ Class to define a data set during implementation.
+
+
1.6 Doing More with Simple Darwin Core
Sooner or later you may want
+ to share more information than the Simple Darwin Core seems to allow.
+ For example, you and your colleagues might decide that it would be useful to
+ have a standard way to exchange additional information relevant to questions
+ in Conservation. How would you do it?
+
+
One way would be to try to "overload" existing terms by using them to hold
+ information other than what was intended based on the definition of the
+ terms. Please don't do this. If an existing term has close to the same
+ meaning as one you want to use, but just doesn't quite fit because of the way
+ the definition is worded, it would be better to request an amendment to the
+ term definition so that it will be clear for your community how to use it.
+ You can request such a change by submitting an issue in the Darwin Core
+ Project [DWC-PROJECT].
+
+
Another way to get more out of the Darwin Core without adding a term is to
+ "payload" the dynamicProperties
+ term with structured content, as shown in the example below, using Javascript
+ Open Notatation (JSON). This is perfectly legal, since it doesn't compromise
+ the meaning of the term. One of the weaknesses of payloading data in this way
+ is that it is subject to a lack of stable or well-defined semantics. Also, it
+ is highly recommended to flatten the content into a single string with no
+ non-printing characters (such as line feeds) to facilitate use in the widest
+ variety of data sharing contexts. Still, this might be a reasonable way to at
+ least allow you to share all of your data, even if there might be problems
+ with people using it reliably.
+
<?xml version="1.0" encoding="UTF-8"?>
<SimpleDarwinRecordSet
xmlns="http://rs.tdwg.org/dwc/xsd/simpledarwincore/"
@@ -366,39 +571,68 @@ your data, even if there might be problems with people using it reliably.
<dwc:nomenclaturalCode>ICZN</dwc:nomenclaturalCode>
<dwc:namePublishedIn>Pearson O. P., and M. I. Christie. 1985. Historia Natural, 5(37):388</dwc:namePublishedIn>
<dwc:taxonomicStatus>valid</dwc:taxonomicStatus>
- <dwc:dynamicProperties>iucnStatus=vulnerable; distribution=Neuquen, Argentina</dwc:dynamicProperties>
+ <dwc:dynamicProperties>{'iucnStatus':'vulnerable', 'distribution':'Neuquén, Argentina'}</dwc:dynamicProperties>
</SimpleDarwinRecord>
</SimpleDarwinRecordSet>
-
-If you were using just CSV text files to exchange information, then you might be tempted to just add the new fields
-to the files. This approach suffers most of the same problems as payloading - no one aside from those with whom you
-communicated would know what those new fields were or how to use them. Sharing in this way via XML would be an even
-bigger problem, because the Simple Darwin Core XML Schema [SIMPLEXMLSCHEMA]
-defines the terms that it supports and the new fields would not correspond with any terms understood by the schema.
-In other words, the XML with your fields in it would not be a valid Simple Darwin Core XML document.
-
-So, if you really need to extend the capabilities of the Darwin Core, the best first step is to follow the standards
-process to add the terms you need. The mechanisms for pursuing this are explained in the Darwin Core Namespace Policy
-[NAMESPACEPOLICY]. The process will help to assure that the new terms are well
-conceived, that they don't conflict with existing terms, and that they are properly defined in the broader context
-of biological diversity information.
-
-
-
-
- Copyright 2009-2013 - Biodiversity Information Standards - TDWG - Contact Us
-
If you were using just CSV text files to exchange information, then you
+ might be tempted to just add the new fields to the files. This approach
+ suffers most of the same problems as payloading - no one aside from those
+ with whom you communicated would know what those new fields were or how to
+ use them. Sharing in this way via XML would be an even bigger problem,
+ because the Simple Darwin Core XML Schema [SIMPLEXMLSCHEMA] defines the terms that
+ it supports and the new fields would not correspond with any terms understood
+ by the schema. In other words, the XML with your fields in it would not be a
+ valid Simple Darwin Core XML document.
-
-
-
+
So, if you really need to extend the capabilities of Darwin Core, the best
+ first step is to follow the standards process to add the terms you need. The
+ mechanisms for pursuing this are explained in the Darwin Core Namespace
+ Policy [NAMESPACEPOLICY]. The
+ process will help to assure that the new terms are well conceived, that they
+ don't conflict with existing terms, and that they are properly defined in the
+ broader context of biological diversity information.
-
\ No newline at end of file
+
1.7 Going Beyond Simple Darwin Core
+
+
For cases where rich data require rich (non-simple) structure, the
+ Simple Darwin Core alone is not suitable. When sharing information via
+ fielded text [FIELDEDTEXT], the
+ solution is to use the Simple Darwin Core as a core record with one or
+ more associated extensions for the additional information. See the Darwin
+ Core Text Guide [TEXTGUIDE]
+ for an explanation and examples.
+
+
When sharing information via XML [XML], a richer structure such as the Access
+ to Biological Collections Data schema [ABCD], or the Generic Darwin
+ Core [GENERICXMLSCHEMA], or
+ another schema built from the Darwin Core terms to suit the use of the data
+ in a particular context. See the Darwin Core XML Guide [XMLGUIDE] for examples and references to model
+ schemas.
The Darwin Core Type Vocabulary extends the DCMI Type Vocabulary and provides a list of approved values that
-may be used for the basisOfRecord term to identify the specific type of a resource. The terms documented here are
-also included in the more comprehensive document
-Darwin Core Terms: A complete history, see [HISTORY].
-
-
-
Contributors:
-
John Wieczorek (MVZ), Markus Döring (GBIF), Renato De Giovanni (CRIA), Tim Robertson (GBIF), Dave Vieglais (KUNHM)
-
-
-
Legal:
-
This document is governed by the standard legal, copyright, licensing provisions and disclaimers issued by the Taxonomic Databases Working Group.
-Audience: This document is targeted toward those who need a reference (lists and definitions) to the essential information
-about the recommended values of the basisOfRecord Darwin Core term.
-
-The Type Vocabulary is a recommended set of values to use for the basisOfRecord term
-to categorize Darwin Core resources. The Darwin Core Type Vocabulary extends and refines terms from the
-Dublin Core Type Vocabulary [DCMI-TYPE] to describe and
-categorize resources more specifically for biodiversity applications. The basisOfRecord should be populated with
-the value from the Darwin Core Type Vocabulary that best corresponds to the resource being shared.
-
-
-
-The table below contains the term information essential for most users. The complete documentation for each term
-can be found by following the link in the Details section of the term description. The link takes you to the appropriate
-entry in the Complete History [HISTORY] document. The definitions for the fields
-describing each term are:
-
-
-
-
-
Term Name:
-
The name by which the latest version of the term is commonly known.
-
-
-
Identifier:
-
The unique identifier for the latest version of the term.
-
-
-
Definition:
-
A description of the nature of the content of the term.
-
-
-
Comment:
-
Further commentary about the usage of the term, with examples and a reference to further information.
-
-
-
Type of Term:
-
The category (property, class, vocabulary encoding scheme) to which the term belongs.
-
-
-
Member Of:
-
The Class (DCMI or Darwin Core Type Vocabulary) of which this term is a member.
-
-
-
Version:
-
The identifier for the specific version of the term.
-
-
-
Refines:
-
The name of a term of which this term is a refined (more specialized) version.
-
-
-
Details:
-
A link to the complete information about the term, including access to its history.
A non-persistent, time-based occurrence. For Darwin Core, a resource describing an instance of the Event class.
Comment:
Metadata for an event provides descriptive information that is the basis for discovery of the purpose, location, duration, and responsible agents associated with an event. For discussion see http://code.google.com/p/darwincore/wiki/DwCTypeVocabulary
A resource describing the physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.
Informative supplement to the Darwin Core Standard.
-
-
-
-
-
-
-
-
-
-
1. Introduction
-
-The Darwin Core is meant to serve a global community. Access to the documents describing the standard in multiple languages
-will facilitate open access and global adoption. This page is meant to be an index to all translations of Darwin Core documents.
-Anyone interested in providing translations to be hosted with the corpus of the standard should contact the Darwin Core Task Group
-[DWC-TASK].
-
-
-
-
-
- Copyright 2009 - Biodiversity Information Standards - TDWG - Contact Us
-
-
- 
- 
-
- Copyright 2009 - Biodiversity Information Standards - TDWG - Contact Us
