This schema provides a fluent template for building non-web-centric Omeka XML instances, while minimizing Omeka-specific metadata. The root element can be most any derivation of Omeka, from multiple Omeka repositories to an individual item, file, or elementText. This schema avoids redundancy with a liberal use of @minOccurs="0", which, if used properly, will prevent unnecessary recursion (e.g. an item refs a collection, which refs an itemContainer, which contains the original item, etc.). It is up to the XML author to include only the data needed for a particular XML instance. An elementSet may contain an elementContainer OR any other XML format that accurately represents the element set. For example, an element set may contain the Dublin Core elements OR a dcmes-xml Dublin Core RDF format defined here: http://dublincore.org/documents/dcmes-xml/ This type must conform to the following tag URI format: "tag:" DNSname "," yyyy "-" mm "-" dd ":repository" See here: http://taguri.org/