Add "iso3166-2" as a value for @countryEncoding and replace "iso639-2" with the more specific options "iso639-2b" and "iso639-2t" for @languageEncoding

[BrigitteMichel]

Creator of issue

1. Brigitte Michel (michel@abes.fr)
2. Abes (Agence bibliographique de l'enseignement supérieur = Bibliographic Agency of Higher Education) 3.for WG EAD in french libraries (gt-ead-b@listes.abes.fr)

The issue relates to

• [ ] EAC-CPF schema issue
• [ ] EAC-CPF Tag Library issue
• [x] EAD schema issue
• [x] EAD Tag Library issue
• [ ] Schema issue
• [ ] Tag Library issue
• [ ] Suggestions for all schemas
• [ ] Suggestions for all Tag Libraries
• [ ] Other

Wanted change/feature

• Text: One must be able to legitimately use the different variants of ISO international standards.

Suggested Solution

• Text: Thus, the ISO3166-2 value must be authorized in the @countryEncoding attribute of <control> and the values iso639-2b or iso639-2t in the @languageEncoding attribute of <control>, as well as in @languageOfElement attributes.

Context

• Text: Indeed, "Note: ISO 639-2 is the alpha-3 code in Codes for the representation of names of languages-- Part 2. There are 21 languages that have alternative codes for bibliographic or terminology purposes. In those cases, each is listed separately and they are designated as "B" (bibliographic) or "T" (terminology). In all other cases there is only one ISO 639-2 code. Multiple codes assigned to the same language are to be considered synonyms. ISO 639-1 is the alpha-2 code." (source: https://www.loc.gov/standards/iso639-2/php/code_list.php)
• Most libraries use ISO 639-2b and systems must be able to automatically detect the correct version to ensure interoperability (e.g. MARC21: https://www.loc.gov/standards/sourcelist/language.html).

[kerstarno]

As a note, if approved "iso639-2b" or "iso639-2t" would only become possible values in the @languageEncoding, but not in @languageOfElement. The latter would only hold specific values from the list defined in ISO 639-2b and ISO 639-2t respectively.

[kerstarno]

Will be discussed by TS-EAS at their meeting on 12/13 August.

[kerstarno]

Not discussed eventually during the TS-EAS meeting on 12/13 August due to time constraints. Will now be on the agenda at the EAD team meeting either in September or October 2024.