-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TG2-VALIDATION_PATHWAY_STANDARD #277
Comments
Should be CORE see comments under #268 |
The four tests (#277, #278, #268, #269) should be CORE (I have discussed this with Lee). Some reasons are
|
Edited comment from "will fail" to the more explicit "This test must return NOT_COMPLIANT if there is leading or trailing whitespace or there are leading or trailing non-printing characters. " |
Source authority should be: bdq:sourceAuthority default = "Pathway Controlled Vocabulary List of Terms" {[https://dwc.tdwg.org/pw/]} {GBIF vocabulary API [https://api.gbif.org/v1/vocabularies/Pathway/]} |
I agree @chicoreus - Changing Source Authority from bdq:sourceAuthority default = "Darwin Core pathway" {[https://dwc.tdwg.org/list/#dwc_pathway]} {dwc:pathway vocabulary API [https://api.gbif.org/v1/vocabularies/Pathway/concepts]} to bdq:sourceAuthority default = "Pathway Controlled Vocabulary List of Terms" {[https://dwc.tdwg.org/pw/]} {GBIF vocabulary API [https://api.gbif.org/v1/vocabularies/Pathway/]} |
Should the Source Authority (API) be "https://api.gbif.org/v1/vocabularies/Pathway/concepts"? |
I think https://api.gbif.org/v1/vocabularies/Pathway/concepts is OK as a source authority because it actually has an API as long as it is understood that the actually vocabulary is maintained at https://dwc.tdwg.org/pw/ and the GBIF API is expected to remain up to date with that. |
Changed Source Authority from bdq:sourceAuthority default = "Pathway Controlled Vocabulary List of Terms" {[https://dwc.tdwg.org/pw/]} {GBIF vocabulary API [https://api.gbif.org/v1/vocabularies/Pathway/concepts]} to bdq:sourceAuthority default = "GBIF Pathway Vocabulary" [https://api.gbif.org/v1/vocabularies/Pathway]} {"dwc:pathway vocabulary API" [https://api.gbif.org/v1/vocabularies/Pathway/concepts]} |
This was correct before the change. Darwin Core has the formal recommended vocabulary. |
Reverted Source Authority |
See #275 (comment) The GBIF API does not help here, it does not provide the actual Controlled Values from the TDWG vocabulary, the values it has differ in case. |
GBIF vocabulary has now been aligned with Darwin Core. Thanks @timrobertson100 |
…ocabulariy. Adding a first cut at an implementation for tdwg/bdq#277 VALIDATION_PATHWAY_STANDARD, using the GBIF vocabulary API by default, instead of the Darwin Core vocabulary, along with unit test.
…o evaluate LSIDs and UUIDs, lookups from GBIF vocabulary for several terms and storage for access in a singleton. Completed all but one stub unit test, commented that one for build. Implementations include tdwg/bdq#75 tdwg/bdq#115 tdwg/bdq#277 tdwg/bdq#285.
The text was updated successfully, but these errors were encountered: