Activity

1. benoitcayladbx

   added

   enhancementNew feature or requestNew feature or request

   on Jun 10, 2026
2. ulsmo commented on Jun 24, 2026

   

   ulsmo

   on Jun 24, 2026

   ContributorAuthor

   More actions

   I explored approach 2, using one mapping to drive multiple entities and mappings.
   This seems like it should be possible using R2RML string templates if the class can be expressed from the data source - e.g. added as a CASE WHEN to create a class column representing the entity. Then the mapping for an entity could be:

   rr:subjectMap [ rr:class <BASE_URI#{class}> ;
           rr:template "BASE_URI/{class}/{id}" ] 
   

   and for a relationship:

   rr:predicateObjectMap [ rr:objectMap [ rr:template "BASE_URI/{source_class]/{source_id}" ] ;
           rr:predicate ont:RELATIONSHIP ] ;
   rr:subjectMap [ rr:template "BASE_URI/{target_class}/{target_id}" ] .
   

   I tried to define this in R2RML manually and import - it didn't map to any classes and the R2RML could not be generated, breaking the build of the knowledge graph.

   This would not fit natively within the current assumptions of the UI. So either it would have to be built in as a native feature, or it would require an "advanced" mapping mode that would support handcoded R2RML that could be used directly in the build phase.
3. benoitcayladbx

   self-assigned this

   on Jul 1, 2026
4. benoitcayladbx

   added the

   Feature

   issue type on Aug 12, 2026
5. benoitcayladbx

   added this to the v0.9.0 milestone on Oct 26, 2026
6. benoitcayladbx commented on Oct 26, 2026

   

   benoitcayladbx

   on Oct 26, 2026

   Collaborator

   More actions

   This landed in 0.9.0. We went with the second idea from the issue: do not clone the relationship mapping onto every subclass. The object property stays declared on the parent; subclasses inherit it at read time.

   What you get:

   • Studio / Mapping canvas — dashed subclass → range edges for inherited outgoing relations.
   • Entity panel — read-only “inherited from <parent>” list; Mapping Status links open the declaring class mapping.
   • Mapping / KG build — one SQL / R2RML triple map per property URI, on the class that declares the relation. Subclass instances that also type as the parent pick up those triples via rdfs:subClassOf. No second mapping on the child, so no mapping-combinatorial explosion (including self-loops).
   • OWL export — still rdfs:domain on the declaring class plus rdfs:subClassOf on the child.

   That also explains the R2RML experiment with {class} templates: OntoBricks still assumes one mapping per class/property URI. We did not add an “advanced” hand-coded R2RML mode.

   Not in scope (on purpose): incoming (range) inheritance, per-subclass relationship SQL, and inferring that a parent instance and a subclass instance are the same individual when their mapped IDs differ. Those stay two ABox nodes unless you model them as the same IRI (or add an explicit same-as / identity rule). If parent and subclass mappings share the same IRI, OWL already treats the subclass instance as a valid subject of the parent property.

   Docs: user guide “Inherited relations”; architecture “Inherited outgoing relations”. Tests: tests/units/ontology/test_inherited_relations.py, tests/units/front/test_inherited_relations_ui.py.

   Closing as completed in 0.9.0. If a case still fails (subclass KG with a distinct IRI from the parent, self-referencing properties, etc.), reopen with that example.
7. benoitcayladbx

   closed this as completedon Oct 26, 2026