Main Page - Revision history

Megankatsumi at 19:03, 13 December 2022

2022-12-13T19:03:45Z

← Older revision		Revision as of 19:03, 13 December 2022
Line 10:		Line 10:
	=== The big picture ===		=== The big picture ===
	The goal of the Collaboratory is to bring together related definitions from various perspectives (including but not necessarily limited to existing standard specifications), for terms relevant for the city domain from various perspectives in order to to develop a global consensus regarding the classes, properties, and definitions that should be included in a City Data Model.		The goal of the Collaboratory is to bring together related definitions from various perspectives (including but not necessarily limited to existing standard specifications), for terms relevant for the city domain from various perspectives in order to to develop a global consensus regarding the classes, properties, and definitions that should be included in a City Data Model.
	This website will serve as a means of establishing this consensus through open communication and collaboration. It facilitates the sharing of definitions, suggestions, comments, and critiques. These activities will be guided by a City Data Model Reference Architecture (CDMRA) and will enable the identification of formal relationships between definitions, with the goal of eventually identifying a [minimum viable definition] for each term. This definition will be formulated such that the relationship with any more specific terms will be clearly identifiable and understandable.		This website will serve as a means of establishing this consensus through open communication and collaboration. It facilitates the sharing of definitions, suggestions, comments, and critiques. These activities will be guided by a City Data Model Reference Architecture (CDMRA) and will enable the identification of formal relationships between definitions, with the goal of eventually identifying a [[Minimum viable definition\|minimum viable definition]] for each term. This definition will be formulated such that the relationship with any more specific terms will be clearly identifiable and understandable.

	The aim of the CDM is not to specify a single, monolithic city data standard, but rather to identify and define the core set of terms necessary to serve as the bridge between existing standards and applications operating in the city context.		The aim of the CDM is not to specify a single, monolithic city data standard, but rather to identify and define the core set of terms necessary to serve as the bridge between existing standards and applications operating in the city context.
Line 46:		Line 46:
	Steps 2 and 3 may be done in any order.		Steps 2 and 3 may be done in any order.

	Use cases and term definitions will be subject to editorial review and feedback by the editorial board to ensure compliance with the [https://github.com/w3c/tocc/blob/master/management/Framework.md CDMRA framework]. As the content on the matures, the editorial board will begin the process of extracting and formalizing the [minimum viable definitions] from related terms. These definitions will form the content of the CDM. The formalized relationship between the definitions and the community-added content will specify the relationship between any two related terms.		Use cases and term definitions will be subject to editorial review and feedback by the editorial board to ensure compliance with the [https://github.com/w3c/tocc/blob/master/management/Framework.md CDMRA framework]. As the content on the matures, the editorial board will begin the process of extracting and formalizing the [[Minimum viable definition\|minimum viable definitions]] from related terms. These definitions will form the content of the CDM. The formalized relationship between the definitions and the community-added content will specify the relationship between any two related terms.

	For details on the information required to specify content, please see the [https://github.com/w3c/tocc/blob/master/management/Framework.mdfull CDMRA framework specification].		For details on the information required to specify content, please see the [https://github.com/w3c/tocc/blob/master/management/Framework.mdfull CDMRA framework specification].

Megankatsumi at 15:46, 13 December 2022

2022-12-13T15:46:09Z

← Older revision		Revision as of 15:46, 13 December 2022
Line 40:		Line 40:

	== How it works ==		== How it works ==
	The content of the CDM is use case-driven. Any terms added ~~should (directly or indirectly)~~ be used by a use case. Beyond this, ~~there are~~ different approaches to adding content: the key patterns could be identified first, followed by a specification of the involved classes and properties. Alternatively, the required classes and properties may be defined first, and then referenced by Pattern specifications that illustrate how they are used together. To add content to the CDM:		The content of the CDM is use case-driven. Any terms added must be used by a use case. Beyond this, different approaches to adding content may be taken: the key patterns could be identified first, followed by a specification of the involved classes and properties. Alternatively, the required classes and properties may be defined first, and then referenced by Pattern specifications that illustrate how they are used together. To add content to the CDM:
	# Specify a [[:Category:Use_Case\|use case]], including the identification of necessary terms.		# Specify a [[:Category:Use_Case\|use case]], including the identification of necessary terms.
	# Specify the definition of the necessary terms ([[:Category:Class\|classes]], [[:Category:ObjectProperty\|object properties]], or [[:Category:DataProperty\|data properties]]), as possible. If no definition is currently available, a term may still be left in the use case as a placeholder to indicate the need for a term.		# Specify the definition of the necessary terms ([[:Category:Class\|classes]], [[:Category:ObjectProperty\|object properties]], or [[:Category:DataProperty\|data properties]]), as possible. If no definition is currently available, a term may still be left in the use case as a placeholder to indicate the need for a term.

Megankatsumi at 15:44, 13 December 2022

2022-12-13T15:44:53Z

← Older revision		Revision as of 15:44, 13 December 2022
Line 24:		Line 24:

	'''Note:''' The following descriptions focus on the meaning of the different types of terms in the context of the OWL, RDF and UML languages. While there are strong similarities between the term types, there are differences in the expressive abilities of the referenced languages. As a result, it will not always be possible to completely translate a term definition from one language to another.		'''Note:''' The following descriptions focus on the meaning of the different types of terms in the context of the OWL, RDF and UML languages. While there are strong similarities between the term types, there are differences in the expressive abilities of the referenced languages. As a result, it will not always be possible to completely translate a term definition from one language to another.
	* A '''Use Case''' describes a scenario where city data is used to meet the needs of various system actors. In doing so it identifies the relevant information, and the classes and properties needed to define that information. In this sense, the use cases defined here are a specialized, more detailed version of use cases as they are defined in UML. See the [https://github.com/w3c/tocc/blob/master/management/Framework.md ~~CDRMA~~ Framework] document for full details on the elements involved in the specification of a use case.		* A '''Use Case''' describes a scenario where city data is used to meet the needs of various system actors. In doing so it identifies the relevant information, and the classes and properties needed to define that information. In this sense, the use cases defined here are a specialized, more detailed version of use cases as they are defined in UML. See the [https://github.com/w3c/tocc/blob/master/management/Framework.md CDMRA Framework] document for full details on the elements involved in the specification of a use case.
	* A '''Pattern''' is a collection of classes and properties that are used to describe a topic of interest; it provides a description of how the terms are related to one another in the context of that topic.		* A '''Pattern''' is a collection of classes and properties that are used to describe a topic of interest; it provides a description of how the terms are related to one another in the context of that topic.
	* A '''Class''' is a term that is used to describe some grouping of things. Classes may be related to other classes via a notion of inheritance (subclass).		* A '''Class''' is a term that is used to describe some grouping of things. Classes may be related to other classes via a notion of inheritance (subclass).

Megankatsumi at 15:44, 13 December 2022

2022-12-13T15:44:27Z

← Older revision		Revision as of 15:44, 13 December 2022
Line 40:		Line 40:

	== How it works ==		== How it works ==
	The content of the CDM is use case-driven. Any terms added should (directly or indirectly) be used by a use case. To add content to the CDM:		The content of the CDM is use case-driven. Any terms added should (directly or indirectly) be used by a use case. Beyond this, there are different approaches to adding content: the key patterns could be identified first, followed by a specification of the involved classes and properties. Alternatively, the required classes and properties may be defined first, and then referenced by Pattern specifications that illustrate how they are used together. To add content to the CDM:
	# Specify a [[:Category:Use_Case\|use case]], including the identification of necessary terms.		# Specify a [[:Category:Use_Case\|use case]], including the identification of necessary terms.
	# Specify the definition of the necessary terms ([[:Category:Class\|classes]], [[:Category:ObjectProperty\|object properties]], or [[:Category:DataProperty\|data properties]]), as possible. If no definition is currently available, a term may still be left in the use case as a placeholder to indicate the need for a term.		# Specify the definition of the necessary terms ([[:Category:Class\|classes]], [[:Category:ObjectProperty\|object properties]], or [[:Category:DataProperty\|data properties]]), as possible. If no definition is currently available, a term may still be left in the use case as a placeholder to indicate the need for a term.
	# Create one or more [[:Category:Pattern\|patterns]] to illustrate how the defined terms relate to one-another.		# Create one or more [[:Category:Pattern\|patterns]] to illustrate how the defined terms relate to one-another.
			Steps 2 and 3 may be done in any order.

	Use cases and term definitions will be subject to editorial review and feedback by the editorial board to ensure compliance with the [https://github.com/w3c/tocc/blob/master/management/Framework.md CDMRA framework]. As the content on the matures, the editorial board will begin the process of extracting and formalizing the [minimum viable definitions] from related terms. These definitions will form the content of the CDM. The formalized relationship between the definitions and the community-added content will specify the relationship between any two related terms.		Use cases and term definitions will be subject to editorial review and feedback by the editorial board to ensure compliance with the [https://github.com/w3c/tocc/blob/master/management/Framework.md CDMRA framework]. As the content on the matures, the editorial board will begin the process of extracting and formalizing the [minimum viable definitions] from related terms. These definitions will form the content of the CDM. The formalized relationship between the definitions and the community-added content will specify the relationship between any two related terms.

	For details on the information required to specify content, please see the [https://github.com/w3c/tocc/blob/master/management/Framework.mdfull CDMRA framework specification].		For details on the information required to specify content, please see the [https://github.com/w3c/tocc/blob/master/management/Framework.mdfull CDMRA framework specification].

Megankatsumi at 15:40, 13 December 2022

2022-12-13T15:40:53Z

← Older revision		Revision as of 15:40, 13 December 2022
Line 24:		Line 24:

	'''Note:''' The following descriptions focus on the meaning of the different types of terms in the context of the OWL, RDF and UML languages. While there are strong similarities between the term types, there are differences in the expressive abilities of the referenced languages. As a result, it will not always be possible to completely translate a term definition from one language to another.		'''Note:''' The following descriptions focus on the meaning of the different types of terms in the context of the OWL, RDF and UML languages. While there are strong similarities between the term types, there are differences in the expressive abilities of the referenced languages. As a result, it will not always be possible to completely translate a term definition from one language to another.
			* A '''Use Case''' describes a scenario where city data is used to meet the needs of various system actors. In doing so it identifies the relevant information, and the classes and properties needed to define that information. In this sense, the use cases defined here are a specialized, more detailed version of use cases as they are defined in UML. See the [https://github.com/w3c/tocc/blob/master/management/Framework.md CDRMA Framework] document for full details on the elements involved in the specification of a use case.
			* A '''Pattern''' is a collection of classes and properties that are used to describe a topic of interest; it provides a description of how the terms are related to one another in the context of that topic.
	* A '''Class''' is a term that is used to describe some grouping of things. Classes may be related to other classes via a notion of inheritance (subclass).		* A '''Class''' is a term that is used to describe some grouping of things. Classes may be related to other classes via a notion of inheritance (subclass).
	**OWL: Classes correspond to Classes as defined in OWL2. <q>In general classes are used to group individuals that have something in common in order to refer to them. Hence, classes essentially represent sets of individuals. In modelling, classes are often used to denote the set of objects comprised by a concept of human thinking, like the concept person or the concept woman.</q> --[https://www.w3.org/TR/owl2-primer/#Classes.2C_Properties.2C_and_Individuals_.E2.80.93_And_Basic_Modeling_With_Them\| Owl2 Primer]		**OWL: Classes correspond to Classes as defined in OWL2. <q>In general classes are used to group individuals that have something in common in order to refer to them. Hence, classes essentially represent sets of individuals. In modelling, classes are often used to denote the set of objects comprised by a concept of human thinking, like the concept person or the concept woman.</q> --[https://www.w3.org/TR/owl2-primer/#Classes.2C_Properties.2C_and_Individuals_.E2.80.93_And_Basic_Modeling_With_Them\| Owl2 Primer]

Megankatsumi at 19:29, 8 December 2022

2022-12-08T19:29:34Z

← Older revision		Revision as of 19:29, 8 December 2022
Line 8:		Line 8:
	[[File:City data levels.png\|thumb\|center\|The three levels of the city data model: foundational concepts, city-level concepts, and service-level concepts.]]		[[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 big picture ==		=== The big picture ===
	The goal of the Collaboratory is to bring together related definitions from various perspectives (including but not necessarily limited to existing standard specifications), for terms relevant for the city domain from various perspectives in order to to develop a global consensus regarding the classes, properties, and definitions that should be included in a City Data Model.		The goal of the Collaboratory is to bring together related definitions from various perspectives (including but not necessarily limited to existing standard specifications), for terms relevant for the city domain from various perspectives in order to to develop a global consensus regarding the classes, properties, and definitions that should be included in a City Data Model.
	This website will serve as a means of establishing this consensus through open communication and collaboration. It facilitates the sharing of definitions, suggestions, comments, and critiques. These activities will be guided by a City Data Model Reference Architecture (CDMRA) and will enable the identification of formal relationships between definitions, with the goal of eventually identifying a [minimum viable definition] for each term. This definition will be formulated such that the relationship with any more specific terms will be clearly identifiable and understandable.		This website will serve as a means of establishing this consensus through open communication and collaboration. It facilitates the sharing of definitions, suggestions, comments, and critiques. These activities will be guided by a City Data Model Reference Architecture (CDMRA) and will enable the identification of formal relationships between definitions, with the goal of eventually identifying a [minimum viable definition] for each term. This definition will be formulated such that the relationship with any more specific terms will be clearly identifiable and understandable.

Megankatsumi at 19:29, 8 December 2022

2022-12-08T19:29:09Z

← Older revision		Revision as of 19:29, 8 December 2022
Line 8:		Line 8:
	[[File:City data levels.png\|thumb\|center\|The three levels of the city data model: foundational concepts, city-level concepts, and service-level concepts.]]		[[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 big picture ==		== The big picture ==
	The goal of the Collaboratory is to bring together related definitions from various perspectives (including but not necessarily limited to existing standard specifications), for terms relevant for the city domain from various perspectives in order to to develop a global consensus regarding the classes, properties, and definitions that should be included in a City Data Model.		The goal of the Collaboratory is to bring together related definitions from various perspectives (including but not necessarily limited to existing standard specifications), for terms relevant for the city domain from various perspectives in order to to develop a global consensus regarding the classes, properties, and definitions that should be included in a City Data Model.
	This website will serve as a means of establishing this consensus through open communication and collaboration. It facilitates the sharing of definitions, suggestions, comments, and critiques. These activities will be guided by a City Data Model Reference Architecture (CDMRA) and will enable the identification of formal relationships between definitions, with the goal of eventually identifying a [minimum viable definition] for each term. This definition will be formulated such that the relationship with any more specific terms will be clearly identifiable and understandable.		This website will serve as a means of establishing this consensus through open communication and collaboration. It facilitates the sharing of definitions, suggestions, comments, and critiques. These activities will be guided by a City Data Model Reference Architecture (CDMRA) and will enable the identification of formal relationships between definitions, with the goal of eventually identifying a [minimum viable definition] for each term. This definition will be formulated such that the relationship with any more specific terms will be clearly identifiable and understandable.

Megankatsumi at 19:28, 8 December 2022

2022-12-08T19:28:49Z

Show changes

Megankatsumi at 19:16, 17 November 2022

2022-11-17T19:16:56Z

← Older revision		Revision as of 19:16, 17 November 2022
Line 1:		Line 1:
	<h1> Welcome to the City Data Model Collaboration Wiki</h1>		<h1> Welcome to the City Data Model Collaboration Wiki</h1>
	== Introduction ==		== Introduction ==
	This website is intended to foster international collaboration between stakeholders and related standards groups on a common [[City_Data_Model_Project_Collaboratory_Wiki:About\|City Data Model]]. The results of this effort will feed into the various city data standards development projects being undertaken by various Standards Development Organizations.		This website is intended to foster international collaboration between stakeholders and related standards groups on a common [[City_Data_Model_Project_Collaboratory_Wiki:About\|City Data Model]]. The results of this effort will be informed by and feed into the various city data standards development projects being undertaken by various Standards Development Organizations.

	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. Beyond syntactic integration (e.g. common data types and protocols), this requires semantic integration: a consistent, shared understanding of the meaning of information.		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. Beyond syntactic integration (e.g. common data types and protocols), this requires semantic integration: a consistent, shared understanding of the meaning of information.
Line 11:		Line 11:

	=== Beta Disclaimer ===		=== Beta Disclaimer ===
	Please note that this is a beta version of the City Data Model Collaboratory website. The website is still undergoing testing and evaluation. Should you encounter any bugs, glitches, ~~lack of functionality~~ or other problems on the website, please let us know immediately so we ~~can rectify these accordingly~~. Your help in this regard is greatly appreciated.		Please note that this is a beta version of the City Data Model Collaboratory website. The website is still undergoing testing and evaluation. Should you encounter any bugs, glitches, or other problems on the website, please let us know immediately and we will address any issues as soon as possible. Your help in this regard is greatly appreciated.

	== Getting started ==		== Getting started ==
	Want to contribute? Log-in or ~~create~~ an account!		Want to contribute? Log-in or request an account!
	Anyone with an account can comment on proposed or existing terms, and even propose their own.		Anyone with an account can comment on proposed or existing terms, and even propose their own.

	~~'''To do~~:~~''' Add material on~~ use ~~cases.~~		Define a [[:Category:Use_Case\|use case]], define a [[:Category:Pattern\|pattern]], propose new [[:Category:Class\|classes]], [[:Category:ObjectProperty\|object properties]], or [[:Category:DataProperty\|data properties]].

	~~Users can~~ propose new ~~terms or new definitions for existing~~ [[:Category:Class\|classes]], [[:Category:ObjectProperty\|object properties]], or [[:Category:DataProperty\|data properties]].

	'''Note:''' The following descriptions focus on the meaning of the different types of terms in the context of the OWL, RDF and UML languages. While there are strong similarities between the term types, there are differences in the expressive abilities of the referenced languages. As a result, it will not always be possible to completely translate a term definition from one language to another.		'''Note:''' The following descriptions focus on the meaning of the different types of terms in the context of the OWL, RDF and UML languages. While there are strong similarities between the term types, there are differences in the expressive abilities of the referenced languages. As a result, it will not always be possible to completely translate a term definition from one language to another.

Xuanni1 at 00:19, 28 September 2021

2021-09-28T00:19:28Z

← Older revision		Revision as of 00:19, 28 September 2021
Line 53:		Line 53:

	Here's a high-level overview of the process that we follow when a new term is proposed for the City Data Model:		Here's a high-level overview of the process that we follow when a new term is proposed for the City Data Model:
	~~[[Category:Ontology]]~~
	<uml>		<uml>
	@startuml		@startuml