You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ossie.apache.org by "daniyarndh (via GitHub)" <gi...@apache.org> on 2026/09/10 13:48:49 UTC
[D] Add bidirectional OpenMetadata semantic model converter (converters/openmetadata) [ossie]
GitHub user daniyarndh created a discussion: Add bidirectional OpenMetadata semantic model converter (converters/openmetadata)
OpenMetadata has emerged as a widely adopted, CNCF-sandbox, enterprise-grade unified metadata catalog. It supports rich business glossaries, metrics definitions, and lineage tracking. However, there is currently no standardized way to serialize these cataloged assets into a vendor-neutral, developer-friendly, and version-controlled format that BI engines and AI agents can consume.
By building a bidirectional converter, we bridge OpenMetadata's central governance platform with Apache Ossie's declarative semantic standard, turning OpenMetadata into a first-class participant in the Ossie ecosystem.
Proposed Design & Mapping
The converter will be written in Python, matching the structure of existing converters like `converters/dbt` and `converters/databricks`.
Attributes specific to OpenMetadata that are not representable in the core Ossie specification (e.g., column-level tags, owners, tiers, and domain classifications) will be preserved in a `custom_extensions` block using the `OPENMETADATA` vendor namespace:
```yaml
custom_extensions:
- vendor_name: OPENMETADATA
data:
owner: "finance_team"
tier: "Tier1"
tags: ["PII.Sensitive", "Finance.Reporting"]
```
The converter package may also ship a CLI, e.g.:
```bash
# Export OpenMetadata to Ossie YAML
osi-openmetadata import --api-url http://localhost:8585 --jwt-token <token> --glossary "Finance" -o finance_semantic_model.yaml
# Ingest Ossie YAML back into OpenMetadata
osi-openmetadata export -i finance_semantic_model.yaml --api-url http://localhost:8585 --jwt-token <token>
```
GitHub link: https://github.com/apache/ossie/discussions/380
----
This is an automatically sent email for dev@ossie.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@ossie.apache.org
Re: [D] Add bidirectional OpenMetadata semantic model converter (converters/openmetadata) [ossie]
Posted by "benvdh (via GitHub)" <gi...@apache.org>.
GitHub user benvdh added a comment to the discussion: Add bidirectional OpenMetadata semantic model converter (converters/openmetadata)
@jpvilla5454 There is a similar discussion going on in the openmetadata community (more about support of OpenMetadata for Ossie), where I've documented some of my findings (quick summary: Collate - the company behind OpenMetadata joined the Open Semantic Interchange consortium (the predecessor of Apache Ossie) in February 2025, in the 2.0 release blog post they mentioned OSI again, but I could not find any concrete documentation, PRs or issues on the matter):
https://github.com/open-metadata/OpenMetadata/issues/31238
Just linking it here as well so that the two threads cross-reference.
GitHub link: https://github.com/apache/ossie/discussions/380#discussioncomment-18876033
----
This is an automatically sent email for dev@ossie.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@ossie.apache.org
Re: [D] Add bidirectional OpenMetadata semantic model converter (converters/openmetadata) [ossie]
Posted by "jbonofre (via GitHub)" <gi...@apache.org>.
GitHub user jbonofre added a comment to the discussion: Add bidirectional OpenMetadata semantic model converter (converters/openmetadata)
It sounds super interesting. Let me know if you need my help to create a converter for OpenMetadata.
GitHub link: https://github.com/apache/ossie/discussions/380#discussioncomment-18896561
----
This is an automatically sent email for dev@ossie.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@ossie.apache.org
Re: [D] Add bidirectional OpenMetadata semantic model converter (converters/openmetadata) [ossie]
Posted by "benvdh (via GitHub)" <gi...@apache.org>.
GitHub user benvdh added a comment to the discussion: Add bidirectional OpenMetadata semantic model converter (converters/openmetadata)
Perhaps good to mention that the specification of a metric definition in OpenMetadata can be found here:
https://openmetadatastandards.org/governance/metric/#schema-specifications
GitHub link: https://github.com/apache/ossie/discussions/380#discussioncomment-18675718
----
This is an automatically sent email for dev@ossie.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@ossie.apache.org
Re: [D] Add bidirectional OpenMetadata semantic model converter (converters/openmetadata) [ossie]
Posted by "jpvilla5454 (via GitHub)" <gi...@apache.org>.
GitHub user jpvilla5454 added a comment to the discussion: Add bidirectional OpenMetadata semantic model converter (converters/openmetadata)
@daniyarndh I am actually actively looking for a solution like this right now..having a bidirectional converter between OpenMetadata and Ossie would solve a real gap for our team.
Also noticed the converters seem to be split out into their own repo now. I’ve subscribed here to track progress, but if anyone starts kicking off work or has updates, please keep me in the loop!
GitHub link: https://github.com/apache/ossie/discussions/380#discussioncomment-18872485
----
This is an automatically sent email for dev@ossie.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@ossie.apache.org
Re: [D] Add bidirectional OpenMetadata semantic model converter (converters/openmetadata) [ossie]
Posted by "daniyarndh (via GitHub)" <gi...@apache.org>.
GitHub user daniyarndh edited a discussion: Add bidirectional OpenMetadata semantic model converter (converters/openmetadata)
OpenMetadata has emerged as a widely adopted, enterprise-grade unified metadata catalog. It supports rich business glossaries, metrics definitions, and lineage tracking. However, there is currently no standardized way to serialize these cataloged assets into a vendor-neutral, developer-friendly, and version-controlled format that BI engines and AI agents can consume.
By building a bidirectional converter, we bridge OpenMetadata's central governance platform with Apache Ossie's declarative semantic standard, turning OpenMetadata into a first-class participant in the Ossie ecosystem.
Proposed Design & Mapping
The converter will be written in Python, matching the structure of existing converters like `converters/dbt` and `converters/databricks`.
Attributes specific to OpenMetadata that are not representable in the core Ossie specification (e.g., column-level tags, owners, tiers, and domain classifications) will be preserved in a `custom_extensions` block using the `OPENMETADATA` vendor namespace:
```yaml
custom_extensions:
- vendor_name: OPENMETADATA
data:
owner: "finance_team"
tier: "Tier1"
tags: ["PII.Sensitive", "Finance.Reporting"]
```
The converter package may also ship a CLI, e.g.:
```bash
# Export OpenMetadata to Ossie YAML
osi-openmetadata import --api-url http://localhost:8585 --jwt-token <token> --glossary "Finance" -o finance_semantic_model.yaml
# Ingest Ossie YAML back into OpenMetadata
osi-openmetadata export -i finance_semantic_model.yaml --api-url http://localhost:8585 --jwt-token <token>
```
GitHub link: https://github.com/apache/ossie/discussions/380
----
This is an automatically sent email for dev@ossie.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@ossie.apache.org