Lee Belbin

Should this now be "VALIDATION_TAXONRANK_STANDARD" or "VALIDATION_TAXONRANK_ISSTANDARD"? I think the first is better.

more... AMBIGUOUS to UNAMBIGUOUS GREATERTHAN to LESSTHAN ZEO to NOTZERO TERRESTRIALMARINE same INCOMPLETE to COMPLETE

Added to Notes: "This test will fail if there are leading or trailing white space or non-printing characters."

Thanks @ArthurChapman. Checked.

Post Zoom 11/7/2023, I have aligned the Source Authority with the suggested syntax: bdq:sourceAuthority default = "GBIF Vocabulary: Taxonomic Rank" [https://api.gbif.org/v1/vocabularies/TaxonRank/concepts] to bdq:sourceAuthority default = "Darwin Core" {https://dwc.tdwg.org} {dwc:taxonRank [https://dwc.tdwg.org/list/#dwc_taxonRank]}...

In the light of recent discussions, I have added the specific dwc terms to the Expected Response.

Examining test data, the following would return NOT_COMPLIANT when I think it should be INTERNAL_PREREQUISITES_NOT_MET dwc:scientificName="", dwc:genus="Hakea", dwc:specificEpithet="decurrens", dwc:infraspecificEpithet="physocarpa" ??

OK, so could we have a taxon guru adapt the Expected response? These epithet things scare me. Names scare me.

Hmm, maybe INTERNAL_PREREQUISITES_NOT_MET if dwc:scientificName is EMPTY, or all of dwc:genus, dwc:specificEpithet and dwc:infraspecificEpithet are EMPTY; COMPLIANT if the polynomial, as represented in dwc:scientificName, is consistent with the atomic parts...

1 + @tucotuco is a majority :) CHANGED