Have read the text and the extended is used in the smLink but I see that the type attribute isn't in the mets schema so there is more needed to be done in that case.
It looks like we are specifying a list of allowed attributes directly in the METS schema for smLink rather than one of the XLink attribute groups from http://www.loc.gov/standards/xlink/xlink.xsd. It seems like the intention is that it have xlink:type="arc", but smLink also requires the xlink:from and xlink:to despite those being optional in the XLink spec (https://www.w3.org/TR/xlink11/#xlinkattusagepat).
I'm not sure what the best way to get the default value for xlink:type="arc" or even just to require xlink:type at all for smLink is while still retaining xlink:from and xlink:to as required attributes. The easiest option might just be to allow xlink:from and xlink:to to be optional on smLink; then we could remove all the explicitly-declared XLink attributes for smLink in the METS schema and just add the xlink:arcLink attribute group.
@karinbredenberg reports:
It looks like we are specifying a list of allowed attributes directly in the METS schema for
smLink
rather than one of the XLink attribute groups from http://www.loc.gov/standards/xlink/xlink.xsd. It seems like the intention is that it havexlink:type="arc"
, butsmLink
also requires thexlink:from
andxlink:to
despite those being optional in the XLink spec (https://www.w3.org/TR/xlink11/#xlinkattusagepat).I'm not sure what the best way to get the default value for
xlink:type="arc"
or even just to requirexlink:type
at all forsmLink
is while still retainingxlink:from
andxlink:to
as required attributes. The easiest option might just be to allowxlink:from
andxlink:to
to be optional onsmLink
; then we could remove all the explicitly-declared XLink attributes forsmLink
in the METS schema and just add thexlink:arcLink
attribute group.