Bringing OSI to the JVM ecosystem — exploring compatibility from the Erupt Cube side

[erupts]

Hi OSI team and community,

I maintain Erupt, a Java/Spring Boot admin framework (Apache 2.0). Within the Erupt ecosystem, Erupt Cube is the semantic-layer module — a commercial, source-code-delivery product sitting in the same category as AtScale or Omni, but JVM-native and annotation-driven. Production users include Bank of Shanghai and a handful of Fortune 500 Chinese subsidiaries.

I'm posting because we're evaluating OSI compatibility for Erupt Cube and would like to understand the working group's perspective before deciding on scope and timing.

Context

Most of the current 47 working group members are Python/SQL-side. There's no annotation-driven JVM-native vendor yet, and the Java/Spring Boot internal-BI segment (a meaningful share of enterprise dev in Asia) has been quiet on OSI so far. That gap is what we're looking at.

Technical alignment

Erupt Cube already declares semantic models via Java annotations that appear to map closely to OSI primitives:

Erupt Cube	OSI v1.0 (spec.yaml)
@EruptCube class	semantic_models[]
@Dimension field	semantic_models[].datasets[].fields[]
@Measure field	semantic_models[].metrics[]
@Explore + @ExploreParameter	views[] / filters / parameters

If we were to ship OSI YAML import/export, the technical work looks relatively contained — annotation reflection → OSI YAML via jackson-dataformat-yaml, validated against the OSI JSON schema. But before we scope it, we'd like to understand the community side better.

Questions for the working group

1. Closed-source vendor pattern — Cube, AtScale, Omni, Snowflake all support OSI from commercial products. We assume the expected pattern is: implement OSI import/export inside the product, contribute tooling/examples (but not core product source) to this repo. Is that the right read?
2. Model Converters & Developer Tools WG — is there a meeting cadence or async channel observers can join to follow scope discussions?
3. Tracking implementations — once a product ships OSI support, what's the typical path to register it as an OSI-implementing product, beyond the partners page on the website?

Happy to share more details on the annotation model or specific mapping questions in this thread. Looking for signal more than commitment at this stage.

Thanks,
YuePeng
Erupt maintainer · https://www.erupt.xyz/#!/cube