That's not what I meant.  The cr2 is altered to accomodate additions to Poser but it is not "re-structured".  You would know that since DSON for Poser uses the customData declaration.

Obviously, if you try to use technology made for Poser 9 in Poser 4 it isn't going to work.  But chances are that something will still load because Poser is designed to ignore what it doesn't understand.  You'll get a Roxie but it's not really going to bend correctly because that tech isn't available in that version.  That was a bit silly, honestly.

If you rig a dress for V4 in Poser Pro 2014, it still works in Poser 4 or whatever, as long as you design using the tech that Poser 4 understands.  Just because the cr2 was made in Pro 2014 is irrelevant.  The only thing that needs to be changed is the version number of the cr2.

However, for example, you decide to put everything on .duf and remove the capability to produce a .dsa (or the number of variants .dsb, dse, whatnot), you've lost those using DS 3.1 (for whatever reason they still might be using it).  Sort of would force you to stay on the current version, wouldn't it? ;)

.