[OASIS Issue Tracker] Created: (ENERGYINTEROP-598) The EiReport service interactions for Historian - eliminate StopHistorian, add flag to CancelHistorian to indicate "send final report"

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

The EiReport service interactions for Historian - eliminate StopHistorian, add flag to CancelHistorian to indicate "send final report"
--------------------------------------------------------------------------------------------------------------------------------------

                 Key: ENERGYINTEROP-598
                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-598
             Project: OASIS Energy Interoperation TC
          Issue Type: Improvement
         Environment: William Cox - EITC 20111026
            Reporter: William Cox
            Assignee: William Cox


Discussion was around eliminating StopHistorian versus CancelHistorian. The former indicates that the rest of the recorded information may be picked up, the latter to discard.

Gerry Gray suggested that a flag on CancelHistorian that says either 
(a) Stop what you're doing on this and you can toss everything you've saved, or
(b) Stop what you're doing on this and send a final report
would fit the interaction patterns better (rejected approach: add "ChangeHistorian" to say "stop" etc -- too much complexity)

BUT the historian is NOT the one sending the reports. It only records.

So the change would be to add SendFinalReport: boolean to CancelHistorian AND to include a reportID so you know what report to finalize and send. In this way the receiver can call their internal code to mimic a "send final report" with the reportID, AND stop the Historian at the appropriate time.

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