OASIS Energy Interoperation TCIcon indicating the project type

OASIS Energy Interoperation TC

Uploaded image for project: 'OASIS Energy Interoperation TC'
  1. OASIS Energy Interoperation TC
  2. ENERGYINTEROP-325 Service Defintion Improvements collector
  3. ENERGYINTEROP-205

Line 721: testEvent should be expanded from Boolean to allow for indication of other types of Events: Advanced (Normal), Immediate, Audit/Test.

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: wd15
    • Fix Version/s: None
    • Component/s: spec
    • Labels:
      None
    • Environment:

      Bruce Bartell wd15 line 721 wd16 line 809

    • Resolution:
      Hide

      Make testEvent a string rather than a boolean. A particular installation would have to look at the strings for meaning, but the boolean treatment could be implemented as "null string" or "not present". Cardinality [0..1] . This should not only be in EiStatus but in EiEvent as well.

      Show
      Make testEvent a string rather than a boolean. A particular installation would have to look at the strings for meaning, but the boolean treatment could be implemented as "null string" or "not present". Cardinality [0..1] . This should not only be in EiStatus but in EiEvent as well.

      Attachments

        Activity

        Ascending order - Click to sort in descending order
        Hide
        Permalink
        william.cox William Cox (Inactive) added a comment -

        Is the suggestion to make testEvent (attribute of EiStatus) an enum or something else?

        Show
        william.cox William Cox (Inactive) added a comment - Is the suggestion to make testEvent (attribute of EiStatus) an enum or something else?
        Hide
        Permalink
        edgardo.luzcando Edgardo Luzcando (Inactive) added a comment -

        A String would work in the near term, but an enum is good candidate once the choices can be discussed and agreed upon.

        Show
        edgardo.luzcando Edgardo Luzcando (Inactive) added a comment - A String would work in the near term, but an enum is good candidate once the choices can be discussed and agreed upon.
        Hide
        Permalink
        william.cox William Cox (Inactive) added a comment -

        Defer. New design, many issues, post PR1.

        Show
        william.cox William Cox (Inactive) added a comment - Defer. New design, many issues, post PR1.
        Hide
        Permalink
        william.cox William Cox (Inactive) added a comment -

        I think that an enum is a mistake, as it's not very flexible going forward. A string is the better choice for 1.0, per Edgardo's suggestion.

        Show
        william.cox William Cox (Inactive) added a comment - I think that an enum is a mistake, as it's not very flexible going forward. A string is the better choice for 1.0, per Edgardo's suggestion.
        Hide
        Permalink
        william.cox William Cox (Inactive) added a comment -

        Make testEvent a string rather than a boolean. A particular installation would have to look at the strings for meaning, but the boolean treatment could be implemented as "null string" or "not present". Cardinality [0..1]

        Show
        william.cox William Cox (Inactive) added a comment - Make testEvent a string rather than a boolean. A particular installation would have to look at the strings for meaning, but the boolean treatment could be implemented as "null string" or "not present". Cardinality [0..1]
        Hide
        Permalink
        william.cox William Cox (Inactive) added a comment -

        See also comment from Toby Considine on 212:

        "If you want the complete suite of Events in Test, wuldn't that argue instead for being able to put a Test flag on all Event, Quote, and Program services? "

        This includes testEvent as redefined on EiStatus and EiEvent classes; should it be in more places?

        Should it be an attribute in the schemas?

        Show
        william.cox William Cox (Inactive) added a comment - See also comment from Toby Considine on 212: "If you want the complete suite of Events in Test, wuldn't that argue instead for being able to put a Test flag on all Event, Quote, and Program services? " This includes testEvent as redefined on EiStatus and EiEvent classes; should it be in more places? Should it be an attribute in the schemas?
        Hide
        Permalink
        william.cox William Cox (Inactive) added a comment -

        Added testEvent: string to EiEvent and EiStatus classes.

        See notes for ENERGYINTEROP-205 (this issue) for possible other places this should/could be used.

        Show
        william.cox William Cox (Inactive) added a comment - Added testEvent: string to EiEvent and EiStatus classes. See notes for ENERGYINTEROP-205 (this issue) for possible other places this should/could be used.

          People

          • Assignee:
            william.cox William Cox (Inactive)
            Reporter:
            bbartell Bruce Bartell (Inactive)
          • Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: