[OASIS Issue Tracker] Issue Comment Edited: (ENERGYINTEROP-541) 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?

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28350#action_28350 ] 

William Cox edited comment on ENERGYINTEROP-541 at 10/26/11 1:55 PM:
---------------------------------------------------------------------

Corrected Resolution to match wd32 descriptions.

emix:MarketContextType is of type anyURI, so acts as an ID to the full EiMarketContext which has additional elements.  Clarifications applied throughout the document.

      was (Author: william.cox):
    Corrected Resolution to match wd32 descriptions.
  
> 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?
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-541
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-541
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Sub-task
>          Components: schema
>    Affects Versions: wd27
>         Environment: OpenADR
>            Reporter: Toby Considine
>            Assignee: Toby Considine
>             Fix For: wd29
>
>
> : 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