kerstarno
commented
1 month ago EAD team discussed this issue during their meeting on 24 May 2024.
While there was a tendency to agree with the suggestion of adding @base to <agents>, <formsAvailable>, <functions>, and <places>, the general question of active usage of @base was brought up as well. Furthermore, the point was raised that - theoretically - users of EAD 4.0 could apply @xml:base following the new possibility to include attributes from other namespaces, even if EAD 4.0 would not add @base here - or, potentially, remove @base completely.
To get a better understanding of whether or not @base is used by the community at the moment - or might be used in future - and in which scenarios, this question will be raised during the open drop-in sessions on 18 June and 9 July. A final decision will be taken after that.
Creator of issue
The issue relates to
Wanted change/feature
@baseis currently available in<eac>,<ead>,<control>(both EAS),<archDesc>,<cpfDescription>,<multipleIdentities>,<identity>,<description>,<sources>(both EAS),<relations>(both EAS),<alternativeSet>, and the numbered and unnumbered<c>elements. The intent for this attribute is to provide a base URI/URL, which applies to all URIs/URLs used within the sub-elements of the elements listed above, as to then only include relative URIs/URLs with those sub-elements.@basewith<daoset>, which has been replaced by<formsAvailable>in EAD 4.0. Depending on the active usage of@baseby the community, it might make sense to enable@baseas an optional attribute with<formsAvailable>as well. In that case, it should be considered to do the same for<agents>,<functions>, and<places>. As the latter two are also used in EAC-CPF and form part of a group of plural elements that are all defined in the same way, such decision should then also be considered for these two - and potentially the other plural - elements in EAC-CPF, too.