<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2007 sp2 (http://www.altova.com) by Dagmar Haller (California ISO) -->
<xs:schema xmlns:m="http://www.caiso.com/soa/2008-08-09/RDTSubmissionStatus.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.caiso.com/soa/2008-08-09/RDTSubmissionStatus.xsd" elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xs:element name="RDTSubmissionStatus" type="m:RDTSubmissionStatus"/>
	<xs:complexType name="RDTSubmissionStatus">
		<xs:sequence>
			<xs:element name="MessageHeader" type="m:MessageHeader" minOccurs="0"/>
			<xs:element name="MessagePayload" type="m:MessagePayload"/>
		</xs:sequence>
	</xs:complexType>
	<xs:complexType name="MessageHeader">
		<xs:annotation>
			<xs:documentation>Message header containing descriptive information about the message.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="TimeDate" type="xs:dateTime">
				<xs:annotation>
					<xs:documentation>Application level relevant time and date for when this  instance of the message was produced.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="Source" type="xs:string">
				<xs:annotation>
					<xs:documentation>Source system that publishes the message. For CAISO, examples include ADS, ALFS, CAP, CRR, EMS, ETCC, FNM, IFM, MF, PI, RLC, RTM, SaMC, SIBR, SLIC, etc.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<xs:complexType name="MessagePayload">
		<xs:sequence>
			<xs:element name="RDTSubmissionStatusHdr" type="m:RDTSubmissionStatusHdr" minOccurs="0" maxOccurs="unbounded"/>
		</xs:sequence>
	</xs:complexType>
	<xs:complexType name="RDTSubmissionStatusHdr">
		<xs:sequence>
			<xs:element name="SchedulingCoordinator" type="m:SchedulingCoordinatorNmReq">
				<xs:annotation>
					<xs:documentation>All CAISO market participants are represented by Scheduling Coordinators (SCs) that are registered with the CAISO (section 5.1.2 IFM SRS). One participant can register multiple SCs with the CAISO. Many participants can do business with the CAISO using a single SC. Each generator resource can only be scheduled by one SC. One SC can schedule multiple generators. A load scheduling point can be used by multiple SCs. Each SC can schedule load at multiple scheduling points. Each SC can have more than one load schedule at any load scheduling point as long as each load schedule at the same load scheduling point has a separate resource ID and settlement-quality meter. An inter-tie scheduling point can be used by multiple SCs. Each SC can schedule interchange at multiple inter-tie scheduling points. An SC can have multiple interchange schedules at the same inter-tie scheduling point by assigning a unique interchange identifier to each interchange schedule. Currently, the type of SC includes: Scheduling Coordinator (MDAS certified) SC of Inter-SC Trades Only (not MDAS certified) SC &amp; FTR holder SC, FTR holder, TO , &amp; UDC.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="RDTSubmissionBatch" type="m:RDTSubmissionBatchRDTBatch" maxOccurs="unbounded"/>
		</xs:sequence>
	</xs:complexType>
	<xs:complexType name="SchedulingCoordinatorNmReq">
		<xs:sequence>
			<xs:element name="mrid" type="xs:string">
				<xs:annotation>
					<xs:documentation>MRID stands for master resource identifier which should be globally unique.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<xs:complexType name="RDTSubmissionBatchRDTBatch">
		<xs:sequence>
			<xs:element name="submissionDate" type="xs:dateTime" minOccurs="0"/>
			<xs:element name="fileName" type="xs:string" minOccurs="0"/>
			<xs:element name="batchID" type="xs:integer"/>
			<xs:element name="batchStatus" type="xs:string" minOccurs="0"/>
			<xs:element name="statusDate" type="xs:dateTime" minOccurs="0"/>
			<xs:element name="effectiveDate" type="xs:dateTime" minOccurs="0"/>
			<xs:element name="submitter" type="xs:string" minOccurs="0"/>
		</xs:sequence>
	</xs:complexType>
</xs:schema>

