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] Created: (OBIX-214) 14.1 History Object (value metadata)

14.1 History Object (value metadata)

                 Key: OBIX-214
                 URL: http://tools.oasis-open.org/issues/browse/OBIX-214
             Project: OASIS Open Building Information Exchange (oBIX) TC
          Issue Type: Improvement
          Components: OBIX 1.1 Specification
    Affects Versions: OBIX 1.1 XSD PR02
         Environment: Brian Frank
            Reporter: Toby Considine
            Assignee: Craig Gemmill 

Experience with oBIX shows that we absolutely need all the history meta-data at this level.  Today the only way to get this information is to actually make a query against the history data which is very inefficient, slow, and buggy.  At the very least we need to know a) if history is number, boolean or enum and b) unit if numeric history.  I'm sort of thinking the best way to tackle this is to have a prototype child object:
  <obj href='obix:History'>
      <real name='valueProto' unit='obix:units/fahrenheit'/>
Or we could potentially have an endValue that defined this (and was null if size was zero).

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


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