14.1 History Object (value metadata)

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'/>
</obj>

Or we could potentially have an endValue that defined this (and was null if size was zero).