Hi all,
I'd like to know your opinion about an IncQuery-specific element in the VIATRA Event Processing Language. The language currently distinguishes between three types of events: atomic, complex and the ones generated by an IncQuery engine when a graph pattern is found or lost. The latter type of events is a specific subtype of atomic events and is currently denoted by the
IQPatternEvent keyword.
Now, this notation might be a bit misleading. The idea behind this specific event type is to enable the processing of events depicting a model change. The fact that we implemented this feature via IncQuery, is just a technical detail from the user's point of view. Moreover, according to the original idea, the API should allow the integration of custom mediating techniques between an underlying model and the CEP engine. That is, the user should be able to replace IncQuery with an arbitrary query engine. (Which is unlikely of course. :) )
Therefore, I think this element should be renamed to either ModelEvent or maybe ModelChangeEvent. I prefer the former one, since terms like "change", "evolution", "modification", etc are often used interchangeably and we might end up with another misleading keyword.
What do you think?
FYI: an overview on the language is available
here. (And
this is the section on IQPatternEvents in particular.)
Thanks for your feedback,
Istvan
