Over the last few years the European Broadcasting Union (EBU) and its members have developed metadata specifications to facilitate the search and exchange of content.
EBU Tech 3293 (EBUCore) is the flagship of EBU's metadata specifications. Combined with the EBU Class Conceptual Data Model (CCDM) of simple business objects, EBUCore provides the appropriate framework for descriptive and technical metadata for use in Service Oriented Architectures and also in audiovisual ontologies for semantic web and linked data developments . EBUCore has been adopted by several broadcasters around the world. It is referenced by the UK DPP (Digital Production Partnership). It has been selected as the best 'core' and integrated in MediaCorp' metadata framework. It is the foundation of technical and descriptive metadata in FIMS 1.0. It is also the metadata scheme of reference in the project EUScreen (European portal on audiovisual public archives counting 12 EBU members and national archives), which delivers linked data to Europeana . EBUCore has been published as AES60 by the Audio Engineering Society ( AES ). The Nordiff group is also using EBUCore for metadata exchange between Nordic countries. The Swiss archive project Memoriav is using EBUCore for its Memobase. The W3C Media Annotation Ontology is based on EBU's Class Conceptual Data Model and is fully compatible with EBUCore, which mapping has been defined and published as part of the W3C specification. EBUCore is also being registered in SMPTE. EBU and Limecraft have developed a MXF SDK for embedding/extracting EBUCore metadata in MXF files. Audio and metadata experts continue their collaboration on the definition of a new metadata model to improve audio description in EBUCore.
EBUcore is also at the heart of EBU's semantic web developments. EBU has developed several collaborations with partners such as Perfect Memory developin solutions for the management, archiving, automatic indexation, and ready-for-monetization packaging of mass media contents (video). First Perfect Memory (EBUCore compliant)middleware deployments can be found at RTBF and Radio-France.
Tech 3295 (P-META) is a library of xml-based descriptive elements and datatypes now superseded by EBUCore.
The EBU is otherwise collaborating with other standardisation bodies like it is the case with IPTC on NewsML-G2, a metadata format for news exchange (EBU defined the audiovisula requirements for remoteContent and the part elements). " EBU Eurovision News Exchange " is a technical specification detailing the NewsML-G2 mapping into which data is now transmitted operationally.
The EBU has also co-published the egtaMETA specification (Tech 3340 based on EBUCore) in collaboration with egta , the association of radio and television sales houses, for the exchange of advertising files. egtaMETA is primarily a set of semantically defined attributes considered to sufficiently describe advertising clips (descriptive information like the title of the advertising spot, exploitation information like what is the period during which it shall be used, credits inc. keys persons and companies involved in the creation, post-production and release of the advertising spot and technical information about the file format and its audio, video and data components. It is also a common representation format in the form of a standardised XML schema. The egtaMETA specification has been used by the NoTube project.
The MIM-AM (Acquisition Metadata) project has published Tech 3349, which contains a set of technical metadata to be delivered from camcorders or live cameras. The EBUCore schema has been improved to allow the XML representation of this data.
The MIM-MM and FAR-BWF groups have jointly developed tech 3352 for the transport of identifiers (in particular ISRC) in BWF chunks.
All EBU metadata specifications are coherent with the EBU Class Conceptual Data Model ( CCDM ).
The SCAIE project members have played a key role in developing two new MPEG7 specifications, namely the AVDP (audiovisual description profile) and it reference implementation, respectively in part 9 and 11 of the mpeg7 specification.