[OASIS Issue Tracker] Commented: (ENERGYINTEROP-614) EIReports section is still very unclear

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

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

Toby Considine commented on ENERGYINTEROP-614:
----------------------------------------------

Could you describe the few simple feedback cases you want to support, in English (no need for xml), so I can demonstrate (or fail) how to use the report services?

thanks

> EIReports section is still very unclear
> ---------------------------------------
>
>                 Key: ENERGYINTEROP-614
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-614
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>            Reporter: Ed Koch 
>            Assignee: William Cox
>
> I honestly still do not understand how to use the EIReports to do some of the very simple feedback use cases that I want to support. The sections seems to be a muddled collection of services and it is not clear what services are really required and how you would use them. There seem to be a bunch of bureaucratic services for creating "historians" and "report specifications", but how they are tied together and used is very unclear. If I can't understand this then I honestly don't know how someone coming into this cold has a hope of understanding it.
> For example on line 1707 it says "EiReport is prepared by a Party upon request and supplied to the requesting party. It may also be defined in the expectations of the Market Context."  Does this mean that the only way a report can be generated is by request? The simple use cases deployed today do not require any registrations or report specification services or any of this overhead. The report specifications and what not are created by convention and while some systems may want to employ all these extra meta data services they should not be required.

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