Language attributes: best practise

[SJagodzinski]

Best practise and recommendation for language attribute usage

Creator of issue

1. Silke Jagodzinski
2. TS-EAS: EAC-CPF subgroup
3. [email protected]

The issue relates to

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

Wanted change/feature

Best practise and recommendation for language attribute usage:

• language attributes @languageOfElement and @scriptOfElement are as optional attribues available in all elements that can contain text
• avoid language attribues in encoding examples for elements which technically can contain text, but expect identifier, codes or other non descriptive content:
  • Identifier elements: identityId, otherAgencyCode, otherRecordId, agencyCode, recordId
  • geographicCoordinates
• no language attributes in empty and non-text elements: entityType, objectXMLWrap
• use @scriptOfElement only if the script or writing system differs from the standard script of the language given in @languageOfElement or the standard script for a language is not explicit, e.g.
  • transliterations of names
  • until 1928 Turkish was written in an Arabic alphabet, that was replaced by the Latin alphabet
  • Sütterlin was use as handwriting script in Germany btw 1911 and 1940s

Context

EAC-CPF revision process