TG2-VALIDATION_COUNTRYCOUNTRYCODE_CONSISTENT

[iDigBioBot]

TestField	Value
GUID	b23110e7-1be7-444a-a677-cdee0cf4330c
Label	VALIDATION_COUNTRYCOUNTRYCODE_CONSISTENT
Description	Does the ISO country code, determined from the value of dwc:country, equal the value of dwc:countryCode?
TestType	Validation
Darwin Core Class	dcterms:Location
Information Elements ActedUpon	dwc:country
	dwc:countryCode
Information Elements Consulted
Expected Response	EXTERNAL_PREREQUISITES_NOT_MET if the bdq:sourceAuthority is not available; INTERNAL_PREREQUISITES_NOT_MET if either of the terms dwc:country or dwc:countryCode are bdq:Empty; COMPLIANT if the values of dwc:country and dwc:countryCode match national-level country name and matching country code respectively in the bdq:sourceAuthority
Data Quality Dimension	Consistency
Term-Actions	COUNTRYCOUNTRYCODE_CONSISTENT
Parameter(s)
Source Authority	bdq:sourceAuthority default = "The Getty Thesaurus of Geographic Names (TGN)" {[https://www.getty.edu/research/tools/vocabularies/tgn/index.html]}
Specification Last Updated	2024-09-25
Examples	[dwc:country="Australia", dwc:countryCode="AU": Response.status=RUN_HAS_RESULT, Response.result=COMPLIANT, Response.comment="dwc:country matches dwc:countryCode"]
	[dwc:country="United States Minor Outlying Islands", dwc:countryCode="US": Response.status=RUN_HAS_RESULT, Response.result=NOT_COMPLIANT, Response.comment="dwc:country does not match dwc:countryCode"]
Source	GBIF
References	ISO (n.dat.) ISO 3166 Country Codes. https://www.iso.org/iso-3166-country-codes.html ISO (n.dat.) ISO 3166 Country Codes. https://www.iso.org/iso-3166-country-codes.html/li> DataHub (2018) List of all countries with their two digit codes (ISO 3166-1). https://datahub.io/core/country-list Chapman AD and Wieczorek JR (2020) Georeferencing Best Practices. Copenhagen: GBIF Secretariat. https://doi.org/10.15468/doc-gg7h-s853
Example Implementations (Mechanisms)
Link to Specification Source Code
Notes	The country code determination service should be able to match the name of a country in the original or any language in the source authority. When dwc:countryCode="XZ" to mark the high seas, country should be empty until a time when a dwc:country="High seas" or similar is adopted. This test must return NOT_COMPLIANT if there is leading or trailing whitespace or there are leading or trailing non-printing characters.

[iDigBioBot]

Comment by Paula Zermoglio (@pzermoglio) migrated from spreadsheet:
In the cases when country was derived from coordinates, this would only make sense AFTER that step.

[iDigBioBot]

Comment by Paul Morris (@chicoreus) migrated from spreadsheet:
In the example given, country=Australia, countryCode=4, I would expect this validation to return a result status INTERNAL_PREREQUISITES_NOT_MET, as 4 is not a valid ISO 2 letter or 3 letter country code or three digit country code (004 would be), and thus can't be compared with "Australia". A better example might be country=Australia, countryCode=GM. Specification should note specific acceptable controlled vocabularies for countryCode

[iDigBioBot]

Comment by Paul Morris (@chicoreus) migrated from spreadsheet:
Rename: COUNTRY_COUNTRYCODE_CONSISTENT

[Tasilee]

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

[ArthurChapman]

Should the Expected Response make a reference to bdq:sourceAuthority or to "ISO 3166-1-alpha-2"? Most similar tests do. @chicoreus @Tasilee

[chicoreus]

@ArthurChapman yes, it should.

[ArthurChapman]

Updated Expected Response (add bolded text) and updated Specification Last Updated

EXTERNAL_PREREQUISITES_NOT_MET if the bdq:sourceAuthority is not available; INTERNAL_PREREQUISITES_NOT_MET if either of the terms dwc:country or dwc:countryCode are EMPTY; COMPLIANT if the value of the country code determined from the value of dwc:country from the bdq:sourceAuthority is equal to the value of dwc:countryCode; otherwise NOT_COMPLIANT |

[Tasilee]

Changed Source Authority value from

bdq:sourceAuthority is "ISO 3166-1-alpha-2" [https://restcountries.eu/#api-endpoints-list-of-codes, https://www.iso.org/obp/ui/#search]

to

{bdq:sourceAuthority = ISO 3166-1-alpha-2} { Country codes [https://www.iso.org/obp/ui/#search]}

to align syntax and provide a better link.

[Tasilee]

Amended Source Authority to align with @chicoreus suggested syntax

{bdq:sourceAuthority = ISO 3166-1-alpha-2} { Country codes [https://www.iso.org/obp/ui/#search]}

to

bdq:sourceAuthority default = "ISO 3166-1-alpha-2 country codes" { [https://www.iso.org/obp/ui/#search]}

[Tasilee]

Corrected syntax on Source Authority

[Tasilee]

Changed Source Authority from

bdq:sourceAuthority default = "ISO 3166-1-alpha-2 country codes" {[https://www.iso.org/obp/ui/#search]}

to

bdq:sourceAuthority default = "ISO 3166 Country Codes" {[https://www.iso.org/iso-3166-country-codes.html]} {ISO 3166-1-alpha-2 Country Code search [https://www.iso.org/obp/ui/#search]}

[Tasilee]

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"

[chicoreus]

Updated notes to change "fail" text to more explict "This test must return NOT_COMPLIANT if there is leading or trailing whitespace or there are leading or trailing non-printing characters." The expected response is clear about exact matching, so this applies.

[chicoreus]

As noted in #21, this one is limited and probably problematic. The notes indicate the problem, specifying that the country code should be matchable to the country name in a local language, something the sourceAuthority doesn't actually provide.

[chicoreus]

Noted in #21 this test probably does need to consult both Getty (for country name synonyms) and the ISO list. Getty TGN has at least some ISO 2 letter code labels, need to check if reachable through API. Logic would be check country code and country against ISO list, if not found check country against getty for label matching the one found in the ISO list for the country code when looking up the country value in getty.

[Tasilee]

@tucotuco knows TGN far better than I.

I did a quick scan of a range of "nation" level country names and they all had values for 2-letter, 3-letter and numeric ISO 3166 codes. Therefore, could we use TGN to resolve consistency?

COMPLIANT if the values of dwc:country and dwc:countryCode match national-level country name and matching country code respectively in the bdq:sourceAuthority.

?

[chicoreus]

Removing underscores in names/labels to make TERM_ACTON consistent

[tucotuco]

@tucotuco knows TGN far better than I.

I did a quick scan of a range of "nation" level country names and they all had values for 2-letter, 3-letter and numeric ISO 3166 codes. Therefore, could we use TGN to resolve consistency?

COMPLIANT if the values of dwc:country and dwc:countryCode match national-level country name and matching country code respectively in the bdq:sourceAuthority.

?

This requires two calls, one each for country and for countryCode. If they both resolve to the same entity, then the COMPLIANT result can be asserted.

[Tasilee]

I have amended the Expected Response and Source Authority to simplify the evaluation, hopefully. The 'high-seas' issue is Noted (in Notes).

[ArthurChapman]

See discussions under #98 wrt to XZ for high seas. As the source Authorities don't include XZ we could change the Expected Response to

EXTERNAL_PREREQUISITES_NOT_MET if the bdq:sourceAuthority is not available; INTERNAL_PREREQUISITES_NOT_MET if either of the terms dwc:country or dwc:countryCode are bdq:Empty; COMPLIANT if the values of dwc:country and dwc:countryCode match national-level country name and matching country code respectively in the bdq:sourceAuthority or if dwc:CountryCode='XZ' and dwc:country="High Seas"

[Tasilee]

As with my comment on #50, I think this test is ok as it stands in regards 'High seas' locations.

Dave Watts has made a case that we should be actively promoting dwc:country="High seas" (or similar) and dwc:countryCode="XZ". Until that project progresses well down the track, we are very likely to get a bdq:Empty for either or both dwc:country and dwc:countryCode. In this case, we end up with INTERNAL_PREREQUISITES_NOT_MET, which is an appropriate assertion.

As @chicoreus second paragraph at #42 (comment) suggests, we need to make some (strong) recommendations. We also need to document the issue consistently in Notes, as we are doing with #42 and #98. Maybe also something something about this issue in Supplementary would also be a good idea?

[tucotuco]

The strong recommendation should actually go to Darwin Core as an issue on countryCode.

[chicoreus]

On Thu, 26 Sep 2024 17:58:12 -0700 John Wieczorek ***@***.***> wrote: The strong recommendation should actually go to Darwin Core as an issue on countryCode.

@tucotuco that's definitely the right place to get this resolved. The question for us is probably whether to support Dave Watt's position noted by @Tasilee in #62 (comment) of dwc:countryCode="XZ" and dwc:country="High Seas", or dwc:countryCode="XZ", dwc:country="". Our position, expressed in the notes on VALIDATION_COUNTRYCOUNTRYCODE_CONSISTENT #62, has been "When countryCode=XZ to mark the high seas, country should be empty." The current note text "When dwc:countryCode="XZ" to mark the high seas, country should be empty until a time when a dwc:country="High seas" or similar is adopted. " is more general, but would take a change in the specification if dwc:country="High Seas" was adopted and remains absent in getty. (so we should consider reverting to the earlier text, as a change in the specification would be needed to support the "until a time" bit of the note, and having that in the note may imply that no change is needed...) At a minimum, issue on dwc:countryCode should highlight the need to identify high seas, and the resonable solution to this of country code XZ. Issue on dwc:country is independent for Darwin Core, but intertwined for us. We could work with either dwc:country="" or dwc:country="High Seas", the latter being a more difficult case than dwc:countryCode where the XZ value is from a controlled vocabulary, while "High seas", "High Seas", "high seas", and other language variants all seem like potential variations. That makes me think our current position of dwc:countryCode="XZ", dwc:country="" is a good one. Dave Watt's proposal seems a harder one to support.

[tucotuco]

The Darwin Core issue for countryCode is already open at tdwg/dwc#520.