chore(submodules): pin ontology-management-base to gx 2.2.1 + range-inference fix#144
Merged
Conversation
…nference fix Advances the OMB pin over its PR #83 squash: gx artifacts refreshed to service-characteristics v2.2.1 (adds gx:ComplianceCredential; removes gx:ServiceEntity, gx:spiffeId, gx:trustDomain, gx:operatedBy) and the upstream validators' rdfs:range entailment now covers blank-node objects. Full validate ran green against these artifacts (11 typecheck + 19 test tasks): schema graph loads, the term index builds with the new gx term set, retrieval/fragment/reference suites pass, prompt-size bounds hold. Nothing here referenced the removed gx terms — the retrieval surface is discovery-driven by design. Signed-off-by: jdsika <carlo.van-driesten@vdl.digital>
…the OMB refresh The OMB pin (eb49b92 -> 0dc1a42) advances 32 upstream commits, restructuring the artifacts well beyond the gx 2.2.1 bump: ISO-34503 ODD hierarchy, openlabel-v2 v1-v2 gap closure, and hdmap constraint reshaping. Three downstream assumptions broke -- two surfaced in CI; the third (llm) was masked because turbo cancels siblings once the ontology task fails first. - domain-registry mis-selected openlabel-v2's primary asset class. The new ISO 34503 ODD annotation shapes (OddDynamicElements, OddEnvironment, OddScenery) are declared AHEAD of Scenario, and "first-declared non-sub-component" is order-fragile. Select the composition ROOT instead -- the target class whose shape references the most other target classes -- an order-independent, ontology-name-free signal (computeCompositionScores). Scenario composes five sub-shapes; the standalone ODD shapes compose zero. [SHACL 2.3] - shacl-validator sh:in happy path. hdmap roadTypes' enum moved onto the version-conditional SEQUENCE path ( hasContent roadTypes ); sequence/inverse paths are intentionally out of scope for bare-value slot validation, so the enum test is re-pinned to hdmap:trafficDirection (a simple-path sh:in still in the validator's remit). - prompt-composer boundedness. Enlarged shapes plus new cross-domain references lift the retrieved tail ~3x (~61k chars, still an order of magnitude under a ~300k whole-file dump). Raise the calibration thresholds; boundedness -- not a specific size -- stays pinned. Adds submodule-independent regression tests for composition-root selection. Full `pnpm run validate` green on the new pin (19 tasks). Signed-off-by: Carlo van Driesten <carlo.van-driesten@bmw.de>
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
1 participant
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.
Summary
Pins
submodules/ontology-management-baseto the merge of ontology-management-base#83 (reviewed, improved, and squash-merged as part of this task):rdfs:rangeentailment fixed for blank-node objects in OMB's SHACL validation tooling (isIRI→!isLiteral, per RDF 1.1 Semanticsrdfs3/ OWL 2 RLprp-rng) — nested JSON-LD nodes without per-node@idnow receive their range-entailed types during upstream validation. This affects OMB's validators only; the nl-search runtime has its own stack.gx:ComplianceCredential(+shape), removesgx:ServiceEntity(+shape) andgx:spiffeId/gx:trustDomain/gx:operatedBy.Verification against the new artifacts
Full
pnpm run validategreen on this pin (11 typecheck + 19 test tasks): schema graph loads, the term index builds with the new gx term set, retrieval/fragment/reference suites pass, prompt-size bounds hold. Nothing in nl-search referenced the removed gx terms (the retrieval surface is discovery-driven by design).