Closed karinbredenberg closed 4 years ago
In their meeting on 23 September 2019, TS-EAS EAD team decided that this bug should be corrected. Issue is therefore assigned to the leads of the Schema team for next steps.
Just a note that I've checked into this issue, and it happens due to the "deglobalize.xsl" transformation process.
@tcatapano : i plan to set up a test before making any changes, but do you remember exactly why that step was necessary?
@fordmadox: it's been a while, but per the comment at https://github.com/SAA-SDT/EAD3/blob/2f4f1d7bfe35ffd171260d8b1177e5bb0616a86f/inprocess/deglobalize/deglobalize.xsl#L14 the main function of the deglobalize.xsl transformation is to wrap definitions of any element not named 'ead' which is a child of 'xsd:schema' in 'xsd:complexType' elements so that they will not be available as root elements. It's basically a cleanup of the result of the trang conversion from rng.
Thanks, @tcatapano! I'll keep that in mind when I add a patch for this issue.
Closing this out since the change has been merged.
Creator of issue
The issue relates to
Reporting a bug
<c12>
element is not validating against the EAD3 schema. You caninsert the
<c12>
element, but no child elements can be used.We looked into the schema (ead3.xsd) and it looks like
<c12>
wasn't defined.The other component levels read something like this:
`