Uploaded image for project: 'OASIS Energy Interoperation TC'
  1. OASIS Energy Interoperation TC
  2. ENERGYINTEROP-389 Collector EiEvent Family refactoring against WIP 5 of the schemas
  3. ENERGYINTEROP-398

Near versus Far - What's needed?

    XMLWordPrintable

    Details

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

      Toby Considine

    • Resolution:
      Hide

      Fully supported in existing schemas

      <xs:simpleType name="EventStatusType">
      <xs:union memberTypes="eitc:EventStatusEnumeratedType eitc:EiExtensionType"/>
      </xs:simpleType>
      <xs:simpleType name="EventStatusEnumeratedType">
      <xs:restriction base="xs:token">
      <xs:enumeration value="none">
      <xs:annotation>
      <xs:documentation>No event pending</xs:documentation>
      </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="far">
      <xs:annotation>
      <xs:documentation>event pending in the far future. The exact definition of how far in the future this refers is dependent upon the DR program, but typically means the next day.</xs:documentation>
      </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="near">
      <xs:annotation>
      <xs:documentation>event pending in the near future. The exact definition of how near in the future the pending event is active is dependent on the DR program</xs:documentation>
      </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="active">
      <xs:annotation>
      <xs:documentation>The event has been initiated and is currently active.</xs:documentation>
      </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="completed">
      <xs:annotation>
      <xs:documentation>The event has completed.</xs:documentation>
      </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="cancelled">
      <xs:annotation>
      <xs:documentation>The event has been canceled.</xs:documentation>
      </xs:annotation>
      </xs:enumeration>
      </xs:restriction>
      </xs:simpleType>

      Show
      Fully supported in existing schemas <xs:simpleType name="EventStatusType"> <xs:union memberTypes="eitc:EventStatusEnumeratedType eitc:EiExtensionType"/> </xs:simpleType> <xs:simpleType name="EventStatusEnumeratedType"> <xs:restriction base="xs:token"> <xs:enumeration value="none"> <xs:annotation> <xs:documentation>No event pending</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="far"> <xs:annotation> <xs:documentation>event pending in the far future. The exact definition of how far in the future this refers is dependent upon the DR program, but typically means the next day.</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="near"> <xs:annotation> <xs:documentation>event pending in the near future. The exact definition of how near in the future the pending event is active is dependent on the DR program</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="active"> <xs:annotation> <xs:documentation>The event has been initiated and is currently active.</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="completed"> <xs:annotation> <xs:documentation>The event has completed.</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="cancelled"> <xs:annotation> <xs:documentation>The event has been canceled.</xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType>

      Description

      ENERGYINTEROP-382 - splitting the near/far question

      Per Ed Koch to address simple clients (OpenADR1). Typcally have only an "in the future" and "now".

      Is this even needed in EI? Concept may not be needed.

      "<xs:documentation>event pending in the far future. The exact definition of how far in the future this refers is dependent upon the DR program, but typically means the next day.</xs:documentation> "

      EK: Need pending if not this; different strategies for things you have to do far in advance like pre-cooling. Difference in the strategy you'd apply - "far" means you can do something.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: