[OASIS Issue Tracker] Commented: (ENERGYINTEROP-295) 247: MissingInteractions and Data Elements

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

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

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

The EiRegister service was, as observed, designed for Party registration.  The items with * below seem to be specialized Parties (with the role being more specifically described).

Among the suggested changes:

Section 1.0 of the linked document includes registration of:

Service Location
Asset Group
Resource
Scheduling Entity*
Meter Authority*
Load Serving Entity*
Transmission/Distribution Service Provider*

Items marked with * have a separate enrollment verification described as asynchronous; the synchronous response to a EiRegisterParty does not directly address the request.

It would appear that the rejection details could be part of the response payloads by adding an attribute eiResponse: String [0..1] to each response payload, similar to other services. Would that address the rejecstion details and qualification rejection?

Moving to the issue of asynchronous registration/enrollment, this is part of the general pattern issue and should be addressed. One approach would be for the  the initial service operation response with registeredParty to optionally have a "EiConfirmRegistration" step. In the alternative, a service (e.g.) EiEnrollParty would have parallel and explicit token return, status update check, and confirmation of verification.

For the following suggest the items in square brackets:
Service Location [use IinterfacePricingPoint as in EMIX-130]
Asset Group [how does this differ from Resource?]
Resource [agree that it's not a Party except in a very general sense. use EMIX Resources. Is registration necessary?]

Comments welcome.






> 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: William Cox
>            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