[ENERGYINTEROP-540] Market Context Collector - OASIS Technical Committees Issue Tracker

XML

Word

Printable

Market Context is used in various ways, and not always consistently. Possible assumptions (which need to be expressed) about Market Contexts are in http://www.oasis-open.org/committees/document.php?document_id=43740&wg_abbrev=energyinterop and ~~ENERGYINTEROP-508~~ (for example).

This issue is to hold as subtasks the issues related to MarketContext (or in some cases clones of them).

Progress

1.	Clarify the purpose of Ei Market Context vs. EMIX Market Context	Closed	William Cox (Inactive)
2.	Attributes in EiMarketContext not in the right context for events	Closed	Toby Considine (Inactive)
3.	Continuity of Transaction	Closed	Toby Considine (Inactive)
4.	Remove eventSchedules from eiMarketContext	Closed	William Cox (Inactive)
5.	Clone of 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?	Closed	Toby Considine (Inactive)
6.	Cloned from 509 - Section 10 - How does one know whether the marketContext returned in a Status response is just a confirmation of the request or something different?	Closed	Toby Considine (Inactive)
7.	Cloned of 507 - Section 10 - There is confusion about how to get a VTN Market Context outside the framework of a specific event	Closed	William Cox (Inactive)
8.	Line 1066 and others- using emix:marketContext instead of eitc:marketContext; Resource ID has multiplicity of -1	Closed	Toby Considine (Inactive)
9.	EiOpt and EiAvail Payloads use EiMarketContext, should be emix:MarketContext as key value.	Closed	Toby Considine (Inactive)