apache / apache/ossie

Extended Metatada Proposal for OSI

Open
#100 2 comments 2 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
2.1k
Forks
267
Avg merge
4d 20h
Merged PRs (30d)
24

Description

This proposal introduces a set of optional, non-executional metadata extensions to OSI semantic models to improve how data is interpreted, presented, and consumed by downstream tools and agents. While OSI effectively standardizes structural and logical semantics, there is currently limited support for conveying interpretability context such as units of measurement, display conventions, default aggregation behavior, KPI polarity, sorting preferences, and alignment to external semantic concepts. As a result, these details are often redefined or inferred inconsistently across developers, BI tools, and AI systems.

The proposed metadata fields (e.g., measurement, display_format, semantic_type, default_aggregation, desired_direction, default_sort, and semantic_mappings) are designed to be fully optional, backward compatible, and non-impacting to execution semantics. They provide a lightweight, extensible layer that enables more consistent rendering, more accurate automated reasoning, and reduced duplication across consuming systems, while aligning with ongoing OSI discussions around semantic typing (#42), metrics and aggregation (#43), and metadata extensibility (#55).

Detailed proposal here: https://docs.google.com/document/d/1DLuteF0WwlVbpD5kmHhcqa6vItqNFL4MoAQrImy6dKo/edit?tab=t.0

Contributor guide

Open the contributing guide

Research direction

Start with the linked proposal and the related discussions in issues #42, #43, and #55 to understand the intended metadata extensions and compatibility constraints. Identify the specification entry points affected; done means producing an agreed implementation plan or changes for optional metadata such as measurement, display format, aggregation, polarity, sorting, and semantic mappings without altering execution semantics.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.