Add SAP Business Partner example for the ontology layer - #310
Open
marioapiphani wants to merge 1 commit into
Open
Add SAP Business Partner example for the ontology layer#310marioapiphani wants to merge 1 commit into
marioapiphani wants to merge 1 commit into
Conversation
An ontology-layer model of a Business Partner domain, exercising entity subtyping with a derived population, four-part compound identity, value types with requires constraints, associations with and without functional multiplicity, verbalizations, and ontology_mappings to a logical model. Validates against ontology/ontology.json as shipped.
jbonofre
self-requested a review
August 9, 2026 13:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
examples/has one ontology-layer example today (flights.yaml). This adds a second, drawn from an enterprise ERP domain, that exercises ontology constructs the existing example does not reach:Customerdeclaresextends: [ BusinessPartner ];flights.yamlhas no EntityType subtypingCustomeruses concept-levelderived_byto define its population as exactly those business partners carrying a customer number, rather than asserting it.flights.yamlusesderived_byonly on relationships, for derived attributes.CustomerSalesAreais identified by customer + sales organization + distribution channel + division. The existing example tops out at two parts.It also covers ground shared with
flights.yaml— value types withrequires, associations with and without functional multiplicity, verbalizations in both reading directions, andontology_mappingsdown to a logical model — so it stands alone as a reading example.Source-system provenance (SAP Data Dictionary domains and check tables) is recorded in the descriptions, showing one way to keep technical origin alongside a business-level model.
The README's
examples/entry is updated to name both ontology-layer models.The file validates against
ontology/ontology.jsonas shipped, withcore-spec/osi-schema.jsonregistered to resolve the remote$reffrom the checkout:Prints
VALID. No code changes.🤖 Generated with Claude Code