Hi all, I am travelling at the moment and unfortunately won’t be able to join the meeting tonight.
All the best,
Peter
From: tdwg-humboldt <tdwg-humboldt-bounces@lists.tdwg.org>
On Behalf Of Baskauf, Steven James
Sent: Sunday, 17 September 2023 5:33 AM
To: tuco@berkeley.edu; Tim Robertson <trobertson@gbif.org>
Cc: Wesley M. Hochachka <wmh6@cornell.edu>; Humboldt Core TG <tdwg-humboldt@lists.tdwg.org>
Subject: Re: [tdwg-humboldt] Taxon Completeness Reported Controlled Vocabulary List of Terms
Just a FYI, there are JSON and CSV representations of the English and translated ratified controlled vocabularies at
https://tdwg.github.io/rs.tdwg.org/translations/
The English CSV files are generated as part of the scripted process for populating the server that handles redirects and delivery of the machine-readable RDF representations. So they are always
there and updated automatically. The translation CSV files were constructed manually. Many were done at that translation workshop that we had at TDWG a couple of years ago. The subjectPart and subjectOrientation CVs were translated prior to adoption by the
task group.
The JSON files are generated by a Python script from the above-mentioned CSVs for each CV. But they don’t contain any information more than the CSVs and have to be generated by running the script
as a separate step.
I would like us to encourage the creators of new vocabularies to provide translations at the time of ratification if possible, at least for the most widespread languages (i.e. Spanish, French,
etc.). But that’s contingent on having someone who can actually do the translations…
Steve
--
Steven J. Baskauf, Ph.D. he/him/his
Data Science and Data Curation Specialist / Librarian III
Jean & Alexander Heard Libraries, Vanderbilt University
Nashville, TN 37235, USA
Biodiversity Information Standards (TDWG) Executive Committee/Technical Architecture Group Chair