Repository navigation
Mapping External Ontologies to ADIRO #70
Zaalouk122576
started this conversation in
Ideas
Replies: 1 comment
|
@alelom and @AhmedElnagar1 Please let me know your thoughts. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
This note surveys the external ontologies ADIRO is likely to import terms from, and which specific classes/properties from each are relevant to our ORSD requirements.
DAnO
Provenance Properties: These properties establish the "traceable link" necessary for auditing AI-generated building models.
dano:inferredBy(actor)dano:inferredWith(algorithm version)dano:inferredFrom(origin drawing)dano:inferredAt(date)ML Reliability and Confidence:
dano:hasConfidence: A per-object data property used to store extraction confidence scores. This is taken specifically to enable the "human-in-the-loop" workflow where high-uncertainty results are flagged for manual correction.Structural Information Interrelation: ADIRO leverages DAnO's categorization to manage how extracted labels relate to building geometry:
dano:DescriptionElement: Used for abstract annotations (text, symbols, dimensions) that describe physical elements via thedano:describesproperty.dano:Composite: Taken to handle grouped elements such asdano:Dimensionordano:TextField, ensuring that multi-line title-block entries are treated as single logical units.dano:depicts/dano:isDepictedBy: This is the closest match to the "working name depicts" mentioned in CQ 5.2. DAnO defines it as anowl:ObjectPropertywith domaindano:DisplayElement, described as linking a display element to "a real-world object, such as a building element, zone, or machine part". Its inverse,dano:isDepictedBy, links the real-world subject back to the depicting DisplayElement.GeoSPARQL
For CQ 1.3 (wall orientation/geometry):
geo:Geometry,geo:hasGeometry,geo:asWKT: Core classes/properties for attaching serialized geometry (WKT) to a DrawingElement.For CQ 2.3 (containment/co-occurrence/spatial inconsistency detection):
geo:sfContains,geo:sfWithin,geo:sfDisjoint,geo:sfOverlaps(Simple Features relation family): Binary topological predicates usable directly in SPARQL/SHACL/SWRL graph patterns for consistency checks.CQ 4.1/4.3 – reference-symbol connectivity, reachability graphs:
geo:rcc8*/geo:rcc9*relations (Region Connection Calculus): Qualitative connectivity relations (e.g.rcc8ec,rcc8dc) could model "reachable via reference symbol" style adjacency if geometric grounding is desired.Note — Query-function layer (for post-processing / rule engines):
For ADIRO's SWRL/DL/SHACL reasoning stack (per ORSD), the Geometry Topology Extension functions operate directly on serialized geometry literals rather than asserted triples, useful for computing relations at extraction/validation time rather than requiring pre-asserted topology:
geof:relate(geom1, geom2, pattern): general pattern matcher.geof:sfEquals,geof:sfWithin, etc.: A family of query functions, paired with SWRL-style query-rewrite rules that bridge assertedgeo:sf*triples down to these functions.Precedent for extendability (NFR 3):
Our ORSD explicitly cites GeoSPARQL as a target for future alignment under NFR 3. GeoSPARQL itself demonstrates this pattern in its alignments file, mapping external ontology classes to
geo:SpatialObject/geo:Feature/geo:Geometryviaowl:equivalentClass/rdfs:subClassOfalignments. This is a useful template if ADIRO's futuredepictsproperty is meant to alignmetadata:DrawingElementinstances withgeo:Feature/geo:Geometryexternally.ifcOWL
ifcOWL is the OWL representation of the IFC schema. Relevant parts of the IFC schema to ADIRO:
IfcRelAssociatesMaterial: This relation links an element to its material [IfcElement→IfcRelAssociatesMaterial→IfcMaterial].IfcRelContainedInSpatialStructure: It describes the spatial hierarchy [Site → Building → Storey → Space → Element] (example: window inside a slab).BEO
Built Element Ontology is an OWL ontology to describe built elements in the built environment. It is based on the Product ontology described in IFC (Industry Foundation Classes) schema:
Joist Beam, Window (Note:
:WindowSystemexists as a:LinearComponent, and glazing (:DGU,:TGU) covers the glazed-unit aspect in ADIRO, but no dedicated Window panel/opening class exists in ADIRO), Door, Skylight, Lintel, Rafter, Purlin.Properties:
CrossSectionArea,OverallHeight,OverallWidth,SteelGradeWhen ADIRO expands more terms, from BEO can be borrowed.
Note about these properties:
None of
CrossSectionArea,OverallHeight,OverallWidth,SteelGradeappear as explicit datatype properties in ADIRO. ADIRO models geometry/structure as property-category classes (:GeometricProperties,:SectionProperties,:StructuralProperties) rather than as literal-valued datatype properties, so BEO's approach of flat datatype properties would be a different modeling style than what's used. Worth aligning conceptually (e.g. minting these as datatype properties under the existingSectionProperties/GeometricPropertiesclasses) rather than importing BEO's properties directly.All reactions