Question : <legalstatus> / <legalstatuses>

[BrigitteMichel]

Creator of issue

1. Brigitte Michel ([email protected])
2. Abes (Agence bibliographique de l'enseignement supérieur = Bibliographic Agency of Higher Education)

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: Why, if <legalstatus> is repeatable, not also define <legalstatuses> in EAD (as in EAC)?

[kerstarno]

This was discussed by TS-EAS at several points during the major revision (last at the EAD team's virtual meetings on 24 November and 15 December 2023). Given the context of EAD and the history of the element in previous versions of EAD, adopting the full entities approach for <legalStatus> with a singular element wrapped in a plural element like in EAC-CPF seemed a non-required/unnecessary overhead.

There also are lots of other elements that can be repeated (essentially near-to-all elements can be repeated for multilingual support), where there is no wrapper element (plural or group/set) in order to join those repeated elements together. The draft of EAD 4.0 reserves the plural/singular approach for entity elements, i.e. <agent>, <formAvailable>, <function>, and <place>.

That being said: TS-EAS will discuss this once more during 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.