Skip to content

Changes requested by Russian Federation in response to Ballot N6268#11

Open
nicholascar wants to merge 11 commits into
mainfrom
LanguageCode-WorldAtlasAdditions
Open

Changes requested by Russian Federation in response to Ballot N6268#11
nicholascar wants to merge 11 commits into
mainfrom
LanguageCode-WorldAtlasAdditions

Conversation

@nicholascar

@nicholascar nicholascar commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

These changes have been requested by the Russian Federation in response to CIB N6268 asking for proposed changes.

The technical change - this Pull Request - was formulated by GOM but will be put to the ISO 19115 Working Group as the Control Body of ISO19115-1 within which the target Code Set - Language Code - sits.

The complication with this proposed change is that this Code Set is derived from ISO 639-2 which is not an TC-211-managed standard, so we cannot unilaterally alter this Code Sets if values are to remain identical to that external source.

@nicholascar nicholascar self-assigned this Jul 2, 2026
@PeterParslow

Copy link
Copy Markdown

I agree that is a complication. I don't think ISO/TC 211 can change the values when all we set out to do was provide a web friendly version of the ISO 639-2 values. Personally, I believe GOST should take this up with the ISO 639-2 Maintenance Agency, although their reference to UNESCO might suggest they already have?

In the meantime, the ISO 639-2 MA (US Library of Congress) have now done the job - each code has a URI like http://id.loc.gov/vocabulary/iso639-2/abk

So perhaps we can withdraw this code set from our platform?

@nicholascar

Copy link
Copy Markdown
Contributor Author

So perhaps we can withdraw this code set from our platform?

If the 19115 Control Body trusts the LoC listing of 639-2 then I suppose you could. If you did so, we could drop the Code Set here but then you would need to indicate how to use the LoC version in the standard. We could eventually compliment this with an example of use of those IRIs in the GOM ontology version of 19115 which we should have a reasonable copy of within a month or two.

@PeterParslow If you do want to drop the vocab, please just put in another PR here and I will indicate that PR invalidates this one and I will tag it and this one in some way to indicate they are relevant to 19115 - more than just containing that string of characters in text!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants