AKN4EU Documentation Version 3.0 (2020-03-30) Volume II

AKN4EU Documentation

Version 3.0 (2020-03-30)

Volume II - XML mark-up

PART 1. AKN4EU GUIDELINES ........................................................................................................................... 3

1 PRINCIPLES FOR THE STRUCTURING OF THE TEXT .................................................................................... 4

1.1 THE AKOMA NTOSO PRINCIPLES .................................................................................................................... 4

1.1.1 Categories of content models ............................................................................................................ 4

1.1.2 The families of elements for the structuring of the text .................................................................... 5

1.2 THE AKN4EU USE OF AKOMA NTOSO FAMILIES OF ELEMENTS ............................................................................ 6

1.2.1 General principles .............................................................................................................................. 6

1.2.2 The subparagraph ............................................................................................................................. 7

1.2.3 Figure and table ................................................................................................................................ 7

1.2.4 Structure inside an article ................................................................................................................ 10

1.2.5 The independent point .................................................................................................................... 16

2 THE METADATA PART OF THE AKOMA NTOSO DOCUMENT ................................................................... 20

2.1 THE AKOMA NTOSO OVERALL STRUCTURE OF METADATA ................................................................................. 20

2.2 ATTRIBUTE @SOURCE FOR THE SECTION OF THE METADATA .............................................................................. 20

2.3 THE <IDENTIFICATION> SECTION OF THE METADATA ........................................................................................ 21

2.3.1 FRBRWork/FRBRcountry.................................................................................................................. 21

2.3.2 FRBRWork/FRBRprescriptive ........................................................................................................... 21

2.3.3 FRBRExpression/FRBRlanguage ...................................................................................................... 21

2.4 THE <ANALYSIS> SECTION OF METADATA ....................................................................................................... 22

2.5 THE <REFERENCES> SECTION OF THE METADATA ............................................................................................. 22

3 DOCUMENTS EXCHANGED IN THE CONTEXT OF THE ORDINARY LEGISLATIVE PROCEDURE (OLP) .......... 24

3.1 REGULATION, DIRECTIVE, DECISION AS RESULTS OF THE OLP AND THE RESPECTIVE PROPOSALS - THE <ACT> AND THE

<BILL> 24

3.1.1 The AKN4EU mark-up of the main part of the act ........................................................................... 27

3.1.2 Annexes (<doc name="ANNEX">) .................................................................................................... 39

3.2 THE PROPOSAL FROM THE COMMISSION: <DOCUMENTCOLLECTION NAME="PROP_ACT"> .................................. 44

3.2.1 The overall structure of the document: <documentCollection> ...................................................... 47

3.2.2 The Explanatory Memorandum: <doc name="EXPL_MEMORANDUM"> ....................................... 52

3.2.3 The legal text ................................................................................................................................... 53

3.3 THE EP LEGISLATIVE RESOLUTION (<BILL NAME="RES_LEGIS") ............................................................... 54

3.3.1 <preface> ......................................................................................................................................... 54

4 OTHER DOCUMENTS .............................................................................................................................. 60

4.1 INTERNATIONAL AGREEMENT ...................................................................................................................... 60

4.1.1 <preface> ......................................................................................................................................... 60

4.1.2 Preamble: the <preamble> .............................................................................................................. 61

4.1.3 Enacting terms: the <body> ............................................................................................................ 63

4.1.4 <conclusions> .................................................................................................................................. 63

AKN4EU – Volume II – PART 1 & 2

30/03/2020 Page 2 of 124

5 SEMANTIC INLINE ELEMENTS IN AKN4EU ............................................................................................... 67

5.1 <DATE> .................................................................................................................................................. 67

5.2 <DOCTYPE> ............................................................................................................................................. 67

5.3 <DOCNUMBER> ....................................................................................................................................... 68

5.4 <DOCSTAGE> .......................................................................................................................................... 68

5.5 <DOCPURPOSE> ....................................................................................................................................... 68

5.6 <DOCKETNUMBER> .................................................................................................................................. 69

5.7 <LOCATION>............................................................................................................................................ 69

5.8 <ORGANIZATION> ..................................................................................................................................... 70

5.9 <PERSON> .............................................................................................................................................. 70

5.10 <INLINE NAME="LANGUAGE"> .................................................................................................................... 70

6 AMENDMENTS ....................................................................................................................................... 71

6.1 CASE OF THE AMENDING ACT: AMENDMENTS ................................................................................................. 71

6.1.1 The part of an act that amends another act ................................................................................... 71

6.1.2 The AKN4EU mark-up for the amendment ...................................................................................... 76

6.1.3 Case of the amending Act: text that repeals an act ...................................................................... 103

6.1.4 Case of the amending Act: summary of the amendment mark-up ............................................... 105

7 ELI SYNTAX ........................................................................................................................................... 112

7.1 URI TEMPLATE FOR EUROPEAN UNION LEGISLATION AND PREPARATORY ACTS (DRAFT) ........................................ 112

7.2 REFERENCE TO SUBDIVISION IN ELI URI TEMPLATES (!!! DRAFT !!!) .................................................................. 113

PART 2. .............................................................. CORRESPONDENCE BETWEEN COV 3.0 AND AKN4EU 3.0

115


30/03/2020 Page 3 of 124

PART 1. AKN4EU Guidelines Scope

This part provides an introductory documentation to AKN4EU regarding the XML mark-up. The

definition required for AKN4EU is carried out on two levels:

On the business level, the ‘Common Vocabulary’ (CoV) identifies and describes the semantic

and logical concepts extracted from examples of the exchanged documents.

On the technical level, the OASIS standard Akoma Ntoso is the structured, machine-readable

format used for implementation.

Because Akoma Ntoso is a rather generic standard that is designed to cover a big variety of legal

documents, it has to be defined how the semantic and logical concepts that are described by the CoV

have to be expressed in Akoma Ntoso. In other words, AKN4EU can be considered as the localisation

of Akoma Ntoso for EU legislation.

In the current version, this document is focused on the documents exchanged in the scope of the

Ordinary Legislative Procedure (OLP) and is a result of the ongoing work of the subgroup Format

Guidelines. Therefore, it currently covers the following document types:

Regulation,

Directive,

Decision,

Proposal for a Regulation,

Proposal for a Directive,

Proposal for a Decision.

Legislative Resolution of the European Parliament

In addition to these documents and beyond the OLP, the document type 'International Agreement' is

also included in this release.

In the current version of AKN4EU, the expression of a modification in an amending act is covered as

well as its associated metadata.

At this stage however, the mark-up for codification and recast and the metadata for consolidation

are not covered.


30/03/2020 Page 4 of 124

1 Principles for the structuring of the text This section describes the general principle of Akoma Ntoso for the mark-up of the content of a

document

1.1 The Akoma Ntoso principles

1.1.1 Categories of content models

Akoma Ntoso defines the content model based on ‘categories of content model (‘refer to families of

elements that share the same conceptual organization of the internals’).

As explained in the Akoma Ntoso Version 1.0. Part 1: XML Vocabulary1, there are six categories of

content models:

The markers: markers are content-less elements placed inside the document. Inside the

content, they are meaningful for their position, their names and their attributes. Metadata

are also markers.

The inlines: an inline element is an element to identify a text fragment as relevant for some

reason. (semantic or presentation)

The blocks: a block is a container of text or inlines.

The subFlow: a subFlow element is an element placed within a mixed content element to

identify a completely separate context that, for any reason, appears within the flow of the

text, but does not belong to it or does not follow its rules.

The containers: containers are sequences of specific elements, some of which can be

optional. The shared characteristic of containers is that no text is allowed directly inside

them, but only a collection of other elements.

The hierarchy: a hierarchy is a set of sections nested to an arbitrary depth, usually provided

with title and numbering. No text is allowed directly inside the hierarchy, but only within a

block element that is contained within a container element (not considering, of course, titles

and numbering). Akoma Ntoso uses only one hierarchy, with predefined names and no

constraints on their order or systematic layering.

Therefore, only elements that are inline or block can contain textual content.

1 The Oasis specification is Akoma Ntoso 1.0 and corresponds to the AKN schema 3.0 (namespace

http://docs.oasis-open.org/legaldocml/ns/akn/3.0)


30/03/2020 Page 5 of 124

1.1.2 The families of elements for the structuring of the text

There are two ways to mark up the structure of a text:

The hierarchical family gives names to the different structural elements, making a

correspondence with a functional reference. This family of elements is used to mark-up the

legislative text. A hierarchical element has a <num> and <heading> and up to 3 available

containers :

o the element <intro>, for introductory text, if any;

o either the element <content>, for the content of the element,

or other hierarchical element(s) if the structure is more complex;

The hierarchical element with a sub-element <content> is the last level of named

structure. Inside the <content> element there are block elements containing the

text.

o the element <wrapUp>, for the final block if any.

The hierarchical family contains 27 elements2, but the hierarchical relation between them is

not predefined in the standard. It depends on the legal tradition.

The family of ‘block elements’ enables the marking-up of content but without a clear naming

of the structure elements and with a predefined relation between the elements.

The table below shows the mapping between these two kinds of elements. Here is the informal

correspondence used in AKN4EU:

element for documents elements for legal text content (enacting terms)

tblock title, part, chapter, section, subsection, article

blockList list

item point, indent

listIntroduction intro

listWrapUp wrapUp

p p

2 The elements are: clause, section, part, paragraph, chapter, title, article, book, tome, division, list, point,

indent, alinea, rule, subrule, proviso, subsection, subpart, subparagraph, subchapter, subtitle, subdivision,

subclause, sublist, level, transitional.


30/03/2020 Page 6 of 124

1.2 The AKN4EU use of Akoma Ntoso families of elements

1.2.1 General principles

The hierarchical structure is used for marking up the enacting terms and the annex of an act.

Each block3 of text MUST be inside its own specific hierarchical element, except for the

following:

o the 'heading' and the 'subject' MUST be marked respectively as <num> and

<heading>,

o the introductory part MUST be marked with the <intro> element, available inside

each hierarchical element,

o the closing part MUST be marked up with the element <wrapUp> , available inside

each hierarchical element.

The hierarchical elements are chosen based on the CoV terminology with the following

exception:

o The CoV term 'subparagraph' is marked up as <subparagraph>, <alinea>, <list>

depending on the structure or the location of the subparagraph (see next section).

o Figure or table with heading and subject (and with legend) are marked up with the

<subdivision> element.

Some hierarchical elements can only contain hierarchical sub-elements, others can only

contain the <content> element and some can contain both, on case per case. Concretely:

o <title>, <part>, <chapter>, <section>, <subsection>4, <list>, <article> MUST always

contain hierarchical elements, as they are never the last level of the hierarchy;

o <subparagraph> and <alinea> MUST have <content> as they are always the last level

of the hierarchy;

o <paragraph>, <point> , <indent>, <subdivision> and <level> can have hierarchical

sub-elements or <content> element (never both together).

The generic element <hContainer> with the @name attribute value for the business name of

the structure is not used.

3 "block" is to be understood as "a simple subparagraph, not composed of point, indent and introductory

sentence". We don't use the term "subparagraph" in the text to be more explicit, as one of the hierarchical

element is called <subparagraph>.

4 <subsection> is not used anymore and will only be used for backlog documents.


30/03/2020 Page 7 of 124

1.2.2 The subparagraph

The CoV concept of 'subparagraph' has multiple mark-up counterparts in AKN4EU, depending on its

internal structure or its location. Therefore, 'subparagraph' can be marked up with the following

elements:

<list>

A <list> is a special type of subparagraph composed of

o an optional introductory part (<intro>),

o a sequence of <point> (numbered) or <indent> (unnumbered) and

o an optional closing part (<wrapUp>).

<subparagraph> or <alinea> or <content> The elements <subparagraph> or <alinea> are only used for subparagraphs that comprise a simple block of text.

Both elements MUST only have <content> as the only subelement, which can only contain

one block ( or <table>).

<subparagraph> and <alinea> MUST only be used when there are sibling subparagraphs. In

case there is no sibling subparagraph and the subparagraph is simply a block of text, the

subparagraph MUST be marked up as a <content> element of the parent structure.

<alinea> MUST be used for subparagraph inside <point> or <indent>. <subparagraph> MUST

be used for the other cases (inside <paragraph> or <level>)

1.2.3 Figure and table

1.2.3.1 A simple image

An image is marked with the element <img> and is inside a block element (). It is a marker

element (empty element) with the following attributes:

- @src (mandatory): contains the relative path to the image file;

- @alt (optional): holds the text to be displayed in case the loading of the external resource is

not possible for any reason;

- @title (optional): This attribute contains single value text, which is used as the tooltip text for

an element.

Example

<img src="EC.png" alt="EUROPEAN COMMISSION" title="EUROPEAN COMMISSION"/>

1.2.3.2 A simple table

In Akoma Ntoso, a table is marked with the element <table>. <table> is a block element comprising

sub-elements <tr> (and an optional <caption>). It can be a block element of the <content> element

of a hierarchical element.


30/03/2020 Page 8 of 124

In AKN4EU, the sub-element <caption> MUST NOT be used. See 'Objects with a heading and/or a

subject and/or a legend' on how to mark the subject of a table.

Example

<paragraph>

<content>

<table>

<tr >

<td>2014</td>

<td>EUR</td>

<td>485097840</td>

</tr>

<tr >

<td>2015</td>

<td>EUR</td>

<td>485097840</td>

</tr>

<tr >

<td>2016</td>

<td>EUR</td>

<td>485097840</td>

</tr>

…

</table>

</content>

</paragraph>

1.2.3.3 Objects with a heading and/or a subject and/or a legend

To be able to associate heading and subject to a table or an image, an envelope element is needed to

group the object and its associated heading and subject.

The chosen hierarchical structure is <subdivision> in both cases. The mandatory @refersTo attribute,

which refers to a TLCConcept in the <references> part of the metadata, is used to clarify whether the

<subdivision> relates to an image or a table.

Object TLCConcept

FIGURE <TLCConcept xml:id="_FIGURE"

href="http://publications.europa.eu/resource/subdivision/FIGURE"

showAs="Figure"/>

TABLE <TLCConcept xml:id="_TABLE"

href="http://publications.europa.eu/resource/subdivision/TABLE"

showAs="Table"/>


30/03/2020 Page 9 of 124

Example

Image with heading and optional subject

<subdivision refersTo="~_FIGURE">

<num>Figure 1</num>

<heading>Fish species</heading>

<content>

<img src="…"/>

</content>

</subdivision>

Table with heading and subject

<subdivision refersTo="~_TABLE">

<num>Table A</num>

<heading>Fish species</heading>

<content>

<table>

<tr>

…

</tr>

…

</table>

</content>

</subdivision>


30/03/2020 Page 10 of 124

1.2.4 Structure inside an article

In AKN4EU, an article has the following structure:

An <article> MUST have a heading (<num>) and can have a subject (<heading>).

An <article> MUST be composed of <paragraph>. The paragraph can be numbered (has

<num> element) or not.

An unnumbered paragraph MUST only have one subparagraph.

A numbered paragraph can have one or multiple subparagraphs.

Mark-up of <subparagraph> inside a <paragraph>

When there is only one subparagraph and the subparagraph is a simple block, the content of the subparagraph MUST be inside a in the element <content> of <paragraph>.

When there are multiple subparagraphs, each subparagraph that is a simple block MUST be is in an element <subparagraph>5.

Mark-up of <subparagraph> inside a <point> or an <indent>

See above, section "The subparagraph"

5 So <subparagraph> will never be inside an unnumbered paragraph.


30/03/2020 Page 11 of 124

Examples:

Article with unnumbered <paragraph>

is marked up as follows:

<article>

<num>Article 7</num>

<heading>Financial support</heading>

<paragraph>

<content>The Commission …</content>

</paragraph>

<paragraph>

<list>

… </list>

</paragraph>

<paragraph>

<content>The Commission shall evaluate …</content>

</paragraph>

</article>


30/03/2020 Page 12 of 124

Numbered <paragraph> with <subparagraph>


<paragraph><num>2.</num>

<subparagraph>

<content>…</content>

</subparagraph>

<subparagraph>


</subparagraph>

<subparagraph>


</subparagraph>

</paragraph>

Numbered <paragraph> with a <list>; <alinea> inside <point>


30/03/2020 Page 13 of 124


<list>

<intro>… </intro>

<point><num>(a)</num>


</point>

<point><num>(b)</num>


</point>

<point><num>(c)</num>


</point>

<point><num>(d)</num>

<alinea>

<content>in the case of …</content>

</alinea>

<alinea>

<content>Where the legal person …</content>

</alinea>

</point>

<point><num>(e)</num>


</point>

</list>

Numbered paragraph with a mix of <subparagraph> and <list>


<paragraph><num>3.</num>

<subparagraph>

<content>

Where a Member State …

</content>

</subparagraph>

<list>

<intro>

That summary shall contain …:


30/03/2020 Page 14 of 124

</intro>


<content>

its subject matter;

</content>

</point>


<content>

its aim and the scope;

</content>

</point>

<point><num>(c)</num>

<content>

its duration;

</content>

</point>

<point><num>(d)</num>

<content>

the parties thereto;

</content>

</point>

<point><num>(e)</num>

<content>

information on the main elements thereof.

</content>

</point>

</list>

<subparagraph>

<content>

This paragraph shall not apply to …

</content>

</subparagraph>

</paragraph>

List with introductory part and closing part


<point>

<num>(1)</num>

<list>

<intro>

‘intergovernmental agreement’ means any legally binding agreement,

regardless of its formal designation, between one or more Member States and one or

more third countries, or between one or more Member States and an international

organisation, which concerns: </intro>


<content>

the purchase, trade, sale, transit, storage or supply of energy in or to

at least one Member State; or

</content>

</point>


30/03/2020 Page 15 of 124


<content>

the construction or operation of energy infrastructure with a physical

connection to at least one Member State;

</content>

</point>

<wrapUp>

however, where such a legally binding agreement also covers issues other

than those referred to in points (a) and (b), only the provisions relating to those

points and the general provisions applicable to those energy-related provisions,

are deemed to constitute an intergovernmental agreement;

</wrapUp>

</list>

</point>


30/03/2020 Page 16 of 124

1.2.5 The independent point

The independent point is not present in the enacting terms of EU acts but is quite frequent inside

annexes. The characteristics of this structure are the following:

The independent point is not part of a list and it cannot be included inside another independent

point or inside a lower level structure.

The independent point can be part of high-level structure like title, part, chapter or section.

Independent points have a particular numbering system (decimal numbering) in order to

represent the relationships between them (see next point). Such decimal numbering is composed

of one or more numbers. Two numbers are separated by a dot, with the first number indicating

the first level point, the second number the second level and so on.

Following that definition, ‘”point 1.1” indicates that the point is related to ‘point 1’. However,

‘point 1.1’ cannot be considered as a sub-point of ‘point 1’ because it is in reality an independent

point. In terms of hierarchy in the document structure they are in fact siblings.

The independent point is marked up with the element <level>.

1.2.5.1 The subject of independent points

An independent point can have a subject that is marked up with the element <heading>.

1.2.5.2 The structure of independent points

A <level> can comprise:

a heading (<num>), mandatory

a subject (<heading>), optional

one of these two cases:

<content> if the structure of a <level> is simple

one or multiple occurrences of these elements:

o <subparagraph> for a simple block, when there are multiple blocks,

o <list> for each block composed of points/indents with an optional introductory

part

o <subdivision>

- for each block composed of a table with heading and/or subject

- for each block composed of a figure (image with heading and/or subject

and/or legend).


30/03/2020 Page 17 of 124

Example:

<level>

<num>4.2</num>

<list>

<intro>

At the second and subsequent stages, in addition to the statutory plate

prescribed by Regulation (EU) No 19/2011, …:

</intro>

<indent><num>—</num>

<content>

the name of the manufacturer;

</content>

</indent>

...

</list>

<subparagraph>

<content>

Unless otherwise provided for in point 4.1 and this point the

additional plate shall comply with the requirements set out in Annex I and Annex II to

Regulation (EU) No 19/2011.

</content>

</subparagraph>

</level>

Consequently, the <level> element can have the following structure:

1.2.5.2.1 <level> with <content>

<level>

<num>…</num>

<content>…</content>

</level>

Example:

<level>

<num>1.</num>

<content>

Internal production control is the conformity assessment procedure

whereby the manufacturer fulfils the obligations laid down in points 2, 3 and 4,

and ensures and declares on his sole responsibility that the PPE concerned

satisfies the applicable requirements of this Regulation.

</content>

</level>


30/03/2020 Page 18 of 124

1.2.5.2.2 <level> with only a subject

<level>

<num>…</num>

<heading>…</heading>

</level>

Example:

<level>

<num>4.</num>

<heading>CE marking and EU declaration of conformity</heading>

</level>

1.2.5.2.3 <level> with subject and <content>

<level>

<num>…</num>


<content>…</content>

</level>

Example:

<level>

<num>2.</num>

<heading>Technical documentation</heading>

<content>

The manufacturer shall establish the technical documentation described

in Annex III.

</content>

</level>

1.2.5.2.4 <level> with <subparagraph>

<level>

<num>…</num>

<subparagraph>…</subparagraph>

<subparagraph>…</subparagraph>

</level>

Example

<level>

<num>4.2.</num>

<subparagraph>

<content>

The manufacturer shall draw up a written EU declaration of

conformity for a PPE model and keep it, together with the technical documentation,

at the disposal of the national authorities for 10 years after the PPE has been

placed on the market. The EU declaration of conformity shall identify the PPE for

which it has been drawn up.

</content>

</subparagraph>

<subparagraph>

<content>

A copy of the EU declaration of conformity shall be made available


30/03/2020 Page 19 of 124

to the relevant authorities upon request.

</content>

</subparagraph>

</level>

1.2.5.2.5 <level> with subject and <subparagraph>

<level>


< subparagraph >…</ subparagraph >

< subparagraph >…</ subparagraph >

</level>

Rules

<subparagraph> MUST always have a sibling <subparagraph> or <list> or <subdivision> (it

MUST only be used in case of multiple subparagraphs).

When the independent point is composed of a subject and only one simple

subparagraph, the element <subparagraph> MUST NOT be used: the simple

subparagraph is in a <content> element.

When the independent point has one subparagraph composed of points, the

subparagraph MUST be marked with a <list> element. No <content> element is present.

When the independent point has one subparagraph composed of a table with heading

and subject or an image with heading, subject and/or legend, the subparagraph MUST be

marked with the <subdivision> element. No <content> element is present.


30/03/2020 Page 20 of 124

2 The metadata part of the Akoma Ntoso document

2.1 The Akoma Ntoso overall structure of metadata

Every Akoma Ntoso document has a section <meta> containing all the metadata regarding the

document. Each metadata element is a marker.

The block <meta> is composed of different main sections; only the sections in bold are currently

used.

identification The <identification> contains all the metadata needed to identify the

document (uri, date, author, language, format etc.)

It is a mandatory section.

publication This section contains the information regarding the official publication of an act.

classification This section contains the keywords defined for this document.

lifecycle

workflow This section contains the events in the legislative process.

analysis This section contains assertions on the text.

The metadata regarding the amendments contained in the document

as well as the information regarding the changes inside the document

(consolidation version) are grouped in this section.

temporalData definition of time interval

references external resources connected with the document

notes editorial annotations

proprietary proprietary metadata

presentation information regarding the rendering of the document

2.2 Attribute @source for the section of the metadata

According to Akoma Ntoso specifications,

‘Editors (i.e., the creators of the FRBR Manifestation) have two main tasks in the production

process of Akoma Ntoso documents: on the one hand to identify and label (i.e., mark up) the

fragments of the original content according to their role and structure, and on the other, to

provide additional information about the document itself that is not contained in the official

text as created by the original author.

Collectively, this additional information is called metadata. Since these are metadata

elements, and since they are added at markup time, their specification is an editorial process,

and not an authorial process, and come under the responsibility of the creator of the

markup.’


30/03/2020 Page 21 of 124

For this reason, each section of the metadata has an attribute @source, containing the information

on the provider of the section.

In AKN4EU, the attribute @source MUST contain the reference to the TLCOrganization entry

corresponding to the responsible organisation that completes this section.

The element TLCOrganization has a mandatory attribute @href with, as value, the URI of the

corresponding entry in the authority table ‘Corporate Body’

(https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/corporate-

body).

Example:

<identification source="~_PUBL">

…

<references source="~_PUBL">

<TLCOrganization xml:id="_PUBL"

href="http://publications.europa.eu/resource/authority/corporate-body/PUBL"

showAs="Publications Office"/>

…

2.3 The <identification> section of the metadata

In this version of AKN4EU, only the following information is provided:

2.3.1 FRBRWork/FRBRcountry

For the EU legislation, the value MUST be "EU":

<FRBRcountry value="EU"/>

2.3.2 FRBRWork/FRBRprescriptive

This element is mandatory in the context of AKN4EU and provides information on which

subdocument of a document collection like a "Proposal for an act" is part of a bill.

For example, the Explanatory Memorandum MUST have FRBRprescriptive set to false, whereas a bill

and annex, or appendices to a bill MUST have FRBRprescriptive set to true.

2.3.3 FRBRExpression/FRBRlanguage

The attribute @language contains the language of the document.

The EU documents display the language in a two-letter code, following the rules and conventions of

the Interinstitutional style guide (http://publications.europa.eu/code/en/en-000100.htm).

For this reason, the attribute @language MUST contain the two-letter code of the language of the

XML document.

However, AKN4EU defines a method to provide the correspondence between the two-letter and the

three-letter code of the language from the authority table 'Language'6:

6 https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/language


30/03/2020 Page 22 of 124

In the references section of the metadata, a TLCReference entry MUST be provided, giving the

information on the three-letter code. The @showAs of this element MUST be the corresponding two-

letter code of the language.

Example:

<FRBRlanguage language="en"/>

...

<references source="…">

<TLCReference name="language"

href="http://publications.europa.eu/resource/authority/language/ENG"

showAs="en"/>

2.4 The <analysis> section of metadata

For the current use of this section of the metadata, see the section on amendments and the section

concerning the repeal of an act.

2.5 The <references> section of the metadata

The references section contains entries pointing to the ontology.

The types of references are the following:

Type of reference Mark-up

Act amended (to be related with the

<activeModifications> metadata)

See the section concerning amendments

<activeRef>

Type of act <TLCReference name="docType">

Subject <TLCReference name="contentSubject">

Location <TLCLocation>

Institution or other organisation <TLCOrganization>

Role <TLCRole>

Language <TLCReference name="language">

TLCConcept

The content of a subdivision of text

The type of a subdivision of text

Other references. Currently

subdivision-content

subdivisions

Examples:

<TLCReference xml:id="_REG" name="docType"

href="http://publications.europa.eu/resource/authority/resource-type/REG"

showAs="Regulation"/>

<TLCLocation xml:id="_BEL_BRU"

href="http://publications.europa.eu/resource/authority/place/BEL_BRU"

showAs="Brussels"/>


30/03/2020 Page 23 of 124

<TLCOrganization xml:id="_CONSIL"

href="http://publications.europa.eu/resource/authority/corporate-body/CONSIL"

showAs="Council of the European Union"/>

<TLCOrganization xml:id="_EP"

href="http://publications.europa.eu/resource/authority/corporate-body/EP"

showAs="European Parliament"/>

<TLCRole xml:id="_PRESID"

href="http://publications.europa.eu/resource/authority/role/PRESID"

showAs="President"/>


30/03/2020 Page 24 of 124

3 Documents exchanged in the context of the Ordinary

Legislative Procedure (OLP)

3.1 Regulation, Directive, Decision as results of the OLP and the

respective proposals - the <act> and the <bill>

The following three document types are considered ‘acts’ in Akoma Ntoso7:

Regulation,

Directive and

Decision.

These document types are very similar in structure, which can thus be described as follows.

NB: In the rest of the document ‘act’ is used as synonym for one of these three document types.

The Proposal for a Regulation, the Proposal for a Directive and the Proposal for a Decision are the

documents of the Commission that initiate an OLP. They contain a draft version of what may

become, at the end of the legislative procedure, an act. Therefore, the structure of this draft version

is very similar to the structure of the final act. For this reason, the description of the act in this

section of the documentation is also applicable to the legal text inside a Proposal.

NB: In the rest of the document ‘Proposal from the Commission’ or ‘Proposal for an act’ are used as a

synonym for ‘Proposal for a Regulation’, ‘Proposal for a Directive’ or ‘Proposal for a Decision’.

Similarly, this description is applicable to the ‘EP Consolidated text’ which marks the Position of the

European Parliament regarding the legal text included in the Proposal from the Commission. It is, in

fact, a new version of this legal text, in form of a text consolidating all amendments adopted by the

Parliament (with all the changes appropriately marked).

NB: In the rest of the document ‘legal text’ is used for the proposal of an act, which is contained for

example, inside a Proposal for an act or in the Texts Adopted of the Parliament.

Akoma Ntoso uses two elements to mark up a legal text:

<act>, for the final version that is published in the Official Journal;

<bill>, for the draft version that is comprised in the proposal initiating the legislative

procedure that can lead to the adoption of the act.

The legal text that constitutes an act MUST be marked up with the element <act>.

The legal text contained in the Proposal from the Commission or in the ‘EP Consolidated text’

(Position of the European Parliament) MUST be marked up with the element <bill>.

These elements <act> and <bill> have a mandatory attribute @name that defines the type of act.

In AKN4EU, the value of this attribute MUST be the code of an entry of the Named Authority List

‘Resource type’ (https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-

/resource/dataset/resource-type).

7 An act, in Akoma Ntoso is a normative document.


30/03/2020 Page 25 of 124

The following values for the attribute @name are used:

Value of the attribute @name

for <act> or <bill>

Description

"REG" - Regulation

- Legal text of the Proposal for a Regulation.

"DIR" - Directive

- Legal text of the Proposal for a Directive.

"DEC" - Decision

- Legal text of the Proposal for a Decision.

This section describes the mark-up for the following components:

(a) A Decision, Directive or Regulation (resulting from on Ordinary Legislative Procedure) and

published in the Official Journal:

(b) The legal text of the Proposal from the Commission:


30/03/2020 Page 26 of 124

(c) The Position of the European Parliament (‘EP Consolidated text’) of the Texts Adopted.


30/03/2020 Page 27 of 124

3.1.1 The AKN4EU mark-up of the main part of the act

The main part of the act has the following structure:

CoV

terminology

Regulation

Example AKN4EU

elements

<act

name="REG">

title

preamble

enacting terms

signature

<preface>

<longTitle>

<preamble>

<body>

<conclusions>

REGULATION (EU) 2017/1938 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL

of 25 October 2017 concerning measures to safeguard the security of gas supply

and repealing Regulation (EU) No 994/2010 (Text with EEA relevance)

THE EUROPEAN PARLIAMENT AND THE COUNCIL OF THE EUROPEAN UNION, Having regard to the Treaty on the Functioning of the European Union, and in particular Article 194(2) thereof, Having regard to the proposal from the European Commission, … Acting in accordance with the ordinary legislative procedure (2), Whereas:

(1) Natural gas (gas) remains an essential component of the energy supply of the Union. A large proportion of such gas is imported into the Union from third countries.

… HAVE ADOPTED THIS REGULATION:

Article 1 Subject matter

This Regulation establishes provisions aiming to safeguard the security of gas supply in the Union by ensuring the … This Regulation shall be binding in its entirety and directly applicable in all Member States.

Done at Strasbourg, 25 October 2017. For the European Parliament For the Council The President The President A. TAJANI M. MAASIKAS


30/03/2020 Page 28 of 124

Akoma Ntoso requires in any documents a first container <meta> grouping all metadata associated

with the document (see the section ‘The metadata part of the Akoma Ntoso document’).

3.1.1.1 <preface>

The preface contains the title of the act as well as additional information like for example the

indication of "EEA relevance".

The title itself MUST be marked up with the element <longTitle>. Additional information MUST be

marked up with the element <container>.

3.1.1.1.1 Title of an act: the <longTitle>

The <longTitle> MUST contain only one .

The contains the following inline elements:

elements in <longTitle> Description

<docStage> The line comprising the information that the document is a proposal or the fragment that indicates that the document is the Position of the European Parliament. It MUST only used if the text is marked as a <bill>.

<docType> The line containing the type of the act. The attribute @refersTo, (mandatory for act and bill), contains the reference of the TLCReference related to the type of the act.

<docNumber> The number of the act.

<date> The date of the act. The mandatory attribute @date contains the date in normalized format.

<docPurpose> The subject of the act. The <docPurpose> can have the following sub-elements :

<ref> Marks the reference to an act mentioned in the subject of the current act. The mandatory attribute @href contains the ELI identifier of that act.

<mref> The fragment of the <docPurpose> that is common to multiple references to an act.


30/03/2020 Page 29 of 124

3.1.1.1.1.1 Examples

For an act:

<longTitle>

<docType @refersTo="~_REG">Regulation <docNumber>(EU) No

1384/2014</docNumber> of the European Parliament and of the Council</docType>

of <date date="2014-12-18"> 18 December 2014</date>

<docPurpose>on the tariff treatment for goods originating in

Ecuador</docPurpose>

</longTitle>

For the legal text of a Proposal from the Commission:

<longTitle>

<docStage>Proposal for a</docStage>

<docType @refersTo="~_REG">Regulation of the European Parliament and of the

Council</docType>


Ecuador</docPurpose>

</longTitle>

NB: The references section of the <meta> element must comprise the corresponding TLCReference. For the above example, it will be: <meta>

…

<references>


href="http://publications.europa.eu/resource/authority/resource-type/REG"


</references>

</meta>

3.1.1.1.1.2 <ref> and <mref>.

(a) All references to one or more other acts in the title of an act is marked with the <ref> element. The mandatory attribute @href contains the ELI identifier of the act. For <act>, this mark-up MUST be present. For the bill, this mark-up SHOULD be used.

For example: <longTitle>

<docType @refersTo="~_REG">REGULATION <docNumber>(EU) No

254/2014</docNumber> OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL</docType>

of <date date="2014-02-26">26 February 2014</date>

<docPurpose>on a multiannual consumer programme for the years 2014-20 and

repealing <ref href="http://data.europa.eu/eli/dec/2006/1926">Decision No

1926/2006/EC</ref></docPurpose>

</longTitle>

(b) When multiple references are grouped in such a way that they cannot be easily separated,

because a part of reference – common to all of them – is mentioned only once, an <mref> element MUST be used to mark the whole span (common part and specific part).


30/03/2020 Page 30 of 124

For example: <longTitle>

<docType @refersTo="~_REG">REGULATION <docNumber>(EU) No

254/2014</docNumber> OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL</docType>

of <date date="2014-02-26">26 February 2014</date>


repealing <mref>Council Directives <ref

href="http://data.europa.eu/eli/dir/1991/672">91/672/EEC</ref> and <ref

href="http://data.europa.eu/eli/dir/50/1926">96/50/EC</ref></mref></docPurpose>

</longTitle>

For the syntax of ELI, see the corresponding section.

3.1.1.1.2 <container>

The other pieces of information of the preface are grouped in <container> elements.

The element <container> has a mandatory attribute @name to define the type of information inside

the container.

For this attribute @name of the element <container>, currently the following values are defined:

<container>

value of attribute

@name

Description

eeaRelevance Contains the indication that the EEA relevance is applicable to the text.

Example:

<container name="eeaRelevance">

(Text with EEA relevance)

</container>

procedureIdentifier Contains the identifier and the type of the legislative procedure.

Example:

<container name="procedureIdentifier">

<docketNumber>2016/0411 (COD)</docketNumber>

</container>


30/03/2020 Page 31 of 124

3.1.1.2 Preamble: the <preamble>

The preamble contains the citations, the recitals and the solemn forms that precede and follow

them.

The mark-up of the different parts is the following:

3.1.1.2.1 <formula>

<formula> is used for the solemn forms. It has a mandatory attribute @name with the following

values:

<formula>

value of attribute @name

Description

actingEntity <formula> at the beginning of the preamble, indicating the acting

entities.

enactingFormula <formula> at the end of the preamble.

Example:

<formula name="actingEntity">

THE EUROPEAN PARLIAMENT AND THE COUNCIL OF THE EUROPEAN UNION,

</formula>

<formula name="enactingFormula">

HAVE ADOPTED THIS REGULATION:

</formula>

3.1.1.2.2 <citations>

The <citations> element is a wrapper that groups a sequence of elements <citation> (one occurrence

for each citation).

When a citation has the attribute @refersTo with the value"~_legalBasis" it is the citation

indicating the legal basis of the act.

When the value of the attribute @refersTo is "~_legalBasis", the <references> part of the metadata

MUST have the following entry with a reference to the legal basis in the eurovoc authority tables:

<meta>

<TLCReference xml:id="_legalBasis" name="contentSubject"

href="http://eurovoc.europa.eu/5456" showAs="Legal basis"/>

<meta>


30/03/2020 Page 32 of 124

Example:

<citations>

<citation refersTo="~_legalBasis">

Having regard to the Treaty on the Functioning

of the European Union, and in particular Article 207(2) thereof,

</citation>

<citation>

Having regard to the proposal from the European Commission,

</citation>

<citation>

After transmission of the draft legislative act to the national

Parliaments,

</citation>

<citation>

Acting in accordance with the ordinary legislative procedure<authorialNote

marker="1" placement="bottom">Position of the European Parliament of <date

date="2015-02-26">26 February 2014</date> and position of the Council at first

reading of <date date="2015-12-10">810 December 2015</date>.

</authorialNote>,

</citation>

</citations>

3.1.1.2.3 <recitals>

The element <recitals> is a wrapper that groups all recitals. It can contain an introductory text

(generally 'Whereas :')9, marked as <intro> and one or more recitals (<recital>).

Each recital is numbered so the element <recital> MUST start with a <num> element.

Example:

<recitals>

<intro>Whereas:</intro>

<recital>

<num>(1)</num>

A number of amendments are to be made to Directive 2002/92/EC of

the European Parliament and of the Council<authorialNote placement="bottom"

marker="3">Directive 2002/92/EC of the European Parliament and of the Council of

<date date="2002-12-09">9 December 2002</date> on insurance mediation (OJ L 9,

15.1.2003, p. 3).</authorialNote>. In the interests of clarity, that Directive

should be recast.

</recital>

...

</recitals>

8 The element <date> outside the <preface> or the <conclusions> is generally an optional mark-up.

9 When there is only one recital, the introductory text is not present in the EU acts.


30/03/2020 Page 33 of 124

3.1.1.3 Enacting terms: the <body>

This element contains the enacting terms of the act or bill.

The normative unit of the enacting terms in the EU legislation is the article, numbered continuously10

from the beginning of the enacting terms. It is marked with the element <article>.

Above the <article>, higher hierarchical divisions are possible:

<title>

<part>

<chapter>

<section>

<subsection>11

All these elements are hierarchical elements. In Akoma Ntoso, these elements are used for the

representation of the structure of the enacting terms.

3.1.1.3.1 <article>

In the legal acts of the European Union, an article is composed of numbered or unnumbered

paragraphs. These paragraphs MUST be marked with the element <paragraph>.

The sub-elements of <article> MUST only be from the following:

Sub-element of

<article>

Description

<num> Defines the number of the article.

<heading> Subject of the article.

<paragraph> A numbered or unnumbered paragraph.

The numbered paragraph starts with a <num> sub-element.

10

"Continuously" means that the number of the article is incremented along the document regardless of the

higher structure containing the article (e.g. no initiation of article numbering at the beginning of each chapter).

This is different to the numbering of the paragraphs, which are numbered discontinuously (re-initialisation

within each article).

11 This division remains only for historical reason but is not used anymore.


30/03/2020 Page 34 of 124

Example:

<article>


<heading>Tariff treatment</heading>

<paragraph>

<num>1.</num>

<content>

Customs duties applied to goods originating in Ecuador on <date

date="2014-12-12">12 December 2014</date> shall not be increased and no new customs

duties introduced after that date shall be applied to those goods.

</content>

</paragraph>

<paragraph>

<num>2.</num>

<content>

The tariff treatment provided for in paragraph 1 shall be applied

without prejudice to any measures taken under Regulations (EC) No 260/2009, (EC) No

597/2009 or (EC) No 1225/2009.

</content>

</paragraph>

</article>

The structure inside the paragraph was described earlier.

Articles on definitions and articles with amendments

In the Joint Handbook, a special style is required for the numbering of points in articles on definitions

and in amending provisions:

‘By way of exception, in the article on definitions (see point C.7) and in amending provisions

(see point C.9.1), the numbering of points starts with Arabic numerals within brackets for the

first level and continues with lower-case letters within brackets, small Roman numerals within

brackets and indents.’

This information is marked up with the @refersTo pointing to an entry of the references section of

the metadata.

Every <article> element, that is an 'article on definition' or an 'article with amending provisions',

MUST have the @refersTo attribute set with a reference to the corresponding entry in the references

section.

The following entry are defined:

Value of

@refersTo

Corresponding entry in the references section of metadata

~_ART_DEF <TLCConcept xml:id="_ART_DEF"

href="http://publications.europa.eu/resource/subdivision-

content/ART_DEF" showAs="Article on definitions"/>

~_ART_AMEND <TLCConcept xml:id="_ART_AMEND"

href="http://publications.europa.eu/resource/subdivision-

content/ART_AMEND" showAs="Article with amending provisions"/>


30/03/2020 Page 35 of 124

Example

<article refersTo="~_ART_DEF">

<num>Article 1</num> <heading>Definitions</heading>

…

</article>

3.1.1.3.2 <title><part><chapter><section><subsection>

As all elements representing an higher subdivision of text have the same structure, they are grouped

in this section.

These elements contain:

- a text providing the numbering of this structure that is associated with the parent structure,

- the subject of the structure,

- articles or sub-structures.

The official documentation12 prescribes an order for the use of these elements, which in practice has

not always been respected in the past.

Example:

<title>

<num>TITLE I</num>

<heading>SCOPE, DEFINITIONS AND GENERAL PRINCIPLES</heading>

<chapter>

<num>CHAPTER I</num>

<heading>Scope and definitions</heading>

<section>

<num>Section 1</num>

<heading>Subject-matter and definitions</heading>

<article>


<heading>Subject-matter and scope</heading>

<paragraph>

<num>1.</num>

<content>

This Directive establishes rules on the procedures for

procurement by contracting authorities with respect to public contracts as well as

design contests, whose value is estimated to be not less than the thresholds laid

down in Article 4.

</content>

</paragraph>

<paragraph>

<num>2.</num>

<content>

Procurement within the meaning of this Directive is the

acquisition by means of a public contract of works, supplies or services by one or

more contracting authorities from economic operators chosen by those contracting

authorities, whether or not the works, supplies or services are intended for a

public purpose.

</content>

</paragraph>

...

</article>

...

</section>

12

Joint Practical Guide (2015) § 15.4


30/03/2020 Page 36 of 124

</chapter>

</title>

3.1.1.3.3 The direct applicability: the <clause>

The body of a Regulation MUST end with a special formula expressing the direct applicability of the Regulation. This text is outside any <article>, but inside the <body>. It MUST be marked with the element <clause>. Example: <clause>

<content>

This Regulation shall be binding in its entirety and directly applicable

in all Member States.

</content>

</clause>


30/03/2020 Page 37 of 124

3.1.1.4 Signature: the <conclusions>

This element marks up the information corresponding to the signature of the document: the

location, date and signature.

3.1.1.4.1 <references> section of the metadata for the <conclusions>

For the conclusions, the <references> part of the metadata must contain the following entries:

a <TLCLocation> for the location (authority table ‘Place’13).

<meta>

…



showAs="Brussels"/>

…

</meta>

a <TLCOrganization> for each institution that signs or will sign the act/bill. For an Ordinary Legislative Procedure, it will be the European Parliament and the Council (authority table ‘Corporate body’ 14).

<meta>

…

<TLCOrganization xml:id="_CONSIL"

href="http://publications.europa.eu/resource/authority/corporate-body/CONSIL"

showAs="Council of the European Union"/>




…

</meta>

a <TLCRole> for the role of the signatory (authority table ‘Role’15)

<meta>

…

<TLCRole xml:id="_PRESID"

href="http://publications.europa.eu/resource/authority/role/PRESID"

showAs="President"/>

…

</meta>

13

https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/place

14 https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/corporate-body

15 https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/role

https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/role


30/03/2020 Page 38 of 124

3.1.1.4.2 Structure of <conclusions>

The structure of <conclusions> is the following:

- a element contains the text with the location and the date. This element MAY comprise

the following inline elements:

Sub-elements of in

<conclusion>

Description

<location> The location of the signature.

The attribute @refersTo points to a <TLCLocation> in the

<references> part of the metadata containing the corresponding

location.

<date> The date of the signature.

The attribute @date contains the date in the format YYYY-MM-DD.

- a <block> element with the attribute @name which has the value "signatory". The element

<block> MUST contain one or more <signature> elements.

Each <signature> element MUST contain the following sub-elements:

Sub-elements of

<signature>

Description

<organization> The institution of the person who signs the document.

The attribute "refersTo" points to the corresponding

TLCOrganization in the <references> part of the metadata.

<role> The role of the person who signs the document.

The attribute "refersTo" points to the corresponding TLCRole in

the <references> part of the metadata.

<person> The name of the person who signs the document.

The attribute "refersTo" remains empty in this version of AKN4EU.

Example:

<conclusions>

Done at <location refersTo="~_BEL_BRU">Brussels</location>, <date

date="2014-12-18">18 December 2014</date>.

<block name="signatory">

<signature>

<organization refersTo="~_EP">For the European Parliament</organization>

<role refersTo="~_PRESID">The President</role>

<person refersTo="">M. SCHULZ</person>

</signature>

...

</block>

</conclusions>


30/03/2020 Page 39 of 124

3.1.2 Annexes (<doc name="ANNEX">)

Annexes are used to present material separately from the body of the enacting terms, because it is

either voluminous or technical or both.

Annexes are an integral part of an act. When there are multiple annexes, they are numbered in the

order of appearance.

The annexes are marked up with the element <doc>.

<doc> has a mandatory attribute @name. The value of this attribute is:

Value of attribute @name Description

ANNEX This is the generic code issued from the Authority table ‘Resource

type’ available on OP EU Vocabularies website16.

3.1.2.1 <preface>

The preface contains the title of annexes.

The title of an annex is more similar to the title of a chapter or a section than to the title of an act: it

contains the numbering of the annex inside the act/bill and the subject of the annex. Therefore,

instead of the element <longTitle> a specific <container> is used.

<container> has a mandatory attribute @name. The value of this attribute is:


headerOfAnnex The title of the annex.

The <container> MUST be composed of elements <block>. The <block> has a mandatory attribute

@name. The value of this attribute is:


num Mandatory.

The numbering of the annex in the act.

If there is only one annex, only the word "ANNEX", without number.

Else, the word ANNEX with a number.

heading Optional.

The subject of the annex.

16

https://publications.europa.eu/en/web/eu-vocabularies/authority-tables

https://publications.europa.eu/en/web/eu-vocabularies/at-concept-scheme/-/resource/authority/resource-type/?target=Browse


30/03/2020 Page 40 of 124

Example:

<preface>

<container name="headerOfAnnex">

<block name="num">ANNEX I</block>

<block name="heading">TYPES OF ACTIONS</block>

</container>

</preface>

3.1.2.2 <mainBody>

Currently, annexes can have various structures. They differ structurally from the body of the act because they are not composed of articles. The structure of annexes can be composed of 3 levels of elements:

High-level structures, which can group sub-structures, as in the enacting terms of the act: part, title, chapter, section.

An intermediate structure, that can contain: o independent points; o unnumbered paragraphs.

A lower level, grouping all structures available inside paragraphs, using the same rules.

All these structures are optional: for example, an annex can be composed only of unnumbered paragraphs, or it can be composed of independent points with or without sub-structures or of an unnumbered paragraph followed by independent points.

3.1.2.2.1 High level structures

As in the enacting terms of acts, the following elements are available to represent the high-level

structures in annexes:

<title>

<part>

<chapter>

<section>

Example:

<chapter>

<num>CHAPTER I</num>

<heading>Subject matter for the training of staff performing official

controls and other official activities</heading>

…

</chapter>


30/03/2020 Page 41 of 124

Inside a high-level structure, the following structures are available:

other high-level structures, respecting the hierarchical order of higher structures as defined

in the Joint Practical Guide;

independent points; or

unnumbered paragraphs.

3.1.2.2.2 Independent points: element <level>

In AKN4EU, the independent point MUST be marked with the element <level>.

Example:

<mainBody>

<level>

<num>1.</num>

<content>

Obligations of manufacturers

</content>

</level>

<level>

<num>1.1</num>

<content>

The satisfactory operation of the multi-stage type-approval requires

joint action by all the manufacturers concerned. To that end approval authorities

must ensure, before granting first and subsequent stage type-approvals, that

suitable arrangements exist between the relevant manufacturers for the supply and

interchange of documents and information, so that the completed type of vehicle

meets the technical requirements of all the relevant regulatory acts listed in

Annex II. Such information must include details of relevant system, component and

separate technical unit type-approvals and of vehicle parts that form part of the

incomplete vehicle but have not yet been type-approved.

</content>

</level>

<level>

<num>1.2</num>

<content>

Each manufacturer involved in a multi-stage type-approval shall be

responsible for the approval and conformity of production of all systems,

components or separate technical units manufactured or added by that manufacturer

to the previously built stage. The manufacturer of the subsequent stage shall not

be responsible for objects that have been approved in an earlier stage, except

where that manufacturer modifies relevant parts to such an extent that the

previously granted type-approval becomes invalid.

</content>

</level>

<level>

<num>2.</num>

<content>

Obligations of approval authorities

</content>

</level>


30/03/2020 Page 42 of 124

3.1.2.2.3 Unnumbered paragraphs

Like in the enacting terms, the unnumbered paragraph is composed of one subparagraph that can be

simple or can be composed of a list of points or indents with an introductory part, or a table with

heading and/or subject, or a figure with heading and subject and/or legend.

The unnumbered paragraph MUST be marked with the element <paragraph> without subelement

<num>.

The <paragraph> element MUST contain one of these alternatives:

a sub-element <content> if the paragraph is simple;

a sub-element <list> if the paragraph is composed of a list of points with an introductory

part;

a sub-element <subdivision> if the paragraph is composed of a table with heading and

subject or is composed of a figure with heading and subject and/or legend.

Example

<mainBody>

<paragraph>

<list>

<intro>

The national plan shall include the following information:

</intro>

<point>

<num>(a)</num>

<content>

national objectives and reduction targets to eliminate the

use of mercury and mercury compounds;

</content>

</point>

…

</list>

</paragraph>

…

</mainBody>

3.1.2.2.4 Low level structure

3.1.2.2.4.1 Subparagraphs

The lower level structures are the same as in the enacting terms.

As in the enacting terms, the subparagraph can be simple, or it can be composed of:

a sequence of points with introductory part;

a table with a heading and a subject;

a figure with a heading and a subject and/or legend.

See above the section "The subparagraph" for the mark-up rule of subparagraph.

Example


30/03/2020 Page 43 of 124

<level>

<num>4.2.</num>

<subparagraph>

<content>

The manufacturer shall draw up a written EU declaration of

conformity for a PPE model and keep it, together with the technical documentation,

at the disposal of the national authorities for 10 years after the PPE has been

placed on the market. The EU declaration of conformity shall identify the PPE for

which it has been drawn up.

</content>

</subparagraph>

<subparagraph>

<content>

A copy of the EU declaration of conformity shall be made available

to the relevant authorities upon request.

</content>

</subparagraph>

</level>


30/03/2020 Page 44 of 124

3.2 The Proposal from the Commission: <documentCollection

name="PROP_ACT">

A Proposal from the Commission (Proposal for a Regulation, Proposal for a Directive or Proposal for a

Decision) is the document that initiates an OLP procedure.

The proposal is composed of at least two subdocuments:

- an Explanatory Memorandum,

- the legal text: it is the main component of the proposal as it is the first version of what can

become an act at the end of the OLP procedure. The legal text may have annexes.

The logical nesting of documents of the Proposal from the Commission is the following:

The annexes are referenced in the legal text only.

Each box in the image above corresponds to an Akoma Ntoso document in a specific file. 17

17

see the section 4.7 on the specification of the packaging of XML files for more information on the LEG

package.

Proposal from the Commission

Explanatory Memorandum

Legal Text

Annex to the legal text Annex to the legal text


30/03/2020 Page 45 of 124

Taking this into account, the basis structure of a Proposal of the Commission in AKN4EU corresponds

to the following schema:

Physically, each box is a specific file. The all document is a LEG package (a kind of zip file containing

all the files that forms the document). The entry point is always named "main.xml".

Proposal from the Commission

Reference to EM

Reference to legal text

Cover page

Explanatory memorandum (EM)

Legal text

Reference to Annex(es)

Annex


30/03/2020 Page 46 of 124

The overall structure of the Proposal from the Commission is the following:

Proposal for a

Regulation <documentCollection

name="PROP_ACT">

logo

place and date

reference

procedure_ide

ntifier

title of the act

<coverPage>

<container

name="logo">

<container

name="mainDoc">

<block

name="placeAndDate”>

<block

name="reference”>

<container name=

"procedureIdentifier">

<longTitle>

</coverPage>

Explanatory

Memorandum

heading

section

unnumber

ed

paragraph

<longtitle>

<tblock >



<doc

name="EXPL_MEMORANDUM

">

<preface>

--------------------

<mainBody>

Regulation

-------------

Preamble

procedure

identifier

title of the

act

<container name=

"procedureIdentifier">

<longTitle>

<bill name="REG">

<preface>

---------------------

<preamble>

EUROPEAN COMMISSION

Strasbourg, 15.12.2015

COM(2015) 668 final

2015/0306 (COD)

Proposal for a

REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL

on a European travel document for the return of illegally staying third-country

nationals


30/03/2020 Page 47 of 124

3.2.1 The overall structure of the document: <documentCollection>

The proposal from the Commission itself is like a dossier. It contains only the information needed to

display the coverPage of the dossier and the reference to the sub-documents it contains.

The Proposal from the Commission document MUST be marked as a <documentCollection>.

<documentCollection> has a mandatory attribute @name. The value of this attribute is:


PROP_ACT This is the generic code issued from the Named Authority Lists of

the Metadata Registry ‘Resource type’.

NB. The attribute value is therefore the same for a ‘Proposal for a

Regulation’, a ‘Proposal for a Directive’ or a ‘Proposal for a Decision’.

The <documentCollection> for the Proposal of the Commission has the following structure:

a <coverPage> mandatory,

a <collectionBody> mandatory, containing one <component> per subdocuments.

Akoma Ntoso requires in any document a first container <meta> grouping all metadata associated to

the document (see the section ‘The metadata part of the Akoma Ntoso document’).

3.2.1.1 <coverPage>

The element <coverPage> contains all the information for the cover page and MUST have as sub-

elements:

- <longTitle>

This is the title of the proposal.

- <container>

This is a generic element gathering further information. The attribute @name is required and

defines the type of information in this element.

3.2.1.1.1 <longTitle>

The <longTitle> of <documentCollection> has the same structure as the <longTitle> of a <bill>

included in this <documentCollection>.


30/03/2020 Page 48 of 124

3.2.1.1.2 <container>

Each <container> corresponds to a type of information.

The following containers are currently defined:

<container>:


Description

eeaRelevance Indicates the EEA relevance.

Example:

<container name="eeaRelevance"> (Text with EEA relevance) </container>

logo The container comprises the emblem and name of the proposing

entity that is responsible for the document.

The sub element of the container is a single containing at least

one element <img> for the emblem.

mainDoc The information related to the document itself: location, date and

the document reference.

The <container> has two sub-elements :

- <block name="placeAndDate"> containing the place and the

date of the approbation of the document by the proposing

entity,

- <block name="reference"> containing the reference of the

document. The reference is inside a <docNumber>

element.

mainDocLanguage The language of the document.

procedureIdentifier The identifier and the type of the legislative procedure.

The sub-element of the container is a single containing the

information inside a <docketNumber> element.

swdReferences The references to staff working documents e.g. the impact

assessment or the summary impact assessment.


30/03/2020 Page 49 of 124

3.2.1.1.3 The reference to Staff Working Documents

In the cover page of the Proposal from the Commission, there may be cross references to Staff Working Documents (SWD) such as the impact assessment or the summary of the impact assessment.

For example :

<container name="swdReferences">

{<ref href="http://data.europa.eu/eli/swd/2016/27">SWD(2016) 27

final</ref>}


final</ref>}

</container>

Syntax of the ELI identifier used in the @href attribute of <ref> element for cross references18. See the section Syntax of ELI

3.2.1.1.4 <container name="mainDocLanguage">

Generally, the language code of the document can be put in the footer of the coverPage.

This will be marked with a <container> element. The @name MUST have the value

"mainDocLanguage".

The language code inside the text MUST be identified with an <inline> element.

18

Warning: This syntax (eli for preparatory document) is a draft syntax and can evolve.


30/03/2020 Page 50 of 124

The value of the @name attribute MUST be "language"

The <inline> element for the language has a mandatory attribute @refersTo pointing to the

FRBRlanguage metadata.

3.2.1.1.5 Example of <coverPage>

<coverPage>

<container name="logo">



<img

src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAUYAAABVCAYAAAA14k1xAAA19..."

alt="European Commission" title="European Commission"/>



</container>

<container name="mainDoc">

<block name="placeAndDate"><location refersTo="~_BEL_BRU">Brussels</location>,

<date date="2016-02-16">16.2.2016</date></block>

<block name="reference"><docNumber>COM(2016) 53 final</docNumber></block>

</container>

<container name="procedureIdentifier">

<docketNumber>2016/0031 (COD)</docketNumber>

</container>

<longTitle>

<docStage>Proposal for a</docStage>

<docType refersTo="~_DEC">DECISION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL</docType>

<docPurpose>on establishing an information exchange mechanism with regard to

intergovernmental agreements and non-binding instruments between Member States and

third countries in the field of energy and repealing <ref href="http://data.europa.eu/eli/dec/2006/1926">Decision No 1926/2006/EC</ref> </docPurpose>

</longTitle>


(Text with EEA relevance)

</container>

<container name="swdReferences">


final">SWD(2016) 27 final</ref>} 


final</ref>}

</container>

<container name="mainDocLanguage">

<inline name="language" refersTo="~_FRBRlanguage">EN</inline>

</container>

</coverPage>

19

In this example, the image is represented in base64. The content of the image can also be in an external file

referenced by <img>


30/03/2020 Page 51 of 124

3.2.1.2 <collectionBody>

The <collectionBody> contains the reference to the two subdocuments that form the Proposal from

the Commission:

- the Explanatory Memorandum,

- the legal text. If the legal text (marked as a <bill>) has annexes, these annexes are not

referenced in the part <collectionBody> of the <documentCollection> but in the element

<attachments> of the <bill>.

Each reference to a subdocument MUST be in an element <component>. Each <component> MUST

contain only one element <documentRef> with the following attributes:

Attributes of documentRef Value of the attribute

href The reference to the file containing the

document in the LEG package.

showAs The content of the <docType> element in the

<longTitle> of the corresponding subdocument.

Example:

<collectionBody>

<component>

<documentRef href="memorandum_cj4gu25z70002xt16s8i6cy2s.xml"

showAs="Explanatory Memorandum"/>

</component>

<component>

<documentRef href="bill_cj4gu271f0003xt16kwnojitf.xml" showAs="REGULATION

OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL "/>

</component>

</collectionBody>


30/03/2020 Page 52 of 124

3.2.2 The Explanatory Memorandum: <doc

name="EXPL_MEMORANDUM">

The Explanatory Memorandum is a document included in the Proposal of the Commission that

explains the context and the purpose of the proposal.

The Explanatory Memorandum MUST be marked as a <doc> element. This element has a mandatory

attribute @name.

The value of this attribute comes from the corresponding code from the Named Authority List

‘Resource type’ (see https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-

/resource/dataset/resource-type). For Explanatory Memorandum, the code MUST be

Value of the attribute @name Description

EXPL_MEMORANDUM Explanatory Memorandum document.

The Explanatory Memorandum has the following structure:

The <preface> containing the title,

The <mainBody> with the content of the Explanatory Memorandum.

Before these structures, Akoma Ntoso requires an additional <meta> part grouping all metadata

associated to the document (see the section ‘The metadata part of the Akoma Ntoso document’).

3.2.2.1 <preface>

The preface contains the title of the Explanatory Memorandum (which is the type of the document).

The title MUST be in the element <longTitle>.

Example:

<preface>

<longTitle>

<docType>EXPLANATORY MEMORANDUM</docType>

</longTitle>

</preface>

3.2.2.2 <mainBody>

The content of the Explanatory Memorandum is organised in well-defined and standardised

hierarchical structures (referred to by the Common Vocabulary as ‘section’).

However, the Explanatory Memorandum is not a legal text and does not have the structure of a legal

text. Therefore, the hierarchical elements are not used to mark up the content of the Explanatory

Memorandum.

The sections MUST be marked up with the element <tblock>.

The whole content of the section MUST be inside a <blockContainer> element.

https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/resource-type

https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/resource-type


30/03/2020 Page 53 of 124

3.2.2.2.1 The section: <tblock>

Each <tblock> is composed of

a <num> element (the <num> element contains the number of the section or the bullet sign

if the section is not numbered)

a <heading> element containing the subject of the section

its content:

o <blockContainer> or

o multiple <tblock> if the content is composed of nested sections.

3.2.2.2.2 The specific content: <blockContainer>

Each section for which content is allowed MUST have an element <blockContainer>.

The structure of the <blockContainer> is composed of one or more of these elements:



<blockList>, composed of <item>, optionally preceded by a <listIntroduction> (introductory

part) and optionally followed by a <listWrapUp> (conclusion of the list).

table.

Example:

<tblock>

<num>•</num>

<heading>Fundamental rights</heading>

<blockContainer>

Not applicable

</blockContainer>

</tblock>

3.2.3 The legal text

See above, [The outcome of the OLP procedure (Regulation, Directive, Decision) and their drafts - the

<act> and the <bill> ]


30/03/2020 Page 54 of 124

3.3 The EP Legislative Resolution (<bill name="RES_LEGIS")

The European Parliament Legislative Resolution is a document that provides, in a formal way, the

position of the Parliament on a Proposal of the Commission. The Parliament may reject the proposal

as a whole1, approve it without amendments or, most commonly, adopt amendments to the

proposal.

The European Parliament Legislative Resolution is marked as a <bill> element. This element has a

mandatory attribute @name.

The value of this attribute comes from the corresponding code from the Named Authority List

‘Resource type’ (see https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-



RES_LEGIS Legislative Resolution document.

The European Parliament Legislative Resolution has the following structure:

The <preface> containing the title,

The preamble

The <body> that describes the position.

Preseeding these structures, Akoma Ntoso requires an additional <meta> part grouping all metadata

associated to the document (see the section ‘The metadata part of the Akoma Ntoso document’).

3.3.1 <preface>

The preface contains the title of the document as well as additional information like the step in the

legislative procedure, the document number of related document or the procedure number.

The block containing the title MUST be marked up with the element <longTitle>. Additional

information in a specific block MUST be marked up with the element <container>.

3.3.1.1 The <longTitle>

In the Legislative Resolution, additional information on the legislative procedure is provided on the

same line as the title of the document.

In AKN4EU, the title of the document is marked-up with the element <longTitle>. This element is a container of block. As in the Legislative Resolution the title and the complementary information are rendered in the same line, there is a need to separate them:


30/03/2020 Page 55 of 124

Inside the of the <longTitle>, the <docTitle> element MUST be used to group all the content that forms the title of the document (<docType>, <date> and <docPurpose> are sub-elements of this element). Additional <inline> elements can be added at the same level as the <docTitle> for the information that is not part of the title of the document.

The element <inline> has a mandatory attribute @name that is used to define the type of information inside the element.

The contains the following inline elements:

elements in <longTitle> Description

<docTitle> The part of the line that contains the title

<docType> The type of the document. The attribute @refersTo, (mandatory for act and bill), contains the reference of the TLCReference related to the type of the document.

<date> The date of the document. The mandatory attribute @date contains the date in normalized format.

<docPurpose The subject of the document. The <docPurpose> can have the following sub-elements (optional):

<ref> Marks the reference to an act mentioned in the subject of the current document. The mandatory attribute @href contains the ELI identifier of that act.

<mref> The fragment of the <docPurpose> that is common to multiple references to an act.

<inline name="relatedProc"> The part of the line that contains complementary information on the legislative procedure

<ref href=""> <docNumber>

The related document number (in general, the Com document number and the EP number for the Proposal from the Commission. Each document number can be marked with a <ref> element with the @href attribute containing the ELI URI or a <docNumber> element.

<docketNumber> The number of the procedure The @refersTo attribute contains a reference to a TLCReference element with @name=”procedureNumber”


30/03/2020 Page 56 of 124

Examples

<preface>

<longTitle>

<docTitle><docType refersTo="~_RES_LEGIS">European Parliament

Legislative Resolution </docType>

of <date date="2017-11-14">14 November 2017</date>

<docPurpose>on the proposal for a directive of the European Parliament

and of the Council on the recognition of professional qualifications in inland

navigation and repealing <ref href="http://data.europa.eu/eli/dir/96/50">

Council Directive 96/50/EC</ref> and <ref

href="http://data.europa.eu/eli/dir/91/672">Council Directive

91/672/EEC</ref></docPurpose></docTitle>

<inline name="relatedProc">(<docNumber>COM(2016)0082</docNumber> –

<docNumber>C8-0061/2016</docNumber> –<docketNumber

refersTo="~_procedure_2016_50">2016/0050(COD)</docketNumber>)</inline>

</longTitle>

<container name="relatedProc">

<process refersTo="">(Ordinary legislative procedure: first

reading)</process>

</container>

</preface>

or, if the document identifier for the proposal from the Commission is marked as reference (ELI URI):

<preface>

<longTitle>

<docTitle><docType refersTo="~_RES_LEGIS">European Parliament

Legislative Resolution </docType>

of <date date="2017-11-14">14 November 2017</date>

<docPurpose>on the proposal for a directive of the European Parliament

and of the Council on the recognition of professional qualifications in inland

navigation and repealing <ref href="http://data.europa.eu/eli/dir/96/50">Council

Directive 96/50/EC</ref> and <ref

href="http://data.europa.eu/eli/dir/91/672">Council Directive

91/672/EEC</ref></docPurpose></docTitle>

<inline name="relatedProc">(<ref

href="http://data.europa.eu/eli/PROP_ACT/2016/82">COM(2016)0082</ref> –

<docNumber>C8-0061/2016</docNumber> –<docketNumber

refersTo="~_procedure_2016_50">2016/0050(COD)</docketNumber>)</inline>

</longTitle>




</container>

</preface>


30/03/2020 Page 57 of 124

<container>

The other pieces of information of the preface MUST be grouped in <container> elements.

The element <container> has a mandatory attribute @name that is used to define the type of

information inside the container.

Currently for the attribute @name of the element <container> one of the following values MUST be

used:

<container> value of attribute

@name

Description

relatedProc

Contains information on the step of the legislative procedure. The <container> contains one 

The step information in in an element <process>. In this version of AKN4EU, the attribute @refersTo is empty.

Example:




</container>

3.3.1.2 <preamble>

The preamble contains the citations and the solemn form that precedes them.

The mark-up of the different parts is the following:

<formula>

The <formula> MUST be used for the solemn forms. It has a mandatory attribute @name with the

following values:

<formula>


Description

actingEntity <formula> at the beginning of the preamble, indicating the acting

entities.

Example:


The European Parliament,

</formula>


30/03/2020 Page 58 of 124

<citations>

The <citations> element is a wrapper that groups all citations. It can only contain a sequence of

elements <citation> (one occurrence for each citation).

When a citation has the attribute @refersTo with the value "~_legalBasis" it is the citation indicating

the legal basis of the act.

When the value of the attribute @refersTo is "~_legalBasis", the <references> part of the metadata

MUST have the following entry:

<meta>

…

<TLCReference xml:id="_legalBasis" name="contentSubject"

href="http://eurovoc.europa.eu/5456" showAs="Legal basis"/>

…

</meta>

In the Legislative Resolution, each citation starts with a dash.

For this reason, <citation> MUST have a <num> element with this character inside.

Example: (<mref> and <ref> in the example are available optional mark-up enriching the text if

needed)

<citations>

<citation>

<num>–</num>

having regard to the Commission proposal to Parliament and the Council

(COM(2016)0082),

</citation>


<num>–</num>

having regard to <mref><ref

href="http://data.europa.eu/eli/treaty/tfeu_2016/oj/art_294.par_2">Article

294(2)</ref> and <ref

href="http://data.europa.eu/eli/treaty/tfeu_2016/oj/art_91.par_1">Article

91(1)</ref> of the Treaty on the Functioning of the

European Union</mref>, pursuant to which the Commission submitted the proposal to

Parliament (C8 0061/2016),

</citation>


<num>–</num>

having regard to <ref

href="http://data.europa.eu/eli/treaty/tfeu_2016/oj/art_294.par_3">Article 294(3)

of the Treaty on the Functioning of the European Union</ref>,

</citation>

<citation>

<num>–</num>

having regard to the opinion of the European Economic and Social

Committee of 13 July 2016 <authorialNote marker="1" placement="bottom"> OJ C

389, 21.10.2016, p. 93. </authorialNote>,

</citation>

<citation>

<num>–</num>

after consulting the Committee of Regions,

</citation>

</citations>

Inside the citation, the reference to the legal basis is marked up with the element <ref>. The needed

attribute @href contains an ELI reference to the legal basis.


30/03/2020 Page 59 of 124

3.3.1.3 <body>

The content of the European Parliament Legislative Resolution is organised in numbered paragraphs.

Example:

<body>

<paragraph>

<num>1.</num>

<content>

Adopts its position at first reading hereinafter set out; 

</content>

</paragraph>

<paragraph>

<num>2.</num>

<content>

Calls on the Commission to refer the matter to Parliament again if

it replaces, substantially amends or intends to substantially amend its

proposal;

</content>

</paragraph>

<paragraph>

<num>3.</num>

<content>

Instructs its President to forward its position to the Council, the

Commission and the national parliaments.

</content>

</paragraph>

</body>


30/03/2020 Page 60 of 124

4 Other documents

4.1 International Agreement

An International Agreement is marked with the <act> element. This element MUST have an attribute

@name that defines the type of act.

The value of this attribute comes from the corresponding code from the Authority table ‘Resource

type’ (see https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-



AGREE_INTERNATION International Agreement

The International Agreement is structured as an act. It is composed of:

a title,

a preamble with recitals,

the enacting terms containing mainly articles with possibly high level structures to group

them,

a conclusion containing the date and place of the signature, and the signatory.

The present section focuses only on specific features of this type of act, and proposes a mark-up in

Akoma Ntoso.

4.1.1 <preface>

The preface contains the title of the document.

The title of the document MUST be marked using the <longTitle> element.

4.1.1.1 Title of the document: the <longTitle>

This element contains one . The MUST contain the following inline elements:

Elements in <longTitle> Description

<docType> The line containing the type of the act. The attribute @refersTo contains the reference of the TLCReference related to the type of the act.

<docPurpose> Indicates, in the title, the parties involved in the International Agreement.


30/03/2020 Page 61 of 124

Example :

<longTitle>

<docType refersTo="~_AGREE_INTERNATION">STRATEGIC PARTNERSHIP

AGREEMENT</docType>

<docPurpose>between the European Union and its Member States, of the one part,

and Canada, of the other part</docPurpose>

</longTitle>

4.1.2 Preamble: the <preamble>

The preamble is as follows:

- in blue, the heading of the preamble

- in orange, the formulas

- not highlighted: the recitals

4.1.2.1 Heading

The preamble can have a heading.

If this is the case, the title MUST be marked up with a <block> element20. This element has a

mandatory attribute @name. The value of this attribute MUST be:


heading This value indicates that the block is, in fact, a subject and is used when the <heading> element is not available.

20

Akoma Ntoso does not allow a <heading> element as sub-element of <preamble>.


30/03/2020 Page 62 of 124

Example:

<preamble>

<block name="heading">PREAMBLE</block>

…

</preamble>

The preamble contains the recitals and the solemn forms that precede and follow them.

The mark-up for these structures is the following:

4.1.2.2 <formula>

The two <formula> already defined in AKN4EU MUST be used:

@name = "actingEntity"at the beginning of the preamble

Each line of this formula is in a specific 

Example


THE EUROPEAN UNION, hereinafter referred to as ‘the Union’,

and

THE KINGDOM OF BELGIUM,

THE REPUBLIC OF BULGARIA,

THE CZECH REPUBLIC,

…

of the one part, and

 CANADA,

of the other part,

hereinafter jointly referred to as ‘the Parties’,

@name = "enactingFormula"

at the end of the preamble

Example

<formula name="enactingFormula">

HAVE AGREED AS FOLLOWS:

</formula>

4.1.2.3 <recitals>

The preamble contains recitals.

The element <recitals> is a wrapper that groups all recitals. The introductory text is optional.

Each recital MUST be in an element <recital>. The recitals can be without numbering (so <num>

element is not mandatory).


30/03/2020 Page 63 of 124

Example

<recitals>

<recital>

INSPIRED BY the long-standing friendship forged between the people of

Europe and Canada through their extensive historical, cultural, political and

economic links,

</recital>

…

</recitals>

4.1.3 Enacting terms: the <body>

Similar to the enacting terms of EU acts.

NB: Subparagraph with points can be without introductory part.

4.1.4 <conclusions>

4.1.4.1 Overview

- In orange, the place and date

- In blue, the signatory

- In green, the signature

The conclusions can be as follows:

first, a sequence of paragraphs

the place and date in the languages of all the parties

the signatory.


30/03/2020 Page 64 of 124

Overall example:

<conclusions>

This Agreement shall be drawn up in duplicate in the Bulgarian, Croatian,

Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hungarian,

Italian, Latvian, Lithuanian, Maltese, Polish, Portuguese, Romanian, Slovak,

Slovenian, Spanish and Swedish languages, each text being equally authentic.

IN WITNESS WHEREOF, the undersigned, duly authorised thereto, have signed

this Agreement.

… 

… 

…


<signature>

…

</signature>

…

</block>

</conclusions>

4.1.4.2 Place and date

Each linguistic variant of the place and date MUST be marked with a element with the @xml:lang attribute with, as value, the two-letter code of the language of the content.

In each linguistic variant, the <location> identifies the place of the signature and the <date> element

identifies the date of the signature.

Example:

Съставено в <location refersTo="~_BEL_BRU">Брюксел</location> на

<date date="2016-10-30">тридесети октомври през две хиляди и шестнадесета

година</date>.

Hecho en <location refersTo="~_BEL_BRU">Bruselas</location>, el

<date date="2016-10-30">treinta de octubre de dos mil dieciséis</date>.

…

For each value of the @xml:lang attribute, a corresponding <TLCReference name="language"> MUST

be created in the <references> section of the metadata.

For each value of the @refersTo attribute of the <location> element, a corresponding <TLCLocation>

MUST be created in the <references> section of the metadata.

For example:

<meta>

…


href="http://publications.europa.eu/resource/authority/language/BUL"

showAs="bg"/>


href="http://publications.europa.eu/resource/authority/language/SPA"

showAs="es"/>



showAs="Brussels"/>

…

</meta>


30/03/2020 Page 65 of 124

4.1.4.3 Signatory

The signatory MUST be marked with a <block> element. The mandatory @name attribute MUST have the value "signatory". It contains one or more <signature> elements.

For the International Agreement each <signature> element MUST contain the following sub-elements:

Sub-elements of <signature> Description

<organization>

The <organization> to identify the party of the person who signs the document.

The attribute @refersTo MUST point to the corresponding <TLCOrganization> in the <references> part of the metadata.

In case of the International Agreement, the <TLCOrganization> MUST be an entry of the Authority table ‘Country’.

The information is expressed in an official language of the country that the signatory represents. Sometimes, the information can thus be expressed in multiple linguistic versions. In any case, it is not always the language of this Expression and this information remains in the original language.

For this reason, there can be multiple occurrences of <organization> in one <signature>, one for each specific linguistic version.

The following rules apply:

If there are multiple occurrences of <organization> in one <signature>, each <organization> of a same <signature> MUST have the same @refersTo value. It means that it MUST point to the same <TLCOrganization> in the references part of the metadata.

When there are multiple occurrences of <organization>, each occurrence MUST have an @xml:lang attribute with a different value.

A corresponding <TLCReference name="language"> MUST be created.

<person>

The <person> element with an empty @refersTo. This element will contain the image of the handwritten signature.

<remark> Additional information after the handwritten signature.

For example:

<remark xml:lang="fr">Cette signature engage également la

Communauté française, la Communauté flamande, la Communauté

germanophone, la Région wallonne, la Région flamande et la

Région de Bruxelles-Capitale.

</remark>


30/03/2020 Page 66 of 124

Example


<signature>

<organization refersTo="_BEL" xml:lang="nl">Voor het Koninkrijk

België</organization>

<organization refersTo="_BEL" xml:lang="fr">Pour le Royaume de

Belgique</organization>

<organization refersTo="_BEL" xml:lang="de">Für das Königreich

Belgien</organization>

<person refersTo="">

<img src="L_2016329EN.01006001.tif"/>

</person>

<remark xml:lang="nl">Deze handtekening verbindt eveneens de Vlaamse

Gemeenschap, de Franse Gemeenschap, de Duitstalige Gemeenschap, het Vlaamse Gewest,

het Waalse Gewest en het Brussels Hoofdstedelijk Gewest.</remark>

<remark xml:lang="fr">Cette signature engage également la Communauté

française, la Communauté flamande, la Communauté germanophone, la Région wallonne,

la Région flamande et la Région de Bruxelles-Capitale.</remark>

<remark xml:lang="de">Diese Unterschrift bindet zugleich die

Deutschsprachige Gemeinschaft, die Flämische Gemeinschaft, die Französische

Gemeinschaft, die Wallonische Region, die Flämische Region und die Region Brüssel-

Hauptstadt.</remark>

</signature>…

</block>

The corresponding metadata will be:

<meta>

…

<TLCOrganization xml:id="_BEL"

href="http://publications.europa.eu/resource/authority/countries/BEL"

showAs="Kingdom of Belgium"/>


href="http://publications.europa.eu/resource/authority/language/NLD"

showAs="nl"/>


href="http://publications.europa.eu/resource/authority/language/FRA"

showAs="fr"/>


href="http://publications.europa.eu/resource/authority/language/DEU"

showAs="de"/>

…

</meta>


30/03/2020 Page 67 of 124

5 Semantic inline elements in AKN4EU The following elements are used for the mark-up of information in the text:

5.1 <date>

The element <date> marks a date in the text. The mandatory attribute @date MUST contain the date

in a standardized form (yyyy-mm-dd).

NB: for the attribute @date, the value "2999-01-01" means "no date".

Example:

<date date="2014-12-18">18 December 2014</date>

Special meaning of <date>

Context Meaning

preface/longTitle/p/date The date of the current act.

container[@name="mainDoc"]/

block[@name="placeAndDate"]/

date

The date of the current document.

5.2 <docType>

Inside the <longTitle>, the <docType> element provides information on the type of the document or

act.

For <act> and <bill> only, the <docType> element MUST have an attribute @refersTo containing the

reference to an entry of the references section of metadata that contains the type of act in the

authority table ‘Resource type’.

Example

<meta>

<references source="">


href="http://publications.europa.eu/resource/authority/resource-

type/REG"


</references> ...

</meta>

...

<longTitle>

<docType refersTo="~_REG">Regulation <docNumber>(EU) No 1384/2014</docNumber>

of the European Parliament and of the Council</docType>

…


30/03/2020 Page 68 of 124

5.3 <docNumber>

The docNumber is used to mark the identifier of a document.

Example:

<docNumber>COM(2016)818 final</docNumber>

Special meaning of <docNumber>

Context Meaning

preface/longTitle/p/docType/docNumber The number of the current document/act.

container[@name="mainDoc"]/

block[@name="reference"]/docNumber

The number of the current document.

(for example, in the coverPage)

NB: The identifier of another document can be marked with:

a <ref> element with an ELI reference in the @href attribute or

a <docNumber>

5.4 <docStage>

This element MUST only be used for the drafting version of an act (i.e a <bill>) or a document and

provides information regarding the step of this document in a procedure.

Example:

The following example is for a Proposal for an act: it contains the first drafting of a legislation, which

initiates the legislative procedure.

<longTitle>

 <docStage>Proposal for a</docStage>

<docType refersTo="~_REG">Regulation of the European Parliament and of the Council</docType>


Ecuador</docPurpose>



</longTitle>

5.5 <docPurpose>

This element is used to mark the subject of the act or a bill.

Example:

<longTitle>

 <docStage>Proposal for a</docStage>

<docType refersTo="~_REG">Regulation of the European Parliament and of the Council</docType>


Ecuador</docPurpose>



</longTitle>


30/03/2020 Page 69 of 124

5.6 <docketNumber>

This element identifies the number of a legislative procedure.

Example:

<docketNumber refersTo=""21>2016/0411 (COD)</docketNumber>

Special meaning of <docketNumber>

Context Meaning

container[@name="procedureIdentifier"]/

p/docketNumber

Legislative procedure of the current document.

inline [@name="relatedProc"] Legislative procedure of the current document,

(when this information is on the same line as

the title of the document).

5.7 <location>

This element identifies a location in the text.

The attribute @refersTo MUST contain the reference to the TLCLocation entry corresponding to the

location.

Example:

<meta>

…

<references>

...



showAs="Brussels"/>

…

</references>

</meta>

...

Done at <location refersTo="~_BEL_BRU">Brussels</location>, <date date="2014-

12-18">18 December 2014</date>.

21

Proposition for @refersTo attribute : points to the EUR-Lex entry related to the procedure .


30/03/2020 Page 70 of 124

5.8 <organization>

This element identifies an organization in the text. The attribute @refersTo MUST contain the

reference to the TLCOrganization entry corresponding to the organization.

Example

<meta>

<references>

...




...

</references>

</meta>

...

<organization refersTo="~_EP">For the European Parliament</organization>

5.9 <person>

This element identifies a person in the text. The attribute @refersTo MUST remain empty.

5.10 <inline name="language">

Contains a language code.

container[@name="mainDocLanguage"]/

inline[@name="language"] language of the current document


30/03/2020 Page 71 of 124

6 Amendments

6.1 Case of the amending Act: amendments

6.1.1 The part of an act that amends another act

In an amending act, the amendment (the specification of a modification to another act) is always

specified inside a structure, generally a point. In case of multiple amendments, their order follows

the order of the structures affected in the amended act.

Each amendment specifies the location affected in the amended act and the operation to perform on

this fragment.

The points containing an amendment can be grouped by structure of the amended document, such

as for example:

by article

by paragraph of article

by subparagraph

by point.

In practical terms, the standard structure of the amending part of an act is the following:

Structure of the amending act Content

article all the amendments on one act

intermediate points inside the article all the amendments on one structure of an act

where there are multiple amendments on it

last level of point one amendment

Example:


30/03/2020 Page 72 of 124

6.1.1.1 The reference to the amended act

The amending act contains a reference to the amended act. This reference is generally included in

the introductory part introducing all the amendments to this act (see previous example).

The reference inside an act is a reference without information on a precise version of the amended

act.

6.1.1.2 The overall structure of an amendment

The amendment contains:

the description of the amendment (the precise location of the modification inside the

amended act and the operation to apply);

if the amendment is a modification or an addition/insertion of a new subdivision, the 'text of

the amendment', that is:

o the new subdivision(s) of text that replace(s) existing subdivision(s) or is(are)

added/inserted. In these cases, all new subdivisions of one amendment are

encompassed by the same quotation marks;

o when the amendment is a fragment of structure (text or sentence), the old and the

new text are inside their own quotation marks.

Example of amendment:

6.1.1.2.1 The description of the amendment

The description of each amendment is composed of the following components:

6.1.1.2.1.1 The location

The reference is not a complete reference but only the last part of a reference. The complete

reference for the previous example above would be:

Regulation (EU) No 1305/2013, Article 8(1), point (h)(ii)

Description of the amendment

Text of the amendment


30/03/2020 Page 73 of 124

6.1.1.2.1.2 The operation

The operation of the amendment on the amended act can be one of the values of the first ("Text")

column in the table below.

Text Characteristics

is replaced by

are replaced by

Provides the new content for a structure.

is added

are added

Introduces a new structure at the end of the parent structure.

is inserted

are inserted

Introduces a new structure before or in-between the sibling

structures.

is deleted

are deleted

Removes the structure referenced.

6.1.1.2.2 The 'text of the amendment'

The 'text of the amendment' is in the amending act and corresponds to the text to be added, inserted

or which replaces the existing text in the act to be amended.

The text of the amendment is always completely encompassed by quotation marks. Footnotes are

also inside the quoted structure.

Example:

The amendment can be:

on a complete structure,

on text. In this case, the amendment can be general or specific to a particular position. In the

latter case, the amending provision contains also the old word(s) to be replaced.

text of the amendment



30/03/2020 Page 74 of 124

6.1.1.3 The amendment of an annex

6.1.1.3.1 The addition, insertion or replacement of a complete annex

To express the addition, insertion or replacement of an annex, the amending act can have the

following structures:

1. In the enacting terms, an amending provision indicating:

a. the operation to perform;

b. the relevant annex in the amended act; and

c. the annex of the amending act that contains the new annex.

2. An annex of the amending act containing the new annex.

Example:

eli/reg/2019/1155/art_1.pnt_40


30/03/2020 Page 75 of 124

6.1.1.3.2 Modification inside an annex

When only part of an annex is changed, the amendments are described like the amendments to the

enacting terms of an act.

Sometimes, the amendment is expressed completely in the enacting terms, but often the

amendments are expressed in the annex and one provision of the enacting terms provides the

information on:

- The annex(es) that is(are) amended;

- The annex of the amending act that contains all the amendments to the annex(es).

Example:

eli/reg/2017/2393/art_4.par_1.spg_1.pnt_23

6.1.1.3.3 Deletion of an annex

The amending provision is in the enacting terms.

Example:

(42) Annexes VII, VIII and IX are deleted;

6.1.1.3.4 Special cases

6.1.1.3.4.1 Addition of an annex in an act that has only one annex.

When an act has only a single annex, the annex is not numbered.

For adding a new annex, two amending provisions are provided:22

One to assign a number to the existing annex;

One to provide the information on the annex(es) to be added.

Example:

(44) the Annex becomes Annex I;

…

(46) the text set out in the Annex to this Regulation is added as Annex II.

22

A GRITL rule on this is pending.


30/03/2020 Page 76 of 124

6.1.2 The AKN4EU mark-up for the amendment

Akoma Ntoso provides two types of mark-up for amendments:

the mark-up of the text;

the metadata expressing in a standardized wayt he operation to be applied.

6.1.2.1 The reference to the amended act

Inside the text, the reference to the amended act (see 6.1.1.1 The reference to the amended act)

MUST be marked up with the element <affectedDocument>. The @href attribute MUST contain the

ELI URI of the act.

The reference inside an act will be a reference without information on a precise version of the

amended act (a ‘relative’ or ‘virtual reference’, so the ELI URI does not end with "/oj").

Therefore, in the following example:

the mark-up will be as follows:

<affectedDocument href="http://data.europa.eu/eli/reg/2013/1305">Regulation (EU) No

1305/2013</affectedDocument> is amended as follows:

In the amending act, there is no indication of the specific version of the amended act to be modified.

The version to be amended is the version ‘in force’ at the moment in time when the amendment is to

be applied, which is not necessarily the last version published in the Official Journal.

In our example, the amended act Regulation (EU) No 1305/2013 had been modified several times

prior to the modifications stated in the amending act of the example. The OP builds a consolidated

version of the act, i.e. a new Expression of the act after applying the amendments of the successive

amending acts on this act.

For the example amended act Regulation (EU) No 1305/2013 OP had created consolidated versions

with the following dates:

05/02/2018 01/01/2018 20/05/2017 23/05/2015 24/12/2014 25/09/2014 01/01/2014

The consolidated versions do not have legal value, so they cannot be referenced as is in the content

of an act. This is the reason why the value of the @href attribute of the <affectedDocument> MUST

only contains an ELI virtual reference. It corresponds to a reference to a Work.

https://eur-lex.europa.eu/legal-content/EN/AUTO/?uri=CELEX:02013R1305-20180205








30/03/2020 Page 77 of 124

If a reference to the specific consolidation (Expression) exists, it is inserted in the metadata

<activeRef>23, in the <references> section.

According to Akoma Ntoso, ‘The element activeRef is a metadata reference to the Akoma Ntoso IRI of

a document that is modified by this document (i.e., an active reference).’

The following attributes of <activeRef> MUST be used:

@href MUST contain the ELI reference of the relevant version to take into account (the latest

consolidated version at the time of the amendment or the original version in case there had

been no amendment to this act before).

@showAs MUST contain the content of the element <affectedDocument> and between

parentheses,

o the date of the consolidation used or

o "OJ" if the original version is used.

Examples:

The reference to a consolidated version of the act:

<meta>

…

<activeRef href="http://data.europa.eu/eli/reg/2013/1305/2017-05-20"

showAs="Regulation (EU) No 1305/2013 (consolidation 2017-05-20)"/>

</meta>

The reference to the original version as published in the OJ:

<meta>

…

<activeRef href="http://data.europa.eu/eli/reg/2013/1305/oj"showAs="Regulation

(EU) No 1305/2013 (OJ)"/>

</meta>

If no consolidated version exists, but the current version is not the version published in the Official Journal, the <activeRef> MUST not be used.

23

<activeRef> is the reference in relation with <activeModification>, so it references the amended act.


30/03/2020 Page 78 of 124

6.1.2.2 The mark-up of the text of an amendment

6.1.2.2.1 The element <mod>

To encapsulate all the text of an amendment, Akoma Ntoso provides the element <mod>. Only the

text specific to one amendment is to be marked-up with the element <mod>.

Consequently, in the following example, the part in green must be in a <mod> element (there are

two <mod> in the following example):

6.1.2.2.2 The elements <quotedStructure> and <quotedText>

To encapsulate the 'text of the amendment', two elements are provided:

<quotedStructure> MUST be used if the content is a complete subdivision

<quotedStructure> MUST be used if the content is a complete annex

<quotedText> MUST be used if the content is a fragment of a subdivision (word or sentence).

Both elements have the following attributes to manage the quotation marks:

@startQuote containing the opening quotation mark of the ‘text of the amendment’,

@endQuote containing the closing quotation mark of the ‘text of the amendment’,

@inlineQuote containing the character showing continuation of a quote e.g at the beginning of each line of the quote (not used).

Examples: When the content is a complete subdivision

<quotedStructure startQuote="‘" endQuote="‘">

<point><num>(n)</num>

<content>“young farmer” means a person who is no more than 40 years of age at the

moment of submitting the application, possesses adequate occupational skills and competence

and is setting up for the first time in an agricultural holding as head of that holding; the

setting up may be done solely or jointly with other farmers, irrespective of its legal

form;</content>

</point>

</quotedStructure>


30/03/2020 Page 79 of 124

When the content is a complete annex In this case, the <quotedStructure> MUST only contain a <documentRef> element. The @href mandatory attribute of this element MUST contain the relative path to the xml file containing the text of the annex.


<documentRef href="annex2-annex5.xml" showAs="ANNEX V"/>

</quotedStructure>

When the content is a fragment of a subdivision

the words <quotedText startQuote="'" endQuote="'">50 kilometre</quotedText> or

<quotedText startQuote="'" endQuote="'">50 km</quotedText> are replaced by the

words <quotedText startQuote="'" endQuote="'">100 km</quotedText>…

6.1.2.2.3 The last punctuation character of an amendment

The last punctuation character included at the end of <mod> MUST be marked with the element

<inline> with value "punctuationMod" for the mandatory @name attribute.

This mark-up MUST be used to mark the last punctuation mark of a <mod> element even if there is

no 'text of the amendment'.

<mod>in paragraph 5, the second subparagraph is deleted<inline name="punctuationMod"

>.</inline></mod>

6.1.2.2.4 General example of mark-up of the text of an amendment

For the following example:

the mark-up will be as follows:

<point>

<num>(a)</num>

<content>

<mod>point (n) is replaced by the following:


<point><num>(n)</num>

<content>“young farmer” means a person who is no more than 40 years of age at the

moment of submitting the application, possesses adequate occupational skills and competence

and is setting up for the first time in an agricultural holding as head of that holding; the

setting up may be done solely or jointly with other farmers, irrespective of its legal

form;</content>

</point>

</quotedStructure><inline name="punctuationMod>;</inline></mod>

</content>

</point>


30/03/2020 Page 80 of 124

6.1.2.2.5 The footnote in an amendment

If the amendment modifies a text containing a footnote, all the footnotes included inside a ‘text of an

amendment’ are displayed at the end of this ‘text of the amendment’ and the closing quotation mark

is placed just after the text of the last footnote. The numbering of the footnote is expressed by a

number of "*".

Example

The mark-up of the footnote MUST be an element <authorialNote> with the following

characteristics:

The @marker is not a number but one or more '*' (the number of '*' is the number of the

note; the numbering is related to the current ‘text of the amendment’)

The @placement MUST be "bottom"

The @placementBase MUST always reference the last element in the <quotedStructure>,

because the footnote must be displayed as last element of <quotedStructure>, just before

the closing quotation mark.

The above example will be marked up as follows (here the <quotedStructure> contains only one <paragraph> that is also the last element in the <quotedStructure>, so the @placementBase references this <paragraph>): <mod>in Article 62, the following paragraph is added:


<paragraph xml:id="_qstruc_1__para_5">

<num>5.</num>

<content>

Member States may apply this Chapter to areas producing wine suitable for producing

wine spirits with a geographical indication as registered in accordance with Annex III to

Regulation (EC) No 110/2008 of the European Parliament and of the Council<authorialNote

placement="bottom" placementBase="~_qstruc_1__para_5" marker="*">Regulation (EC) No

110/2008 of the European Parliament and of the Council of <date date="2008-01-15">15 January

2008</date> on the definition, description, presentation, labelling and the protection of

geographical indications of spirit drinks and repealing Council Regulation (EEC) No 1576/89

(OJ L 39, 13.2.2008, p. 16).</authorialNote>. For the purposes of this Chapter, those

areas may be treated as areas where wines with a protected designation of origin or protected

geographical indication may be produced.

</content>

</paragraph>



30/03/2020 Page 81 of 124

6.1.2.3 The metadata associated to an amendment

The following subsections inside the metadata section <analysis> concern amendments:

<activeModifications> groups the metadata related to the modification that the current

amending act applies on another act.

The metadata is linked to the <activeRef> metadata of the <references> section, which

contains the reference to the Expression that is modified by the current amending act.

<passiveModifications> groups the metadata related to the modification that are at the

source of the current consolidation of the act. The metadata is linked to the <passiveRef>

metadata of the <references> section, which contains the reference to the act that modifies

the current Expression.

Inside <activeModifications> and <passiveModifications>, the <textualMod> metadata provides the

textual modification.

6.1.2.3.1 <textualMod>

The <textualMod> metadata provides metadata related to a textual modification.

Each amendment of an amending act MUST have at least one corresponding <textualMod>

metadata.

6.1.2.3.1.1 Attributes of <textualMod>

@type, mandatory

The type of the amendment can have the following values:

@type operation in the

text of the

amending act

entry of the authority table

'modification type'

repeal deleted http://publications.europa.eu/resource/authority/modification-

type/DELETION

substitution replaced http://publications.europa.eu/resource/authority/modification-

type/REPLACEMENT

insertion added

or

inserted

http://publications.europa.eu/resource/authority/modification-

type/INSERTION

replacement / /

renumbering / http://publications.europa.eu/resource/authority/modification-

type/RENUMBERING

split / /

join / /

The four last values of the table are not used in the amendment of an amending act.


30/03/2020 Page 82 of 124

@incomplete

Value: "true" or "false"

When the metadata is incomplete, this attribute MUST be used and set to "true"

Example:

In the following example, the <textualMod> is about a provision in the enacting terms that

modifies two annexes. However, the real amendments on these annexes are in an annex of

the amending act. For this reason, the <textualMod> related to the provision in the enacting

terms has the @incomplete attribute set to "true". The <source> sub element that points to

the provision in the enacting terms has also the @incomplete attribute set to "true".

<meta>

…

<textualMod type="substitution" incomplete="true">

<source href="~_ar5896" incomplete="true"/>

<source href="annex3.xml"/>

<destination href="http://data.europa.eu/eli/reg/2013/1305/ann_7/>

<destination href="http://data.europa.eu/eli/reg/2013/1305/ann_8"/>

</textualMod>

…

</meta>

…

<mod xml:id="_ar5896">Annexes VII and VIII are amended in accordance with

Annex III to this Regulation<inline name="punctuationMod">.</inline></mod>



…

6.1.2.3.1.2 Sub-elements of <textualMod>

The main sub-elements are the following:

<source>

metadata element specifying the IRI of the source of the modification (reference to the

<mod> element),

<destination>

metadata element specifying the IRI of the destination of the modification (part of the

amended act that is modified by this amendment),

<old>

metadata element containing the old text of the modification,

<new>

metadata element containing the new text of the modification.

The following sub-elements are also available to correctly define the legal scope of the modification

(Their use is not covered in this release of the specifications):

<force>

metadata element specifying the period of the force modification,

<efficacy>

metadata element specifying the period of the efficacy modification,

http://data.europa.eu/eli/reg/2013/1305/ann_7


30/03/2020 Page 83 of 124

<application>

metadata element specifying the period of the application modification,

<duration>

metadata element specifying the period of the duration modification,

<condition>

metadata element specifying an open set of conditions on the modification (not managed by

Akoma Ntoso),

<previous>

used for the renumbering.

In AKN4EU the elements <old> and <new> MUST only be used in the following cases:

when the <mod> element contains multiple <quotedStructure> or multiple <quotedText>,

(with some for the old, and some for the new text), <old> and <new> are used to mark the

distinction;

when the <quotedStructure> is outside the element <mod>: for example, in case of an

amendment that inserts or replaces a complete annex (the new version of the annex is in

one annex of the amending act but the amendment is in the enacting terms), or when the

result of the amendment is provided in a consolidated version (consolidated amendment of

EP, for example).

The attribute @href of the <source> element MUST contain a reference to an element <mod>, using

the @xml:id of this element (technical reference).

6.1.2.3.2 Example

6.1.2.3.2.1 Amendment of a subdivision

Considering the following amendment:

Context: textual subdivision identifier during the drafting and after the publication of a document:

the technical and functional identifier

A technical identifier is an identifier that carries no meaning. A functional identifier is an identifier that is meaningful. It is a machine-readable form of the way the user references a subdivision, based on its location inside the document.

During the drafting process, the main feature of the identifier of a subdivision is its immutability (once initialised, never to be changed thereafter), allowing to follow the evolution of the same text throughout the drafting process. As the structure of the document evolves a lot during the drafting without necessarily following a strict formal procedure, the use of a functional (business) identifier built on the location of the subdivision does not makes sense. Therefore, the identifier of a subdivision is during the drafting, a technical identifier (@xml:id).


30/03/2020 Page 84 of 124

After the publication of a document users (e.g. lawyers) make reference to a subdivision by providing its location in the text, especially when the document is a legal act. This makes sense as the document will not evolve a lot and any modification is formalized by amendments following a legislative procedure. Modifications never comprise implicit renumbering, so that a subdivision’s location remains correct.

ELI defines for the reference to a subdivision a syntax mapped to the business approach to the referencing. The subdivision reference is based on the CoV concepts structuring the text.

In Akoma Ntoso, the @eId attribute is provided to store the identifier used for the business reference in a well-defined structure and machine readable way. The following example of mark-up is based on this logic:

in the proposal, the identifier is the @xml:id attribute.

for the amended act already published in the Official Journal, the identifier is (for the example) stored in the @eId attribute to indicate that it corresponds to a business way to identify the subdivision. This value is used as the subdivision part of ELI reference.

The mark-up for <textualMod> (metadata) is based on the following principles:

the @type MUST be completed following the table ;

the @href attribute of the <source> element MUST reference the element <mod>;

the @href attribute of the <destination> MUST be an ELI reference to the subdivision

specified in the amendment (see the syntax for the ELI reference).


30/03/2020 Page 85 of 124

6.1.2.3.2.2 Example of an amendment of text

The following amendment:

will be represented as follows24:

The mark-up for <textualMod> (metadata) is based on the following principles:

The @type MUST completed following the table.

The @incomplete attribute MUST be used to indicate that the change cannot be automated.

The @href attribute of the <source> element MUST reference the element <mod>.

The @href attribute of the <old> element references the element <quotedText> with the old value.

The @href attribute of the <new> element references the <quotedText> with the new value.

24

Only part of the destinations are in the mark-up.

amendment

metadata

…


30/03/2020 Page 86 of 124

The @href attribute of the <destination> MUST be an ELI reference to the subdivision specified in the amendment (see the syntax for the ELI reference).

If multiple subdivisions are provided, two cases can be distinguished:

o uses one <destination> and the attribute @upTo to indicate the end of the interval.

o provides one element <destination> per first level subdivision of the text that is affected by the amendment.

6.1.2.3.3 Metadata for the replacement

The replacement of a structure ("substitution" as AKN type) has the following characteristics:

The ‘text of the amendment’ MUST be in a <quotedStructure>.

The corresponding <textualMod> in the <activeModification> has the following

characteristics:

o The @type of the <textualMod> MUST have the value "substitution".

o The @href of the <source> MUST point to the corresponding <mod> element.

o The @href of the <destination> sub-element MUST point to the structure of the

amended act, that is referenced in the amendment.

o If a range of structures is modified, two options are available to specify the

destination:

there is one <destination> sub-element and the @upTo attribute of this

element points to the last structure modified in the amended act.

there is one <destination> per first level of subdivision modified.

6.1.2.3.4 Metadata for the insertion

The insertion of a structure ("insertion" as AKN type) inserts a new structure before or after an

already existing structure. As the principle of the amendment is to never renumber the existing

structure, the insertion uses a specific type of numbering.

For the insertion, the characteristics are as follows:

The 'text of the amendment' MUST be in a <quotedStructure>.


characteristics:

o The @type of the <textualMod> MUST have the value "insertion".


o The <destination> sub-element has the following attributes:

The @href MUST point to the structure indicated in the amendment as the

reference structure.

The @pos MUST be used with the following value:

"after" if the referenced structure is the preceding structure;


30/03/2020 Page 87 of 124

"start" if the referenced structure is the parent structure;

"before" if the referenced structure is the following structure.

6.1.2.3.5 Metadata for the addition

The addition of a structure ("insertion" as AKN type) adds a new structure at the end of an existing

structure. In this case, if the new structure is a numbered structure, it is an increment of the last

sibling structure.

For the addition, the characteristics are as follows:

The 'text of the amendment' MUST be in a <quotedStructure>.


characteristics:

o The @type of the <textualMod> MUST be the value "insertion".


o The <destination> sub-element has the following attributes:

The @href MUST point to the parent structure.

The @pos MUST be used with the value "end" = insert at the end of the

parent structure.

6.1.2.3.6 Metadata for the deletion

For the deletion, the characteristics are as follows:

There is no text of the amendment.


characteristics :

o The @type of the <textualMod> has the value "repeal".

o The @href of the <source> points to the corresponding <mod> element.

o the <destination> element has the following attribute:

the @href points to the structure to be deleted.

In case of deletion of an interval of subdivisions, two alternative mark-ups are

possible:

One <destination> element with the @href attribute pointing to the start of

the interval and @UpTo attribute pointing to the end of the interval.

Multiple <destination> elements (one per subdivision of the sequence), each

with the @href attribute pointing to the corresponding subdivision (no

@upTo attribute used in this case).


30/03/2020 Page 88 of 124

Example 1:

<point> <num>(c)</num> <content>

<mod xml:id="_a123od">paragraph 3 is deleted<inline name="punctuationMod>;</inline></mod>

</content> 

will have the following metadata:

<meta>

…

<textualMod type="repeal">

<source href="~_a123od "/>

<destination href="http://data.europa.eu/eli/reg/2013/1305/art_152.par_3"/>

</textualMod>

…

</meta>

Example 2: Mark-up of the provision for deletion of annex(es)

(42) Annexes VII, VIII and IX are deleted;

<point>

<num>(42)</num>

<content>

<mod xml:id="_ab123">Annexes VII, VIII and IX are deleted<inline

name="punctuationMod">.</inline></mod>

</content>

</point>

As there is an interval, there are two alternative mark-ups for the destination:

<meta>

…


<source href="~_ab123"/>

<destination

href="http://data.europa.eu/eli/reg/2013/1308/ann_7"

upTo="http://data.europa.eu/eli/reg/2013/1308/ann_9"/>

</textualMod>

or

<meta>

…






</textualMod>


30/03/2020 Page 89 of 124

6.1.2.4 Special cases

6.1.2.4.1 Modification of the first unnumbered structure of a numbered structure

When the first substructure of a modified structure is on the same line as the number of the

englobing structure, generally, the whole line is included in the quoted structure, including this

number.

In this case, the mark-up in the <quotedStructure> MUST be isolate in two sibling elements, the

amended text and the contextual text (generally the number of the parent structure) like in the

following examples:

The corresponding mark-up will be as follows:

<mod xml:id="_a123od">in paragraph 3, the first subparagraph is replaced by the following: <quotedStructure xml:id="_qstruc_1" startQuote="‘" endQuote="‘">

<num>3.</num> <subparagraph> <content> The authorities or bodies selected to provide advice shall have appropriate resources in the form of regularly trained and qualified staff and advisory experience and reliability with respect to the fields in which they advise. The providers under this measure shall be chosen through a selection procedure open to both public and private bodies. That selection procedure shall be objective and shall exclude candidates with conflicts of interest. </content> </subparagraph>


With the following metadata

<meta>

…

<textualMod type="substitution">


<destination href="http://data.europa.eu/eli/reg/2013/1305/art_15.par_3.sub_1"/>

</textualMod>

…

</meta>

The amendment:


30/03/2020 Page 90 of 124

will be marked as follows:

<point> <num>(a)</num> <content> <mod xml:id="_a123od">in paragraph 1, the introductory part is replaced by the following: <quotedStructure xml:id="_qstruc_1" startQuote="‘" endQuote="‘">

<num>1.</num> <intro> Support under this measure shall cover new participation, or participation in the five preceding years, by farmers and groups of farmers, in: </intro>


</content> </point>

The corresponding metadata refers to the <quotedStructure>:

<meta>

…



<destination href="http://data.europa.eu/eli/reg/2013/1305/art_16.par_1.sub_1.int"/>

</textualMod>

…

</meta>

General rule: the consolidation will never take into account a <num> element that is the first child of

the <quotedStructure>


30/03/2020 Page 91 of 124

6.1.2.4.2 Amendment of multiple sibling structures

When an amendment modifies multiple sibling structures, only these structures are included in the

<quotedStructure>.

The mark-up will be as follows:

<mod xml:id="_a123od">paragraphs 2 and 3 are replaced by the following:


<paragraph>

<num>2.</num>

<content>

Support under this measure may also cover costs arising from information and

promotion activities implemented by groups of producers, concerning products covered by a

quality scheme receiving support in accordance with paragraph 1 of this Article. By way of

derogation from Article 70(3) of Regulation (EU) No 1303/2013, those activities may only be

implemented in the internal market.

</content>

</paragraph>

<paragraph>

<num>3.</num>

<subparagraph>

<content>

Support under this measure may also cover costs arising from information and

promotion activities implemented by groups of producers, concerning products covered by a

quality scheme receiving support in accordance with paragraph 1 of this Article. By way of

derogation from Article 70(3) of Regulation (EU) No 1303/2013, those activities may only be

implemented in the internal market.

</content>

</subparagraph>

<subparagraph>

<content>

In the case of initial participation prior to the application for support under

paragraph 1, the maximum duration of five years shall be reduced by the number of years which

have elapsed between the initial participation in a quality scheme and the time of the

application for the support. 

</content>

</subparagraph>

<subparagraph>

<content>

For the purposes of this paragraph, “fixed costs” means the costs incurred for

entering a supported quality scheme and the annual contribution for participating in that


30/03/2020 Page 92 of 124

scheme, including, where necessary, expenditure on checks required to verify compliance with

the specifications of the scheme. 

</content>

</subparagraph>

<subparagraph>

<content>

For the purposes of this Article, “farmer” means active farmer within the meaning

of Article 9 of Regulation (EU) No 1307/2013, as applicable in the Member State concerned.



</content>

</subparagraph>

…

</paragraph>


Inside the metadata, there are two alternative options to specify the <destination>:

One <destination> element with the @href attribute pointing to the start of the interval and

@UpTo attribute pointing to the end of the interval.

Multiple <destination> elements (one per subdivision of the sequence), each with the @href

attribute pointing to the corresponding subdivision (no @upTo attribute used in this case).

The mark-up of the metadata can be as follows:

<meta> …


<source href="~_a123od"/>

<destination href="http://data.europa.eu/eli/reg/2013/1305/art_16.par_2"

upTo="http://data.europa.eu/eli/reg/2013/1305/art_16.par_3"/>

</textualMod>

…

</meta>


30/03/2020 Page 93 of 124

The sibling structure can be an introductory part and one or more following points of a list, but not

the complete list. For example:

In this case, only the modified subdivisions MUST be included in the <quotedStructure>; the

subdivision <list> MUST not be part of the <quotedStructure>.


<mod xml:id="_a123od">in paragraph 4, the introductory part and point (a) of the second subparagraph are replaced by the following:

<quotedStructure xml:id="_abc123 __mod__qstr" startQuote="‘" endQuote="‘">

<intro>

Notwithstanding the first subparagraph, one or more of the following shall apply:

</intro>

<point>

<num>(a)</num>

<list>

<intro>

where a Member State decides to make a written contract for the delivery of raw

milk compulsory in accordance with paragraph 1, it may establish:

</intro>

<point>

<num>(i)</num>

<content>

an obligation for the parties to agree on a relationship between a given

quantity delivered and the price payable for that delivery;

</content>

</point>

<point>

<num>(ii)</num>

<content>

a minimum duration, applicable only to written contracts between a farmer

and the first purchaser of raw milk; such a minimum duration shall be at least six months, and

shall not impair the proper functioning of the internal market;

</content>

</point>

</list>

</point>


The corresponding metadata can be as follows:

<meta> …

<textualMod type="substitution"> <source href="~_a123od"/> <destination href="http://data.europa.eu/eli/reg/2013/1305/art_16.par_4.sub_2.int" upTo="http://data.europa.eu/eli/reg/2013/1305/art_16.par_4.sub_2.pnt_a"/> </textualMod> …

</meta>


30/03/2020 Page 94 of 124

6.1.2.4.3 Modification of the subject of an article

For the following example:

the amendment will be marked as follows:

<mod xml:id="_a123od">the heading is replaced by the following: <quotedStructure startQuote="‘" endQuote="‘">

<num>Article 23 </num> <heading>Establishment, regeneration or renovation of agroforestry systems </heading>


And the corresponding metadata: <meta>

…


<source href="~_a123od"/>

<destination href="http://data.europa.eu/eli/reg/2013/1305/art_23.tit"/>

</textualMod>

…

</meta>


30/03/2020 Page 95 of 124

6.1.2.4.4 Insertion of multiple numbered structures

The following example:

will have the following metadata:

<meta> …

<textualMod type="insertion"> <source href="~_a123od"/> <destination href=http://data.europa.eu/eli/reg/2013/1305/art_152.par_1" pos="after"/> </textualMod> … </meta>


30/03/2020 Page 96 of 124

6.1.2.4.5 Addition, insertion or replacement of an annex

The overall mark-up for this kind of amendment corresponds to the following schema:

Mark-up of the text and metadata are needed in both the main part of the amending act and the

annex of the amending act, as both components contain part of the information on the amendment.

6.1.2.4.5.1 In enacting terms

The amending provision MUST be marked with a <mod> element but the <mod> element MUST be

without <quotedStructure>, as the text of the amendment is not there.

The punctuation after the <mod> element MUST be marked with the <inline

name="punctuationMod"> element as usual.

For example:

(40) Annex V is replaced by the text set out in Annex II to this Regulation.


<point>

<num>(40)</num>

<content>

<mod xml:id="_uy8547"> Annex V is replaced by the text set out in Annex II to this Regulation<inline name="punctuationMod">.</inline></mod>

</content>

</point>


30/03/2020 Page 97 of 124

The corresponding metadata in the main document will contain:

in the attribute @type, the operation,

in the sub-element <source>, the link to the <mod> in the enacting terms,

in the sub-element <destination>, in the @href attribute, the location in the amended act,

When the operation is insertion or addition:

o @href attribute contains the reference point (for addition it is the uri of the act) and

o @pos attribute indicates where to put the insertion/ addition ("end" or "after" or

"before").

There MUST be a sub-element <new> that contains the information related to the place

where the 'text of the amendment' is. In this case, it MUST be the relative path to the annex

of the amending act, which contains the text of the amendment.

Example

<meta>

…


<source href="~_uy8547"/>

<destination

href="http://data.europa.eu/eli/reg/2009/818/ann_V"/>

<new href="annex2.xml"/>

</textualMod>

…

</meta>

6.1.2.4.5.2 In the corresponding annex of the amending act

In this case, the content of the annex is the new annex. For example:

ANNEX II

‘

ANNEX V

LIST OF RESIDENCE PERMITS ENTITLING THE HOLDER TO TRANSIT THROUGH THE AIRPORTS OF

MEMBER STATES WITHOUT BEING REQUIRED TO HOLD AN AIRPORT TRANSIT VISA

…..

… .’.

In this case, the annex MUST contain:

the heading of the annex with its numbering; then

between quotation marks, the new annex;

finally, (optionally) the last punctuation mark. The new annex MUST be marked-up by a <quotedStructure> element inside a <mod> element. The <mod> MUST contain also the last punctuation mark. If it exists, it MUST be in an <inline name="punctuationMod"> element. <mod> is the only content of the <paragraph> element. As one of the rules in AKN4EU is to not allow subdocument inside document, the content of the annex as amended is not put directly in the annex of the amending act, but is in a specific file. The relative path MUST be referenced in this annex in the @href attribute of the element <documentRef>.


30/03/2020 Page 98 of 124

So, the above example will be marked as follows:

<doc name="ANNEX">

...

<preface>


<block name="num">ANNEX II</block>

</container>

</preface>

<mainBody>

<paragraph>

<mod xml:id="_avt58pt66">


<documentRef href="annex2-annex5.xml" showAs="ANNEX V"/>

</quotedStructure>

<inline name="punctuationMod">.</inline></mod>

<paragraph>

</mainBody>

</doc>

The mark-up of the 'text of the amendment' which is the new annex (annex2-annex5.xml) is marked as usual. <doc name="ANNEX">

...

<preface>


<block name="num">ANNEX V</block>

<block name="heading">LIST OF RESIDENCE PERMITS ENTITLING THE HOLDER TO

TRANSIT THROUGH THE AIRPORTS OF MEMBER STATES WITHOUT BEING REQUIRED TO HOLD AN

AIRPORT TRANSIT VISA</block>

</container>

</preface>

<mainBody>

...

</mainBody>

</doc>

The corresponding metadata in the annex of the amending act MUST contain a <textualMod>

corresponding to the amendment. It is very similar to the corresponding <textualMod> of the main

part of the amending act, except that it MUST not have a <new> element, as the text of the

amendment is in the same file.

Therefore, the <textualMod> has the following information:

in the attribute @type, the operation (see in the main part),

in the sub-element <source>, the link to the <mod> in the annex,

in the sub-element <destination>, the location in the amended act (same as the main part).

Example:

<meta>

…


<source href="~_avt58pt66"/>

<destination

href="http://data.europa.eu/eli/reg/2009/818/ann_V"/>

</textualMod>

…

</meta>


30/03/2020 Page 99 of 124

6.1.2.4.6 The modifications of an annex

The overall mark-up for this kind of amendment corresponds to the following schema:

6.1.2.4.6.1 In the enacting terms

In this case, the point related to the modification inside an annex in the enacting terms is not really

an amendment: it does not contain the list of modifications to apply to an annex but only the

reference to the annex that contains these amendments.

Nevertheless, for technical reason, this content MUST be marked with a <mod> element and a

corresponding metadata <textualMod> MUST exist (the @href attribute of the <source> element of

the <textualMod> references this <mod>).

For example:

(23) Annexes VII and VIII are amended in accordance with Annex III to this

Regulation.

In this case, the mark-up will be the following:

<point xml_id="_abc12">

<num>(23)</num>

<content>

<mod xml:id="_ar5896">Annexes VII and VIII are amended in accordance

with Annex III to this Regulation<inline name="punctuationMod">.</inline></mod>

</content>

</point>


30/03/2020 Page 100 of 124

and the corresponding metadata will contain:

in the attribute @type, the operation 'substitution',

an @attribute @incomplete MUST be set to "true" (this point is not really an amendment

but only a reference to the annex containing the amendments),

It MUST exist two sub-element <source>:

o in a first sub-element <source>,

the link to the <mod>.

the attribute @incomplete is set to "true" as the source does not contain all

the information and is not really an amendment;

o in a second sub-element <source>, the reference to the amending annex,

one or more sub-element <destination> MUST contain the location(s) in the amended act, so

the reference to the annexes that are amended.

Example

<meta>

…




<destination href="http://data.europa.eu/eli/reg/2013/1305/ann_7"

upTo="http://data.europa.eu/eli/reg/2013/1305/ann_8"/>

</textualMod>

…

</meta>

or

<meta>

…






</textualMod>

…

</meta>

6.1.2.4.6.2 In the amending annex

The introductory part of the sequence of amendments MUST contain the reference to the amended

act. In this case, it MUST be marked with the element <affectedDocument>.

In such case, the annex MUST contain <mod> elements for each amendment and each <mod> MUST

have a <textualMod> metadata associated to this amendment.


30/03/2020 Page 101 of 124

For example

The introductory part will be marked as follows: Annexes VII and VIII to <affectedDocument

href="http://data.europa.eu/eli/reg/2013/1308">Regulation (EU) No 1308/2013</affectedDocument>

are amended as follows:

The first amendment will be marked as follows: <point>

<num>(1)</num>

<content>

<mod xml:id="_ab123">in point 1(c) of Part II of Annex VII, the second

indent is replaced by the following:<quotedStructure startQuote="‘" endQuote="‘">

<indent><num>—</num>

<content>

the upper limit for the total alcoholic strength may

exceed 15 % volume for wines with a protected designation of origin which have been

produced without enrichment, or enriched only by partial concentration processes

listed in point 1 of Section B of Part I of Annex VIII, provided that the product

specification in the technical file of the protected designation of origin

concerned allows for that possibility;

</content>

</indent>

</quotedStructure><inline name="punctuationMod">;</inline></mod>

</content>

</point>

and the corresponding metadata will contain:

in the attribute @type, the operation,

in the sub-element <source>, the link to the <mod> in the annex,

in the sub-element <destination>, the location in the amended act.

<meta>

…



<destination

href="http://data.europa.eu/eli/reg/2013/1308/ann_7.prt_1.pnt_1.spg_1.pnt_c.spg_1.ind_2"/>

</textualMod>


30/03/2020 Page 102 of 124

6.1.2.4.7 Addition of an annex in an act that has only one annex.

The case of the addition of an annex in an act that has only one annex can be expressed with two

amendments:

the previous sole annex, that had no numbering, receives a number;

the new annex is added.

Each amendment MUST be marked with a <mod> element.

For example,

(44) the Annex becomes Annex I;

…

(46) the text set out in the Annex to this Regulation is added as Annex II.

will be marked as

<point><num>(44)</num>

<content>

<mod xml:id="_jt123"> the Annex becomes Annex I<inline

name="punctuationMod">;</inline></mod>

</content>

</point>

…

<point><num>(46) </num>

<content>

<mod xml:id="_pz521"> the text set out in the Annex to this Regulation is

added as Annex II<inline name="punctuationMod">.</inline></mod>

</content>

</point>

In the metadata related to the amendment, two <textualMod> MUST be defined:

one <textualMod type="substitution" incomplete="true"> :

the @href attribute of <source> MUST point to the <mod> regarding the renumbering of the

existing annex. The <source> MUST have an @incomplete attribute sets to "true".

The @href of <destination> MUST be an ELI reference to the heading (<num> element) of

the sole annex.

one <textualMod type="insertion"> :

the @href attribute of <source> MUST point to the <mod> regarding the addition of the new

annex inside the enacting terms.

The @href of <destination> MUST be an ELI reference to the act and the @pos attribute of

<destination> has the "end" value.

The <new> element MUST contain the relative path (inside .leg file) of the annex of the

amending act that contains the new annex.

<meta>

…


<source href="~_jt123" incomplete="true"/>

<destination href="http://data.europa.eu/eli/.../anx_1/num" />

</textualMod>

<textualMod type="insertion">

<source href="~_pz521" />

<destination href="http://data.europa.eu/eli/<ACT>..." pos="end"/>

<new href="annex1.xml"/>

</textualMod>


30/03/2020 Page 103 of 124

6.1.3 Case of the amending Act: text that repeals an act

The act may contain articles that repeal another act.

in this case the title of the act contains also the information:

For the repeal of an act, the characteristics of the mark-up are as follows:

The text that indicates this repeal is not marked with a <mod>

The corresponding <textualMod> metadata MUST exist that MUST have the following

characteristics :

empty <source> child

the attribute @href of the sub-element <destination> MUST contain the ELI IRI of the

act.

Example

<meta>

…


<source/>

<destination href="http://data.europa.eu/eli/dec/2006/1926"/>

</textualMod>

…

</meta>

<longTitle>

<docType refersTo=~_"REG">REGULATION <docNumber>(EU) No 254/2014</docNumber>

OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL</docType> of <date date="2014-02-

26">26 February 2014</date>


repealing <ref href="http://data.europa.eu/eli/dec/2006/1926">Decision No

1926/2006/EC</ref></docPurpose>

</longTitle>

…

<article>


<heading>Repeal</heading>

<paragraph>

<content>

Decision No 1926/2006/EC is repealed with effect from <date

date="2014-01-01">1 January 2014</date>.


30/03/2020 Page 104 of 124

</content>

</paragraph>

</article>


30/03/2020 Page 105 of 124

6.1.4 Case of the amending Act: summary of the amendment mark-up

Amendment type Mark-up in the text Related metadata

Replacement

Replacement of a

structure

The text of the new version is in the

<quotedStructure> of a <mod> element.

NB: Special case

If the structure replaced is the first

structure of a point or of a

numbered paragraph, then, the

<num> element of the parent

structure is the first element of the

<quotedStructure>.

<textualMod>

@type="substitution"

<source>

@href points to the <mod> element

<destination> (alternative 1) :

@href is the ELI URI of the first subdivision

modified.

@upTo (optional) is the ELI URI of the last

subdivision modified.

multiple <destination> (alternative 2):

There is one <destination> per top level subdivision

modified.

@href is the ELI URI of the corresponding

subdivision

Replacement of the

subject of a structure

The text of the new version is in the

<quotedStructure> of a <mod> element.

<textualMod>


<source>


<destination>

@href is the ELI URI of the subject.

Replacement of an

annex

Enacting terms:

The amending provision is in a <mod>

element without <quotedStructure>

Annex with the text of the amendment

The content (<mainBody>) of the annex

is composed of one <paragraph> with as

content, one with a <mod> with a

<quotedStructure>.

The content of the <quotedStructure> is

a <documentRef> with a @href attribute

containing the relative path to the file

with the new version of the annex.

File with the new version of the annex

This document is simply an annex.

Metadata in the enacting terms

<textualMod>


<source>


<destination>

@href is the ELI URI of the annex replaced.

<new>

@href is the relative path to the annex

containing the <quotedStructure>

Metadata in the annex with the text of the

amendment

<textualMod>


<source>

@href points to the local <mod> element

<destination>



30/03/2020 Page 106 of 124


Insertion

Insertion of one or

more structure(s)

The text of the amendment is in a

<quotedStructure> of a <mod> element

<textualMod>

@type="insertion"

<source>


<destination>

@href points to the subdivision related to

which the insertion is done

@pos can have the following values

o "after"

o "before"

o "start"

Insertion of an annex Enacting terms:





is composed of a <paragraph> with

inside <content>, a with a <mod>

element with a <quotedStructure>.



containing the relative path to the new

annex.

File with the new annex



<textualMod>


<source>


<destination>

@href is the ELI URI of the annex relatively

to which the insertion is done

@pos = "after" or "before".

<new>


containing the new annex


amendment

<textualMod>


<source>


<destination>

@href is the ELI URI of the annex replaced


30/03/2020 Page 107 of 124


Addition

Addition of one or

more structure(s)

The text of the amendment is in a

<quotedStructure> of a <mod> element

<textualMod>

@type="insertion"

<source>


<destination>

@href points to the parent subdivision

@pos = “end” .

Addition of an annex Enacting terms:











annex.




<textualMod>


<source>


<destination>


<new>




amendment

<textualMod>


<source>


<destination>

@href is the ELI URI of the annex replaced


30/03/2020 Page 108 of 124


Addition of an annex

in an act that has a

sole annex

Enacting terms:

Two amending provision exist for this

operation

the previous sole annex, that had no

numbering, receives a number.

the new annex is added.

Each amending provision is inside a

<mod> element without

<quotedStructure>









annex.




For the addition of a number to the sole Annex

<textualMod>


@incomplete="true"

<source>


@incomplete="true"

<destination>

@href is the ELI URI to the subject of the

annex (tit).

<new>



For the addition of an annex:

<textualMod>

@type="insertion"

<source>


<destination>

@href is the ELI URI of the amended act

@pos="end"

<new>

@href is the relative path to the file

containing the annex with the new annex


amendment

<textualMod>

@type="addition"

<source>


<destination>

@href is the ELI URI of the act

@pos="end"


30/03/2020 Page 109 of 124


Deletion

Deletion of one or

more structure(s)

The provision for the deletion of the

structure is in a <mod>.

There is no <quotedStructure> inside.

<textualMod>

@type="repeal"

<source>




deleted.

@upTo is the ELI URI of the last subdivision

deleted.



modified.


deleted subdivision

Deletion of annex(es) Enacting terms:

The provision for the deletion of the

structure is in a <mod>.

There is no <quotedStructure> inside.


<textualMod>

@type="repeal"

<source>



@href is the ELI URI of the first annex

deleted.

@upTo is the ELI URI of the last annex

deleted.



modified.

@href is the ELI URI of the corresponding deleted

annex

Repeal of an act No provision is marked with a <mod>

element for this operation

<textualMod>

@type="repeal"

<source>

empty

<destination>

@href is the ELI URI of the act repealed.


30/03/2020 Page 110 of 124


Replacement of a text

Replacement of a

text

The amendment is in a <mod> element.

Each term is in a <quotedText> element.

<textualMod>


@incomplete="true"

<source>


<old>

@href points to a <quotedText> (old

version of text)

<new>

@href points to a <quotedText> (new

version of the text).



modified.





modified.


subdivision


30/03/2020 Page 111 of 124


Modification of an annex

Modification of an

annex

Enacting terms

The provision that specifies the annex

containing the amendment and which

annex(es) is (are) affected, is in a <mod>

element.

Annex with the amending provision

The introductory part of the sequence of

amendments contains the reference to

the amended act. (marked with

<affectedDocument>)

Each amending provision is in a <mod>

element with or without

<quotedStructure> depending on the

type of the amendment.


<textualMod>


@incomplete="true"

<source>


@incomplete="true"

<source>

@href is the relative path of the annex

containing the amendments



modified.





modified.


subdivision

Metadata in the annex with the annex containing

the amendment(s):

one <textualMod> per amendment.


30/03/2020 Page 112 of 124

7 ELI Syntax

Important remark: The syntax regarding the identification of preparatory documents as well as the

syntax regarding the identification of subdivisions are draft. They are likely to change significantly.

7.1 URI template for European Union legislation and preparatory acts

(draft)

ELI's HTTP URIs enables users to access legislation in a persistent way. The URIs are formally

described by machine-readable templates, using semantic components from a legal and an end-user

point of view.

Example (!!! this is currently a draft) :

http://data.europa.eu/eli/reg/2013/1305/art_5/par_3/sub_2/pnt_a

This kind of reference can exist regardless of whether it is marked and regardless of whether the

target document is in the AKN4EU format or not.The template for the act and consolidated

legislation is defined here: https://eur-lex.europa.eu/eli-register/eu_publications_office.html

ELI for preparatory documents (!!! draft !!!)

The syntax to identify preparatory documents is the following25:

http://data.europa.eu/eli/{typedoc}/{year}/{naturalnumber}

where

- {typedoc} is the code of the authority table Resource type

corresponding to this type of document, in lowercase.

- {year} is the year part of the <docNumber>

- {naturalnumber} is the number part of the <docNumber>

For the {typedoc} of the staff working document referenced in the cover page of a Proposal from the

Commission, the following values are available:

impact_assess for impact assessment (the alias "swd" is also possible)

impact_assess_sum for the summary of impact assessment (the alias "swd" is also possible)

swd for Staff Working Document. The references in the <container name="swdReferences"> will use the alias.

Example:

SWD(2016)168 http://data.europa.eu/eli/swd/2016/168

25

see http://publications.europa.eu/mdr/eli/documentation/uri_templates.html for the syntax of ELI URI for

European Union legislation.

identification

of

the resolver

identification

of

the act

identification

of

the subdivision

https://eur-lex.europa.eu/eli-register/eu_publications_office.html


30/03/2020 Page 113 of 124

7.2 Reference to subdivision in ELI URI templates (!!! draft !!!)

The ELI subdivision in the ELI URI templates must be built on a generic, format-independent

reference, based on the Common Vocabulary. The objective is to ensure that for an EU act, the

subdivision used reflects the vocabulary used by drafters/users, is standardised and machine

readable and can be interpreted uniquely.

For the current draft, the following syntax is used :

The information on the subdivision is inserted just after the part identifying the document.

When a succession of subdivision is needed, each subdivision information is separated by a

"/".

For example :

http://data.europa.eu/eli/dir/2000/31/art_1/par_2

The type of subdivision is separated from the number by using an "_";

The acronym for the subdivision type of an act is the following :

article art

chapter cpt

citation cit

clause cls

enacting terms enc

footnote ftn

indent idt

numbered or unnumbered paragraph par

part prt

point pnt

preamble pbl

recital rct

section sec

subject tit

subparagraph sub

subsection sbs

table tab

title tis

"TEC" subdivision : reference in ELI subdivision using @xml:id (!!! early draft !!!)


30/03/2020 Page 114 of 124

To allow to use ELI reference for preparatory acts that have been finalized (for example, Proposal)

with the subdivision reference specified using technical id, a special subdivision is defined : "TEC".

The number contains the value of an @xml:id

for example :

"…/eli/prop_act/2014/123/TEC_ eiroz158

It references the subdivision with @xml:id attribute with the value "eiroz158" of the document

COM(2014) 123.


30/03/2020 Page 115 of 124

PART 2. Correspondence between CoV 3.0 and AKN4EU 3.0

CoV terms or business rules Akoma Ntoso mark-up

acting entity

COV DESCRIPTION

Indicates the name of the acting entity or entities of a document.

<formula name = "actingEntity">

no correspondence in CoV

DESCRIPTION

"textual amendment"

<mod>

annex

COV DESCRIPTION

Annexes in the strict sense are used to present material separately from the body of the enacting terms, because it is voluminous or technical or both [JPG 22.1.].

<doc name = "ANNEX">

IS REFERENCED BY

<attachments>/<attachment>/<documentRef>/@href in <act> or <bill> or <doc>

article

COV DESCRIPTION

Basic unit of the enacting terms of a legal act [ JPG 15.4.]

<article>

article on definition

COV DESCRIPTION

By way of exception, in the article on definitions and in amending provisions, if there is more than one definition or amendment, the numbering of points starts with Arabic numerals within brackets for the first level.

<article> with the @refersTo attribute pointing to the <TLCConcept> with the @href attribute= "http://publications.europa.eu/resource/subdivision-content/ART_DEF">

article with amendments

COV DESCRIPTION

By way of exception, in the article on definitions and in amending provisions, if there is more than one definition or amendment, the numbering of points starts with Arabic numerals within brackets for the first level.

<article> with the @refersTo attribute pointing to the <TLCConcept> with the @href attribute= "http://publications.europa.eu/resource/subdivision-content/ART_AMEND".

cell

COV DESCRIPTION

Individual unit, within a table, used for

<td>


30/03/2020 Page 116 of 124

displaying data. chapter

COV DESCRIPTION

Indicates a level of higher subdivisions of an act [JPG 15.4.].

<chapter>

citation

COV DESCRIPTION

Sets out the legal basis of an act or a main step in the procedure leading to its adoption [JPG 9.].

<citation> (possibility to qualify a citation as legal basis)

CONTEXT: <citations>

closing part

COV DESCRIPTION

In a sentence including an enumeration of points or indents, the part following that enumeration.

<wrapUp>

CONTEXT: <list>

<listwrapUp>

CONTEXT: <blockList>

column

COV DESCRIPTION

Represents, in a table, a set of related data vertically.

no specific mark-up

column header

COV DESCRIPTION

Table cell used to indicate the subject of a column.

<th> for any cell considered as a 'header'

date

COV DESCRIPTION

Identifies a specific day in time.

<date>

decision

COV DESCRIPTION

Legal act of the European Union described in the fourth paragraph of Article 288 TFEU.

<act name="DEC">

direct applicability

COV DESCRIPTION

Corresponds, in Regulations, to the special formula used after the final article as regards the binding and directly applicable nature.

<clause> in <body>

CONTEXT:

<act name="REG">

<bill name="REG">

directive

COV DESCRIPTION

Legal act of the European Union specified in

<act name ="DIR">


30/03/2020 Page 117 of 124

Article 288 TFEU. eea relevance

COV DESCRIPTION

Indicates that the subject-matter of the act is governed by the Agreement on the European Economic Area (EEA) [JH A, p.1].


emblem

COV DESCRIPTION

Graphical element identifying an entity

<container name ="logo">/<img>

enacting formula

COV DESCRIPTION

Indicates the text between recitals and enacting terms

<formula name = "enactingFormula">

CONTEXT: <preamble>

enacting terms

COV DESCRIPTION

Operative part of the act.

<body>

CONTEXT: <act> or <bill>

EP consolidated text

COV DESCRIPTION

Consolidated version of European Parliament's position after first or second reading in the context of the ordinary legislative procedure.

to be defined

EP legislative resolution

COV DESCRIPTION

European Parliament's position on a given draft legislative act.

<bill name="RES_LEGIS">

<bill name="DRAFT_RES_LEGIS"> for the draft version

EP legislature

COV DESCRIPTION

Indicates the European Parliament legislative term.

to be defined

EP text adopted

COV DESCRIPTION

Resolution adopted by the European Parliament giving its position in the context of a given

procedure.

to be defined


30/03/2020 Page 118 of 124

explanatory memorandum

COV DESCRIPTION

Document which accompanies all Commission proposals submitted to the Council or to the European Parliament and the Council. It explains the context, justifications and foreseen impact of the Commission's proposal based on the different stages of the preparatory process.

<doc name = "EXPL_MEMORANDUM">

IS REFERENCED BY

<documentCollection name ="PROP_ACT">/ <collectionBody>/<component>/<documentRef>/@href

figure

Indicates an image supplemented by related text..

<subdivision> with the @refersTo attribute pointing to the <TLCConcept> with the @href attribute= "http://publications.europa.eu/resource/subdivision/FIGURE".

heading

COV DESCRIPTION

Numbering, accompanied by a term, if any.

<num>

<inline name = "num">

CONTEXT: <doc name ="ANNEX">/<preface>/ <container name="headerOfAnnex">

image

JPG DESCRIPTION

Graphical element depicting an object which

may contain alphanumeric data.

Note: Alphanumeric data contained in an image should always be editable..

<img>

indent

COV DESCRIPTION

Indicates each element of an enumeration preceded by a dash.

<indent>

CONTEXT: <list>

<item>

CONTEXT: <blocklist>

international agreement

COV DESCRIPTION

Indicates agreements concluded by the European Union with third parties and agreements concluded jointly by the Member States and the European Union with third parties.

<act name ="AGREE_INTERNATION">

introduction to the recitals

COV DESCRIPTION

Indicates the word 'whereas' at the beginning of the statement of the reasons [JPG 10.1.].

<recitals>/<intro>


30/03/2020 Page 119 of 124

introductory part

COV DESCRIPTION

One or more sentences or phrases in the

beginning of a paragraph, or of a subparagraph, or

of a point, preceding an enumeration (of points or

indents) and ending with a colon.

<intro>

CONTEXT: <list>

<listIntroduction>

CONTEXT: <blockList>

legal basis

COV DESCRIPTION

The provision(s) which directly confer competence to adopt the act, whether preceded or not by a general reference to the Treaty/ies.

<citation>/@refersTo that points to <TLCReference name="legalBasis">

legend

COV DESCRIPTION

Text detailing the meaning of the elements of an image, a table or a scientific formula it relates to.

to be defined

logo

COV DESCRIPTION

Graphic(al) element identifying an entity consisting of the emblem of the entity complemented by the name of the entity (author/proponent).

<container name = "logo">

note

COV DESCRIPTION

Consists of additional information giving further explanation/details to the reader.

<authorialNote>

numbered paragraph

COV DESCRIPTION

Indicates an independent subdivision of an article [JPG 15.4. (table)]

<article>/<paragraph>

<paragraph> must contain as first sub-element <num>

numbering

COV DESCRIPTION

Indicates the number or letter used for structural identification [JH C.9.3.2., p. 29].

inside <num>


30/03/2020 Page 120 of 124

part

COV DESCRIPTION

Indicates the highest level of higher subdivisions of an act [JPG 15.4.] or of an annex.

<part>

place and date

COV DESCRIPTION

Indicates the date of signature for acts adopted by ordinary legislative procedure, the budget and budget decisions adopted by the European Parliament and the Council [JPG 8.6. (4)] or the date of signature of other acts as well as the place.

<conclusions>/

CONTEXT: <act> or <bill>

<preface>/<block name = "placeAndDate">

CONTEXT: <documentCollection name ="PROP_ACT">

point

COV DESCRIPTION

Indicates each element of an enumeration under a paragraph or a subparagraph (this enumeration being generally preceded by an introductory phrase) or the basic unit generally used for the provisions of an annex

<list>/<point>

<blocklist>/<item>

<level>

CONTEXT: <doc name="ANNEX">

preamble

COV DESCRIPTION

Part of an act after the title of the act including the citations, the recitals and the solemn forms preceding the enacting terms.

<preamble>

procedure identifier

COV DESCRIPTION

Unique reference number for the interinstitutional procedures.

<docketNumber>

CONTEXT: <preface>/<container name="procedureIdentifier">

procedure stage

COV DESCRIPTION

Code or full wording indication of the stage of a procedure.

<inline name = "procedureStage">

proposal for a decision

COV DESCRIPTION

Version of a decision as issued by the proposing

entity or the consideration of its adoption by the

acting entity.

<documentCollection name="PROP_ACT">

Inside, it exists a <bill name="DEC.">


30/03/2020 Page 121 of 124

proposal for a directive

COV DESCRIPTION

Version of a directive as issued by the proposing


acting entity.


Inside, it exists a <bill name="DIR">

proposal for a regulation

COV DESCRIPTION

Version of a regulation as issued by the proposing


acting entity.


Inside, it exists a <bill name="REG">

proposing entity

COV DESCRIPTION

Name of the proponent institution.

<coverPage>/<container name="logo">

quotation (changed)

COV DESCRIPTION

Quoted passage of words of third parties reported in the text.

<embeddedText>

<embeddedStructure>

recital

COV DESCRIPTION

Recitals set out concise reasons for the chief provisions of the enacting terms [JPG 10.]

<recital>

reference

COV DESCRIPTION

Identifier assigned to a document by an entity.

<block name="reference">/<docNumber> The reference of the current document

<container name="crossReferences">/<ref> The reference of the documents referenced

regulation

COV DESCRIPTION

Legal act of the European Union specified in Article 288 TFEU.

<act name="REG">

row

COV DESCRIPTION

Represents, in a table, a set of related data horizontally.

<tr>


30/03/2020 Page 122 of 124

row header

COV DESCRIPTION

Table cell used to indicate the subject of a row.

<th> for any cell considered as a 'header'

scientific formula

COV DESCRIPTION

Indicates a complex technical or scientific expression.

<foreign> when the scientific formula is represented in MathML

<inline name=" mathTex "> when the scientific formula is in Latex

section

COV DESCRIPTION

Indicates the lowest level of higher subdivisions (JPG 15.4).

<section>

CONTEXT: <body> of <act> or <bill> or <mainBody> of <doc name = "ANNEX">

<tblock>

CONTEXT: <mainbody> of <doc name = "EXPL_MEMORANDUM">

signatory

COV DESCRIPTION

Information concerning the signing authority/person.

<block name = "signatory">

signature

COV DESCRIPTION

Includes the place and date of the signature of an act as well as the information about the signatory.

<conclusions>

subject

COV DESCRIPTION

Terms reflecting the essential topic of the subdivision of text they precede.

<heading>

<inline name = "num">

CONTEXT: <doc name ="ANNEX">/<preface>/ <container name="headerOfAnnex">

subparagraph

COV DESCRIPTION

Indicates the first level of an unnumbered subdivision of a numbered paragraph, point or indent, where there are at least two of such elements of subdivision. A single subparagraph is consequently not marked-up.

<subparagraph>

CONTEXT: <paragraph>

<alinea>

CONTEXT: <point> or <indent>

<list>

when it contains <point> or <indent >

<subdivision>

when it contains complex structure on <img> or <table>


30/03/2020 Page 123 of 124

sub-section

COV DESCRIPTION

Indicates, in exceptional cases and in long and highly structured texts, the division of a section.

<subsection (deprecated)>

table

COV DESCRIPTION

Indicates an arrangement of data in rows and columns, possibly preceded by a heading.

<table> if it is not preceded by a heading

<subdivision> with @refersTo attribute attribute pointing to the <TLCConcept> with the @href attribute= "http://publications.europa.eu/resource/subdivision/TABLE">


COV DESCRIPTION

Text to be inserted in the act to be amended in accordance with an amending instruction referring to insertion, addition or replacement.

<quotedStructure>

<quotedText>

text to be amended

COV DESCRIPTION

Text in the act to be amended.

to be defined

title

COV DESCRIPTION

Indicates in long and highly structured texts the grouping of higher subdivisions [JPG 15.4., p. 28].

<title>

title of the document

COV DESCRIPTION

The title of the document comprises all the information in the heading of the document which serves to identify it (JPG 7.1).

<longTitle>

CONTEXT: <preface>

type of document

COV DESCRIPTION

Indication of the type of document.

<docType>

NB: Not totally mapped to Common Vocabulary : when the document is a proposal for an act, use <docStage> for this indication.


30/03/2020 Page 124 of 124

unnumbered paragraph

COV DESCRIPTION

Indicates the sole element or a non-independent element of an article [JPG 15.4. (table)] or exceptionally an element of an annex.

<paragraph>

IT MUST NOT have <num> as first sub-element. 

CONTEXT: <doc name="EXPL_MEMORANDUM">

version

COV DESCRIPTION

Indicates the version of the document.

to be defined