kerstarno
commented
1 year ago This mainly effects elements and attributes in the descriptive part of EAG, as the <control> section already uses camelCase spelling throughout in EAG 2012. Some element and attribute names will also be slightly changed in this context:
<repositorid>becomes<repositoryId>- While
<otherRepositorId>uses camelCasing already, it is in this context renamed to<otherRepositoryId>
- While
<buildinginfo>becomes<buildingInfo><repositorarea>becomes<repositoryArea><lengthshelf>becomes<lengthOfShelves><techservices>becomes<technicalServices><restorationlab>becomes<restorationLaboratory><reproductionser>becomes<reproductionServices>
Provide a general summary of the issue in the Title above. Delete the part of the issue template that does not apply depending on whether you describe a change to an existing element / attribute or the addition of a new one.
Creator of issue
State your name, organisation and ways to reach you. Name: Kerstin Arnold Organisation: Archives Portal Europe Foundation, Working Group on Standards Email: standards@archivesportaleurope.net GitHub username (if applicable): @kerstarno
Change in name
Indicate any changes in name. Throughout EAG 3.0, element and attribute names are to be used with camelCase spelling, i.e. if consisting of two or more words, the second and any following parts of the element and attributes names have to start with a capital letter. The same applies to any predefined lists of element contents and attribute values. EAG 2012 had implemented this inconsistently only with elements and attributes added as new back then, while keeping existing elements and attributes from EAG 0.2 with small letters.