The core abstraction that represents assets, facilities, and spaces in one 4-table EAV model.
The resource ontology represents every operational object with four tables: instance (resource), class (resource_class), dynamic schema (resource_schema), and properties (resource_prop). The core principle: do not create child tables.
Why a single model
- Adding a new asset type needs no migration.
- Cross-domain relations are fixed to 25 core relations.
- Validation rules are managed as data via dynamic schema.
Before creating a table or column for a feature, abstract two levels further to check if existing metadata can absorb it.