OBIX Migration 2008-02-25T22:13:47-07:00

HOME Forums Gateways EZSrve OBIX Migration

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • Anonymous
    Post count: 408
    #39884 |

    There is a consideration to migrate to OBIX for the XML API, this will remove backwards compatibility, but greatly improve our ability to interface with other networks.

    If we migrate – we are going to have to abandon backwards compatibility for the API only – note the web interface will NOT be affected.

    The question to developers is, what do you think?

    Here is the link:

    Post count: 69

    Would this mean the LinuxMCE guys would have to re-write their code, too?

    Post count: 408

    I am now using the LinuxMCE plugin – I would not want to leave that out.

    We are discussing options, but I guess the first question is, do the developers out there see any shortcoming in the current API, or benefit in OBIX?

    As for options, we may leave the original API in place as well, with OBIX as an option to enable…

    Post count: 20

    I’m not familiar with oBIX, but it looks like it’s just an XML interface, but with a standard vocabulary, right? In that case, it’s probably a good idea.

    On the other hand, I’ve noted in the past that the XML interface you’ve got is really over-permissive and doesn’t exactly conform to XML standards, so if you do want to go to a standard like oBIX, you’ll probably have to make XML conformance a lot more strict…

    Post count: 408

    For now, we will not be migrating to OBIX – we do not see a pressing need, and talking to others outside of this forum who use the API, it sounds like a pain for those out there.

    Sorry for the heart attack to a few of you…

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.