Derive the ISO 639 sets from the registration authority data - #106
Conversation
Signed-off-by: Juan Cruz Viotti <jv@jviotti.com>
🤖 Augment PR SummarySummary: This PR updates the ISO 639 language datasets so the published “sets” are derived directly from the official registration authority sources. Changes:
Technical Notes: Set 2 terminologic is generated as “bibliographic except for the ~20 divergent pairs”, and Set 5 now tracks the LOC ISO 639-5 vocabulary directly. 🤖 Was this summary useful? React with 👍 or 👎 |
| vendor/data/xbrl/utr/utr.xml https://www.xbrl.org/utr/utr.xml | ||
| vendor/data/iso/language/ISO-639-2_utf-8.txt https://www.loc.gov/standards/iso639-2/ISO-639-2_utf-8 | ||
| vendor/data/iso/language/iso-639-3_Code_Tables https://iso639-3.sil.org/sites/iso639-3/files/downloads/iso-639-3_Code_Tables_20251015.zip | ||
| vendor/data/iso/language/iso639-5.tsv http://id.loc.gov/vocabulary/iso639-5.tsv |
There was a problem hiding this comment.
The new ISO 639-5 source URL is plain http://; since https://id.loc.gov/vocabulary/iso639-5.tsv is available, sticking to HTTPS would avoid environments that block HTTP and provides transport integrity for vendored data downloads.
Severity: medium
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
There was a problem hiding this comment.
All reported issues were addressed
Not reviewed (too large): schemas/2020-12/iso/language/2023/set-2-terminologic.json (~3,939 lines), schemas/2020-12/iso/language/2023/set-2-bibliographic.json (~823 lines) - if these are generated or fixture files, add them to ignored paths to exclude them from future reviews.
Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.
Re-trigger cubic
Signed-off-by: Juan Cruz Viotti jv@jviotti.com