| Re: [viatra-dev] IncQuery-related change in the concrete syntax of the CEP Language |
On 18 Jan 2015 at 00:20:39, David, Istvan (davidi@xxxxxxxxxxxxxx) wrote:
I see your point in general, however replacing “IQPatternEvent” with “ModelChangeEvent” might just as well be misleading. “IQPatternEvent” represents a “change in the result set of a query” event, which is only indirectly related to model changes. Result set changes can even be induced in scenarios when models are not manipulated at all, e.g. if a new resource is loaded into a resourceset (on which a query has been initialized with the ResourceSet scope). Further, “ModelChangeEvent”, to me, represents an event on a lower level of abstraction, i.e. the level of elementary model changes (notifications: ADD, REMOVE, etc); which, by the way, could also be interesting for CDTs. So, if we wish to direct the development of the VIATRA-CEP engine towards CDTs, one could argue that instead of renaming the construct, we actually need to extend detectable change events to 1) atomic change operations (“ModelChangeEvent”) 2) compound changes that can either be 2a) complete transactions (“ModelChangeTransactionEvent”) or 2b) query result set changes (“QueryResultChangeEvent”). cheers -- István Ráth Research Fellow Fault Tolerant Systems Research Group Budapest University of Technology and Economics http://inf.mit.bme.hu/en/members/rath rath@xxxxxxxxxx |