Beyond EBUCorePlus: Why Leaner Ontologies and Data Autonomy Win the Streaming War
To compete with streaming platforms, TV broadcasters need to develop new products quickly. I think the search for one perfect, universal data model slows them down. I propose domain ownership, data products and a minimal central ontology instead, which governs the joins between systems and not every single attribute.

When people talk about the “Streaming War”, they mostly talk about content. I would say speed is at least as important. For traditional TV broadcasters, being able to launch a new product feature or change a digital strategy within weeks instead of years is a precondition for staying relevant next to the big tech companies.
One of the things which slow down broadcasters the most is the search for the perfect, universal data model. In this article I’d like to explain why, and what I propose instead.
Why Speed Matters
To compete, two things need to happen:
- New product ideas need to get from the whiteboard into production quickly, without getting stuck in endless alignment meetings.
- We need to analyze the success of these ideas in real time. If a new recommendation algorithm or a UI change doesn’t work, we need the data to tell us now, and not in next quarter’s report.
Domain-Driven Design Instead of Global Alignment
Traditional Enterprise Data Models (EDM) try to create a single “source of truth”, in which every term is defined globally. In a TV station this does not work well. A “program” means something different to the licensing department than to the playout team or the ad-sales department:
- For licensing, a program is content which has been licensed from a licensor, together with the rights to use it. It can consist of several media files for different distribution channels, plus accompanying material.
- For playout, a program is one specific media file which is played out on a specific channel.
- For ad sales, a program is content which reaches a certain target group, e.g. adults aged 16 and older, on a specific channel at a specific time.
Strategic Domain-Driven Design (DDD) accepts that a “Ubiquitous Language” only works within the boundaries of a domain. This has a couple of consequences:
- Teams who own the language of their domain can develop much faster.
- Alignment is only required at the borders between domains.
- If you extend this autonomy into the analytical world by using Data Products, teams can take data-driven decisions locally and quickly.
Govern the Joins, Not the Attributes
Industry standards like EBUCore+ are impressive, but they are heavyweight. They define so many entities and attributes that implementing them across a whole organization can feel like a project which never ends.
My proposal is a radical reduction. Data Governance should focus on a minimal central ontology, which identifies the core entities (like a “Creation” or an “Asset”) and their global identifiers.
- Keep it lean and don’t mandate a hundred attributes.
- Focus on connectivity: as long as every system can respond to a specific ID, the data can be linked.
- Govern the joins and leave the attributes to the teams. This way small teams can innovate without having to wait for a central “Data Pope” who approves their local schema.
Search Instead of Archive Metadata
We should stop trying to define rigid, structured archive metadata formats for every single item. Instead I would start from the question of how people find things:
- Collect data in a central search index. It doesn’t matter which piece of information you start with. If it is in the index, you find the item.
- The search result only points to the source system(s) or the archive where the physical asset is stored. This way the archive is no longer a data silo, but a resource everyone can search.
The Role of Enterprise Architecture
There’s often a gap between Data Governance and the tech stack. Data Governance is good at stewardship and business alignment, but often doesn’t have the technical depth to shape operational systems.
This is where Enterprise Architecture (EA) can help. Using frameworks like TOGAF, EA looks at the big picture:
- Business Architecture: does this data flow support the process?
- Application & Infrastructure: can the system handle the bandwidth and latency requirements? Is the API gateway scalable?
Data Governance defines what is needed and why, and EA adds how it can be implemented. This way data principles do not only exist in PDF documents, but can be enforced technically and are aligned with the overall IT strategy.
Conclusion
I think large, central data departments which define everything for everyone are too slow for the streaming business. To be successful, broadcasters need to give up some central control and get governed autonomy in return. Lean ontologies, unique identifiers and Enterprise Architecture help to connect the data of autonomous teams, so that no new data silos are created.
Not everyone needs to speak the same language, as long as we make sure that people can talk to each other when it matters.