validate XML files using XSD files located in data/xsd
|Assignee:||Dan Gillean||% Done:|
|Target version:||Release 2.2.0|
|Google Code Legacy ID:||atom-837||Tested version:||2.2, pre-1.2|
When importing a XML file that uses a relative path to the DTD in its
DOCTYPE declaration (best practice for EAD), it looks for the file in the
/web directory. Qubit needs to maintain copies of supported DTDs in a
/data/dtd directory and update the XML Import code to look for it there.
[g] Legacy categories: EAD, Import/Export
#1 Updated by Peter Van Garderen almost 13 years ago
- Subject set to validate XML files using XSD files located in data/xsd
- File qubit_xsd_validation.patch added
The attached patch bypasses the validation check (see patch line 49) that MJ created
for the XML import class (this stops the XML import from reporting that it did not
find the DTD).
The patch then also uses the ValidSchema array to match it to the appropriate import
file schema which is stored locally at /data/xsd/* and validate the schema (see patch
Unfortunately, there appears to be an issue with XSD validation in libxml < 2.7.3
which has not yet been packaged for Ubuntu (current release is 2.6). See the
For now, the temporary workaround will be to check in ead.dtd to /web which works
with existing code (i.e. will validate and report issues when importing EAD XML).
When Debian/Ubuntu upgrades the libxml package we need to revisit this issue by
applying the patch and validating xml import using schemas maintained in /data/xsd
#17 Updated by Dan Gillean about 7 years ago
- Status changed from QA/Review to Verified
- Tested version 2.2 added
Ironically, it seems that some of our EAD files will produce warnings when roundtripped and verified against the DTD - but we can handle that later, in a separate issue ticket, when we have time.
XSD files can be found in data/XSD; EAD DTD is in data/DTD.