eBank Terms XML Schema Created 2004-03-19 Created by Monica Duke (m.duke@ukoln.ac.uk). Encoding schemes are defined as complexTypes which are restrictions of the dc:SimpleLiteral complexType. These complexTypes restrict values to an appropriate syntax or format using data typing, regular expressions, or enumerated lists. In order to specify one of these encodings an xsi:type attribute must be used in the instance document. Also, note that one shortcoming of this approach is that any type can be applied to any of the elements or refinements. There is no convenient way to restrict types to specific elements using this approach. *** Changes *** Modified 2008-04-29 to update location of ebank schema Modified 2006-03-10 to update location of imported dc schemas. Modified 2006-02-05 to add keywords as the list of types for dc:subject and added DOI as a specific type of identifier i.e. as an encoding scheme for identifier. Modified 2005-08-08 to remove the complex types CCDC and Empirical Formula and to change IUPAC to InChI. Modified 2005-06-17 to add a ValidationDataset to eBankDataset Types and ChemicalFormula to the complex types Modified 2004-06-11 to change to 20030402 dc schema for use with qualified dc. dc Schema location changes to http://www.dublincore.org/schemas/xmls/qdc/2003/04/02/dc.xsd Corrected case of compoundclass to CompoundClass, empiricalFormula to EmpiricalFormula, and ebankDatasetType to EbankDatasetType organic to Organic, inorganic to Inorganic, organometallic to Organometallic and bio-organic to Bio-organic. initialisationDatase to InitialisationDataset, refinementDataset to RefinementDataset, collectionDataset to CollectionDataset, processingDataset to ProcessingDatset solutionDataset to SolutionDataset, refinementDataset to RefinementDataset This group is included as a convenience for schema authors who need to refer to all the DC elements and element refinements in the http://purl.org/dc/elements/1.1/ and http://purl.org/dc/terms namespaces. N.B. Refinements available via substitution groups. This is included as a convenience for schema authors who need to define a root or container element for all of the DC elements and element refinements.