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-376

EventInfoType needs clarification

    XMLWordPrintable

    Details

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

      Toby Considine

    • Proposal:
      Hide

      Use this instead - replace all event-Ids. Note the extensibility as well.

      <xs:element name="eiEventInfoType" type="eitc:EiEventInfoTypeType"/>
      <xs:simpleType name="EiEventInfoTypeType">
      <xs:union memberTypes="eitc:EiEventInfoTypeEnumeratedType eitc:EiExtensionType"/>
      </xs:simpleType>
      <xs:simpleType name="EiEventInfoTypeEnumeratedType">
      <xs:annotation>
      <xs:documentation>each event type should have an ID[tc - what does this mean? Should this be more complex than an enum?] Price responsive Reliability responsive / Instead of deployment - say price/rel level Reliab level, percent, event / Price response - mutliple, relative / Add reliability? on hierarchy side. Receive RTP comm – want to send RTP info. DR should fall under that. Next layer is grid reliab or emerg signals. First RTP
      Then DR (rel and pric) Emergency?</xs:documentation>
      </xs:annotation>
      <xs:restriction base="xs:string">
      <xs:enumeration value="LoadLevel"/>
      <xs:enumeration value="LoadAmount"/>
      <xs:enumeration value="LoadPercentage"/>
      <xs:enumeration value="GridReliability"/>
      <xs:enumeration value="PriceRelative"/>
      <xs:enumeration value="PriceMultiple"/>
      </xs:restriction>
      </xs:simpleType>

      Show
      Use this instead - replace all event-Ids. Note the extensibility as well. <xs:element name="eiEventInfoType" type="eitc:EiEventInfoTypeType"/> <xs:simpleType name="EiEventInfoTypeType"> <xs:union memberTypes="eitc:EiEventInfoTypeEnumeratedType eitc:EiExtensionType"/> </xs:simpleType> <xs:simpleType name="EiEventInfoTypeEnumeratedType"> <xs:annotation> <xs:documentation>each event type should have an ID [tc - what does this mean? Should this be more complex than an enum?] Price responsive Reliability responsive / Instead of deployment - say price/rel level Reliab level, percent, event / Price response - mutliple, relative / Add reliability? on hierarchy side. Receive RTP comm – want to send RTP info. DR should fall under that. Next layer is grid reliab or emerg signals. First RTP Then DR (rel and pric) Emergency?</xs:documentation> </xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="LoadLevel"/> <xs:enumeration value="LoadAmount"/> <xs:enumeration value="LoadPercentage"/> <xs:enumeration value="GridReliability"/> <xs:enumeration value="PriceRelative"/> <xs:enumeration value="PriceMultiple"/> </xs:restriction> </xs:simpleType>
    • Resolution:
      Hide

      Overtaken by events; changed title to indicate EiEventInfo relatoinship.

      Show
      Overtaken by events; changed title to indicate EiEventInfo relatoinship.

      Description

      Reading all the schemas, it appears to be more of a type than an ID. Either we are using the same name for two things, or we shonge what the "thing" is.

      NOTE original title was "EventID needs some clarification"

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: