dengc367 opened a new pull request, #14310:
URL: https://github.com/apache/gravitino/pull/14310
### What changes were proposed in this pull request?
Add `design-docs/gravitino-ontology-design.md`, a design for three
metalake-level objects that let
Gravitino describe business semantics:
1. **Ontology** — an Apache Ossie `ontology.json` document: concepts
(`EntityType` / `ValueType`),
relationships with cardinality and required natural-language phrasings,
and IRIs.
2. **OntologyMapping** — an Ossie mapping document binding a Semantic
Model's datasets, fields and
relationships onto ontology concepts. Ossie deprecates embedding this map
in the ontology, so it is
a separate entity.
3. **Page** — a governed definition of a business term: description,
synonyms, Markdown body, related
assets, sources, owner, and draft/published state.
The document also covers scoping, privileges and visibility, REST and MCP
surfaces, alternatives
considered, and a phased task breakdown.
### Why are the changes needed?
The Semantic Model design defers this work explicitly:
> **Ontology management.** Apache Ossie Ontology definitions and mappings
are separate metadata
> concepts and require their own design.
Domains group assets by tag but define no concepts, and Semantic Models hold
metrics and joins but do
not say what a concept means. Two questions therefore have no home today:
what concepts exist and how
they relate, and what a term means and who vouches for it.
The design separates the machine-readable concept graph, which conforms to
Ossie, from the narrative
layer, which Ossie does not define. It proposes no separate Glossary entity
because the reference
implementation, Databricks Unity Catalog semantics, defines terms through
Pages.
Fixes #14309
### Does this PR introduce _any_ user-facing change?
No. This PR adds a design document only; there are no code, API or
configuration changes.
### How was this patch tested?
Not applicable — documentation only. No build or test behavior is affected.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
