Skip to content

Documentation request: clarify Ossie’s relationship with FIBO and financial-services ontology layering #220

Description

@Joker-of-Gotham

I would like to request documentation or guidance clarifying how Apache Ossie is expected to relate to FIBO and other financial-services reference ontologies.

Ossie appears to be positioned as an open, vendor-neutral semantic-model interchange layer. In financial services, however, FIBO already exists as a formal reference ontology for financial business concepts, definitions, and relationships.

It would be helpful to clarify whether Ossie intends to:

  1. complement FIBO by referencing and mapping to it;
  2. provide an operational semantic-model layer on top of FIBO;
  3. define independent financial-domain semantic models that may or may not align with FIBO;
  4. support multiple alignment strategies depending on the use case.

Possible acceptance criteria

  • Add documentation explaining Ossie’s relationship to FIBO and external financial reference ontologies.
  • Clarify the intended financial-services semantic stack.
  • Provide a minimal example mapping an Ossie semantic model to FIBO concepts.
  • Clarify whether financial-services templates are expected to be FIBO-aligned, FIBO-derived, FIBO-compatible, or independent.
  • Define where external ontology references, mapping types, ontology versions, and provenance should live in the Ossie schema.
  • Add guidance on validation or conformance checks for ontology mappings.
  • Clarify where industry-specific semantic packages should be maintained.

Thank you again for your work on Ossie. I may have misunderstood parts of the project’s current scope, roadmap, or intended relationship with existing ontology efforts such as FIBO, so apologies in advance if any of the questions above are based on incomplete context or cause any inconvenience. I would appreciate any clarification or correction from the maintainers and community.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions