The MXF Book
Written by a top team of industry professionals, this must-have guide introduces and explains the MXF standard, helps engineers write MXF applications, and explains the reasons behind many details of the specification documents.
TABLE OF CONTENTS The MXF Book
Chapter 13: The MXF Data Model in Context
Phil Tudor
Introduction
This chapter describes the MXF data model from the perspective of the AAF data model, from which it is derived. The MXF data model defines the data structures that can be included in an MXF file. An instance of a data structure in an MXF file is an object. An object has properties, which have a type and a value. The MXF data model defines objects by specifying a class model.
The MXF data model is expressed in terms that closely correspond to the video and audio domain. For example, it defines classes to hold metadata describing the material structure, format, derivation, and annotation; and classes to hold essence for file source material. The mapping of these objects into a file (or other persistent storage) is defined by a stored format specification. For MXF, the stored format is based on SMPTE 336M KLV encoding.
History of the MXF Data Model
The MXF data model is derived from the AAF data model, an insightful model created by Avid Technology for structuring source and editing metadata along object-oriented lines and used in the AAF file format. [1]
In 1998, the AAF Promoters, led by Avid and Microsoft, announced the AAF file format and participated in the EBU/SMPTE Task Force [2] to ensure that the AAF data model and file format would meet the requirements for standardized data transfer between authoring tools. By 2000, the independent, non-profit AAF Association had replaced the AAF Promoters and was responsible for...
Copyright Elsevier Inc. 2006 under license agreement with Books24x7
