by Gary Myers
Earlier this year, ObjectVideo released an updated OV Ready specification and the corresponding OV Ready reference application (which now includes an ‘event push’ functionality) to our partners to incorporate onto their devices. In addition, we provided the 1.0 version of our new web UIs, which we call the ObjectVideo management console.
For those who are unfamiliar with OV Ready, it is an ObjectVideo program that constitutes a protocol specification, reference code and compliance tools to allow interoperability between various devices and applications with respect to video analytics operations and alerting. More detailed info is provided on our website.
Even though that one-sentence summary is quite a mouthful, think of HTTP as an analogy. At a basic level, it is a protocol that specifies how web browsers and web servers can talk. It doesn’t matter if you are using Firefox or Chrome or IE, you can still talk to IIS or Apache. OV Ready is similar except the focus is on ObjectVideo OnBoard configuration, rule management and event output. We want to make sure all ObjectVideo-enabled devices (cameras, encoders, servers, etc.) can be used by a wide variety of management applications (VMS, PSIMs, etc.) regardless of type or brand.
At the technical level, the OV Ready specification defines a protocol that uses XML over HTTP/HTTPS. OV Ready is based on the REST architectural approach versus SOAP (I’ll do a post on the differences in the near future). What this means is that the XML is easy to read and the API is based around HTTP URIs so that everything is easy to understand. In fact, OV Ready and its use of REST heavily influenced the PSIA to recommend REST be the architectural basis for all forthcoming specifications, not just the standard for analytics.