Update the modelling of languages in EAD to align with EAC-CPF

[kerstarno]

Creator of issue

1. Kerstin Arnold
2. EAD team lead, TS-EAS
3. @kerstarno
4. [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

• Text: Update the modelling of languages in <languageDeclaration> and in <langmaterial> to align with EAC-CPF.

Note for working on and testing this issue: When the schema changes are done in the respective development branch, please mark the tasks on the highest levels of the list (printed in bold) by ticking the box. When the changes have been tested successfully, please mark the tasks on the lowest level by ticking the box.

• For <languageDeclaration> see Align <control> across EAD and EAC-CPF #32
• For <language>
  • Adapt @audience (see Remove fixed value lists #1)
  • Rename @lang and @script to @languageOfElement and @scriptOfElement respectively (see Adapt @lang and @script to @languageOfElement and @scriptOfElement and align usage with EAC-CPF #30)
  • Add @target (see Add @target to all elements except <ead> #31) (optional)
  • Add @conventionDeclarationReference, @maintenanceEventReference, @sourceReference (see Add @conventionDeclarationReference, @maintenanceEventReference, and @sourceReference to EAD #11) (optional)
  • Rename @langcode to @languageCode
  • Add option to include attributes from any other namespace (see Add option to include attributes from any other namespace to all elements of EAD #28)
  • Remove @altrender, @encodinganalog, and @label
• For <languageset>
  • Apply camelCasing and rename to <languageSet>
  • Replace <script> with <writingSystem>
  • Adapt @audience (see Remove fixed value lists #1)
  • Rename @lang and @script to @languageOfElement and @scriptOfElement respectively (see Adapt @lang and @script to @languageOfElement and @scriptOfElement and align usage with EAC-CPF #30)
  • Add @target (see Add @target to all elements except <ead> #31) (optional)
  • Add option to include attributes from any other namespace (see Add option to include attributes from any other namespace to all elements of EAD #28)
• Remove <script> and add <writingSystem>
  • <writingSystem>...
    • Can have text
    • Includes @audience (optional)
    • Includes @id (optional)
    • Includes @target (optional)
    • Includes @languageOfElement (optional), changed from @lang in <script>
    • Includes @scriptOfElement (optional), changed from @script in <script>
    • Includes @maintenanceEventReference (optional)
    • Includes @sourceReference (optional)
    • Includes @conventionDeclarationReference (optional)
    • Includes @scriptCode (optional), changed from @scriptcode in <script>
    • Can include attributes from any other namespace
    • Does not include @encodinganalog nor @label anymore

[fordmadox]

Should be ready to test, though I haven't looked at this in a while.

[deletedname]

All but Add option to include attributes from any other namespace tested and worked (Issue #28). @fordmadox I'm not sure how to test this particular issue with my very old version of oXygen.

Some overall notes:

• In EAD, <language> is a sub-element of <languageOfMaterial>. In EAC-CPF, <language> is a sub-element of <languageUsed>.
• The following attributes require a defined @id to successfully validate: @conventionDeclarationReference, @maintenanceEventReference, @sourceReference and @target.

[kerstarno]

@deletedname -
Hi Iris, just picking up on the question around testing for the attributes from other namespaces. The following works with my Oxygen version 20, so hopefully it'll work with your older version as well:

• I tend to use the XLink namespace for testing this
• For the XSD schema testing, I add @xmlns:xlink="http://www.w3.org/1999/xlink" to <ead> and I include "http://www.w3.org/1999/xlink http://www.loc.gov/standards/xlink/xlink.xsd" into the @xsi:schemaLocation attribute that already holds the EAD4 schema location
  • Then I am able to e.g. add @xlink:href="" to any element and the file still validates (note that the attribute doesn't actually need to have a value)
• For the RNG schema testing, I add the reference to the XLink namespace directly to the element that I want to check, i.e. I add @xmlns:xlink="http://www.w3.org/1999/xlink" and then @xlink:href="" for example to the <language> element
  • Again, the file still validates

[deletedname]

Thank you @kerstarno! The RNG and XSD files have been tested successfully.