The lightweight control system interface OBIX (Open Building Information Exchange) was written originally assuming XML, i.e., fat XML. At the request of users in the field, we have recently defined standard encodings of the underlying model, in XML (obviously), JSON, COAP, and, yes, EXI. As far as I can tell, the EXI encodings of OBIX are used in internet of things applications / sensornets wherein extremely constrained bandwidth / battery power is the norm. EXI is not a “complete” specification in that one is faced with several choices, which one must make to achieve interoperability. The standard encoding for OBIX makes those choices. So yes, someone is using EXI tc "If something is not worth doing, it`s not worth doing well " -- Peter Drucker
From: Stephen Cameron [mailto:steve.cameron.62@gmail.com] Hi
For example, the concept of meta-data has a completely different meaning in science than the markup world, being something beside the data, not inside it, to the detriment of scientists I believe. Maybe a perception of XML as a textual format is part of an explanation, where CSV is good enough for most things. Does anyone actually use Efficient XML Interchange (EXI) Format? Thanks |