{"id":27326,"date":"2026-02-07T20:26:23","date_gmt":"2026-02-07T20:26:23","guid":{"rendered":"http:\/\/141.23.68.248\/wp\/?page_id=27326"},"modified":"2026-02-16T11:52:52","modified_gmt":"2026-02-16T11:52:52","slug":"integrated-urban-corridor","status":"publish","type":"page","link":"http:\/\/141.23.68.248\/wp\/?page_id=27326","title":{"rendered":"Group Ontology (Urban Corridor System)"},"content":{"rendered":"\n

We developed a group ontology (OWL\/Prot\u00e9g\u00e9) to provide a shared semantic backbone for the UrbanCorridor system and to keep terminology consistent across the integrated project. The ontology defines the corridor at the top level (UrbanCorridor) and major CorridorElement categories such as CableStayedPedestrianBridge and Roadpavementsystem, then decomposes them into BridgeComponent and PavementComponent. For pavements, it explicitly models the layered assembly (SurfaceLayer, BinderCourseLayer, BaseLayer, SubBaseLayer, Subgrade) with common alternatives (e.g., AsphaltConcrete\/StoneMasticAsphalt).<\/p>\n\n\n\n

Integration relations are formalized via an object property hierarchy centered on hasComponent (with inverse isComponentOf), and key descriptors are captured through a data property hierarchy (e.g., hasDeckWidth\/Thickness\/Elevation, hasCableInclination, hasPylonHeight, hasMainGirderDepth, and design\/traffic indicators).<\/p>\n\n\n\n

The ontology also includes individuals that represent the concrete elements and options from our individual projects, so it captures specific bridge\/pavement configurations and variants rather than remaining purely abstract. This makes it easier to trace how each individual contribution is reflected in the final integrated corridor model and supports clearer querying and documentation.<\/p>\n\n\n\n

Figure 1<\/strong> shows the Ontograph, Figure 2<\/strong> the class hierarchy, Figure 3<\/strong> the object properties, and Figure 4<\/strong> the data properties of the group ontology.<\/p>\n\n\n\n

\"\"<\/a>
Figure 1.<\/strong> Ontograph view of the group ontology showing the UrbanCorridor structure and key part\u2013whole relationships (hasComponent \/ isComponentOf).<\/figcaption><\/figure>\n\n\n\n
\"\"<\/a>
Figure 2<\/strong>. Class hierarchy overview of the group ontology, highlighting corridor elements (bridge and pavement systems) and their component decomposition.<\/figcaption><\/figure>\n\n\n\n
\"\"<\/a>
Figure 3.<\/strong> Object property hierarchy of the group ontology, showing core part\u2013whole relations (e.g., hasComponent) and their specialized subproperties, including inverse relations (e.g., isComponentOf) used to connect corridor elements and components.<\/figcaption><\/figure>\n\n\n\n
\"\"<\/a>
Figure 4.<\/strong> Data property hierarchy of the group ontology capturing key descriptive and parametric attributes (e.g., deck dimensions, pylon\/cable parameters, pavement layer properties, and design\/traffic indicators) used to describe corridor elements consistently.<\/figcaption><\/figure>\n","protected":false},"excerpt":{"rendered":"

We developed a group ontology (OWL\/Prot\u00e9g\u00e9) to provide a shared semantic backbone for the UrbanCorridor system and to keep terminology consistent across the integrated project. The ontology defines the corridor at the top level (UrbanCorridor)Continue reading<\/a><\/p>\n","protected":false},"author":286,"featured_media":0,"parent":24743,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-27326","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/pages\/27326","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\/286"}],"replies":[{"embeddable":true,"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=27326"}],"version-history":[{"count":15,"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/pages\/27326\/revisions"}],"predecessor-version":[{"id":29132,"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/pages\/27326\/revisions\/29132"}],"up":[{"embeddable":true,"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/pages\/24743"}],"wp:attachment":[{"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=27326"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}