* advantage over proposal II: this can easily be extended to the case where a resource consists of multiple LDAP objects by concatenating the different <code>csn</code> entries in a reproducible fashion
* disadvantage over proposal I: we have to read from the LDAP again before we can write
* instead of the <code>csn</code> one could use the <code>modifyTimestamp</code> instead, but it seems that this attribute has a lower resolution while <code>csn</code> features microsecond resolution and is also used for replication and it can therefore be assumed to be unique.
= Implementation proposal II =