kerstarno
commented
8 months ago Tested with the XSD and the RNG. Apart from @localType and @localTypeDeclarationReference currently missing from <agent>, all the above changes are implemented as expected.
I have created a pull request with this change (#84). Once this has been merged and the schemas have been generated anew, this issue will need another quick round of testing.
Creator of issue
The issue relates to
Wanted change/feature
@agentRoleto<agent>. This will not only help to differentiate e.g. between an employee and a volunteer when used in the context of<maintenanceEvent>, but also to differentiate between the author, publisher, and possibly sponsor when used in the context of<findAidDesc>. Also applies to EAC-CPF.~<agent>as discussed and confirmed by the EAD sub-team during their meeting on 15 December 2023.<agent>, along with<function>(#61) and<formAvailable>(#65), is to be established more as a related entity rather than a piece of descriptive information. It will be made available in a new and dedicated part of the archival description part of EAD (#68), apart from already being available in<findAidDesc>(#27) and in<control>under<maintenanceEvent>(#32).<agent>will combine and replace all current elements that refer to an agent as a related entity, i.e.<origination>and<repository>, but also<corpname>,<famname>,<name>, and<persname>as sub-elements of<controlaccess>and<index>(for the changes in the latter two see #67).Note for working on and testing this issue: When the schema changes are done in development branch, please mark the tasks on the highest levels of the list (printed in bold) by ticking the box. When the changes have been tested successfully, please mark the tasks on the lowest level of the list.
@agentRoleas an optional attribute to<agent>~@agentRoleof data type "token"~<agent>as follows:<agent>cannot include text<agent>includes<agentName>as a required and repeatable sub-element<agent>includes<agentType>and<agentRole>as optional and repeatable sub-elements<agentName>,<agentRole>, and<agentType>all have the same content model by allowing the elements to contain text, by enabling the optional attributes@audience,@id,@target,@languageOfElement,@scriptOfElement,@conventionDeclarationReference,@maintenanceEventReference,@sourceReference,@localType,@localTypeDeclarationReference,@valueURI,@vocabularySource, and@vocabularySourceURI, and by allowing for attributes from any other namespace<agent>includes<relationType>as a optional and repeatable sub-element<agent>allows for the optional sub-elements<date>,<dateRange>, or<dateSet>(choice between these three, not repeatable),<placeName>(repeatable), and<descriptiveNote>(not repeatable)<agent>allows for the optional attributes@audience,@id,@target,@languageOfElement,@scriptOfElement,@conventionDeclarationReference,@maintenanceEventReference,@sourceReference,@localType,@localTypeDeclarationReference,@valueURI,@vocabularySource, and@vocabularySourceURI<agent>allows for attributes from any other namespace<agent>is a required and repeatable sub-element of<agents>(#68), a required, not repeatable sub-element in<maintenanceEvent>(#32) and an optional and repeatable sub-element in<findAidDesc>(#27)As a result of the above:
<origination>from EAD<repository>from EAD<corpname>from EAD<famname>from EAD<name>from EAD<persname>from EAD