Difference between revisions of "Editorial Update/Renumbering"
| Line 13: | Line 13: | ||
This was achieved by inserting new <code><ukl:P1group></code> tagging for reg. 6B and new <code><ukl:P1></code> tagging was inserted into this (using the Element List). The existing content of reg. 6A was copied into this new tagging (via straightforward copy and paste of everything within the <code><ukl:P1para></code> tagging). The number 6A was copied from the amending provision and inserted into the number tagging using the update task in the Task Manager to generate the square brackets and annotation. | This was achieved by inserting new <code><ukl:P1group></code> tagging for reg. 6B and new <code><ukl:P1></code> tagging was inserted into this (using the Element List). The existing content of reg. 6A was copied into this new tagging (via straightforward copy and paste of everything within the <code><ukl:P1para></code> tagging). The number 6A was copied from the amending provision and inserted into the number tagging using the update task in the Task Manager to generate the square brackets and annotation. | ||
| − | The new reg. 6A was then substituted for the old reg. 6A using the insertion task to generate the square brackets and correct annotation for that task | + | The new reg. 6A was then substituted for the old reg. 6A using the insertion task to generate the square brackets and correct annotation for that task: |
| + | |||
[[File: Renumbering_1a.png |link=]] | [[File: Renumbering_1a.png |link=]] | ||
| − | The annotation for the original insertion of reg. 6A was also amended to say that reg. 6A was subsequently renumbered as reg. 6B (so this information is then visible both in the old reg. 6A at the previous PiT and also in the new reg. 6B at the current PiT) | + | |
| + | The annotation for the original insertion of reg. 6A was also amended to say that reg. 6A was subsequently renumbered as reg. 6B (so this information is then visible both in the old reg. 6A at the previous PiT and also in the new reg. 6B at the current PiT): | ||
| + | |||
[[File: Renumbering_1b.png |link=]] | [[File: Renumbering_1b.png |link=]] | ||
| + | |||
In this example, there was a new provision inserted for the provision that was renumbered. However, if there had been no insertion of a new provision in this way, the original provision should have been repealed using the same task so both the omitted old provision and the renumbered new provision had the same annotation. | In this example, there was a new provision inserted for the provision that was renumbered. However, if there had been no insertion of a new provision in this way, the original provision should have been repealed using the same task so both the omitted old provision and the renumbered new provision had the same annotation. | ||
Revision as of 14:53, 4 February 2021
This is a draft version
Renumbering whole provisions
When a whole provision is renumbered, it should be treated as though the original provision is omitted and a new provision (with exactly the same text) is inserted. This will maintain the correct URL for each provision and so preserve the continuity of the URLs.
For example, S.I. 2020/150 reg. 6A was renumbered as reg. 6B on 25/12/2020 and a new reg. 6A was inserted. This resulted in the following URLs:
https://www.legislation.gov.uk/nisr/2020/150/regulation/6A
https://www.legislation.gov.uk/nisr/2020/150/regulation/6B
This was achieved by inserting new <ukl:P1group> tagging for reg. 6B and new <ukl:P1> tagging was inserted into this (using the Element List). The existing content of reg. 6A was copied into this new tagging (via straightforward copy and paste of everything within the <ukl:P1para> tagging). The number 6A was copied from the amending provision and inserted into the number tagging using the update task in the Task Manager to generate the square brackets and annotation.
The new reg. 6A was then substituted for the old reg. 6A using the insertion task to generate the square brackets and correct annotation for that task:
The annotation for the original insertion of reg. 6A was also amended to say that reg. 6A was subsequently renumbered as reg. 6B (so this information is then visible both in the old reg. 6A at the previous PiT and also in the new reg. 6B at the current PiT):
In this example, there was a new provision inserted for the provision that was renumbered. However, if there had been no insertion of a new provision in this way, the original provision should have been repealed using the same task so both the omitted old provision and the renumbered new provision had the same annotation.
Renumbering paragraphs within a Schedule
To renumber a paragraph within a Schedule, new <ukl:P1> tags should be inserted for the new renumbered provision using the Element List.
The number of the renumbered paragraph should then be copied and inserted into the number tags using the update task to get the annotation. The brackets should remain around the new paragraph number.
Next, the <ukl:P1para> tagging containing all the content from the original paragraph should be copied and pasted into the new renumbered paragraph.
Finally, the same task should be used to repeal the original paragraph so that both the omitted old paragraph and the renumbered new paragraph have the same annotation.
Renumbering sub-provisions
This often involves renumbering a whole provision as a sub-provision and then inserting a new sub-provision (or sub-provisions) into the provision.
New <ukl:P2> tagging for the newly renumbered sub-provision should be inserted in the appropriate position within the existing tagging of the provision (i.e. within the <ukl:P1para> tagging), then the number of the renumbered sub-provision is copied from the amending provision and inserted into the number tags using the update task to get the annotation. The brackets should remain around the new sub-provision number:
The content of the original provision or sub-provision should be copied into <ukl:P2para> tagging of the newly renumbered sub-provision:
Note: the complete tagging of the whole provision has not been included in this screenshot.
Further sub-provisions can then be inserted in the usual way according to the update task.
Example
2017 c. 3 s. 50 renumbered as s. 50(1) and new s. 50(2) inserted
