[OASIS Issue Tracker] (ENERGYINTEROP-731) Transaction Facet

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

Toby Considine created ENERGYINTEROP-731:
--------------------------------------------

             Summary: Transaction Facet
                 Key: ENERGYINTEROP-731
                 URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-731
             Project: OASIS Energy Interoperation TC
          Issue Type: Bug
          Components: cts
    Affects Versions: CTSPR01
         Environment: [https://lists.oasis-open.org/archives/energyinterop-comment/202112/msg00001.html]ÂHoria Pop; Lateral Inc
            Reporter: Toby Considine
            Assignee: Toby Considine


*Transaction Facet*

The interaction pattern and payload are confusing.ÂThe interaction diagram shows Party and a Counter Party with the Party initiating the EiCreateTransactionPayload().
This seems counterintuitive for a typical scenario, where a market actor would match two parties. For each of their contracts, one is the Party the other CounterParty. The market needs to notify each andÃconfirm the transaction. What is the expected payload of the market sent to the two parties? EiCreateTransactionPayload or EiCreatedTransactionPayload? In what scenario does a Market actor need to expose both?Â__ÂIf the latter, who would callÂEiCreateTransaction?

_[Lines 592]_



--
This message was sent by Atlassian Jira
(v8.3.3#803004)