<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2010 (http://www.altova.com) by Vaclav Snasel (Logica Czech Republic s.r.o.) -->
<xsd:schema xmlns="http://www.ote-cr.cz/schema/etso/types/esr-v1r1" xmlns:ecc="http://www.ote-cr.cz/schema/etso/types/etso-core-cmpts-v8r0" xmlns:ecl="http://www.ote-cr.cz/schema/etso/types/etso-code-lists-v6r4" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ote-cr.cz/schema/etso/types/esr-v1r1" elementFormDefault="qualified">
	<xsd:import namespace="http://www.ote-cr.cz/schema/etso/types/etso-code-lists-v6r4" schemaLocation="etso-code-lists-v6r4.xsd"/>
	<xsd:import namespace="http://www.ote-cr.cz/schema/etso/types/etso-core-cmpts-v8r0" schemaLocation="etso-core-cmpts-v8r0.xsd"/>
	<xsd:element name="StatusRequest">
		<xsd:annotation>
			<xsd:documentation>Object used for the transmission of status requests to the ETSO environment.</xsd:documentation>
		</xsd:annotation>
		<xsd:complexType>
			<xsd:sequence>
				<xsd:element name="MessageIdentification" type="ecc:IdentificationType">
					<xsd:annotation>
						<xsd:documentation>Unique identification of the status request.</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="MessageType" type="ecc:MessageType">
					<xsd:annotation>
						<xsd:documentation>The coded type of the status request being sent. The status request message type identifies the type of the transaction to which the request is being made. </xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="ProcessType" type="ecc:ProcessType">
					<xsd:annotation>
						<xsd:documentation>The nature of the process that the status request is directed at.</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="SenderIdentification">
					<xsd:annotation>
						<xsd:documentation>Identification of the party who is sending the status request. </xsd:documentation>
					</xsd:annotation>
					<xsd:complexType>
						<xsd:complexContent>
							<xsd:extension base="ecc:IdentificationType">
								<xsd:attribute name="codingScheme" type="ecl:CodingSchemeType" use="required"/>
							</xsd:extension>
						</xsd:complexContent>
					</xsd:complexType>
				</xsd:element>
				<xsd:element name="SenderRole" type="ecc:RoleType">
					<xsd:annotation>
						<xsd:documentation>Identification of the role that is played by the sender. </xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="ReceiverIdentification">
					<xsd:annotation>
						<xsd:documentation>Identification of the party who is receiving the status request. </xsd:documentation>
					</xsd:annotation>
					<xsd:complexType>
						<xsd:complexContent>
							<xsd:extension base="ecc:IdentificationType">
								<xsd:attribute name="codingScheme" type="ecl:CodingSchemeType" use="required"/>
							</xsd:extension>
						</xsd:complexContent>
					</xsd:complexType>
				</xsd:element>
				<xsd:element name="ReceiverRole" type="ecc:RoleType">
					<xsd:annotation>
						<xsd:documentation>Identification of the role that is played by the receiver.</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="MessageDateTime" type="ecc:MessageDateTimeType">
					<xsd:annotation>
						<xsd:documentation>Date and time of the preparation of the status request. The time must be expressed in UTC as: YYYY-MM-DDTHH:MM:SSZ.</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="RequestedTimeInterval" type="ecc:TimeIntervalType">
					<xsd:annotation>
						<xsd:documentation>The beginning and ending date and time of the period that the status request is covering. This information provides the start and end date and time for which the status information is to be supplied.Typically in the case of schedule information requests the sender will make a request covering the same period as the of the submitting transaction. The receiver will discard any request, without replying for a time interval that is outside the scope of the transaction covered by the request.</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="ReqSenderIdentification" type="ecc:PartyType" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation>Identification of a sender of the requested document. Mandatory when requesting internal daily schedule (MessageType=A01) document provided by Exchange and when ReqMessageIdentification and ReqMessageVersion are not specified.</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="ReqSenderRole" type="ecc:RoleType" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation>Role of a sender of the requested document. For mandatory condition look at ReqSenderIdentification.</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="ReqSubjectParty" type="ecc:PartyType" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation>Identification of a subject party of the required document. Mandatory for requests for schedules (MessageType=A01) in case elements SenderIdentification and SubjectParty of the required document are different (for external schedules sent from PPS and internal schedules sent from Exchange) and when ReqMessageIdentification and ReqMessageVersion are not specified.</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="ReqSubjectRole" type="ecc:RoleType" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation>Identification of the role that is played by the subject party of the required document. For mandatory condition look at ReqSubjectParty.</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="ReqMatchingPeriod" type="ecc:TimeIntervalType" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation>The beginning and ending date and time of the period that is to be matched within the schedule of the required document. Mandatory for intraday shedule requests (MessageType=A01) if ReqMessageIdentification and ReqMessageVersion are not specified.</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="ReqBusinessType" type="ecc:BusinessType" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation>Identifies the trading nature of an energy product of the required document. Mandatory for shedule requests (MessageType=A01) if ReqMessageIdentification and ReqMessageVersion are not specified.</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="ReqCounterParty" type="ecc:PartyType" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation>Identification of the participant which is a counterpaty of the required document subject party. Mandatory for requests for all internal schedules not sent by Exchange  and when ReqMessageIdentification and ReqMessageVersion are not specified.</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="ReqMessageIdentification" type="ecc:IdentificationType" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation>A required document identification. Mandatory for shedule requests (MessageType=A01) if ReqSubjectParty, ReqBusinessType and ReqSenderIdentification are not specified.</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="ReqMessageVersion" type="ecc:VersionType" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation>A required document version.  For mandatory condition look at ReqMessageIdentification.</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
			</xsd:sequence>
			<xsd:attribute name="DtdVersion" type="xsd:string" use="required">
				<xsd:annotation>
					<xsd:documentation>Version of the Schema</xsd:documentation>
				</xsd:annotation>
			</xsd:attribute>
			<xsd:attribute name="DtdRelease" type="xsd:string" use="required">
				<xsd:annotation>
					<xsd:documentation>Release of the Schema</xsd:documentation>
				</xsd:annotation>
			</xsd:attribute>
		</xsd:complexType>
	</xsd:element>
</xsd:schema>
