[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Reports, Historian, and related guidance in Energy Interoperation
Craig and others -- As promised. The references are to line numbers in the Energy Interoperation 1.0 Committee Specification, which can be downloaded at http://docs.oasis-open.org/energyinterop/ei/v1.0/ (the PDF). Direct link is http://docs.oasis-open.org/energyinterop/ei/v1.0/energyinterop-v1.0.pdf . (4.1 MBytes) Overview in Semantics of Energy Interoperation: Sections 5.4 and 5.5 Section 10 is Details of the Report Services (Service-Oriented Architecture; these are the interactions - request and response - to use the report service, with payloads and WSDL specified). This section includes the Historian, which is an extension and update using the obix 1.0 historian approach: Section 10 pages 106-113. An example using streams and reports is at line 948. I would recommend that we adapt or adopt this approach, with the report types consistent with obix value approaches (for 1.x) and evolve to a view of reports that includes the streams work now being standardized in WS-Calendar and largely consistent with Energy interoperation. Note that OpenADR2 events and reports conform to the referenced sections with some simplifications (and a REST binding). Thanks! bill --
William Cox Email: wtcox@CoxSoftwareArchitects.com Web: http://www.CoxSoftwareArchitects.com +1 862 485 3696 mobile +1 908 277 3460 fax |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]