Schema defining metadata corresponding to all levels of the DAITSS ArchiveEntity object hierarchy and to all other metadata defined in the DAITSS database (e.g. relationships, events,...). The schemas, like DAITSS ArchiveEntity objects and subclasses, are hierarchical. For example, a schema exists for metadata at the DataFile level, another schema exists for the more specific Bitstream level, and another for the Bitstream type level (e.g. TiffImage). The primary purpose for these schemas is for metadata redundnacy within DAITSS. The intent is that all metadata stored in the DAITSS database will also be stored in an XML-based format. When possible, occurrence, integrity (referential), and format constraints will be replicated in the schema as they appear in the DAITSS database. Defualt values, however, will not be represented in the schemas - values must be provided explicitly. Currently the DAITSS namespace will be used in <xmlData> sections within a METS instance document. Since redundancy is the goal, the naming convention for elements and attributes (if applicable) will be the same as that in the DAITSS database. Type names (for simple and complexTypes defined in the DAITSS namespace) will follow the naming convention used for class names in the DAITSS object architecture (which is the standard Java class naming convention). The daitss namespace is defined using a hierarchical arrangement of xml-schema documents. At the top of the hierarchy is this document which defines the <daitss> root element which may contain an arbitrary number of subelements. Each subelement is named for a table in the daitss database and contains the complete set of elements that represent fields of the table. The convention being used here is that element names should only be defined at the namespace root and table levels. Types are only defined at these levels if they are referenced locally (local to the xml-schema document in which it was defined) or if the type represents a primary key that is referred to using a foreign key. Types with a global scope are defined in separate documents that are divided by general data type (e.g. daitssString, daitssNumber,...). Element names should not be specified at this level to more easily accomodate field name changes in the database. This convention also prevents elements from being used out of context. Each schema at this level should be included (using the xml-schema <included> element) in the daitssDataTypes schema which in turn is the only schema to be included in the table-level schemas. This document should include all table-level schemas and is the only document required to be referenced (in the schemaLocation attribute) by instance documents. Type definition for the root element of the daitss namespace. The element may contain an arbitrary number of subelements in any order with each subelement representing a complete entry in a table of the daitss database.