Commit 3de28745 authored by Matthias Bueker's avatar Matthias Bueker
Browse files

Added my key points for the WP "Temporal Aspects"

parent dcc2ded5
Pipeline #986 passed with stage
in 14 seconds
......@@ -64,11 +64,41 @@ WP DM-Ontology - Develop ontology to establish relations between entities
==== Language Core
===== Temporal Aspects (TC_Temporal)
(M. Büker, R. Heidtman, Y. Hollander, H. Hungar
Goals:
* Also consider parameters and their bindings and resolutions times
* Events, sampling of variables/ properties
* Support for 1.0 and 1.1 runtime execution model to the extent possible
* Relationship to temporal logic languages
===== WP Temporal Aspects (TC_Temporal)
Involved: Matthias Büker, Rich Heidtman, Yoav Hollander, Hardi Hungar
The following goals are pursued by this work package:
====== Substantiate and integrate concept of events
* Refine definitions of events (if needed)
* How exactly can conditions be used to define events (raising/falling edge, etc)?
* In which language are events and conditions are specified? (see also relationship to temporal logic langauges)
====== Substantiate definition and semantics of phases
* Refine definition of phases if needed
* How is the start, end, duration,... of a phase is determined/defined when not using events?
* How can events be used to define the start and end of a phase?
* How do we handle/avoid ambiguity between the different ways to specify phase start/end conditions?
* How do we specify semantics of phases in general?
* Check integration of modifiers into phase concept and re-iterate if needed
====== Substantiate temporal composition operators
* Substantiate synchronization of mixed phases by using events
* Are there other cases where events play a role for temporal composition operators?
* How do we specify semantics of temporal composition operators in general?
====== Sampling of variables and properties
* ?
====== Integrate parameters and their bindings and resolution times into temporal aspect
* How can parameters be used in the context of the temporal aspects of the language (phases, temporal composition aspects)
====== Support OSC 1.0 and 1.1 runtime execution model to the extent possible
* How do we connect the two worlds of a declarative language and an execution/command-like way to specify behavior (OSC 1.0)?
** Should it be possible to mix both ways of specification in an arbitrary manner? How exactly should this look like? Is this still intuitive/readable?
** Or should we separate these two styles somehow (language sets)?
** How can we translate the temporal apsects of the OSC 1.0 language into OSC 2.0?
====== Relationship to temporal logic languages
* In which contexts should it be possible to use temporal logic langauges? Only to specify conditions for events?
* Do we pre-define allowed languages or do we allow arbitrary langauges? How should this exactly work?
\ No newline at end of file
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment