OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Created: (ENERGYINTEROP-618) WD33 Transactive EiPayloads Schema Comments and Corrections


WD33 Transactive EiPayloads Schema  Comments and Corrections
------------------------------------------------------------

                 Key: ENERGYINTEROP-618
                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-618
             Project: OASIS Energy Interoperation TC
          Issue Type: Improvement
          Components: schema
            Reporter: Edward Cazalet 
            Assignee: William Cox
             Fix For: wd33


Transactive EiPayloads Schema  Comments and Corrections

808 <xs:documentation>Tender Indicates a specific offer to buy or sell. A Tender can be for any number of EmixBase derived types, and the Tender is treated as all-or-none.</xs:documentation>

Change to:

808 <xs:documentation>Tender is an offer to buy or sell. A Tender can be for any number of EmixBase derived types.  If more than  one EMIXBase the a Tender for all EMIXBases must be transacted once or none transacted. .</xs:documentation>



819 <xs:documentation>A specific offer to sell for a particular price.  A Quote can be for any number of EmixBase derived types, and the Quote is treated as all-or-none.</xs:documentation>

Change to:

819 <xs:documentation>An Indication of the price of a possible Tender such as the transacted price of a previous Tender or a published forecast of a price of a possible Tender.  A Quote can be for any number of EmixBase derived types.</xs:documentation>


830 <xs:documentation>A Transaction is a specific agreement to accept a specific Tender or Tenders.</xs:documentation>
		
Change to:

830 <xs:documentation>A Transaction is a specific agreement to accept a specific Tender.</xs:documentation>



833	<xs:element ref="ei:transactionID" minOccurs="1" maxOccurs="1"/>
834	<xs:element ref="ei:tenderID" minOccurs="0" maxOccurs="unbounded"/>
835	<xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="unbounded"/>
	
Change to:

833	<xs:element ref="ei:transactionID" minOccurs="1" maxOccurs="1"/>
834	<xs:element ref="ei:tenderID" minOccurs="0" maxOccurs="1"/>
835	<xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="1"/>

See JIra 607 to explain above changes.



812   <xs:documentation>Request for usage [delivery], Party-to-Party, specifying interval, what is to be measured, and the direction for the measurement.</xs:documentation>

Change to:

812   <xs:documentation>Request for usage or generation [delivery] at an EMIXInterface by a requestor Party, specifying interval, what is to be measured, and the direction for the measurement.</xs:documentation>


See separate Jira 617 on EiDelivery


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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]