In the current model the objects define their own update policies with respect to RDF harvesting. The vast majority of objects define a policy that the object is immutable. However this is certainly not the case with respect to the objects behaviour nor the database persistence policy. Virtually all of the object may be updated. This will allow for cases where objects are not correctly synchronized with the RDF system and thus both persistence mechanisms will be out of sync. This could be as simple as a misspelling of a name.

To correct this problem objects that need to be correctly synchronized need have valid timestamp behaviour implemented. The method for determining if an object is immutable should also be reviewed.

Note: Once we go live the timestamp information will be lost. So a post release fix would also need to included a complete reharvest with a different set of rules or reinitialization.