Bruno,
It is a bit tricky because in the general case, the form can really be messed up if the version of the data doesn't correspond to the form definition. And you wouldn't want it to be up to the user (via a URL parameter) to make that choice. It really should be the administrator's decision.
There are two possibilities:
1. When publishing a version of a form, be able to overwrite the previous form version. The administrator must be very careful to publish a version of the form definition which is compatible with existing data if any. The good news is that this is already done in 4.6.
2. Have some data migration feature, so the data can be associated, and possibly migrated, to the new form definition. We have an RFE here for very basic migration:
https://github.com/orbeon/orbeon-forms/issues/1523Migration is not yet implemented yet though.
What do you think?
-Erik
Locked
