[OASIS Issue Tracker] (ENERGYINTEROP-730) Transactive State

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

    [ https://issues.oasis-open.org/browse/ENERGYINTEROP-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=80711#comment-80711 ] 

William Cox commented on ENERGYINTEROP-730:
-------------------------------------------

Transactive State is described on lines 561-566 in CTS (https://docs.oasis-open.org/energyinterop/ei-cts/v1.0/csd01/ei-cts-v1.0-csd01.html#_Toc85711690), and references EMIX (http://docs.oasis-open.org/emix/emix/v1.0/cs02/emix-v1.0-cs02.html#_Toc319594523).

There are subsets of Transactive State profiled in the TEMIX profile of EMIX and in the TEMIX profile of Energy Interoperation; the CTS subset excludes Indication of Interest from the EMIX TEMIX profile.

Software engineering has generally evolved beyond the object in which you read a flag to determine what the actual type is. Instead the trend for some years is to strongly-typed objects. CTS follows this latter set of rules, and transactive state should be eliminated.



> Transactive State
> -----------------
>
>                 Key: ENERGYINTEROP-730
>                 URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-730
>             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: Toby Considine
>            Priority: Major
>              Labels: ARCH-CONF
>
> *Transactive State*
> Transactive state values are not documented in CTS nor [EMIX]. While one can imply the meaning, the boundaries of each state seem vague when analyzed. Is there an implied order too? What state would a delivered and settled tender take? Delivery or publication?Ã What about in a market where settlement occurs at the time of the transaction before delivery?
> Having the same transactive state map over both tenders and transaction is a stretch when taking the individual values.Ã This dual-use also becomes a source of conflictual information and implementations intent between a tender transactive state and the transaction transactive state.
> _[Lines 555, 599]_



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