Clarify the meaning of "Role" as part of an element's or attribute's name - Githubissues

SAA-SDT / EAS-Best-Practices

The Encoded Archival Standards: Best Practice Guide is a resource that describes and provides explanations and examples of complex encodings and concepts in EAC-CPF and EAD. Created and maintained by SAA TS-EAS, the guide is intended to be a living resource that will be built on and developed over time.

https://saa-sdt.github.io/EAS-Best-Practices/

2 stars 4 forks source link

Clarify the meaning of "Role" as part of an element's or attribute's name #10

Open BrigitteMichel opened 1 month ago

BrigitteMichel commented 1 month ago

Creator of issue

Brigitte Michel (michel@abes.fr)
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: It seems that element names with Role (<placeRole>, <targetRole>, <agentRole>) are intended to encode a relationship. If this perception is correct, the name of the attribut @linkRole (already defined in EAC) is paradoxical because the definition clearly states that it is used to qualify the nature of the target rather than the relationship.

Suggested Solution

Text: It would be beneficial to have a vocabulary that avoids any confusion between what characterizes the nature and attributes (in the RiC sense) of an entity on one hand, and what characterizes a relationship on the other.

kerstarno commented 1 month ago

This seems to be more of a Best Practices Guide (and Tag Library) issue and has hence been moved.

This will be discussed by TS-EAS during their meeting on 12/13 August.