Issue 98031 | Editor: Erik Sandewall | [postscript] | ||
29.3.1998 |
|
|||
Today | |||||||||||||||||||||||||||||||||
Today: Ray Reiter and John McCarthy join the debate about the ontology of time.
| |||||||||||||||||||||||||||||||||
Debates | |||||||||||||||||||||||||||||||||
Ontologies for timeRay Reiter:During all the years that the debate has raged about time points vs intervals, we devotees of the sitcalc have never seen it as an issue. Here's why I think this is so.
In the sitcalc, a fluent (
In the sitcalc with explicit time, the first might become
meaning that as a result of the action history consisting of first
switching off the light at time 1.41, then switching on the light at time 3.14,
the light will be on. Notice that there is no way of expressing the claim that
the light is, or is not on at time 3.14 (or 3.5), independently of the
situation leading up to this time. On
the other hand, time based formalisms do allow one to write Now, one could rightly object to the above account because it provides only for fluent truth values at discrete time points, namely at the action occurrence times. So we are tempted to understand
to mean that the light is on at time 3.14, but it tells us nothing about time 3.5 say. This is particularly bad for (functional) fluents that vary continuously with time, for example, the location of a falling object. To handle this, introduce a time argument for fluents, in addition to their situation argument. For the light, one can write:
Here, An instance of this would be
Here we have committed to the light being on at exactly the time of the switchOn action, and forever thereafter, relative to the history
without contradiction. This seems to be precisely the point at which purely time-based formalisms run into difficulties, and the sitcalc version of this problem illustrates the role that explicit situation arguments play in resolving these difficulties. Now, we can axiomatize falling objects:
John McCarthy:When my car accelerates, there is a time point at which it passes 65 miles per hour. It is awkward to describe this point in a language not providing for time points.
|