⚠️ Under Review

BDQ Use Case Controlled Vocabulary

Title
BDQ Use Case Controlled Vocabulary

Date version issued
2026-06-03

Date created
2025-05-10

Part of TDWG Standard
http://example.org/to_be_determined

Preferred namespace abbreviation
bdquc

This version
http://rs.tdwg.org/bdquc/terms/2026-06-03

Latest version
http://rs.tdwg.org/bdquc/terms/

Previous version

Abstract
This document is a reference for the BDQ standard. It covers named individual Use Cases.

Authors
Lee Belbin (Blatant Fabrications), Arthur D. Chapman (Australian Biodiversity Information Services), Paul J. Morris (Museum of Comparative Zoology, Harvard University), John Wieczorek (Rauthiflor LLC)

Creator
TDWG Biodiversity Data Quality Interest Group Task Group 2: Data Quality Tests and Assertions

Bibliographic citation
TDWG Biodiversity Data Quality Interest Group Task Group 2: Data Quality Tests and Assertions. 2026. BDQ Use Case Controlled Vocabulary. Biodiversity Information Standards (TDWG). http://rs.tdwg.org/bdquc/terms/2026-06-03

Status
Draft Standard for Review

Table of Contents

1 Introduction (non-normative)

1.1 Purpose (non-normative)

The purpose of this document is to provide the full term list for the bdquc: controlled vocabulary for BDQ Use Cases within the BDQ standard, which support the specification and use of BDQ Tests.

This term list defines the formal structure and meanings of these concepts and provides reference material for implementation and documentation purposes.

1.2 Audience (non-normative)

TODO: Rework for just Use Cases

This document is intended for users who need a precise understanding of the vocabulary elements used in the description of BDQ Use Cases. It will be useful for:

  • Implementers interpreting or extending BDQ Use Cases
  • Standards developers and data quality modelers working with BDQ vocabularies
  • Users who need to understand an potentially extend BDQ Use Cases, either inside or outside the BDQ standard

Familiarity with RDF vocabularies and the Fitness For Use Framework is recommended for full comprehension, but the document is organized to be accessible for any reader needing detailed term definitions.

1.3 Data Quality Vocabulary Terms (non-normative)

The bdquc: vocabulary covers one set of concepts used across the BDQ standard:

  • Use Cases (bdqffdq:UseCase) – formal representations of the purposes for which data might be evaluated using BDQ Tests.

1.4 Associated Documents (non-normative)

For the list and links to all associated documents see The Biodiversity Data Quality (BDQ) Standard.

1.5 Term List Distributions (non-normative)

Description IRI Download URL
HTML file http://rs.tdwg.org/bdquc/terms/ https://raw.githubusercontent.com/tdwg/bdq/master/tg2/_review/docs/list/bdquc/index.md
RDF/XML file TBD https://raw.githubusercontent.com/tdwg/bdq/master/tg2/_review/dist/bdquc.xml

1.6 Status of the Content of this Document (normative)

Sections may be either normative (defines what is required to comply with the standard) or non-normative (supports understanding but is not binding) and are marked as such.

Any sentence or phrase beginning with "For example" or "e.g.", whether in a normative section or a non-normative section, is non-normative.

Section 1.9 Key to Vocabulary Terms (normative) identifies which values in Section 4 are normative and which are non-normative.

1.7 RFC 2119 key words (normative)

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC 2119] and [RFC 8174] when, and only when, they appear in all capitals, as shown here.

1.8 Namespace abbreviations (non-normative)

The following namespace abbreviations are used in this document:

Abbreviation Namespace
bdqffdq: https://rs.tdwg.org/bdqffdq/terms/
bdqval: https://rs.tdwg.org/bdqval/terms/
bdquc: https://rs.tdwg.org/bdquc/terms/
dc: https://purl.org/dc/elements/1.1/
dcterms: http://purl.org/dc/terms/
dwc: http://rs.tdwg.org/dwc/terms/
rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs: http://www.w3.org/2000/01/rdf-schema#
skos: http://www.w3.org/2004/02/skos/core#
tdwgutility: http://rs.tdwg.org/dwc/terms/attributes/

1.9 Key to Vocabulary Terms (normative)

The terminology used to describe the terms in this vocabulary follows the TDWG TDWG Standards Documentation Standard (SDS) (SDS). Each term definition includes the original RDF definition, and may also provide a TDWG-specific interpretation from the SDS, as well as a definition tailored to this local context.

Label (Term) Normative Definition Example
Term Name (rdf:value) normative Idiomatic property used for structured values. TDWG SDS: The term name is a controlled value that represents the class, property, or concept described by the term definition. Alien-Species
Term IRI (dcterms:isVersionOf) normative A related resource of which the described resource is a version, edition, or adaptation. TDWG SDS: The HTTP IRI that uniquely identifies the current term. https://rs.tdwg.org/ bdquc/terms/ Alien-Species
Modified (dcterms:issued) normative Date of formal issuance of the resource. TDWG SDS: The date in ISO 8601 Date format on which the most recent version of the term was issued. 2026-04-22
Term Version IRI (rdf:about) normative The HTTP IRI that identifies the version of the term that is currently in force. https://rs.tdwg.org/ bdquc/terms/version/ Alien-Species-2026-04-22
Label (rdfs:label) normative A human-readable name for the subject. TDWG SDS: A a word or short phrase that serves as a human-readable name for the term. Alien-Species
Definition (rdfs:comment) normative A description of the subject resource. TDWG SDS: The normative definition of the term, written in English. A bdqffdq:UseCase that involves the identification and analysis of whether the occurrence of a taxon is native to a location or not, how it got there and to what extent the taxon has become a permanent feature of the location in order to improve the management and reduce the spread of alien species.
Comments (skos:note) non-normative A general note, for any purpose. See Groom et al. (2019). Improving Darwin Core for research and management of alien species. Biodiversity Information Science and Standards, 3: e38084. https://doi.org/10.3897/biss.3.38084.
Status (tdwgutility:status) Used to indicate if the term is recommended for use or if it is only of historical significance. recommended
Controlled Value () normative A string that is unique within a controlled vocabulary that identifies the concept in the context of a text-based metadata transfer system. The value MUST consist of Unicode characters. Alien-Species
Type (rdf:type) normative The subject is an instance of a class. bdqffdq:UseCase
Fitness Requirements (bdqffdq:hasFitnessRequirements) non-normative The property of a bdqffdq:UseCase that provides text listing the qualities that data must have to be fit for a given use. Data are fit for this use when occurrence records can be reliably interpreted for alien-species management: the organism identity, observation status, and establishment context are present and standard.
  • Organism identity is usable: Taxon/scientific name terms (e.g., dwc:scientificName, related dwc:Taxon terms, and identifiers where provided) are present, resolvable to a taxonomic authority, and consistent.
  • Establishment context is usable: Terms defining the invasion status (dwc:establishmentMeans, dwc:degreeOfEstablishment, dwc:pathway) are present when relevant, valid and standard.
  • Observation Status is present in valid form to reliably distinguish between presence and absence records; dwc:occurrenceStatus is present, valid and standardizable.
  • Metadata context (dwc:basisOfRecord and dc:type) is present, valid, and standard so record meaning is consistent in downstream use.
Scope Note (skos:scopeNote) non-normative A note that helps to clarify the meaning and/or the use of a concept. Darwin Core Occurrences

2 Use of Terms (normative)

In an RDF context, a reference to a term in the bdquc: namespace MUST use the Term IRI (e.g., https://rs.tdwg.org/bdquc/terms/NotEmpty) or Term Qualified name (e.g., bdquc:NotEmpty). In a non-RDF context in which resources may be used by software (e.g., a value in a spreadsheet or database table) the Controlled Value String (local name, e.g., NotEmpty) SHOULD be used. In a purely human context a label (e.g., Not Empty) MAY be used.

3 Term index (non-normative)

3.1 Index By Term Name (non-normative)

(See also 3.2 Index By Label (non-normative))

Vocabulary

bdquc:Alien-Species | bdquc:SDM-Trees | bdquc:Spatial-Temporal_Patterns | bdquc:Taxon-Management

3.2 Index By Label (non-normative)

(See also 3.1 Index By Term Name (non-normative))

Alien-Species | Spatial-Temporal Patterns | Species-Distribution-Modeling-Trees | Taxon-Management

4 Vocabulary (normative)

Term Name bdquc:Alien-Species
Term IRI https://rs.tdwg.org/bdquc/terms/Alien-Species
Modified 2026-04-22
Term version IRI https://rs.tdwg.org/bdquc/terms/version/Alien-Species-2026-04-22
Label Alien-Species
Definition A bdqffdq:UseCase that involves the identification and analysis of whether the occurrence of a taxon is native to a location or not, how it got there and to what extent the taxon has become a permanent feature of the location in order to improve the management and reduce the spread of alien species.
Comments See Groom et al. (2019). Improving Darwin Core for research and management of alien species. Biodiversity Information Science and Standards, 3: e38084. https://doi.org/10.3897/biss.3.38084.
Fitness requirements Data are fit for this use when occurrence records can be reliably interpreted for alien-species management: the organism identity, observation status, and establishment context are present and standard.
  • Organism identity is usable: Taxon/scientific name terms (e.g., dwc:scientificName, related dwc:Taxon terms, and identifiers where provided) are present, resolvable to a taxonomic authority, and consistent.
  • Establishment context is usable: Terms defining the invasion status (dwc:establishmentMeans, dwc:degreeOfEstablishment, dwc:pathway) are present when relevant, valid and standard.
  • Observation Status is present in valid form to reliably distinguish between presence and absence records; dwc:occurrenceStatus is present, valid and standardizable.
  • Metadata context (dwc:basisOfRecord and dc:type) is present, valid, and standard so record meaning is consistent in downstream use.
Scope note Darwin Core Occurrences
Status recommended
Controlled value Alien-Species
Type bdqffdq:UseCase
Term Name bdquc:SDM-Trees
Term IRI https://rs.tdwg.org/bdquc/terms/version/SDM-Trees
Modified 2026-04-26
Term version IRI https://rs.tdwg.org/bdquc/terms/version/SDM-Trees-2026-04-26
Label Species-Distribution-Modeling-Trees
Definition A bdqffdq:UseCase for improving the quality of, and selecting dwc:Occurrence records suitable for predicting the spatial distribution of tree species. This Use Case filters for occurrence records that meet criteria for a known species at a known location and date. Records can be further filtered to meet the requirements of the predictive modeling of specific tree species distributions (e.g., Eucalypts) using high-precision occurrence data and environmental variables to evaluate modeling methodologies and refine expert distribution envelopes.
Comments References:
  • Gill, A.M., Belbin, L. and Chippendale, G.M. (1985). Phytogeography of EUCALYPTUS in Australia. Bureau of Flora and Fauna, Australian Flora and Fauna Series, 3. Canberra. 53p. ISBN: 0644040815.
  • Phillips, S. J., Anderson, R. P., and Schapire, R. E. (2006). Maximum entropy modeling of species geographic distributions. Ecological Modeling, 190(3-4), 231-259. 
  • Guisan, A. Edwards, T.C. and Hastie, T. (2002). Generalized linear and generalized additive models in studies of species distributions: setting the scene. Ecological Modeling 157, 89-100.
Fitness requirements Data are fit for the use case bdquc:Species-Distribution-Modeling-Trees when records have valid:
  • dwc:scientificName identified to species level.
  • dwc:basisOfRecord = "Occurrence".
  • dwc:occurrenceStatus = "present".
  • dwc:decimalLatitude and dwc:decimalLongitude.
  • dwc:coordinateUncertaintyInMeters less than 500.
  • dwc:dataGeneralizations = bdqval:empty.
  • dwc:year or dwc:eventDate within provided temporal limits.
Scope note Darwin Core Occurrences
Status recommended
Controlled value Species-Distribution-Modeling-Trees
Type bdqffdq:UseCase
Term Name bdquc:Spatial-Temporal_Patterns
Term IRI https://rs.tdwg.org/bdquc/terms/Spatial-Temporal_Patterns
Modified 2026-04-22
Term version IRI https://rs.tdwg.org/bdquc/terms/version/Spatial-Temporal_Patterns-2026-04-22
Label Spatial-Temporal Patterns
Definition A bdqffdq:UseCase that pertains to dwc:Occurrence data where the Information Elements concerning what dwc:Organism occurred when at what location are used for analysies such as of taxon distributions across space and time to quantify biodiversity patterns, identify range shifts, or modeling of ecological niches.
Comments See Rees ER and Nicholls M (2020) Data Quality Use Case Study Results. Biodiversity Information Science and Standards 4: e50889, suppl. 2. https://doi.org/10.3897/biss.4.50889.suppl2.
Fitness requirements Data are fit for the Use Case bdquc:Spatial-Temporal_Patterns when occurrence records can be reliably interpreted as organism occurrences in space and time: the organism identity is usable, the location is usable (with adequate precision and metadata), textual geography data is consistent with the coordinates, the event date is usable and internally consistent, and any generalization (spatial or temporal) is detectable so users can decide whether the record is fit at the intended analysis scale.
  • Organism identity is usable: Taxon and scientific name terms (e.g., dwc:scientificName and related taxon terms) are present and sufficiently resolvable and consistent to support analyses of spatio-temporal patterns of organisms.
  • Location is usable and interpretable (including precision and metadata): Coordinates are present, are in-range, and are accompanied by adequate spatial metadata (e.g., uncertainty and spatial reference such as datum); obvious artifact coordinates (e.g., zeros) are detectable.
  • Textual geography is coherent with coordinates: Textual geography fields (e.g., dwc:countryCode, dwc:country, dwc:stateProvince) are valid and standardizable and consistent with the coordinates.
  • Date is usable and internally consistent: dwc:eventDate is present, valid, in standard form and consistent with other temporal terms (e.g. dwc:year) terms when those are provided. Generalization and low precision are detectable: Any indication that the record has been generalized (via dwc:dataGeneralizations) is available along with coordinate uncertainty, broad and interval event dates, and taxonomic rank so that users can judge whether records are fit for the intended spatial and temporal resolution.
Scope note Darwin Core Occurrences
Status recommended
Controlled value Spatial-Temporal Patterns
Type bdqffdq:UseCase
Term Name bdquc:Taxon-Management
Term IRI https://rs.tdwg.org/bdquc/terms/Taxon-Management
Modified 2026-04-22
Term version IRI https://rs.tdwg.org/bdquc/terms/version/Taxon-Management-2026-04-22
Label Taxon-Management
Definition A bdqffdq:UseCase that involves the nomenclatural audit, taxonomic verification, and systematic organization of taxon names and associated metadata to ensure identification stability and compliance with global taxonomic standards.
Comments See Rees ER and Nicholls M (2020) Data Quality Use Case Study Results. Biodiversity Information Science and Standards 4: e50889, suppl. 2. https://doi.org/10.3897/biss.4.50889.suppl2.
Fitness requirements Data are fit for this use when when taxonomic information is sufficient to unambiguously determine which taxon is being referenced and to position it within a nomenclatural hierarchy. Taxon terms are sufficient to resolve an organism they may be applied to (or flag ambiguity), core name and rank terms (e.g., dwc:scientificName, dwc:taxonRank) are present and align with an appropriate bdqval:sourceAuthority, name strings are consistent with atomized name fields and identifiers or authorship.
  • Taxon can be resolved: Taxon terms are present and sufficient to support unambiguous resolution (dwc:scientificName, dwc:scientificNameAuthorship, dwc:scientificNameID).
  • Names and ranks are authoritative: dwc:scientificName and required rank and classification terms are present, standardizable, and consistent with the bdqval:sourceAuthority.
  • Name fields are consistent: dwc:scientificName agrees with atomized name fields; authorship is provided where needed.
  • Identifiers are usable: Identifiers (e.g., dwc:scientificNameID) are present when available and correctly formed; dwc:taxonRank is present and valid.
Scope note Darwin Core dwc:Taxon terms.
Status recommended
Controlled value Taxon-Management
Type bdqffdq:UseCase

Glossary (non-normative)

A glossary of acronyms and terms additional to those in the various namespaces can be found in the Glossary (non-normative) section of the Biodiversity Data Quality (BDQ) landing page.

References (non-normative)

The references for the BDQ standard can be found in the References (non-normative) section of the Biodiversity Data Quality (BDQ) landing page.

Cite BDQ (non-normative)

To cite BDQ in general, use the peer-reviewed article:

Chapman AD, Belbin L, Zermoglio PF, Wieczorek J, Morris PJ, Nicholls M, Rees ER, Veiga AK, Thompson A, Saraiva AM, James SA, Gendreau C, Benson A, Schigel D (2020). Developing Standards for Improved Data Quality and for Selecting Fit for Use Biodiversity Data. Biodiversity Information Science and Standards 4: e50889. https://doi.org/10.3897/biss.4.50889

To cite this document specifically, use the following:

TDWG Biodiversity Data Quality Interest Group Task Group 2: Data Quality Tests and Assertions. 2026. BDQ Use Case Controlled Vocabulary. Biodiversity Information Standards (TDWG). http://rs.tdwg.org/bdquc/terms/2026-06-03

Biodiversity Information Standards (TDWG)

This content made open by Biodiversity Information Standards (TDWG) is licensed under a Licensed under a Creative Commons Attribution 4.0 International (CC BY) License.