[OASIS Issue Tracker] Commented: (EMIX-528) Price Optionality

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/EMIX-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27213#action_27213 ] 

Toby Considine commented on EMIX-528:
-------------------------------------

Issue 1: 
Within blockPowerFullRequirements: 
power:unitEnergyPrice 
<xs:element name="price" type="emix:PriceType" substitutionGroup="emix:priceBase"/> 
is required. 

tc>> Power Product has it optional
			<xs:extension base="emix:ProductDescriptionType">
				<xs:sequence>
					<xs:element ref="power:productType"/>
					<xs:element ref="emix:emixInterface"/>
					<xs:element ref="power:unitEnergyPrice" minOccurs="0" maxOccurs="1"/>
					<xs:element ref="power:powerItem" minOccurs="0" maxOccurs="1"/>
					<xs:element ref="power:charges" minOccurs="0" maxOccurs="1"/>
				</xs:sequence>
			</xs:extension>

tc>> And Block power does not require it
		<xs:complexContent>
			<xs:extension base="power:PowerProductDescriptionType">
				<xs:sequence>
					<xs:element name="maximumPower" type="emix:QuantityType" minOccurs="0" maxOccurs="1"/>
					<xs:element name="minimumPower" type="emix:QuantityType" minOccurs="0" maxOccurs="1"/>
					<xs:element name="priceTiers" type="power:ArrayOfBlockPowerPrices" minOccurs="1" maxOccurs="1"/>
				</xs:sequence>
			</xs:extension>
tc>> And  the tiers require it as requested:

Unable to reproduce this


power:priceTiers -> power:blocPowerPrice 
<!-- 8.3.1 Absolute Price --> 
<xs:element name="price" type="emix:PriceType" substitutionGroup="emix:priceBase"/> 
is where the actual price is for the applicable consumption block. 

What is the first price for? unitEnergyPrice is probably used a bunch of places,so making the price optional there might be a problem. 
Maybe energyitem is all that is needed within blockPowerFullRequirements? 

Issue 2: 
powerItem is still required. It should only be applicable to demand charges. So I am assuming itemUnits in demandCharge would be W. If we leave it in, what do I say it is for? 

tc>> MinOccurs = 0 ==> means not required. See above.

Issue 3: 
<power:charges></power:charges><!-- charges is mandatory, but all of the elements are optional --> Still the case. Not a big deal, but it looks corny. 

TC>> The schema says:
<xs:element ref="power:charges" minOccurs="0" maxOccurs="1"/>
which means Charges is optional


Issue 4: 
<power:maximumEnergyQuantity>999999</power:maximumEnergyQuantity><!-- mandatory element; what to do with the highest block?--> 
If a start value is used for each consumption block then is this is not an issue. Changing to optional would require some rules on what to do if it is not there. 

TC>> Any Tariff has a maximum, even if it is the maxumim capacity of the feeder cable. Usually exceeding it moves one from Residential to Commercial. In Industrial, it may be a fixed maximum.


All these (except 4) have already been changed to MinOccurs=0, as requested

> Price Optionality
> -----------------
>
>                 Key: EMIX-528
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-528
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Improvement
>          Components: schema, spec
>    Affects Versions: CSD03/PR03
>         Environment: Bruce Bartell
>            Reporter: Bruce Bartell
>            Assignee: Toby Considine
>             Fix For: wd36
>
>
> Remaining issue from EMIX-129:
> See Sept 1 Comment. Price should be optional in EmixBase etc.
> Topic of EMIX-129 addressed; that issue is closed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira