OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Updated: (ENERGYINTEROP-572) Wip 8 Schema : Why does eiRequestMarketContext refer to venID, Resouce ID and a request for status?


     [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated ENERGYINTEROP-572:
--------------------------------------

    Environment: Ed Cazalet  WD 29 WIP 8 Schema  (was: WD 29 WIP 8 Schema)
     Resolution: 
No action required. The venID, vtnID, and resourceID are optional, so a transactive implementation need not use those at all, providing exactly what's requested.

Close no action.

The other elements are optional. For transactive use, they are not required.

The wd32 elements are 
marketContext [1..*]
venID [0..1]
resourceID [0..*]
vtnID [0..1]

The semantics will be more clear in wd33. In short, the market context(s) are required. The others are optional and restrict the information to those that meet those other criteria. If a marketContext is not relevant to (say) vtn XYZ then there is no response on that marketContext.

> 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
>    Affects Versions: wd28
>         Environment: Ed Cazalet  WD 29 WIP 8 Schema
>            Reporter: Edward Cazalet 
>            Assignee: William Cox
>             Fix For: wd32
>
>
> 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]