Difference between revisions of "City Data Model Project Collaboratory Wiki:About"

From City Data Model Project Collaboratory
Jump to navigation Jump to search
Line 1: Line 1:
 +
A common data model enables city software applications to share information, plan, coordinate, and execute city tasks, and support decision making within and across city services, by providing a precise, unambiguous representation of information and knowledge commonly shared across city services. This requires a clear understanding of the terms used in defining the data, as well as how they relate to one another. This requirement goes beyond syntactic integration (e.g. common data types and protocols), it requires semantic integration: a consistent, shared understanding of the meaning of information.
 +
City data cover a wide and varied range of concepts. Likewise, uses and sources of this data are numerous and diverse. Different application areas tend to focus on different facets of city data, and so different organizations may attribute different definitions to concepts that describe the same thing. For example, in some applications a Road Segment may be described according to its physical characteristics, whereas other applications may focus on its flow and connectivity to other road segments.
 +
 
== What is the City Data Model? ==
 
== What is the City Data Model? ==
The City Data Model is...
+
A common data model enables city software applications to share information, plan, coordinate, and execute city tasks, and support decision making within and across city services, by providing a precise, unambiguous representation of information and knowledge commonly shared across city services. This requires a clear understanding of the terms used in defining the data, as well as how they relate to one another. This requirement goes beyond syntactic integration (e.g. common data types and protocols), it requires semantic integration: a consistent, shared understanding of the meaning of information.
The City Data Model covers data specific to the city domain, but generic in the sense that it could be expected to be both generated and consumed by many city services.
 
  
For example...the city services' data models a multi-part international standard being proposed within ISO to support data integration in cities.  
+
The City Data Model represents a long-term goal wherein there exists a shared model of all city-related data. This City Data Model will integrate perspectives from a broad range of standards efforts, with sometimes overlapping or sometimes incompatible semantics. This model will allow anyone to see how their data model “fits in” relative to others’. Organizations will be free to maintain their own models, but can also leverage the City Data Model as a source from which the appropriate data models may be extracted as required.
  
A draft of the proposed city services standard, developed prior to implementation of the collaboratory, is available [https://github.com/EnterpriseIntegrationLab/City-Data-Model here]. This draft was derived from earlier work on a the iCity Transportation Planning Suite of Ontologies (TPSO), developed for the [https://uttri.utoronto.ca/news/icity-urban-informatics-sustainable-metropolitan-growth/ iCity-ORF Project]. See [[publications | Publications]] for more background on the iCity-ORF Project.
+
This will be achieved by an effort to integrate existing perspectives on city data. Groups involved with city data models will be encouraged to contribute their content in a form that will support alignment with other, heterogeneous views. The result will be an extensive, all-encompassing data model that captures the relationships between different views of the same concept.
  
[[File:ICity TPSO and projects.png|thumbnail|center|The iCity TPSO and related transportation planning work from the iCity-ORF project.]]
+
The contents of the City Data Model will be stratified into 3 levels of abstraction (pictured below). The Foundation Level covers very general concepts such as Time, Location, and Activity. The City Level covers concepts that are general to cities and span all services such as Households, Services, Residents. The Service Level spans concepts commonly associated with a particular service but still shared with other services, such as Vehicles and Transportation network. Initial efforts in this collaboratory will focus on the identification and development of the City-level concepts.
  
== Why a global collaboratory? ==
+
[[File:City data levels.png|thumb|center|The three levels of the city data model: foundational concepts, city-level concepts, and service-level concepts.]]
The purpose of this collaboratory is to provide an environment wherein individuals from related standards organizations and other stakeholders can openly contribute to the development of a standard model for city data.
 
  
== Who are we? ==
+
== What is the a global collaboratory? ==
This website is created and maintained by researchers at the University of Toronto's [http://www.eil.utoronto.ca Enterprise Integration Laboratory].
+
The Collaboratory is a tool to support the creation of the city data model. It houses the conversation on what concepts should be included, and how different concepts from different groups are related to one another. The purpose of this collaboratory is to provide an environment wherein individuals from related standards organizations and other stakeholders can openly contribute to the development of a standard model for city data. It is maintained by the University of Toronto’s [https://www.schoolofcities.utoronto.ca School of Cities] and [http://www.eil.utoronto.ca Enterprise Integration Laboratory].

Revision as of 17:29, 9 April 2020

A common data model enables city software applications to share information, plan, coordinate, and execute city tasks, and support decision making within and across city services, by providing a precise, unambiguous representation of information and knowledge commonly shared across city services. This requires a clear understanding of the terms used in defining the data, as well as how they relate to one another. This requirement goes beyond syntactic integration (e.g. common data types and protocols), it requires semantic integration: a consistent, shared understanding of the meaning of information. City data cover a wide and varied range of concepts. Likewise, uses and sources of this data are numerous and diverse. Different application areas tend to focus on different facets of city data, and so different organizations may attribute different definitions to concepts that describe the same thing. For example, in some applications a Road Segment may be described according to its physical characteristics, whereas other applications may focus on its flow and connectivity to other road segments.

What is the City Data Model?

A common data model enables city software applications to share information, plan, coordinate, and execute city tasks, and support decision making within and across city services, by providing a precise, unambiguous representation of information and knowledge commonly shared across city services. This requires a clear understanding of the terms used in defining the data, as well as how they relate to one another. This requirement goes beyond syntactic integration (e.g. common data types and protocols), it requires semantic integration: a consistent, shared understanding of the meaning of information.

The City Data Model represents a long-term goal wherein there exists a shared model of all city-related data. This City Data Model will integrate perspectives from a broad range of standards efforts, with sometimes overlapping or sometimes incompatible semantics. This model will allow anyone to see how their data model “fits in” relative to others’. Organizations will be free to maintain their own models, but can also leverage the City Data Model as a source from which the appropriate data models may be extracted as required.

This will be achieved by an effort to integrate existing perspectives on city data. Groups involved with city data models will be encouraged to contribute their content in a form that will support alignment with other, heterogeneous views. The result will be an extensive, all-encompassing data model that captures the relationships between different views of the same concept.

The contents of the City Data Model will be stratified into 3 levels of abstraction (pictured below). The Foundation Level covers very general concepts such as Time, Location, and Activity. The City Level covers concepts that are general to cities and span all services such as Households, Services, Residents. The Service Level spans concepts commonly associated with a particular service but still shared with other services, such as Vehicles and Transportation network. Initial efforts in this collaboratory will focus on the identification and development of the City-level concepts.

The three levels of the city data model: foundational concepts, city-level concepts, and service-level concepts.

What is the a global collaboratory?

The Collaboratory is a tool to support the creation of the city data model. It houses the conversation on what concepts should be included, and how different concepts from different groups are related to one another. The purpose of this collaboratory is to provide an environment wherein individuals from related standards organizations and other stakeholders can openly contribute to the development of a standard model for city data. It is maintained by the University of Toronto’s School of Cities and Enterprise Integration Laboratory.