You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Continuation of a discussion started in the old inference engine repo: how can we best model "temporal entities", i.e. entities that subset the time dimension, like "harvest season" and "sowing season" or "wet season" and "dry season".
The problem with "entity/event" is that they want to load data, which does not make sense or is not required in a definition of "spring". Having a different block can solve this issue because the inference engine can be designed to add another rule/switch, in addition to the idea that something like "spring" or "harvest season" is conceptually not an "entity" or an "event". (Please correct, if this summary was not sufficient or something is missing).
Other options could be:
Dimension
Domain (e.g., consider domains in database systems, which are similar (but not equal)
...
FYI: semantique is updated such that the translator function of an ontology is aware of the current "self" object in a processing chain at the moment the translator is called. Hence, a different block is not needed anymore from the technical perspective. Does of course not take away the naming issue.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Continuation of a discussion started in the old inference engine repo: how can we best model "temporal entities", i.e. entities that subset the time dimension, like "harvest season" and "sowing season" or "wet season" and "dry season".
All reactions