<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://ontologydesignpatterns.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=MeganKatsumi</id>
		<title>'Ontology Design Patterns' - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="http://ontologydesignpatterns.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=MeganKatsumi"/>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php/Special:Contributions/MeganKatsumi"/>
		<updated>2026-05-20T20:23:20Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.25.6</generator>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13879</id>
		<title>Submissions:Change of Time Varying Entities</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13879"/>
				<updated>2020-08-27T18:50:50Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Logical_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Before-after.png&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP General Template&lt;br /&gt;
|Name=Change of Time Varying Entities&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Description Template&lt;br /&gt;
|Motivation=This work is motivated by a project on urban informatics, iCity \cite{miller2014}, in which our role is to develop an ontology capable of representing the urban system -- both the information that is collected, as well as information that is simulated and analyzed by various research groups. Such an ontology would not only provide valuable integration and inference capabilities for the research groups internally, it would support sharing of the results on the Semantic Web, in particular for reproducibility of simulations and analyses. Owing to its popularity, tool support, and role as the de facto standard for the Semantic Web, OWL was selected as the logical language for the formalization of the ontology. &lt;br /&gt;
To capture the urban domain, the notion of change over time is a critical requirement: the population, family and household structures, transportation networks, and the locations of particular transportation vehicles (buses, household vehicles, and so on) are all subject to change.&lt;br /&gt;
&lt;br /&gt;
Change over time plays a role in many domains, and is by no means a new research topic. In fact, several approaches for capturing change in OWL have been proposed in the literature. Despite these solutions, we have found that Semantic Web practitioners currently lack clear and precise method for how to apply these approaches to capture change at a domain level, whether reusing an atemporal ontology or developing an ontology from scratch.&lt;br /&gt;
|Aim=The work presented here aims to provide a straightforward, pattern-based guide to implementing a representation of change for any given domain. In particular, we provide consideration for the reuse of atemporal ontologies, as our experience has led us to believe that this is an important design task.&lt;br /&gt;
|Solution=The solution is based on the 4D Fluents Ontology [2], as reinterpreted by Krieger [1].&lt;br /&gt;
&lt;br /&gt;
[1] Krieger, H.U.: Where temporal description logics fail: Representing temporally changing relationships. In: Annual Conference on Arti�cial Intelligence. pp. 249-257. Springer (2008)&lt;br /&gt;
&lt;br /&gt;
[2] Welty, C., Fikes, R., Makarios, S.: A reusable ontology for Fuents in owl. In: Formal Ontology in Information Systems (FOIS). vol. 150, pp. 226-236 (2006)&lt;br /&gt;
|Implementation=A foundational ontology of change is to be imported. Then, based on the foundational classes of TimeVaryingEntity and Manifestation, a simple set of logical design patterns may be applied. A pragmatic guideline to support this process is provided in the accompanying paper submission.&lt;br /&gt;
Several additional logical design patterns are identified, along with descriptions of how they could be employed to provide extended semantics in a representation beyond OWL (e.g. SWRL), should additional reasoning capabilities be required.&lt;br /&gt;
|ReusableComponent=http://ontology.eil.utoronto.ca/icity/Change&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Example Template}}&lt;br /&gt;
{{Logical OP Reference Template}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13639</id>
		<title>Submissions:ActivitySpecification</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13639"/>
				<updated>2019-03-11T20:03:41Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Content_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Activityspec op.png&lt;br /&gt;
}}&lt;br /&gt;
{{Content OP Proposal Template&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
|Name=ActivitySpecification&lt;br /&gt;
|ContentODPAlsoKnownAs=Activity Specification OP&lt;br /&gt;
|Intent=This work is concerned with supporting a correct and meaningful representation of activities on the Semantic Web, with the potential to support tasks such as activity recognition and reasoning about causation. This requires an ontology capable of more than simply documenting and annotating individual activity occurrences; definitions of activity specifications are required.&lt;br /&gt;
Current representations of activities in OWL do not meet the basic requirements for activity specifications. Detailed definitions of an activity's preconditions and effects are lacking, in particular with respect to a consideration of change over time.&lt;br /&gt;
This pattern leverages existing work to fill this void with an ontology design pattern for activity specifications in OWL.&lt;br /&gt;
|Domain=Event Processing, General&lt;br /&gt;
|CompetencyQuestion=What are the preconditions (effects) of a given activity?,&lt;br /&gt;
Is/are the precondition(s) true at some time t?,&lt;br /&gt;
Is/are the effect(s) true at some time t?,&lt;br /&gt;
If we observe some state, what activity may have caused it?&lt;br /&gt;
|ContentODPDescription=The proposed solution adopts a view of causality similar to the Event Calculus [Kowalski, 1986], employing the concept of manifestations to describe the states (fluents).&lt;br /&gt;
|ReusableOWLBuildingBlock=http://ontology.eil.utoronto.ca/icity/ActivitySpecification&lt;br /&gt;
|Consequences=(-) Requires a temporal representation of the domain -- specifically using the Logical OP for change -- which results in a larger, more complex representation.&lt;br /&gt;
(+) However, given that the concepts are preconditions and effects of an activity, they should be subject to change and so the resulting representation is (though larger) more appropriate and more accurate.&lt;br /&gt;
|Scenario=This pattern is applicable for a wide range of scenarios. In essence, for the formalization of any activity precondition/effect. For example: -My car must have gas (an manifestation of a specific vehicle should have gas) before I can drive to work (the manifestation should exist at some time before the drive to work activity occurs)  -An effect of my driving to work is that I am at work and so is my car.&lt;br /&gt;
|KnownUse=http://ontology.eil.utoronto.ca/icity/UrbanSystem&lt;br /&gt;
|ExtractedFrom=http://ontology.eil.utoronto.ca/icity/Activity/1.1/&lt;br /&gt;
|HasComponent=http://ontology.eil.utoronto.ca/icity/Change/&lt;br /&gt;
|RelatedCP=http://ontologydesignpatterns.org/wiki/Submissions:Change_of_Time_Varying_Entities&lt;br /&gt;
}}&lt;br /&gt;
{{Element list header}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13638</id>
		<title>Submissions:ActivitySpecification</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13638"/>
				<updated>2019-03-11T20:02:40Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Content_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Activityspec op.png&lt;br /&gt;
}}&lt;br /&gt;
{{Content OP Proposal Template&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
|Name=ActivitySpecification&lt;br /&gt;
|ContentODPAlsoKnownAs=Activity Specification OP&lt;br /&gt;
|Intent=This work is concerned with supporting a correct and meaningful representation of activities on the Semantic Web, with the potential to support tasks such as activity recognition and reasoning about causation. This requires an ontology capable of more than simply documenting and annotating individual activity occurrences; definitions of activity specifications are required.&lt;br /&gt;
Current representations of activities in OWL do not meet the basic requirements for activity specifications. Detailed definitions of an activity's preconditions and effects are lacking, in particular with respect to a consideration of change over time.&lt;br /&gt;
This pattern leverages existing work to fill this void with an ontology design pattern for activity specifications in OWL.&lt;br /&gt;
|Domain=Event Processing, General&lt;br /&gt;
|CompetencyQuestion=What are the preconditions (effects) of a given activity?,&lt;br /&gt;
Is/are the precondition(s) true at some time t?,&lt;br /&gt;
Is/are the effect(s) true at some time t?,&lt;br /&gt;
If we observe some state, what activity may have caused it?&lt;br /&gt;
|ContentODPDescription=The proposed solution adopts a view of causality similar to the Event Calculus [Kowalski, 1986], employing the concept of manifestations to describe the states (fluents).&lt;br /&gt;
|ReusableOWLBuildingBlock=http://ontology.eil.utoronto.ca/icity/ActivitySpecification&lt;br /&gt;
|Consequences=(-) Requires a temporal representation of the domain -- specifically using the Logical OP for change -- which results in a larger, more complex representation.&lt;br /&gt;
(+) However, given that the concepts are preconditions and effects of an activity, they should be subject to change and so the resulting representation is (though larger) more appropriate and more accurate.&lt;br /&gt;
|Scenario=This pattern is applicable for a wide range of scenarios. In essence, for the formalization of any activity precondition/effect. For example: -My car must have gas (an manifestation of a specific vehicle should have gas) before I can drive to work (the manifestation should exist at some time before the drive to work activity occurs)  -An effect of my driving to work is that I am at work and so is my car.&lt;br /&gt;
|KnownUse=https://w3id.org/icity/iCity-UrbanSystem&lt;br /&gt;
|ExtractedFrom=https://w3id.org/icity/iCity-Activity/1.1/&lt;br /&gt;
|HasComponent=https://w3id.org/icity/iCity-Change/&lt;br /&gt;
|RelatedCP=http://ontologydesignpatterns.org/wiki/Submissions:Change_of_Time_Varying_Entities&lt;br /&gt;
}}&lt;br /&gt;
{{Element list header}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13283</id>
		<title>Submissions:Change of Time Varying Entities</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13283"/>
				<updated>2017-09-09T10:35:32Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Logical_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Before-after.png&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP General Template&lt;br /&gt;
|Name=Change of Time Varying Entities&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Description Template&lt;br /&gt;
|Motivation=This work is motivated by a project on urban informatics, iCity \cite{miller2014}, in which our role is to develop an ontology capable of representing the urban system -- both the information that is collected, as well as information that is simulated and analyzed by various research groups. Such an ontology would not only provide valuable integration and inference capabilities for the research groups internally, it would support sharing of the results on the Semantic Web, in particular for reproducibility of simulations and analyses. Owing to its popularity, tool support, and role as the de facto standard for the Semantic Web, OWL was selected as the logical language for the formalization of the ontology. &lt;br /&gt;
To capture the urban domain, the notion of change over time is a critical requirement: the population, family and household structures, transportation networks, and the locations of particular transportation vehicles (buses, household vehicles, and so on) are all subject to change.&lt;br /&gt;
&lt;br /&gt;
Change over time plays a role in many domains, and is by no means a new research topic. In fact, several approaches for capturing change in OWL have been proposed in the literature. Despite these solutions, we have found that Semantic Web practitioners currently lack clear and precise method for how to apply these approaches to capture change at a domain level, whether reusing an atemporal ontology or developing an ontology from scratch.&lt;br /&gt;
|Aim=The work presented here aims to provide a straightforward, pattern-based guide to implementing a representation of change for any given domain. In particular, we provide consideration for the reuse of atemporal ontologies, as our experience has led us to believe that this is an important design task.&lt;br /&gt;
|Solution=The solution is based on the 4D Fluents Ontology [2], as reinterpreted by Krieger [1].&lt;br /&gt;
&lt;br /&gt;
[1] Krieger, H.U.: Where temporal description logics fail: Representing temporally changing relationships. In: Annual Conference on Arti�cial Intelligence. pp. 249-257. Springer (2008)&lt;br /&gt;
&lt;br /&gt;
[2] Welty, C., Fikes, R., Makarios, S.: A reusable ontology for Fuents in owl. In: Formal Ontology in Information Systems (FOIS). vol. 150, pp. 226-236 (2006)&lt;br /&gt;
|Implementation=A foundational ontology of change is to be imported. Then, based on the foundational classes of TimeVaryingEntity and Manifestation, a simple set of logical design patterns may be applied. A pragmatic guideline to support this process is provided in the accompanying paper submission.&lt;br /&gt;
Several additional logical design patterns are identified, along with descriptions of how they could be employed to provide extended semantics in a representation beyond OWL (e.g. SWRL), should additional reasoning capabilities be required.&lt;br /&gt;
|ReusableComponent=https://w3id.org/icity/iCity-Change&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Example Template}}&lt;br /&gt;
{{Logical OP Reference Template}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13277</id>
		<title>Submissions:ActivitySpecification</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13277"/>
				<updated>2017-07-25T17:01:25Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Content_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Activityspec op.png&lt;br /&gt;
}}&lt;br /&gt;
{{Content OP Proposal Template&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
|Name=ActivitySpecification&lt;br /&gt;
|ContentODPAlsoKnownAs=Activity Specification OP&lt;br /&gt;
|Intent=This work is concerned with supporting a correct and meaningful representation of activities on the Semantic Web, with the potential to support tasks such as activity recognition and reasoning about causation. This requires an ontology capable of more than simply documenting and annotating individual activity occurrences; definitions of activity specifications are required.&lt;br /&gt;
Current representations of activities in OWL do not meet the basic requirements for activity specifications. Detailed definitions of an activity's preconditions and effects are lacking, in particular with respect to a consideration of change over time.&lt;br /&gt;
This pattern leverages existing work to fill this void with an ontology design pattern for activity specifications in OWL.&lt;br /&gt;
|Domain=Event Processing, General&lt;br /&gt;
|CompetencyQuestion=What are the preconditions (effects) of a given activity?,&lt;br /&gt;
Is/are the precondition(s) true at some time t?,&lt;br /&gt;
Is/are the effect(s) true at some time t?,&lt;br /&gt;
If we observe some state, what activity may have caused it?&lt;br /&gt;
|ContentODPDescription=The proposed solution adopts a view of causality similar to the Event Calculus [Kowalski, 1986], employing the concept of manifestations to describe the states (fluents).&lt;br /&gt;
|ReusableOWLBuildingBlock=https://w3id.org/icity/ActivitySpecification&lt;br /&gt;
|Consequences=(-) Requires a temporal representation of the domain -- specifically using the Logical OP for change -- which results in a larger, more complex representation.&lt;br /&gt;
(+) However, given that the concepts are preconditions and effects of an activity, they should be subject to change and so the resulting representation is (though larger) more appropriate and more accurate.&lt;br /&gt;
|Scenario=This pattern is applicable for a wide range of scenarios. In essence, for the formalization of any activity precondition/effect. For example: -My car must have gas (an manifestation of a specific vehicle should have gas) before I can drive to work (the manifestation should exist at some time before the drive to work activity occurs)  -An effect of my driving to work is that I am at work and so is my car.&lt;br /&gt;
|KnownUse=https://w3id.org/icity/iCity-UrbanSystem&lt;br /&gt;
|ExtractedFrom=https://w3id.org/icity/iCity-Activity/1.1/&lt;br /&gt;
|HasComponent=https://w3id.org/icity/iCity-Change/&lt;br /&gt;
|RelatedCP=http://ontologydesignpatterns.org/wiki/Submissions:Change_of_Time_Varying_Entities&lt;br /&gt;
}}&lt;br /&gt;
{{Element list header}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Feedback:Unable_to_move_pattern&amp;diff=13276</id>
		<title>Feedback:Unable to move pattern</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Feedback:Unable_to_move_pattern&amp;diff=13276"/>
				<updated>2017-07-25T16:56:34Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: issue clarified, this issue is n/a&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TitleDescription Template&lt;br /&gt;
|Title=Unable to move pattern&lt;br /&gt;
|Description=I've just created a Logical OP, originally entitled &amp;quot;Change Logical OP&amp;quot;. I tried to use the move option to rename the pattern's page more accurately to &amp;quot;Change of Time Varying Entities&amp;quot; but receive a message &amp;quot;You are not allowed to execute the action you have requested.&amp;quot; when I attempt this. I've checked and the latter name is not currently in use.&lt;br /&gt;
}}&lt;br /&gt;
{{Feedback Template&lt;br /&gt;
|Author=MeganKatsumi,&lt;br /&gt;
|Priority=Medium&lt;br /&gt;
|Status=obsolete&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13274</id>
		<title>Submissions:Change of Time Varying Entities</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13274"/>
				<updated>2017-07-25T16:54:35Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: Submissions:Change Logical OP moved to Submissions:Change of Time Varying Entities: More accurate title&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Logical_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Before-after.png&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP General Template&lt;br /&gt;
|Name=Change of Time Varying Entities&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Description Template&lt;br /&gt;
|Motivation=This work is motivated by a project on urban informatics, iCity \cite{miller2014}, in which our role is to develop an ontology capable of representing the urban system -- both the information that is collected, as well as information that is simulated and analyzed by various research groups. Such an ontology would not only provide valuable integration and inference capabilities for the research groups internally, it would support sharing of the results on the Semantic Web, in particular for reproducibility of simulations and analyses. Owing to its popularity, tool support, and role as the de facto standard for the Semantic Web, OWL was selected as the logical language for the formalization of the ontology. &lt;br /&gt;
To capture the urban domain, the notion of change over time is a critical requirement: the population, family and household structures, transportation networks, and the locations of particular transportation vehicles (buses, household vehicles, and so on) are all subject to change.&lt;br /&gt;
&lt;br /&gt;
Change over time plays a role in many domains, and is by no means a new research topic. In fact, several approaches for capturing change in OWL have been proposed in the literature. Despite these solutions, we have found that Semantic Web practitioners currently lack clear and precise method for how to apply these approaches to capture change at a domain level, whether reusing an atemporal ontology or developing an ontology from scratch.&lt;br /&gt;
|Aim=The work presented here aims to provide a straightforward, pattern-based guide to implementing a representation of change for any given domain. In particular, we provide consideration for the reuse of atemporal ontologies, as our experience has led us to believe that this is an important design task.&lt;br /&gt;
|Solution=The solution is based on the 4D Fluents Ontology [2], as reinterpreted by Krieger [1].&lt;br /&gt;
&lt;br /&gt;
[1] Krieger, H.U.: Where temporal description logics fail: Representing temporally changing relationships. In: Annual Conference on Arti�cial Intelligence. pp. 249-257. Springer (2008)&lt;br /&gt;
&lt;br /&gt;
[2] Welty, C., Fikes, R., Makarios, S.: A reusable ontology for Fuents in owl. In: Formal Ontology in Information Systems (FOIS). vol. 150, pp. 226-236 (2006)&lt;br /&gt;
|Implementation=A foundational ontology of change is to be imported. Then, based on the foundational classes of TimeVaryingConcept and Manifestation, a simple set of logical design patterns may be applied. A pragmatic guideline to support this process is provided in the accompanying paper submission.&lt;br /&gt;
Several additional logical design patterns are identified, along with descriptions of how they could be employed to provide extended semantics in a representation beyond OWL (e.g. SWRL), should additional reasoning capabilities be required.&lt;br /&gt;
|ReusableComponent=https://w3id.org/icity/iCity-Change&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Example Template}}&lt;br /&gt;
{{Logical OP Reference Template}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:Change_Logical_OP&amp;diff=13275</id>
		<title>Submissions:Change Logical OP</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:Change_Logical_OP&amp;diff=13275"/>
				<updated>2017-07-25T16:54:35Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: Submissions:Change Logical OP moved to Submissions:Change of Time Varying Entities: More accurate title&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Submissions:Change of Time Varying Entities]]&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13273</id>
		<title>Submissions:ActivitySpecification</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13273"/>
				<updated>2017-07-25T14:42:50Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Content_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Activityspec op.png&lt;br /&gt;
}}&lt;br /&gt;
{{Content OP Proposal Template&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
|Name=ActivitySpecification&lt;br /&gt;
|ContentODPAlsoKnownAs=Activity Specification OP&lt;br /&gt;
|Intent=This work is concerned with supporting a correct and meaningful representation of activities on the Semantic Web, with the potential to support tasks such as activity recognition and reasoning about causation. This requires an ontology capable of more than simply documenting and annotating individual activity occurrences; definitions of activity specifications are required.&lt;br /&gt;
Current representations of activities in OWL do not meet the basic requirements for activity specifications. Detailed definitions of an activity's preconditions and effects are lacking, in particular with respect to a consideration of change over time.&lt;br /&gt;
This pattern leverages existing work to fill this void with an ontology design pattern for activity specifications in OWL.&lt;br /&gt;
|Domain=Event Processing, General&lt;br /&gt;
|CompetencyQuestion=What are the preconditions (effects) of a given activity?,&lt;br /&gt;
Is/are the precondition(s) true at some time t?,&lt;br /&gt;
Is/are the effect(s) true at some time t?,&lt;br /&gt;
If we observe some state, what activity may have caused it?&lt;br /&gt;
|ContentODPDescription=The proposed solution adopts a view of causality similar to the Event Calculus [Kowalski, 1986], employing the concept of manifestations to describe the states (fluents).&lt;br /&gt;
|ReusableOWLBuildingBlock=https://w3id.org/icity/ActivitySpecification&lt;br /&gt;
|Consequences=(-) Requires a temporal representation of the domain -- specifically using the Logical OP for change -- which results in a larger, more complex representation.&lt;br /&gt;
(+) However, given that the concepts are preconditions and effects of an activity, they should be subject to change and so the resulting representation is (though larger) more appropriate and more accurate.&lt;br /&gt;
|Scenario=This pattern is applicable for a wide range of scenarios. In essence, for the formalization of any activity precondition/effect. For example: -My car must have gas (an manifestation of a specific vehicle should have gas) before I can drive to work (the manifestation should exist at some time before the drive to work activity occurs)  -An effect of my driving to work is that I am at work and so is my car.&lt;br /&gt;
|KnownUse=https://w3id.org/icity/iCity-UrbanSystem&lt;br /&gt;
|ExtractedFrom=https://w3id.org/icity/iCity-Activity/1.1/&lt;br /&gt;
|HasComponent=https://w3id.org/icity/iCity-Change/&lt;br /&gt;
|RelatedCP=http://ontologydesignpatterns.org/wiki/Submissions:Change_Logical_OP&lt;br /&gt;
}}&lt;br /&gt;
{{Element list header}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13272</id>
		<title>Submissions:ActivitySpecification</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13272"/>
				<updated>2017-07-25T14:40:18Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Content_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Activityspec op.png&lt;br /&gt;
}}&lt;br /&gt;
{{Content OP Proposal Template&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
|Name=ActivitySpecification&lt;br /&gt;
|ContentODPAlsoKnownAs=Activity Specification OP&lt;br /&gt;
|Intent=This work is concerned with supporting a correct and meaningful representation of activities on the Semantic Web, with the potential to support tasks such as activity recognition and reasoning about causation. This requires an ontology capable of more than simply documenting and annotating individual activity occurrences; definitions of activity specifications are required.&lt;br /&gt;
Current representations of activities in OWL do not meet the basic requirements for activity specifications. Detailed definitions of an activity's preconditions and effects are lacking, in particular with respect to a consideration of change over time.&lt;br /&gt;
This pattern leverages existing work to fill this void with an ontology design pattern for activity specifications in OWL.&lt;br /&gt;
|Domain=Event Processing, General&lt;br /&gt;
|CompetencyQuestion=What are the preconditions (effects) of a given activity?,&lt;br /&gt;
Is/are the precondition(s) true at some time t?&lt;br /&gt;
Is/are the effect(s) true at some time t?,&lt;br /&gt;
If we observe some state, what activity may have caused it?&lt;br /&gt;
|ContentODPDescription=The proposed solution adopts a view of causality similar to the Event Calculus [Kowalski, 1986], employing the concept of manifestations to describe the states (fluents).&lt;br /&gt;
|ReusableOWLBuildingBlock=https://w3id.org/icity/ActivitySpecification&lt;br /&gt;
|Consequences=(-) Requires a temporal representation of the domain -- specifically using the Logical OP for change -- which results in a larger, more complex representation.&lt;br /&gt;
(+) However, given that the concepts are preconditions and effects of an activity, they should be subject to change and so the resulting representation is (though larger) more appropriate and more accurate.&lt;br /&gt;
|Scenario=This pattern is applicable for a wide range of scenarios. In essence, for the formalization of any activity precondition/effect. For example: -My car must have gas (an manifestation of a specific vehicle should have gas) before I can drive to work (the manifestation should exist at some time before the drive to work activity occurs)  -An effect of my driving to work is that I am at work and so is my car.&lt;br /&gt;
|KnownUse=https://w3id.org/icity/iCity-UrbanSystem&lt;br /&gt;
|ExtractedFrom=https://w3id.org/icity/iCity-Activity/1.1/&lt;br /&gt;
|HasComponent=https://w3id.org/icity/iCity-Change/&lt;br /&gt;
|RelatedCP=http://ontologydesignpatterns.org/wiki/Submissions:Change_Logical_OP&lt;br /&gt;
}}&lt;br /&gt;
{{Element list header}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13271</id>
		<title>Submissions:ActivitySpecification</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13271"/>
				<updated>2017-07-25T14:39:03Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Content_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Activityspec op.png&lt;br /&gt;
}}&lt;br /&gt;
{{Content OP Proposal Template&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
|Name=ActivitySpecification&lt;br /&gt;
|ContentODPAlsoKnownAs=Activity Specification OP&lt;br /&gt;
|Intent=This work is concerned with supporting a correct and meaningful representation of activities on the Semantic Web, with the potential to support tasks such as activity recognition and reasoning about causation. This requires an ontology capable of more than simply documenting and annotating individual activity occurrences; definitions of activity specifications are required.&lt;br /&gt;
Current representations of activities in OWL do not meet the basic requirements for activity specifications. Detailed definitions of an activity's preconditions and effects are lacking, in particular with respect to a consideration of change over time.&lt;br /&gt;
This pattern leverages existing work to fill this void with an ontology design pattern for activity specifications in OWL.&lt;br /&gt;
|Domain=Event Processing, General&lt;br /&gt;
|CompetencyQuestion=What are the preconditions (effects) of a given activity?&lt;br /&gt;
Is/are the precondition(s) true at some time, t?&lt;br /&gt;
Is/are the effect(s) true at some time, t?&lt;br /&gt;
If we observe some state, what activity may have caused it?&lt;br /&gt;
|ContentODPDescription=The proposed solution adopts a view of causality similar to the Event Calculus [Kowalski, 1986], employing the concept of manifestations to describe the states (fluents).&lt;br /&gt;
|ReusableOWLBuildingBlock=https://w3id.org/icity/ActivitySpecification&lt;br /&gt;
|Consequences=(-) Requires a temporal representation of the domain -- specifically using the Logical OP for change -- which results in a larger, more complex representation.&lt;br /&gt;
(+) However, given that the concepts are preconditions and effects of an activity, they should be subject to change and so the resulting representation is (though larger) more appropriate and more accurate.&lt;br /&gt;
|Scenario=This pattern is applicable for a wide range of scenarios. In essence, for the formalization of any activity precondition/effect. For example: -My car must have gas (an manifestation of a specific vehicle should have gas) before I can drive to work (the manifestation should exist at some time before the drive to work activity occurs)  -An effect of my driving to work is that I am at work and so is my car.&lt;br /&gt;
|KnownUse=https://w3id.org/icity/iCity-UrbanSystem&lt;br /&gt;
|ExtractedFrom=https://w3id.org/icity/iCity-Activity/1.1/&lt;br /&gt;
|HasComponent=https://w3id.org/icity/iCity-Change/&lt;br /&gt;
|RelatedCP=http://ontologydesignpatterns.org/wiki/Submissions:Change_Logical_OP&lt;br /&gt;
}}&lt;br /&gt;
{{Element list header}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=File:Activityspec_op.png&amp;diff=13270</id>
		<title>File:Activityspec op.png</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=File:Activityspec_op.png&amp;diff=13270"/>
				<updated>2017-07-25T14:37:58Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=File:Activityspec_op.pdf&amp;diff=13269</id>
		<title>File:Activityspec op.pdf</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=File:Activityspec_op.pdf&amp;diff=13269"/>
				<updated>2017-07-25T14:32:46Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: uploaded a new version of &amp;quot;Image:Activityspec op.pdf&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Activity Specification Design Pattern&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=File:Activityspec_op1.pdf&amp;diff=13268</id>
		<title>File:Activityspec op1.pdf</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=File:Activityspec_op1.pdf&amp;diff=13268"/>
				<updated>2017-07-25T14:31:31Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: Activity Specification Content OP diagram&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Activity Specification Content OP diagram&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13267</id>
		<title>Submissions:ActivitySpecification</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13267"/>
				<updated>2017-07-25T14:14:48Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Content_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Activityspec op.pdf&lt;br /&gt;
}}&lt;br /&gt;
{{Content OP Proposal Template&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
|Name=ActivitySpecification&lt;br /&gt;
|ContentODPAlsoKnownAs=Activity Specification OP&lt;br /&gt;
|Intent=This work is concerned with supporting a correct and meaningful representation of activities on the Semantic Web, with the potential to support tasks such as activity recognition and reasoning about causation. This requires an ontology capable of more than simply documenting and annotating individual activity occurrences; definitions of activity specifications are required.&lt;br /&gt;
Current representations of activities in OWL do not meet the basic requirements for activity specifications. Detailed definitions of an activity's preconditions and effects are lacking, in particular with respect to a consideration of change over time.&lt;br /&gt;
This pattern leverages existing work to fill this void with an ontology design pattern for activity specifications in OWL.&lt;br /&gt;
|Domain=Event Processing, General&lt;br /&gt;
|CompetencyQuestion=What are the preconditions (effects) of a given activity?&lt;br /&gt;
Is/are the precondition(s) true at some time, t?&lt;br /&gt;
Is/are the effect(s) true at some time, t?&lt;br /&gt;
If we observe some state, what activity may have caused it?&lt;br /&gt;
|ContentODPDescription=The proposed solution adopts a view of causality similar to the Event Calculus [Kowalski, 1986], employing the concept of manifestations to describe the states (fluents).&lt;br /&gt;
|ReusableOWLBuildingBlock=https://w3id.org/icity/ActivitySpecification&lt;br /&gt;
|Consequences=(-) Requires a temporal representation of the domain -- specifically using the Logical OP for change -- which results in a larger, more complex representation.&lt;br /&gt;
(+) However, given that the concepts are preconditions and effects of an activity, they should be subject to change and so the resulting representation is (though larger) more appropriate and more accurate.&lt;br /&gt;
|Scenario=This pattern is applicable for a wide range of scenarios. In essence, for the formalization of any activity precondition/effect. For example: -My car must have gas (an manifestation of a specific vehicle should have gas) before I can drive to work (the manifestation should exist at some time before the drive to work activity occurs)  -An effect of my driving to work is that I am at work and so is my car.&lt;br /&gt;
|KnownUse=https://w3id.org/icity/iCity-UrbanSystem&lt;br /&gt;
|ExtractedFrom=https://w3id.org/icity/iCity-Activity/1.1/&lt;br /&gt;
|HasComponent=https://w3id.org/icity/iCity-Change/&lt;br /&gt;
|RelatedCP=http://ontologydesignpatterns.org/wiki/Submissions:Change_Logical_OP&lt;br /&gt;
}}&lt;br /&gt;
{{Element list header}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13266</id>
		<title>Submissions:ActivitySpecification</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:ActivitySpecification&amp;diff=13266"/>
				<updated>2017-07-25T13:58:55Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: Imported from OWL file.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Content_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=&lt;br /&gt;
}}&lt;br /&gt;
{{Content OP Proposal Template&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
|ReusableOWLBuildingBlock=https://w3id.org/icity/ActivitySpecification&lt;br /&gt;
|Name=ActivitySpecification&lt;br /&gt;
}}&lt;br /&gt;
{{Element list header}}&lt;br /&gt;
&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}{{Modeling issues about me}}{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=File:Activityspec_op.pdf&amp;diff=13265</id>
		<title>File:Activityspec op.pdf</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=File:Activityspec_op.pdf&amp;diff=13265"/>
				<updated>2017-07-25T13:41:08Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: Activity Specification Design Pattern&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Activity Specification Design Pattern&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Feedback:Unable_to_move_pattern&amp;diff=13264</id>
		<title>Feedback:Unable to move pattern</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Feedback:Unable_to_move_pattern&amp;diff=13264"/>
				<updated>2017-07-21T15:43:38Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: New page: {{TitleDescription Template |Title=Unable to move pattern |Description=I've just created a Logical OP, originally entitled &amp;quot;Change Logical OP&amp;quot;. I tried to use the move option to rename the...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TitleDescription Template&lt;br /&gt;
|Title=Unable to move pattern&lt;br /&gt;
|Description=I've just created a Logical OP, originally entitled &amp;quot;Change Logical OP&amp;quot;. I tried to use the move option to rename the pattern's page more accurately to &amp;quot;Change of Time Varying Entities&amp;quot; but receive a message &amp;quot;You are not allowed to execute the action you have requested.&amp;quot; when I attempt this. I've checked and the latter name is not currently in use.&lt;br /&gt;
}}&lt;br /&gt;
{{Feedback Template&lt;br /&gt;
|Author=MeganKatsumi, &lt;br /&gt;
|Priority=Medium&lt;br /&gt;
|Status=To be done&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13263</id>
		<title>Submissions:Change of Time Varying Entities</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13263"/>
				<updated>2017-07-21T15:35:10Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Logical_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Before-after.png&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP General Template&lt;br /&gt;
|Name=Change of Time Varying Entities&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Description Template&lt;br /&gt;
|Motivation=This work is motivated by a project on urban informatics, iCity \cite{miller2014}, in which our role is to develop an ontology capable of representing the urban system -- both the information that is collected, as well as information that is simulated and analyzed by various research groups. Such an ontology would not only provide valuable integration and inference capabilities for the research groups internally, it would support sharing of the results on the Semantic Web, in particular for reproducibility of simulations and analyses. Owing to its popularity, tool support, and role as the de facto standard for the Semantic Web, OWL was selected as the logical language for the formalization of the ontology. &lt;br /&gt;
To capture the urban domain, the notion of change over time is a critical requirement: the population, family and household structures, transportation networks, and the locations of particular transportation vehicles (buses, household vehicles, and so on) are all subject to change.&lt;br /&gt;
&lt;br /&gt;
Change over time plays a role in many domains, and is by no means a new research topic. In fact, several approaches for capturing change in OWL have been proposed in the literature. Despite these solutions, we have found that Semantic Web practitioners currently lack clear and precise method for how to apply these approaches to capture change at a domain level, whether reusing an atemporal ontology or developing an ontology from scratch.&lt;br /&gt;
|Aim=The work presented here aims to provide a straightforward, pattern-based guide to implementing a representation of change for any given domain. In particular, we provide consideration for the reuse of atemporal ontologies, as our experience has led us to believe that this is an important design task.&lt;br /&gt;
|Solution=The solution is based on the 4D Fluents Ontology [2], as reinterpreted by Krieger [1].&lt;br /&gt;
&lt;br /&gt;
[1] Krieger, H.U.: Where temporal description logics fail: Representing temporally changing relationships. In: Annual Conference on Arti�cial Intelligence. pp. 249-257. Springer (2008)&lt;br /&gt;
&lt;br /&gt;
[2] Welty, C., Fikes, R., Makarios, S.: A reusable ontology for Fuents in owl. In: Formal Ontology in Information Systems (FOIS). vol. 150, pp. 226-236 (2006)&lt;br /&gt;
|Implementation=A foundational ontology of change is to be imported. Then, based on the foundational classes of TimeVaryingConcept and Manifestation, a simple set of logical design patterns may be applied. A pragmatic guideline to support this process is provided in the accompanying paper submission.&lt;br /&gt;
Several additional logical design patterns are identified, along with descriptions of how they could be employed to provide extended semantics in a representation beyond OWL (e.g. SWRL), should additional reasoning capabilities be required.&lt;br /&gt;
|ReusableComponent=https://w3id.org/icity/iCity-Change&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Example Template}}&lt;br /&gt;
{{Logical OP Reference Template}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13262</id>
		<title>Submissions:Change of Time Varying Entities</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13262"/>
				<updated>2017-07-21T15:30:25Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Logical_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Before-after.png&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP General Template&lt;br /&gt;
|Name=Change: Time Varying Entities&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Description Template&lt;br /&gt;
|Motivation=This work is motivated by a project on urban informatics, iCity \cite{miller2014}, in which our role is to develop an ontology capable of representing the urban system -- both the information that is collected, as well as information that is simulated and analyzed by various research groups. Such an ontology would not only provide valuable integration and inference capabilities for the research groups internally, it would support sharing of the results on the Semantic Web, in particular for reproducibility of simulations and analyses. Owing to its popularity, tool support, and role as the de facto standard for the Semantic Web, OWL was selected as the logical language for the formalization of the ontology. &lt;br /&gt;
To capture the urban domain, the notion of change over time is a critical requirement: the population, family and household structures, transportation networks, and the locations of particular transportation vehicles (buses, household vehicles, and so on) are all subject to change.&lt;br /&gt;
&lt;br /&gt;
Change over time plays a role in many domains, and is by no means a new research topic. In fact, several approaches for capturing change in OWL have been proposed in the literature. Despite these solutions, we have found that Semantic Web practitioners currently lack clear and precise method for how to apply these approaches to capture change at a domain level, whether reusing an atemporal ontology or developing an ontology from scratch.&lt;br /&gt;
|Aim=The work presented here aims to provide a straightforward, pattern-based guide to implementing a representation of change for any given domain. In particular, we provide consideration for the reuse of atemporal ontologies, as our experience has led us to believe that this is an important design task.&lt;br /&gt;
|Solution=The solution is based on the 4D Fluents Ontology [2], as reinterpreted by Krieger [1].&lt;br /&gt;
&lt;br /&gt;
[1] Krieger, H.U.: Where temporal description logics fail: Representing temporally changing relationships. In: Annual Conference on Arti�cial Intelligence. pp. 249-257. Springer (2008)&lt;br /&gt;
&lt;br /&gt;
[2] Welty, C., Fikes, R., Makarios, S.: A reusable ontology for Fuents in owl. In: Formal Ontology in Information Systems (FOIS). vol. 150, pp. 226-236 (2006)&lt;br /&gt;
|Implementation=A foundational ontology of change is to be imported. Then, based on the foundational classes of TimeVaryingConcept and Manifestation, a simple set of logical design patterns may be applied. A pragmatic guideline to support this process is provided in the accompanying paper submission.&lt;br /&gt;
Several additional logical design patterns are identified, along with descriptions of how they could be employed to provide extended semantics in a representation beyond OWL (e.g. SWRL), should additional reasoning capabilities be required.&lt;br /&gt;
|ReusableComponent=https://w3id.org/icity/iCity-Change&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Example Template}}&lt;br /&gt;
{{Logical OP Reference Template}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13261</id>
		<title>Submissions:Change of Time Varying Entities</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13261"/>
				<updated>2017-07-21T15:30:09Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Logical_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Before-after.png&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP General Template&lt;br /&gt;
|Name=Change: Time Varying Entities&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Description Template&lt;br /&gt;
|Motivation=This work is motivated by a project on urban informatics, iCity \cite{miller2014}, in which our role is to develop an ontology capable of representing the urban system -- both the information that is collected, as well as information that is simulated and analyzed by various research groups. Such an ontology would not only provide valuable integration and inference capabilities for the research groups internally, it would support sharing of the results on the Semantic Web, in particular for reproducibility of simulations and analyses. Owing to its popularity, tool support, and role as the de facto standard for the Semantic Web, OWL was selected as the logical language for the formalization of the ontology. &lt;br /&gt;
To capture the urban domain, the notion of change over time is a critical requirement: the population, family and household structures, transportation networks, and the locations of particular transportation vehicles (buses, household vehicles, and so on) are all subject to change.&lt;br /&gt;
&lt;br /&gt;
Change over time plays a role in many domains, and is by no means a new research topic. In fact, several approaches for capturing change in OWL have been proposed in the literature. Despite these solutions, we have found that Semantic Web practitioners currently lack clear and precise method for how to apply these approaches to capture change at a domain level, whether reusing an atemporal ontology or developing an ontology from scratch.&lt;br /&gt;
|Aim=The work presented here aims to provide a straightforward, pattern-based guide to implementing a representation of change for any given domain. In particular, we provide consideration for the reuse of atemporal ontologies, as our experience has led us to believe that this is an important design task.&lt;br /&gt;
|Solution=The solution is based on the 4D Fluents Ontology [2], as reinterpreted by Krieger [1].&lt;br /&gt;
&lt;br /&gt;
[1] Krieger, H.U.: Where temporal description logics fail: Representing temporally changing relationships. In: Annual Conference on Arti�cial Intelligence. pp. 249-257. Springer (2008)&lt;br /&gt;
&lt;br /&gt;
[2] Welty, C., Fikes, R., Makarios, S.: A reusable ontology for Fuents in owl. In: Formal Ontology in Information Systems (FOIS). vol. 150, pp. 226-236 (2006)&lt;br /&gt;
|Implementation=A foundational ontology of change is to be imported. Then, based on the foundational classes of TimeVaryingConcept and Manifestation, a simple set of logical design patterns may be applied. A pragmatic guideline to support this process is provided in the accompanying paper submission.&lt;br /&gt;
Several additional logical design patterns are identified, along with descriptions of how they could be employed to provide extended semantics in a representation beyond OWL (e.g. SWRL), should additional reasoning capabilities be required.&lt;br /&gt;
|ReusableComponent=https://w3id.org/icity/iCity-Change&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Example Template}}&lt;br /&gt;
{{Logical OP Reference Template}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;br /&gt;
{{Submission to event&lt;br /&gt;
|Event=WOP:2017&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=File:Complex_ex.png&amp;diff=13260</id>
		<title>File:Complex ex.png</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=File:Complex_ex.png&amp;diff=13260"/>
				<updated>2017-07-21T15:10:20Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: An example of a complex precondition implemented with the Activity Specification pattern.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;An example of a complex precondition implemented with the Activity Specification pattern.&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=File:Simple_ex.png&amp;diff=13259</id>
		<title>File:Simple ex.png</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=File:Simple_ex.png&amp;diff=13259"/>
				<updated>2017-07-21T15:09:04Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: A simple example of the Activity Specification pattern.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A simple example of the Activity Specification pattern.&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13258</id>
		<title>Submissions:Change of Time Varying Entities</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13258"/>
				<updated>2017-07-21T14:28:48Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Logical_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Before-after.png&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP General Template&lt;br /&gt;
|Name=Change: Time Varying Entities&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Description Template&lt;br /&gt;
|Motivation=This work is motivated by a project on urban informatics, iCity \cite{miller2014}, in which our role is to develop an ontology capable of representing the urban system -- both the information that is collected, as well as information that is simulated and analyzed by various research groups. Such an ontology would not only provide valuable integration and inference capabilities for the research groups internally, it would support sharing of the results on the Semantic Web, in particular for reproducibility of simulations and analyses. Owing to its popularity, tool support, and role as the de facto standard for the Semantic Web, OWL was selected as the logical language for the formalization of the ontology. &lt;br /&gt;
To capture the urban domain, the notion of change over time is a critical requirement: the population, family and household structures, transportation networks, and the locations of particular transportation vehicles (buses, household vehicles, and so on) are all subject to change.&lt;br /&gt;
&lt;br /&gt;
Change over time plays a role in many domains, and is by no means a new research topic. In fact, several approaches for capturing change in OWL have been proposed in the literature. Despite these solutions, we have found that Semantic Web practitioners currently lack clear and precise method for how to apply these approaches to capture change at a domain level, whether reusing an atemporal ontology or developing an ontology from scratch.&lt;br /&gt;
|Aim=The work presented here aims to fill this gap by providing a straightforward, pattern-based guide to implementing a representation of change for any given domain. In particular, we provide consideration for the reuse of atemporal ontologies, as our experience has led us to believe that this is an important design task.&lt;br /&gt;
|Solution=The solution is based on the 4D Fluents Ontology [2], as reinterpreted by Krieger [1].&lt;br /&gt;
&lt;br /&gt;
[1] Krieger, H.U.: Where temporal description logics fail: Representing temporally changing relationships. In: Annual Conference on Arti�cial Intelligence. pp. 249-257. Springer (2008)&lt;br /&gt;
&lt;br /&gt;
[2] Welty, C., Fikes, R., Makarios, S.: A reusable ontology for Fuents in owl. In: Formal Ontology in Information Systems (FOIS). vol. 150, pp. 226-236 (2006)&lt;br /&gt;
|Implementation=A foundational ontology of change is to be imported. Then, based on the foundational classes of TimeVaryingConcept and Manifestation, a simple set of logical design patterns may be applied. A pragmatic guideline to support this process is provided in the accompanying paper submission.&lt;br /&gt;
Several additional logical design patterns are identified, along with descriptions of how they could be employed to provide extended semantics in a representation beyond OWL (e.g. SWRL), should additional reasoning capabilities be required.&lt;br /&gt;
|ReusableComponent=https://w3id.org/icity/iCity-Change&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Example Template}}&lt;br /&gt;
{{Logical OP Reference Template}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;br /&gt;
{{Submission to event&lt;br /&gt;
|Event=WOP:2017&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13257</id>
		<title>Submissions:Change of Time Varying Entities</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13257"/>
				<updated>2017-07-21T14:27:34Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Logical_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Before-after.png&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP General Template&lt;br /&gt;
|Name=Change Logical OP&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Description Template&lt;br /&gt;
|Motivation=This work is motivated by a project on urban informatics, iCity \cite{miller2014}, in which our role is to develop an ontology capable of representing the urban system -- both the information that is collected, as well as information that is simulated and analyzed by various research groups. Such an ontology would not only provide valuable integration and inference capabilities for the research groups internally, it would support sharing of the results on the Semantic Web, in particular for reproducibility of simulations and analyses. Owing to its popularity, tool support, and role as the de facto standard for the Semantic Web, OWL was selected as the logical language for the formalization of the ontology. &lt;br /&gt;
To capture the urban domain, the notion of change over time is a critical requirement: the population, family and household structures, transportation networks, and the locations of particular transportation vehicles (buses, household vehicles, and so on) are all subject to change.&lt;br /&gt;
&lt;br /&gt;
Change over time plays a role in many domains, and is by no means a new research topic. In fact, several approaches for capturing change in OWL have been proposed in the literature. Despite these solutions, we have found that Semantic Web practitioners currently lack clear and precise method for how to apply these approaches to capture change at a domain level, whether reusing an atemporal ontology or developing an ontology from scratch.&lt;br /&gt;
|Aim=The work presented here aims to fill this gap by providing a straightforward, pattern-based guide to implementing a representation of change for any given domain. In particular, we provide consideration for the reuse of atemporal ontologies, as our experience has led us to believe that this is an important design task.&lt;br /&gt;
|Solution=The solution is based on the 4D Fluents Ontology [2], as reinterpreted by Krieger [1].&lt;br /&gt;
&lt;br /&gt;
[1] Krieger, H.U.: Where temporal description logics fail: Representing temporally changing relationships. In: Annual Conference on Arti�cial Intelligence. pp. 249-257. Springer (2008)&lt;br /&gt;
&lt;br /&gt;
[2] Welty, C., Fikes, R., Makarios, S.: A reusable ontology for Fuents in owl. In: Formal Ontology in Information Systems (FOIS). vol. 150, pp. 226-236 (2006)&lt;br /&gt;
|Implementation=A foundational ontology of change is to be imported. Then, based on the foundational classes of TimeVaryingConcept and Manifestation, a simple set of logical design patterns may be applied. A pragmatic guideline to support this process is provided in the accompanying paper submission.&lt;br /&gt;
Several additional logical design patterns are identified, along with descriptions of how they could be employed to provide extended semantics in a representation beyond OWL (e.g. SWRL), should additional reasoning capabilities be required.&lt;br /&gt;
|ReusableComponent=https://w3id.org/icity/iCity-Change&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Example Template}}&lt;br /&gt;
{{Logical OP Reference Template}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;br /&gt;
{{Submission to event&lt;br /&gt;
|Event=WOP:2017&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13256</id>
		<title>Submissions:Change of Time Varying Entities</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13256"/>
				<updated>2017-07-21T13:49:04Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Logical_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Before-after.png&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP General Template&lt;br /&gt;
|Name=Change Logical OP&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Description Template&lt;br /&gt;
|Motivation=This work is motivated by a project on urban informatics, iCity \cite{miller2014}, in which our role is to develop an ontology capable of representing the urban system -- both the information that is collected, as well as information that is simulated and analyzed by various research groups. Such an ontology would not only provide valuable integration and inference capabilities for the research groups internally, it would support sharing of the results on the Semantic Web, in particular for reproducibility of simulations and analyses. Owing to its popularity, tool support, and role as the de facto standard for the Semantic Web, OWL was selected as the logical language for the formalization of the ontology. &lt;br /&gt;
To capture the urban domain, the notion of change over time is a critical requirement: the population, family and household structures, transportation networks, and the locations of particular transportation vehicles (buses, household vehicles, and so on) are all subject to change.&lt;br /&gt;
&lt;br /&gt;
Change over time plays a role in many domains, and is by no means a new research topic. In fact, several approaches for capturing change in OWL have been proposed in the literature. Despite these solutions, we have found that Semantic Web practitioners currently lack clear and precise method for how to apply these approaches to capture change at a domain level, whether reusing an atemporal ontology or developing an ontology from scratch.&lt;br /&gt;
|Aim=The work presented here aims to fill this gap by providing a straightforward, pattern-based guide to implementing a representation of change for any given domain. In particular, we provide consideration for the reuse of atemporal ontologies, as our experience has led us to believe that this is an important design task.&lt;br /&gt;
|Solution=The solution is based on the 4D Fluents Ontology [2], as reinterpreted by Krieger [1].&lt;br /&gt;
&lt;br /&gt;
[1] Krieger, H.U.: Where temporal description logics fail: Representing temporally changing relationships. In: Annual Conference on Arti�cial Intelligence. pp. 249-257. Springer (2008)&lt;br /&gt;
&lt;br /&gt;
[2] Welty, C., Fikes, R., Makarios, S.: A reusable ontology for Fuents in owl. In: Formal Ontology in Information Systems (FOIS). vol. 150, pp. 226-236 (2006)&lt;br /&gt;
|Implementation=A foundational ontology of change is to be imported. Then, based on the foundational classes of TimeVaryingConcept and Manifestation, a simple set of logical design patterns may be applied. A pragmatic guideline to support this process is provided in the accompanying paper submission.&lt;br /&gt;
Several additional logical design patterns are identified, along with descriptions of how they could be employed to provide extended semantics in a representation beyond OWL (e.g. SWRL), should additional reasoning capabilities be required.&lt;br /&gt;
|ReusableComponent=https://w3id.org/icity/iCity-Change&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Example Template}}&lt;br /&gt;
{{Logical OP Reference Template}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13255</id>
		<title>Submissions:Change of Time Varying Entities</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=Submissions:Change_of_Time_Varying_Entities&amp;diff=13255"/>
				<updated>2017-07-21T13:45:43Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: This pattern supports the implementation of a representation of change for any given domain.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Logical_OP_Proposal_toolbar}}&lt;br /&gt;
{{Graphical representation header}}&lt;br /&gt;
{{Graphical representation&lt;br /&gt;
|ImageName=Before-after.png&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP General Template&lt;br /&gt;
|Name=Change Logical OP&lt;br /&gt;
|SubmittedBy=MeganKatsumi&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Description Template&lt;br /&gt;
|Motivation=This work is motivated by a project on urban informatics, iCity \cite{miller2014}, in which our role is to develop an ontology capable of representing the urban system -- both the information that is collected, as well as information that is simulated and analyzed by various research groups. Such an ontology would not only provide valuable integration and inference capabilities for the research groups internally, it would support sharing of the results on the Semantic Web, in particular for reproducibility of simulations and analyses. Owing to its popularity, tool support, and role as the de facto standard for the Semantic Web, OWL was selected as the logical language for the formalization of the ontology. &lt;br /&gt;
To capture the urban domain, the notion of change over time is a critical requirement: the population, family and household structures, transportation networks, and the locations of particular transportation vehicles (buses, household vehicles, and so on) are all subject to change.&lt;br /&gt;
&lt;br /&gt;
Change over time plays a role in many domains, and is by no means a new research topic. In fact, several approaches for capturing change in OWL have been proposed in the literature. Despite these solutions, we have found that Semantic Web practitioners currently lack clear and precise method for how to apply these approaches to capture change at a domain level, whether reusing an atemporal ontology or developing an ontology from scratch. &lt;br /&gt;
|Aim=The work presented here aims to fill this gap by providing a straightforward, pattern-based guide to implementing a representation of change for any given domain. In particular, we provide consideration for the reuse of atemporal ontologies, as our experience has led us to believe that this is an important design task. &lt;br /&gt;
|Solution=The solution is based on the 4D Fluents Ontology [2], as reinterpreted by Krieger [1].&lt;br /&gt;
&lt;br /&gt;
[1] Krieger, H.U.: Where temporal description logics fail: Representing temporally changing relationships. In: Annual Conference on Arti�cial Intelligence. pp. 249-257. Springer (2008)&lt;br /&gt;
&lt;br /&gt;
[2] Welty, C., Fikes, R., Makarios, S.: A reusable ontology for Fuents in owl. In: Formal Ontology in Information Systems (FOIS). vol. 150, pp. 226-236 (2006)&lt;br /&gt;
|Implementation=A foundational ontology of change is to be imported. Then, based on the foundational classes of TimeVaryingConcept and Manifestation, a simple set of logical design patterns may be applied. A pragmatic guideline to support this process is provided in the accompanying paper submission.&lt;br /&gt;
Several additional logical design patterns are identified, along with descriptions of how they could be employed to provide extended semantics in a representation beyond OWL (e.g. SWRL), should additional reasoning capabilities be required.&lt;br /&gt;
}}&lt;br /&gt;
{{Logical OP Example Template}}&lt;br /&gt;
{{Logical OP Reference Template}}&lt;br /&gt;
{{Additional information header}}&lt;br /&gt;
&lt;br /&gt;
{{Scenarios about me}}&lt;br /&gt;
{{Reviews about me}}&lt;br /&gt;
{{Modeling issues about me}}&lt;br /&gt;
{{My references}}&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	<entry>
		<id>http://ontologydesignpatterns.org/index.php?title=File:Before-after.png&amp;diff=13254</id>
		<title>File:Before-after.png</title>
		<link rel="alternate" type="text/html" href="http://ontologydesignpatterns.org/index.php?title=File:Before-after.png&amp;diff=13254"/>
				<updated>2017-07-21T13:35:26Z</updated>
		
		<summary type="html">&lt;p&gt;MeganKatsumi: Example definition of Vehicle before and after the application of the logical design patterns for capturing change.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Example definition of Vehicle before and after the application of the logical design patterns for capturing change.&lt;/div&gt;</summary>
		<author><name>MeganKatsumi</name></author>	</entry>

	</feed>