[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (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?
[ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William Cox updated ENERGYINTEROP-508:
--------------------------------------
Proposal: Recommend making the emix:maketContext mandatory in the event (EiEventType), and have another means/service to request an entire eiMarketContext when needed. (was: Recommend making the emix:maketContext mandatory in the event, and have another means/service to request an entire eiMarketContext when needed.)
Resolution:
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.
was:
EiRequestStatusPayloadType should include elements
marketContext: emix:MarketContextType [0..*]
requestEiMarketContext: boolean [0..1]
EiReplyStatusPayloadTpe should include element
eiMarketContext: EiMarketContextType [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.
Clarified Resolution with current (wd32) model.
See other issues for payload items for wd32.
> 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?
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ENERGYINTEROP-508
> URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-508
> Project: OASIS Energy Interoperation TC
> Issue Type: Sub-task
> Components: schema
> Affects Versions: wd27
> Environment: OpenADR - Cloned in ENERGYINTEROP-541 for Market Context Collector
> Reporter: Toby Considine
> Assignee: William Cox
>
> : 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]