Lee Belbin

I agree with @chicoreus and amended Dimension and will check **Conformance** on others next. @ArthurChapman: How do we refer to Parameters? Maybe like this: INTERNAL_PREREQUISITES_NOT_MET if the field dwc:minimumElevationInMeters is...

Do all agree that #24, #107 (and this one) should be Data Quality Dimension = Likelihood? What about #108? I presume Conformance.

As we are providing elevation limits, the result either conforms to this range or it does not. There is no likeliness about it.

Edited Parameter(s) and Source authority to align with proposed structure and format

Splitting bdqffdq:Information Elements into "Information Elements ActedUpon" and "Information Elements Consulted"

Splitting bdqffdq:Information Elements into "Information Elements ActedUpon" and "Information Elements Consulted". Also changed "Fields" to "TestField" and "Output Type" to "TestType".

I agree with @tucotuco. How do we therefore handle refs to "ISO 8601:2004(E)" as in #26, #52, #61, #66, #69 and #76?

Changed the Expected response from EXTERNAL_PREREQUISITES_NOT_MET if the DCMI type vocabulary is not available; INTERNAL_PREREQUISITES_NOT_MET if the value of dc:type is EMPTY; AMENDED the value of dc:type if it can...

Post Zoom 11/7/2023, I have aligned the Source Authority with the suggested syntax: bdq:sourceAuthority is "DCMI Type Vocabulary" [https://www.dublincore.org/specifications/dublin-core/dcmi-type-vocabulary/] to bdq:sourceAuthority is "Dublin Core Metadata Initiative (DCMI)" {[https://www.dublincore.org/]} {DCMI Type...

Splitting bdqffdq:Information Elements into "Information Elements ActedUpon" and "Information Elements Consulted". Also changed "Fields" to "TestFields" and "Output Type" to "TestType".