Create a separate section for elements established as entities

[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: In reviewing EAD, the conceptual approaches to its elements and its relation to Records in Contexts, the EAD sub-team has concluded that there are three types of entities, currently encoded as part of descriptive information, which should rather be emphasised as related entities of certain importance. That importance results from EAD's relation with its sibling standard EAC-CPF (referring to the element <agent> (Establish <agent> more as a related entity rather than a piece of descriptive information #58)), with the standard for functions (currently under development by TS-EAS and referring to the element<function> (Establish <function> more as a related entity rather than a piece of descriptive information #61)), and with standards such as Records in Contexts or PREMIS, but also standards from related cultural heritage domains that include the concept of instantiations, representations, manifestations, or expressions of the "thing" being described (new element <formAvailable> (Add new element <formAvailable> to encode any type of instantiations of the materials described #65)). to represent this entity of instantiations is to be established, combining the three current elements.
• To emphasise these three elements and the related entities they represent, the EAD sub-team has decided during their meeting on 15 December 2023, that these elements should be moved from their current place within the EAD structure and that there should be a dedicated section for them in the definition of <archDesc> and numbered and unnumbered <c> elements.

Note for working on and testing this issue: When the schema changes are done in 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 and - if applicable - the intermediate levels (printed in italics).

• Adapt the definition of <archDesc> and numbered and unnumbered <c> elements to the following structure
  • Have <identificationData> as required and not repeatable sub-element (as it already is in EAD3)
  • Add the plural elements <agents>, <formsAvailable>, and <functions> as optional and not repeatable
    • The concept of plural elements is new in EAD, but adopting the approach already known from EAC-CPF
    • <agents> requires at least one <agent> sub-element and allows for an optional <descriptiveNote> as sub-element
    • <formsAvailable> requires at least one <formAvailable> sub-element and allows for an optional <descriptiveNote> as sub-element
    • <functions> requires at least one <function> sub-element and allows for an optional <descriptiveNote> as sub-element (<functions> hereby becomes a shared element between EAD and EAC-CPF
    • All three plural elements allow for the optional attributes @audience, @id, @target, @languageOfElement, @scriptOfElement, @localType, @localTypeDeclarationReference, @maintenanceEventReference, @sourceReference, @conventionDeclarationReference, and the option to include attributes form any other namespace
  • Have the following elements allowing for longer descriptive texts as optional and repeatable
    • <otherFindAid>, <publicationNote> (renamed from <bibliography>, Rename certain elements for better alignment with ISAD(G), DACS, etc. respectively for being better understandable #66), <relatedMaterial>, <separatedMaterial>, <accessConditions> (renamed from <accessrestrict>, Rename <accessrestrict> and <userestrict> and update their content model #60), <useConditions> (renamed from <userestrict>, Rename <accessrestrict> and <userestrict> and update their content model #60), <accruals>, <sourceOfAcquisition> (renamed from <acqInfo>, Rename certain elements for better alignment with ISAD(G), DACS, etc. respectively for being better understandable #66), <appraisal>, <arrangement>, <biogHist>, <custodHist>, <filePlan>, <otherDescriptiveInfo> (renamed from <odd>, Rename certain elements for better alignment with ISAD(G), DACS, etc. respectively for being better understandable #66), <physicalOrTechnicalRequirements> (renamed from <physTech>, Rename certain elements for better alignment with ISAD(G), DACS, etc. respectively for being better understandable #66), <preferCite>, <processInfo>, <scopeContent>, and <subjectHeadings> (replacing <controlAccess> and <index>, Rename <controlaccess> to <subjectHeadings> and combine with <index> #67); (note: for <legalStatus> see Align content model of <legalStatus> with EAC-CPF 2.0 and move it into <did> #5)
  • Have <descriptionOfComponents> as optional, not repeatable sub-element for <archDesc> and <c> respectively <c02>, <c03>, etc. as optional and repeatable sub-elements for unnumbered and numbered elements
    • Remove <thead> as optional sub-elements of numbered and unnumbered <c> elements

[fordmadox]

Just a note that I'd like to discuss the name "formsAvailable", as I think that there might be a better choice for that one.

[fordmadox]

I took a shot at adding this. Just let me know what still needs to be changed.

[kerstarno]

Tested with the XSD and the RNG and can confirm that the above has been implemented as described.