[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Issue Comment Edited: (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=28038#action_28038 ]
William Cox edited comment on ENERGYINTEROP-508 at 10/2/11 9:06 PM:
--------------------------------------------------------------------
Suggestion here is to partially follow the proposal, and use the emix:marketContext's URI as the UID for the EiMarketContext.
An issue that remains is how to get the related EiMarketContext to get the other information in that Type. The October 2 payloads model does not add an operation but instead passes the emix:marketContext and gets back 0 or more EiMarketContexts.
The alternative is to define (e.g.)
EiRequestMarketContext which includes 1..* emix:marketContexts and
EiReplyMarketContext which includes 0..* eitc:EiMarketContexts.
One could also return anything else associated with the emix:marketContext - such as StandardTerms.
was (Author: william.cox):
Suggestion here is to partially follow the proposal, and use the emix:marketContext's URI as the UID for the EiMarketContext.
An issue that remains is how to get the related EiMarketContext to get the other information in that Type. The October 2 payloads model does not add an operation but instead passes the emix:marketContext and gets back 0 or more EiMarketContexts.
The alternative is to define (e.g.)
EiRequestMarketContext which includes 1..* emix:marketContexts and
EiReplyMarketContext which includes 0..* eitc:EiMarketContexts.
> 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
>
> : 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]