[OASIS Issue Tracker] Updated: (ENERGYINTEROP-432) Ei Response TypeProposal: WD23 - WIP7

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

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

William Cox updated ENERGYINTEROP-432:
--------------------------------------

    Resolution: Add response values per description.

Gerry and Rish may add or suggest changes to table. This can be for PR02 if it's in the Jira lists now, or a review comment.

> Ei Response Type Proposal: WD23 - WIP7
> --------------------------------------
>
>                 Key: ENERGYINTEROP-432
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-432
>             Project: OASIS Energy Interoperation TC
>          Issue Type: New Feature
>    Affects Versions: wd23
>         Environment: Girish Ghatikar
>            Reporter: Girish Ghatikar 
>            Assignee: William Cox
>             Fix For: wd24
>
>
> This is the result of discussions between Gerald and Rish with respect to EiEvent
> - Response Types = ERRORS (between a VEN and VTN)
> - Models considered = PULL and PUSH
> - The ERRORS for payloads NOT communications.
> - Focus on Mandatory elements within eiEventPayload
> - generic ERROR: mandatory filed/string is empty
> eiCreateEventPayload 
> (some of it applies to eiCreatedPayload)
> - createdTime:
>  -- xcal:dtstamp: event past current time + invalid time stamp. 
>  -- ts:accuracy: accuracy is out of tolerance
>  -- rest ignored as they seemed to be informational. 
> - vtnGluon:
>  -- xcal:uri: uri is malformed. 
>  -- cal:uid: no such uid
> -eitc:eiEvent:
>  -- eitc:eventID: event already exists
> - eitc:eventSchedules: 
>  -- itemUnits: no such units
>  -- scale: no such scale
> - resourceTarget + others generic
>  -- powerNode: No such node
>  -- powerMRID: No such MRID
> - serviceArea
>  -- emix:geographicArea: not in the Geographic area
> NOTE: 
> - Why emix:marketContext is mandatory and NOT optional?
> - Why modificationNumber in createEventPayload (should not). 

-- 
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