<xsd:schema targetNamespace="http://www.iredes.org/xml" xmlns:opt="http://www.iredes.org/IRoption" xmlns="http://www.iredes.org/xml" xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xsd:annotation>
<xsd:documentation>IREDES generic data types XML schema version 1.4</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>Schema created by IREDES office, see www.iredes.org.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType name="IRlength">
<xsd:annotation>
<xsd:documentation>Data Type for length specification; recommended data type for values = double</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5"/>
<xsd:minLength value="1"/>
<xsd:enumeration value="mm">
<xsd:annotation>
<xsd:documentation>Metric Millimeters acc. to ISO..... 1mm = 0,001m</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="cm">
<xsd:annotation>
<xsd:documentation>Metric Centimeters acc. to ISO..... 1 cm = 0,01 m</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="m">
<xsd:annotation>
<xsd:documentation>Metric Meters (Metric Base unit) acc. to ISO.....</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="km">
<xsd:annotation>
<xsd:documentation>Metric Kilometers acc. to ISO..... 1km = 1000m</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ft">
<xsd:annotation>
<xsd:documentation>Feet according to ..... 1ft = ........ m</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="IRtextShort">
<xsd:annotation>
<xsd:documentation>Text data type element for short text information provided in the standard. For longer or complex text information use the "IRText" type. White spaces are preserved so simple whitespace based formatting is kept.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="24"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="IRtext">
<xsd:annotation>
<xsd:documentation>Text data type for comments or text information provided in the standard. Comments may use 1-n instances of this IRtext element. Each single element in the comment then represents one line ready to display. White spaces are preserved so simple whitespace based formatting is kept.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:minLength value="0"/>
<xsd:maxLength value="64"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="IRtextLong">
<xsd:annotation>
<xsd:documentation>Text data type element for long text information</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="256"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="IRangle">
<xsd:annotation>
<xsd:documentation>Data Type for angle specification</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:float">
<xsd:minInclusive value="-360.000"/>
<xsd:maxExclusive value="360.000"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="IRvelocity">
<xsd:annotation>
<xsd:documentation>Data Type for velocity specification</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:float">
<xsd:whiteSpace value="collapse"/>
<xsd:minInclusive value="0.000"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:element name="GenHead">
<xsd:annotation>
<xsd:documentation>This is the General Header</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="FileCreateDate" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>Date of file creation. This is the date/time stamp for initializatioin of the Data Set. Keep in mind that different application objects possibly contained in the IREDES data set may be created at different dates/times. This is stated in the profile internal time tags!</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="IRversion" fixed="V 1.4">
<xsd:annotation>
<xsd:documentation>Version of the IREDES main components of the standard. this version number changes any time IREDES top level schemas are modified. Please note to state downward compatibility in the separate Attribute!</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>IREDES base standard version this data set bases on. IRversion is valid for all components exchanged in the data set residing in the IREDES home namespace. Observer that equipment profiles carry separate version tags as attribute of the equipment profiles root element!</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="IRversion">
<xsd:attribute name="DownwCompat" type="IRversion" use="required" fixed="V 1.3">
<xsd:annotation>
<xsd:documentation>Downward compatibility of the profile version stated in "version" can be guaranteed down to the version number stated in this attribute. Please note that interpreting a newer profile with an old processing software may result in data loss as additional parameters cannot be interpreted! When a new version cannot be marked downward compatible due to changes in Content definitions, changes in structure or removal of mandatory tags the "DownwCompat" attribute contains the same version number as stated in the "version" attribute above. Downward compatibility may only be activated if: - Optional elements have been removed from the schema - New additional elements have been added to a newer schema version.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="ProjectInfo" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Project information</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Signature" type="IRtext" minOccurs="0"/>
<xsd:element name="Comment" type="IRtextLong" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EquipmentInfo" minOccurs="0" type="EquipmentInfoType">
<xsd:annotation>
<xsd:documentation>
Equipment specific information concerning the main aggregate the information comes from.
ATTENTION: This information shall not be required to interpret a standard conformant data set.
It is just provided to identify a machine.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="SiteHead">
<xsd:annotation>
<xsd:documentation>Optional Site Header</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="DisplayToOperator" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Up to 10 Strings a 256 char to be displayed as stated in the flag related to the corresponding string.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="DispFlag" minOccurs="0">
<xsd:annotation>
<xsd:documentation>States under which circumstances the line (message) has to be displayed to the operator (See enumeration)</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="IRtextShort">
<xsd:enumeration value="MachStart">
<xsd:annotation>
<xsd:documentation>To be displayed when the machine is started. Machine start is defined as switching on the main power supply or power generation (Hyd. pump,...)</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="FileLoad">
<xsd:annotation>
<xsd:documentation>To be displayed as soon as the file is loaded (activated) in the machine's automation system (applicable especially to plan files originating from the mine!)</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AckFlag" type="IRtext" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Acknowledgement by the operator that he has read the message. (Will be transferred back as soon as the SiteHead is returned to the mine's computer system with the next protocol exchange. Contains the name of the operator (user name in the Automation system) or simply ACK if automation system does not work with user logins.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DispText" type="IRtextLong" maxOccurs="10"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="SiteOptions" type="IRoptionType"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="GenTrailer" type="GenTrailerType">
<xsd:annotation>
<xsd:documentation>The Trailer contains a checksum over all data in an IREDES file.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="IREDESType">
<xsd:annotation>
<xsd:documentation>Base type IREDES complete Data Set</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="GenHead"/>
<xsd:element ref="SiteHead" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="IRVersion" type="IRversion" use="required" fixed="V 1.4">
<xsd:annotation>
<xsd:documentation>Version tag for the version of the Equipment Profile. Note that this version may differ from the IREDES general version tag in the GenHead object! The implementation has to take care of being able to interpret this equipment profile version.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="IRDownwCompat" type="IRversion" use="required" fixed="V 1.3">
<xsd:annotation>
<xsd:documentation>Downward compatibility of the profile version stated in "version" can be guaranteed down to the version number stated in this attribute. Please note that interpreting a newer profile with an old processing software may result in data loss as additional parameters cannot be interpreted! When a new version cannot be marked downward compatible due to changes in Content definitions, changes in structure or removal of mandatory tags the "DownwCompat" attribute contains the same version number as stated in the "version" attribute above. Downward compatibility may only be activated if: - Optional elements have been removed from the schema - New additional elements have been added to a newer schema version.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<xsd:simpleType name="IRversion">
<xsd:annotation>
<xsd:documentation>IREDES Version Numbering</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:pattern value="V\s\d+\.\d{1,2}"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="IRoptionType">
<xsd:annotation>
<xsd:documentation>Data type for all individual IREDES standard extensions</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="OptionSchema" type="xsd:anyURI" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Name of the xml schema used for OptionData validation. In URL format.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:any namespace="opt" processContents="skip">
<xsd:annotation>
<xsd:documentation>Optional Data, either freely defined or to be validated and interpreted using the xml schema stated in the OptionSchema element. ATTENTION: Individual information may only be used in addition to the standard to enhance accuracy or operational comfort. IT MAY NOT BE USED TO MAKE A MACHINE INCOMPATIBLE TO IREDES COMPLIANT OPERATION!</xsd:documentation>
</xsd:annotation>
</xsd:any>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="GenTrailerType">
<xsd:sequence>
<xsd:element name="FileCloseDate" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>Date/time stamp of closing the Data Set. This value is written immediately before the checksum is calculated. Keep in mind that different application objects possibly contained in the IREDES data set may be created at different dates/times. This is stated in the profile internal time tags! </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ChkSum" type="xsd:hexBinary">
<xsd:annotation>
<xsd:documentation>Check sum including all data Objects in the Data Set Checksum is calculated over the ENTIRE XML file ready to send using the value string "0" as ChkSum value. After calculating the checksum the resulting value is written into the ChkSum tag thereby replacing the "0" string. Thereafter the Data Set is issued. Interpretation is done in reverse order also using "0" as a defined value of the ChkSum tag for checksum validation. The algorithm is: CRC32</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="EquipmentInfoType">
<xsd:sequence>
<xsd:element name="EqpManufact" type="IRtextShort">
<xsd:annotation>
<xsd:documentation>Name of manufacturer</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="EqpType" type="IRtextShort">
<xsd:annotation>
<xsd:documentation>Manufacturer internal type name of the machine.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="EqpModel" type="IRtextShort" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Equipment model describing the model in the specified EqpType.To be stated if required for unequivocal machine type identification</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="EqpSerNo" type="IRtext" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Serial number of machine</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="EqpSysVer" type="IRtextShort" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Version Info Automation System / Software.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="EqpInfo" type="IRtextLong" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Other equipment specific information. Free text</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="EqpName" type="IRtext" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Used for designation of the machine</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
|
XSD Schema Code: