Darwin Core Recommended Terms
comment: 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 https://github.com/tdwg/dwc/issues
publisher: Biodiversity Information Standards (TDWG)
modified: 2014-12-05

Accepted Name Usage
comment: The full name, with authorship and date information if known, of the currently valid (zoological) or accepted (botanical) taxon.
description: Example: "Tamias minimus" valid name for "Eutamias minimus"
issued: 2008-11-19
modified: 2009-09-21
type: Property
has version: acceptedNameUsage-2009-09-21
replaces: acceptedScientificName-2009-07-06
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

Accepted Name Usage ID
comment: An identifier for the name usage (documented meaning of the name according to a source) of the currently valid (zoological) or accepted (botanical) taxon.
description: Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"
issued: 2009-01-21
modified: 2009-09-21
type: Property
has version: acceptedNameUsageID-2009-09-21
sub property of: identifier
replaces: acceptedTaxonID-2009-08-24
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

According To
comment: Abstract term to attribute information to a source.
issued: 2009-01-21
modified: 2009-01-21
type: Property
has version: accordingTo-2009-01-21
status: recommended
abcd equivalence: not in ABCD

Associated Media
comment: A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of media associated with the Occurrence.
description: 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".
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: associatedMedia-2014-10-23
replaces: associatedMedia-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: DataSets/DataSet/Units/Unit/MultimediaObjects
organized in class: Occurrence

Associated Occurrences
comment: A list (concatenated and separated) of identifiers of other Occurrence records and their associations to this Occurrence.
description: The recommended best practice is to separate the values with a vertical bar (' | ').
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: associatedOccurrences-2014-10-23
replaces: associatedOccurrences-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
organized in class: Organism

Associated Organisms
comment: A list (concatenated and separated) of identifiers of other Organisms and their associations to this Organism.
description: 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"
issued: 2014-10-23
modified: 2014-10-23
type: Property
has version: associatedOrganisms-2014-10-23
status: recommended
decision: Decision-2014-10-26 14
abcd equivalence: not in ABCD
organized in class: Organism

Associated References
comment: A list (concatenated and separated) of identifiers (publication, bibliographic reference, global unique identifier, URI) of literature associated with the Occurrence.
description: 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.".
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: associatedReferences-2014-10-23
replaces: associatedReferences-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: DataSets/DataSet/Units/Unit/UnitReferences
organized in class: Occurrence

Associated Sequences
comment: A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of genetic sequence information associated with the Occurrence.
description: 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".
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: associatedSequences-2014-10-23
replaces: associatedSequences-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: DataSets/DataSet/Units/Unit/Sequences/Sequence/ID-in-Database + constant
organized in class: Occurrence

Associated Taxa
comment: A list (concatenated and separated) of identifiers or names of taxa and their associations with the Occurrence.
description: 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".
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: associatedTaxa-2014-10-23
replaces: associatedTaxa-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Synecology/AssociatedTaxa
organized in class: Occurrence

Basis of Record
comment: The specific nature of the data record.
description: Recommended best practice is to use a controlled vocabulary such as the list of Darwin Core classes. Examples: "PreservedSpecimen", "FossilSpecimen", "LivingSpecimen", "HumanObservation", "MachineObservation"
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: basisOfRecord-2014-10-23
replaces: basisOfRecord-2009-12-07
status: recommended
decision: Decision-2014-10-26 15
abcd equivalence: DataSets/DataSet/Units/Unit/RecordBasis
organized in class: all

Bed
comment: The full name of the lithostratigraphic bed from which the cataloged item was collected.
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: http://rs.tdwg.org/dwc/terms/history/#bed-2009-04-24
replaces: http://rs.tdwg.org/dwc/terms/Bed-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Behavior
comment: 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.
description: Examples: "roosting", "foraging", "running"
issued: 2009-03-06
modified: 2009-04-24
type: Property
has version: behavior-2009-04-24
status: recommended
abcd equivalence: not in ABCD
organized in class: Occurrence

Catalog Number
comment: An identifier (preferably unique) for the record within the data set or collection.
description: Examples: "2008.1334", "145732a", "145732"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: catalogNumber-2009-04-24
replaces: CatalogNumber-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/UnitID
organized in class: Occurrence

Class
comment: The full scientific name of the class in which the taxon is classified.
description: Examples: "Mammalia", "Hepaticopsida"
issued: 2008-11-19
modified: 2009-08-24
type: Property
has version: class-2009-08-24
replaces: class-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = classis
organized in class: Taxon

Collection Code
comment: The name, acronym, coden, or initialism identifying the collection or data set from which the record was derived.
description: Examples: "Mammals", "Hildebrandt", "eBird"
issued: 2008-11-19
modified: 2013-10-04
type: Property
has version: collectionCode-2009-09-11
replaces: collectionCode-2009-08-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/SourceID
organized in class: all

Collection ID
comment: An identifier for the collection or dataset from which the record was derived.
description: 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".
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: collectionID-2009-09-11
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/SourceID
organized in class: all

Continent
comment: 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.
description: Examples: "Africa", "Antarctica", "Asia", "Europe", "North America", "Oceania", "South America"
issued: 2008-11-19
modified: 2013-10-04
type: Property
has version: continent-2009-04-24
replaces: Continent-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Continent
organized in class: Location

Coordinate Precision
comment: A decimal representation of the precision of the coordinates given in the decimalLatitude and decimalLongitude.
description: Examples: "0.00001" (normal GPS limit for decimal degrees), "0.000278" (nearest second), "0.01667" (nearest minute), "1.0" (nearest degree)
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: coordinatePrecision-2009-04-24
replaces: CoordinatePrecision-2003-06-13
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/ISOAccuracy or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/AccuracyStatement
organized in class: Location

Coordinate Uncertainty In Meters
comment: 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.
description: 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).
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: coordinateUncertaintyInMeters-2009-04-24
replaces: CoordinateUncertaintyInMeters-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinateErrorDistanceInMeters
organized in class: Location

Country
comment: 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.
description: Examples: "Denmark", "Colombia", "España"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: country-2009-04-24
replaces: Country-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Country/Name
organized in class: Location

Country Code
comment: The standard code for the country in which the Location occurs. Recommended best practice is to use ISO 3166-1-alpha-2 country codes.
description: Examples: "AR" for Argentina, "SV" for El Salvador
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: countryCode-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Country/ISO3166Code
organized in class: Location

County
comment: The full, unabbreviated name of the next smaller administrative region than stateProvince (county, shire, department, etc.) in which the Location occurs.
description: Examples: "Missoula", "Los Lagos", "Mataró"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: county-2009-04-24
replaces: County-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= County
organized in class: Location

Data Generalizations
comment: 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.
description: Example: "Coordinates generalized from original GPS coordinates to the nearest half degree grid cell"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: dataGeneralizations-2009-04-24
replaces: Generalizations-2008-11-19
status: recommended
abcd equivalence: not in ABCD
organized in class: all

Dataset ID
comment: An identifier for the set of data. May be a global unique identifier or an identifier specific to a collection or institution.
issued: 2008-11-19
modified: 2009-09-11
type: Property
has version: datasetID-2009-09-11
sub property of: identifier
replaces: datasetID-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/DataSetGUID
organized in class: all

Dataset Name
comment: The name identifying the data set from which the record was derived.
description: Examples: "Grinnell Resurvey Mammals", "Lacey Ctenomys Recaptures"
issued: 2009-09-11
modified: 2009-09-11
type: Property
has version: datasetName-2009-09-11
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/SourceID
organized in class: all

Date Identified
comment: 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).
description: 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.
issued: 2008-11-19
modified: 2009-08-24
type: Property
has version: dateIdentified-2009-08-24
sub property of: date
replaces: dateIdentified-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/Date/DateText
organized in class: Identification

Day
comment: The integer day of the month on which the Event occurred.
description: Examples: "9", "28"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: day-2009-04-24
replaces: DayCollected-2003-06-17
status: recommended
abcd equivalence: accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
organized in class: Event

Decimal Latitude
comment: 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.
description: Example: "-41.0983423"
issued: 2008-11-19
modified: 2009-07-06
type: Property
has version: decimalLatitude-2009-04-24
replaces: DecimalLatitude-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal
organized in class: Location

Decimal Longitude
comment: 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.
description: Example: "-121.1761111"
issued: 2008-11-19
modified: 2009-07-06
type: Property
has version: decimalLongitude-2009-04-24
replaces: DecimalLongitude-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal
organized in class: Location

Disposition
comment: 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.
description: Examples: "in collection", "missing", "voucher elsewhere", "duplicates elsewhere"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: disposition-2009-04-24
replaces: Disposition-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/SpecimenUnit/Disposition
organized in class: Occurrence

Dynamic Properties
comment: A list of additional measurements, facts, characteristics, or assertions about the record. Meant to provide a mechanism for structured content.
description: 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"}".
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: dynamicProperties-2014-10-23
replaces: dynamicProperties-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: not in ABCD
organized in class: all

Earliest Age Or Lowest Stage
comment: 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.
description: Examples: "Atlantic", "Boreal", "Skullrockian"
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: earliestAgeOrLowestStage-2009-04-24
replaces: EarliestAgeOrLowestStage-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Earliest Eon Or Lowest Eonothem
comment: 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.
description: Examples: "Phanerozoic", "Proterozoic"
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: earliestEonOrLowestEonothem-2009-04-24
replaces: EarliestEonOrLowestEonothem-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Earliest Epoch Or Lowest Series
comment: 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.
description: Examples: "Holocene", "Pleistocene", "Ibexian Series"
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: earliestEpochOrLowestSeries-2009-04-24
replaces: EarliestEpochOrLowestSeries-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Earliest Era Or Lowest Erathem
comment: 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.
description: Examples: "Cenozoic", "Mesozoic"
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: earliestEraOrLowestErathem-2009-04-24
replaces: EarliestEraOrLowestErathem-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Earliest Period Or Lowest System
comment: 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.
description: Examples: "Neogene", "Tertiary", "Quaternary"
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: earliestPeriodOrLowestSystem-2009-04-24
replaces: EarliestPeriodOrLowestSystem-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

End Day Of Year
comment: 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).
description: Examples: "1" (=1 Jan), "366" (=31 Dec), "365" (=30 Dec in a leap year, 31 Dec in a non-leap year)
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: endDayOfYear-2009-04-24
replaces: DayOfYear-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberEnd
organized in class: Event

Establishment Means
comment: 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.
description: Examples: "native", "introduced", "naturalised", "invasive", "managed"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: establishmentMeans-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/EstablishmentMeans
organized in class: Occurrence

Event
comment: An action that occurs at some location during some time.
description: Examples: A specimen collection process. A machine observation.
issued: 2008-11-19
modified: 2014-10-23
type: Class
has version: Event-2014-10-23
replaces: Event-2009-04-29
status: recommended
decision: Decision-2014-10-26 15
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering

Event Date
comment: 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).
description: 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.
issued: 2009-04-24
modified: 2009-07-01
type: Property
has version: eventDate-2009-04-24
sub property of: date
replaces: EarliestDateCollected-2007-04-17
replaces: LatestDateCollected-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
organized in class: Event

Event ID
comment: 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.
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: eventID-2009-04-24
sub property of: identifier
replaces: SamplingEventID-2008-11-19
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Code
organized in class: Event

Event Remarks
comment: Comments or notes about the Event.
description: Example: "after the recent rains the river is nearly at flood stage"
issued: 2009-01-18
modified: 2009-04-24
type: Property
has version: eventRemarks-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Notes
organized in class: Event

Event Time
comment: The time or interval during which an Event occurred. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
description: 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.
issued: 2009-04-24
modified: 2009-04-24
type: Property
has version: eventTime-2009-04-24
replaces: StartTimeOfDay-2005-07-10
replaces: EndTimeOfDay-2005-07-10
status: recommended
abcd equivalence: accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin and DataSets/DataSet/Units/Unit/Gathering/ISODateTimeEnd
organized in class: Event

Family
comment: The full scientific name of the family in which the taxon is classified.
description: Examples: "Felidae", "Monocleaceae"
issued: 2008-11-19
modified: 2009-08-24
type: Property
has version: family-2009-08-24
replaces: family-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = familia
organized in class: Taxon

Field Notes
comment: 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.
description: Example: "notes available in Grinnell-Miller Library"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: fieldNotes-2009-04-24
replaces: FieldNotes-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/FieldNotes
organized in class: Event

Field Number
comment: An identifier given to the event in the field. Often serves as a link between field notes and the Event.
description: Example: "RV Sol 87-03-08"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: fieldNumber-2009-04-24
replaces: FieldNumber-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Code
organized in class: Event

Footprint Spatial Fit
comment: 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.
description: Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006.
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: footprintSpatialFit-2009-04-24
replaces: FootprintSpatialFit-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/FootprintSpatialFit (ABCD v2.06b)
organized in class: Location

Footprint SRS
comment: 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.
description: 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.
issued: 2009-07-06
modified: 2009-07-06
type: Property
has version: footprintSRS-2009-07-06
status: recommended
abcd equivalence: not in ABCD
organized in class: Location

Footprint WKT
comment: 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.
description: 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))
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: footprintWKT-2009-04-24
replaces: FootprintWKT-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/FootprintWKT (ABCD v2.06b)
organized in class: Location

Formation
comment: The full name of the lithostratigraphic formation from which the cataloged item was collected.
description: Examples: "Notch Peak Fromation", "House Limestone", "Fillmore Formation"
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: formation-2009-04-24
replaces: Formation-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Fossil Specimen
comment: A preserved specimen that is a fossil.
issued: 2014-10-23
modified: 2014-10-23
type: Class
has version: FossilSpecimen-2014-10-23
replaces: FossilSpecimen-2011-10-16
status: recommended
decision: Decision-2014-10-26 15
abcd equivalence: RecordBasisEnum/FossileSpecimen

Genus
comment: The full scientific name of the genus in which the taxon is classified.
description: Examples: "Puma", "Monoclea"
issued: 2008-11-19
modified: 2009-08-24
type: Property
has version: genus-2009-08-24
replaces: genus-2009-04-24
status: recommended
abcd equivalence: {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}
organized in class: Taxon

Geodetic Datum
comment: 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".
description: Examples: "EPSG:4326", "WGS84", "NAD27", "Campo Inchauspe", "European 1950", "Clarke 1866"
issued: 2008-11-19
modified: 2009-07-06
type: Property
has version: geodeticDatum-2009-04-24
replaces: GeodeticDatum-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/SpatialDatum
organized in class: Location

Geological Context
comment: Geological information, such as stratigraphy, that qualifies a region or place.
description: Example: A lithostratigraphic layer.
issued: 2009-07-06
modified: 2014-10-23
type: Class
has version: GeologicalContext-2014-10-23
replaces: GeologicalContext-2009-07-06
status: recommended
decision: Decision-2014-10-26 15
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Stratigraphy

Geological Context ID
comment: 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.
issued: 2009-07-06
modified: 2009-07-06
type: Property
has version: geologicalContextID-2009-07-06
sub property of: identifier
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Georeferenced By
comment: A list (concatenated and separated) of names of people, groups, or organizations who determined the georeference (spatial representation) for the Location.
description: The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Brad Millen (ROM)", "Kristina Yamamoto (MVZ) | Janet Fang (MVZ)".
issued: 2009-01-21
modified: 2014-10-23
type: Property
has version: georeferencedBy-2014-10-23
sub property of: According To
replaces: georeferencedBy-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: not in ABCD
organized in class: Location

Georeferenced Date
comment: The date on which the Location was georeferenced. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
description: 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.
issued: 2011-10-16
modified: 2011-10-16
type: Property
has version: georeferencedDate-2011-10-16
sub property of: date
status: recommended
decision: Decision-2011-10-16 9
abcd equivalence: not in ABCD
organized in class: Location

Georeference Protocol
comment: A description or reference to the methods used to determine the spatial footprint, coordinates, and uncertainties.
description: 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"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: georeferenceProtocol-2009-04-24
replaces: GeoreferenceProtocol-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinateMethod
organized in class: Location

Georeference Remarks
comment: 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.
description: Example: "assumed distance by road (Hwy. 101)"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: georeferenceRemarks-2009-04-24
replaces: GeoreferenceRemarks-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceRemarks
organized in class: Location

Georeference Sources
comment: 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.
description: 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".
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: georeferenceSources-2014-10-23
replaces: georeferenceSources-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceSources
organized in class: Location

Georeference Verification Status
comment: 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.
description: Examples: "requires verification", "verified by collector", "verified by curator".
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: georeferenceVerificationStatus-2009-04-24
replaces: GeoreferenceVerificationStatus-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/GeoreferenceVerificationStatus
organized in class: Location

Group
comment: The full name of the lithostratigraphic group from which the cataloged item was collected.
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: group-2009-04-24
replaces: Group-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Habitat
comment: A category or description of the habitat in which the Event occurred.
description: Examples: "oak savanna", "pre-cordilleran steppe"
issued: 2008-11-19
modified: 2009-05-17
type: Property
has version: habitat-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Biotope/Text
organized in class: Event

Higher Classification
comment: A list (concatenated and separated) of taxa names terminating at the rank immediately superior to the taxon referenced in the taxon record.
description: 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".
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: higherClassification-2014-10-23
replaces: higherClassification-2009-08-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: not in ABCD
organized in class: Taxon

Higher Geography
comment: A list (concatenated and separated) of geographic names less specific than the information captured in the locality term.
description: 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.
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: higherGeography-2014-10-23
replaces: higherGeography-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: {DataSets/DataSet/Units/Unit/Gathering/LocalityText or DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName}
organized in class: Location

Higher Geography ID
comment: 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.
description: Example: "TGN: 1002002" for Prov. Tierra del Fuego, Argentina
issued: 2009-01-21
modified: 2009-04-24
type: Property
has version: higherGeographyID-2009-04-24
sub property of: identifier
status: recommended
abcd equivalence: not in ABCD
organized in class: Location

Highest Biostratigraphic Zone
comment: The full name of the highest possible geological biostratigraphic zone of the stratigraphic horizon from which the cataloged item was collected.
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: highestBiostratigraphicZone-2009-04-24
replaces: HighestBiostratigraphicZone-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Human Observation
comment: An output of a human observation process.
issued: 2014-10-23
modified: 2014-10-23
type: Class
has version: HumanObservation-2014-10-23
replaces: HumanObservation-2011-10-16
status: recommended
decision: Decision-2014-10-26 15
abcd equivalence: RecordBasisEnum/HumanObservation

Identification
comment: A taxonomic determination (e.g., the assignment to a taxon).
description: Example: A subspecies determination of an organism.
issued: 2008-11-19
modified: 2014-10-23
type: Class
has version: Identification-2014-10-23
replaces: Identification-2008-11-19
status: recommended
decision: Decision-2014-10-26 15
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification

Identification ID
comment: 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.
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: identificationID-2009-04-24
sub property of: identifier
status: recommended
abcd equivalence: not in ABCD
organized in class: Identification

Identification Qualifier
comment: A brief phrase or a standard term ("cf.", "aff.") to express the determiner's doubts about the Identification.
description: 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.
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: identificationQualifier-2009-04-24
replaces: IdentificationQualifier-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/IdentificationQualifier
organized in class: Identification

Identification References
comment: A list (concatenated and separated) of references (publication, global unique identifier, URI) used in the Identification.
description: 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.".
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: identificationReferences-2014-10-23
replaces: identificationReferences-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/References
organized in class: Identification

Identification Remarks
comment: Comments or notes about the Identification.
description: Example: "Distinguished between Anthus correndera and Anthus hellmayri based on the comparative lengths of the uñas."
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: identificationRemarks-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/Notes
organized in class: Identification

Identification Verification Status
comment: 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.
description: Examples: "0", "4"
issued: 2011-10-16
modified: 2011-10-16
type: Property
has version: identificationVerificationStatus-2011-10-16
status: recommended
decision: Decision-2011-10-16 10
abcd equivalence: not in ABCD
organized in class: Identification

Identified By
comment: A list (concatenated and separated) of names of people, groups, or organizations who assigned the Taxon to the subject.
description: The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "James L. Patton", "Theodore Pappenfuss | Robert Macey".
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: identifiedBy-2014-10-23
sub property of: According To
replaces: identifiedBy-2009-08-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/Identifiers/IdentifiersText
organized in class: Identification

Individual Count
comment: The number of individuals represented present at the time of the Occurrence.
description: Examples: "1", "25"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: individualCount-2009-04-24
replaces: IndividualCount-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/SiteMeasurementOrFact/MeasurementOrFactAtomised/LowerValue
organized in class: Occurrence

Information Withheld
comment: Additional information that exists, but that has not been shared in the given record.
description: Examples: "location information not given for endangered species", "collector identities withheld", "ask about tissue samples"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: informationWithheld-2009-04-24
replaces: InformationWithheld-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/InformationWithheld
organized in class: all

Infraspecific Epithet
comment: The name of the lowest or terminal infraspecific epithet of the scientificName, excluding any rank designation.
description: Examples: "concolor", "oxyadenia", "sayi"
issued: 2008-11-19
modified: 2009-08-24
type: Property
has version: infraspecificEpithet-2009-08-24
replaces: infraspecificEpithet-2009-04-24
status: recommended
abcd equivalence: {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}
organized in class: Taxon

Institution Code
comment: The name (or acronym) in use by the institution having custody of the object(s) or information referred to in the record.
description: Examples: "MVZ", "FMNH", "AKN-CLO", "University of California Museum of Paleontology (UCMP)"
issued: 2008-11-19
modified: 2013-10-04
type: Property
has version: institutionCode-2009-09-11
replaces: institutionCode-2009-08-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/SourceInstitutionID
organized in class: all

Institution ID
comment: An identifier for the institution having custody of the object(s) or information referred to in the record.
description: 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".
issued: 2009-09-11
modified: 2014-10-23
type: Property
has version: institutionID-2009-09-11
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/SourceInstitutionID
organized in class: all

Island
comment: 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.
description: Examples: "Isla Victoria", "Vancouver", "Viti Levu", "Zanzibar"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: island-2009-04-24
replaces: Island-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island
organized in class: Location

Island Group
comment: 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.
description: Examples: "Alexander Archipelago", "Seychelles"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: islandGroup-2009-04-24
replaces: IslandGroup-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Island group
organized in class: Location

Kingdom
comment: The full scientific name of the kingdom in which the taxon is classified.
description: Examples: "Animalia", "Plantae"
issued: 2008-11-19
modified: 2009-08-24
type: Property
has version: kingdom-2009-08-24
replaces: kingdom-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = regnum
organized in class: Taxon

Latest AgeOr Highest Stage
comment: 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.
description: Examples: "Atlantic", "Boreal", "Skullrockian"
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: latestAgeOrHighestStage-2009-04-24
replaces: LatestAgeOrHighestStage-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Latest Eon Or Highest Eonothem
comment: 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.
description: Examples: "Phanerozoic", "Proterozoic"
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: latestEonOrHighestEonothem-2009-04-24
replaces: LatestEonOrLowestEonothem-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Latest Epoch Or Highest Series
comment: 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.
description: Examples: "Holocene", "Pleistocene", "Ibexian Series"
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: latestEpochOrHighestSeries-2009-04-24
replaces: LatestEpochOrHighestSeries-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Latest Era Or Highest Erathem
comment: 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.
description: Examples: "Cenozoic", "Mesozoic"
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: latestEraOrHighestErathem-2009-04-24
replaces: LatestEraOrHighestErathem-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Latest Period Or Highest System
comment: 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.
description: Examples: "Neogene", "Tertiary", "Quaternary"
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: latestPeriodOrHighestSystem-2009-04-24
replaces: LatestPeriodOrHighestSystem-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Life Stage
comment: 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.
description: Examples: "egg", "eft", "juvenile", "adult", "2 adults 4 juveniles"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: lifeStage-2009-04-24
replaces: LifeStage-2007-04-17
status: recommended
abcd equivalence: 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
organized in class: Occurrence

Lithostratigraphic Terms
comment: The combination of all litho-stratigraphic names for the rock from which the cataloged item was collected.
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: lithostratigraphicTerms-2009-04-24
replaces: LithostratigraphicTerms-2005-07-03
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Stratigraphy/LithostratigraphicTerms
organized in class: Geological Context

Living Specimen
comment: A specimen that is alive.
issued: 2014-10-23
modified: 2014-10-23
type: Class
has version: LivingSpecimen-2014-10-23
replaces: LivingSpecimen-2011-10-16
status: recommended
decision: Decision-2014-10-26 15
abcd equivalence: RecordBasisEnum/LivingSpecimen

Locality
comment: 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.
description: Example: "Bariloche, 25 km NNE via Ruta Nacional 40 (=Ruta 237)"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: locality-2009-04-24
replaces: Locality-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
organized in class: Location

Location According To
comment: Information about the source of this Location information. Could be a publication (gazetteer), institution, or team of individuals.
description: Examples: "Getty Thesaurus of Geographic Names", "GADM"
issued: 2009-08-24
modified: 2009-08-24
type: Property
has version: locationAccordingTo-2009-08-24
sub property of: According To
status: recommended
abcd equivalence: not in ABCD
organized in class: Location

Location ID
comment: 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.
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: locationID-2009-04-24
sub property of: identifier
replaces: SamplingLocationID-2008-11-19
status: recommended
abcd equivalence: not in ABCD
organized in class: Location

Location Remarks
comment: Comments or notes about the Location.
description: Example: "under water since 2005"
issued: 2009-01-18
modified: 2009-04-24
type: Property
has version: locationRemarks-2009-04-24
replaces: SamplingLocationRemarks-2009-01-18
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/AreaDetail
organized in class: Location

Lowest Biostratigraphic Zone
comment: The full name of the lowest possible geological biostratigraphic zone of the stratigraphic horizon from which the cataloged item was collected.
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: lowestBiostratigraphicZone-2009-04-24
replaces: LowestBiostratigraphicZone-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Machine Observation
comment: An output of a machine observation process.
issued: 2014-10-23
modified: 2014-10-23
type: Class
has version: MachineObservation-2014-10-23
replaces: MachineObservation-2011-10-16
status: recommended
decision: Decision-2014-10-26 15
abcd equivalence: RecordBasisEnum/MachineObservation

Material Sample
comment: A physical results of a sampling (or subsampling) event. In biological collections, the material sample is typically collected, and either preserved or destructively processed.
description: Examples: A whole organism preserved in a collection. A part of an organism isolated for some purpose. A soil sample. A marine microbial sample.
issued: 2013-03-28
modified: 2014-10-23
type: Class
has version: MaterialSample-2014-10-23
replaces: MaterialSample-2013-03-28
status: recommended
decision: Decision-2014-10-26 15
abcd equivalence: DataSets/DataSet/Units/Unit

Material Sample ID
comment: 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.
issued: 2013-03-28
modified: 2013-09-26
type: Property
has version: materialSampleID-2013-05-25
sub property of: identifier
replaces: source mat id-2011-01-26
status: recommended
decision: Decision-2013-10-09 13
abcd equivalence: not in ABCD
organized in class: Material Sample

Maximum Depth In Meters
comment: The greater depth of a range of depth below the local surface, in meters.
description: Example: "200"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: maximumDepthInMeters-2009-04-24
replaces: MaximumDepthInMeters-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/UpperValue
organized in class: Location

Maximum Distance Above Surface In Meters
comment: 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.
description: 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"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: maximumDistanceAboveSurfaceInMeters-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/UpperValue
organized in class: Location

Maximum Elevation In Meters
comment: The upper limit of the range of elevation (altitude, usually above sea level), in meters.
description: Example: "200"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: maximumElevationInMeters-2009-04-24
replaces: MaximumElevationInMeters-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue
organized in class: Location

Measurement Accuracy
comment: The description of the potential error associated with the measurementValue.
description: Examples: "0.01", "normal distribution with variation of 2 m"
issued: 2009-01-18
modified: 2009-04-24
type: Property
has version: measurementAccuracy-2009-04-24
replaces: occurrenceMeasurementAccuracy-2009-04-24
replaces: eventMeasurementAccuracy-2009-04-24
status: recommended
abcd equivalence: 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
organized in class: Measurement or Fact

Measurement Determined By
comment: A list (concatenated and separated) of names of people, groups, or organizations who determined the value of the MeasurementOrFact.
description: The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "Rob Guralnick", "Julie Woodruff | Eileen Lacey".
issued: 2009-01-23
modified: 2014-10-23
type: Property
has version: measurementDeterminedBy-2014-10-23
sub property of: According To
replaces: measurementDeterminedBy-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: 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
organized in class: Measurement or Fact

Measurement Determined Date
comment: The date on which the MeasurementOrFact was made. Recommended best practice is to use an encoding scheme, such as ISO 8601:2004(E).
description: 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.
issued: 2009-01-23
modified: 2009-04-24
type: Property
has version: measurementDeterminedDate-2009-04-24
sub property of: date
replaces: occurrenceMeasurementDeterminedDate-2009-04-24
replaces: eventMeasurementDeterminedDate-2009-04-24
status: recommended
abcd equivalence: 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
organized in class: Measurement or Fact

Measurement ID
comment: 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.
issued: 2009-03-06
modified: 2009-04-24
type: Property
has version: measurementID-2009-04-24
sub property of: identifier
replaces: occurrenceMeasurementID-2009-04-24
replaces: eventMeasurementID-2009-04-24
status: recommended
abcd equivalence: not in ABCD
organized in class: Measurement or Fact

Measurement Method
comment: A description of or reference to (publication, URI) the method or protocol used to determine the measurement, fact, characteristic, or assertion.
description: Examples: "minimum convex polygon around burrow entrances" for a home range area, "barometric altimeter" for an elevation
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: measurementMethod-2009-04-24
status: recommended
abcd equivalence: /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
organized in class: Measurement or Fact

Measurement or Fact
comment: A measurement of or fact about an rdfs:Resource (http://www.w3.org/2000/01/rdf-schema#Resource).
description: 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.
issued: 2009-04-24
modified: 2014-10-23
type: Class
has version: MeasurementOrFact-2014-10-23
replaces: MeasurementOrFact-2009-04-24
status: recommended
decision: Decision-2014-10-26 15
abcd equivalence: Datasets/Dataset/Units/Unit/MeasurementsOrFacts or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts

Measurement Remarks
comment: Comments or notes accompanying the MeasurementOrFact.
description: Example: "tip of tail missing"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: measurementRemarks-2009-04-24
replaces: occurrenceMeasurementRemarks-2009-04-24
replaces: eventMeasurementRemarks-2009-04-24
status: recommended
abcd equivalence: not in ABCD
organized in class: Measurement or Fact

Measurement Type
comment: The nature of the measurement, fact, characteristic, or assertion. Recommended best practice is to use a controlled vocabulary.
description: Examples: "tail length", "temperature", "trap line length", "survey area", "trap type"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: measurementType-2009-04-24
replaces: occurrenceMeasurementType-2009-04-24
replaces: eventMeasurementType-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter
organized in class: Measurement or Fact

Measurement Unit
comment: The units associated with the measurementValue. Recommended best practice is to use the International System of Units (SI).
description: Examples: "mm", "C", "km", "ha"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: measurementUnit-2009-04-24
replaces: occurrenceMeasurementUnit-2009-04-24
replaces: eventMeasurementUnit-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement or DataSets/DataSet/Units/Unit/Gathering/SiteMeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement
organized in class: Measurement or Fact

Measurement Value
comment: The value of the measurement, fact, characteristic, or assertion.
description: Examples: "45", "20", "1", "14.5", "UV-light"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: measurementValue-2009-04-24
replaces: occurrenceMeasurementValue-2009-04-24
replaces: eventMeasurementValue-2009-04-24
status: recommended
abcd equivalence: 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
organized in class: Measurement or Fact

Member
comment: The full name of the lithostratigraphic member from which the cataloged item was collected.
description: Examples: "Lava Dam Member", "Hellnmaria Member"
issued: 2009-04-24
modified: 2009-07-06
type: Property
has version: member-2009-04-24
replaces: Member-2005-07-03
status: recommended
abcd equivalence: not in ABCD
organized in class: Geological Context

Minimum Depth In Meters
comment: The lesser depth of a range of depth below the local surface, in meters.
description: Example: "100"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: minimumDepthInMeters-2009-04-24
replaces: MinimumDepthInMeters-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactAtomised/LowerValue
organized in class: Location

Minimum Distance Above Surface In Meters
comment: 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.
description: 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"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: minimumDistanceAboveSurfaceInMeters-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactAtomised/LowerValue
organized in class: Location

Minimum Elevation In Meters
comment: The lower limit of the range of elevation (altitude, usually above sea level), in meters.
description: Example: "100"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: minimumElevationInMeters-2009-04-24
replaces: MinimumElevationInMeters-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue
organized in class: Location

Month
comment: The ordinal month in which the Event occurred.
description: Examples: "1" (=January), "10" (=October)
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: month-2009-04-24
replaces: MonthCollected-2003-06-17
status: recommended
abcd equivalence: accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
organized in class: Event

Municipality
comment: 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.
description: Examples: "Holzminden"
issued: 2008-11-19
modified: 2009-08-24
type: Property
has version: municipality-2009-08-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
organized in class: Location

Name According To
comment: 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.
description: 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"
issued: 2008-11-19
modified: 2009-09-21
type: Property
has version: nameAccordingTo-2009-09-21
sub property of: According To
replaces: taxonAccordingTo-2009-04-24
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

Name According To ID
comment: An identifier for the source in which the specific taxon concept circumscription is defined or implied. See nameAccordingTo.
description: Example: "doi:10.1016/S0269-915X(97)80026-2"
issued: 2009-08-24
modified: 2009-09-21
type: Property
has version: nameAccordingToID-2009-09-21
sub property of: identifier
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

Name Published In
comment: A reference for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.
description: 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"
issued: 2008-11-19
modified: 2009-09-21
type: Property
has version: namePublishedIn-2009-09-21
sub property of: bibliographicCitation
replaces: namePublishedIn-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference/TitleCitation
organized in class: Taxon

Name Published In ID
comment: An identifier for the publication in which the scientificName was originally established under the rules of the associated nomenclaturalCode.
description: Example: "http://hdl.handle.net/10199/7"
issued: 2009-05-18
modified: 2009-09-21
type: Property
has version: namePublishedInID-2009-09-21
sub property of: identifier
replaces: namePublicationID-2009-05-18
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

Name Published In Year
comment: The four-digit year in which the scientificName was published.
description: Examples: "1915", "2008"
issued: 2011-10-16
modified: 2011-10-16
type: Property
has version: namePublishedInYear-2011-10-16
status: recommended
decision: Decision-2011-10-16 8
abcd equivalence: not in ABCD
organized in class: Taxon

Nomenclatural Code
comment: 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.
description: Examples: "ICBN", "ICZN", "BC", "ICNCP", "BioCode", "ICZN; ICBN"
issued: 2008-11-19
modified: 2009-09-21
type: Property
has version: nomenclaturalCode-2009-09-21
replaces: NomenclaturalCode-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/Code
organized in class: Taxon

Nomenclatural Status
comment: 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.
description: Examples: "nom. ambig.", "nom. illeg.", "nom. subnud."
issued: 2009-01-18
modified: 2009-04-24
type: Property
has version: nomenclaturalStatus-2009-04-24
status: recommended
abcd equivalence: (DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/NomenclaturalReference/TitleCitation) pro parte
organized in class: Taxon

Occurrence
comment: An existence of an Organism (sensu http://rs.tdwg.org/dwc/terms/Organism) at a particular place at a particular time.
description: 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.
issued: 2008-11-19
modified: 2014-10-23
type: Class
has version: Occurrence-2014-10-23
replaces: Occurrence-2009-04-29
status: recommended
decision: Decision-2014-10-26 15
abcd equivalence: DataSets/DataSet/Units/Unit

Occurrence ID
comment: 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.
description: 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"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: occurrenceID-2009-04-24
sub property of: identifier
replaces: GlobalUniqueIdentifier-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/UnitGUID
organized in class: Occurrence

Occurrence Remarks
comment: Comments or notes about the Occurrence.
description: Example: "found dead on road"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: occurrenceRemarks-2009-04-24
replaces: SampleRemarks-2009-01-18
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Notes
organized in class: Occurrence

Occurrence Status
comment: A statement about the presence or absence of a Taxon at a Location. Recommended best practice is to use a controlled vocabulary.
description: Examples: "present", "absent"
issued: 2009-09-17
modified: 2009-09-17
type: Property
has version: occurrenceStatus-2009-09-17
status: recommended
abcd equivalence: not in ABCD
organized in class: Occurrence

Order
comment: The full scientific name of the order in which the taxon is classified.
description: Examples: "Carnivora", "Monocleales"
issued: 2008-11-19
modified: 2009-08-24
type: Property
has version: order-2009-08-24
replaces: order-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = ordo
organized in class: Taxon

Organism
comment: A particular organism or defined group of organisms considered to be taxonomically homogeneous.
description: 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.
issued: 2014-10-23
modified: 2014-10-23
type: Class
has version: Organism-2014-10-23
status: recommended
decision: Decision-2014-10-26 14
abcd equivalence: not in ABCD

Organism ID
comment: 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.
issued: 2014-10-23
modified: 2014-10-23
type: Property
has version: organismID-2014-10-23
sub property of: identifier
replaces: individualID-2009-04-24
status: recommended
decision: Decision-2014-10-26 14
abcd equivalence: not in ABCD
organized in class: Organism

Organism Name
comment: A textual name or label assigned to an Organism instance.
description: Examples: "Huberta", "Boab Prison Tree", "J pod".
issued: 2014-10-23
modified: 2014-10-23
type: Property
has version: organismName-2014-10-23
status: recommended
decision: Decision-2014-10-26 14
abcd equivalence: not in ABCD
organized in class: Organism

Organism Remarks
comment: Comments or notes about the Organism instance.
description: Example: "One of a litter of six."
issued: 2014-10-23
modified: 2014-10-23
type: Property
has version: organismRemarks-2014-10-23
status: recommended
decision: Decision-2014-10-26 14
abcd equivalence: not in ABCD
organized in class: Organism

Organism Scope
comment: 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.
description: 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".
issued: 2014-10-23
modified: 2014-10-23
type: Property
has version: organismScope-2014-10-23
status: recommended
decision: Decision-2014-10-26 14
abcd equivalence: not in ABCD
organized in class: Organism

Original Name Usage
comment: 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.
description: Examples: "Pinus abies", "Gasterosteus saltatrix Linnaeus 1768"
issued: 2008-11-19
modified: 2009-09-21
type: Property
has version: originalNameUsage-2009-09-21
replaces: basionym-2009-04-24
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

Original Name Usage ID
comment: 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.
description: Example: "http://species.gbif.org/abies_alba_1753"
issued: 2009-01-21
modified: 2009-09-21
type: Property
has version: originalNameUsageID-2009-09-21
sub property of: identifier
replaces: basionymID-2009-04-24
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

Other Catalog Numbers
comment: 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.
description: The recommended best practice is to separate the values with a vertical bar (' | '). Examples: "FMNH:Mammal:1234", "NPS YELLO6778 | MBG 33424".
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: otherCatalogNumbers-2014-10-23
replaces: otherCatalogNumbers-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: DataSets/DataSet/Units/Unit/SpecimenUnit/History/PreviousUnitsText
organized in class: Occurrence

Owner Institution Code
comment: The name (or acronym) in use by the institution having ownership of the object(s) or information referred to in the record.
description: Examples: "NPS", "APN", "InBio"
issued: 2009-08-24
modified: 2013-10-04
type: Property
has version: ownerInstitutionCode-2009-08-24
status: recommended
abcd equivalence: not in ABCD
organized in class: all

Parent Name Usage
comment: 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.
description: Examples: "Rubiaceae", "Gruiformes", "Testudinae"
issued: 2009-08-24
modified: 2009-09-21
type: Property
has version: parentNameUsage-2009-09-21
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName
organized in class: Taxon

Parent Name Usage ID
comment: 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.
description: Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"
issued: 2009-01-21
modified: 2009-09-21
type: Property
has version: parentNameUsageID-2009-09-21
sub property of: identifier
replaces: higherTaxonNameID-2009-04-24
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

Phylum
comment: The full scientific name of the phylum or division in which the taxon is classified.
description: Examples: "Chordata" (phylum), "Bryophyta" (division)
issued: 2008-11-19
modified: 2009-08-24
type: Property
has version: phylum-2009-08-24
replaces: phylum-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/HigherTaxa/HigherTaxon/HigherTaxonName with HigherTaxa/HigherTaxon/HigherTaxonRank = phylum
organized in class: Taxon

Point Radius Spatial Fit
comment: 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.
description: Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006.
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: pointRadiusSpatialFit-2009-04-24
replaces: PointRadiusSpatialFit-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/PointRadiusSpatialFit
organized in class: Location

Preparations
comment: A list (concatenated and separated) of preparations and preservation methods for a specimen.
description: 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)".
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: preparations-2014-10-23
replaces: preparations-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: DataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/PreparationsText
organized in class: Occurrence

Preserved Specimen
comment: A specimen that has been preserved.
issued: 2014-10-23
modified: 2014-10-23
type: Class
has version: PreservedSpecimen-2014-10-23
replaces: PreservedSpecimen-2011-10-16
status: recommended
decision: Decision-2014-10-26 15
abcd equivalence: RecordBasisEnum/PreservedSpecimen

Previous Identifications
comment: A list (concatenated and separated) of previous assignments of names to the Organism.
description: 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".
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: previousIdentifications-2014-10-23
replaces: previousIdentifications-2009-05-18
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification with PreferredFlag = false
organized in class: Organism

Recorded By
comment: 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.
description: 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.
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: recordedBy-2014-10-23
sub property of: According To
replaces: recordedBy-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/GatheringAgents/GatheringAgentsText
organized in class: Occurrence

Record Number
comment: 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.
description: Example: "OPP 7101"
issued: 2008-11-19
modified: 2009-05-18
type: Property
has version: recordNumber-2009-04-24
replaces: CollectorNumber-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/CollectorsFieldNumber
organized in class: Occurrence

Related Resource ID
comment: An identifier for a related resource (the object, rather than the subject of the relationship).
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: relatedResourceID-2009-04-24
sub property of: identifier
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitSourceName + DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociatedUnitID
organized in class: Resource Relationship

Relationship According To
comment: The source (person, organization, publication, reference) establishing the relationship between the two resources.
description: Example: "Julie Woodruff"
issued: 2009-04-24
modified: 2009-04-24
type: Property
has version: relationshipAccordingTo-2009-04-24
sub property of: According To
status: recommended
abcd equivalence: not in ABCD
organized in class: Resource Relationship

Relationship Established Date
comment: 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).
description: 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.
issued: 2009-04-24
modified: 2009-04-24
type: Property
has version: relationshipEstablishedDate-2009-04-24
sub property of: date
status: recommended
abcd equivalence: not in ABCD
organized in class: Resource Relationship

Relationship Of Resource
comment: 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.
description: Examples: "duplicate of", "mother of", "endoparasite of", "host to", "sibling of", "valid synonym of", "located within"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: relationshipOfResource-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Associations/UnitAssociation/AssociationType
organized in class: Resource Relationship

Relationship Remarks
comment: Comments or notes about the relationship between the two resources.
description: Examples: "mother and offspring collected from the same nest", "pollinator captured in the act"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: relationshipRemarks-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Associations/UnitAssociation/Comments
organized in class: Resource Relationship

Reproductive Condition
comment: The reproductive condition of the biological individual(s) represented in the Occurrence. Recommended best practice is to use a controlled vocabulary.
description: Examples" "non-reproductive", "pregnant", "in bloom", "fruit-bearing"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: reproductiveCondition-2009-04-24
status: recommended
abcd equivalence: not in ABCD
organized in class: Occurrence

Resource ID
comment: An identifier for the resource that is the subject of the relationship.
issued: 2009-04-24
modified: 2009-04-24
type: Property
has version: resourceID-2009-04-24
sub property of: identifier
status: recommended
abcd equivalence: not in ABCD
organized in class: Resource Relationship

Resource Relationship
comment: A relationship of one rdfs:Resource (http://www.w3.org/2000/01/rdf-schema#Resource) to another.
description: 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.
issued: 2008-11-19
modified: 2014-10-23
type: Class
has version: ResourceRelationship-2014-10-23
replaces: ResourceRelationship-2009-01-21
status: recommended
decision: Decision-2014-10-26 15
abcd equivalence: DataSets/DataSet/Units/Unit/Associations

Resource Relationship ID
comment: An identifier for an instance of relationship between one resource (the subject) and another (relatedResource, the object).
issued: 2009-01-26
modified: 2009-04-24
type: Property
has version: resourceRelationshipID-2009-04-24
sub property of: identifier
status: recommended
abcd equivalence: not in ABCD
organized in class: Resource Relationship

Sampling Effort
comment: The amount of effort expended during an Event.
description: Examples: "40 trap-nights", "10 observer-hours; 10 km by foot; 30 km by car"
issued: 2009-08-24
modified: 2009-08-24
type: Property
has version: samplingEffort-2009-08-24
status: recommended
abcd equivalence: not in ABCD
organized in class: Event

Sampling Protocol
comment: The name of, reference to, or description of the method or protocol used during an Event.
description: 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"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: samplingProtocol-2009-04-24
replaces: CollectingMethod-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Method
organized in class: Event

Scientific Name
comment: 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.
description: 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)
issued: 2008-11-19
modified: 2009-09-21
type: Property
has version: scientificName-2009-09-21
replaces: scientificName-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/FullScientificNameString
organized in class: Taxon

Scientific Name Authorship
comment: The authorship information for the scientificName formatted according to the conventions of the applicable nomenclaturalCode.
description: Example: "(Torr.) J.T. Howell", "(Martinovský) Tzvelev", "(Györfi, 1952)"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: scientificNameAuthorship-2009-04-24
replaces: AuthorYearOfScientificName-2007-04-17
status: recommended
abcd equivalence: {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}
organized in class: Taxon

Scientific Name ID
comment: An identifier for the nomenclatural (not taxonomic) details of a scientific name.
description: Example: "urn:lsid:ipni.org:names:37829-1:1.3"
issued: 2008-11-19
modified: 2009-08-24
type: Property
has version: scientificNameID-2009-08-24
sub property of: identifier
replaces: TaxonNameID-2009-04-24
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

Sex
comment: The sex of the biological individual(s) represented in the Occurrence. Recommended best practice is to use a controlled vocabulary.
description: Examples: "female", "hermaphrodite", "8 males, 4 females"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: sex-2009-04-24
replaces: Sex-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Sex
organized in class: Occurrence

Specific Epithet
comment: The name of the first or species epithet of the scientificName.
description: Examples: "concolor", "gottschei"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: specificEpithet-2009-04-24
replaces: SpecificEpithet-2007-04-17
status: recommended
abcd equivalence: {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}
organized in class: Taxon

Start Day Of Year
comment: 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).
description: Examples: "1" (=1 Jan), "366" (=31 Dec), "365" (=30 Dec in a leap year, 31 Dec in a non-leap year)
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: startDayOfYear-2009-04-24
replaces: DayOfYear-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/DateTime/DayNumberBegin
organized in class: Event

State Province
comment: The name of the next smaller administrative region than country (state, province, canton, department, region, etc.) in which the Location occurs.
description: Examples: "Montana", "Minas Gerais", "Córdoba"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: stateProvince-2009-04-24
replaces: StateProvince-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= State or = Province (etc.)
organized in class: Location

Subgenus
comment: The full scientific name of the subgenus in which the taxon is classified. Values should include the genus to avoid homonym confusion.
description: Examples: "Strobus (Pinus)", "Puma (Puma)" "Loligo (Amerigo)", "Hieracium subgen. Pilosella"
issued: 2008-11-19
modified: 2009-08-24
type: Property
has version: subgenus-2009-08-24
replaces: subgenus-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Zoological/Subgenus
organized in class: Taxon

Taxon
comment: A group of organisms (sensu http://purl.obolibrary.org/obo/OBI_0100026) considered by taxonomists to form a homogeneous unit.
description: Example: The genus Truncorotaloides as published by Brönnimann et al. in 1953 in the Journal of Paleontology Vol. 27(6) p. 817-820.
issued: 2008-11-19
modified: 2014-10-23
type: Class
has version: Taxon-2014-10-23
replaces: Taxon-2009-09-21
status: recommended
decision: Decision-2014-10-26 15
abcd equivalence: no simple equivalent in ABCD

Taxon Concept ID
comment: An identifier for the taxonomic concept to which the record refers - not for the nomenclatural details of a taxon.
description: Example: "8fa58e08-08de-4ac1-b69c-1235340b7001"
issued: 2009-04-24
modified: 2009-09-21
type: Property
has version: taxonConceptID-2009-09-21
sub property of: identifier
replaces: taxonConceptID-2009-04-24
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

Taxon ID
comment: 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.
description: Examples: "8fa58e08-08de-4ac1-b69c-1235340b7001", "32567", "http://species.gbif.org/abies_alba_1753", "urn:lsid:gbif.org:usages:32567"
issued: 2008-11-19
modified: 2009-08-24
type: Property
has version: taxonID-2009-08-24
sub property of: identifier
replaces: scientificNameID-2009-07-06
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

Taxonomic Status
comment: 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.
description: Examples: "invalid", "misapplied", "homotypic synonym", "accepted"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: taxonomicStatus-2009-04-24
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

Taxon Rank
comment: The taxonomic rank of the most specific name in the scientificName. Recommended best practice is to use a controlled vocabulary.
description: Examples: "subspecies", "varietas", "forma", "species", "genus"
issued: 2008-11-19
modified: 2009-09-21
type: Property
has version: taxonRank-2009-09-21
replaces: scientificNameRank-2009-07-06
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Identifications/Identification/TaxonIdentified/ScientificName/NameAtomised/Botanical/Rank
organized in class: Taxon

Taxon Remarks
comment: Comments or notes about the taxon or name.
description: Example: "this name is a misspelling in common use"
issued: 2008-11-19
modified: 2009-08-24
type: Property
has version: taxonRemarks-2009-08-24
replaces: taxonRemarks-2009-04-24
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

Type Status
comment: A list (concatenated and separated) of nomenclatural types (type status, typified scientific name, publication) applied to the subject.
description: 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".
issued: 2008-11-19
modified: 2014-10-23
type: Property
has version: typeStatus-2014-10-23
replaces: typeStatus-2009-04-24
status: recommended
decision: Decision-2014-10-30 16
abcd equivalence: DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeText
organized in class: Identification

Verbatim Coordinates
comment: 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.
description: Examples: "41 05 54S 121 05 34W", "17T 630000 4833400"
issued: 2008-11-19
modified: 2009-07-06
type: Property
has version: verbatimCoordinates-2009-04-24
replaces: VerbatimCoordinates-2007-04-17
status: recommended
abcd equivalence: {DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/CoordinatesText or DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesUTM/UTMText}
organized in class: Location

Verbatim Coordinate System
comment: The spatial coordinate system for the verbatimLatitude and verbatimLongitude or the verbatimCoordinates of the Location. Recommended best practice is to use a controlled vocabulary.
description: Examples: "decimal degrees", "degrees decimal minutes", "degrees minutes seconds", "UTM"
issued: 2008-11-19
modified: 2009-07-06
type: Property
has version: verbatimCoordinateSystem-2009-04-24
replaces: VerbatimCoordinateSystem-2007-04-17
status: recommended
abcd equivalence: (partly) DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesGrid/GridCellSystem
organized in class: Location

Verbatim Depth
comment: The original description of the depth below the local surface.
description: Example: "100-200 m"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: verbatimDepth-2009-04-24
replaces: VerbatimDepth-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactText
organized in class: Location

Verbatim Elevation
comment: The original description of the elevation (altitude, usually above sea level) of the Location.
description: Example: "100-200 m"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: verbatimElevation-2009-04-24
replaces: VerbatimElevation-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactText
organized in class: Location

Verbatim EventDate
comment: The verbatim original representation of the date and time information for an Event.
description: Examples: "spring 1910", "Marzo 2002", "1999-03-XX", "17IV1934"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: verbatimEventDate-2009-04-24
replaces: VerbatimCollectingDate-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/DateTime/DateText
organized in class: Event

Verbatim Latitude
comment: 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.
description: Example: "41 05 54.03S"
issued: 2008-11-19
modified: 2009-07-06
type: Property
has version: verbatimLatitude-2009-04-24
replaces: VerbatimLatitude-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLatitude
organized in class: Location

Verbatim Locality
comment: The original textual description of the place.
description: Example: "25 km NNE Bariloche por R. Nac. 237"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: verbatimLocality-2009-04-24
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName
organized in class: Location

Verbatim Longitude
comment: 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.
description: Example: "121d 10' 34" W"
issued: 2008-11-19
modified: 2009-07-06
type: Property
has version: verbatimLongitude-2009-04-24
replaces: VerbatimLongitude-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/VerbatimLongitude
organized in class: Location

Verbatim SRS
comment: 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".
description: Examples: "EPSG:4326", "WGS84", "NAD27", "Campo Inchauspe", "European 1950", "Clarke 1866"
issued: 2009-07-06
modified: 2009-07-06
type: Property
has version: verbatimSRS-2009-07-06
status: recommended
abcd equivalence: not in ABCD
organized in class: Location

Verbatim Taxon Rank
comment: The taxonomic rank of the most specific name in the scientificName as it appears in the original record.
description: Examples: "Agamospecies", "sub-lesus", "prole", "apomict", "nothogrex", "sp.", "subsp.", "var."
issued: 2009-07-06
modified: 2009-09-21
type: Property
has version: verbatimRank-2009-09-21
replaces: verbatimScientificNameRank-2009-07-06
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

Vernacular Name
comment: A common or vernacular name.
description: Examples: "Andean Condor", "Condor Andino", "American Eagle", "Gänsegeier"
issued: 2009-07-06
modified: 2009-07-06
type: Property
has version: vernacularName-2009-07-06
status: recommended
abcd equivalence: not in ABCD
organized in class: Taxon

Water Body
comment: 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.
description: Examples: "Indian Ocean", "Baltic Sea", "Hudson River"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: waterBody-2009-04-24
replaces: WaterBody-2007-04-17
status: recommended
abcd equivalence: DataSets/DataSet/Units/Unit/Gathering/NamedAreas/NamedArea/AreaName with NamedAreas/NamedArea/AreaClass= Water body
organized in class: Location

Year
comment: The four-digit year in which the Event occurred, according to the Common Era Calendar.
description: Example: "2008"
issued: 2008-11-19
modified: 2009-04-24
type: Property
has version: year-2009-04-24
replaces: YearCollected-2003-06-17
status: recommended
abcd equivalence: accessible from DataSets/DataSet/Units/Unit/Gathering/ISODateTimeBegin
organized in class: Event