[OASIS Issue Tracker] Commented: (ENERGYINTEROP-399) Use of eiQuoteto represent Time-of-Use and Consumption Block rates

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

    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26144#action_26144 ] 

Toby Considine commented on ENERGYINTEROP-399:
----------------------------------------------

In the current schema

	<xs:element name="eiDistributeQuote" type="payloads:EiDistributeQuoteType"/>
	<xs:complexType name="EiDistributeQuoteType">
		<xs:annotation>
			<xs:documentation>For price distribution through broadcast, the VTN-VEN links, or otherwise (e.g. passive placing on a web site for REST-style access). A quote is delivered as an EMIX Product. This is a push, not a pull. EiRequestQuote is a pull, to which EiSentQuote is a response.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="applicableLocation" type="emix:EmixInterfaceType" minOccurs="1" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>EmixInterfaceType is an abstract type with specific locations including geospatial as subclasses.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="unbounded"/>
		</xs:sequence>
	</xs:complexType>


> Use of eiQuote to represent Time-of-Use and Consumption Block rates
> -------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-399
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-399
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Task
>          Components: schema
>    Affects Versions: wd22
>            Reporter: Bruce Bartell
>            Assignee: William Cox
>
> Structure to support Time-of-Use in conjunction with Consumption Block Rates is not apparent.
> The Consumption Block is represented by type blockPowerFullRequirementsProductDescription which is a type of productDescription referernced by the wsCalendar-attach.
> The interval and gluon structures are parallel in emixBase to the productDescrpiton. I think the interval and gluon can represent the same structures as part of a recursive structure. If these contain the date/time ranges that would have the productDescription embedded in the the list, then I think this could represent the TOU with each occurance containing the block rates. 

-- 
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