With respect to time and space, "point in time" and "location" can be regarded as "essence", respectively (Sowa 2000). In the English language, the preposition "at" is used if essential spatial or temporal information is expressed. "At" thus can be seen as a tag to mark expressed essential spatial or temporal information.
Sometimes, when we give spatial or temporal information, we express something which is more complex. For example, we want to relate two points in time or two locations to each other. In English, we use prepositions like "in front of", "behind", "before", "after" and others to specify the relation in question. I will not elaborate on this, here, but I would like to underline that in C2SIM points in time and locations are not sufficient to express even core information. We also need time spans and routes. Luckily, we already have "StartingTime" and "EndingTime" to be able to express time spans. (In order to be consistent with the ontology, I would like to suggest to add "PointInTime"-tags to the schema: 2018-03-02T09:00:00Z .) The main point I would like to stress here, however, is that we need route. Routes are needed even for the most simplest orders like moving orders. If one can only give one location in such an order, that location is to be interpreted as destination and the tasker loses the control to determine the route the taskee has to follow. I would like to argue for routes which consists of a number of locations (at least one). If there is only one location that one is the destination, all other locations constitute the path towards the location. The locations have to be given in the correct sequence, of course. This then may look like the following: ...............
(For some applications, e.g. applications with UAVs, it of course would be .........).
Ulrich says:
With respect to time and space, "point in time" and "location" can be regarded as "essence", respectively (Sowa 2000). In the English language, the preposition "at" is used if essential spatial or temporal information is expressed. "At" thus can be seen as a tag to mark expressed essential spatial or temporal information. Sometimes, when we give spatial or temporal information, we express something which is more complex. For example, we want to relate two points in time or two locations to each other. In English, we use prepositions like "in front of", "behind", "before", "after" and others to specify the relation in question. I will not elaborate on this, here, but I would like to underline that in C2SIM points in time and locations are not sufficient to express even core information. We also need time spans and routes. Luckily, we already have "StartingTime" and "EndingTime" to be able to express time spans. (In order to be consistent with the ontology, I would like to suggest to add "PointInTime"-tags to the schema:2018-03-02T09:00:00Z ... ... ... ... ... ... ...