Uploaded image for project: 'OASIS Energy Interoperation TC'
  1. OASIS Energy Interoperation TC
  2. ENERGYINTEROP-515 Collector for OpenADR Alliance Comments EI PR02
  3. ENERGYINTEROP-508

Section 10 - Why would the requestStatus operation contain market context in the payload? Perhaps having an ID of some sort might make sense to filter the request response, but why the entire marketContext?

    XMLWordPrintable

    Details

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

      Recommend making the emix:maketContext mandatory in the event (EiEventType), and have another means/service to request an entire eiMarketContext when needed.

      Show
      Recommend making the emix:maketContext mandatory in the event (EiEventType), and have another means/service to request an entire eiMarketContext when needed.
    • Resolution:
      Hide

      emix:marketContext is 1..1 in EventDescriptorType.

      New service EiMarketContext has operations Request and Reply. A Request passes at least one emix:marketContext (which acts as an ID for the EIMarketContext) and returns the relevant EiMarketContexts.

      payloads:EiRequestEventType should include elements
      marketContext: emix:MarketContextType [0..*]

      Note that this does not associate the requested URIs with the returned EiMarketContext, but the requested URI is a key and is in each EiMarketContext returned.

      Show
      emix:marketContext is 1..1 in EventDescriptorType. New service EiMarketContext has operations Request and Reply. A Request passes at least one emix:marketContext (which acts as an ID for the EIMarketContext) and returns the relevant EiMarketContexts. payloads:EiRequestEventType should include elements marketContext: emix:MarketContextType [0..*] Note that this does not associate the requested URIs with the returned EiMarketContext, but the requested URI is a key and is in each EiMarketContext returned.

      Description

      : Section 10 of the EI specification describes Market Context indicating that both parties in
      a transaction can have a "market context". Furthermore, the narrative framework (section 5.3)
      describes VEN's querying VTNs for their market context. However, when looking at the schema, the only
      two places where market context appears in the payload is as follows:
      1) Various eiOpt payloads, in both the requests and responses. We assume that the responses are just a
      mirror of the requests marketContext. If not, this needs to be described.
      2) In eiRequestStatusPayload and as part of eiSentStatusPayload eiEventDescriptor.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: