Notifications
Clear all
Topic starter
24/06/2026 7:22 pm
TL;DR: Business context, semantics and governance are being brought directly into the lakehouse so users can trust data definitions, ownership and policy in place, while also improving semantic consistency for AI and analytics, according to Collibra. The real shift is that governed meaning becomes part of the operating model, not a separate review layer.
NHIMG editorial — based on content published by Collibra: Google Cloud and Collibra deepen their partnership to bring business context and semantics directly to the Dataplex Universal Catalog
Questions worth separating out
Q: How should teams govern data context in a hybrid lakehouse environment?
A: Teams should treat business context as an enforceable control, not a reference layer.
Q: What is the difference between a data glossary and a semantic layer?
A: A data glossary defines terms in human language, while a semantic layer defines how those terms behave in queries, calculations and downstream analytics.
Q: When does centralised governance fail in an open lakehouse?
A: It fails when policy is centralised but enforcement is not.
Practitioner guidance
- Map authoritative data context to runtime locations Identify where business glossary, ownership and policy metadata are consumed in practice, then confirm those records are available inside the same environment where analysts and AI workloads operate.
- Test metadata sync in both directions Validate that discovery updates from the lakehouse reach the system of record and that governance policies published in the catalog appear correctly in the operational environment.
- Separate glossary management from semantic enforcement Review whether definitions are merely documented or actually used in transformations, feature engineering and reporting logic, then close gaps where the two diverge.
What's in the full article
Collibra's full blog post covers the operational detail this post intentionally leaves for the source:
- How the Dataplex and Collibra integration is configured in practice across the governance and catalog layers
- Which metadata objects move inbound from Dataplex into Collibra and which business semantics move outbound into the fabric
- How the semantic layer is presented to joint customers inside Google Cloud workflows
- What Collibra says about preview availability and product documentation for implementation
👉 Read Collibra's analysis of Dataplex business context and semantic governance →
Dataplex business context and semantics: what changes for governance teams?
Explore further
25/06/2026 4:37 am
Context is becoming the control plane for trust. When business meaning, ownership and policy sit outside the operational data environment, governance becomes advisory instead of enforceable. Collibra’s partnership update reflects a broader shift: organisations are trying to make meaning portable, not just metadata visible. For practitioners, that means the control question is no longer whether data is catalogued, but whether the same context survives where analytics and AI actually consume it.
A few things that frame the scale:
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
- Another finding from the same survey shows that only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security.
A question worth separating out:
Q: How do security teams know whether governed semantics are actually working?
A: Look for consistent answers across reporting, analytics and AI outputs when the same business term is used. If finance, data science and platform teams resolve the same metric differently, the semantic layer is not operating as a control. The signal of success is not more documentation, but fewer interpretation disputes.
👉 Read our full editorial: Business context in Dataplex: what Collibra’s partnership changes
