Web 2.0 is often chiefly defined by it's 'interoperability' - which is the ability to work conjunctively with other technologies. Middleware is the software that makes this happen, a common example could be an API (application programming language) which are used for things like social networking plug-ins; the provider (e.g. Facebook) publishes an API for it's services, and this is then used by the developer (e.g. Wordpress) to link directly to the service. Because this middleware is designed for any potential connection to the service it can be fairly generic, reducing the need for the developer to directly contact the provider.
Because middleware allows interoperability, it is an important part of broadcast IT systems. Any IT system replacing a particular segment in broadcast technology must be able to match or improve it's interoperability. This is because assets in broadcasting are often managed by several stakeholders which may have differing equipment. However, broadcast standards (such as SDI) are standardised by organisations, and then often enforced by licencing.
Issues arise when IT systems convert standards into file systems, at which point they stop conforming to a specific standard and cannot be read by equipment designed to read that particular standard. As a result, the IT systems must have appropriate middleware to allow different stakeholders to manage assets in IT systems.
Data transfer languages such as XML can be very useful in creating such middleware.
Source: Own knowledge.
No comments:
Post a Comment