IMF offers great efficiencies by storing media as components which can be packaged together to make specific versions, which can then be transformed into various output formats. We therefore we have more individual files to manage, but IMF makes this easier as each file has a universal identifier. Nonetheless, it leaves us with a question: How do you get products and services to exchange assets if all they have is an ID … or two … or a thousand?
That’s where the IMF Media Management API (imf-mm-api) comes in. It’s an open source minimum viable API (application programming interface) to allow the exchange of IMF assets. The project was started as a collaboration of manufacturers, broadcasters and knowledge companies involved in the development and standardisation of IMF, led by MrMXF. It is now publicly available, and its ongoing development is managed through the DPP.
The requirements for the API are outlined on the API Requirements page.
The API is defined using OpenAPI, and is available on SwaggerHub.
A reference implementation of the API is available under an open source licence. It is available on GitHub.
A demonstration is available on MrMXF’s project page here.
A huge thanks must be given to Mr MXF, also known as Bruce Devlin, who put the project together. Other contributing members included CineCert, Dalet, EditShare, EIDR, ReinMain University, Marquise, OwnZones, PBS, Prime Focus Technologies, Signiant, and Turner.
If you’d like to use the IMF MM API, you’re welcome to access the definition and reference implementation directly. If you’d like to provide feedback, or get involved in future development, please contact Gill Reston, who manages the DPP’s IMF work.