Difference between revisions of "Editorial Update/Limited Extent Amendments"
| Line 25: | Line 25: | ||
If, during update, you find that your limited extent amendment has already been made for another jurisdiction at an earlier PiT, you will need to amend the original limited extent amendment as follows: | If, during update, you find that your limited extent amendment has already been made for another jurisdiction at an earlier PiT, you will need to amend the original limited extent amendment as follows: | ||
| − | If the amendment is still limited extent after your amendment (i.e. the amendment has already been made for E+W and your amendment is for N.I., but the full extent of the provision is E+W+S+N.I. (and the amendment hasn't yet been made for S.)), then you will need to: | + | * If the amendment is still limited extent after your amendment (i.e. the amendment has already been made for E+W and your amendment is for N.I., but the full extent of the provision is E+W+S+N.I. (and the amendment hasn't yet been made for S.)), then you will need to: |
1. Leave the retained text from the original limited extent amendment intact but remember to amend the [[Editorial_Update/XMetaL_and_XML_tagging#Extent_attribute|Extent attribute]] of the amendment tagging to include the new jurisdiction; and | 1. Leave the retained text from the original limited extent amendment intact but remember to amend the [[Editorial_Update/XMetaL_and_XML_tagging#Extent_attribute|Extent attribute]] of the amendment tagging to include the new jurisdiction; and | ||
2. Merge the annotation details in such way that the new details don't flow back into the previous versions (see example below). | 2. Merge the annotation details in such way that the new details don't flow back into the previous versions (see example below). | ||
| − | If this amendment means that that the original amendment is now in wholly in force for all jurisdictions, you will need to: | + | * If this amendment means that that the original amendment is now in wholly in force for all jurisdictions, you will need to: |
1. Fully carry out the original amendment (i.e. remove any retained text), as the old text will no longer be needed for any jurisdictions; | 1. Fully carry out the original amendment (i.e. remove any retained text), as the old text will no longer be needed for any jurisdictions; | ||
2. Amend the [[Editorial_Update/XMetaL_and_XML_tagging#Extent_attribute|Extent attribute]] of the amendment tagging to include the new jurisdiction; and | 2. Amend the [[Editorial_Update/XMetaL_and_XML_tagging#Extent_attribute|Extent attribute]] of the amendment tagging to include the new jurisdiction; and | ||
| − | + | 3. Merge the annotation details in such way that the new details don't flow back into the previous versions (see example below). | |
===Example: 2004 c. 33, s.237(2)(b)(ii)=== | ===Example: 2004 c. 33, s.237(2)(b)(ii)=== | ||
Revision as of 13:49, 3 December 2021
Overview
Limited extent amendments occur when the amendment to be applied has a narrower geographical extent (or territorial application) than that of the amended provision. We have to make sure that we don’t remove or replace text that still applies in other jurisdictions.
Whether or not an amendment is limited extent or not will have been established prior to update, through extent research. The editorial system will compare the affecting and affected extent when the update is allocated. Where a limited extent amendment is found a warning message will appear on the ‘Update Details’ page and the extents for the relevant amendments will appear in red.
XMetaL has special amendment options for limited extent amendments. These will produce slightly different results than for standard amendments. If you attempt to use the standard menu options when carrying out a limited extent amendment XMetaL will prompt you to use the Limited Extent Menu options.
Limited Extent Insertions:
A limited extent insertion will look exactly the same as a standard insertion. The only difference is that the extent information will be added to the XML. For an insertion of words or a sub-provision, this means that the extent information will be included in the Extent attribute of the ukl:Addition element. For an insertion of a whole provision (and higher level insertions), as well as including the extent in the extent attribute of the ukl:Addition element, the extent will also be included in the RestrictExtent attribute of the relevant provision. This information will be used by the website to identify the extent of the amendment. The annotation will also include a reference to the extent.
Limited Extent Repeals:
Limited Extent Repeals will not result in the text being replaced by a dotted line. Instead the repeal text will be retained, enclosed by brackets and ukl:Repeal tags, with an F-note reference appearing immediately after the opening bracket. As with insertions, the extent of the amendment will be added to the XML (i.e. the Extent attribute of the ukl:Repeal tags) and the annotation will include reference to the extent.
Limited Extent Substitutions:
Limited Extent Substitutions will result in both the new and the old text being retained side by side. Both sets of text will be enclosed by brackets with an F-note reference appearing immediately after each opening bracket. The old text will be enclosed by ukl:Repeal tags and the new ukl:Addition tags. As with repeals and insertions, the extent will be added to the XML (i.e. the Extent attribute of the ukl:Repeal and code>ukl:Addition tags, and the RestrictExtent attribute of the substituted provision, where relevant) and the annotation will include reference to the extent.
See more on the Extent and RestrictExtent attributes on the XMetaL and XML tagging page.
Making changes to an existing limited extent amendment when the same amendment is being carried out for another jurisdiction
If, during update, you find that your limited extent amendment has already been made for another jurisdiction at an earlier PiT, you will need to amend the original limited extent amendment as follows:
- If the amendment is still limited extent after your amendment (i.e. the amendment has already been made for E+W and your amendment is for N.I., but the full extent of the provision is E+W+S+N.I. (and the amendment hasn't yet been made for S.)), then you will need to:
1. Leave the retained text from the original limited extent amendment intact but remember to amend the Extent attribute of the amendment tagging to include the new jurisdiction; and 2. Merge the annotation details in such way that the new details don't flow back into the previous versions (see example below).
- If this amendment means that that the original amendment is now in wholly in force for all jurisdictions, you will need to:
1. Fully carry out the original amendment (i.e. remove any retained text), as the old text will no longer be needed for any jurisdictions; 2. Amend the Extent attribute of the amendment tagging to include the new jurisdiction; and 3. Merge the annotation details in such way that the new details don't flow back into the previous versions (see example below).
Example: 2004 c. 33, s.237(2)(b)(ii)
On 2/12/2019, there was a limited extent limited extent substitution of words for E.W. and this was followed by the same amendment being made for N.I. on 13.1.2020:
On 1/6/2021, there was a further substitution of exactly the same words for S., so that the substitution of words was now wholly in force for all jurisdictions. The retained text could therefore be removed at this PiT and the annotation was amended as follows:
1. Because the substitution was now complete for all jurisdictions, we removed the retained text from the original limited extent substitution, i.e. the ukl:Repeal tags and words they contained were deleted after checking the provision out in XMetaL:
This left just the substituted text (within the <codeukl:Addition</code tagging) :
2. Next, we needed to add the details of the S. substitution to the existing annotation. To prevent this from flowing back into the previous versions of the provision (which would happen if we just merged the text for S. substitution into the existing annotation), it had to be done in a special way, using the following method:
a) Insert a new commentary in front of the existing ukl:Addition opening bracket (having selected the relevant task in the Task Manager so that the correct annotation text is generated):
b) Copy the text of the existing annotation to the beginning of the new annotation as plain text (this can be copied from the website Preview of the provision):
c) Edit the annotation to merge the text for the various jurisdictions. In this example, the words “Words in s. 237(2)(b)(ii) substituted “ were deleted from before “(S.)” and replaced with “; and”. The word ”and” before “(N.I.)” was also replaced with a semicolon. You should end up with an entirely plain text version of the new annotation, as follows:
d) View the Attributes of the new ukl:CommentaryRef tag in the Attribute Inspector (click on the id number to the right of the ukl:CommentaryRef/ tag and open up the Attribute Inspector), The copy the id Ref number of the new annotation by clicking on the Ref number and right clicking and selecting “copy”;
e) Place the cursor in the opening ukl:Addition tag for the substitution of words and paste that id number over its CommentaryRef attribute. This makes the existing amendment point to the new annotation:
WARNING: Do not alter the Change ID reference number in the Attribute Inspector, as this will cause problems with the update:
While you are viewing the attributes of the ukl:Addition tagging, you will need to amend the Extent attribute to include the new extent (in this case the extent of the previous E amendments was E+W+N.I., and S. needed to be included so E+W+S+N.I. was selected from the drop-down menu)
f) Delete the inserted ukl:CommentaryRef tagging as it’s no longer needed (just highlight the ukl:CommentaryRef/ tag and delete it);
g) Check the provision back in and the deployment code will add links to the plain text annotation;
h) Preview your amendment to check the amendment brackets are in the correct location, you have removed the retained text and the annotation content and links are correct.
Editing legislation with concurrent versions created for limited extent substitutions
Our old editorial practice was to create ‘concurrent versions’ (or ‘parallel texts’) for all limited extent substitutions. This involved splitting up a provision into multiple versions in order to show the text for different geographical extents, for example:
http://www.legislation.gov.uk/ukpga/1967/84/section/18
On the new system we will only do this for whole section substitutions that are limited extent. All other amendments will be managed in a single version, unless the end result would be deemed confusing to the end user. If you think concurrent versions would be beneficial please seek advice from a Review Editor.
When the provision you are editing has existing concurrent versions: From time to time an amendment you are applying might hit a concurrent version.
When an amendment hits a concurrent version, (x2) or (x3) will appear next to the amendment on the Update Overview page and the Details Page to signify there are multiple versions in the data (the number will change depending on the number of versions).
All amendments to concurrent versions will be listed as high level amendments because they have to be edited from parent level:
On the Table of Contents any concurrent versions will be marked with an exclamation mark.
To edit a concurrent version, make sure you check the relevant provision out from the parent level.
In XMetaL you will be presented with multiple versions of the provision in question. In this example there are two versions of s. 18, one for Scotland and one for E.W. A blue header will appear at the top of each provision to indicate which is which, as shown in the following example:
Note: you may have to carry out the amendment in more than one version, depending on the extent of the amendment. For example, if your amendment extends to E.W.S, and there are two versions(one for E.W. and one for S.) you will need to carry your amendment out in both versions. Equally if your amendment extends to Scotland only you need only carry it out in the Scotland version and you won't have to treat it as limited extent because that version only extends to Scotland.
Examples
- Limited Extent; re-numbering of sub-paragraphs: 1992 c. 51, s. 10 This example also includes a good variety of other limited extent amendments.
- Limited Extent; exceptions where it is not possible to use the usual limited extent substitution of a provision procedure to produce concurrent versions as the affected provisions are tagged as ukl:P1 rather than ukl:P1 group: 1920 c.41, Sch. para 5B and 1920 c.41, Sch. para 5C