The ISO 21000-6 Glossary You Actually Need: 10 Rights Metadata Terms That Define Successful Implementation
Implementing ISO 21000-6 without a firm command of its core vocabulary is analogous to configuring a network without understanding IP addressing — the mechanics may proceed, but the outcomes will be unreliable. The MPEG-21 Rights Data Dictionary is a formally structured specification, and its terminology carries precise meanings that diverge, sometimes significantly, from how similar words are used in everyday licensing conversations.
This reference is designed for engineers and compliance officers in the early stages of ISO 21000-6 implementation. Each entry below pairs the term's formal definition within the specification with applied context relevant to the US media market. Bookmark this page. You will return to it.
1. Rights Data Dictionary (RDD)
Formal definition: A structured, hierarchical collection of terms and their definitions, designed to provide a controlled vocabulary for expressing rights-related concepts in a machine-processable format.
Practical context: The RDD is the core deliverable of ISO 21000-6. It is not a rights management system, a licensing platform, or a contract template — it is a dictionary. Its value lies in providing shared semantic meaning across disparate systems. When a US streaming platform and an international content licensor both reference the same RDD term, they are working from an identical definition, regardless of what their internal systems call the equivalent concept. Think of it as a Rosetta Stone for rights metadata interoperability.
2. Intellectual Property (IP) Entity
Formal definition: Any identifiable asset — whether a work, a performance, a recording, or a derivative — that is subject to intellectual property rights and can be described within the RDD framework.
Practical context: This term is broader than it may initially appear. In a US streaming context, an IP Entity might be a feature film, but it could equally be a specific dubbed version of that film, a trailer, a behind-the-scenes featurette, or a still image extracted from the production. Implementers must establish clear policies about which assets in their catalog will be treated as discrete IP Entities within their RDD-compliant metadata schema, because each entity can carry its own rights profile.
3. Right
Formal definition: A permission or entitlement associated with an IP Entity, specifying what actions may be performed with respect to that entity, under what conditions, and by whom.
Practical context: Within the RDD, a Right is not a vague contractual concept — it is a structured data element with defined attributes. For a US broadcaster, this might encode the entitlement to transmit a specific program within a defined geographic territory during a specified time window. The precision of the RDD's Right definition is what makes automated rights checking feasible: a system can evaluate whether a proposed action falls within the bounds of a recorded Right without human interpretation.
4. Condition
Formal definition: A constraint or requirement that must be satisfied in order for a Right to be exercised, potentially including temporal, geographic, technical, or commercial parameters.
Practical context: Conditions are where the complexity of real-world licensing agreements gets encoded into structured metadata. A US SVOD platform might hold the right to stream a particular title, subject to conditions including: availability only to subscribers within the contiguous 48 states, maximum resolution of 4K, and a window expiring 18 months from the contract execution date. Each of these is a Condition in RDD terms. Implementers frequently underestimate the number of distinct Conditions present in their existing licensing agreements — a thorough audit is essential before schema design begins.
5. Principal
Formal definition: Any party — individual, organization, or automated agent — that holds, grants, or is subject to Rights within the RDD framework.
Practical context: In US media licensing, Principals typically include content owners, licensees, sub-licensees, and distributors. The RDD's treatment of Principal is notable because it explicitly accommodates automated agents — meaning that a rights management system acting on behalf of an organization can itself be identified as a Principal. This has direct relevance for organizations implementing automated content supply chains, where systems rather than humans may be initiating rights transactions.
6. Rights Expression
Formal definition: A formally structured statement that associates one or more Rights with a specific IP Entity and one or more Principals, encoded in a machine-readable format consistent with the RDD vocabulary.
Practical context: A Rights Expression is the atomic unit of rights communication within an ISO 21000-6-compliant system. It is, in essence, a machine-readable sentence that states: this Principal may perform this action on this IP Entity under these Conditions. For implementers building rights exchange interfaces with partner organizations — say, a US distributor connecting with a European rights clearance organization — the Rights Expression is the data structure that travels between systems. Its integrity depends entirely on both parties using RDD-defined terms with consistent meaning.
7. Namespace
Formal definition: A formally declared identifier that scopes a set of terms within the RDD, distinguishing definitions originating from the core specification from those introduced by extension or by specific communities of practice.
Practical context: Namespaces matter enormously in implementation. The core ISO 21000-6 namespace contains the base vocabulary of the standard. However, industry sectors — including US broadcast organizations and music licensing bodies — may define extension namespaces that introduce domain-specific terms while maintaining interoperability with the core specification. Implementers must be explicit about which namespace any given term belongs to, particularly when exchanging data with partners who may be operating under different extension sets. Namespace confusion is a common source of interoperability failures in early-stage implementations.
8. Unique Identifier
Formal definition: A globally unambiguous reference assigned to an IP Entity, a Principal, or a Rights Expression, enabling consistent identification across systems and organizational boundaries.
Practical context: In the US market, content is already identified by a range of industry identifiers — ISAN for audiovisual works, ISRC for sound recordings, EIDR for entertainment content. ISO 21000-6 does not mandate a specific identifier scheme but requires that whatever identifier is used be globally unique and consistently applied. Implementers must make deliberate decisions about identifier strategy early in the project, particularly when their catalog contains content that may be identified differently across internal systems and partner databases.
9. Action
Formal definition: A defined operation that may be performed with respect to an IP Entity, such as reproduction, distribution, public performance, synchronization, or transformation, as enumerated within the RDD.
Practical context: The RDD's taxonomy of Actions is one of its most practically consequential components. In US licensing contexts, the distinction between Actions such as "reproduce," "distribute," and "communicate to the public" maps directly to the categories of rights recognized under US copyright law and the contractual language used in licensing agreements. Implementers should systematically map their existing contract vocabulary to RDD Action definitions during the gap analysis phase, as misalignment here will propagate errors throughout the entire rights metadata schema.
10. Rights Holder
Formal definition: A Principal that possesses one or more Rights with respect to an IP Entity, whether through original creation, contractual assignment, or statutory provision.
Practical context: The RDD treatment of Rights Holder is more nuanced than the term's casual usage in the industry might suggest. The specification recognizes that rights holding is not binary — an organization may hold certain Rights with respect to an IP Entity while lacking others. A US music publisher, for example, might hold synchronization rights to a composition without holding the mechanical rights. Implementers must ensure that their metadata schema captures rights holding at the level of individual Rights, not merely at the level of the IP Entity as a whole. Conflating these levels is one of the most common structural errors in early ISO 21000-6 implementations.
Building Vocabulary Before Building Systems
The ten terms above do not exhaust the ISO 21000-6 specification — the full RDD contains a substantially larger vocabulary. However, these entries represent the conceptual foundation upon which compliant implementations are built. Engineers who internalize these definitions before writing a line of integration code, and compliance officers who apply them before drafting metadata governance policies, will encounter significantly fewer costly corrections downstream.
The MPEG-21 Rights Data Dictionary rewards precision. Organizations that invest in vocabulary mastery at the outset of their implementation projects are the ones that arrive at interoperable, auditable, and scalable rights metadata infrastructure — rather than discovering midway through that their schema was built on ambiguous foundations.
This reference will be expanded as the ISO 21000-6 Standards Hub continues to document implementation guidance for the US market. Practitioners are encouraged to consult the full specification text alongside resources published here for authoritative definitional guidance.
