ECiCo
language en

ECiCo

Release: 2026-02-03

This version:
https://kanzo.tech/ECiCo/BuildingOntology/0.1
Latest version:
https://kanzo.tech/ECiCo/BuildingOntology#
Issued on:
Date issued
Imported Ontologies:
https://digitalconstruction.github.io/Contexts/v/0.5/contexts.ttl
https://digitalconstruction.github.io/Variables/v/0.5/variables.ttl
https://digitalconstruction.github.io/Entities/v/0.5/entities.ttl
https://digitalconstruction.github.io/Processes/v/0.5/processes.ttl
https://digitalconstruction.github.io/Agents/v/0.5/
https://digitalconstruction.github.io/Information/v/0.5/
https://digitalconstruction.github.io/Materials/v/0.5/materials.ttl
https://digitalconstruction.github.io/Occupancy/v/0.5/
https://digitalconstruction.github.io/Lifecycle/v/0.5/
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
http://insertlicenseURIhere.example.org
Visualization:
Visualize with WebVowl
Cite as:
Retrieved from: https://kanzo.tech/ECiCo/BuildingOntology/0.1
Ontology Specification Draft

Abstract

The construction sector faces critical challenges in efficiency, sustainability, and resource management, being one of the sectors with the greatest environmental impact. To address this, the ECiCo project aims to drive the sector's transition towards a Circular Economy (CE) model through a technological solution that integrates efficient data sharing and promotes construction sustainability. The ECiCo ontology network will formalize, structure, integrate, and model knowledge in construction, establishing a common semantic language to tackle interoperability, improve decision-making regarding sustainability, resource efficiency, waste reduction, and project lifecycle optimization. This network will also serve as a lingua franca, enabling stakeholders in a data space to share reusable resources. The ontology's domain is the construction sector with a focus on Circular Economy, encompassing resource management, sustainability, material traceability, carbon footprint, data interoperability, Digital Twins, BIM models, and waste management. OWL has been chosen as the implementation language due to its W3C recommendation and widespread acceptance in the linked data web community.

Introduction back to ToC

The construction sector stands at a critical juncture, confronting significant challenges in efficiency, sustainability, and resource management, positioning it as one of the primary contributors to environmental impact. In this pressing context, the ECiCo initiative emerges with the fundamental purpose of catalyzing the sector's transformation towards a Circular Economy model. This will be achieved through the development of an advanced technological solution that will not only facilitate efficient data sharing but also actively promote more sustainable practices across the entire construction value chain, laying the groundwork for a more resilient and responsible industry.

Namespace declarations

Table 1: Namespaces used in the document
[Ontology NS Prefix]<https://kanzo.tech/ECiCo/BuildingOntology#>
dica<https://w3id.org/digitalconstruction/0.5/Agents#>
dicbm<https://w3id.org/digitalconstruction/0.5/Materials#>
dicc<https://w3id.org/digitalconstruction/0.5/Contexts#>
dice<https://w3id.org/digitalconstruction/0.5/Entities#>
dices<https://w3id.org/digitalconstruction/0.5/Energy#>
dici<https://w3id.org/digitalconstruction/0.5/Information#>
dicl<https://w3id.org/digitalconstruction/0.5/Lifecycle#>
dicob<https://w3id.org/digitalconstruction/0.5/Occupancy#>
dicp<https://w3id.org/digitalconstruction/0.5/Processes#>
dicv<https://w3id.org/digitalconstruction/0.5/Variables#>
ecico<https://kanzo.tech/ECiCo/BuildingOntology>
owl<http://www.w3.org/2002/07/owl#>
rdf<http://www.w3.org/1999/02/22-rdf-syntax-ns#>
rdfs<http://www.w3.org/2000/01/rdf-schema#>
xml<http://www.w3.org/XML/1998/namespace>
xsd<http://www.w3.org/2001/XMLSchema#>

ECiCo: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

ECiCo: Description back to ToC

The ECiCo ontology network is designed with the primary objective of comprehensively formalizing, structuring, integrating, and modeling knowledge inherent to the construction domain, with a particular focus on Circular Economy principles. Its development addresses the urgent need to establish a unified semantic language, essential for overcoming interoperability challenges and improving decision-making in crucial aspects such as sustainability, resource efficiency, waste minimization, and comprehensive project lifecycle optimization. This network will act as a conceptual lingua franca, enabling the various stakeholders involved in the construction data ecosystem to effectively share and reuse resources, covering key areas like resource management, material traceability, carbon footprint, data interoperability, Digital Twins, BIM models, and waste management. It will be implemented in OWL, a recognized W3C standard. introduction=The construction sector stands at a critical juncture, confronting significant challenges in efficiency, sustainability, and resource management, positioning it as one of the primary contributors to environmental impact. In this pressing context, the ECiCo initiative emerges with the fundamental purpose of catalyzing the sector's transformation towards a Circular Economy model. This will be achieved through the development of an advanced technological solution that will not only facilitate efficient data sharing but also actively promote more sustainable practices across the entire construction value chain, laying the groundwork for a more resilient and responsible industry.

Cross-reference for ECiCo classes, object properties and data properties back to ToC

This section provides details for each class and property defined by ECiCo.

Classes

A part of an organizationc back to ToC or Class ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#Department

A part of an organization such as a school, business, or government that deals with a particular area of study or work
has super-classes
Group c
has sub-classes
Unit c
is in domain of
occupies building unit op

Building stagec back to ToC or Class ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#BuildingStage

Stage at which a certain building is during the construction lifecycle
has super-classes
Building c
is in domain of
has lifecycle impact op
is in range of
has building stage op

Carbon footprintc back to ToC or Class ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#EmbodiedCarbonFootprint

Calculated value or index of greenhouse gases
has super-classes
Life Cycle Impact c

Contractc back to ToC or Class ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#Contract

A contract
has super-classes
File c
is in range of
linked to system op

Flow sensorc back to ToC or Class ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#FlowSensor

A sensor that measures the air entering a system
has super-classes
Sensor c

Pressure sensorc back to ToC or Class ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#PressureSensor

A device that senses and measures pressure
has super-classes
Sensor c

Providerc back to ToC or Class ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#Provider

Provider or service or product
has super-classes
Legal Person c

Source of Energyc back to ToC or Class ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#EnergySource

Source for obtaining energy
has super-classes
Energy Data c
is in domain of
produces energy op, supplies energy op

Systemc back to ToC or Class ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#System

Group of interacting or interrelated elements that act according to a set of rules to form a unified whole
has super-classes
Immaterial Entity c
is in domain of
has sensor op, linked to system op, present in model op

Treatmentc back to ToC or Class ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#Treatment

Treatment for waste
has super-classes
Waste c
is in range of
requires treatment op

Unitc back to ToC or Class ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#Unit

Organizational or functional entity that occupies, uses or is responsible for one or more physical spaces within a project or facility
has super-classes
A part of an organization c

Wastec back to ToC or Class ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#Waste

Unwanted or unusable materials
has super-classes
Object c
has sub-classes
Treatment c
is in domain of
requires treatment op
is in range of
produces waste op

Object Properties

establishes a fileop back to ToC or Object Property ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#establishesFile

An entity can establish a certain file (e.g. a contract)
has domain
Entity c
has range
File c

found inop back to ToC or Object Property ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#foundIn

A building object that is found in certaing lifecycle stage
has domain
Building Object c
has range
Building Lifecycle Stage c

has building stageop back to ToC or Object Property ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#hasBuildingStage

A building goes through an amount of stages during its lifecycle
has domain
Building c
has range
Building stage c

has fileop back to ToC or Object Property ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#hasFile

Entity has specific file (once it has been established)
has domain
Entity c
has range
File c

has lifecycle impactop back to ToC or Object Property ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#hasLifecycleImpact

Has lifecycle impact associated
has domain
Building stage c
has range
Life Cycle Impact c

has sensorop back to ToC or Object Property ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#hasSensor

Has some sensor associated
has domain
System c
has range
Sensor c

linked to systemop back to ToC or Object Property ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#linkedToSystem

File linked to specific system
has domain
System c
has range
Contract c

occupies building unitop back to ToC or Object Property ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#occupiesBuildingUnit

Department occupies a certain building unit
has domain
A part of an organization c
has range
Building Unit c

present in modelop back to ToC or Object Property ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#presentInModel

System is present in a model
has domain
System c
has range
Information Model c

produces energyop back to ToC or Object Property ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#producesEnergy

Produces energy data
has domain
Source of Energy c
has range
Energy Data c

produces wasteop back to ToC or Object Property ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#producesWaste

An activity produces waste
has domain
Building Lifecycle Stage c
has range
Waste c

requires treatmentop back to ToC or Object Property ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#requiresTreatment

A waste requires a specific treatment
has domain
Waste c
has range
Treatment c

supplies energyop back to ToC or Object Property ToC

IRI: https://kanzo.tech/ECiCo/BuildingOntology#suppliesEnergy

Produces and supplies energy to certain building
has domain
Source of Energy c
has range
Building c

Legend back to ToC

c: Classes
op: Object Properties

References back to ToC

Add your references here. It is recommended to have them as a list.

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.