Fitness For Use Framework Ontology List of Terms

Title
Fitness For Use Framework Ontology List of Terms

Date version issued
2026-06-03

Date created
2025-05-10

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

Preferred namespace abbreviation
bdqffdq

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

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

Previous version

Abstract
This document is a reference for the BDQ standard, documenting vocabulary values in the Fitness For Use Framework Ontology, excluding additional axioms.

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. Fitness For Use Framework Ontology List of Terms. Biodiversity Information Standards (TDWG). http://rs.tdwg.org/bdqffdq/terms/2026-06-03

Status
Draft Standard for Review

1 Introduction (non-normative)
2 Use of Terms (normative)
3 Term index (non-normative)
4 Vocabulary (normative)

1 Introduction (non-normative)

1.1 Purpose (non-normative)

The purpose of this document is to provide the full term list for the bdqffdq: vocabulary, which defines the elements used in the Biodiversity Data Quality Fitness For Use Framework (Ontology). The vocabulary includes classes, object properties, data properties, and named individuals that collectively support the semantic description of BDQ Tests and related quality constructs.

1.2 Audience (non-normative)

This document is intended for technical users who need to reference the bdqffdq: vocabulary in detail. It is particularly useful for:

Ontology developers integrating BDQ concepts into semantic systems
Data quality analysts and system implementers interpreting or expressing BDQ Test structures using RDF/OWL
Standards developers needing access to term-level details when aligning or extending the Fitness For Use Framework.

Familiarity with RDF, OWL, and the structure of the BDQ Tests is recommended.

1.3 Associated Documents (non-normative)

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

Information about the bdqffdq: Fitness For Use Framework Ontology, its usage, and its extensions can be found in the following subset of BDQ resources:

Fitness For Use Framework Ontology: Concepts and Use - Provides a visual and narrative introduction to the concepts and application of the ontology along with normative guidance.
Fitness For Use Framework Ontology List of Terms - The term list document, which enumerates and describes the vocabulary terms (this document).
Fitness For Use Framework Ontology Vocabulary Extension - Defines additional axioms extending the core vocabulary.
Biodiversity Data Quality Fitness For Use Framework (Ontology) - The ontology, which provides the formal RDF/OWL representation of the vocabulary.

1.3.1 Distributions for bdqffdq: (non-normative)

Description	IRI	Download URL
Human Readable Term List	TBD	/docs/list/bdqffdq/index.md
Human Readable Vocabulary Extension	TBD	/docs/extension/bdqffdq/index.md
OWL Ontology	TBD	/vocabulary/bdqffdq.owl

1.4 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.7 Key to Vocabulary Terms (normative) identifies which values in Section 4 are normative and which are non-normative.

1.5 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.6 Namespace abbreviations (non-normative)

The following namespace abbreviations are used in this document:

Abbreviation	Namespace
bdqffdq:	https://rs.tdwg.org/bdqffdq/terms/
bdqtest:	https://rs.tdwg.org/bdqtest/terms/
bdqval:	https://rs.tdwg.org/bdqval/terms/
dcterms:	http://purl.org/dc/terms/
dcmitype:	http://purl.org/dc/dcmitype/
dwc:	http://rs.tdwg.org/dwc/terms/
mids:	http://rs.tdwg.org/mids/elements/ (draft)
oa:	http://www.w3.org/ns/oa#
owl:	http://www.w3.org/2002/07/owl#
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.7 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.	https://rs.tdwg.org/ bdqffdq/terms/ AbstractInformationElement
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/ bdqffdq/terms/ AbstractInformationElement
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/ bdqffdq/terms/ AbstractInformationElement
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.	Abstract Information Element
Definition (rdfs:comment)	normative	A description of the subject resource. TDWG SDS: The normative definition of the term, written in English.	A bdqffdq:InformationElement described in abstract terms and not linked with any concrete terms.
Comments (skos:note)	non-normative	A general note, for any purpose.	Such bdqffdq:InformationElements as DATE and DAY are abstract, they could reference any representation of those concepts. In contrast, dwc:eventDate and dwc:day can be linked to concrete bdqffdq:ActedUponInformationElements or bdqffdq:ConsultedInformationElements. A MIDS Information Element such as mids:Chronostratigraphy corresponds to a bdqffdq:AbstractInformationElement.
Type (rdf:type)	normative	The subject is an instance of a class.	http://www.w3.org/2002/07/ owl#Class
Scope Note (skos:scopeNote)	non-normative	A note that helps to clarify the meaning and/or the use of a concept.

2 Use of Terms (normative)

In an RDF context, a reference to a term in the bdqffdq: namespace MUST use the Term IRI (e.g., https://rs.tdwg.org/bdqffdq/terms/InformationElement) or Term Qualified name (e.g., bdqffdq:InformationElement). 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., InformationElement) SHOULD be used. In a purely human context a label (e.g., Information Element) MAY be used.

3.1 Alphabetical Index of classes (non-normative)

3.2 Alphabetical Index of object properties (non-normative)

3.3 Alphabetical Index of data properties (non-normative)

3.4 Alphabetical Index of named individuals (non-normative)

4 Vocabulary (normative)

4.1 Class terms (normative)

AbstractInformationElement

Name: bdqffdq:AbstractInformationElement
Preferred Label: Abstract Information Element
Definition: A bdqffdq:InformationElement described in abstract terms and not linked with any concrete terms.
SubClass Of: InformationElement
Comments: Such bdqffdq:InformationElements as DATE and DAY are abstract, they could reference any representation of those concepts. In contrast, dwc:eventDate and dwc:day can be linked to concrete bdqffdq:ActedUponInformationElements or bdqffdq:ConsultedInformationElements. A MIDS Information Element such as mids:Chronostratigraphy corresponds to a bdqffdq:AbstractInformationElement.

ActedUpon

Name: bdqffdq:ActedUpon
Preferred Label: Acted Upon
Definition: A bdqffdq:InformationElement, expressed in concrete terms, about which a bdqffdq:DataQualityNeed expresses bdqffdq:Responses about the data quality in that bdqffdq:InformationElement.
SubClass Of: InformationElement
Comments: A bdqffdq:InformationElement to which a bdqffdq:ResponseResult applies.

Amendment

Name: bdqffdq:Amendment
Preferred Label: Amendment
Definition: A bdqffdq:DataQualityNeed that expresses how proposals may be made to improve the fitness for use of data.
SubClass Of: AmendmentConcept; DataQualityNeed
Comments: ContextualizedEnhancement in the original framework. Describes an instance of a bdqffdq:Enhancement in the context of the associated bdqffdq:InformationElements from a controlled vocabulary (fields bdqffdq:ActedUpon or bdqffdq:Consulted), and a bdqffdq:ResourceType of bdqffdq:SingleRecord or bdqffdq:MultiRecord.
Describes a proposal for a bdqffdq:Enhancement of original data, which if accepted, would improve the quality of the data for a use. For example: 'Recommends valid value for taxon name in a Single Record.'
bdqffdq:Amendments may describe proposed changes to data values, or proposed changes to processes for the production and manipulation of data, for example, a bdqffdq:Amendment on a bdqffdq:SingleRecord may provide bdqffdq:Criteria for proposing that dwc:decimalLatitude and dwc:decimalLongitude are transposed in that record. Similarly, a bdqffdq:Amendment on a bdqffdq:MultiRecord may provide bdqffdq:Critera for proposing that all dwc:decimalLatitudes and dwc:decimalLongitudes from a data source have been transposed, and the mapping of data values to transport terms should be changed.
A bdqffdq:Amendment is the bdqffdq:DataQualityNeed that parallels a bdqffdq:AmendmentMethod in the Solutions layer (see Figure 3 in Veiga et al., 2017), and a bdqffdq:AmendmentResponse in the Report layer (see Figure 3 in Veiga et al., 2017).
AM = { am | am = < ie, e, d, rt >, ie ∈ IE, e ∈ E, d ∈ D ⋀ rt ∈ RT }

AmendmentConcept

Name: bdqffdq:AmendmentConcept
Preferred Label: Amendment Concept
Definition: A term involved in proposals of changes to data or process to improve data quality to fit an expressed bdqffdq:DataQualityNeed.
Comments:

AmendmentMethod

Name: bdqffdq:AmendmentMethod
Preferred Label: Amendment Method
Definition: A data quality bdqffdq:SolutionsConcept that relates a bdqffdq:Amendment to its bdqffdq:Specifications.
SubClass Of: AmendmentConcept; DataQualityMethod
Comments: The bdqffdq:AmendmentMethod is a bdqffdq:DataQualityMethod describing the relationship between a bdqffdq:Specification (technical description of a Test) and a bdqffdq:Amendment (a bdqffdq:Enhancement in the context of bdqffdq:ResourceType (bdqffdq:SingleRecord or bdqffdq:MultiRecord) and associated bdqffdq:InformationElements).
AMM(am) = { s | s ∈ S ⋀ (am, s) ∈ rel_AMM }

AmendmentPolicy

Name: bdqffdq:AmendmentPolicy
Preferred Label: Amendment Policy
Definition: A bdqffdq:NeedConcept that relates a bdqffdq:UseCase to a set of supporting bdqffdq:Amendments.
SubClass Of: AmendmentConcept; Policy
Comments: A data quality Need layer concept (see Figure 3 in Veiga et al., 2017) that describes how a bdqffdq:Amendment relates to a bdqffdq:UseCase. This relationship defines which bdqffdq:Amendments are supported by a given bdqffdq:UseCase.
AP(u) = { am | am ∈ AM ⋀ (u, am) ∈ rel_AP }

AmendmentResponse

Name: bdqffdq:AmendmentResponse
Preferred Label: Amendment Response
Definition: A bdqffdq:Response expressing the result of a bdqffdq:Implementation evaluating a bdqffdq:Amendment supporting a particular bdqffdq:DataQualityNeed to improve a particular bdqffdq:DataResource.
SubClass Of: AmendmentConcept; Response
Comments: The bdqffdq:AmendmentResponse type is a Report layer concept (see Figure 3 in Veiga et al., 2017) that describes the results of the execution of a Test that performs a bdqffdq:AmendmentMethod following a bdqffdq:Specification to propose changes based on a bdqffdq:Amendment.
A bdqffdq:AmendmentResponse is expected to carry, through bdqffdq:hasResponseStatus, a bdqffdq:ResponseStatus result that includes a status bdqffdq:FILLED_IN or bdqffdq:AMENDED, as well as a bdqffdq:hasResponseResultValue that asserts proposed changes to values from the original data.
DQA(dr) = { dqa | dqa ∈ RespA ⋀ (dr, dqa) ∈ rel_DQA }

Argument

Name: bdqffdq:Argument
Preferred Label: Argument
Definition: A value that, when provided to a Test bdqffdq:Specification to replace a bdqffdq:Parameter changes the behavior of the Test in a defined manner.
SubClass Of: SolutionsConcept
Comments: The bdqffdq:Argument is an Actual Parameter, for which a bdqffdq:Parameter is the corresponding Formal Parameter. An extension to the original fitness for use framework as described in Veiga et al., 2017.

Consulted

Name: bdqffdq:Consulted
Preferred Label: Consulted
Definition: A bdqffdq:InformationElement, expressed in concrete terms, about which a bdqffdq:DataQualityNeed examines in order to expresses bdqffdq:Responses about the data quality in another bdqffdq:InformationElement.
SubClass Of: InformationElement
Comments: A bdqffdq:InformationElement the content of which is examined to assert a result on one or more other bdqffdq:InformationElements.

Criterion

Name: bdqffdq:Criterion
Preferred Label: Criterion
Definition: Rule against which data are evaluated for conformance to quality bdqffdq:Criteria.
SubClass Of: FundamentalConcept; NeedConcept
Comments: General statement, for example, 'In a controlled vocabulary.' Composed with both bdqffdq:Validations and bdqffdq:Issues.

DataQualityDimension

Name: bdqffdq:DataQualityDimension
Preferred Label: Data Quality Dimension
Definition: An aspect of data quality.
SubClass Of: FundamentalConcept; NeedConcept
Comments: Describes the aspect of data quality (accuracy, precision, completeness, etc.) that a Test examines. For example, [precision] in [coordinate precision of Single Records]. In the original framework, only related to Measures, here may be related to any bdqffdq:DataQualityNeed.

DataQualityMethod

Name: bdqffdq:DataQualityMethod
Preferred Label: Data Quality Method
Definition: A bdqffdq:SolutionsConcept that relates a bdqffdq:DataQualityNeed to a bdqffdq:Specification.
SubClass Of: SolutionsConcept
Comments: A bdqffdq:DataQualityMethod is an associative entity that allows bdqffdq:Specifications or data quality Tests to be reused by supporting a many-to-many relationship between the two.

DataQualityNeed

Name: bdqffdq:DataQualityNeed
Preferred Label: Data Quality Need
Definition: A bdqffdq:NeedConcept that expresses what bdqffdq:Responses may be made about data with respect to fitness for use.
SubClass Of: NeedConcept
Comments: Subtypes of bdqffdq:DataQualityNeed are the Test Types (Validation, Issue, Measure, and Amendment). The bdqffdq:DataQualityNeed appoximates the informal concept of a Test as used in the BDQ standard.

DataQualityProfile

Name: bdqffdq:DataQualityProfile
Preferred Label: Data Quality Profile
Definition: A bdqffdq:NeedConcept expressing the composition of bdqffdq:Policies to satisfy a bdqffdq:UseCase.
SubClass Of: NeedConcept
Comments: The bdqffdq:DataQualityProfile is a data quality Need layer concept (see Figure 3 in Veiga et al., 2017) describing the bdqffdq:UseCases that make up a data quality operation such as the behavior of a single actor or workflow producing the relevant bdqffdq:Responses.
DQP(u) = MP(u) ⋃ VP(u) ⋃ ISP(u) ⋃ AP(u), where u ∈ U

DataQualityReport

Name: bdqffdq:DataQualityReport
Preferred Label: Data Quality Report
Definition: A bdqffdq:ReportConcept comprising a set of data quality bdqffdq:Responses.
SubClass Of: ReportConcept
Comments: A bdqffdq:DataQualityReport consists of a set of bdqffdq:Responses (bdqffdq:ValidationResponses, bdqffdq:IssueResponses, bdqffdq:MeasurementResponses, and bdqffdq:AmendmentResponses) pertaining to a bdqffdq:DataResource that represent the output of a workflow/actor run. These bdqffdq:Responses form an account of the fitness for use of a tested data set for a specified bdqffdq:UseCase, as produced by a bdqffdq:Mechanism.

DataResource

Name: bdqffdq:DataResource
Preferred Label: Data Resource
Definition: An owl:Thing to which a data quality bdqffdq:Response applies.
SubClass Of: ReportConcept
Comments: Describes a bdqffdq:DataResource containing terms from a vocabulary such as Darwin Core that can be related to bdqffdq:InformationElements, and represents the original values of the data operated on by a bdqffdq:Response Test (e.g., an instance of dwc:Occurrence). Ideally, bdqffdq:DataResources have persistent GUIDs.
A bdqffdq:DataResource could be the oa:target of a oa:Annotation of which a bdqffdq:Response is the oa:body.
DR = { dr | dr = < id, rt, v >, id ∈ ID, rt ∈ RT ⋀ v ∈ V }

Enhancement

Name: bdqffdq:Enhancement
Preferred Label: Enhancement
Definition: Description of a means by which data could be improved.
SubClass Of: AmendmentConcept; FundamentalConcept; NeedConcept
Comments: A general statement about improvement, for example, 'Recommend replacement value from a controlled vocabulary'.

FundamentalConcept

Name: bdqffdq:FundamentalConcept
Preferred Label: Fundamental Concept
Definition: Category of fitness for use concepts that are not derived by composition with other concepts.
Comments: Contrast with derived concepts, which are compositions of two or more bdqffdq:FundamentalConcepts, see Veiga et al., 2017. Derived concepts can be organized by Test type into bdqffdq:ValidationConcept, bdqffdq:IssueConcept, bdqffdq:MeasurementConcept, or bdqffdq:AmendmentConcept. Derived concepts can also be organized by framework layer into bdqffdq:NeedConcept, bdqffdq:SolutionsConcept, and bdqffdq:ReportConcept (see Figure 3 in Veiga et al., 2017).

Implementation

Name: bdqffdq:Implementation
Preferred Label: Implementation
Definition: A bdqffdq:SolutionsConcept that describes the portion of a bdqffdq:Mechanism that carries out the proccess described in a particular bdqffdq:Specification.
SubClass Of: SolutionsConcept
Comments: A bdqffdq:Implementation describes the relationship between a bdqffdq:Specification (technical description of a Test) and the bdqffdq:Mechanism that implements it.
I(s) = { m | m ∈ M ⋀ (s, m) ∈ rel_I }

ImprovementTarget

Name: bdqffdq:ImprovementTarget
Preferred Label: Improvement Target
Definition: A specific bdqffdq:DataQualityNeed that a specific bdqffdq:Amendment is intended to improve.
SubClass Of: NeedConcept
Comments: A bdqffdq:ImprovementTarget describes which bdqffdq:Validations, bdqffdq:Issues, and bdqffdq:Measures are improved by a bdqffdq:Amendment. The bdqffdq:ImprovementTarget includes relationships between a bdqffdq:Amendment and one or more bdqffdq:Validations or bdqffdq:Measures.
IT(am) = { x | (x ∈ ME ⋁ x ∈ VA ⋁ x ∈ IS) ⋀ (am, x) ∈ rel_IT }

InformationElement

Name: bdqffdq:InformationElement
Preferred Label: Information Element
Definition: A portion of data with which a bdqffdq:DataQualityNeed is concerned.
SubClass Of: FundamentalConcept
Comments: A bdqffdq:InformationElement identifies a portion of data to which a Test pertains. A bdqffdq:InformationElement can be represented as a single or composite element that consists of one or more terms from a controlled vocabulary (fields bdqffdq:ActedUpon or bdqffdq:Consulted by a bdqffdq:Response Test) that identifies concepts in data relevant to a bdqffdq:UseCase. An abstraction or a concrete term that represents relevant content (e.g., coordinates; dwc:decimalLatitude, dwc:decimalLongitude).

Issue

Name: bdqffdq:Issue
Preferred Label: Issue
Definition: A bdqffdq:DataQualityNeed that expresses how quality problems may be identified in data.
SubClass Of: DataQualityNeed; IssueConcept
Comments: Added to the original framework. Inverse of ContextualizedCriterion in the original framework. Describes an instance of the bdqffdq:IssueConcept in terms of the associated bdqffdq:InformationElements from a controlled vocabulary (fields bdqffdq:ActedUpon or bdqffdq:Consulted), and a bdqffdq:ResourceType of bdqffdq:SingleRecord or bdqffdq:MultiRecord. Describes bdqffdq:Criteria by which data that lack quality for some purpose may be identified. A bdqffdq:Issue is phrased in a negative sense, and approximates an inverse of a bdqffdq:Validation. A bdqffdq:Issue identifies data that lack or may lack quality. A bdqffdq:Issue may flag a bdqffdq:POTENTIAL_ISSUE that would need further review to determine if the data have quality for some purpose. If the conditions described by a bdqffdq:Issue are identified by a Test, the bdqffdq:ResponseResult will be either bdqffdq:IS_ISSUE or bdqffdq:POTENTIAL_ISSUE, if no bdqffdq:Issue is found with the data, the bdqffdq:ResponseResult will be bdqffdq:NOT_ISSUE. The term bdqffdq:NOT_ISSUE, unlike bdqffdq:COMPLIANT for a bdqffdq:Validation, does not assert that data are fit for some purpose. A bdqffdq:Issue is the bdqffdq:DataQualityNeed concept that parallels a bdqffdq:IssueMethod in the Solutions layer (see Figure 3 in Veiga et al., 2017), and a bdqffdq:IssueResponse in the Report layer (see Figure 3 in Veiga et al., 2017).
IS = { is | is = < ie, c, d, rt >, ie ∈ IE, c ∈ C, d ∈ D ⋀ rt ∈ RT }

IssueConcept

Name: bdqffdq:IssueConcept
Preferred Label: Issue Concept
Definition: A term involved in flagging problems or potential problems in assessment of data quality that would or might prevent the data from meeting an expressed bdqffdq:DataQualityNeed.
Comments: A bdqffdq:Issue term is expressed in a negative sense, it identifies data that do not or may not conform to bdqffdq:DataQualityNeeds.

IssueMethod

Name: bdqffdq:IssueMethod
Preferred Label: Issue Method
Definition: A data quality bdqffdq:SolutionsConcept that relates a bdqffdq:Issue to its bdqffdq:Specifications.
SubClass Of: DataQualityMethod; IssueConcept
Comments: A bdqffdq:IssueMethod is a data quality Solutions layer concept (see Figure 3 in Veiga et al., 2017) describing the relationship between a bdqffdq:Specification (technical description of a Test) and a bdqffdq:Issue (a bdqffdq:Criterion in the context of bdqffdq:ResourceType (bdqffdq:SingleRecord or bdqffdq:MultiRecord) and associated bdqffdq:InformationElements). ISM(is) = { s | s ∈ S ⋀ (is, s) ∈ rel_ISM }

IssuePolicy

Name: bdqffdq:IssuePolicy
Preferred Label: Issue Policy
Definition: A bdqffdq:NeedConcept that relates a bdqffdq:UseCase to a set of supporting bdqffdq:Issues.
SubClass Of: IssueConcept; Policy
Comments: A bdqffdq:IssuePolicy is a data quality Need layer concept (see Figure 3 in Veiga et al., 2017) that describes how a bdqffdq:Issue relates to a bdqffdq:UseCase. This relationship defines which bdqffdq:Issues are supported by a given bdqffdq:UseCase. ISP(u) = { is | is ∈ IS ⋀ (u, is) ∈ rel_ISP }

IssueResponse

Name: bdqffdq:IssueResponse
Preferred Label: Issue Response
Definition: A bdqffdq:Response expressing the result of a bdqffdq:Implementation evaluating a bdqffdq:Issue for a particular bdqffdq:DataQualityNeed in a particular bdqffdq:DataResource.
SubClass Of: IssueConcept; Response
Comments: The bdqffdq:DataQualityReport concept describing the output of a Test in the negative (i.e., identifying the potential absence of data quality).
If a problem was found, the bdqffdq:IssueResponse is expected to carry, through bdqffdq:hasResponseResult, a bdqffdq:ResponseResult value of bdqffdq:IS_ISSUE, if a potential problem was found that requires human review, the bdqffdq:ResponseResult is expected to be bdqffdq:POTENTIAL_ISSUE, otherwise if the bdqffdq:ResponseStatus is bdqffdq:RUN_HAS_RESULT, the bdqffdq:ResponseResult is expected to be bdqffdq:NOT_ISSUE.
DQI(dr) = { dqi | dqi ∈ RespI ⋀ (dr, dqi) ∈ rel_DQI }

Measure

Name: bdqffdq:Measure
Preferred Label: Measure
Definition: A bdqffdq:DataQualityNeed that expresses how the fitness of data for some use may be measured.
SubClass Of: DataQualityNeed; MeasurementConcept
Comments: ContextualizedDimension in the original framework. Describes an instance of the bdqffdq:MeasurementConcept in terms of the associated bdqffdq:InformationElements from a controlled vocabulary (fields bdqffdq:ActedUpon or bdqffdq:Consulted), and a bdqffdq:ResourceType of bdqffdq:SingleRecord or bdqffdq:MultiRecord.
Describes the bdqffdq:Criteria for measuring an aspect of data quality related to a bdqffdq:DataQualityNeed. May be bdqffdq:Criteria for determining that data are bdqffdq:COMPLETE or bdqffdq:NOT_COMPLETE, or may be bdqffdq:Criteria for asserting a numeric bdqffdq:Measure. The bdqffdq:COMPLETE and bdqffdq:NOT_COMPLETE bdqffdq:Measures are fundamental to data quality control, as a set of data is filtered to the subset of data that have quality for some need if all records are bdqffdq:COMPLETE for all pertinent bdqffdq:Measures.
A bdqffdq:Measure is the bdqffdq:DataQualityNeed concept that parallels a bdqffdq:MeasurementMethod in the Solutions layer (see Figure 3 in Veiga et al., 2017), and a bdqffdq:MeasurementResponse in the Report layer (see Figure 3 in Veiga et al., 2017).
ME = { me | me = < ie, d, rt >, ie ∈ IE, d ∈ D ⋀ rt ∈ RT }
also acceptable bdqffdq:Measure
MEaq(u) = { me | me ∈ ME ⋀ me ∈ MP(u) ⋀ u ∈ U ⋀ resultType(me) = categorical }

MeasurementConcept

Name: bdqffdq:MeasurementConcept
Preferred Label: Measurement Concept
Definition: A term involved in measurement of data quality with regards to expressed bdqffdq:DataQualityNeed.
Comments:

MeasurementMethod

Name: bdqffdq:MeasurementMethod
Preferred Label: Measurement Method
Definition: A data quality bdqffdq:SolutionsConcept that relates a bdqffdq:Measure to its bdqffdq:Specifications.
SubClass Of: DataQualityMethod; MeasurementConcept
Comments: A bdqffdq:MeasurementMethod is a data quality Solutions layer concept (see Figure 3 in Veiga et al., 2017) describing the relationship between a bdqffdq:Specification (technical description of a Test) and a bdqffdq:Measurement (a bdqffdq:DataQualityDimension in the context of bdqffdq:ResourceType (bdqffdq:SingleRecord or bdqffdq:MultiRecord) and associated bdqffdq:InformationElements).
MM(me) = { s | s ∈ S ⋀ (me, s) ∈ rel_MM }

MeasurementPolicy

Name: bdqffdq:MeasurementPolicy
Preferred Label: Measurement Policy
Definition: A bdqffdq:NeedConcept that relates a bdqffdq:UseCase to a set of supporting bdqffdq:Measures.
SubClass Of: MeasurementConcept; Policy
Comments: A bdqffdq:MeasurementPolicy is a data quality Need layer concept (see Figure 3 in Veiga et al., 2017) that describes how a bdqffdq:Measurement relates to a bdqffdq:UseCase. This relationship defines which bdqffdq:Measures are supported by a given bdqffdq:UseCase.
MP(u) = { me | me ∈ ME ⋀ (u, me) ∈ rel_MP }

MeasurementResponse

Name: bdqffdq:MeasurementResponse
Preferred Label: Measurement Response
Definition: A bdqffdq:Response expressing the result of a bdqffdq:Implementation measuring a particular bdqffdq:DataQualityNeed in a particular bdqffdq:DataResource.
SubClass Of: MeasurementConcept; Response
Comments: A bdqffdq:MeasurementResponse is a Report layer concept (see Figure 3 in Veiga et al., 2017) that describes the output of the execution of a Test that performs a bdqffdq:MeasurementMethod following a bdqffdq:Specification to assess a data quality bdqffdq:Measure.
A MeasuremenResponse is expected to carry a bdqffdq:ResponseResult, through bdqffdq:hasResponseResult of bdqffdq:COMPLETE or bdqffdq:NOT_COMPLETE or a numeric measured value (e.g., a bdqffdq:Measure of a dwc:eventDate duration in seconds).
DQM(dr) = { dqm | dqm ∈ RespM ⋀ (dr, dqm) ∈ rel_DQM }

Mechanism

Name: bdqffdq:Mechanism
Preferred Label: Mechanism
Definition: An entity that can execute bdqffdq:DataQualityMethods.
SubClass Of: FundamentalConcept; SolutionsConcept
Comments: A bdqffdq:Mechanism may produce bdqffdq:DataQualityReports as products.
A bdqffdq:Mechanism describes the entity that performs a bdqffdq:Response Test (code, external service, actor, etc.). Tied to a bdqffdq:Specification via the concept of a bdqffdq:Implementation.

NeedConcept

Name: bdqffdq:NeedConcept
Preferred Label: Need Concept
Definition: A concept that expresses an aspect of a bdqffdq:DataQualityNeed.
Comments: Category of concepts forming the Need layer of the fitness for use framework (see Figure 3 in Veiga et al., 2017).

Parameter

Name: bdqffdq:Parameter
Preferred Label: Parameter
Definition: A placeholder for a value that, when provided to a Test bdqffdq:Specification changes the behavior of the Test in a defined manner.
SubClass Of: SolutionsConcept
Comments: A bdqffdq:Parameter is a Formal Parameter for which an bdqffdq:Argument is an Actual Parameter that replaces it to determine the behavior of a bdqffdq:Specification. An extension to the original fitness for use framework as described in Veiga et al., 2017.

Policy

Name: bdqffdq:Policy
Preferred Label: Policy
Definition: The set of bdqffdq:DataQualityNeeds for a bdqffdq:UseCase.
SubClass Of: NeedConcept
Comments: Composition of bdqffdq:DataQualityNeeds into a bdqffdq:UseCase.

QualityAssurance

Name: bdqffdq:QualityAssurance
Preferred Label: Quality Assurance
Definition: The process of evaluating data for fitness for some use and selecting just those data that are fit for that use. This includes, in BDQ, the operation of filtering a bdqffdq:MultiRecord bdqffdq:DataResource for a specified bdqffdq:Use Case to retain only the data subset where every associated bdqffdq:MultiRecord bdqffdq:Measure that evaluates as COMPLETE/NOT_COMPLETE has a Response.result of COMPLETE, signifying that all contained records are fit for use for the specified bdqffdq:UseCase.
SubClass Of: FundamentalConcept
Comments: The output of a BDQ Quality Assurance operation is a set of records (a MultiRecord). The records contained in a data set filtered for Quality Assurance will comply with the fitness criteria for the given Use Case, this may include accepting changes proposed by Amendments to the data. QA(dr, u) = { dr' | dr' ∈ DR ⋀ dr'.rt = ds ⋀ records(dr') ⊆ records(dr) ⋀ dr ∈ DR ⋀ dr.rt = ds ⋀ u ∈ U ⋀ ∀ me ∈ MEaq(u), ∃ dqm ∈ DQM(dr') ( need(dqm) = me ⋀ result(dqm) = COMPLETE ) }
Scope Note: This concept of Quality Assurance encompasses Check and Act phases of Plan, Do, Check, Act of Shewhart (1939).

QualityControl

Name: bdqffdq:QualityControl
Preferred Label: Quality Control
Definition: The process of identifying data that are not fit for particular uses, with the goal of improving the data quality. This includes in BDQ the operation on a bdqffdq:DataQualityReport for a specified bdqffdq:UseCase that yields the filtered subset Responses in that report required to diagnose, prioritize, and remediate detected data quality defects for that Use Case.
SubClass Of: FundamentalConcept
Comments: The output of a BDQ Quality Control operation is a set of assertions about a data set (a MultiRecord) under test. BDQ does not specify how or whether consumers of Data Quality Reports act to improve their data, conceptually the actions of actually improving the data are included in Quality Control. QC(dr, u) = { x ∈ A(dr) | (x ∈ DQV(dr) ⋀ need(x) ∈ VP(u) ⋀ result(x) = NOT_COMPLIANT) ⋁ (x ∈ DQA(dr) ⋀ need(x) ∈ AP(u) ⋀ status(x) ∈ {FILLED_IN, AMENDED}) ⋁ (x ∈ DQI(dr) ⋀ need(x) ∈ ISP(u) ⋀ result(x) ∈ {IS_ISSUE, POTENTIAL_ISSUE}) ⋁ (x ∈ DQM(dr) ⋀ need(x) ∈ MP(u) ⋀ resultType(x) = numeric) }
Scope Note: This concept of Quality Control encompasses Check and Act phases of Plan, Do, Check Act of Shewhart (1939).

ReportConcept

Name: bdqffdq:ReportConcept
Preferred Label: Report Concept
Definition: A concept concerning data quality expressed in a bdqffdq:DataQualityReport.
Comments: Category of concepts forming the Report layer of the fitness for use framework (see Figure 3 in Veiga et al., 2017).

ResourceType

Name: bdqffdq:ResourceType
Preferred Label: Resource Type
Definition: Category of things that are data objects about which data quality bdqffdq:Responses may be made.
SubClass Of: FundamentalConcept
Comments: The concept of bdqffdq:ResourceType has instances for bdqffdq:SingleRecord or bdqffdq:MultiRecord.

Response

Name: bdqffdq:Response
Preferred Label: Response
Definition: A bdqffdq:ReportConcept produced by a bdqffdq:Implementation expressing a statement about data quality resulting from the application of the logic of a bdqffdq:Specification to a bdqffdq:DataResource.
SubClass Of: ReportConcept
Comments: The bdqffdq:Response type is the bdqffdq:FundamentalConcept that makes up a bdqffdq:DataQualityReport. A bdqffdq:Response can be any one of four types (represented as subclasses), bdqffdq:ValidationResponse, bdqffdq:IssueResponse, bdqffdq:MeasurementResponse, and bdqffdq:AmendmentResponse. The bdqffdq:Response concept relates a bdqffdq:Specification (the technical description of a performed Test), a bdqffdq:DataResource (initial values of input data expressed in terms of a controlled vocabulary), the bdqffdq:Mechanism (external service, actor, or code that performs the Test), and represents the output of the performed Test. Response was called Response in the original formulation of the Framework.

ResponseQualifier

Name: bdqffdq:ResponseQualifier
Preferred Label: Response Qualifier
Definition: A bdqffdq:ReportConcept to which additional bdqffdq:Responses providing additional information beyond that of bdqffdq:ResponseResult from the execution of the bdqffdq:Specification of a bdqffdq:DataQualityNeed are attached.
SubClass Of: ReportConcept
Comments: Intended as an extension point for qualifying information about uncertainty or ambiguity.

ResponseResult

Name: bdqffdq:ResponseResult
Preferred Label: Response.result
Definition: A bdqffdq:ReportConcept to which controlled vocabulary bdqffdq:Responses about the result of the execution of the bdqffdq:Specification of a bdqffdq:DataQualityNeed are attached.
SubClass Of: ReportConcept
Comments: For a bdqffdq:Validation, a bdqffdq:ResponseResult may be bdqffdq:COMPLIANT, or bdqffdq:NOT_COMPLIANT. For a bdqffdq:Measure, a bdqffdq:ResponseResult object may be bdqffdq:COMPLETE or bdqffdq:NOT_COMPLETE. For a bdqffdq:Issue, a bdqffdq:ResponseResult may be bdqffdq:IS_ISSUE, bdqffdq:POTENTIAL_ISSUE, or bdqffdq:NOT_ISSUE. A bdqffdq:Measure may also use a numeric data property. A bdqffdq:Amendment asserts a string data property.
The bdqffdq:ResponseResult is represented as a value or a result object for bdqffdq:MeasureAsssertions, or just a result object for bdqffdq:ValidationResponses or just values for changes proposed in bdqffdq:AmendmentResponses.

ResponseStatus

Name: bdqffdq:ResponseStatus
Preferred Label: Response.status
Definition: A bdqffdq:ReportConcept expressing controlled vocabulary values about the exit state of an execution process of a data quality bdqffdq:Specification by a bdqffdq:Implementation.
SubClass Of: ReportConcept
Comments: The bdqffdq:ResponseStatus is metadata, indicating if data should be present in a bdqffdq:ResponseResult. Any bdqffdq:Response may have the values bdqffdq:INTERNAL_PREREQUISITES_NOT_MET or bdqffdq:EXTERNAL_PREREQUISITES_NOT_MET, indicating that no value would be present in the accompanying bdqffdq:ResponseResult. Other values depend on the bdqffdq:Response type; bdqffdq:RUN_HAS_RESULT for a bdqffdq:Validation, bdqffdq:Issue or bdqffdq:Measure, and bdqffdq:FILLED_IN, bdqffdq:AMENDED, or bdqffdq:NOT_AMENDED for a bdqffdq:Amendment. Additional metadata qualifying the bdqffdq:Response in a bdqffdq:ResponseResult, such as statements of uncertainy or ambiguity may be placed in the bdqffdq:ResponseQualifier.

SolutionsConcept

Name: bdqffdq:SolutionsConcept
Preferred Label: Solutions Concept
Definition: A concept that expresses an aspect of a data quality solution.
Comments: Category of concepts forming the Solutions layer of the fitness for use framework (see Figure 3 in Veiga et al., 2017). A bdqffdq:SolutionsConcept is a tool that evaluates data against bdqffdq:NeedConcepts and express conclusions in bdqffdq:DataQualityReports.

Specification

Name: bdqffdq:Specification
Preferred Label: Specification
Definition: A specific statement about how to evaluate a bdqffdq:DataQualityNeed.
SubClass Of: FundamentalConcept; SolutionsConcept
Comments: A bdqffdq:Specification is a technical description of a bdqffdq:Response Test. A bdqffdq:Specification is expected to have the following properties: (1) bdqffdq:hasExpectedResponse and (2) bdqffdq:hasAuthoritiesDefaults.

UseCase

Name: bdqffdq:UseCase
Preferred Label: Use Case
Definition: A bdqffdq:NeedConcept expressing a purpose to which data are put for which the data must have quality for the result to have meaning and reliability.
SubClass Of: FundamentalConcept; NeedConcept
Comments: A bdqffdq:UseCase describes a purpose or use for which data must have quality. The bdqffdq:ValidationPolicies, bdqffdq:MeasurementPolicies and bdqffdq:AmendmentPolicies that make up a bdqffdq:UseCase define which bdqffdq:Responses cover a given bdqffdq:UseCase. An example of a bdqffdq:UseCase could be 'Check for internal consistency of dates', with bdqffdq:ValidationPolicies for checking consistency between atomic date fields and a bdqffdq:Amendment such as 'eventDate filled in from verbatim'. A bdqffdq:UseCase is not the same as a use cases in the software engineering sense, but is similar in that it is a formal bdqffdq: statement derived from analyis of user stories concerning data use. A bdqffdq:UseCase is expected to have a bdqffdq:hasFitnessRequirements property.

Validation

Name: bdqffdq:Validation
Preferred Label: Validation
Definition: A bdqffdq:DataQualityNeed that expresses how data may be evaluated for fitness for use.
SubClass Of: DataQualityNeed; ValidationConcept
Comments: ContextualizedCriterion in the original framework. Describes the bdqffdq:Criteria for determining compliance of data to fill a bdqffdq:DataQualityNeed. A description of a bdqffdq:Criterion applied to a bdqffdq:InformationElement for a bdqffdq:ResourceType. Describes an instance of a bdqffdq:Criterion in terms of the associated bdqffdq:InformationElements from a controlled vocabulary (fields bdqffdq:ActedUpon or bdqffdq:Consulted), and a bdqffdq:ResourceType of bdqffdq:SingleRecord or bdqffdq:MultiRecord.
A bdqffdq:Validation is phrased in a positive sense. It identifies data which have quality for some need. For example, the value of dwc:basisOfRecord of bdqffdq:SingleRecords must be in the controlled vocabulary for dwc:basisOfRecord.
A bdqffdq:Validation is the bdqffdq:DataQualityNeed that parallels a bdqffdq:ValidationMethod in the Solutions layer (see Figure 3 in Veiga et al., 2017), and a bdqffdq:ValidationResponse in the Report layer (see Figure 3 in Veiga et al., 2017). A bdqffdq:ValidationResponse may specify a result that is bdqffdq:COMPLIANT, where the data have quality, or bdqffdq:NOT_COMPLIANT, where the data lack quality for a bdqffdq:UseCase.
VA = { va | va = < ie, c, d, rt >, ie ∈ IE, c ∈ C, d ∈ D ⋀ rt ∈ RT }

ValidationConcept

Name: bdqffdq:ValidationConcept
Preferred Label: Validation Concept
Definition: A term involved in statements about the conformance of data to expressed bdqffdq:DataQualityNeeds.
Comments: A bdqffdq:Validation term is expressed in a positive sense, it identifies data that conform to a bdqffdq:NeedConcept.

ValidationMethod

Name: bdqffdq:ValidationMethod
Preferred Label: Validation Method
Definition: A data quality bdqffdq:SolutionsConcept that relates a bdqffdq:Validation to its bdqffdq:Specifications.
SubClass Of: DataQualityMethod; ValidationConcept
Comments: A bdqffdq:ValidationMethod is a data quality Solutions layer concept (see Figure 3 in Veiga et al., 2017) describing the relationship between a bdqffdq:Specification (technical description of a Test) and a bdqffdq:Validation (a bdqffdq:Criterion in the context of bdqffdq:ResourceType (bdqffdq:SingleRecord or bdqffdq:MultiRecord) and associated bdqffdq:InformationElements).
VM(va) = { s | s ∈ S ⋀ (va, s) ∈ rel_VM }

ValidationPolicy

Name: bdqffdq:ValidationPolicy
Preferred Label: Validation Policy
Definition: A bdqffdq:NeedConcept that relates a bdqffdq:UseCase to a set of supporting bdqffdq:Validations.
SubClass Of: Policy; ValidationConcept
Comments: A bdqffdq:ValidationPolicy is a data quality Need layer concept (see Figure 3 in Veiga et al., 2017) that describes how a bdqffdq:Validation relates to a bdqffdq:UseCase. This relationship defines which bdqffdq:Validations are needed to identify quality in a given bdqffdq:UseCase.
VP(u) = { va | va ∈ VA ⋀ (u, va) ∈ rel_VP }

ValidationResponse

Name: bdqffdq:ValidationResponse
Preferred Label: Validation Response
Definition: A bdqffdq:Response expressing the result of a bdqffdq:Implementation validating compliance with a particular bdqffdq:DataQualityNeed in a particular bdqffdq:DataResource.
SubClass Of: Response; ValidationConcept
Comments: The bdqffdq:ValidationResponse is a Report layer concept (see Figure 3 in Veiga et al., 2017) that describes the output of the execution of a Test that performs a bdqffdq:ValidationMethod following a bdqffdq:Specification to assess the validity of some data with respect to the bdqffdq:Criteria of a bdqffdq:Validation.
The bdqffdq:ValidationResponse concept is expected to carry through bdqffdq:hasResponseResult a bdqffdq:ResponseResult of bdqffdq:COMPLIANT or bdqffdq:NON_COMPLIANT.
DQV(dr) = { dqv | dqv ∈ RespV ⋀ (dr, dqv) ∈ rel_DQV }

4.2 ObjectProperty terms (normative)

aggregatesResponsesFrom

Name: bdqffdq:aggregatesResponsesFrom
Preferred Label: aggregates Responses From
Definition: Relates an ActedUpon Information Element (typically used by a MultiRecord Measure) to the DataQualityNeed (Validation, Issue, Measure, or Amendment) whose Responses in a DataQualityReport are aggregated as inputs to that Measure.
Comments: This property provides an explicit machine-queryable link between an acted-upon set of aggregated Response outcomes and the upstream Test whose Responses it aggregates. It is intended to complement use of bdqffdq:hasActedUponInformationElement / bdqffdq:composedOf when the acted-upon data are Responses in a Data Quality Report, rather than raw source-data terms.

amendmentProperty

Name: bdqffdq:amendmentProperty
Preferred Label: amendment Property
Definition: Category of object properties that apply to bdqffdq:Amendments
Comments: Subproperties of this type group object properties that apply to bdqffdq:AmendmentConcepts such as bdqffdq:AmendmentPolicy (bdqffdq:DataQualityNeed), bdqffdq:AmendmentMethod (bdqffdq:DataQualityMethod) and bdqffdq:Amendment (bdqffdq:DataQualityReports).

appliesTo

Name: bdqffdq:appliesTo
Preferred Label: applies To
Definition: Describes the bdqffdq:DataResource about which a bdqffdq:Response is made.
Comments: If a bdqffdq:Response forms the oa:body of an oa:Annotation, the bdqffdq:appliesTo bdqffdq:DataResource would be the oa:target of the bdqffdq:Annotation. If bdqffdq:Responses are composed in bdqffdq:DataQualityReports, the bdqffdq:appliesTo bdqffdq:DataResource is an item examined as part of the bdqffdq:DataQualityReport. Expectation for bdqffdq:SingleRecord Test bdqffdq:Responses on Darwin Core data in the BDQ standard is that bdqffdq:appliesTo would point at a dwc:Occurrence record.

composedOf

Name: bdqffdq:composedOf
Preferred Label: composed Of
Definition: Specific vocabulary term that comprises a bdqffdq:InformationElement that is not a bdqffdq:AbstractInformationElement.
Comments: Describes the properties from a controlled vocabulary that compose an InformationElement. For example, an InformationElement may be composedOf properties such as dwc:day, dwc:month and dwc:year.

containsResponse

Name: bdqffdq:containsResponse
Preferred Label: contains Response
Definition: Connects a bdqffdq:DataQualityReport with bdqffdq:Responses that comprise that bdqffdq:DataQualityReport.
Comments: Connects bdqffdq:Responses together into bdqffdq:DataQualityReports. Alternatively, bdqffdq:Responses can be contained in oa:Annotations, in which case this property is not used.

forAmendment

Name: bdqffdq:forAmendment
Preferred Label: for Amendment
Definition: Relates a bdqffdq:AmendmentMethod to a bdqffdq:Amendment.
SubClass Of: amendmentProperty; forDataQualityNeed
Comments: Use to link a bdqffdq:AmendmentMethod to a bdqffdq:Amendment. Describes the relationship between a bdqffdq:AmendmentMethod (Solutions layer, see Figure 3 in Veiga et al., 2017) and a bdqffdq:Amendment (Need layer, see Figure 3 in Veiga et al., 2017).

forDataQualityNeed

Name: bdqffdq:forDataQualityNeed
Preferred Label: for Data Quality Need
Definition: Category of properties that relates a bdqffdq:DataQualityNeed to specific bdqffdq:Methods.
Comments: Category of properties that link Tests to their bdqffdq:Methods.

forIssue

Name: bdqffdq:forIssue
Preferred Label: for Issue
Definition: Relates a bdqffdq:IssueMethod to a bdqffdq:Issue.
SubClass Of: forDataQualityNeed; issueProperty
Comments: Use to link a bdqffdq:IssueMethod to a bdqffdq:Issue. Describes the relationship between a bdqffdq:IssueMethod (Solutions layer, see Figure 3 in Veiga et al., 2017) and a bdqffdq:Issue (Need layer, see Figure 3 in Veiga et al., 2017). Parallel concepts are bdqffdq:forAmendment, bdqffdq:forValidation, and bdqffdq:forMeasure.

forMeasure

Name: bdqffdq:forMeasure
Preferred Label: for Measure
Definition: Relates a bdqffdq:MeasurementMethod to a bdqffdq:Measure.
SubClass Of: forDataQualityNeed; measurementProperty
Comments: Use to link bdqffdq:MeasurementMethods (Solutions layer, see Figure 3 in Veiga et al., 2017) to bdqffdq:Measures (Need layer, see Figure 3 in Veiga et al., 2017). Parallel concepts are bdqffdq:forAmendment, bdqffdq:forValidation, and bdqffdq:forIssue.

forValidation

Name: bdqffdq:forValidation
Preferred Label: for Validation
Definition: Relates a bdqffdq:ValidationMethod to a bdqffdq:Validation.
SubClass Of: forDataQualityNeed; validationProperty
Comments: Use to link bdqffdq:ValidationMethods to bdqffdq:Validations. Describes the relationship between a bdqffdq:ValidationMethod (Solutions layer, see Figure 3 in Veiga et al., 2017) and a bdqffdq:Validation (Need layer, see Figure 3 in Veiga et al., 2017). Parallel concepts are bdqffdq:forAmendment, bdqffdq:forMeasure, and bdqffdq:forIssue.

hasActedUponInformationElement

Name: bdqffdq:hasActedUponInformationElement
Preferred Label: has Acted Upon Information Element
Definition: Describes the bdqffdq:ActedUpon bdqffdq:InformationElements assessed by a bdqffdq:DataQualityNeed about which bdqffdq:Responses arising from the bdqffdq:DataQualityNeed would apply.
SubClass Of: hasInformationElement
Comments: Provides a relationship between bdqffdq: concepts and the bdqffdq:InformationElements that are bdqffdq:ActedUpon in a Test.

hasArgument

Name: bdqffdq:hasArgument
Preferred Label: has Argument
Definition: Relates a bdqffdq:Specification to a bdqffdq:Argument
Comments: Expected to be a relationship between a bdqffdq:Specification and a bdqffdq:Argument, where the bdqffdq:Argument provides a value for a bdqffdq:Parameter (e.g., bdqval:sourceAuthority), and a bdqffdq:hasAuthoritiesDefaults for the bdqffdq:Specification may provide a default value for the bdqffdq:Parameter under that bdqffdq:Specification.

hasConsultedInformationElement

Name: bdqffdq:hasConsultedInformationElement
Preferred Label: has Consulted Information Element
Definition: Describes the bdqffdq:InformationElements assessed by a bdqffdq:DataQualityNeed in order to make bdqffdq:Responses concerning bdqffdq:ActedUpon bdqffdq:InformationElements.
SubClass Of: hasInformationElement
Comments: Provides a relationship between bdqffdq: concepts and the bdqffdq:InformationElements that are bdqffdq:Consulted, but not bdqffdq:ActedUpon in a Test.

hasCriterion

Name: bdqffdq:hasCriterion
Preferred Label: has Criterion
Definition: The bdqffdq:Criterion under which a bdqffdq:Validation or bdqffdq:Issue assesses for data quality.
SubClass Of: issueProperty; validationProperty
Comments: Used to link the derived concept of a bdqffdq:Validation to the bdqffdq:FundamentalConcept of a bdqffdq:Criterion.

hasDataQualityDimension

Name: bdqffdq:hasDataQualityDimension
Preferred Label: has Data Quality Dimension
Definition: The bdqffdq:DataQualityDimension to which a bdqffdq:DataQualityNeed applies.
SubClass Of: amendmentProperty; issueProperty; measurementProperty; validationProperty
Comments: Used to link a derived concept of a bdqffdq:DataQualityNeed (a Test, whether rdf:type Validation, Issue, Measure, or Amendment) to the bdqffdq:FundamentalConcept of a bdqffdq:DataQualityDimension. For a bdqffdq:Validation or bdqffdq:Issue, the bdqffdq:DataQualityDimension of data quality assessed. For a bdqffdq:Measure, the bdqffdq:DataQualityDimension of data quality measured. For a bdqffdq:Amendment, the bdqffdq:DataQualityDimension of data quality to be improved.
Under the original formulation of the Framework, only Measures have Dimensions.

hasEnhancement

Name: bdqffdq:hasEnhancement
Preferred Label: has Enhancement
Definition: The bdqffdq:Enhancement that describes how a bdqffdq:Amendment may propose changes to improve data quality.
SubClass Of: amendmentProperty
Comments: Used to link the derived property of a bdqffdq:Amendment to the bdqffdq:FundamentalConcept of a bdqffdq:Enhancement.

hasInformationElement

Name: bdqffdq:hasInformationElement
Preferred Label: has Information Element
Definition: Describes the bdqffdq:InformationElements assessed by a bdqffdq:DataQualityNeed.
SubClass Of: amendmentProperty; issueProperty; measurementProperty; validationProperty
Comments: Provides a relationship between bdqffdq:DataQualityNeed concepts and bdqffdq:InformationElements. For example, bdqffdq:Validation uses this property with bdqffdq:hasResourceType to define a bdqffdq:Criterion in the context of related bdqffdq:InformationElements.
Subtypes bdqffdq:hasActedUponInformationElement and bdqffdq:hasConsultedInformationElement allow a bdqffdq:DataQualityNeed to be related to specific bdqffdq:InformationElement terms in a way that allows bdqffdq:DataQualityReports to distinguish for consumers which bdqffdq:InformationElements a Test makes bdqffdq:Responses about (and which only informed that bdqffdq:Response).

hasParameter

Name: bdqffdq:hasParameter
Preferred Label: has Parameter
Definition: Relates a bdqffdq:Argument to a bdqffdq:Parameter.
Comments: The bdqffdq:hasParameter property is expected to describe the Formal Parameter for which a bdqffdq:hasArgumentValue of the same bdqffdq:Argument provides the Actual Parameter. The bdqffdq:Argument is also expected to be the bdqffdq:hasArgument for a bdqffdq:Specification that provides the default value for the bdqffdq:hasArgumentValue and bdqffdq:hasParameter within a bdqffdq:hasAuthoritiesDefaults.

hasResourceType

Name: bdqffdq:hasResourceType
Preferred Label: has Resource Type
Definition: The bdqffdq:ResourceType to which a bdqffdq:DataQualityNeed applies.
Comments: Provides additional metadata, with the bdqffdq:InformationElements, that describe the bdqffdq:ResourceType (bdqffdq:SingleRecord or bdqffdq:MultiRecord) on which the bdqffdq: concept operates. For example, a bdqffdq:Amendment with bdqffdq:ResourceType bdqffdq:MultiRecord defines that bdqffdq:Amendment as operating on a data set.

hasResponseQualifier

Name: bdqffdq:hasResponseQualifier
Preferred Label: has Response Qualifier
Definition: ResponseQualifier object asserted by an Response.
SubClass Of: reportProperty
Comments: Optional extension point, could be used to add structured information about uncertainty.

hasResponseResult

Name: bdqffdq:hasResponseResult
Preferred Label: has Response Result
Definition: The bdqffdq:ResponseResult object asserted by a bdqffdq:Response.
SubClass Of: reportProperty
Comments: Used in a bdqffdq:DataQualityReport to describe bdqffdq:ResponseResult objects. For example, values could be bdqffdq:COMPLIANT or bdqffdq:NOT_COMPLIANT for bdqffdq:ValidationResponses. Both bdqffdq:ValidationResponses and bdqffdq:IssueResponses have bdqffdq:ResponseResults as objects. The bdqffdq:AmendmentResponses have bdqffdq:ResponseResults that are data properties, so they are not expected to use this object property. The bdqffdq:MeasurementResponse bdqffdq:ResponseResults may be objects or data.
If bdqffdq:ResponseResults are not objects, use the datatype property bdqffdq:hasResponseResultValue.

hasResponseStatus

Name: bdqffdq:hasResponseStatus
Preferred Label: has Response Status
Definition: The bdqffdq:ResponseStatus object asserted by a bdqffdq:Response.
SubClass Of: reportProperty
Comments: Used in a bdqffdq:DataQualityReport to describe bdqffdq:ResponseStatus. For example, in the case of a bdqffdq:ValidationResponse, bdqffdq:ResponseStatus values could be bdqffdq:RUN_HAS_RESULT, bdqffdq:INTERNAL_PREREQUISITES_NOT_MET, or bdqffdq:EXTERNAL_PREREQISITES_NOT_MET. Similarly, bdqffdq:AmendmentResponses can assert bdqffdq:ResponesStatus objects including bdqffdq:AMENDED or bdqffdq:FILLED_IN.
The bdqffdq:ResponseStatus is always an object, unlike bdqffdq:ResponseResult, where either the object property bdqffdq:hasResponseResult or the data property bdqffdq:hasResponseResultValue may apply.

hasSpecification

Name: bdqffdq:hasSpecification
Preferred Label: has Specification
Definition: Relates a bdqffdq:Method to a bdqffdq:Specification.
Comments: Describes the relationship between a derived bdqffdq: concept that is a bdqffdq:Method and the bdqffdq:FundamentalConcept of a bdqffdq:Specification (technical description of a Test).

hasUseCase

Name: bdqffdq:hasUseCase
Preferred Label: has Use Case
Definition: Relates a bdqffdq:Policy to a bdqffdq:UseCase.
Comments: Used by concepts in the bdqffdq:DataQualityNeed category to describe the relationship between bdqffdq:Policies (bdqffdq:ValidationPolicy, bdqffdq:MeasurementPolicy, bdqffdq:AmendmentPolicy) and an instance of a bdqffdq:UseCase.

implementedBy

Name: bdqffdq:implementedBy
Preferred Label: implemented By
Definition: The bdqffdq:Mechanism that provides a bdqffdq:Implementation
Comments: Describes the link between a bdqffdq:Implementation and a bdqffdq:Mechanism.

improvedBy

Name: bdqffdq:improvedBy
Preferred Label: improved By
Definition: The bdqffdq:ImprovementTarget that would have data quality improved by bdqffdq:Responses resulting from a bdqffdq:Amendment.
Comments: Originally had Domain: Amendment and Range: ImprovementTarget. Asserts that a bdqffdq:ImprovementTarget could be improved by the bdqffdq:Amendment.
Object property that describes a bdqffdq:Amendment, as part of the bdqffdq:ImprovementTarget, that would improve data bdqffdq:ActedUpon by a set of bdqffdq:Measures or bdqffdq:Validations. This can be used to determine which bdqffdq:Measures and bdqffdq:Validations are improved upon by a given bdqffdq:Amendment.

includedInPolicy

Name: bdqffdq:includedInPolicy
Preferred Label: included In Policy
Definition: Assserts that a bdqffdq:DataQualityNeed is part of a bdqffdq:Policy.
Comments: Relates bdqffdq:Policies to Tests (bdqffdq:DataQualityNeed).

issueProperty

Name: bdqffdq:issueProperty
Preferred Label: issue Property
Definition: Category of object properties that apply to bdqffdq:Issues.
Comments: Properties that relate bdqffdq:Issues to bdqffdq:IssueMethods, bdqffdq:Criteria, and bdqffdq:DataQualityDimensions.

measurementProperty

Name: bdqffdq:measurementProperty
Preferred Label: measurement Property
Definition: Category of object properties that apply to bdqffdq:Measures.
Comments: Subproperties of this type group object properties that apply to bdqffdq:MeasurementConcepts such as bdqffdq:MeasurementPolicy (bdqffdq:DataQualityNeed), bdqffdq:MeasurementMethod (bdqffdq:DataQualityMethod) and bdqffdq:Measure (bdqffdq:DataQualityReport).

producesResponse

Name: bdqffdq:producesResponse
Preferred Label: produces Response
Definition: Connects an entity with a bdqffdq:Response that the entity created.
Comments: Connects bdqffdq:Implementations (Solutions layer, see Figure 3 in Veiga et al., 2017) with the bdqffdq:Responses (Reports layer, see Figure 3 in Veiga et al., 2017) that they produce from the execution of a bdqffdq:Specification.

reportProperty

Name: bdqffdq:reportProperty
Preferred Label: report Property
Definition: Category of object properties that apply to bdqffdq:Responses.
Comments: Category of properties used in reports (object properties associated with response objects (bdqffdq:Responses)). See also the data properties bdqffdq:hasResponseComment and bdqffdq:hasResponseResultValue.

targetedIssue

Name: bdqffdq:targetedIssue
Preferred Label: targeted Issue
Definition: A bdqffdq:Issue for which the data conformance with a bdqffdq:NeedConcept may be improved by accepting proposals from a bdqffdq:Amendment via a bdqffdq:ImprovementTarget.
Comments: The bdqffdq:Issue targeted by a problem via the bdqffdq:ImprovementTarget object. Describes the relationship between a bdqffdq:ImprovementTarget and a bdqffdq:Issue.

targetedMeasure

Name: bdqffdq:targetedMeasure
Preferred Label: targeted Measure
Definition: A bdqffdq:Measure for which the data conformance with a bdqffdq:NeedConcept may be improved by accepting proposals from a bdqffdq:Amendment via a bdqffdq:ImprovementTarget.
Comments: Describes the relationship between a bdqffdq:ImprovementTarget and a bdqffdq:Measure.

targetedValidation

Name: bdqffdq:targetedValidation
Preferred Label: targeted Validation
Definition: A bdqffdq:Validation for which the data conformance with a bdqffdq:NeedConcept may be improved by accepting proposals from a bdqffdq:Amendment via a bdqffdq:ImprovementTarget.
SubClass Of: http://www.w3.org/2002/07/owl#topObjectProperty
Comments: Relates a bdqffdq:ImprovementTarget to a bdqffdq:Validation. Describes the relationship between a bdqffdq:ImprovementTarget and a bdqffdq:Validation.

usesSpecification

Name: bdqffdq:usesSpecification
Preferred Label: uses Specification
Definition: The bdqffdq:Specification that a bdqffdq:Implementation implements.
Comments: Relates a bdqffdq:Implementation to the bdqffdq:Specification that the bdqffdq:Implementation implements.

validationProperty

Name: bdqffdq:validationProperty
Preferred Label: validation Property
Definition: Category of object properties that apply to bdqffdq:Validations.
Comments: Subproperties of this type group object properties that apply to bdqffdq:ValidationConcepts such as bdqffdq:ValidationPolicy (bdqffdq:DataQualityNeed), bdqffdq:ValidationMethod (bdqffdq:DataQualityMethod) and bdqffdq:Validation (bdqffdq:DataQualityReport).

4.3 DataProperty terms (normative)

hasArgumentValue

Name: bdqffdq:hasArgumentValue
Preferred Label: has Argument value
Definition: The value of a bdqffdq:Argument that is used in a bdqffdq:Specification to replace a Formal Parameter to determine the behavior of the bdqffdq:Specification.
Comments:

hasAuthoritiesDefaults

Name: bdqffdq:hasAuthoritiesDefaults
Preferred Label: has Authorities and Defaults
Definition: Text describing bdqval:sourceAuthorities and bdqffdq:Parameters with their default values to attach to a bdqffdq:Specification to further specify the behavior described in the bdqffdq:hasExpectedResponse.
Comments: Details of the bdqval:sourceAuthority listed in a bdqffdq:Specification, with bdqffdq:Parameters that may affect the bdqffdq:hasExpectedResponse, and with their default values.

hasDateLastUpdated

Name: bdqffdq:hasDateLastUpdated
Preferred Label: has Date Last Updated
Definition: Date of the most recent dcterms:issued for this class with a change that would be pertinent to a bdqffdq:Implementation.
Comments: While a new instance of a resource with a new dcterms:issued is required for any change to that resource, not all changes would be pertinent to implementers, (i.e., that would required implementers to evaluate their code for changes needed to comply with the update). The bdqffdq:hasDateLastUpdated allows implementers to identify which new changes to the definition of a Test would entail changes to code, and which would not. For example, a change to the logic of a bdqffdq:Specification in the text of bdqffdq:hasExpectedResponse would imply needed changes to the logic of code implementing that bdqffdq:Specification, but a correction of a spelling mistake within the text of a bdqffdq:hasExpectedResponse would not.

hasExpectedResponse

Name: bdqffdq:hasExpectedResponse
Preferred Label: has Expected Response
Definition: Text describing the logic to be followed by a bdqffdq:Implementation of a bdqffdq:Specification specifying the values of bdqffdq:ResponseStatus and bdqffdq:ResponseResults that should be produced from the evaluation of input bdqffdq:InformationElements.
Comments: The description of the logic of a Test Specification. A bdqffdq:hasExpectedResponse is expected to be a data property of a Specification.

hasFitnessRequirements

Name: bdqffdq:hasFitnessRequirements
Preferred Label: has Fitness Requirements
Definition: The property of a bdqffdq:UseCase that provides text listing the qualities that data must have to be fit for a given use.
Comments: The bdqffdq:hasFitnessRequirements should sumarize the properties that data need to have to be fit for purpose for that bdqffdq:UseCase. It should briefly list the general properties that bdqffdq:DataQualityNeeds associated with the UseCase need to assess (for example, stating that georeferences must be correctly formatted and have adequate metadata), and can identify particular threshold values (such as a coordinate uncertainty greater than some value) that would make data unfit for that use. The hasFitnessRequirements property should not, however, simply list bdqffdq:DataQualityNeeds instances, but should provide a succinct human readable summary of the quality requirements.

hasResponseComment

Name: bdqffdq:hasResponseComment
Preferred Label: has Response Comment
Definition: Free text describing the bdqffdq:Response made in the response and why that conclusion was reached.
Comments: Intended for consumption by human readers of bdqffdq:DataQualityReports to understand why particular bdqffdq:Responses were made.

hasResponseResultValue

Name: bdqffdq:hasResponseResultValue
Preferred Label: has Response Result Value
Definition: Data property carrying the value of a bdqffdq:Response when the value is not an object.
Comments: Applies to bdqffdq:AmendmentResponses. To support bdqtest: Tests, bdqffdq:hasResponseResultValue is expected to carry a key:value list where the keys are the names of bdqffdq:ActedUpon bdqffdq:InformationElements, and the values are the proposed new values (filling in or replacing the values of those terms in the input). Applies to bdqffdq:MeasurementResponses that assert a numeric value.

4.4 NamedIndividual terms (normative)

MultiRecord

Name: bdqffdq:MultiRecord
Type: bdqffdq:ResourceType
Preferred Label: Multi Record
Definition: A set of one or more bdqffdq:SingleRecords.
Comments: A data set. Encoded data with a defined structure that can be described as dcmitype:Dataset.

SingleRecord

Name: bdqffdq:SingleRecord
Type: bdqffdq:ResourceType
Preferred Label: Single Record
Definition: A single entity comprised of encoded data with a defined structure that contains one instance of a core concept from the perspective of bdqffdq:InformationElements assessed for a bdqffdq:DataQualityNeed.
Comments: A record from a dcmitype:Dataset. May be a database tuple, in the strict sense (i.e, a single row in a table) or may be rows related across several tables, or a graph of data. A bdqffdq:SingleRecord is single in that it has one instance of a core concept from the perspective of bdqffdq:InformationElements assessed for a bdqffdq:UseCase. For example, in a bdqffdq:UseCase where dwc:Occurences are central, a bdqffdq:SingleRecord would represent a single dwc:Occurrence, but could have multiple dwc:Identifications and multiple dwc:Taxa related to it in a graph or data structure. However, in a bdqffdq:UseCase where dwc:Taxa are central, a bdqffdq:SingleRecord would represent a single dwc:Taxon entity (and might have multiple dwc:Occurrences related to it as part of the bdqffdq:SingleRecord, so long as the graph was limited before reaching other dwc:Taxon entities).
A bdqffdq:SingleRecord, like a bdqffdq:MultiRecord, consists of data with a defined structure that can be described as dcmitype:Dataset

COMPLETE

Name: bdqffdq:COMPLETE
Type: bdqffdq:ResponseResult
Preferred Label: COMPLETE
Definition: A bdqffdq:ResponseResult of a bdqffdq:Measure that asserts that data are present and sufficiently comprehensive for use.
Comments: This value can be used to filter data for bdqffdq:QualityAssurance. This value can be asserted, for example, by bdqffdq:Measures of bdqffdq:MultiRecords where all the bdqffdq:Validation bdqffdq:ResponseResults from all included records in the dataset are bdqffdq:COMPLIANT.

COMPLIANT

Name: bdqffdq:COMPLIANT
Type: bdqffdq:ResponseResult
Preferred Label: COMPLIANT
Definition: A bdqffdq:ResponseResult of a bdqffdq:Validation where the data conforms to the bdqffdq:Criteria for quality in the Test bdqffdq:Specification.
Comments:

IS_ISSUE

Name: bdqffdq:IS_ISSUE
Type: bdqffdq:ResponseResult
Preferred Label: IS_ISSUE
Definition: A bdqffdq:ResponseResult of a bdqffdq:Issue indicating that the data do not have sufficient quality for a use.
Comments: This is a parallel bdqffdq:ResponseResult to bdqffdq:NOT_COMPLIANT

NOT_COMPLETE

Name: bdqffdq:NOT_COMPLETE
Type: bdqffdq:ResponseResult
Preferred Label: NOT_COMPLETE
Definition: A bdqffdq:ResponseResult of a bdqffdq:Measure which asserts that data are not present or are not sufficiently comprehensive for a use.
Comments: This value can be used to exclude data for bdqffdq:QualityAssurance. This value can be asserted, for example, by bdqffdq:Measures of bdqffdq:MultiRecords where not all the bdqffdq:Validation bdqffdq:ResponseResult from all included records in the dataset have a bdqffdq:ResponseResult of bdqffdq:COMPLIANT.

NOT_COMPLIANT

Name: bdqffdq:NOT_COMPLIANT
Type: bdqffdq:ResponseResult
Preferred Label: NOT_COMPLIANT
Definition: A bdqffdq:ResponseResult of a bdqffdq:Validation where the data do not conform to the bdqffdq:Criteria for quality in the Test bdqffdq:Specification.
Comments:

NOT_ISSUE

Name: bdqffdq:NOT_ISSUE
Type: bdqffdq:ResponseResult
Preferred Label: NOT_ISSUE
Definition: A bdqffdq:ResponseResult of a bdqffdq:Issue where no potential problems were detected.
Comments: This is similar to, but has different semantics to, bdqffdq:COMPLIANT for a bdqffdq:Validation. The value bdqffdq:COMPLIANT means that the data were evaluated as having quality according to a bdqffdq:Criterion. The value bdqffdq:NOT_ISSUE means that no bdqffdq:Issue with data quality was found under a bdqffdq:Criterion for identifying the absence of quality.

POTENTIAL_ISSUE

Name: bdqffdq:POTENTIAL_ISSUE
Type: bdqffdq:ResponseResult
Preferred Label: POTENTIAL_ISSUE
Definition: A bdqffdq:ResponseResult of a bdqffdq:Issue that indicates that the data may not have sufficient quality for a use. The user will need to evaluate if the data are fit for their particular use or not.
Comments: See also bdqffdq:IS_ISSUE and bdqffdq:NOT_ISSUE. The value bdqffdq:POTENTIAL_ISSUE has no analog in a bdqffdq:Validation.

AMENDED

Name: bdqffdq:AMENDED
Type: bdqffdq:ResponseStatus
Preferred Label: AMENDED
Definition: A bdqffdq:ResponseStatus used to indicate that a bdqffdq:hasResponseResultValue from a bdqffdq:Amendment contains a proposed change.
Comments: The value bdqffdq:AMENDED implies that a change is being proposed to an existing bdqval:NotEmpty value. bdqffdq:Amendments do not provide bdqffdq:hasResponseResult object properties. Proposed changes will be in a bdqffdq:hasResponseResultValue data property.

EXTERNAL_PREREQUISITES_NOT_MET

Name: bdqffdq:EXTERNAL_PREREQUISITES_NOT_MET
Type: bdqffdq:ResponseStatus
Preferred Label: EXTERNAL_PREREQUISITES_NOT_MET
Definition: A bdqffdq:ResponseStatus used to indicate that a bdqffdq:ResponseResult was not generated because a bdqval:sourceAuthority was not accessible. If the Test is run at a later time, it may produce a different bdqffdq:ResponseStatus.
Comments:

FILLED_IN

Name: bdqffdq:FILLED_IN
Type: bdqffdq:ResponseStatus
Preferred Label: FILLED_IN
Definition: A bdqffdq:ResponseStatus used to indicate that a bdqffdq:Amendment contains a proposed change to a record in a bdqffdq:hasResponseResultValue where the bdqffdq:InformationElement was bdqval:Empty.
Comments:

INTERNAL_PREREQUISITES_NOT_MET

Name: bdqffdq:INTERNAL_PREREQUISITES_NOT_MET
Type: bdqffdq:ResponseStatus
Preferred Label: INTERNAL_PREREQUISITES_NOT_MET
Definition: A bdqffdq:ResponseStatus used to indicate that a bdqffdq:ResponseResult was not generated because values of the bdqffdq:InformationElement were insufficient to run the Test. If the Test is run at a later time on unmodified data, it should produce the same bdqffdq:ResponseStatus.
Comments:

NOT_AMENDED

Name: bdqffdq:NOT_AMENDED
Type: bdqffdq:ResponseStatus
Preferred Label: NOT_AMENDED
Definition: A bdqffdq:ResponseStatus used to indicate that a bdqffdq:Amendment proposed no change.
Comments: No value will be provided in a bdqffdq:hasResponseResultValue. bdqffdq:Amendments do not provide bdqffdq:hasResponseResult object properties.

RUN_HAS_RESULT

Name: bdqffdq:RUN_HAS_RESULT
Type: bdqffdq:ResponseStatus
Preferred Label: RUN_HAS_RESULT
Definition: A bdqffdq:ResponseStatus used to indicate that that a result was correctly generated.
Comments: Applies to bdqffdq:Validations, bdqffdq:Issues and bdqffdq:Measures, but not bdqffdq:Amendments. For a bdqffdq:Validation or a bdqffdq:Issue, the value will be found as a bdqffdq:ResponseResult object by following bdqffdq:hasResponseResult. For a bdqffdq:Measure, the value could be either in the data property bdqffdq:hasResponseResultValue or could be a ResponseResult object.

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. Fitness For Use Framework Ontology List of Terms. Biodiversity Information Standards (TDWG). http://rs.tdwg.org/bdqffdq/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.