i didn't understand why this property has its onParentVersion set to IGNORE. For example, let N be a versionable node and have the nt:resource node type. Suppose N holds a file F with lastModified holding the value A. Now, I check in a new version of N and this property wont be stored in VN (version of N stored in your version history). Let's make N hold the same file F (with lastModified holding the value B) and after restoring VN. How jcr:lastModified has its onParentVersion set to IGNORE, this property of the current N will be remain and not be removed, that is, the first version of F had its lastModified property with the value A, and now has this property set to B, the value of the second version. Does it make sense?
Thanks in advance
