Our ontology <\/span>integrates three domains<\/b>:<\/span><\/p>\n Through this integration, the ontology will <\/span>support decision-making<\/b> for sustainable urban planning, structural integrity, and efficient maintenance.<\/span><\/strong><\/p>\n According to Noy and Mcguiness (2001), the first step in developing an ontology is to determine the domain and scope of the ontology. For our ontology, the following concepts are considered:<\/span><\/p>\n \u00a0Figure 1. Concepts considered in the Integrated Ontology<\/p>\n <\/p>\n To integrate the ontology, some classes were deleted and some were modified to come up with a holistic ontology that meets our objective. The integrated Classes and Subclasses defined in Prot\u00e9g\u00e9 are as follows:<\/span><\/p>\n \u00a0Figure 2.\u00a0Classes and Subclasses defined in Prot\u00e9g\u00e9<\/p>\n To provide more information for the classes to answer the competency questions, we need to define the Object and Data Properties. Table 1 shows the Object Properties of classes defined in Prot\u00e9g\u00e9. This will enable us to determine the relationship between two classes that have connected concepts.<\/span><\/strong><\/p>\n \u00a0\u00a0Table 1. Object Properties of Classes defined in Prot\u00e9g\u00e9<\/p>\n <\/p>\n Table 2 shows the Data Properties of classes. This indicates the literal value of the class by using slot values such as dateTime, string, and float. These are important details used for practical applications like documenting maintenance dates, recording how long it took to do a specific maintenance task, and the status of the maintenance.<\/span><\/p>\n \u00a0\u00a0Table 2. Data Properties of Classes defined in Prot\u00e9g\u00e9 Figure 3 shows an example of an Instance for a structural design option for Multi-story Family Housing. The reasoner automatically populates the Property Assertion section with assigned and inferred properties for each building design. By using Pellet, the ontology validates logical consistency and ensures that relationships between concepts are accurately inferred and represented. The Data Property assertion shown in Figure 4 was defined manually based on the initial design of the building.<\/span><\/p>\n <\/p>\n Figure 3. Structural Design Option 1 for Multi-Story Family Housing<\/p>\n \u00a0Figure 4. Data Property assertion for the Design Option 1 of Multi-Story Family Housing<\/p>\n \u00a0Another instance is for the maintenance of the building. In this example, Multi-Story Family Housing needs an inspection for the smoke detectors which are required to be inspected annually. It also shows the date and time of the scheduled inspection as well as the status of the task. It also needs a minor repair of the walls which will be performed by the carpenter.<\/span><\/strong><\/p>\n \u00a0Figure 5. Maintenance plan for\u00a0Multi-Story Family Housing<\/p>\n <\/p>\n \u00a0Figure 6. Ontograf showing the Functionality of the Ontology<\/p>\n Figure 7. Ontograf of the Integrated System<\/p>\n <\/p>\n Figure 8. Ontograf showing the Structural Analysis Components and the Maintenance<\/p>\n Figure 9. Ontograf showing an instance of a building inside the urban complex<\/p>\n If an earthquake happens, the structural integrity of the building should be the top priority. The ontology offers an ordered method for post-earthquake inspections, ensuring that every structural element is assessed. For example, a starting point can be: <\/span>\u201cWhich structural components need to be inspected, and which service providers are responsible for them?\u201d<\/span><\/i> This helps in creating an inspection plan and organizing maintenance activities for each floor. The ontology connects structural components with maintenance activities (inspection and repair) and assigns them to service providers, ensuring that the appropriate professionals handle the work. This structured approach enhances safety by minimizing oversight and enabling systematic, detailed assessment of the building. As a result, the ontology facilitates not only the recovery process after an emergency but also ensures long-term maintenance and adherence to safety protocols.<\/span><\/p>\n Engineers can use the ontology to validate building designs by ensuring that all structural components\u2014such as beams, columns, slabs, and walls\u2014meet specific requirements. By utilizing object properties like <\/span>HasLoad<\/span><\/i> and <\/span>HasMaterial<\/span><\/i>, the ontology verifies that correct load factors and material grades are applied to each component. This helps ensure compliance with design codes and standards, streamlining the design review process. For example, if a column is designed to withstand seismic loads but lacks adequate reinforcement, the ontology can flag this inconsistency. This validation process helps prevent structural failures and ensures that all design elements contribute to a stable and resilient building.<\/span><\/p>\n The ontology assists engineers in adapting building designs to improve seismic resistance. By analyzing structural components like <\/span>ShearWalls<\/span><\/i> and <\/span>Columns<\/span><\/i> in relation to <\/span>SeismicLoad<\/span><\/i>, engineers can identify weak areas that require reinforcement. The ontology helps determine whether modifications, such as increasing reinforcement ratios or using higher-grade concrete, are necessary to meet seismic safety standards. For example, an older building lacking shear walls in a high-risk seismic zone can be flagged for retrofitting recommendations. This structured approach ensures that buildings are designed or modified to withstand earthquakes, thereby enhancing structural resilience and safety in disaster-prone areas.<\/span><\/p>\n You can reach\u00a0our full ontology by clicking:\u00a0Combined-Ontologies-GroupD<\/a><\/p>\n <\/p>\n <\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Engineering Challenge As cities expand and become more complex, a unified knowledge framework is essential for integrating different building typologies and their interactions. This ontology serves as a structured representation of knowledge related toContinue reading<\/a><\/p>\n","protected":false},"author":222,"featured_media":0,"parent":19280,"menu_order":5,"comment_status":"closed","ping_status":"open","template":"page-templates\/page_fullwidth.php","meta":{"footnotes":""},"class_list":["post-19302","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/pages\/19302","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/users\/222"}],"replies":[{"embeddable":true,"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=19302"}],"version-history":[{"count":30,"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/pages\/19302\/revisions"}],"predecessor-version":[{"id":23899,"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/pages\/19302\/revisions\/23899"}],"up":[{"embeddable":true,"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/pages\/19280"}],"wp:attachment":[{"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=19302"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
Developing an Ontology<\/h2>\n
What is the purpose?<\/h3>\n
\n
What is the scope?<\/h3>\n
\n
Who are the Intended Users?<\/h3>\n
\n
What is the Intended Use?<\/h3>\n
\n
\nBuilding an OWL Ontology for an Urban Complex<\/h2>\n
![\"classes\"](\"http:\/\/141.23.68.248\/wp\/wp-content\/uploads\/2025\/01\/Classes.png\")
<\/a><\/p>\nDefining the Classes and the Class Hierarchy<\/h3>\n
![\"fig2\"](\"http:\/\/141.23.68.248\/wp\/wp-content\/uploads\/2025\/01\/Fig2.png\")
<\/p>\nDefining the Object and Data Properties of Classes<\/h3>\n
![\"fig3\"](\"http:\/\/141.23.68.248\/wp\/wp-content\/uploads\/2025\/01\/Fig3.png\")
<\/a><\/p>\n
\n![\"fig4\"](\"http:\/\/141.23.68.248\/wp\/wp-content\/uploads\/2025\/01\/Fig4.png\")
<\/p>\nCreate Instance<\/h3>\n
![\"fig5\"](\"http:\/\/141.23.68.248\/wp\/wp-content\/uploads\/2025\/01\/Fig5.png\")
<\/a><\/p>\n![\"fig6\"](\"http:\/\/141.23.68.248\/wp\/wp-content\/uploads\/2025\/01\/Fig6.png\")
<\/p>\n![\"fig7\"](\"http:\/\/141.23.68.248\/wp\/wp-content\/uploads\/2025\/01\/Fig7.png\")
<\/a><\/p>\nVisualizing the Ontology using OntoGraf
![\"ontograf1\"](\"http:\/\/141.23.68.248\/wp\/wp-content\/uploads\/2025\/01\/Ontograf1.png\")
<\/a><\/h3>\n<\/h3>\n
\n![\"ontograf3\"](\"http:\/\/141.23.68.248\/wp\/wp-content\/uploads\/2025\/01\/Ontograf3.png\")
<\/a><\/p>\n
\n![\"ontograf2\"](\"http:\/\/141.23.68.248\/wp\/wp-content\/uploads\/2025\/01\/Ontograf2.png\")
<\/a><\/p>\n
\n![\"multi-story\"](\"http:\/\/141.23.68.248\/wp\/wp-content\/uploads\/2025\/01\/Multi-Story.png\")
<\/a><\/p>\n
\nEngineering Examples of the Ontology<\/h2>\n
1. Structural Safety Inspections After an Earthquake<\/b><\/h3>\n
2. Structural Design Validation<\/b><\/h3>\n
3. Seismic Retrofitting and Design Adaptation<\/b><\/h3>\n
\nDownloadable Content<\/h2>\n
\n\u00a0|\u00a0\u00a0Main Page<\/a>\u00a0|\u00a0\u00a0Introduction<\/a>\u00a0|\u00a0\u00a0Individual Systems<\/a>\u00a0|\u00a0Integration Context<\/a>\u00a0|\u00a0\u00a0Combined Ontology<\/a>\u00a0|\u00a0\u00a0Combined Parametric Model<\/a>\u00a0|<\/h5>\n