Consider a rule to ensure that @...Encoding attributes are present and linked to <conventionDeclaration>

[kerstarno]

Creator of issue

1. Kerstin Arnold
2. EAD team lead, TS-EAS
3. @kerstarno
4. kerstin.arnold@archivesportaleurope.net

The issue relates to

• [x] EAC-CPF schema issue
• [ ] EAC-CPF Tag Library issue
• [x] EAD schema issue
• [ ] EAD Tag Library issue
• [x] Schema issue
• [ ] Tag Library issue
• [x] Suggestions for all schemas
• [ ] Suggestions for all Tag Libraries
• [x] Other

Wanted change/feature

• Text: This feature request follows https://github.com/SAA-SDT/eas-schemas/issues/1. With the decision to define the use of value lists via @...Encoding attributes within <control>, it might be worth investigating and considering if this could be linked to a Schematron rule, especially if - as currently suggested - the vast majority of these @...Encoding attributes would be optional. Ideally there would be two checks:
• First, if any of the attributes that would require the definition of a value list via @...Encoding is used, there should be a check if this @...Encoding attribute indeed is present. E.g. if I use the @audience attribute, I need to have the @audienceEncoding attribute in <control>.
• Second, though I will admit that I'm not sure, if Schematron can be used in this case, it would be great if there could be a check that, in case the @audienceEncoding attribute (to stick with the example) is set to "otherAudienceEncoding", there indeed is a <conventionDeclaration> element that defines or references a definition of the values used for @audience. As there would be not prescribed way on how to encode this, though, it might not be possible to do this?

[kerstarno]

Adding @marieelia as eventually this might also apply to EAC-CPF given that it would be expected for EAC-CPF to also remove the predefined values from attributes and to use the @...Encoding attributes in <control> instead.