XML Schema : DataHistory.xsd
Target namespace: http://openmicroscopy.com/XMLschemas/DataHistory/IR3/DataHistory.xsd
Schema Comments:
Imports namespace:http://www.openmicroscopy.org/XMLschemas/OME/FC/ome.xsd schemaLocation: http://www.openmicroscopy.org/XMLschemas/OME/FC/ome.xsd
Processing Instructions
Schema has: 6element definitions,  0 global attribute definitions,  14 element attribute definitions,  0 datatype definitions.
Possible root elements: DataHistory

Element list

Element AttributeRef
 
diagram
description Reference to an attribute.
uses attributes AttributeRef/ID
 
used by elementsOutput
content sequence (default)
 
Attribute Datatype Use Values Default Comments
ID string required References an attribute by LSID or id local to document.
 
source
-<element name="AttributeRef">
-<annotation>
 <documentation>Reference to an attribute.</documentation>
 </annotation>
-<complexType>
-<attribute name="ID" use="required" type="string">
-<annotation>
 <documentation>References an attribute by LSID or id local to document.</documentation>
 </annotation>
 </attribute>
 </complexType>
 </element>

Element DataHistory
 
diagram
description Describes all known history of data.
uses elements ModuleExecution
 
content sequence
 
source
-<element name="DataHistory">
-<annotation>
 <documentation>Describes all known history of data.</documentation>
 </annotation>
-<complexType>
-<sequence>
 <element ref="DH:ModuleExecution" maxOccurs="unbounded" />
 </sequence>
 </complexType>
 </element>

Element ExecutionHistory
 
diagram
description
uses attributes ExecutionHistory/AttributeCreateTime, ExecutionHistory/AttributeSortTime, ExecutionHistory/ErrorMessage, ExecutionHistory/RunTime, ExecutionHistory/Status, ExecutionHistory/Timestamp
 
used by elementsModuleExecution
content sequence (default)
 
Attribute Datatype Use Values Default Comments
RunTime string required How long the module took to run.
Timestamp string required When the module was executed.
Status string required
ErrorMessage string optional (default)
AttributeCreateTime string optional (default)
AttributeSortTime string optional (default)
 
source
-<element name="ExecutionHistory">
-<complexType>
-<attribute name="RunTime" use="required" type="string">
-<annotation>
 <documentation>How long the module took to run. </documentation>
 </annotation>
 </attribute>
-<attribute name="Timestamp" use="required" type="string">
-<annotation>
 <documentation>When the module was executed.</documentation>
 </annotation>
 </attribute>
 <attribute name="Status" use="required" type="string" />
 <attribute name="ErrorMessage" type="string" />
 <attribute name="AttributeCreateTime" type="string" />
 <attribute name="AttributeSortTime" type="string" />
 </complexType>
 </element>

Element Input
 
diagram
description Identifies a set of attributes that satisfied a formal input.
uses attributes Input/ModuleExecutionID, Input/Name
 
used by elementsModuleExecution
content sequence (default)
 
Attribute Datatype Use Values Default Comments
Name string required Formal Input name
ModuleExecutionID string optional (default) References a module execution that produced the attribute set fed to this input.
 
source
-<element name="Input">
-<annotation>
 <documentation>Identifies a set of attributes that satisfied a formal input.</documentation>
 </annotation>
-<complexType>
-<attribute name="Name" use="required" type="string">
-<annotation>
 <documentation>Formal Input name</documentation>
 </annotation>
 </attribute>
-<attribute name="ModuleExecutionID" type="string">
-<annotation>
 <documentation>References a module execution that produced the attribute set fed to this input.</documentation>
 </annotation>
 </attribute>
 </complexType>
 </element>

Element ModuleExecution
 
diagram
description Describes the data dependency of a module run. ModuleRun is meant to describe the relationships a module run creates, not the specifics of its execution. A Module may in fact have been executed more than once. Isolating execution specifics from the relationship allows us to acknowledge that multiple executions occured without storing two copies of their identical output. Non-deterministic modules may have only one ExecutionHistory per ModuleRun because their results are not guaranteed to be the same for identical inputs.
uses elements ExecutionHistory, Input, Output
uses attributes ModuleExecution/DatasetID, ModuleExecution/Dependence, ModuleExecution/ID, ModuleExecution/ModuleID
 
used by elementsDataHistory
substitution hierarchy ModuleExecution
content sequence
 
Attribute Datatype Use Values Default Comments
ID string required
DatasetID OME:DatasetID required Dataset this was run against.
ModuleID OME:ModuleID required References a module by LSID
Dependence {} required possible values: G | D | I | F Module Execution Dependence.
 
source
-<element name="ModuleExecution">
-<annotation>
 <documentation>Describes the data dependency of a module run. ModuleRun is meant to describe the relationships a module run creates, not the specifics of its execution. A Module may in fact have been executed more than once. Isolating execution specifics from the relationship allows us to acknowledge that multiple executions occured without storing two copies of their identical output. Non-deterministic modules may have only one ExecutionHistory per ModuleRun because their results are not guaranteed to be the same for identical inputs. </documentation>
 </annotation>
-<complexType>
-<sequence>
 <element ref="DH:ExecutionHistory" />
 <element ref="DH:Input" minOccurs="0" maxOccurs="unbounded" />
 <element ref="DH:Output" minOccurs="0" maxOccurs="unbounded" />
 </sequence>
 <attribute name="ID" use="required" type="string" />
-<attribute name="DatasetID" use="required" type="OME:DatasetID">
-<annotation>
 <documentation>Dataset this was run against.</documentation>
 </annotation>
 </attribute>
-<attribute name="ModuleID" use="required" type="OME:ModuleID">
-<annotation>
 <documentation>References a module by LSID</documentation>
 </annotation>
 </attribute>
-<attribute name="Dependence" use="required">
-<annotation>
 <documentation>Module Execution Dependence.</documentation>
 </annotation>
-<simpleType>
-<restriction base="string">
 <enumeration value="G" />
 <enumeration value="D" />
 <enumeration value="I" />
 <enumeration value="F" />
 </restriction>
 </simpleType>
 </attribute>
 </complexType>
 </element>

Element Output
 
diagram
description Identifies a set of attributes that were generated by a formal output.
uses elements AttributeRef
uses attributes Output/Name
 
used by elementsModuleExecution
content sequence
 
Attribute Datatype Use Values Default Comments
Name string required Formal Output Name
 
source
-<element name="Output">
-<annotation>
 <documentation>Identifies a set of attributes that were generated by a formal output.</documentation>
 </annotation>
-<complexType>
-<sequence>
 <element ref="DH:AttributeRef" minOccurs="0" maxOccurs="unbounded" />
 </sequence>
-<attribute name="Name" use="required" type="string">
-<annotation>
 <documentation>Formal Output Name</documentation>
 </annotation>
 </attribute>
 </complexType>
 </element>

DataType definitions

http://openmicroscopy.com/XMLschemas/DataHistory/IR3/DataHistory.xsd Original Schema Source

<!-- 
Generated by Turbo XML 2.3.1.100. Conforms to w3c http://www.w3.org/2001/XMLSchema
 -->
-<schema targetNamespace="http://openmicroscopy.com/XMLschemas/DataHistory/IR3/DataHistory.xsd" elementFormDefault="qualified">
 <import namespace="http://www.openmicroscopy.org/XMLschemas/OME/FC/ome.xsd" schemaLocation="http://www.openmicroscopy.org/XMLschemas/OME/FC/ome.xsd" />
-<element name="Input">
-<annotation>
 <documentation>Identifies a set of attributes that satisfied a formal input.</documentation>
 </annotation>
-<complexType>
-<attribute name="Name" use="required" type="string">
-<annotation>
 <documentation>Formal Input name</documentation>
 </annotation>
 </attribute>
-<attribute name="ModuleExecutionID" type="string">
-<annotation>
 <documentation>References a module execution that produced the attribute set fed to this input.</documentation>
 </annotation>
 </attribute>
 </complexType>
 </element>
-<element name="Output">
-<annotation>
 <documentation>Identifies a set of attributes that were generated by a formal output.</documentation>
 </annotation>
-<complexType>
-<sequence>
 <element ref="DH:AttributeRef" minOccurs="0" maxOccurs="unbounded" />
 </sequence>
-<attribute name="Name" use="required" type="string">
-<annotation>
 <documentation>Formal Output Name</documentation>
 </annotation>
 </attribute>
 </complexType>
 </element>
-<element name="AttributeRef">
-<annotation>
 <documentation>Reference to an attribute.</documentation>
 </annotation>
-<complexType>
-<attribute name="ID" use="required" type="string">
-<annotation>
 <documentation>References an attribute by LSID or id local to document.</documentation>
 </annotation>
 </attribute>
 </complexType>
 </element>
-<element name="ModuleExecution">
-<annotation>
 <documentation>Describes the data dependency of a module run. ModuleRun is meant to describe the relationships a module run creates, not the specifics of its execution. A Module may in fact have been executed more than once. Isolating execution specifics from the relationship allows us to acknowledge that multiple executions occured without storing two copies of their identical output. Non-deterministic modules may have only one ExecutionHistory per ModuleRun because their results are not guaranteed to be the same for identical inputs. </documentation>
 </annotation>
-<complexType>
-<sequence>
 <element ref="DH:ExecutionHistory" />
 <element ref="DH:Input" minOccurs="0" maxOccurs="unbounded" />
 <element ref="DH:Output" minOccurs="0" maxOccurs="unbounded" />
 </sequence>
 <attribute name="ID" use="required" type="string" />
-<attribute name="DatasetID" use="required" type="OME:DatasetID">
-<annotation>
 <documentation>Dataset this was run against.</documentation>
 </annotation>
 </attribute>
-<attribute name="ModuleID" use="required" type="OME:ModuleID">
-<annotation>
 <documentation>References a module by LSID</documentation>
 </annotation>
 </attribute>
-<attribute name="Dependence" use="required">
-<annotation>
 <documentation>Module Execution Dependence.</documentation>
 </annotation>
-<simpleType>
-<restriction base="string">
 <enumeration value="G" />
 <enumeration value="D" />
 <enumeration value="I" />
 <enumeration value="F" />
 </restriction>
 </simpleType>
 </attribute>
 </complexType>
 </element>
-<element name="ExecutionHistory">
-<complexType>
-<attribute name="RunTime" use="required" type="string">
-<annotation>
 <documentation>How long the module took to run. </documentation>
 </annotation>
 </attribute>
-<attribute name="Timestamp" use="required" type="string">
-<annotation>
 <documentation>When the module was executed.</documentation>
 </annotation>
 </attribute>
 <attribute name="Status" use="required" type="string" />
 <attribute name="ErrorMessage" type="string" />
 <attribute name="AttributeCreateTime" type="string" />
 <attribute name="AttributeSortTime" type="string" />
 </complexType>
 </element>
-<element name="DataHistory">
-<annotation>
 <documentation>Describes all known history of data.</documentation>
 </annotation>
-<complexType>
-<sequence>
 <element ref="DH:ModuleExecution" maxOccurs="unbounded" />
 </sequence>
 </complexType>
 </element>
 </schema>