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. This schema allows XML authors to extend container elements with any data deemed necessary for the particular context, e.g., pagination data. 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/ These attributes intended to contextualize and/or uniquely identify root elements. When an XML instance derives from a HTTP request, use a combination of @uri and @accessDate, where @uri is the absolute URL of the request (including the query string) and @accessDate is the current ISO 8601 date. When an XML instance derives from other sources, such as a script outside the Web context, use a tag URI: http://taguri.org/