Extended Metatada Proposal for OSI
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- data
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.
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
- Dominant language
- Python
- Stars
- 2.7k
- Forks
- 353
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 86
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/ossie
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
validation: field reference resolution is case-insensitive but name uniqueness is case-sensitivePossibly taken @MikeNitsenko claimed this 6 days ago. Openneeds-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
apache/ossie#710 · 6 comments ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
apache/ossie#707 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
integration: media_player
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
home-assistant/core#193344 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
daniel-ospina/tortoise#13607 ·
Maintainers usually reply within 1 day
-
documentation priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 66/100
Robin-IA/Congressional-Letters-Dev#1347 ·
Maintainers usually reply within 1 day