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

Need more explicit definition of how wscal::Sequnce is used to describe the EiEvent time periods (WD16 - 642)

    XMLWordPrintable

    Details

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

      Ed Koch wd16 line 642

    • Resolution:
      Hide

      Create examples of how core concepts from WS-Calendar and EMIX (schedule and terms) are used in Energy Interoperation. See also Issue 238. Addesection describing core concepts.

      Show
      Create examples of how core concepts from WS-Calendar and EMIX (schedule and terms) are used in Energy Interoperation. See also Issue 238. Addesection describing core concepts.

      Description

      There does not appear to be enough definiton of how the wscal:Sequnce is used to describe the different time periods associated with EiEvent. I think this issue goes beyond just adding a descriptiobn of wscal, but requires us to further identify the time periods such as "StartTime" and "EndTime" and show how wscal is used to represent them. For the overall EiEvent we need as a minimum:

      Notification time
      Start time
      End time - note that some dispatches that may use EiEvent may be open ended with no edn time to this could be optional

      Optinally we could add the various ramp times.

      We also need to further show how a sequence of EventInfo instances are represented as a sequence witin the the Starttime - Endtime interval.

        Attachments

          Activity

            People

            • Assignee:
              toby.considine Toby Considine (Inactive)
              Reporter:
              ed.koch Ed Koch (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: