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] Commented: (ENERGYINTEROP-295) 247: MissingInteractions and Data Elements



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

William Cox commented on ENERGYINTEROP-295:
-------------------------------------------

Section 3 of the referenced document:

Examples are needed; can this section be described as only deployment? The communications are addressed in the service operations and can be implemented with whatever communication characteristics are required (e.g. reliability, security)

Re Section 2: the separation of Award, Schedule, and Event/Notification needs discussion. Award would seem to be a market notification (addressed via  EiContract, but I'm not clear as to the distinction between Schedule and Event/Notification--is Schedule a function in the VTN (the ISO in these examples) that is reflected in the sending of an Event that tells the VTN when to perform>

> 247:  Missing Interactions and Data Elements
> --------------------------------------------
>
>                 Key: ENERGYINTEROP-295
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-295
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: spec
>    Affects Versions: csd01 - Public Review Draft
>            Reporter: Edgardo Luzcando 
>            Assignee: Edgardo Luzcando 
>            Priority: Critical
>
> "The service definitions provided by the IRC cannot be fully mapped to the existing specification.  See details of current mappings here: http://www.oasis-open.org/apps/org/workgroup/energyinterop/download.php/40404/Mapping_IRC-to-EITC_Interactions_20101124.docx.  All 35 Interactions need to be accounted for to account for the IRC requirements.  The payloads of the interactions are largely missing as well.  There is an understanding that the Interactions (and corresponding payloads) currently missing are not there because they specificication is still under development, but there is concern of when this will be incorporated into the specification to allow sufficient time to review.
> This issue affect a large portion of the specification (namely sections 7, 8 and 9) where all the current EI services are defined.  These services do not currently include the IRC Interactions and corresponding data elements."

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