Major emix.xsd Schema Comments:
Line 21: <xs:element name="energyPrice" type="emix:type-price"/>
Extended price, depending on the underlying product should be a $ amount and not a unit price. It is either a total net revenue or a total net cost. AS this may not be applicable in all situations and is a nilible field.
Line 22 <xs:element name="packageDiscount" type="emix:type-price"/>
also should be a nilable field as it may not always applicable
Line 66 : <xs:documentation>Price Support products may be needed to justify the price. An example would be a T amp D product justifying the price up-tick on power</xs:documentation>
Suggest changing as follows: "An example would be a transport product that support the difference between a product price at a point of delivery and a product price at a point of receipt"
Line 121 : <xs:complexType name="type-productPerformance">
The use of the term product Performance is confusing in relation to the use of performance as a transactive state on Line 156
Line 51 insert the following
<!-- 1.3 EMIX VEN (virtual end node Resource)-->
<xs:element name="emix" type="emix:type-emixVEN">
<xs:annotation>
<xs:documentation>Base element for Demand and Generation Resource Management </xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="type-emixResource">
<xs:sequence>
<xs:element name="uid" type="xs:string"/>
<xs:element name="createdDateTime" type="xs:dateTime"/>
<xs:element name="resourceState" type="emix:type-resourceState"/>
<xs:element name="resource" type="emix:type-resource" maxOccurs="unbounded"/>
<xs:element name="extendedPrice" type="emix:type-price" nillable="true"/>
<xs:element name="packageDiscount" type="emix:type-price"/>
<xs:element name="marketContext" type="emix:type-marketContext"/>
<xs:element name="currency" type="xs:string"/>
<xs:element name="envelopeContents" type="emix:type-envelope"/>
</xs:sequence>
</xs:complexType>
The above would apply only to the resource characteristics define in resource.xsd. These include generation and DR load reduction resources characteristics. An event that invokes one of thise resources or a dispatch of these resources by a Virtual Top Node will result in transactions characterized in type emix:(1.1). A Virtual Top Node may have a process to aggregate the resource characteristics under its control and express this as a resource characteristic thus taking the role of a VEN under the control of another VTN.
Since a resource is not a product there may need to be some more plumbing as in power.xsd to hock up to resource.xsd for serviceLocation and Interval etc.
After line 157 define resourceState as follows
<xs:simpleType name="type-resourceState">
<xs:restriction base="xs:string">
<xs:enumeration value="contract"/>
<xs:enumeration value="deployment"/>
<xs:enumeration value="performance"/>
</xs:restriction>
power.xsd Schema Comments
Line 19: <xs:element name="energyPrice" type="emix:type-price"/> should be
<xs:element name="energyPrice" type="emix:type-unitEnergyprice"/> "see line 128 comment below.
Line 36: "An" should be "A"
Line 63: "Contracted" should be "Contract"
Line 120 should be Transport
Line 121 name should be transportProduct
Line 123 : Should be " Class for all Transport Products in EMIX"
Line 114 and line 174 "Assett" should be "Asset"
Line 128 or so: We also need a unitEnergyPrice in addition to unitPowerPrice
<xs:complexType name="type-unitEnergyPrice">
<xs:annotation>
<xs:documentation>Price per Unit of Energy</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="unitPrice" type="emix:type-price"/>
<xs:element name="energyUnits" type="power:enum-energyUnits"/>
</xs:sequence>
</xs:complexType>
and then replace line 20
<xs:element name="energyPrice" type="emix:type-price"/>
with
<xs:element name="energyPrice" type="emix:type-unitEnergyPrice"/>
Following Line 148 insert
<xs:complexType name="type-energyQuantity">
<xs:annotation>
<xs:documentation>Quantity of Energy</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name=energy" type="energy:type-quantity"/>
<xs:element name="energyUnits" type="power:enum-energyUnits"/>
</xs:sequence>
</xs:complexType>
LIne 160 Delete the follows - voltage is an attribute of power and not a product - vars are a product to adjust voltage to withing standard levels.
<xs:complexType name="type-voltageQuantity">
<xs:annotation>
<xs:documentation>Price per Unit of Power</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="volts" type="power:type-quantity"/>
<xs:element name="voltageUnits" type="power:enum-voltageUnits"/>
</xs:sequence>
</xs:complexType>
should be
<xs:complexType name="type-voltageQuantity">
<xs:annotation>
<xs:documentation>Vo</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="volts" type="power:type-quantity"/>
<xs:element name="voltageUnits" type="power:enum-voltageUnits"/>
</xs:sequence>
</xs:complexType>
line 170
<!-- 9.8.1 Energy Quantity -->
should be
<!-- 9.8.1 Quantity -->
transport.xsd Schema Comments
Line 9 :"servcies, inclluding" should be "services, including"
Line 58 replace documentation with "point-to-point congestion price".
Line 65: Point-to-point marginal loss price
Line 37 :delete because there are no access revenues associated with a congestion revenue right
Line 38 : need advice from IRC members on names and units.
Line 42 comment no longer needed
Line 73 : should be Ratio of energy delivered to energy received for transport ( may greater or less than 1.0):
PowerContract.xsd Schema Comments
Because a full-requirements contract is a contract for energy then the units should be energy unitsso change Line 15 & 16
<xs:element name="powerUnits" type="power:enum-powerUnits"/>
<xs:element name="attributes" type="power:type-powerAttributes"/>
to
<xs:element name="energyUnits" type="power:enum-energyUnits"/>
<xs:element name="attributes" type="power:type-energyAttributes"/>
line 8: We can define the full requirements power contracts with blocks of maximum energy and a price for each blocks. The number of blocks can be 1 to
<xs:complexType name="type-fullRequirementsBlPowerDescription">
<xs:annotation>
<xs:documentation>Often used in retail residential rates. Simple prices, will supply all used. Demand Charges Optional</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="emix:type-productDescription">
xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element name="blockEnergyPrice" type="emix:type-unitEnergyPrice"/>
<xs:element name="blockMaxEnergyQuantity" type="emix:type-energyQuantity/>
</xs:sequence>
<xs:element name="energyUnits" type="power:enum-energyUnits"/>
<xs:element name="serviceLocation" type="power:type-interfacePricingPoint"/>
<xs:element name="demandCharge" type="contract:type-demandCharge"
<xs:element name="maximumPower" type="power:type-quantity"/>
<xs:element name="minimumPower" type="power:type-quantity"/>
<xs:element name="contractType" type="contract:enum-contractTypes"/>
<xs:sequence >
<xs:element name="attributes" type="power:type-powerAttributes"/>
</xs:extension>
</xs:sequence>
</xs:complexContent>
</xs:complexType>