Crown Legislation Markup Language (CLML) User Guide

Abstract

This schema describes the Crown Legislation Markup Language (CLML). CLML is a dialect of XML that can describe legislation published by UK national governments and legislatures, as well as legislation originating from the European Union. The schema is suitable for both print and web publication of legislation, as well as for use in editorial applications (that is, it is intended that editors may directly edit the XML to produce revised versions of legislation).

Acknowledgements

We would like to thank the following individuals for their contributions to this documentation:

• Paul Appleby, for writing the original CLML schema and the CLML User Guide (on which this guide is substantially based);
• Colin Mackenzie of Mackenzie Solutions, for combining the separate versions of the CLML schema into one “unified” schema, converting the entire User Guide from Word to HTML and developing the documentation generator that dynamically incorporates the schema annotations, element diagrams and XML examples shown within the text of this guide;
• Jim Mangiafico of Juris Datum, for extending the CLML schema to support European Union legislation and for providing technical information for the guide;
• Mark “Griff” Chamberlain of The Stationery Office, for providing further technical information for the guide;
• Karl Rajangam of The Stationery Office, for assistance in writing inline annotations for the schema;
• Pip Arnott of The National Archives, for editing the User Guide to bring it up to date with the current CLML schema and its usage and to add fresh examples.

Change history

Date	Schema version	Changes
2/6/2023	2.6	First public release of the CLML schema documentation. Changes include: A new structure for the Guide, with separate parts for the core content model and each of the additional models; Up-to-date information on all schema features that explains how legislation.gov.uk uses them today; Multiple new sections on EU legislation and the changes to the content models to support it; New sections on the website, revised and editorial content models; Updated examples with new images, inline XML and a link to each document on legislation.gov.uk.

Overview

The Legislation Schema (also known as the CLML schema, for Crown Legislation Markup Language) specifies a document structure that can comprehensively represent:

• United Kingdom primary and secondary legislation;
• Legislation originating from the European Union.

Scope and objectives

The primary objectives for the design of the schema are as follows:

Expressivity:

• The schema should be able to describe all existing UK legislation data (within reason), along with any relevant metadata.
• The schema should be able to describe all EU regulations, decisions, directives and treaties, along with any relevant metadata, to allow for the publication of EU legislation (see the section below on EU legislation).

Versatility:

• The schema should enable the typesetting of documents that use the schema.
• The schema should allow fragmentation of the data, to enable a user to view or edit a subsection of the document.
• The schema should allow documents to use the functionality of hypermedia, such as URIs and hyperlinking on websites.

Modularity and standardisation:

• The schema should use a modular approach where appropriate, to enable reuse or replacement of individual schema modules (for example, the schema has different profiles for Publishing, Editorial and the website, each of which specify different constraints on allowable content).
• The schema should conform to recognized standards wherever practicable (e.g. W3 recommendations and UK Government schema guidelines).

Terminology used in this document

This documentation uses the following definitions:

• “The schema” means the legislation schema;
• A reference to a “chapter” number also includes measure numbers for Church Measures.

Schema documentation

Wherever possible, the schema includes inline documentation within each of its components, to make it easier to consult the documentation and keep it up to date.

The documentation explaining the meaning of each element and attribute, and the content that is allowed to be present within them, can be found in the Schema Reference Guide.

This documentation (the user guide) is intended to provide:

• Background information about the schema;
• Further information and guidance on major structures and elements.

Note: where a diagram of an element is provided in this document (or in the reference guide), it should be possible to click on an element or attribute in that diagram and navigate to the detailed information in the Schema Reference Guide.

Sample files

The user guide includes numerous examples of the use of CLML in legislation documents. Where this guide includes an excerpt from a legislation document, and the document is available as XML on legislation.gov.uk, the example will include a link to that document as XML.

Tool support

The legislation schema attempts to represent the structure of legislation in great detail and is consequently very complex. As a result, some tools and processors may not correctly interpret the schema, even though it is valid and compliant with the XML Schema specification.

The latest version of each of the following popular tools and processors supports validation using the schema:

• Saxon EE
• .NET (System.Xml)
• MSXML
• Xerces Java
• oXygen XML (Editor and Developer)
• Altova XMLSpy

Top-level schemas

The schema has the following top-level schemas that can be used to validate legislation documents:

• legislation.xsd—used to validate primary and secondary UK legislation and legislation originating from the EU, including that available from legislation.gov.uk and from the bulk downloads site, as well as data held within the legislation.gov.uk platform.
• fragment.xsd—used to validate fragments of legislation during the editing process. This schema has a root element of <Fragment> (rather than <Legislation>) and re-uses the content models from legislation.xsd in a more flexible way.

The following schema modules are not currently used for new data:

• en.xsd—used to validate explanatory notes and explanatory memoranda. (Note that government departments now normally deliver Explanatory Notes in a Markdown format that is then converted to HTML)
• impactAssessment.xsd—originally intended to validate UK Impact Assessments delivered as XML, but never used for data on legislation.gov.uk.

This documentation focuses on the legislation.xsd top-level schema, whose latest release is available on legislation.gov.uk. The fragment schema re-uses most of the features of the legislation schema but has some important differences, which the part on the fragment schema details.

Modular approach

The legislation schema uses a modular approach. The modules are of three different types:

• Legislation-specific (those that describe structures specific to legislation)
• Generic
• Off-the-shelf

We intend to re-use existing standards wherever possible to develop legislation.gov.uk and its components, including the legislation schema. The schema uses the following “off-the-shelf” modules, with minor adaptations to some of the modules to support our in-house tools:

• MathML (for mathematical formulae)
• Dublin Core (for metadata)
• Atom (for internal links to other versions or related resources of a document)
• XHTML (for tables and Atom feeds)
• XML namespace (for attributes relating to language and whitespace)

A secondary objective was to create generic modules for features that could be used for other content we publish, such as explanatory notes. Legislation and its associated documents are highly structured with similar content models, and share many common elements such as paragraphs, tables, lists, footnotes and hyperlinks, so the schema provides these in modules that the top-level schemas reuse.

A list of modules can be found in the Table of Contents in the Schema Reference Guide (group by “Location” or navigate through each file by selecting “resource hierarchy”).

Paragraph model

The schema models a paragraph as a modular entity built up of items of text, lists, tables and so on. In this model, the items of which the paragraph is built belong to the paragraph. This is different to, for instance, HTML, which uses the “sibling-blocks” model—that is, structures such as lists do not belong to the paragraph.

The schema paragraph model gives us paragraphs structured as in the following example:

<Para>
  <Text>“emergency services” include—</Text>
  <OrderedList Decoration="parens" Type="alpha">
    <ListItem>
      <Para>
        <Text>police, fire, rescue and ambulance services;</Text>
      </Para>
    </ListItem>
    <ListItem>
      <Para>
        <Text>Her Majesty’s Coastguard;</Text>
      </Para>
    </ListItem>
  </OrderedList>
</Para>

Ref: Example taken from https://www.legislation.gov.uk/uksi/2005/1643/regulation/2/1/data.xml

Namespaces

Each XML element and attribute has a name. This name consists of the local name (for example, img or src) and optionally a namespace, which is a URI (for example, http://www.legislation.gov.uk/namespaces/legislation). A namespace distinguishes elements or attributes with the same local name from one another, which is useful where a single XML schema or document combines elements or attributes from multiple modules or organisations.

A namespace URI need not have any special meaning, or even be possible for the processing application to resolve—it simply serves to be a globally unique identifier for the namespace, and can also imply “ownership” of a data model that uses the namespace (as opposed to the data itself) by a particular person or organisation.

An XML document can apply a namespace directly to an element using the xmlns attribute on that element (for example, <Citation xmlns="http://www.legislation.gov.uk/namespaces/legislation">). This indicates that the <Citation> element is in the http://www.legislation.gov.uk/namespaces/legislation namespace.

Alternatively, an XML document can apply a namespace to an element or attribute by defining a prefix on an element (for example, one can define the xs: prefix as denoting the XML Schema namespace by adding the attribute xmlns:xs="http://www.w3.org/2001/XMLSchema" to an element), which makes the namespace available for use on that element or any of its attributes or child nodes.

In the legislation schema, namespaces help to distinguish elements and attributes from different modules and schemas. For example, leg:Correction and ukm:Correction both have the same “local” name (Correction), but exist in different namespaces (http://www.legislation.gov.uk/namespaces/legislation for leg:Correction and http://www.legislation.gov.uk/namespaces/metadata for ukm:Correction) and appear as different types of element to an XML processor.

The default namespace for the schema is http://www.legislation.gov.uk/namespaces/legislation. Normally legislation documents use this namespace without a prefix, but in contexts where a prefix is used the normal prefix is leg:.

The schema uses other namespaces, including (but not limited to):

• http://www.legislation.gov.uk/namespaces/metadata—for legislation metadata (normally using the prefix ukm:);
• http://purl.org/dc/elements/1.1/—for Dublin Core metadata (normally using the prefix dc:);
• http://www.w3.org/2005/Atom—for Atom format links to resources (normally using the prefix atom:);
• http://www.w3.org/1998/Math/MathML—For MathML mathematical content (normally using the prefix m:).

A list of namespaces can be found in the Table of Contents in the Schema Reference Guide (group by “Namespace”).

EU legislation

In 2019, legislation.gov.uk began to publish EU legislation, in order to fulfil the obligations of the Queen’s Printer under Schedule 5 of the European Union (Withdrawal) Act 2018. We now publish all EU regulations, decisions and directives as they stood at the end of the Brexit implementation period.

The EU legislation on legislation.gov.uk originally comes from EUR-Lex, the EU legislation website operated by the Publications Office of the EU. Where legislation is available on EUR-Lex as XML, we have converted it into CLML before uploading it to legislation.gov.uk. We have extended the schema to support structures and metadata specific to EU legislation.

For more information on EU law following the UK’s withdrawal from the European Union, please see the EU legislation and UK law page on legislation.gov.uk.

High-level document structure

The root element of a legislation document consists of a <Legislation> element. Within this element, the following structures can occur:

• Metadata (the <ukm:Metadata> element)
• Tables of contents (the <Contents> element
• The high-level class container (the <Primary>, <Secondary> or <EURetained> element)
• Footnotes (the <Footnotes> element)
• Margin notes (the <MarginNotes> element)
• Versions (the <Versions> element)
• Resources (the <Resources> element)
• Commentaries (the <Commentaries> element)

The root element also permits citation lists (the <CitationLists> element), but these are defunct and no longer used in CLML.

All of these are detailed in the following sections or in the Schema Reference Guide.

The schema treats footnotes, margin notes, versions and resources as out-of-line constructs—that is, they are separate from the main flow of the content and are referenced from that content. The main reasons for this approach are that the content may reference the items in these constructs more than once, and by removing them from the main content it allows the main content to flow more easily.

Preliminary matter

The preliminary matter for primary and secondary legislation differs enough that the decision was taken to create separate mark-up for each. The preliminary matter for EU legislation also differs greatly from UK legislation, and so it too has its own structure to represent it.

Headings

The schema provides five levels of generic headings, which are sufficient to represent all cross-headings that appear in UK primary and secondary legislation. The following is a list of the heading structures:

• <Group>
• <Part>
• <Chapter>
• <Pblock>
• <PsubBlock>

The <Group>, <Part> and <Chapter> headings correspond to the numbered headings of the same name that appear in the text of legislation. The <Pblock> and <PsubBlock> elements correspond to the two levels of cross-headings that appear in legislation. (The <PsubBlock> level does not tend to occur in primary legislation.)

The schema enforces a hierarchy for the generic heading elements. Each of the above elements can contain as a child any of the elements below it (except that only a <Pblock> may contain a <PsubBlock>), but it may not contain an instance of the same element or any of the elements above. For example, a <Part> may contain a <Chapter> or a <Pblock>, but not a <Group> or another <Part>.

Each level can contain <Number> and <Title> elements, although the <Number> element is not always used for all document types. The <Number> element should contain words such as “Part 1”, whilst the <Title> element should contain the text of the heading for the section.

An example from a Scottish Act is given below:

<Body>
  <Part>
    <Number>Part 1</Number>
    <Title>Access rights</Title>
    <Chapter>
      <Number>Chapter 1</Number>
      <Title>Nature and extent of access rights</Title>
      <P1group>
        <Title>Access rights</Title>
        <P1>
          <Pnumber>1</Pnumber>
          <P1para>
            <P2>
              <Pnumber>1</Pnumber>
              <P2para>
                <Text>Everyone has the statutory rights established by this Part of this Act.</Text>
              </P2para>
            </P2>

Ref: Example taken from https://www.legislation.gov.uk/asp/2003/2/section/1/enacted/data.xml

Note: The content of this element has been reduced to make the example clearer.

In addition, each heading can have a <Reference> element, which is used to list the sections of the document to which the heading relates.

Schedules and annexes

For many pieces of legislation, the schedules form the major part of the document, and generally provide the detail to content described in the body of the document. The <Schedules> section (see the entry in the Reference Guide) follows on from the <Body> element and has a structure as shown below:.

Abstracts, signed sections (signatures), attachments and appendices are described elsewhere in this document. There may be an appendix to all the schedules, in which case it should be part of the <Schedules> element and occur after the schedules or, alternatively, it may be an appendix, in which case it should be part of a <Schedule> element.

The <Number> and <Title> elements should hold the schedule number and title respectively.

The <Reference> element is used to list the sections of the document to which the schedule relates.

Introductory text can, sometimes, occur between the schedule title and the table of contents of the schedule (if one occurs). The <IntroductoryText> element can be used to contain this text.

The following is an excellent example, where a schedule is amending a schedule and both contain <Reference> elements:

<Schedules>
  <Schedule id="schedule" NumberOfProvisions="24" NumberFormat="default">
    <Number>SCHEDULE</Number>
    <Reference>Regulation 16</Reference>
    <ScheduleBody>
      <BlockAmendment TargetClass="unknown" TargetSubClass="unknown" Context="schedule" Format="default" NumberFormat="default">
        <Schedule NumberFormat="default">
          <Number>SCHEDULE 3</Number>
          <TitleBlock><Title>FEES FOR ADVOCACY IN THE CROWN COURT</Title></TitleBlock>
          <Reference>Regulations 6(2C), 9(2A)</Reference>

Ref: Example taken from https://www.legislation.gov.uk/uksi/1996/2655/schedule/made/data.xml

Note: The content of this element has been reduced to make the example clearer.

EU documents have “annexes”, rather than schedules, but these also use the <Schedule> element. (However, when an EU document has an attached document, it normally appears in an attachment rather than in a schedule.)

Attachments

The <Attachment> element describes a document attached to an EU document. An attachment contains a high-level class container element (<EURetained> for EU documents), and so can use the full content model of a normal document, including preliminary matter, annexes and attachments. The <Attachment> element may currently only appear in an EU document.

An example of an attachment appears below:

<Attachment id="attachment-1">
   <EURetained>
      <EUPrelims>
         <MultilineTitle>
            <Text>DRAFT</Text>
            <Text>DECISION OF THE JOINT COMMITTEE</Text>
            <Text>of …</Text>
            <Text>on the adoption of its Rules of Procedure</Text>
         </MultilineTitle>
         <EUPreamble>
            <P>
               <Text>THE JOINT COMMITTEE,</Text>
            </P>
            <P>
               <Text>Having regard to the Agreement between the European Union and Georgia on protection of geographical indications of agricultural products and foodstuffs, and in particular Article 11 thereof,</Text>
            </P>
            <P>
               <Text>Whereas that Agreement entered into force on 1 April 2012,</Text>
            </P>
            <P>
               <Text>HAS ADOPTED THIS DECISION:</Text>
            </P>
         </EUPreamble>
      </EUPrelims>
      <EUBody>
         <P1group>
            <Title>Heads of Delegation</Title>
            <P1>
               <Pnumber>Article 1</Pnumber>
               <P1para>
                  <P2>
                     <Pnumber PuncBefore="" PuncAfter=".">1</Pnumber>
                     <P2para>
                        <Text>The European Union and Georgia (‘the Parties’), shall each appoint a Head of Delegation who shall be the contact person for all matters relating to the Committee.</Text>
                     </P2para>
                  </P2>

Ref: Example taken from https://www.legislation.gov.uk/eudn/2012/533/attachment/1/adopted/data.xml

Note: The content of this element has been reduced to make the example clearer.

The <AttachmentGroup> element describes a group of attachments that may share a number and/or title.

An example of an attachment group appears below:

<AttachmentGroup id="attachment-group">
   <Title>
      <Uppercase>Protocols</Uppercase>
   </Title>
   <Attachment id="attachment-group-attachment-1" RestrictStartDate="2015-12-25" AltDates="2015-12-25" ValidDates="2015-12-25" RestrictExtent="E+W+S+N.I.">
      <EURetained>
         <EUPrelims AltDates="" ValidDates="" RestrictExtent="E+W+S+N.I.">
            <MultilineTitle>
               <Text>PROTOCOL (No 1)</Text>
               <Text>ON THE ROLE OF NATIONAL PARLIAMENTS IN THE EUROPEAN UNION</Text>
            </MultilineTitle>
            <EUPreamble>
               <P>
                  <Text>THE HIGH CONTRACTING PARTIES,</Text>
               </P>
               <P>
                  <Text>RECALLING that the way in which national Parliaments scrutinise their governments in relation to the activities of the Union is a matter for the particular constitutional organisation and practice of each Member State,</Text>
               </P>
               <P>
                  <Text>DESIRING to encourage greater involvement of national Parliaments in the activities of the European Union and to enhance their ability to express their views on draft legislative acts of the Union as well as on other matters which may be of particular interest to them,</Text>
               </P>
               <P>
                  <Text>HAVE AGREED UPON the following provisions, which shall be annexed to the Treaty on European Union, to the Treaty on the Functioning of the European Union and to the Treaty establishing the European Atomic Energy Community:</Text>
               </P>
            </EUPreamble>
         </EUPrelims>
         <EUBody RestrictStartDate="2015-12-25" AltDates="2015-12-25" ValidDates="2015-12-25" RestrictExtent="E+W+S+N.I.">
            <EUTitle>
               <Number>TITLE I</Number>
               <Title>
                  <Strong>INFORMATION FOR NATIONAL PARLIAMENTS</Strong>
               </Title>
               <P1>
                  <Pnumber>Article 1</Pnumber>
                  <P1para>
                     <Text>Commission consultation documents (green and white papers and communications) shall be forwarded directly by the Commission to national Parliaments upon publication. The Commission shall also forward the annual legislative programme as well as any other instrument of legislative planning or policy to national Parliaments, at the same time as to the European Parliament and the Council.</Text>
                  </P1para>
               </P1>

Ref: Example taken from https://www.legislation.gov.uk/eut/teu/attachmentgroup/1/2020-03-01/data.xml

Note: The content of this element has been reduced to make the example clearer.

The legislation.gov.uk website does not support navigating to provisions within attachments, and so does the descendant elements of an <Attachment> element should not have structural IDs or URIs.

Provisions and paragraphs

The main body of an item of modern legislation consists of numbered paragraphs. (Older legislation, particularly that enacted before 1600, often does not contain numbered paragraphs.)

There are seven levels of numbered paragraphs in the schema, with element names of <P1>–<P7> (see the P1 entry in the Schema Reference Guide). The level that should be used should reflect the structural level that is required. The following guidelines should indicate the level to use:

• A numbered paragraph that is a direct child of the body, a heading element or a <P1group> (see below) must be a <P1>.
• A numbered paragraph that is a direct child of a <P1>’s <P1para> element:
  • should normally be a <P2> if its number uses Arabic numerals (1-9), even if the number also uses letters (e.g. 2A); or
  • should normally be a <P3> if its number uses letters only (a-z).
• A numbered paragraph that is a child of a <P2para> or a lower level should normally be of the next level down (for example, numbered paragraphs within a <P3para> should normally use the <P4> element).

Each numbered level must contain a <Pnumber> element that contains the number of the paragraph. Normally, a document should not include punctuation for the number, as this is implied formatting. However, if an author needs to specify non-standard punctuation, they can use the attributes PuncBefore and PuncAfter to specify punctuation occurring before or after the number. The below example uses these attributes to replace the brackets that normally surround a <P2> with a trailing full stop:

<P1group>
   <Title>Beneficiaries and scope</Title>
   <P1 id="article-1">
      <Pnumber>Article 1</Pnumber>
      <P1para>
         <P2 id="article-1-1">
            <Pnumber PuncBefore="" PuncAfter=".">1</Pnumber>
            <P2para>
               <Text>Any natural or legal person shall have a right of access to documents of the Translation Centre for the bodies of the European Union (the Centre) subject to the principles, conditions and limits laid down in Regulation (EC) No 1049/2001 and in accordance with the provisions of this decision.</Text>
            </P2para>
         </P2>

Ref: Example taken from https://www.legislation.gov.uk/eudn/2004/605/article/1/adopted/data.xml

Note: The content of this element has been reduced to make the example clearer.

In addition to the seven numbered paragraph levels, there is also a <P> element (see the P entry in the Schema Reference Guide), which represents an unnumbered paragraph. A <P> element must start with some inline content, and after this may contain <P1> children as well as lower levels of paragraph. A <P1group> element may contain <P> children, allowing for a heading to a collection of paragraphs, although this use is rare and discouraged. An example of <P> is given below:

<ExplanatoryNotes>
  <Title>EXPLANATORY NOTE</Title>
  <Comment>
    <Para>
      <Text>(This note is not part of the Regulations)</Text>
    </Para>
  </Comment>
  <P>
    <Text>These Regulations amend the Education (School Performance Information) (England) Regulations 2001.</Text>
  </P>
  <P>
    <Text>The principal amendments will—</Text>
    <P3>
      <Pnumber>a</Pnumber>
      <P3para>
        <Text>require Academies to provide the Secretary of State with information about second key stage assessment results <Emphasis>(regulation 4)</Emphasis>;</Text>
      </P3para>
    </P3>
    <P3>
      <Pnumber>b</Pnumber>
      <P3para>
        <Text>require maintained schools, non-maintained special schools and independent schools to provide the Secretary of State with information about the results of pupils at or near the end of the fourth key stage and of pupils aged 15 but not at or near the end of the fourth key stage <Emphasis>(regulation 5)</Emphasis>;</Text>
      </P3para>
    </P3>

Ref: Example taken from https://www.legislation.gov.uk/uksi/2005/2338/note/made/data.xml

Note: The content of this element has been reduced to make the example clearer.

There is also a <Para> element (see the Para entry in the Schema Reference Guide). This is used where it is not possible for a paragraph to contain numbered paragraphs (it may include numbered lists). For example:

<EnactingText>
  <Para>
    <Text>The Secretary of State, in the exercise of the powers conferred on him by sections 15(1), (2), and (5), and 82(2) and (3) of, and paragraphs 1(1)(a) and (c), 8(1), 9, 11, 13(2) and (3), 14, 15(1), 16 and 20 of Schedule 3 to the Health and Safety at Work etc. Act 1974<FootnoteRef Ref="f00001"/> (“the 1974 Act”) and of all other powers enabling him in that behalf, for the purpose of giving effect without modifications to proposals submitted to him by the Health and Safety Commission under section 11(2)(d) of the 1974 Act after the carrying out by the said Commission of consultations in accordance with section 50(3) of that Act, hereby makes the following Regulations:</Text>
  </Para>
</EnactingText>

Ref: Example taken from https://www.legislation.gov.uk/uksi/2005/1643/introduction/made/data.xml

Note: The content of this element has been reduced to make the example clearer.

The next example shows an example covering the first three levels of paragraph.

<P1group>
  <Title>General functions of the Board</Title>
  <P1 id="section-3">
    <Pnumber>3</Pnumber>
    <P1para>
      <P2 id="section-3-1">
        <Pnumber>1</Pnumber>
        <P2para>
          <Text>The Board shall secure the maintenance of the police in Northern Ireland.</Text>
        </P2para>
      </P2>
      <P2 id="section-3-2">
        <Pnumber>2</Pnumber>
        <P2para>
          <Text>The Board shall secure that—</Text>
          <P3 id="section-3-2-a">
            <Pnumber>a</Pnumber>
            <P3para>
              <Text>the police,</Text>
            </P3para>
          </P3>
          <P3 id="section-3-2-b">
            <Pnumber>b</Pnumber>
            <P3para>
              <Text>the police support staff, and</Text>
            </P3para>
          </P3>
          <P3 id="section-3-2-c">
            <Pnumber>c</Pnumber>
            <P3para>
              <Text>traffic wardens appointed by the Board under section 71,</Text>
            </P3para>
          </P3>
          <Text>are efficient and effective.</Text>
        </P2para>
      </P2>

Ref: Example taken from https://www.legislation.gov.uk/ukpga/2000/32/section/3/made/data.xml

Note: The content of this element has been reduced to make the example clearer.

The following example is from a UK SI and shows the numbering system working within a <BlockAmendment> element (detailed in the Amendments section). Note that exactly the same mark-up is used within the amendment as would be in the main text. Although the formatting is completely different to the previous example the semantics are the same and therefore the mark-up is the same.

<Schedules>
  <Schedule>
    <Number>SCHEDULE</Number>
    <Reference>Regulation 2(g)</Reference>
    <ScheduleBody>
      <BlockAmendment TargetClass="secondary" TargetSubClass="regulation" Context="schedule" Format="default">
        <Schedule>
          <Number>SCHEDULE 1A</Number>
          <TitleBlock>
            <Title>MEANING OF END OF SERIES VEHICLE</Title>
          </TitleBlock>
          <Reference>Regulation 18A(7)</Reference>
          <ScheduleBody>
            <P1>
              <Pnumber>1</Pnumber>
              <P1para>
                <P2>
                  <Pnumber>1</Pnumber>
                  <P2para>
                    <Text>A vehicle is an end of series vehicle for an EC type approval to which regulation 18A applies if—</Text>
                    <P3>
                      <Pnumber>a</Pnumber>
                      <P3para>
                        <Text>an EC certificate of conformity has been issued in respect of the vehicle under the EC type approval (whether before or after the giving of the direction by the Secretary of State);</Text>
                      </P3para>
                    </P3>
                    <P3>
                      <Pnumber>b</Pnumber>
                      <P3para>
                        <Text>the vehicle was in the territory of an EEA State at a time when the EC type approval had effect;</Text>
                      </P3para>
                    </P3>
                    <P3>
                      <Pnumber>c</Pnumber>
                      <P3para>
                        <Text>it was manufactured with the intention that it should be supplied by retail for use in the United Kingdom;</Text>
                      </P3para>
                    </P3>

Ref: Example taken from https://www.legislation.gov.uk/uksi/2003/1099/schedule/made/data.xml

Note: The content of this element has been reduced to make the example clearer.

Lists

The schema provides ordered lists (e.g. numbered lists), unordered lists (e.g. bulleted lists) and key lists (lists that provide a key to something, such as a formula). In general, the schema’s paragraph model specifies that lists are part of a paragraph, although formulae may contain a key list or unordered list as a direct child.

Inline structures and local formatting

Signatures

Signatures occur routinely in secondary and EU origin legislation. Very rarely, an item of primary legislation may have a signature, although in practice these only occur in a schedule. The container for the signatures is a <SignedSection> element (see the SignedSection entry in the Schema Reference Guide). This can contain one or more <Signatory> elements. A signatory is one or more persons connected for some reason (i.e. by department). Each <Signatory> element can contain a <Para> element and then one or more <Signee> elements for each signee of the document. It may also have a Date and Time attribute to hold the value of the date and time of signing.

Each <Signee> element has the following structure:

The <LSseal> element represents the official seal with which the signee sealed the document. The <Para> element allows the author of a document to add information about the signee (for example, a statement made by the signee, or a statement that the document has been sealed).

The following are examples of signatures:

<SignedSection>
  <Signatory>
    <Signee>
      <PersonName>Chris Smith</PersonName>
      <JobTitle>Secretary of State for Culture, Media and Sport</JobTitle>
      <DateSigned Date="2000-03-30">
        <DateText>30th March 2000</DateText>
      </DateSigned>
    </Signee>
  </Signatory>
</SignedSection>

Ref: Example taken from https://www.legislation.gov.uk/uksi/2000/933/signature/made/data.xml

<SignedSection>
  <Signatory>
    <Signee>
      <PersonName>Jim Fitzpatrick</PersonName>
      <PersonName>John Heppell</PersonName>
      <JobTitle>Two of the Lords Commissioners of Her Majesty’s Treasury</JobTitle>
      <DateSigned Date="2003-04-09">
        <DateText>9th April 2003</DateText>
      </DateSigned>
    </Signee>
  </Signatory>
  <Signatory>
    <Para>
      <Text>The Secretary of State hereby concurs</Text>
    </Para>
    <Para>
      <Text>Signed by the authority of the Secretary of State</Text>
    </Para>
    <Signee>
      <PersonName>Maria Eagle</PersonName>
      <JobTitle>Parliamentary Under Secretary of State</JobTitle>
      <Department>Department for Work and Pensions</Department>
      <DateSigned Date="2003-04-09">
        <DateText>9th April 2003</DateText>
      </DateSigned>
    </Signee>
  </Signatory>
  <Signatory Date="2003-04-09">
    <Para>
      <Text>The Department for Social Development hereby concurs</Text>
    </Para>
    <Para>
      <Text>Sealed with the Official Seal of the Department for Social Development on 9th April 2003</Text>
    </Para>
    <Signee>
      <LSseal Date="2003-04-09"/>
      <PersonName>Henry Johnston</PersonName>
      <JobTitle>Senior Officer of the</JobTitle>
      <Department>Department for Social Development</Department>
    </Signee>
  </Signatory>
</SignedSection>

Ref: Example taken from https://www.legislation.gov.uk/uksi/2003/1059/signature/made/data.xml

Appendices

Appendices do not occur frequently. They can appear after the body of the document, after a schedule, or after the schedules (in which case they apply to all the schedules).

The <Appendix> element (see the Appendix entry in the Schema Reference Guide) must contain a <Number> element, and may also, optionally, contain a <TitleBlock> element. A <Reference> element can be used to refer back to an introducing provision with the body or schedules of the document.

Additionally, there may also be a table of contents for the appendix, held in the <Contents> element.

The content of the appendix is held in the <AppendixBody> element.

An example is given below:

<Appendix NumberFormat="default" id="appendix">
  <Number>APPENDIX</Number>
  <AppendixBody>
    <Tabular Orientation="portrait">
      <Number>
        <Strong>Table A</Strong>
      </Number>
      <table cols="4">
        <thead>
          <tr>
            <th/>
            <th colspan="3">
              <Emphasis>Annual Pay</Emphasis>
            </th>
          </tr>
          <tr>
            <th>
              <Emphasis>Rank</Emphasis>
            </th>
            <th>
              <Emphasis>Service in Rank</Emphasis>
            </th>
            <th>
              <Emphasis>London</Emphasis>
            </th>
            <th>
              <Emphasis>Provinces</Emphasis>
            </th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td/>
            <td/>
            <td>£</td>
            <td>£</td>
          </tr>
          <tr>
            <td>Chief Superintendent</td>
            <td>Less than 1 year</td>
            <td>37,071</td>
            <td>37,071</td>
          </tr>
          <tr>
            <td/>
            <td>After 1 year</td>
            <td>37,599</td>
            <td>37,599</td>
          </tr>

Ref: Example taken from https://www.legislation.gov.uk/uksi/1991/2484/appendix/made/data.xml

Note: The content of this element has been reduced to make the example clearer.

Abstracts

Abstracts are rare (the only regular occurrence is the Appropriation Act). They provide a summary of the contents of the schedules (they are not a table of contents). The <Abstract> element contains a <TitleBlock> element, where a title and subtitle can be held, and a <AbstractBody element, where the main content of the abstract is held.

<Abstract>
  <TitleBlock>
    <Title>Abstract of schedules 1 and 2</Title>
    <Subtitle>to which this Act refers</Subtitle>
  </TitleBlock>
  <AbstractBody>
    <Chapter>
      <Number>Schedule 1</Number>
      <Tabular Orientation="portrait">
        <table width="100%" cols="2">
          <col width="80%"/>
          <col width="20%" align="right"/>          
                <tbody>
            <tr>
              <td>Resources authorised for use <leg:Character Name="DotPadding"/>
              </td>
              <td>£1,250,531,000</td>
            </tr>
            <tr>
              <td>Grants out of the Consolidated Fund <leg:Character Name="DotPadding"/>
              </td>
              <td>£2,853,190,000</td>
            </tr>
          </tbody>
        </table>
      </Tabular>

Ref: Example taken from ukpga_20010021_en (not currently available online in this form)

Note: The content of this element has been reduced to make the example clearer.

Earlier orders

In a commencement order, the ”earlier orders” table gives a list of commencement orders that have previously brought into force provisions of the same commenced item of legislation. The <EarlierOrders> element (see the EarlierOrders entry in the Schema Reference Guide) only occurs within commencement orders and is therefore only applicable to secondary legislation. This element may contain a <Title> element and a <Comment> element, both of which normally contain a standard piece of text. The following is an example:

<EarlierOrders>
  <Title>Note as to Earlier Commencement Orders</Title>
  <Comment>
    <Para>
      <Text>(This note is not part of the Order)</Text>
    </Para>
  </Comment>
  <P>
    <Text Hanging="indented">The following provisions of the Nationality, Immigration and Asylum Act 2002 have been brought into force on the dates shown by commencement orders before the date of this Order.</Text>
    <Tabular Orientation="portrait">
      <table cols="3" fo:border-left-style="solid" fo:border-bottom-style="solid" fo:border-right-style="solid" fo:border-top-style="solid">
        <col width="50%"/>
        <col width="25%"/>
        <col width="25%"/>
        <thead fo:border-bottom-style="solid" fo:border-top-style="solid">
          <tr>
            <th fo:border-right-style="solid">Provision</th>
            <th fo:border-right-style="solid">Date of Commencement</th>
            <th>S.I. No. </th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td fo:border-bottom-style="solid" fo:border-right-style="solid">Section 54 and paragraphs 2, 8, 9, 10, 11, 12, 15 and 16 of Schedule 3 (withholding and withdrawal of support) (for the purpose of enabling the Secretary of State to exercise the power to make subordinate legislation)</td>
            <td fo:border-bottom-style="solid" fo:border-right-style="solid">8th December 2002</td>
            <td fo:border-bottom-style="solid">2002/2811</td>
          </tr>
          <tr>
            <td fo:border-bottom-style="solid" fo:border-right-style="solid">Section 54 and Schedule 3 (withholding and withdrawal of support) (so far as not already in force)</td>
            <td fo:border-bottom-style="solid" fo:border-right-style="solid">8th January 2003</td>
            <td fo:border-bottom-style="solid">2002/2811</td>
          </tr>
          <tr>
            <td fo:border-bottom-style="solid" fo:border-right-style="solid">Section 55 (late claim for asylum: refusal of support)</td>
            <td fo:border-bottom-style="solid" fo:border-right-style="solid">8th January 2003</td>
            <td fo:border-bottom-style="solid">2002/2811</td>
          </tr>

Ref: Example taken from https://www.legislation.gov.uk/uksi/2003/1/earlier-orders/made/data.xml

Note: The content of this element has been reduced to make the example clearer.

Commencement orders are secondary legislation, and so this element may only appear within a <Secondary> class container element.

Explanatory notes

An item of secondary legislation may contain an explanatory note, which describes the content of the item and provides information about the impact assessment for the item (if there is one) and any associated documents.

The explanatory note for an item of secondary legislation is not the same as the explanatory note for an item of primary legislation, nor is it the same as the explanatory memorandum or explanatory document provided with some secondary legislation—for more information on these, see the section on explanatory material.

The <ExplanatoryNotes> element may contain a <Title> element and a <Comment> element, both of which normally contain a standard piece of text. The title is not needed if it contains the standard text “Explanatory Notes”. If the <Title> element is missing an application should render a title with the words “EXPLANATORY NOTE” (or “NODYN ESBONIADOL” in a Welsh document).

The following is an example of an explanatory note:

<ExplanatoryNotes>
  <Title>Explanatory Note</Title>
  <Comment>
    <Para>
      <Text>(This note is not part of the Order)</Text>
    </Para>
  </Comment>
  <P>
    <Text>This Order brings into force a variation to the Public Lending Right Scheme 1982 made by the Secretary of State on 30th March 2000.</Text>
  </P>
  <P>
    <Text Hanging="indented">The variation is set out in the Appendix. The effect of the variation is to include within the Scheme as eligible persons under Article 5 of the Scheme those authors who are resident in any country of the European Economic Area.</Text>
  </P>
</ExplanatoryNotes>

Ref: Example taken from https://www.legislation.gov.uk/uksi/2000/933/note/made/data.xml

For more details, see the ExplanatoryNotes entry in the Schema Reference Guide.

Forms

Many items of legislation contain “forms”, which specify the content, and often the appearance, of a document that a specific process must use. A document will normally include a form as an image, although a form may contain markup in addition to an image or (more rarely) instead of an image.

The <Form> element denotes a form. The below example is a form that includes an image using an <Image> element, with reference to an image resource described by a <Resource> element:

<Form>
  <Number>Form 12: Form of Certificate of Employment</Number>
  <Figure ImageLayout="vertical" Orientation="portrait">
    <Image ResourceRef="r00009" Width="396.96pt" Height="279.84pt"/>
  </Figure>
</Form>

<Resource id="r00009">
  <ExternalVersion URI="http://www.legislation.gov.uk/uksi/2014/333/images/uksi_20140333_en_009"/>
</Resource>

Ref: Example taken from https://www.legislation.gov.uk/uksi/2014/333/schedule/1/made/data.xml

For more information on the structure of forms, see the Form entry in the Schema Reference Guide.

Images

The <Image> element represents a single image. An image may be inline, or alternatively display as a block when it is contained in a <Figure> element or in a <Signee> element in a signature.

An image does not link directly to a file, but instead to a resource represented by a <Resource> element. The reason for this is that the resource may be external (i.e. a file) or it may be internal (i.e. the image data is held within the document).

The resource is referenced with a ResourceRef attribute. It is perfectly acceptable for more than one Image element to reference the same resource.

Each Image element must have Width and Height attributes. The values held are expected to reflect the size of the original image as printed (not necessarily the actual native size of the image) if absolute values are held (for example, 580pt). The values can be in points or ems. Ems are expected mainly to be used inline (where it would be likely that the image would be less than 1em high to avoid problems with line spacing). Obviously for display images ems may not have a defined value, in which case it would be down to the implementation to define what an em is.

It it is possible to use relative values. These have been created with authoring of legislation in mind and are explained below:

• auto (default value) - This indicates that the image should be scaled automatically for the output format. This is generally used in conjunction with ‘scale-to-fit’ on the other attribute to maintain the aspect ratio of the image. If the image will not fit on the output then it should be cropped. If both attributes are auto then the image should be output at its native size.
• scale-to-fit - This should enlarge the image for either the width or height (whichever attribute this is on) to fit the output format. For printed output this would generally be the page width or height. It would be down to implementations as to how to treat this value for, say, web output.
• fit-page-to-image - This is designed for use with oversize images where it is desirable to enlarge the page size to fit the image. For other output formats it would be down to implementation as to how to treat this value
• spread - This is also designed for use with oversize images but in this instance it indicates that for printed documents the output should be put on a page spread.
• % - For values defined as percent this should be a percentage of the containing area. For printed output this will be the printable section of the page.

For display images a <Figure> element is used to wrap the images (there may be more than one image in a figure). The figure may, optionally, have a number, a title, explanatory paragraphs of text and notes (i.e. footnotes to the figure).

The following is an example of a figure with a number, title and some explanatory text:

<Figure Orientation="portrait" ImageLayout="vertical">
  <Number>7001.3</Number>
  <Title>Vehicular traffic should proceed slowly owing to workforce in road ahead</Title>
  <Para>
    <Tabular Orientation="portrait">
      <table cols="2">
        <thead>
          <tr>
            <th colspan="1" rowspan="1">Item</th>
            <th colspan="1" rowspan="1"/>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td colspan="1" rowspan="1">1</td>
            <td colspan="1" rowspan="1">Regulations: None</td>
          </tr>
          <tr>
            <td colspan="1" rowspan="1">2</td>
            <td colspan="1" rowspan="1">Diagrams: None</td>
          </tr>
          <tr>
            <td colspan="1" rowspan="1">3</td>
            <td colspan="1" rowspan="1"><Para>
                <Text>Permitted variants:</Text>
              </Para>
              <Para>
                <Text>“WORKFORCE IN ROAD” may be varied to “SETTING OUT ROAD WORKS AHEAD” and “SLOW” omitted</Text>
              </Para>
            </td>
          </tr>
          <tr>
            <td colspan="1" rowspan="1">4</td>
            <td colspan="1" rowspan="1">Illumination requirements: Schedule 17, item 1</td>
          </tr>
        </tbody>
      </table>
    </Tabular>
  </Para>
  <Image Height="117.12pt" Width="593.04pt" ResourceRef="r00006"/>
</Figure>

Ref: Example taken from https://www.legislation.gov.uk/nisr/2007/311/made/data.xml

It is possible to control the orientation of the figure in print output using the Orientation attribute. The attribute can take values of “portrait” or “landscape”.

The ImageLayout attribute defines the layout of the images. This mainly applies when there is more than one image in a figure. They may be laid vertically (normal), horizontally, e.g. across the page, or when there are many images, in a matrix format up to 5 images wide.

There is the possibility that this option may cause a conflict on image widths and page size. It it left to individual implementations as to how this should be resolved.

The ImageLayout attribute permits the following values:

Value	Description
vertical	Images will be laid below each other on the page
horizontal	Images will be placed beside each other on the page
matrix-2-wide	Images will be placed two to a line, using enough lines as needed to place all the images
matrix-3-wide	Images will be placed three to a line, using enough lines as needed to place all the images
matrix-4-wide	Images will be placed four to a line, using enough lines as needed to place all the images
matrix-5-wide	Images will be placed five to a line, using enough lines as needed to place all the images

Additionally a figure can carry an id attribute which acts as a unique identifier for the figure. The format of this identifier should be gxxxxx, where xxxxx is a five digit padded number (for example, “g00010” or “g01353”).

For more information, see the Figure section of the Schema Reference Guide.

Tables

Tables occur frequently within legislation and can be of reasonable complexity and large in size (both in terms of number of rows and columns and actual printed size).

The <Tabular> element contains one or more tables. This element is a wrapper for the table (or tables) and any associated content. The <table> element from the XHTML namespace describes the table itself, and appears as a child once for each table in the <Tabular> element.

The schema uses a modified form of the XHTML table model. The modified version tightens the model slightly and extends it to support legislation content. For instance, a tbody element is obligatory. In some areas unnecessary mark-up is omitted, e.g. cellspacing and cellpadding attributes. In addition the style attribute has been replaced with attributes from XSL:FO (XSL Formatting Objects, which use the http://www.w3.org/TR/xsl namespace), hereafter referred to as “FO”. The reason for this is to ease the task of processing documents and also to enable easier authoring by not requiring authors or processing applications to understand CSS.

A table may be given a title using either the <Title> child of the <Tabular> element. Alternatively, each individual table can be given a caption using an XHTML <caption> element within the <table> element. In general the table title should be described using the <Title> element rather than the <caption> element—the caption element should be reserved for when multiple tables occur in a <Tabular> element.

For details of the structure, child elements (e.g. <caption>) and the use of the Orientation attribute (to control the rotation of the entire structure), please see the Tabular entry in the Schema Reference Guide.

The following example demonstrates the use of <Number> to add a number to a set of tables, <TableText> to include notes to the tables and the use of <caption> to provide a title for an individual table:

<Tabular Orientation="portrait">
  <Number>TABLE 2</Number>
  <TableText>
    <P1>
      <Pnumber>1</Pnumber>
      <P1para>
        <Text>This table is for the determination of payments to dependants of deceased sufferers under regulation 4(2) or (6).</Text>
      </P1para>
    </P1>
    <P1>
      <Pnumber>2</Pnumber>
      <P1para>
        <Text>The relevant period is the period specified in regulation 3(2) or, in the case of a disabled person to whom regulation 6 applies, the first period specified in regulation 6(1)(b).</Text>
      </P1para>
    </P1>
    <P1>
      <Pnumber>3</Pnumber>
      <P1para>
        <P2>
          <Pnumber>1</Pnumber>
          <P2para>
            <Text>Part A of the table prescribes payments to dependants of disabled persons who died as a result of a disease other than diffuse mesothelioma.</Text>
          </P2para>
        </P2>
        <P2>
          <Pnumber>2</Pnumber>
          <P2para>
            <Text>Part B of the table prescribes payments to dependants of disabled persons who died as a result of diffuse mesothelioma.</Text>
          </P2para>
        </P2>
      </P1para>
    </P1>
    <P1>
      <Pnumber>4</Pnumber>
      <P1para>
        <Text>Part A of the table prescribes payments to-</Text>
        <P3>
          <Pnumber>a</Pnumber>
          <P3para>
            <Text>dependants to whom death benefit under section 108 of the Social Security Contributions and Benefits Act 1992 is payable;</Text>
          </P3para>
        </P3>
        <P3>
          <Pnumber>b</Pnumber>
          <P3para>
            <Text>dependants of a person to whom disablement benefit under that section or under any corresponding provision of the former Industrial Injuries Acts was payable immediately before that person died; and</Text>
          </P3para>
        </P3>
        <P3>
          <Pnumber>c</Pnumber>
          <P3para>
            <Text>dependants of a person to whom disablement benefit would have been payable immediately before that person died but for the occurrence of one of the circumstances listed in regulation 5(1)(a)(iii), or but for the person’s disablement amounting to less than the appropriate percentage.</Text>
          </P3para>
        </P3>
      </P1para>
    </P1>
  </TableText>
  <table cols="6">
    <caption>Part A</caption>
    <colgroup>
      <col width="61.05pt"/>
      <col width="60pt"/>
      <col width="54pt"/>
      <col width="54pt"/>
      <col width="54pt"/>
      <col width="66pt"/>
    </colgroup>
    <thead>
      <tr>
        <th rowspan="2" colspan="1"><Strong><Emphasis>Age of disabled person on their last birthday before their death</Emphasis></Strong></th>
        <th rowspan="1" colspan="5"><Strong><Emphasis>Percentage assessment for the relevant period</Emphasis></Strong></th>
      </tr>
      <tr>
        <th rowspan="1" colspan="1"><Para>
            <Text><Emphasis>10%</Emphasis></Text>
          </Para>
          <Para>
            <Text><Emphasis>or under</Emphasis></Text>
          </Para>
          <Para>
            <Text><Emphasis>£</Emphasis></Text>
          </Para>
        </th>
        <th rowspan="1" colspan="1"><Para>
            <Text><Emphasis>11%</Emphasis></Text>
          </Para>
          <Para>
            <Text><Emphasis>-20%</Emphasis></Text>
          </Para>
          <Para>
            <Text><Emphasis>£</Emphasis></Text>
          </Para>
        </th>
        <th rowspan="1" colspan="1"><Para>
            <Text><Emphasis>21%</Emphasis></Text>
          </Para>
          <Para>
            <Text><Emphasis>-30%</Emphasis></Text>
          </Para>
          <Para>
            <Text><Emphasis>£</Emphasis></Text>
          </Para>
        </th>
        <th rowspan="1" colspan="1"><Para>
            <Text><Emphasis>31%</Emphasis></Text>
          </Para>
          <Para>
            <Text><Emphasis>-49%</Emphasis></Text>
          </Para>
          <Para>
            <Text><Emphasis>£</Emphasis></Text>
          </Para>
        </th>
        <th rowspan="1" colspan="1"><Para>
            <Text><Emphasis>50%</Emphasis></Text>
          </Para>
          <Para>
            <Text><Emphasis>or over</Emphasis></Text>
          </Para>
          <Para>
            <Text><Emphasis>£</Emphasis></Text>
          </Para>
        </th>
      </tr>
    </thead>
    <tbody>
      <tr>
        <td rowspan="1" colspan="1">37 and under</td>
        <td rowspan="1" colspan="1" valign="middle">22,102</td>
        <td rowspan="1" colspan="1" valign="middle">37,684</td>
        <td rowspan="1" colspan="1" valign="middle">42,251</td>
        <td rowspan="1" colspan="1" valign="middle">43,501</td>
        <td rowspan="1" colspan="1" valign="middle">44,537</td>
      </tr>

Ref: Example taken from https://www.legislation.gov.uk/uksi/2014/869/regulation/2/5/made/data.xml

Note: The content of this element has been reduced to make the example clearer.

The following example demonstrates the use of <Subtitle>, the use of multiple <table> elements, and the use of <tfoot> and <Footnote> elements to create table-specific footnotes:

<Tabular Orientation="portrait">
   <Title>
      <Emphasis>Table 11</Emphasis>
   </Title>
   <Subtitle>
      <Strong>Continuing Airworthiness Management Organisation Approval</Strong>
   </Subtitle>
   <Subtitle>(referred to in Part M Subpart G of Annex I to Regulation (EC) No 2042/2003)</Subtitle>
   <table cols="2">
      <tbody>
         <tr>
            <th/>
            <th>Flat fee<FootnoteRef Ref="f00019"/> (EUR)</th>
         </tr>
         <tr>
            <th>Approval fee</th>
            <td>50 000</td>
         </tr>
         <tr>
            <th>Surveillance fee</th>
            <td>50 000</td>
         </tr>
      </tbody>
   </table>
   <table cols="3">
      <tfoot>
         <tr>
            <td colspan="3">
               <Footnote id="f00019">
                  <FootnoteText>
                     <Para>
                        <Text>The fee to be paid shall be composed of the flat fee plus the flat fee(s) based on technical rating.</Text>
                     </Para>
                  </FootnoteText>
               </Footnote>
            </td>
         </tr>
         <tr>
            <td colspan="3">
               <Footnote id="f00020">
                  <FootnoteText>
                     <Para>
                        <Text>For organisations holding several A ratings, only the highest fee shall be charged.</Text>
                     </Para>
                  </FootnoteText>
               </Footnote>
            </td>
         </tr>
      </tfoot>
      <tbody>
         <tr>
            <th>Technical Ratings</th>
            <th>Flat fee based on technical rating<FootnoteRef Ref="f00020"/> (EUR) – Initial Approval</th>
            <th>Flat fee based on technical rating<FootnoteRef Ref="f00020"/> (EUR) – Surveillance</th>
         </tr>
         <tr>
            <td>A1 = airplanes above 5,7 ton</td>
            <td>12 500</td>
            <td>12 500</td>
         </tr>
         <tr>
            <td>A2 = airplanes below 5,7 ton</td>
            <td>6 250</td>
            <td>6 250</td>
         </tr>
         <tr>
            <td>A3 = helicopters</td>
            <td>6 250</td>
            <td>6 250</td>
         </tr>
         <tr>
            <td>A4: all others</td>
            <td>6 250</td>
            <td>6 250</td>
         </tr>
      </tbody>
   </table>
</Tabular>

Ref: Example taken from https://www.legislation.gov.uk/eur/2014/319/annex/part/I/adopted/data.xml

Decorated groups

The <DecoratedGroup> element provides a mechanism for adding accolades to blocks of text (usually a right brace). Accolades are very long vertical or horizontal objects that typically occur within tables and are used to “group” content together by visual presentation. The element exists so that the “grouping” concept is held structurally within the XML mark-up and the decoration (normally a brace) can then be auto-generated for output.

Usually a decorated group will be made up of two <GroupItem> elements, the first containing the text of the first half of the content and the second one containing the second half of the content.

The Orientation attribute specifies the orientation of the accolade. The following table is a list of possible values:

Value	Description
leftToRight	Group item 1 on the left, group item 2 on the right, accolade should be output as normal
topToBottom	Group item 1 on the top, group item 2 on the bottom, accolade should be rotated 90 degrees right
bottomToTop	Group item 1 on the bottom, group item 2 on the top, accolade should be rotated 90 degrees left
rightToLeft	Group item 1 on the right, group item 2 on the left, accolade should be flipped from right to left

Sometimes the second half of the content is in an adjacent table cell so grouping of the content is not possible across the cell boundaries. The solution is to use a <GroupItemRef> element instead of <GroupItem>. This uses a Ref attribute to reference an id on the associated cell. An example is given below:

<td rowspan="19" id="t01001">
  <DecoratedGroup Decoration="}" Orientation="leftToRight">
    <GroupItem>
      <P>
        <Text>and Part I of Schedules 2 to 5, 7, 9 to 13 and 17 to 21 to the extent specified in Part II of those Schedules</Text>
      </P>
    </GroupItem>
    <GroupItemRef Ref="t01001"/>
  </DecoratedGroup>
</td>

Ref: Example taken from https://www.legislation.gov.uk/nisr/2000/169/regulation/23/made/data.xml

Note: The content of this element has been reduced to make the example clearer.

See the entry on Decorated groups in the Schema Reference Guide.

Mathematics

Mathematical formulae do occur in legislation (although not frequently). They range from very simple to highly complex and can occur inline or as a block element. The schema therefore permits the embedding of formulae in documents using MathML. MathML is a W3 standard XML format for marking up mathematics that provides comprehensive support for mathematical notation.

Resources

The <Resources> element holds all of the content that is needed by the document but is not part of the main flow of the document or is external to the document, e.g. graphics.

Resources may be held internally or externally.

If the resource is held internally then it may be held as XML content, e.g. SVG for a graphic. Internal versions are held using the <InternalVersion> element. It is expected that an application processing the schema should know how to handle the following namespaces:

• SVG
• XSL:FO
• XHTML
• MathML

The id attribute is used as a unique identifier for the resource.

The following example shows how an SVG resource held internally as XML would be marked up:

<Resources>
  <Resource id="r00001">
    <InternalVersion>
      <XMLcontent>
        <svg i:viewOrigin="80.1851 505.6704" i:rulerOrigin="0 9.765625e-04" i:pageBounds="0 841.8887 595.2754 -9.765625e-04" width="439.54" height="176.852" viewBox="0 0 439.54 176.852" overflow="visible" enable-background="new 0 0 439.54 176.852" xml:space="preserve">
          <metadata>
            <variableSets>
              <variableSet varSetName="binding1" locked="none">
                <variables/>
                <v:sampleDataSets/>
              </variableSet>

Ref: Example taken from uksi_19961686_en (not currently available online in this form)

Note: The content of this element has been reduced to make the example clearer.

The <XMLcontent> element is used to indicate that the content is in XML format. Note that this content does not get parsed.

An internally held resource may also be held in Base64 format, which allows raw binary files to be stored as text. This is done using the <BinaryContent> element. The obvious advantage of holding resources internally is that when transporting a file there are no external files to worry about. A Format attribute can be used to give a hint to a processing application as to the format of the encoded data. The possible values are the same as described for <ExternalVersion> below.

If it is held externally the <ExternalVersion> element can be used. The location of the resource is held in the URI attribute, which should contain a URI. An example is given below:

<Resource id="r00001">
  <ExternalVersion URI="uksi_20051643_en_001.tif" Format="tiff"/>
</Resource>

Ref: Example taken from https://www.legislation.gov.uk/uksi/2005/1643/schedule/1/paragraph/1/made/data.xml

The Format attribute describes the format of the external resource. The following formats are available:

Value	Description
doc	Word document
eps	EPS graphic
gif	GIF graphic
html	HTML document
jpeg	JPEG graphic
mpeg	MPEG video
png	PNG graphic
rtf	Rich Text Format document
svg	SVG graphic
xml	XML document
pdf	PDF document
tiff	TIFF graphic
other	Unspecified format. Note that an application processing the document may not know how to handle the file

For more details, see the Resources entry in the Schema Reference Guide.