[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:all-tabpanel ] Toby Considine updated OBIX-227: -------------------------------- Assignee: Craig Gemmill > 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. > 14.2.4.2 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 (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]