ontology-design

Design BIM ontology schemas and governance rules for consistent data modeling.

1|Updated Jan 9, 2026

Search Tags:#ontology #validation #schema #governance #data-modeling #graph #BIM

Ready to run

npx skills add https://github.com/tygwan/AgenticREVIT --skill ontology-design

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ontology-design
Source: https://github.com/tygwan/AgenticREVIT/tree/main/.claude/skills/ontology-design
Command: npx skills add https://github.com/tygwan/AgenticREVIT --skill ontology-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BIM projects often struggle with inconsistent data models and unclear relationships across physical, semantic, process, and document layers. This skill provides a principled approach to designing and governing BIM ontologies and schema rules.

Core Features & Use Cases

Ontology layering: define Physical, Semantic, Process, and Document layers with clear node types and relationships.
- Schema governance: establish naming conventions, constraints, and validation rules to ensure data integrity.
Use Case: model a new architectural element by specifying Element, Category, Type, and related Tasks and Costs, then validate graph consistency.

Quick Start

Start by drafting the Element node schema and a few core relationships in the ontology, then run a validation pass to verify constraints.

Frequently Asked Questions about ontology-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design a BIM ontology schema for consistent data modeling?▼

Design a BIM ontology schema by defining Physical, Semantic, Process, and Document layers with clear node types and relationships. Establish naming conventions, constraints, and validation rules to ensure data integrity across your project's Element, Category, Type, and relationship definitions.

What are the key layers in BIM ontology design and how do they work together?▼

BIM ontology layering separates concerns into Physical (structural elements), Semantic (meaning and properties), Process (workflows and tasks), and Document (specifications and records) layers. Each layer defines its node types and relationships, enabling standardized data modeling and graph queries across all project dimensions.

How do I validate BIM schema governance rules and constraints?▼

Validate BIM schema governance by running a validation pass against your ontology to verify constraints on Element, Category, Type, Relationships, and validation rules. This ensures graph consistency and catches data modeling errors before they propagate across your project.

Can I model architectural elements with relationships to tasks and costs in BIM?▼

Yes. Specify Element nodes with Category and Type classifications, then define relationships to related Tasks and Costs within your ontology schema. Validation confirms that all relationships satisfy your governance constraints and maintain data consistency.

When should I use ontology-based schema governance instead of flat data models?▼

Use ontology schema governance when BIM projects need consistent relationships across multiple layers—physical structure, semantics, processes, and documents. Layered ontologies prevent data inconsistency and enable graph queries that flat models cannot support.