This proposal is part of the 2.03 upgrade process, please comment by replying below.
Standard
Activity and Organisation
Schema Object
All uses of @xml:lang attribute
Type of Change
Change Definition
Issue
Xml:lang references the generic XML spec which allows for a range of languages, locales, regions and scripts. It is used in our schema with a more limiting definition - specifying sole use of ISO 639-1. This is not enforceable. Moreover, there are users who need to specify languages that aren’t on the ISO 639-1 list, but can be specified with BCP 47.
Proposal
Change all definitions of xml:lang
- From ISO 639-1 code specifying the language of text in this element.
- To A code specifying the language of text in this element.It is recommended that wherever possible only codes from ISO 639-1 are used.
Standards Day
Accepted
Links
This change makes the xml:lang definition consistent with the fact the language codelist is complete="0". So I don’t see it as redundant.
That said, this isn’t my proposal and I have no strong feelings either way.
So it does… redundant probably isn’t the best term.
Looking at this again, there are currently multiple definitions for valid values within the xml:lang attribute:
Looking at how these interact…
At present, there is no documented manner in which contradictions within the IATI Standard should be resolved. I would premise that the more permissive of valid interpretations of the contradicting statements be deemed the correct interpretation of the IATI Standard.
Based on the above, this proposal does not need to go through the 2.03 upgrade process, and should instead be implemented as a backwards-compatible bug fix.
Separately, the auto-generated documentation stating presence on Codelists should be fixed to take into account the complete attribute.
Ace – sounds good to me.