Skip to content

ontology-cdm-p2

Building Ontology

A Building is a structure with some location in the urban system. The location of the Building in space may change due to construction, but the Parcel/Lot of land it is located on cannot. There may be many different types (subclasses) of buildings, such as House, Apartment Building, Office Building, and so on.

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.

Bylaw Pattern

“Municipal by-laws are public regulatory laws which apply in a certain area. The main difference between a by-law and a law passed by a national/federal or regional/state body is that a by-law is made by a non-sovereign body, which derives its authority from another governing body, and can only be made on a limited range of matters. A local council or municipal government derives its power to pass laws through a law of the national or regional government which specifies what things the town or city may regulate through by-laws. It is therefore a form of delegated legislation.” (Wikipedia, 2020) “A municipal by-law is no different than any other law of the land, and can be enforced with penalties, challenged in court and must comply with higher levels of law. Municipal bylaws are often enforceable through the public justice system, and offenders can be charged with a criminal offence for breach of a bylaw.” (Alberta, 2017) The intent of the Bylaw ontology is to capture the major components of a city bylaw, such as dates, geographic areas of application, penalties, etc. It is not intended to provide a legal semantics with which to codify a particular bylaw. The following three types of bylaws are represented in the Bylaw Ontology (Alberta, 2017): 1. Main bylaws; 2. Amending bylaws, which reflect material changes, in principle or substance, to an existing bylaw; and 3. Revision bylaws, which reflect limited changes to an existing bylaw.

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.

City Organization Ontology

Added for organizational purposes, to identify properties defined in the iCity-Organization ontology.

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.

City Pattern

The City pattern captures basic information about the geospatial aspects of the city. In particular it represents the different ways in which the city is administratively divided.

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.

City Resident Pattern

As different cities have different definitions of who is that city’s Resident, the City Resident Pattern must contain the properties required by each. Central to all of the definitions is the concept of residing. Variously referred to as a home or domicile in which the resident spends significant amounts of time. They may own it, rent it or just stay in it. Legally, “reside means to dwell permanently or continuously. It expresses an idea that a person keeps or returns to a particular dwelling place as his fixed, settled, or legal abode. The meaning of reside implies a continuous arrangement” ; reside has both a temporal and spatial dimension. The city of Toronto’s definition of a city resident includes the concept of owning property or owning or operating a business in the city. For Beijing, nationality is a unique aspect.

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.

City Service Pattern

Cities provide a variety of services to residents and businesses, including health and social services. The city service ontology, is based on the Canadian Government Reference Model (CGRM). See Wiseman, R. (2015). Canadian Governments Reference Models. In Service Systems Science (pp. 109-128). Springer, Tokyo.

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.

Code Pattern

The Code Pattern provides a structure to address the challenge of value enumeration with a general approach. In city data there are many classes of things that are intended to be instantiated using a set list of values (e.g., classification systems), however these values may change based on application or context. The Code Pattern introduces a generic set of classes and properties that can be used to extend such classes to define various classification systems in an integrated way. Instead of enumerating value sets for classes, values can be defined with an associated Code that specifies additional metadata about the value and its origins.

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.

Contact Pattern

Properties that define the hours of operation of the contact.

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.

Contract Pattern

A contract is a legal document that specifies some agreement(s) between two or more parties. The aim of the Contract Ontology is not to formalize the semantics of all possible involved legal concepts, but rather to enable to representation of the general structure and contents of a particular contract. The Contract Ontology adopts the definition of Contract specified in the Financial Business Ontology (FIBO) [8] specified at: https://spec.edmcouncil.org/fibo/ontology/FND/Agreements/Contracts/ with a key modification that a Contract is defined as a type of Document and is distinct from an Agreement (not a subclass, as specified in FIBO).

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.

Household Pattern

The Household ontology defines the classes: Household, Family, and DwellingUnit. These definitions serve as a basis which may be extended for more specific applications such as a surveys and simulations.

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.

Infrastructure Pattern

The Infrastructure pattern defines the concepts needed to capture various types of city infrastructure, such as buildings and roads. The Infrastructure pattern reuses the Spatial Location pattern (from ISO 5087-1) in order to capture the location of these infrastructure elements.

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.

Land Use Ontology

The Land Use Pattern captures concepts related to land use and cover over time. Land Use Classifications provide a means of describing the land cover/use in a standard way. Various classification systems are used to identify types of land use. Currently, we include LBCS, CLUMP, and AAFC. The ontology reuses and extends the Land Based Classification Standards (LBCS) Ontology presented by (Montenegro, Gomes, Urbano, and Duarte, 2011) for this purpose.

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.

Person Ontology

Ontology to capture concepts related to Persons.

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.

SSN Ontology

Ontology to capture concepts related to sensors and their observations. Directly reuses the SSN Ontology; adds classes and properties for organization of terms.

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.

Transportation Infrastructure Pattern

The Transportation Infrastructure pattern defines the concepts that are relevant in describing the physical transportation infrastructure and their characteristics. This includes the concepts of a Road, Bridge, and Tunnel. The Infrastructure Pattern is reused here, as these transportation structures are all defined as types of (subclasses) Infrastructure Elements.

This ontology consists of the following patterns:

The ontology also contains the following classes that are not assigned to any pattern:

The formal definition of these patterns is available in OWL Syntax.