Hi Mike. oBIX is a standard for building exchange which is a standardized REST Web service interface for communication. oBIX is specified around XML and generic web interface for control systems.
EBO can expose the data using RESTFUL API via a smart connector.
The question is: are you trying to consume data via the oBIX protocol or trying to transmit or both?
You can actually bind RESTFul API to oBIX via using mapping request
GET (HTTP/HTTPS) = read (oBIX)
PUT (HTTP/HTTPS) = write (oBIX)
POST (HTTP/HTTPS) = invoke (oBIX)
so in a way, you can actually map oBIX into EBO or BACnet objects using GET/PUT/POST commands.
You may find that the oBIX requirement is just there so the building data can be exposed to the IoT. Although we do not support oBIX, EBO uses RESTful API and SOAP to expose the building data using the smart connector; which in essence provides the mechanism to share data using web-services.
IF mapping needs to be done to oBIX; possibly a smart connector can be developed to accommodate that.
JACE controllers have a driver for oBIX and they can convert Bacnet objects into OBIX (XML), which in essence can be used as a gateway.
