Record sub-property bridging as a mapping-layer mechanism - #1248
Open
JeroenDeDauw wants to merge 2 commits into
Open
Record sub-property bridging as a mapping-layer mechanism#1248JeroenDeDauw wants to merge 2 commits into
JeroenDeDauw wants to merge 2 commits into
Conversation
Adds the rdfs:subPropertyOf option to Limitations To The Upsides: the projection can emit local property terms declared subPropertyOf ontology terms, keeping local distinctions while ontology-term queries still find them. Notes the entailment caveat: neither QLever nor Oxigraph does RDFS reasoning, so on our own endpoints queries traverse the declaration with a property path. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Corrects the mechanism's interaction with the as-built projection: predicates are flat per-name (neo-prop:Name), so one declaration spans all same-named properties; per-Schema anchoring needs Schema-scoped predicates, making the mechanism an argument in NativeRdfProjection's open predicate-scope question. Leads with what the ontology anchor buys, keeps the runnable property path, and points ontology-shape consumers at the ontology projection. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
JeroenDeDauw
marked this pull request as ready for review
August 5, 2026 00:00
Member
Author
|
Sub-property Idea originally coming from @vrandezo, though not exactly as written here |
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.
Adds a sub-property option to Limitations To The Upsides, written for the consortium readers weighing the local-vs-global question: a mapping can declare native predicates
rdfs:subPropertyOfontology terms, making the ontology term the shared anchor a global property registry would otherwise provide. States the interaction with the as-built projection honestly — predicates are flat per-name (neo-prop:Name), so one declaration spans all same-named properties, and per-Schema anchoring needs Schema-scoped predicates (the open predicate-scope question in NativeRdfProjection.md). Keeps the entailment caveat as a runnable property path and points ontology-shape consumers at the ontology projection.Considered, omitted: where wiki-level declaration triples live in the per-page named-graph sync; the property path also matching co-hosted ontology projections (#1053 setups); owl:equivalentProperty for the genuinely-identical case; entailment availability on stores beyond the shipped pair (ADR 19 names more).