[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (ENERGYINTEROP-508) Section 10 - Whywould the requestStatus operation contain market context in the payload?Perhaps having an ID of some sort might make sense to filter the requestresponse, but why the entire marketContext?
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: Improvement Components: schema Affects Versions: wd27 Environment: OpenADR Reporter: Toby Considine Assignee: Toby Considine : 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]