Uploaded image for project: 'OASIS Energy Interoperation TC'
  1. OASIS Energy Interoperation TC
  2. ENERGYINTEROP-581

Suggests for corrections to schema documentation and multiplicity for Tenders, Transactions and Quotes in EIPaloads 7.0

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: wd30
    • Component/s: schema
    • Labels:
      None
    • Environment:

      WD30,WD31

    • Proposal:
      Hide

      <!-- 7.1 Tenders -->
      <xs:documentation>
      Tender Indicates a soecific 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.
      Correction: Tender indicates a binding offer to buy or sell. A Tender is for a single EmixBase derived types.
      <!-- 7.2 Quotes -->
      <xs:documentation>
      A non-binding indication of price for a potential Tender. A Quote is for a single EmixBase derived types.

      <!-- 7.3 Transations -->
      Correction: <!-- 7.3 Transactions -->

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

      It is my understanding that EI 1.0 does not deal with compound Tenders with multiple.TenderIDs and emixBases. EiCreateTender communicates multiple TenderIDs and emixBases in its Payload, but each of them can be independently transacted. Post Ei 1.0 we can deal with compound Tenders where a single TenderID is associated with multiple emixBases.

      Hence for Tenders:
      Currently:
      <xs:element ref="eitc:tenderID" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="unbounded"/>

      Correction:
      <xs:element ref="eitc:tenderID" minOccurs="0" maxOccurs="1"/>
      <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="1"/>

      And for Transactions:

      Currently:
      <xs:element ref="eitc:transactionID" minOccurs="1" maxOccurs="1"/>
      <xs:element ref="eitc:tenderID" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="unbounded"/>

      Correction:
      <xs:element ref="eitc:transactionID" minOccurs="1" maxOccurs="1"/>
      <xs:element ref="eitc:tenderID" minOccurs="0" maxOccurs="1"/>
      <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="1"/>

      And for Quotes

      <xs:element ref="eitc:quoteID" minOccurs="1" maxOccurs="1"/>
      <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="unbounded"/>

      Correction:
      <xs:element ref="eitc:quoteID" minOccurs="1" maxOccurs="1"/>
      <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="1"/>

      Show
      <!-- 7.1 Tenders --> <xs:documentation> Tender Indicates a soecific 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. Correction: Tender indicates a binding offer to buy or sell. A Tender is for a single EmixBase derived types. <!-- 7.2 Quotes --> <xs:documentation> A non-binding indication of price for a potential Tender. A Quote is for a single EmixBase derived types. <!-- 7.3 Transations --> Correction: <!-- 7.3 Transactions --> <xs:documentation> A Transaction is a specific agreement to accept a specific Tender or Tenders It is my understanding that EI 1.0 does not deal with compound Tenders with multiple.TenderIDs and emixBases. EiCreateTender communicates multiple TenderIDs and emixBases in its Payload, but each of them can be independently transacted. Post Ei 1.0 we can deal with compound Tenders where a single TenderID is associated with multiple emixBases. Hence for Tenders: Currently: <xs:element ref="eitc:tenderID" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="unbounded"/> Correction: <xs:element ref="eitc:tenderID" minOccurs="0" maxOccurs="1"/> <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="1"/> And for Transactions: Currently: <xs:element ref="eitc:transactionID" minOccurs="1" maxOccurs="1"/> <xs:element ref="eitc:tenderID" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="unbounded"/> Correction: <xs:element ref="eitc:transactionID" minOccurs="1" maxOccurs="1"/> <xs:element ref="eitc:tenderID" minOccurs="0" maxOccurs="1"/> <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="1"/> And for Quotes <xs:element ref="eitc:quoteID" minOccurs="1" maxOccurs="1"/> <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="unbounded"/> Correction: <xs:element ref="eitc:quoteID" minOccurs="1" maxOccurs="1"/> <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="1"/>

      Description

      Current Schema in EiPayloads WD30
      <!-- 7.0 Tenders, Quotes, and Transactions -->
      <!-- 7.1 Tenders -->
      <xs:element name="eiTender" type="eitc:EiTenderType"/>
      <xs:complexType name="EiTenderType">
      <xs:annotation>
      <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>
      </xs:annotation>
      <xs:sequence>
      <xs:element ref="eitc:tenderID" minOccurs="1" maxOccurs="1"/>
      <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="unbounded"/>
      </xs:sequence>
      </xs:complexType>
      <!-- 7.2 Quotes -->
      <xs:element name="eiQuote" type="eitc:EiQuoteType"/>
      <xs:complexType name="EiQuoteType">
      <xs:annotation>
      <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>
      </xs:annotation>
      <xs:sequence>
      <xs:element ref="eitc:quoteID" minOccurs="1" maxOccurs="1"/>
      <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="unbounded"/>
      </xs:sequence>
      </xs:complexType>
      <!-- 7.3 Transations -->
      <xs:element name="eiTransaction" type="eitc:EiTransactionType"/>
      <xs:complexType name="EiTransactionType">
      <xs:annotation>
      <xs:documentation>A Transaction is a specific agreement to accept a specific Tender or Tenders.</xs:documentation>
      </xs:annotation>
      <xs:sequence>
      <xs:element ref="eitc:transactionID" minOccurs="1" maxOccurs="1"/>
      <xs:element ref="eitc:tenderID" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element ref="emix:emixBase" minOccurs="1" maxOccurs="unbounded"/>
      </xs:sequence>
      </xs:complexType>

        Attachments

          Activity

            People

            • Assignee:
              ecazalet Edward Cazalet (Inactive)
              Reporter:
              ecazalet Edward Cazalet (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: