Lee Belbin

A tweak to the Expected Response (@chicoreus - please check as I am unsure on REPORT/NOT_REPORTED) REPORT the number of tests of output type AMENDMENT that have been run against...

From Zoom 30th May 2022, change the Expected Response from REPORT the number of tests of output type AMENDMENT that have been run against the record and have proposed changes...

Splitting bdqffdq:Information Elements into "Information Elements ActedUpon" and "Information Elements Consulted": **I'm unsure about how we deal with MEASUREs**. I used "Consulted". Also changed "Field" to "TestField", "Output Type" to...

I tend to agree with @ArthurChapman. The test would make more sense to me if EITHER dwc:decimalLatitude or dwc:decimalLongitude were zero. It just makes it a more useful test as...

As usual, I bow to the experts. I found 22 records in ALA of lat/lon=0,0. These are rendered as 'spatially invalid' on test 'coordinates don't match country (error)' and also...

This was a test for lat/lon 0,0 so reflecting it to the 'positive' probably stuffed the logic. The intent is INTERNAL_PREREQUISITES_NOT_MET if dwc:decimalLatitude or dwc:decimalLongitude are EMPTY or not interpretable...

So, what you are suggesting for the ER is- INTERNAL_PREREQUISITES_NOT_MET if dwc:decimalLatitude or dwc:decimalLongitude are EMPTY or either value is not interpretable as a number; COMPLIANT if either the value...

Sorry to be pedantic, but surely you only need any one of the input values to be EMPTY to trigger INTERNAL_PREREQUISITES_NOT_MET? As in INTERNAL_PREREQUISITES_NOT_MET if dwc:decimalLatitude or dwc:decimalLongitude are EMPTY...

Thanks @chicoreus - I can live with that.

Splitting bdqffdq:Information Elements into "Information Elements ActedUpon" and "Information Elements Consulted". Also changed "Field" to "TestField", "Output Type" to "TestType" and updated "Specification Last Updated"