[OASIS Issue Tracker] Updated: (ENERGYINTEROP-576) SignalType enumeration should be the same for Signal / Report / Baseline

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

     [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated ENERGYINTEROP-576:
--------------------------------------

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

> SignalType enumeration should be the same for Signal / Report / Baseline
> ------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-576
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-576
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>         Environment: Toby Considine
>            Reporter: Toby Considine
>            Assignee: Girish Ghatikar 
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira