What we have discussed here is putting a gateway b/w the Pan and the Internet at large such that:
- External world uses normal HTTP / XML oBIX
- Internal PAN used Chopan / Binary oBIX
In this design there is no loss of fidelity in that the protocol and data model is exactly the same on both sides of the gateway - just different encodings.
The goal is that "enterprise" guys just use normal HTTP and XML.
On Thu, Aug 20, 2009 at 2:17 PM, Considine, Toby (Campus Services IT) <> wrote:
While early products are building system integration products,
we have to keep the focus on the purpose of oBIX as an Enterprise interface to
building systems. If the alternate oBIX encoding is entirely subsumed behind a
wireless gateway to a wireless oBIX gizmo, this does not matter much. If we
expect enterprise programmers to now start using oBIX specific libraries, that
that is a problem.
Whatever tight serialization we use, it should be as open, as
unquirky. As widely adopted as we can manage.
