Details

    • Proposal:
      Hide

      It appears that the sentence in question has the matter backward (Toby please clarify).

      Show
      It appears that the sentence in question has the matter backward (Toby please clarify).
    • Resolution:
      Hide

      Item 24: No action - can't find referenced text.

      Item 26: No action. We have removed Transactive State, using the strongly typed payloads to reflect the EMIX Transactive State and the TEMIX/CTS restriction.

      Show
      Item 24: No action - can't find referenced text. Item 26: No action. We have removed Transactive State, using the strongly typed payloads to reflect the EMIX Transactive State and the TEMIX/CTS restriction.

      Description

      There are 30 specific recommendations in the "Specific Recommendations" section of the submitted Hammerstrom paper. I have numbered them all for traceability as I recombine them into specific issues. The original white paper/submission can be read in the URI under "environment"

      24. Section 8: This section points out the weakness of using transaction and Transaction differently. I liked the use of Transaction in TEMIX as a state of a transaction. All this subtle distinction is lost if capitalization is not used consistently, as is the case in this section. 

      26. Table 9-2: I think the fact that an EiTransaction always has Transactive State=transaction is a vestige of an earlier, preferable approach. Wouldn’t it be much more elegant to define a single transaction behavior, in which the transaction migrates through its available states? Each of the Tender Facet, Transaction Facet (and possibly Quote Facet) should be defined as state transition behaviors, but I question why the structure of the interaction payloads should differ at all.  

      • Tender, Transaction, Delivery, (Quote) address states of an interaction and were more clearly addressed by a TEMIX enumeration. This may be an unwise simplification, as it limits future extension of interaction attributes. 

        Attachments

          Activity

          Hide
          WilliamCox William Cox added a comment - - edited

          Point 24: I could not find the described text.

          Point 26: The use of TransactiveStateType is indeed a vestige of an earlier approach, but the direction for some decades in software engineering is use the type of the object, rather than a value of an attribute. Alas, as a tender evolves (potentially) into a transaction, values (price, quantity) will change due to market actions. Figure 9-2 line 601 shows that EiTransaction "has an" EiTender included. (In fact, the EiTransaction is a wrapper on an evolved, rewritten Tender).

          Evolving the containing set of attributes from a Tender through a Transaction seems inconsistent with current strongly-typed message structures.

          Show
          WilliamCox William Cox added a comment - - edited Point 24: I could not find the described text. Point 26: The use of TransactiveStateType is indeed a vestige of an earlier approach, but the direction for some decades in software engineering is use the type of the object, rather than a value of an attribute. Alas, as a tender evolves (potentially) into a transaction, values (price, quantity) will change due to market actions. Figure 9-2 line 601 shows that EiTransaction "has an" EiTender included. (In fact, the EiTransaction is a wrapper on an evolved, rewritten Tender). Evolving the containing set of attributes from a Tender through a Transaction seems inconsistent with current strongly-typed message structures.
          Hide
          WilliamCox William Cox added a comment -

          Item 24 has been split off in a new item (editorial) ENERGYINTEROP-741

          Item 26: No action. We have removed Transactive State, using the strongly typed payloads to reflect the EMIX Transactive State and the TEMIX/CTS restriction. This is consistent with the software architectural approach described in Introduction line 37 (wd15).

          Show
          WilliamCox William Cox added a comment - Item 24 has been split off in a new item (editorial) ENERGYINTEROP-741 Item 26: No action. We have removed Transactive State, using the strongly typed payloads to reflect the EMIX Transactive State and the TEMIX/CTS restriction. This is consistent with the software architectural approach described in Introduction line 37 (wd15).
          Hide
          WilliamCox William Cox added a comment -

          Transition all RESOLVED to APPLIED excepting ENERGYINTEROP-706 per Energy Interoperation TC Motion April 28, 2022.

          Show
          WilliamCox William Cox added a comment - Transition all RESOLVED to APPLIED excepting ENERGYINTEROP-706 per Energy Interoperation TC Motion April 28, 2022.
          Hide
          WilliamCox William Cox added a comment -

          Transition all APPLIED to CLOSED per Energy Interoperation TC Motion April 28, 2022.

          Show
          WilliamCox William Cox added a comment - Transition all APPLIED to CLOSED per Energy Interoperation TC Motion April 28, 2022.

            People

            • Assignee:
              toby.considine Toby Considine (Inactive)
              Reporter:
              toby.considine Toby Considine (Inactive)
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: