Onvif recently announced it is implementing open source for its network interface specifications for physical security technology. The move aims to streamline administrative and collaborative processes while also leveraging the collective ingenuity of the global developer community.
Onvif interoperability specifications are already publicly available as open standards and are widely used as common communication interfaces between devices and software clients, such as IP surveillance cameras, video management software and physical access control systems from different manufacturers.
The use of GitHub, an online open source development platform, will allow for easier contribution and collaboration on Onvif specifications by applying state-of-the-art software development tools to specification engineering. This will enable software engineers and developers from security, IoT, Artificial Intelligence, cloud services and other industries to contribute new ideas and proposals, spurring greater feature interoperability and new interface specifications that will help Onvif continue to contribute to these industries. Other important aspects of Onvif, such as the development of Onvif profiles and test tools, the conformant product submission process, the activities of the Onvif committees and working groups, and the Onvif membership and governance structure remain unchanged.
“The data that powers our businesses and homes relies on feature-rich and standardized pathways of communications for interoperability, and Onvif will continue to evolve to provide those pathways,” said Per Björkdahl, chairman of the Onvif Steering Committee. “Augmenting our development methods with open source adds a collaborative and convenient platform through which innovative ideas can be discussed and implemented and eases many of the administrative burdens that are inherent in the standards development process.”
The source files of Onvif specification-related documents, including schema files, which describe the XML framework of specific Onvif features and functions, will be available on GitHub. The Onvif Technical Committee will continue to govern the integration of new technical proposals and, once approved according to the Onvif Rules of Membership, these will be published on the Onvif website. All contributors are required to sign an Onvif Contributor License agreement, and any changes that are ultimately accepted by the Onvif Technical Committee will be licensed to Onvif.
Over the course of its eleven-year history, Onvif has developed several profiles, which are groupings of certain functionalities derived from established Onvif network interface specifications, that enable the performance of set features for common uses: Profile S for streaming video; Profile G for video recording and storage; Profile C for physical access control; Profile Q for quick installation, Profile A for broader physical access control configuration and Profile T for advanced video streaming.
While profile development will not be a part of the open source strategy, Onvif widely expects that specification contributions realized via open source will support the development of future profiles.
