[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (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:comment-tabpanel&focusedCommentId=28028#action_28028 ]
Toby Considine commented on ENERGYINTEROP-508:
----------------------------------------------
This is correct. The relationship between Market Context and Standard terms in EMIX could be clearer.
Still, Market Context is presumeably largely invariant, and prices and offers (and events) vary within that. The variable MarketContext as in some sense the ID for the standard terms. There should be a way to request the StandardTerms using a marketContext.
As for the expanded information in the EiMarketContext, its all optional.
Recommend making the emix:maketContext mandatory in the event, and have another means/service to request an entire eiMarketContext when needed.
> 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
> Reporter: Toby Considine
> Assignee: William Cox
> Fix For: wd29
>
>
> : 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]