Allow mechanism for interactions between VEN andVTN for transactions.

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Fixed
    • Priority: Major
    • wd22
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:

      Girish Ghatikar wd15 lines 643-649; wd16 lines 643-649

    • Hide

      EventInfoTypeID is a class, eventStateID seems to be what you're suggesting but it's not clear how you suggest applying it

      Show
      EventInfoTypeID is a class, eventStateID seems to be what you're suggesting but it's not clear how you suggest applying it
    • Hide

      Corrected with applied solutions to ENERGYINTEROP-342 and 343 correcting EiEvent payloads.

      Show
      Corrected with applied solutions to ENERGYINTEROP-342 and 343 correcting EiEvent payloads.

      Allow mechanism for interactions between VEN and VTN for transactions/ For example, the eventStateID in OpenADR 1.0 is intended to handle transactions by avoiding data payload issues. Other option (may be better) is to create a framework that allow creation of multiple XSDs for each of the types.

            Assignee:
            Girish Ghatikar (Inactive)
            Reporter:
            William Cox (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: