[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ENERGYINTEROP-724) Transactions vs Contracts
[ https://issues.oasis-open.org/browse/ENERGYINTEROP-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=80731#comment-80731 ] William Cox commented on ENERGYINTEROP-724: ------------------------------------------- This should be clarified as to the relationship of contracts and transactions. One example from the EML-CTS open source implementation: A match in the market creates two symmetric EiCreateTransaction messages, with Side and Party/Counterparty reversed. > Transactions vs Contracts > ------------------------- > > Key: ENERGYINTEROP-724 > URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-724 > Project: OASIS Energy Interoperation TC > Issue Type: Bug > Components: cts > Affects Versions: CTSPR01 > Environment: Horia Pop; Lateral Inc https://lists.oasis-open.org/archives/energyinterop-comment/202112/msg00001.html > Reporter: Toby Considine > Assignee: William Cox > Priority: Major > Labels: ARCH-CONF, editorial > > *Transactions vs Contract* > The standard implies a one-to-one relationship between transaction and contract. In practice, I believe it is more appropriate to have a one-to-many relationship between transactions and contracts. Each party of a transaction will receive its own distinct contract (the counterparty may not be public to each other). Also, for the market to match an integral tender, t may have to match with multiple counterparties tenders to create a transaction. > _[Lines 282, 318, 379]_ -- This message was sent by Atlassian Jira (v8.3.3#803004)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]