This represents the final release of EAD 2002 issued by TS-EAS, mainly looking at resolving the various ISO codes (country, language, script) that were part of the schema to being of type NMTOKEN, i.e. allowing nearly any content in the related attributes. The update only relates to the RNG and the XSD versions of the schema. The DTD remains unchanged.
The EAD 2002 Schema is available in two syntaxes: Relax NG Schema (RNG) and W3C Schema (XSD).
Note: Comments, questions, and error reports should be sent to the EAD listserv with the subject line: Schema Comment
Listserv address: [email protected]
The RNG version is the maintenance and therefore authoritative version. The XSD version is derived from the RNG using Trang, with minor manual editing subsequent editing.
EAD DTD / SCHEMA RELATIONSHIP
With one exception (XLink elements and attributes), the EAD Schema is a subset of the EAD 2002 DTD.
The Xlink compatible elements and attributes in the DTD have been made compliant by implementing XML Namespace. As a result, DTD compliant instances containing ANY of the XLink tags and attributes will not validate against the Schema. These instances must be converted into XLink compliant tags and attributes. The EAD Schema WG has provided an Alpha XSLT for this conversion. A parameter on line 51 allows the user to specify whether the resulting schema should have RNG or W3C addressing information:
Instructions for Using dtd2schema.xsl (PDF file, 2 p.)
The following elements and their XLink-specific attributes are impacted by this change:
For example, the following DTD compliant tag:
Must be converted to the following:
Do note also that while RNG does support external entities, XSD does not. Thus @entityref must be resolved and converted to @xlink:href on XLink "locator" tags. Do note also that @xlink:href is a required attribute on XLink "locator" tags, and thus using RNG will require the presence of this attribute on the relevant tags.
With the exception of the XLink tags and attributes, a Schema valid instance will be a DTD valid instance. However, because of the imposition of datatype contraints on specific attribute values, a DTD valid instance may not be Schema valid.
The following attributes are impacted by the imposition of datatype constraints:
@normal on <unitdate> and <date>: constrained
to date and date range subset of ISO 8601
In preliminary testing, many of the attribute values intended by encoders to be compliant with each relevant ISO standard were found to be incorrect. Thus scriptcode="latn" for the Latin script is incorrect. The correct code for the Latin script is "Latn". The case of the character matters!!
Attribute validations errors indicate that the attribute value does not conform to the ruling ISO standard.
Publisher: Society of American Archivists and the Library of Congress
Funding: National Historical Publications and Records Commission
Editors (SAA/EADWG/EAD Schema Working Group):
Francoise Bourdon (Bibliothèque
nationale de France)
March 29, 2022