You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ossie.apache.org by "marioapiphani (via GitHub)" <gi...@apache.org> on 2026/08/09 09:58:34 UTC
Re: [PR] Initial Foundational Semantics Spec [ossie]
marioapiphani commented on PR #246:
URL: https://github.com/apache/ossie/pull/246#issuecomment-5230916616
Will — read the full document. Strong support, both for the content and for the foundational-first approach: As discussed in #46, full support from an SAP perspective.
The five user-visible semantics — especially Semantic 5 (typed error, never a plausible-but-wrong number) and Semantic 1's NULL-bucketing of unmatched fact rows — address the *query-time* family of what we saw in the field. The NULL determinism work (§5.1 ordering defaults, §6.11 empty/NULL aggregate behaviour, NULL-safe stitch merges) pins down the places where observed engines quietly disagree. Adding composite keys as first-class citizens in relationships (`from_columns`/`to_columns`, `unique_keys`) covers the compound-identity shape that SAP-class models live on — our four-part keys map onto §6.4's inference very cleanly.
The worst losses we measured were not query-time — they were *transport-time*: an observed ontology platform (Fabric) accepted parts of our semantic model with a success response and silently discarded them. We only caught it by re-reading what was stored. The Foundation guarantees no silently wrong *answer*; nothing yet guarantees no silently dropped *model construct*. A conformance rule in the same spirit — an implementation MUST either represent a construct, reject it with a typed error, or explicitly report it as unsupported (never accept-and-drop) — would extend Semantic 5's philosophy to interchange itself, and would have caught every silent loss in our audit. The working draft's reference to a conformance suite (§11.1) looks like this rule's natural home. If useful, I'm happy to share the anonymized loss table as test material.
In SAP, there are 2 validations
1. *Sentinel values vs. NULL.* In SAP-sourced data, "missing" is usually not NULL — it's an initial value (`''`, `'0000000000'`, `'00000000'`). Semantic 1's NULL bucket won't catch those; a broken reference surfaces as a legitimate-looking key instead. Not a Foundation blocker, but worth a future hook (declared sentinel values on a dataset, folding them into the NULL bucket) — otherwise real-world ERP data quietly defeats the guarantee.
2. *Declared cardinality, when it lands.* §6.4's inference is the right conservative default, but closed-world sources like SAP always *know* their cardinality — associations declare it. When the deferred declared-cardinality/RI proposal comes, two requests from the emitter side: keep declaration cheap (we declare, we never infer), and make declared-vs-inferred disagreement a typed error and not a silenced accept on any side.
**Two editorial catches:** (1) the body references §9, §10, §11, §12 (SQL-interface proposal, deferred-features registry, extension flags + conformance suite, vendor comparison incl. "§12.A divergence note") — none of which exist in the committed file or, as far as I can see, in the working draft either. As committed, readers hit dangling anchors; either trimming the references or landing stub sections would tighten it. (2) The working draft's §4.6.1 explicitly pins quoted-identifier case-sensitivity (`"id"` ≠ `id`, `"ID"` = `id`) and notes the conformance suite asserts it — the committed §4.6.1 dropped that pin. If the position now lives in the expression-language proposal, a pointer would help; if it was dropped accidentally, it's worth restoring — it's exactly the kind of cross-engine divergence this document exists to kill.
One clarifying question: the ontology layer's `requires`/`derived_by` fields also carry ANSI-SQL expressions. Is the intent that `Ossie_SQL_2026` plus these evaluation semantics govern those expressions too, or does the ontology layer get its own semantics pass? Asking because we're building a CSN (SAP model language) → Ossie converter that emits closed-world constraints into `requires`, and we'd like to target whichever contract will govern them.
Happy to turn any of the above into concrete test fixtures — that's the form feedback is most useful in.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ossie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org