You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the version 7 is closed and frozen and the specifications don't state anything about the compulsory of the reversion, I wish to inform that I will never revert back just because my partner has reverted back his IIA, as claimed by the DeleteModifyScenarios.xlsx
Scenario: a description of how things might happen in the future
(please note: might happen and not must happen)
IIA Specifications - Important rules: To modify an IIA which has been mutually approved, HEIs SHOULD take a snapshot of the last approved version to be able to revert to it if they don't conclude a new approved version of the agreement
"To be able to revert" is a free choice, not a mandatory requirement
And I add two more considerations about the fact that specifications suggest to take a snapshot of the last approved version before starting an amendment.
This means that if I receive two approvals in sequence (because I changed my IIA twice), my last snapshot represents my IIA after the first new approval and not the IIA mutually approved
In order to have something useful and reliable, the snapshot must be taken only, and I stress only, when we reach the mutual approval. And this is essential even for the XSLT computation in switching from version 6 to 7, but the specification for approval don't say anything about this, only that "A snapshot of the approved v6 IIA is needed".It doesn't say when we must take the snapshot.
All that said, I think that if you wish to make the reversion mandatory, we should wait for version 8.
Version 7 is frozen.
The text was updated successfully, but these errors were encountered:
I guess no one is bound by the scenarios list. Those are just ideal representation of the complex specification. Or probably drafted based on how a particular system works.
We go by specifications. If something is not in specification, that is not relevant for us.
I guess no one is bound by the scenarios list. Those are just ideal representation of the complex specification. Or probably drafted based on how a particular system works. We go by specifications. If something is not in specification, that is not relevant for us.
Since the version 7 is closed and frozen and the specifications don't state anything about the compulsory of the reversion, I wish to inform that I will never revert back just because my partner has reverted back his IIA, as claimed by the DeleteModifyScenarios.xlsx
(please note: might happen and not must happen)
"To be able to revert" is a free choice, not a mandatory requirement
And I add two more considerations about the fact that specifications suggest to take a snapshot of the last approved version before starting an amendment.
All that said, I think that if you wish to make the reversion mandatory, we should wait for version 8.
Version 7 is frozen.
The text was updated successfully, but these errors were encountered: