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

SignalType enumeration should be the same for Signal / Report / Baseline

    XMLWordPrintable

    Details

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

      Toby Considine

    • Proposal:
      Hide

      Unify these Types into a single enumeration used for all Streams

      Show
      Unify these Types into a single enumeration used for all Streams
    • Resolution:
      Hide

      Unify these Types into a single enumeration used for all Streams (applied in wd32)

      Show
      Unify these Types into a single enumeration used for all Streams (applied in wd32)

      Description

      There is already substantial overlap.
      Signals are request to Make It So. Reports are What did you make of it. Baselines are expectations about what it is.

      With the current structure of ItemBase / Payload, there is no barrier to using the same enumeration for all. I can think of use cases even for Price as a Baseline and as a Report.

        Attachments

          Activity

            People

            • Assignee:
              william.cox William Cox (Inactive)
              Reporter:
              Toby.Considine Toby Considine
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: