You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of real-world semantic layer work is not “one universal model for everyone.” Teams need to package the same semantic definitions into audience-specific views: Finance vs Sales, Exec vs Analyst, Customer-facing vs Internal, etc. OSI needs a first-class concept for packaging/audiences.
Strawman Approach
Introduce an optional top-level construct such as:
domains: groupings with metadata (owner, description, tags)
perspectives (or packages / audiences): named bundles that reference a subset of semantic assets
includes/excludes for metrics, dimensions, entities, semantic_models
optional aliases (renames) and folders for presentation
optional visibility_rules hook (even if enforcement stays vendor-specific)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
A lot of real-world semantic layer work is not “one universal model for everyone.” Teams need to package the same semantic definitions into audience-specific views: Finance vs Sales, Exec vs Analyst, Customer-facing vs Internal, etc. OSI needs a first-class concept for packaging/audiences.
Strawman Approach
Introduce an optional top-level construct such as:
Example
All reactions