Closed rockivist closed 9 years ago
Looking at this more closely, I think we should add @base
to a few more elements. Within EAC-CPF, @xml:base
is available on <alternativeSet>
, <control>
, <cpfDescription>
, <description>
, <eac-cpf>
[the root element], <identity>
, <multipleIdentities>
, <relations>
, and <sources>
. That includes all of the major sections of the document and each of the two elements that wrap multiple links. I think we should follow that general rule and include @base
on the following: <ead>
, <control>
, <archdesc>
, <daoset>
, <relations>
, and <sources>
.
Kerstin also suggested adding @base
to the component elements, which I agree could be useful.
Implemented in my mike_post_gamma_3 branch per TS-EAD feedback (and lack of objections).
To be clear, @base
is now available on the following elements:
ead control archdesc daoset relations sources c c01-c12
Assigning to @kshepher for documentation review.
TL updated.
The
@base
attribute is taken from EAC and currently available on control, sources, and relations. The attribute definition, from the EAC tag library, is as follows: "@xml:base
is used to specify the base URI other than the base URI of the EAC-CPF instance, for the purpose of resolving any relative URIs used with elements that contain one or more descendants that use an attribute of type anyURI.@xml:base
makes it possible to declare an absolute base URI to facilitate the use of relative URIs on the descendants."Given that
<daoset>
is designed to bundle two or more digital objects, I think it makes sense to add@base
to that element as well. This would allow for relative@href
values on the<dao>
s wrapped by a given<daoset>
on which a@base
URI has been specified.