DataChange even is inconsistent with changes in the data store via Restconf

I'm trying to provide a configuration facility to my bundle, where the configuration state can be updated over the Restconf interface, and my code reacts to those changes via onDataChange events.

I would like to raise that the current DataChange events are quite counter-intuitive to use. While practically it is possible to deduce what happened, it would be more convenient if the reported maps/sets contained only what their name suggests.

1) When a new configuration element is created, it appears both as "created" and "updated". It would be more convenient if created elements would only be reported as "created".

2) When a configuration element is updated with identical data (i.e., did not change), it is still reported as "updated". It would be useful if such identical updates were filtered by the data store internals, and would not be reported to the listeners.

3) When a configuration element is deleted, it is not reported as "removed"; it only appears among the "original" elements. It would be useful if was contained among the "removed" elements as well.

I have attached a bundle which can be used to reproduce what happens. Check the readme.txt file for details.