Quick reference guide by dependencies

Recommended best practice is to separate the values in a list with space vertical bar space ( | ). This term has an equivalent in the dwciri: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

• Rob Guralnick
• Peter Desmet | Stijn Van Hoey

Recommended best practice is to use a date that conforms to ISO 8601-1:2019.

• 1963-03-08T14:07-0600 (8 Mar 1963 at 2:07pm in the time zone six hours earlier than UTC)
• 2009-02-20T08:40Z (20 February 2009 8:40am UTC)
• 2018-08-29T15:19 (3:19pm local time on 29 August 2018)
• 1809-02-12 (some time during 12 February 1809)
• 1906-06 (some time in June 1906)
• 1971 (some time in the year 1971)
• 2007-03-01T13:00:00Z/2008-05-11T15:30:00Z (some time during the interval between 1 March 2007 1pm UTC and 11 May 2008 3:30pm UTC)
• 1900/1909 (some time during the interval between the beginning of the year 1900 and the end of the year 1909)
• 2007-11-13/15 (some time in the interval between 13 November 2007 and 15 November 2007)

• 9c752d22-b09a-11e8-96f8-529269fb1459

This term has an equivalent in the dwciri: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

• minimum convex polygon around burrow entrances (for a home range area)
• barometric altimeter (for an elevation)

• tip of tail missing

Recommended best practice is to use a controlled vocabulary. This term has an equivalent in the dwciri: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

• tail length
• temperature
• trap line length
• survey area
• trap type

Recommended best practice is to use the International System of Units (SI). This term has an equivalent in the dwciri: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

• m
• g
• l
• °C
• mm
• km²
• %
• hh:mm:ss

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

• http://vocab.nerc.ac.uk/collection/L22/current/TOOL0960/

This term has an equivalent in the dwciri: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

• 45
• 20
• 1
• 14.5
• UV-light

• http://arctos.database.museum/guid/WNMU:Mamm:1249

• Huberta
• Boab Prison Tree
• J pod

A dwc:organismQuantityType must have a corresponding dwc:organismQuantity. This term has an equivalent in the dwciri: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

• 27 (organismQuantity) with individuals (organismQuantityType)
• 12.5 (organismQuantity) with % biomass (organismQuantityType)
• r (organismQuantity) with Braun-Blanquet Scale (organismQuantityType)
• many (organismQuantity) with individuals (organismQuantityType)

• One of a litter of six

Recommended best practice is to use a controlled vocabulary. This term is not intended to be used to specify a type of dwc:Taxon. To describe the kind of dwc:Organism using a URI object in RDF, use rdf:type (http://www.w3.org/1999/02/22-rdf-syntax-ns#type) instead.

• multicellular organism
• virus
• clone
• pack
• colony

Recommended best practice is to separate the values in a list with space vertical bar space ( | ).

• Chalepidae
• Pinus abies
• Anthus sp., field ID by G. Iglesias | Anthus correndera, expert ID by C. Cicero 2009-02-12 based on morphology

• dc609808-b09b-11e8-96f8-529269fb1459

• Julie Woodruff

Recommended best practice is to use a date that conforms to ISO 8601-1:2019.

• 1963-03-08T14:07-0600 (8 Mar 1963 at 2:07pm in the time zone six hours earlier than UTC)
• 2009-02-20T08:40Z (20 February 2009 8:40am UTC)
• 2018-08-29T15:19 (3:19pm local time on 29 August 2018)
• 1809-02-12 (some time during 12 February 1809)
• 1906-06 (some time in June 1906)
• 1971 (some time in the year 1971)
• 2007-03-01T13:00:00Z/2008-05-11T15:30:00Z (some time during the interval between 1 March 2007 1pm UTC and 11 May 2008 3:30pm UTC)
• 1900/1909 (some time during the interval between the beginning of the year 1900 and the end of the year 1909)
• 2007-11-13/15 (some time in the interval between 13 November 2007 and 15 November 2007)

Recommended best practice is to use a controlled vocabulary.

• same as
• duplicate of
• mother of
• offspring of
• sibling of
• parasite of
• host of
• valid synonym of
• located within
• pollinator of members of taxon
• pollinated specific plant
• pollinated by members of taxon
• on slab with

Recommended best practice is to use the identifiers of the terms in a controlled vocabulary, such as the OBO Relation Ontology.

• http://purl.obolibrary.org/obo/RO_0002456 (for the relation pollinated by)
• http://purl.obolibrary.org/obo/RO_0002455 (for the relation pollinates)
• https://www.inaturalist.org/observation_fields/879 (for the relation eaten by)

• mother and offspring collected from the same nest
• pollinator captured in the act

• f809b9e0-b09b-11e8-96f8-529269fb1459

• 04b16710-b09c-11e8-96f8-529269fb1459

• a specimen collecting event
• a camera trap image capture
• a marine trawl

• a body fossil
• a coprolite
• a gastrolith
• an ichnofossil
• a piece of a petrified tree

• a lithostratigraphic layer

• evidence of a dwc:Occurrence taken from field notes or literature
• a record of a dwc:Occurrence without physical evidence or evidence captured with a machine

• a subspecies determination of an organism

• a living plant in a botanical garden
• a living animal in a zoo

• the municipality of San Carlos de Bariloche, Río Negro, Argentina
• the place defined by a georeference

• a photograph
• a video
• an audio recording
• a remote sensing image
• a dwc:Occurrence record based on telemetry

This class constitutes a new value for the controlled vocabulary in the recommendations for basisOfRecord. When importing Darwin Core Archives of literature-based datasets to GBIF, the basisOfRecord should be changed from "Occurrence", "PreservedSpecimen" or "Literature" to "MaterialCitation".

• a citation of a physical specimen from a scientific collection in a taxonomic treatment in a scientific publication
• a citation of a group of physical specimens, such as paratypes in a taxonomic treatment in a scientific publication

The term is defined at the most general level to admit descriptions of any subtype of material entity within the scope of Darwin Core. In particular, any kind of material sample, preserved specimen, fossil, or exemplar from living collections is intended to be subsumed under this term.

• an instance of a fossil
• an instance of a herbarium sheet with its attached plant specimen
• a particular part of the plant-derived material affixed to a herbarium sheet
• an instance of a frozen tissue sample
• a specific water sample
• an instance of a meteorite fragment
• a particular wolf in a zoo
• a particular pack of wolves in the wild
• an isolated molecule of DNA
• a specific deep-frozen DNA sample
• a particular field notebook
• a particular paper page from a field notebook
• an instance of a printed photograph

• a whole organism preserved in a collection
• a part of an organism isolated for some purpose
• a soil sample; a marine microbial sample

Resources can be thought of as identifiable records or instances of classes and may include, but need not be limited to instances of dwc:Occurrence, dwc:Organism, dwc:MaterialEntity, dwc:Event, dcterms:Location, dwc:GeologicalContext, dwc:Identification, or dwc:Taxon.

• the weight of a dwc:Organism in grams
• the number of placental scars; surface water temperature in Celsius

• a wolf pack on the shore of Kluane Lake in 1988
• a virus in a plant leaf in the New York Botanical Garden at 15:29 on 2014-10-23
• a fungus in Central Park in the summer of 1929

Instances of the dwc:Organism class are intended to facilitate linking one or more dwc:Identification instances to one or more dwc:Occurrence instances. Therefore, things that are typically assigned scientific names (such as viruses, hybrids, and lichens) and aggregates whose dwc:Occurrences are typically recorded (such as packs, clones, and colonies) are included in the scope of this class.

• a specific bird
• a specific wolf pack
• a specific instance of a bacterial culture

• a plant on an herbarium sheet
• a cataloged lot of fish in a jar

Resources can be thought of as identifiable records or instances of classes and may include, but need not be limited to instances of dwc:Occurrence, dwc:Organism, dwc:MaterialEntity, dwc:Event, dcterms:Location, dwc:GeologicalContext, dwc:Identification, or dwc:Taxon.

• an instance of a dwc:Organism is the mother of another instance of a dwc:Organism
• a uniquely identified dwc:Occurrence represents the same dwc:Occurrence as another uniquely identified dwc:Occurrence
• a dwc:MaterialEntity is a subsample of another dwc:MaterialEntity

• the genus Truncorotaloides as published by Brönnimann et al. in 1953 in the Journal of Paleontology Vol. 27(6) p. 817-820

Recommended best practice is to use a controlled vocabulary. Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Recommended best practice is to use a controlled vocabulary that aligns best with the dwc:Taxon. Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Recommended best practice is to use IRIs from the controlled vocabulary designated for use with this term, listed at http://rs.tdwg.org/dwc/doc/doe/. For details, refer to https://doi.org/10.3897/biss.3.38084. Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

• http://rs.tdwg.org/dwcdoe/values/d003
• http://rs.tdwg.org/dwcdoe/values/d005

Recommended best practice is to use a controlled vocabulary. Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Recommended best practice is to use an IRI from a controlled vocabulary. A "convenience property" that replaces Darwin Core literal-value terms related to geological context. See Section 2.7.6 of the Darwin Core RDF Guide for details.

Recommended best practice is to use IRIs from the controlled vocabulary designated for use with this term, listed at http://rs.tdwg.org/dwc/doc/em/. For details, refer to https://doi.org/10.3897/biss.3.38084 . Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

• http://rs.tdwg.org/dwcem/values/e001
• http://rs.tdwg.org/dwcem/values/e005

Recommended best practice is to use a controlled vocabulary. Regardless of the dwc:eventType, the interval of the dwc:Event can be captured in dwc:eventDate. Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

The subject is a dwc:Event instance and the object is a (possibly IRI-identified) resource that is the field notes.

The subject is a (possibly IRI-identified) resource that is the field notes and the object is a dwc:Event instance.

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Recommended best practice is to use an IRI from a controlled vocabulary. A "convenience property" that replaces Darwin Core literal-value terms related to geological context. See Section 2.7.7 of the Darwin Core RDF Guide for details.

Recommended best practice is to use an IRI for the EPSG code of the SRS, if known. Otherwise use an IRI or controlled vocabulary for the name or code of the geodetic datum, if known. Otherwise use an IRI or controlled vocabulary for the name or code of the ellipsoid, if known. If none of these is known, use the value unknown.

• https://epsg.io/4326

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Recommended best practice is to use a controlled vocabulary. Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects. Recommended best practice is to use a controlled vocabulary such as that used in HISPID and ABCD.

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Recommended best practice is to use an IRI from a controlled registry. A "convenience property" that replaces literal-value terms related to collections and institutions. See Section 2.7.3 of the Darwin Core RDF Guide for details.

A string literal name of the dataset can be provided using the term dwc:datasetName. See the Darwin Core RDF Guide for details.

Recommended best practice is to use an IRI from a controlled registry. A "convenience property" that replaces Darwin Core literal-value terms related to locations. See Section 2.7.5 of the Darwin Core RDF Guide for details.

• http://vocab.getty.edu/tgn/1019987

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Recommended best practice is to use a controlled vocabulary such as RFC 5646. This term has an equivalent in the dcterms: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

• en (for English)
• es (for Spanish)

Recommended best practice is to use an IRI from a controlled vocabulary. A "convenience property" that replaces Darwin Core literal-value terms related to geological context. See Section 2.7.6 of the Darwin Core RDF Guide for details.

Recommended best practice is to use a controlled vocabulary. Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Recommended best practice is to use a controlled vocabulary. Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Recommended best practice is to use a controlled vocabulary such as the Ontology of Units of Measure http://www.wurvoc.org/vocabularies/om-1.8/ of SI units, derived units, or other non-SI units accepted for use within the SI.

Recommended best practice is to use a controlled vocabulary. Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

A dwc:organismQuantityType must have a corresponding dwc:organismQuantity.

Recommended best practice is to use IRIs from the controlled vocabulary designated for use with this term, listed at http://rs.tdwg.org/dwc/doc/pw/. For details, refer to https://doi.org/10.3897/biss.3.38084 . Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

• http://rs.tdwg.org/dwcpw/values/p002
• http://rs.tdwg.org/dwcpw/values/p046

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

The subject is a dwc:Occurrence and the object is a (possibly IRI-identified) resource that is the field notes.

Recommended best practice is to use a controlled vocabulary. Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

A dwc:sampleSizeUnit must have a corresponding dwc:sampleSizeValue. Recommended best practice is to use a controlled vocabulary such as the Ontology of Units of Measure http://www.wurvoc.org/vocabularies/om-1.8/ of SI units, derived units, or other non-SI units accepted for use within the SI.

Recommended best practice is describe a dwc:Event with no more than one sampling protocol. In the case of a summary dwc:Event in which a specific protocol can not be attributed to specific dwc:Occurrences, the recommended best practice is to repeat the property for each IRI that denotes a different sampling protocol that applies to the dwc:Occurrence.

• https://doi.org/10.1111/j.1466-8238.2009.00467.x

Recommended best practice is to use a controlled vocabulary. Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

A "convenience property" that replaces Darwin Core literal-value terms related to taxonomic entities. See Section 2.7.4 of the Darwin Core RDF Guide for details.

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Recommended best practice is to use a controlled vocabulary. Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Recommended best practice is to use an IRI for the EPSG code of the SRS, if known. Otherwise use a controlled vocabulary IRI for the name or code of the geodetic datum, if known. Otherwise use a controlled vocabulary IRI for the name or code of the ellipsoid, if known.

Recommended best practice is to use a controlled vocabulary. Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Recommended best practice is to use a controlled vocabulary. Intended to be used with records having a dwc:basisOfRecord of PreservedSpecimen, MaterialEntity, MaterialSample, or HumanObservation. Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Access Rights may include information regarding access or restrictions based on privacy, security, or other policies.

• not-for-profit use only (string literal example)
• https://www.fieldmuseum.org/field-museum-natural-history-conditions-and-suggested-norms-use-collections-data-and-images (URI example)

Recommended best practice is to use a controlled vocabulary such as the set of local names of the identifiers for classes in Darwin Core.

• MaterialEntity
• PreservedSpecimen
• FossilSpecimen
• LivingSpecimen
• MaterialSample
• Event
• HumanObservation
• MachineObservation
• Taxon
• Occurrence
• MaterialCitation

From Dublin Core, "Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible." The intended usage of this term in Darwin Core is to provide the preferred way to cite the resource itself - "how to cite this record". Note that the intended usage of dcterms:references in Darwin Core, by contrast, is to point to the definitive source representation of the resource - "where to find the as-close-to-original reference", if one is available.

• Museum of Vertebrate Zoology, UC Berkeley. MVZ Mammal Collection (Arctos). Record ID: http://arctos.database.museum/guid/MVZ:Mamm:165861?seid=101356. Source: http://ipt.vertnet.org:8080/ipt/resource.do?r=mvz_mammal. (Occurrence example)
• https://www.gbif.org/species/2439608 Source: GBIF Taxonomic Backbone (Taxon example)
• Rand, K.M., Logerwell, E.A. The first demersal trawl survey of benthic fish and invertebrates in the Beaufort Sea since the late 1970s. Polar Biol 34, 475–488 (2011). https://doi.org/10.1007/s00300-010-0900-2 (Event example)

• Mammals
• Hildebrandt
• EBIRD
• VP

For physical specimens, the recommended best practice is to use a globally unique and resolvable identifier from a collections registry such as the GBIF Registry of Scientific Collections.

• https://www.gbif.org/grscicoll/collection/fbd3ed74-5a21-4e01-b86a-33d36f032d9c

This term has an equivalent in the dwciri: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

• Coordinates generalized from original GPS coordinates to the nearest half degree grid cell.

• b15d4952-7d20-46f1-8a3e-556a512b04c5

• Grinnell Resurvey Mammals
• Lacey Ctenomys Recaptures

According to the DCMI Metadata Terms Vocabulary recommended practice is to describe the date, date/time, or period of time as recommended for the property Date, of which this is a subproperty. According to Darwin Core standard recommended best practice is to use a date that conforms to ISO 8601-1:2019.

• 1963-03-08T14:07-0600 (8 Mar 1963 at 2:07pm in the time zone six hours earlier than UTC)
• 2009-02-20T08:40Z (20 February 2009 8:40am UTC)
• 2018-08-29T15:19 (3:19pm local time on 29 August 2018)
• 1809-02-12 (some time during 12 February 1809)
• 1906-06 (some time in June 1906)
• 1971 (some time in the year 1971)
• 2007-03-01T13:00:00Z/2008-05-11T15:30:00Z (some time during the interval between 1 March 2007 1pm UTC and 11 May 2008 3:30pm UTC)
• 1900/1909 (some time during the interval between the beginning of the year 1900 and the end of the year 1909)
• 2007-11-13/15 (some time in the interval between 13 November 2007 and 15 November 2007)

Recommended best practice is to use a key:value encoding schema for a data interchange format such as JSON.

• {"heightInMeters":1.5}
• {"targusLengthInMeters":0.014, "weightInGrams":120}
• {"natureOfID":"expert identification", "identificationEvidence":"cytochrome B sequence"}
• {"relativeHumidity":28, "airTemperatureInCelsius":22, "sampleSizeInKilograms":10}
• {"aspectHeading":277, "slopeInDegrees":6}
• {"iucnStatus":"vulnerable", "taxonDistribution":"Neuquén, Argentina"}

This term has an equivalent in the dwciri: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

• location information not given for endangered species
• collector identities withheld
• ask about tissue samples

• MVZ
• FMNH
• CLO
• UCMP

For physical specimens, the recommended best practice is to use a globally unique and resolvable identifier from a collections registry such as the Research Organization Registry (ROR) or the GBIF Registry of Scientific Collections.

• https://ror.org/015hz7p22
• http://grscicoll.org/institution/museum-southwestern-biology
• https://www.gbif.org/grscicoll/institution/e3d4dcc4-81e2-444c-8a5c-41d1044b5381

Recommended best practice is to use an IRI from the Library of Congress ISO 639-2 scheme.

Recommended practice is to identify the license document with a URI. If this is not possible or feasible, a literal value that identifies the license may be provided.

• http://creativecommons.org/publicdomain/zero/1.0/legalcode
• http://creativecommons.org/licenses/by/4.0/legalcode

• NPS
• APN
• InBio

From Dublin Core, "This property is intended to be used with non-literal values. This property is an inverse property of Is Referenced By." the intended usage of this term in Darwin Core is to point to the definitive source representation of the resource (e.g.,dwc:Taxon, dwc:Occurrence, dwc:Event), if one is available. Note that the intended usage of dcterms:bibliographicCitation in Darwin Core, by contrast, is to provide the preferred way to cite the resource itself.

• http://arctos.database.museum/guid/MVZ:Mamm:165861 (MaterialEntity example)
• https://www.catalogueoflife.org/data/taxon/32664 (Taxon example)

Recommended practice is to refer to the rights holder with a URI. If this is not possible or feasible, a literal value that identifies the rights holder may be provided.

• The Regents of the University of California

Recommended practice is to use a controlled vocabulary such as the DCMI Type Vocabulary DCMI-TYPE. To describe the file format, physical medium, or dimensions of the resource, use the property Format.

• StillImage
• MovingImage
• Sound
• PhysicalObject
• Event
• Text

Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names. Recommended best practice is to leave this field blank if the dcterms:Location spans multiple entities at this administrative level or if the dcterms:Location might be in one or another of multiple possible entities at this level. Multiplicity and uncertainty of the geographic entity can be captured either in the term dwc:higherGeography or in the term dwc:locality, or both.

• Africa
• Antarctica
• Asia
• Europe
• North America
• Oceania
• South America

• 0.00001 (normal GPS limit for decimal degrees)
• 0.000278 (nearest second)
• 0.01667 (nearest minute)
• 1.0 (nearest degree)

• 30 (reasonable lower limit on or after 2000-05-01 of a GPS reading under good conditions if the actual precision was not recorded at the time)
• 100 (reasonable lower limit before 2000-05-01 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)

Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names. Recommended best practice is to leave this field blank if the dcterms:Location spans multiple entities at this administrative level or if the dcterms:Location might be in one or another of multiple possible entities at this level. Multiplicity and uncertainty of the geographic entity can be captured either in the term dwc:higherGeography or in the term dwc:locality, or both.

• Denmark
• Colombia
• España

Recommended best practice is to use an ISO 3166-1-alpha-2 country code. Recommended best practice is to leave this field blank if the dcterms:Location spans multiple entities at this administrative level or if the dcterms:Location might be in one or another of multiple possible entities at this level. Multiplicity and uncertainty of the geographic entity can be captured either in the term dwc:higherGeography or in the term dwc:locality, or both.

• AR
• SV

Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names. Recommended best practice is to leave this field blank if the dcterms:Location spans multiple entities at this administrative level or if the dcterms:Location might be in one or another of multiple possible entities at this level. Multiplicity and uncertainty of the geographic entity can be captured either in the term dwc:higherGeography or in the term dwc:locality, or both.

• Missoula
• Los Lagos
• Mataró

• -41.0983423

• -121.1761111

Detailed explanations with graphical examples can be found in the Georeferencing Best Practices, Chapman and Wieczorek, 2020.

• 0
• 1
• 1.5708

Recommended best practice is to use the EPSG code of the 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. It is also permitted to provide the SRS in Well-Known-Text, especially if no EPSG code provides the necessary values for the attributes of the SRS. Do not use this term to describe the SRS of the dwc:decimalLatitude and dwc:decimalLongitude, nor of any verbatim coordinates - use the dwc:geodeticDatum and dwc:verbatimSRS instead. This term has an equivalent in the dwciri: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

This term has an equivalent in the dwciri: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

• POLYGON ((10 20, 11 20, 11 21, 10 21, 10 20))

Terms in the dwciri namespace are intended to be used in RDF with non-literal objects.

Recommended best practice is to use the EPSG code of the 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. This term has an equivalent in the dwciri: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

• EPSG:4326
• WGS84
• NAD27
• Campo Inchauspe
• European 1950
• Clarke 1866
• unknown

Recommended best practice is to separate the values in a list with space vertical bar space ( | ). This term has an equivalent in the dwciri: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

• Brad Millen (ROM)
• Kristina Yamamoto | Janet Fang

Recommended best practice is to use a date that conforms to ISO 8601-1:2019.

• 1963-03-08T14:07-0600 (8 Mar 1963 at 2:07pm in the time zone six hours earlier than UTC)
• 2009-02-20T08:40Z (20 February 2009 8:40am UTC)
• 2018-08-29T15:19 (3:19pm local time on 29 August 2018)
• 1809-02-12 (some time during 12 February 1809)
• 1906-06 (some time in June 1906)
• 1971 (some time in the year 1971)
• 2007-03-01T13:00:00Z/2008-05-11T15:30:00Z (some time during the interval between 1 March 2007 1pm UTC and 11 May 2008 3:30pm UTC)
• 1900/1909 (some time during the interval between the beginning of the year 1900 and the end of the year 1909)
• 2007-11-13/15 (some time in the interval between 13 November 2007 and 15 November 2007)

This term has an equivalent in the dwciri: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

• Georeferencing Quick Reference Guide (Zermoglio et al. 2020, https://doi.org/10.35035/e09p-h128)

• Assumed distance by road (Hwy. 101)

Recommended best practice is to separate the values in a list with space vertical bar space ( | ). This term has an equivalent in the dwciri: namespace that allows only an IRI as a value, whereas this term allows for any string literal value.

• https://www.geonames.org/
• USGS 1:24000 Florence Montana Quad 1967 | Terrametrics 2008 on Google Earth
• GeoLocate

Recommended best practice is to separate the values in a list with space vertical bar space ( | ), with terms in order from least specific to most specific.

• North Atlantic Ocean
• South America | Argentina | Patagonia | Parque Nacional Nahuel Huapi | Neuquén | Los Lagos with accompanying values South America (continent) Argentina (country), Neuquén (first order division), and Los Lagos (second order division)

Recommended best practice is to use a persistent identifier from a controlled vocabulary such as the Getty Thesaurus of Geographic Names.

• http://vocab.getty.edu/tgn/1002002 (Antártida e Islas del Atlántico Sur, Territorio Nacional de la Tierra del Fuego, Argentina).

Recommended best practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names.

• Nosy Be
• Bikini Atoll
• Vancouver
• Viti Levu
• Zanzibar