Articulation with RiC: <date> as a separate entity (RiC-E18), similar to <place>

[BrigitteMichel]

Creator of issue

1. Brigitte Michel (michel@abes.fr)
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
• [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: We should consider <date> as a separate entity (in line with RiC-E18), similar to <place>.
• It should also benefit from child elements <dateType> and <dateRole> and accept <relationType>.
• It would then make sense to remove the <eventDateTime> element in favour of <date> with a <dateType> that could be 'date of maintenance event': <date> would then be a required child of <maintenanceEvent>.

Context

• Text: WT EAD-b (for all libraries in France), including National Library (BnF) has defined a list of controlled values for the TYPE attribute of <date> in EAD 2002.

[kerstarno]

Might be discussed by TS-EAS during their meeting on 12/13 August 2024 if time allows (i.e. if other discussion points can be solved in less time than anticipated. Otherwise, the EAD team will pick this up at their next monthly meeting end of September.

[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.