By a ‘successive version’ we mean a new version that replaces an earlier version. A new version of a provision is created whenever the text is amended. Earlier versions are retained and the user may navigate through the amendment history of the provision. The first version will usually show the provision in the form in which it was enacted (or the form in which it had effect at the relevant basedate if that was later).
You can find out whether there is more than one version of a provision or other level of division by viewing the table of Attributes.
New versions are not usually created for modifications and other effects that do not alter the text. Occasional exceptions are made to this policy. For example, a provision is modified at frequent intervals by statutory instruments and each such instrument revokes the previous one. The provision would rapidly become overburdened with redundant annotations. In these circumstances, a new version of the provision would be made each time it is modified.
New versions may also be created for higher levels of division if there is a change to the text operating at that level (for example, an amendment to the text of a Part heading). New versions of a higher level are also generated if there is a change to the structure below it. So if, for example, a wholly new section is inserted under an existing cross-heading, a new version will be created of that cross-heading level of division.
|
|
NOTE that when a higher-level division is wholly substituted, the version history starts again from version 1, the start date of which will be the date on which the substitution took effect. This means that if, for example, a whole Schedule is replaced, the old Schedule can not be reached from the new one by navigation via the attributes table of the new Schedule. The simplest way to reach the old Schedule in this case would be to make an ‘advanced search’ specifying an ‘as at’ date before the substitution took effect |
See also
Parent topic
