Following up on a discussion on Twitter where someone asked me and @ruthtillman about this, there is a need for documentation for how to validate EAD3 files. In particular, we need to clarify the role of the namespace (http://ead3.archivists.org/schema/) vs. the file path for the schema.
Lots of people are accustomed to validating EAD 2002 against the copy of the schema or DTD hosted at loc.gov. Now that we are hosting the code at GitHub, it is possible to validate against that copy (to which the namespace redirects), but it might be wiser to host a copy oft he schema locally.
Validation declarations in EAD instances vary from XSD, RNG, and DTD - we should clarify that as well. Would also be helpful to provide some guideance on creating Oxygen validation scenarios, especially on incorporating the ead3.sch Schematron.
For @karinbredenberg and Kathy to take up when we get TS-EAS organized.
Following up on a discussion on Twitter where someone asked me and @ruthtillman about this, there is a need for documentation for how to validate EAD3 files. In particular, we need to clarify the role of the namespace (http://ead3.archivists.org/schema/) vs. the file path for the schema.
Lots of people are accustomed to validating EAD 2002 against the copy of the schema or DTD hosted at loc.gov. Now that we are hosting the code at GitHub, it is possible to validate against that copy (to which the namespace redirects), but it might be wiser to host a copy oft he schema locally.
Validation declarations in EAD instances vary from XSD, RNG, and DTD - we should clarify that as well. Would also be helpful to provide some guideance on creating Oxygen validation scenarios, especially on incorporating the ead3.sch Schematron.
For @karinbredenberg and Kathy to take up when we get TS-EAS organized.