Add XSOLCORP KOREA to the Ossie ecosystem

[isocline]

Summary

This PR adds XSOLCORP KOREA to the Apache Ossie ecosystem page.

• data/ecosystem.yml — new vendor entry, inserted alphabetically between ThoughtSpot and Zeta Global
• docs/assets/images/logos/xsolcorp-korea-logo.png — logo asset (800×122, transparent background, 38 KB)

About XSOLCORP KOREA

XSOLCORP KOREA Inc. is a Seoul-based enterprise software company building model-driven
platforms for regulated industries — banking, insurance, and mobility. The company was
incorporated in 2022 and began commercial operations in 2024 through a partnership with
XSOLCORP, a Canadian fintech group, and carries forward a lineage of more than four
decades of financial IT delivery in Korea. Its product portfolio spans core insurance and
fleet-management platforms (XyroInsureCORE, Xyro FleetCORE), a customer-engagement and
AI contact-center stack (XyroPLUG SONA), and the platform relevant to this proposal,
ElastiCORE.

ElastiCORE is a domain semantic layer for trustworthy enterprise AI. Teams declare their
domain once — entities, fields, enums, and relationships — in a YAML-based DSL that acts
as the single source of truth, and ElastiCORE deterministically generates the full
production stack from it: JPA entities, DTOs, repositories, services, controllers, and
REST APIs on Spring Boot 3.x. The same model is exposed to AI systems through ElastIDE,
which combines a knowledge graph, hybrid retrieval, natural-language-to-SQL, and MCP agent
integration, so that model, code, diagram, and graph stay losslessly in sync. Because our
customers operate under data-sovereignty mandates, the entire platform runs on-premise and
air-gapped with no external API calls.

Relationship to Apache Ossie

The problem Ossie addresses is the problem our DSL was designed around: a semantic
definition that is authored once and consumed consistently by every downstream tool. Our
DSL already models the same conceptual surface Ossie standardizes — entities, attributes
and types, enumerations, relationships, and business-level naming — but it does so in a
vendor-specific dialect, which is exactly the fragmentation Ossie exists to remove.

We are therefore implementing bidirectional Ossie conversion in ElastiCORE:

• Export — emit Ossie-conformant YAML from an ElastiCORE domain model, so semantic
  definitions authored in ElastiCORE can be consumed by BI, analytics, and AI tools across
  the Ossie ecosystem without hand-maintained mappings.
• Import — ingest Ossie YAML into the ElastiCORE DSL, so organizations that already
  maintain a semantic layer elsewhere can generate applications and ground AI agents
  against it rather than re-authoring the model.

Our particular interest in the specification is round-trip fidelity and deterministic
conversion: for the regulated, air-gapped deployments we serve, a semantic exchange format
is only useful if the same input always produces the same output and no meaning is lost in
either direction. We would like to contribute that perspective — along with feedback from
applying Ossie to Korean insurance and mobility domain models — to the working group as
the specification evolves.

Checklist

• Logo placed in docs/assets/images/logos/
• Entry added to ecosystem.vendors in data/ecosystem.yml, alphabetically ordered
• Logo is transparent-background PNG, sized for the member card (renders at max 120×60)
• We have the right to use this logo and grant the ASF permission to display it

Links: XSOLCORP KOREA · ElastiCORE

[isocline]

Friendly ping — no urgency, just flagging this so it doesn't fall off the radar.

The change is small: a two-line entry in data/ecosystem.yml and one logo asset, following the same pattern as #11 and #12. The branch is still conflict-free.

I noticed a few other PRs are waiting as well (#14, #16), so it may simply be that the queue needs a sweep from someone with the commit bit rather than anything specific to this one. Happy to rebase or adjust the entry if anything here should be done differently.

Thanks for your work on Ossie.