[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (ENERGYINTEROP-572) Wip 8 Schema : Why does eiRequestMarketContext refer to venID, Resouce ID and a request for status?
Wip 8 Schema : Why does eiRequestMarketContext refer to venID, Resouce ID and a request for status? --------------------------------------------------------------------------------------------------- Key: ENERGYINTEROP-572 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-572 Project: OASIS Energy Interoperation TC Issue Type: Bug Components: schema Environment: WD 29 WIP 8 Schema Reporter: Edward Cazalet Assignee: William Cox Fix For: wd29 Why does eiRequestMarketContext refer to venID, Resouce ID and a request for status? Just seems out of place since Transactive Services may request market context and not convey such information. <!-- 7.5 Market Context Payloads --> <xs:element name="eiRequestEiMarketContext" type="payloads:EiRequestEiMarketContextType"/> <xs:complexType name="EiRequestEiMarketContextType"> <xs:sequence> <xs:element ref="emix:marketContext" minOccurs="1" maxOccurs="unbounded"/> <xs:element ref="eitc:venID" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>VEN for which Resource Status is requested.</xs:documentation> </xs:annotation> </xs:element> <xs:element ref="eitc:resourceID" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>Resource(s) for which status is requested.</xs:documentation> </xs:annotation> </xs:element> <xs:element ref="eitc:vtnID" minOccurs="0" maxOccurs="1"/> </xs:sequence> </xs:complexType> -- 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]