OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

obix message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (OBIX-227) Suggestion for History Object

    [ https://issues.oasis-open.org/browse/OBIX-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55449#comment-55449 ] 

Toby Considine commented on OBIX-227:

If we are going to open up the Historian, we should also consider interoperability with the wider group of building system telemetry, particularly those used for energy usage scheduling, tracking, and reporting.These are based upon the WS-Calendar-derived STREAMS. This evolving draft has recently been recast to be based upon the WS-Calendar PIM. As implemented within OASIS Energy Interoperation, it include notions of template reports, ad hoc reports, and referencing those templates when requesting or reading a report.  

The latest draft of Streams can be found at:

The mechanism for external specification of streams, including referencing external sources can be seen in Energy Interoperation at:
In the Report Section. The key elements of reporting, including the report specifier, are described in Section 5.4
The general report service is described in  (Section 10)

FWIW, OBIX was influential in thinking about the Reprot Services of EI, now used world-wide in OpenADR. 

> Suggestion for History Object
> -----------------------------
>                 Key: OBIX-227
>                 URL: https://issues.oasis-open.org/browse/OBIX-227
>             Project: OASIS Open Building Information Exchange (oBIX) TC
>          Issue Type: Improvement
>          Components: OBIX 1.1 Schema, OBIX 1.1 Specification
>    Affects Versions: OBIX 1.1 PR03
>         Environment: Brian Frank
>            Reporter: Toby Considine
>            Assignee: Craig Gemmill 
> 14.1 History Object - HistoryCollection
> The terms "collection" and "HistoryCollection" seem sort of generic and confusing.  How about "collectMode" and "HistoryCollectMode" 
> 14.1 History Object - prototype
> Glad to finally see something like this.  However I am not quite sure how it works.  I think we need an example.
> History Query as Preformatted List
> This design requires two separate round trip requests which is pretty terrible for performance.  I think a requirement of this design is that once the history point is learned by the client system, that it can request history data with a single HTTP request.  I don't see that having an oBIX XML response before getting the data provides much value.  I would suggest this: just add a "format" field to the HistoryFilter object and when specified the result is returned in the requested MIME type.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]