Document Class: Normative Documents

Caveat. The definitions below are to be considered only as a general description with the sole purpose of providing an indication of the types of documents that may belong to each class and subclass.

UN document class

Normative Documents

subclasses

Charter

Description: foundational treaty outlining the conditions under which a body is organised, and defining its rights and privileges.

Code of Conduct

Description: rules outlining the responsibilities of, or proper practices for: individuals, parties, organizations, or countries on specific issues.

Code of Practice

Description: defines correct procedures on how to implement principles and/or standards.

Constitution

Description: a set of fundamental principles or established precedents according to which a body is acknowledged to be governed.

Convention

Description: mandatory regulations subject to ratification. Instruments usually negotiated under the auspices of an international organization.

Protocol

Description: international agreement that supplements a previous treaty or international agreement.

Recommendation

Description: provide guidance and may create reporting obligations for parties.

Rules

Description: prescribe principles governing conduct or procedure within a particular area of activity.

Rules of Procedure

Description: prescribe guides for conduct or actions, such as rules for conducting business within a body, as well as for the financial administration of organizations and their members.

Regulation

Description: set guides to enforce a statutory instrument or regulate activities.

Standard

Description: set of guides established by consensus outlining the responsibilities of, or proper practices for, individuals, parties, organizations or countries on specific issues.

Treaty

Description: international agreements concluded between States, and bilateral or multilateral agreements governed by international law to which international organizations are parties.

AKN4UN

AKN

AKN4UN

UN Document

AKN4UN

documentType
mandatory

subtype
mandatory

sub-class

@name sub-class

mandatory

value is prescribed

value is suggested

normative documents

<act> <bill>

provision

charter

charter

code of conduct

codeOfConduct

code of practice

codeOfPractice

constitution

constitution

convention

convention

protocol

protocol

recommendation

recommendation

rules

rules

rules of procedure

rulesOfProcedure

regulation

regulation

treaty

treaty

standard

standard

function

Formal provisions concerning commands, recommendations, opinions or expressions of will issued by a principal or a subsidiary organ or other empowered bodies.

Function Formal provisions concerning commands, recommendations, opinions or expressions of will issued or entered into by a principal or a subsidiary organ or other empowered bodies.

Structure Usually articulated in hierarchical structures in which the text is subdivided into higher and lower subdivisions.

authors

UN principal and subsidiary organs, funds, programs, specialized agencies, other entities deliberative bodies of intergovernmental organizations, conference, commission, etc.

editors

Secretariats of the assemblies, councils, conferences, boards, or international organizations, governmental organizations, etc.

Caveat. What follows is the modelling and description of the "Normative Documents Class" (logical normative document) in which a "normative document" may appear during its lifecycle.

The Normative Documents Class is not specific to the normative documents of any organization in particular. It lists all the possible characteristics that a normative document may have across all the UN organizations, since the objective is to cover all the variances that may exist. The description and modelling of the publications in which a normative document may be published is presented in the "Publication Document Class".

The Normative Documents Class will have to be localised by the different organizations, based on their specific editorial and style traditions, by selecting only the elements that are required to model all the relevant structural and semantic parts of a specific typology of a normative document.

Please note that the XML examples provided in the next sections should not be considered complete. Examples show only the essential structural elements of the mark-up and only the ones relevant in a specific context without any semantic or presentation markup in order to keep the XML "humanly’" readable.

Document Structure

The structure of normative documents may have the following elements:

Identification part

Title, proponent authority, identification, etc.

always present

Justificatory text

Purpose, motivations, justification or legal basis.

not always present.

Main content

Main text usually articulated in hierarchical structures.

always present

Closing formula

Closing formulas, date etc.

not always present.

Attachments

Informative or technical documents.

not always present.

Modelling

document type

<akomaNtoso>

<act contains="originalVersion" name="{AKN4UN:subclass}">

metadata

<meta>

<identification source="#{manifestationAuthor}1">

</identification>

</meta>

identification part

<preface>

(...)

</preface>

justificatory text

<preamble>

(...)

</preamble>

main content

<body>

(...)

</body>

closing formula

<conclusions>

(...)

</conclusions>

attachments

<attachments>

(...)

</attachments>

</act>

</akomaNtoso>

Examples

Below are some practical examples of the Akoma Ntoso mark-up of the main blocks of a normative document.

document type

source2

<akomaNtoso>

<act contains="originalVersion" name="{AKN4UN:subclass}">

identification part

<preface>

………

</preface>

???

preamble

<preamble>

………

</preamble>

???

main content

<body>

………

</body>

???

closing block

<conclusions>

…..

</conclusions>

???

annexes

<attachments>

…..

</attachments>

???

</act>

</akomaNtoso>

Identification part: <preface>

The identification part <preface> includes any matter found from the very beginning of a document up to where the <preamble> begins. It may contain information related to the title of the document, proponent authority, identification numbers, date of approval, etc. It may include long titles, tables of contents, and the like.

Normative documents may start with some or all of the information below, not necessarily in the same order:

document type

title

document authority

acronym

identifier

date of adoption

Modelling <preface>

For information about element specific usage, see 1.2 <preface>.

Examples

source3

???

modelling

<preface>
<p>
<docTitle>INTERNATIONAL <docType refersTo="#convention">CONVENTION</docType>

FOR THE SAFETY OF LIFE AT SEA <inline name="year" value="2004">2004</inline>
</docTitle>
</p>
</preface>

source4

???

modelling

<preface>

<p>
<docTitle>
<docType refersTo="#guidelines">GUIDELINES</docType> ON NUTRITION LABELLING

</docTitle>
<docNumber>CAC/GL 2-1985</docNumber>

Adopted in <inline name="year" value="1985" refersTo="#yearOfAdoption">1985</inline>.
Revision: <inline name="year" value="1993" refersTo="#yearOfRevision">1993 </inline>and

<inline name="year" value="2011" refersTo="#yearOfRevision">2011</inline>.

Amendment: <inline name="year" value="2003" refersTo="#yearOfAmendment">2003 </inline>,
<inline name="year" value="2006" refersTo="#yearOfAmendment">""2006 </inline>,

<inline name="year" value="2009" refersTo="#yearOfAmendment">""2009 </inline>,
<inline name="year" value="2010" refersTo="#yearOfAmendment">""2010 </inline>,

<inline name="year" value="2012" refersTo="#yearOfAmendment">""2012 </inline>,

<inline name="year" value="2013" refersTo="#yearOfAmendment">""2013 </inline>,

<inline name="year" value="2015" refersTo="#yearOfAmendment">""2015</inline> and

<inline name="year" value="2016" refersTo="#yearOfAmendment">""2016 </inline>.

ANNEX adopted in <inline name="year" value="2011" refersTo="#yearOfAdoption">2011</inline>.

Revision: <inline name="year" value="2013" refersTo="#yearOfAdoption">""2013</inline>,
<inline name="year" value="2015" refersTo="#yearOfAdoption">""2015</inline> and

<inline name="year" value="2016" refersTo="#yearOfAdoption">""2016</inline>

</p>

</preface>

Notes

Here we use the <inline> element to qualify the dates with a specific name indicating the type of date. For the years, we recommend using @value to expresse the value of the year followed by the @refersTo noun form of the word to describe the year, e.g. "Amendment" and "Adoption" which gives us : "yearAdoption" and "yearAmendment".

source5

???

modelling

<preface>

<p>
<docTitle><docType refersTo="#constitution">Constitution</docType> of the

<docAuthority refersTo="#unesco">United Nations Educational, Scientific and Cultural
Organization </docAuthority>

</docTitle>

Adopted in <docDate date="1945-11-16">

London on 16 November 1945</docDate> and amended by the General Conference at its

<session refersTo="#sessionSecond" value="2">2nd</session>,

<session refersTo="#sessionThird" value="3">3rd</session>,

<session refersTo="#sessionFourth" value="4">4th</session>,

<session refersTo="#sessionFifth" value="5">5th.</session>
</p>

</preface>

source6

???

modelling

<preface>

<p>
<docTitle>

<docType refersTo="#agreement">AGREEMENT

</docType> FOR THE ESTABLISHMENT OF A CENTRE ON INTEGRATED RURAL DEVELOPMENT
FOR AFRICA

</docTitle>
<inline name="subTitle">
FINAL ACT OF THE GOVERNMENT CONSULTATION ON THE ESTABLISHMENT OF A
CENTRE ON INTEGRATED RURAL DEVELOPMENT FOR AFRICA </inline>
<location refersTo="#arusha"> Arusha, Tanzania</location>,

<event name="interval" refersTo="#interval">

<date date="1979-09-18" refersTo="#startDate">18</date>

<date date="1979-09-21" refersTo="#endDate">21 September 1979</date></event>
</p>

</preface>

source7

???

modelling

<preface>

<p>
<docNumber>P089</docNumber>

<docTitle>

<docType>Protocol</docType>

of 1990 to the Night Work (Women) Convention (Revised), 1948

</docTitle>
<inline name="subTitle">Protocol of 1990 to the Convention concerning Night Work of Women
Employed in Industry (Revised 1948) (Entry into force: 26 Jun 1990)</inline> Adoption:
<location refersTo="#geneva"> Geneva</location>, <session refersTo="#sessionILC"
 value="77">77th ILC session</session> (<docDate date="1990-06-26">

26 Jun 1990</docDate>)
- Status:

<docStatus refersTo="#upToDateInstrument">Up-to-date instrument</docStatus>. </p>

</preface>

Justificatory text: <preamble>

The justificatory text includes any matter found after the <preface> up to where the <body> begins. It may contain one or more paragraphs stating purpose, aims, and justification of a normative document. They may refer to the legal basis, other normative documents, statements, etc.

This part may consist of one or more different paragraphs, usually not numbered, which state the considerations on the legal basis and rationale of a document. At times it might be structured as a single long sentence formatted into multiple paragraphs for readability, in which each paragraph begins with a verb.

The preambular part usually begins with an "enacting formula", followed by unnumbered paragraphs.

The preamble typically begins with a present, past or perfect participle or participial phrase in italics, and ends with a comma. Preamble paragraphs may be subdivided as follows:

First-degree sub-paragraphs: e.g. identified by lower-case letters between parentheses.

Second-degree sub-paragraphs: e.g. identified by lower-case roman numerals between parentheses.

Note: the styles may vary according to the language and organization.

Some or all the informational parts below, but not necessarily in the same order, may be found:

Recitals: motivations and justifications of the legal document.

Citations: references to other legal documents.

Enacting Formula: enacting sentences.

Paragraph(s).

Modelling <preamble>

For information about element specific usage, see section 1.4 <preamble>.

Examples

source8

???

modelling

<preamble>
<recitals>

<heading>Preamble</heading>
<recital>
<p> Whereas the Charter of the United Nations affirms, inter alia, the determination of Member
States to establish conditions under which justice may be maintained to achieve
international cooperation in promoting and encouraging respect for human rights and
fundamental freedoms without any discrimination,</p>
</recital>
</recitals>
</preamble>

source9

???

modelling

<preamble>

<container name="">

<block name="heading">PREAMBLE</block>
<formula name="enactingAuthority">
<p>The Parties to this Protocol, </p>
</formula>
<recitals>
<recital>
<p>

Considering that on 21 May 2003, the Fifty-sixth World Health Assembly adopted by consensus the WHO Framework Convention on Tobacco Control, which came into force on 27 February 2005;

</p>
</recital>
</recitals>

</container>

</preamble>

Here we have to use <block name="heading">PREAMBLE</block> and not <heading> because in this case we have also the "enacting formula" and "recital" that wrapped in a "conatainer" elements that does not support <heading>. Please note that all these "containement rules" will be managed by the editing software that will provide to the content editors only the correct options.

In <container name=""> the @name is required.

source

???

modelling

<preamble>

<container name="">

<recitals>
<heading>PREAMBLE</heading>
<recital>
<p>
Whereas it is provided ...(omissis)
</p>
</recital>
<recital>
<p>
And whereas...(omissis)
</p>
</recital>
</recitals>
<formula name="enactingFormula">
<p> NOW THEREFORE the Parties hereto agree as follows:</p>
</formula>
<container>

</preamble>

notes

If recitals are mumbered you may use eId and <num> e.g. <recital eId="recital_1"><num>1</num>

If you want to number recitals that are not explicitly numbered you may just use eId e.g. <recital eId="recital_1">

source10

???

modelling

<preamble>

<container name="">

<formula name="enactingAuthority">
<p>The General Conference...(omissis) </p>
</formula>
<block name="preamble"> Having been convened at Geneva by the Governing Body of the

International Labour Office,
and having met in its Third Session on 25 October 1921, and </block>
<block name="preamble"> Having decided upon the adoption of certain proposals with regard to the employment of
children and young persons in agriculture during the night, which is included in the third
item of the agenda of the Session, and </block>
<block name="preamble"> Having decided that these proposals shall take the form of a Recommendation,adopts the
following Recommendation, which may be cited as the Night Work of Children and Young Persons
(Agriculture) Recommendation, 1921, to be submitted to the Members of the International
Labour Organization for consideration with a view to effect being given to it by national
legislation or otherwise, in accordance with the provisions of the Constitution of the
International Labour Organization </block>
<formula name="enactingFormula">
<p> The General Conference of the International Labour Organization recommends:</p>
</formula>

</container>

</preamble>

Main content: <body>

The main content includes any matter found after the <preamble> up to the <conclusion>, or <attachments>, or the end of the document. It contains the main part of the document, which is characterised by a structural complexity that may vary depending on the document typology and purpose.

It is usually articulated in hierarchical structures in which the text is subdivided into higher subdivisions, basic units and lower subdivisions.

The higher subdivision may be called parts, sections, chapter etc. and groups the basic units. Higher subdivision may have Roman or Arabic numbers or letters to identify them and may or may not have a title.

The basic units (e.g. articles, clauses) may or may not have heading and may be numbered (Roman or Arabic numbers or letters) with a single numeration for the entire body or within each of the parts of which they may be composed of.

The lower subdivision may include paragraphs, sub-paragraphs, sub-points, etc. Single paragraph are usually not numbered or may be numbered with Roman or Arabic numbers or letters with different styling conventions.

<body>

Normative documents are usually modelled in hierarchical structures. By hierarchical structure we mean a structure organized with higher subdvision that groups basic units and lower subdivisions inside of the basic unit, much like a hierarchy of headings in a word document as heading1, heading2, heading3 and so on. The "hierarchy" in the hierarchy structure is analogous to a typical heading hierarchy in a document.

The <body> element is used for any document that presents an explicit hierarchy of parts, which may be identified by a meaningful name. The content is composed of higher levels subdivisions e.g. chapters, sections, etc.) that group basic units (e.g. article, section, etc.) and all the lower levels subdivisions they might contain (e.g. paragraphs, lists, etc.).

The Akoma Ntoso standard is neutral with respect to the legal drafting traditions and provides most of the hierarchical elements for modelling the body structure in a very precise way without prescribing any fixed order for the different hierarchical elements. It explicitly supports the following hierarchical containers in alphabetical order: alinea, article, book, chapter, clause, division, hcontainer, indent, level, list, paragraph, part, point, proviso, rule, section, subchapter, subclause, subdivision, sublist, subparagraph, subpart, subrule, subsection, subtitle, title, tome and transitional.

Please note that the word "paragraph" appears with two meanings in this section:

Legislative structure: corresponds to the <paragraph> hierarchical element when it is numbered or to the <alinea> element when it is not numbered.

Text (typographical) paragraph: it is the minimum unit of text that will be marked with a single <p> element.

The following table, taken from the Akoma Ntoso documentation, shows an example of the different hierarchical elements which fit the different legal traditions:

Anglophone

French

Portuguese

Spanish

AKOMA NOTOSO

Higher Subdivision

Tome

Tome

tome

Part

Partie (codes)

Parte (codes)

Parte

part

Livre (codes)

Livro (codes)

Libro

book

Title

Titre

Título

Título

title

Chapter

Chapitre

Capítulo

Capítulo

chapter

Subchapter

Article (US)

Section (codes)

Secção

Sección o Párrafo

section

Subsection (code)

SubSeçcão

subsection

level

level11

Basic Unit

Section

Rule

Article

Artigo

Artículo

article/

section/
rule

Lower Subdivision

Subsection

Clause (in US Constitution)

Alinéa

Alineas

Inciso

subsection
aliena

clause

Paragraph

Paragraphe

Paragrafo

paragraph

Proviso

proviso

Subparagraph

subparagraph

division

letra

point/item

número

point/item

Latin number

point/item

point/item

There are cases where the hierarchical levels are either not named or their naming is unclear. For instance, in some cases the reference might be simply stated as §7(f)(2), where it is not clear how the lower levels are named. For these undefined or inconsistent cases, the more generic <level> element may be used.

Please note that there are cases where it is possible to have headings that act as a divider, more than as hierarchical containers. These cases should be modelled using the <crossheading> element, which does not participate in the hierarchy of a document.

For the actual organization of the hierarchical elements and their specific content model please see the section "Hierarchical Elements".

Examples

source12

???

modelling

<body>
<part eId="part_I">
<num>PART I</num>
<heading>: INTRODUCTION</heading>
<article eId="part_I__art_1">
<num>ARTICLE 1</num>
<heading>Use of terms</heading>
<paragraph eId="part_I__art_1__para_1">
<num> 1.</num>
<content>
<p>

<def eId="def_1">"<term refersTo="#brokering">Brokering</term>" means acting as an agent for others, as in negotiating contracts, purchases, or sales in return for a fee or commission.</def>

</p>
</content>
</paragraph>
<paragraph eId="part_I__art_1__para_2">
<num> 2.</num>
<content>
<p>

<def eId="def_2">"<term refersTo="#cigarette">Cigarette</term>"means a roll of cut tobacco for smoking, enclosed in cigarette paper. This excludes specific regional products such as bidis, ang hoon, or other similar products which can be wrapped in paper or leaves. For the purpose of Article 8, "cigarette" also includes fine cut "roll your own" tobacco for the purposes of making a cigarette.</def>

</p>
</content>
</paragraph>
</article>
</part>
</body>

source13

???

modelling

<body>
<part eId="part_I">
<num>Part I. </num>
<heading>Definitions and scope</heading>
<chapter eId="part_I__chp_1">
<heading>Definitions</heading>
<article eId="part_I__chp_1__art_1">
<num>Article 1</num>
<list eId="part_I__chp_1__art_1__list_1">
<intro>
<p>For the purposes of the Convention:</p>
</intro>

<point eId="part_I__chp_1__art_1__list_1__point_a">
<num>(a)</num>
<content>
<p>commercial fishing means all fishing operations, including fishing
operations on rivers, lakes or canals, with the exception of
subsistence fishing and recreational fishing;</p>
</content>
</point>
 <point eId="part_I__chp_1__art_1__list_1__point_b">
<num>(b)</num>
<content>
<p>competent authority means the minister, government department or
other authority having power to issue and enforce regulations,
orders or other instructions having the force of law in respect of
the subject matter of the provision concerned;</p>
</content>
</point>

</list>
</article>
</chapter>
</part>
</body>

source14

???

modelling

<body>
<article eId="art_10">
<num>ARTICLE 10</num>
<heading>Security and preventive measures </heading>
<paragraph eId="art_10__para_1">
<num>1.</num>
<list eId="art_10__para_1__list_1">

<intro> <p>Each Party shall, where appropriate, consistent with its national law and the objectives of the WHO Framework Convention on Tobacco Control, require that all natural and legal persons subject to Article 6 take the necessary measures to prevent the diversion of tobacco products into illicit trade channels, including, inter alia:</p></intro>

<point eId="art_10__para_1__list_1__point_a">
<num>(a)</num>
<list eId="art_10__para_1__list_1__point_a__list_1">
<intro>
<p>reporting to the competent authorities: </p>
</intro>
<point eId="art_10__para_1__list_1__point_a__list_1__point_i">
<num>(i)</num>
<content>
<p>the cross-border transfer of cash in amounts stipulated in
national law or of cross-border payments in kind; and </p>
</content>
</point>
<point eId="art_10__para_1__list_1__point_a__list_1__point_ii">>
<num>(ii)</num>
<content>
<p>all "suspicious transactions"; and</p>
</content>
</point>

</list>
</point>
</list>
</paragraph>
</article>
</body>

source15

???

modelling

<body>
<article eId="art_9">
<num>Article 9.</num>
<heading>Information exchange </heading>
<paragraph eId="art_9__para_9-1">
<num>9.1.</num>
<list eId="art_9__para_9-1__list_1">
<intro>
<p>Governments should: </p>
</intro>

<point eId="art_9__para_9-1__list_1__point_1">
<num>9.1.1</num>
<content>
<p>promote the establishment or strengthening of networks for information
exchange on pesticides through national institutions, international,
regional and subregional organizations and public sector groups; </p>
</content>
</point>
<point eId="art_9__para_9-1__list_1__point_2">
<num>9.1.2</num>
<list eId="art_9__para_9-1__list_1__point_2__list_1">
<intro>
<p>facilitate the exchange of information between regulatory authorities
to strengthen cooperative efforts. The information to be exchanged
should include: </p>
</intro>
<point eId="art_9__para_9-1__list_1__point_2__list_1__point_1">
<num>9.1.2.1</num>
<content>
<p>actions to ban or severely restrict a pesticide in order to
protect human health or the environment, and additional
information upon request; </p>
</content>
</point>
<point eId="art_9__para_9-1__list_1__point_2__list_1__point_2">
<num>9.1.2.2</num>
<content>
<p>scientific, technical, economic, regulatory and legal
information</p>
</content>
</point>
</list>
</point>

</list>
</paragraph>
</article>
</body>

source16

???

(omissis)

???

modelling

<body>
<article eId="art_VIII">
<num>Article VIII</num>
<heading>Amendments*</heading>
<list eId="art_VIII__list_1">

<point eId="art_VIII__list_1__point_a">
<num>(a) </num>
<content>
<p>The present Convention may be amended by either of the procedures specified
in the following paragraphs.</p>
</content>
</point>
<point eId="art_VIII__list_1__point_b">
<num>(b) </num>
<list eId="art_VIII__list_1__point_b__list_1">
<intro>
<p>Amendments after consideration within the Organization: </p>
</intro>

<point eId="art_VIII__list_1__point_b__list_1__point_i">
<num>(i)</num>
<content>
<p>Any amendment proposed by a Contracting Government shall be submitted to
the Secretary-General of the Organization, who shall then circulate it
to all Members of the Organization and all Contracting Governments at
least six months prior to its consideration.</p>
</content>
</point>
<point eId="art_VIII__list_1__point_b__list_1__point_ii">
<num>(ii)</num>
<content>
<p>Any amendment proposed and circulated as above shall be referred to the
Maritime Safety Committee of the Organization for consideration.</p>
</content>
</point>
<point eId="art_VIII__list_1__point_b__list_1__point_iv">
<num>(iv)</num>
<list eId="art_VIII__list_1__point_b__list_1__point_iv__list_1">
<num>(1)</num>
<point eId="art_VIII__list_1__point_b__list_1__point_iv__list_1__point_1">
<num>(1)</num>
<content>
<p>An amendment to an article of the Convention or to chapter I of
the annex shall be deemed to have been accepted on the date on
which it is accepted by two thirds of the Contracting
Governments.</p>
</content>
</point>
</list>
<point eId="art_VIII__list_1__point_b__list_1__point_iv__list_1__point_2">
<num>(2)</num>
<list
 eId="art_VIII__list_1__point_b__list_1__point_iv__list_1__point_2__list_1">
<point
 eId="art_VIII__list_1__point_b__list_1__point_iv__list_1__point_2__list_1__point_aa">
<num>(aa)</num>
<content>
<p>An amendment to the annex other than chapter I shall be
deemed to have been accepted</p>
</content>
</point>
</list>

</point>
</point>
</point>

</list>
</article>
</body>

source17

???

modelling

<body>
<part eId="part_XX">
<num>PART XX</num>
<heading>Miscellaneous provisions</heading>
<article eId="art_76">
<num>Article 76</num>
<heading>Signature and acceptance</heading>
<list eId="art_76__list_1">
<intro>
<p>Subject to the provisions of part III the present Convention shall remain
open for signature or acceptance and States may become Parties to the
Convention by: </p>
</intro>

<point eId="art_76__list_1__point_a">
<num>(a)</num>
<content>
<p>Signature without reservation as to acceptance;</p>
</content>
</point>
<point eId="art_76__list_1__point_b">
<num>(b)</num>
<content>
<p>Signature subject to acceptance followed by acceptance; or</p>
</content>
</point>
<point eId="art_76__list_1__point_c">
<num>(c)</num>
<content>
<p>Acceptance.</p>
</content>
</point>

<wrapUp>
<p>Acceptance shall be effected by the deposit of an instrument with the
Secretary-General of the United Nations</p>
</wrapUp>
</list>
</article>
</part>
</body>

source18

???

modelling

<body>
<part eId="part_I-A">
<num>Part I-A</num>
<heading> – Safety measures</heading>
<chapter eId="part_I-A__chp_1">
<num>Chapter 1</num>
<heading>General</heading>
<paragraph eId="part_I-A__chp_1__para_1-1">
<num>1.1</num>
<heading> Structure of this part</heading>
<list eId="part_I-A__chp_1__para_1-1__list_1">
<intro>
<p>Each chapter in this part consists of the overall goal of the chapter,
functional requirements to fulfil the goal, and regulations. A ship
shall be considered to meet a functional requirement set out in this
part when either:</p>
</intro>

<point eId="part_I-A__chp_1__para_1-1__list_1__point_1">
<num>.1</num>
<content>
<p> the ship’s design and arrangements comply with all the regulations
associated with that functional requirement; or</p>
</content>
</point>

<!-- omissis -->
</list>
<!-- omissis-->
</paragraph>
</chapter>
</part>
</body>

source19

???

modelling

<body>
<chapter eId="chp_XV">
<num>XV. </num>
<heading>ELECTIONS TO PRINCIPAL ORGANS</heading>
<division eId="chp_XV__div_1">
<heading>GENERAL PROVISIONS</heading>
<level eId="chp_XV__div_1__level_1">
<heading>Terms of office</heading>
<rule eId="chp_XV__div_1__level_1__rule_139">
<num> Rule 139</num>
<content>
<p>Except as provided in rule 147, the term of office of members of Councils
shall begin on 1 January following their election by the General
Assembly and shall end on 31 December following the election of their
successors. </p>
</content>
</rule>
</level>
</division>
</chapter>
</body>

source20

???

modelling

<body>
<rule eId="rule_16bis">
<num>Rule 16bis</num>
<heading>Extension of Time Limits for Payment of Fees </heading>
<paragraph eId="rule_16bis__para_16bis-1">
<num>16bis.1 </num>
<heading>Invitation by the Receiving Office </heading>
<list eId="rule_16bis__para_16bis-1__list_1">

<point eId="rule_16bis__para_16bis-1__list_1__point_a">
<num>(a)</num>
<content>
<p>Where, by the time they are due under Rules 14.1(c), 15.3 and 16.1(f),
the receiving Office finds that no fees were paid to it, or that the
amount paid to it is insufficient to cover the transmittal fee, the
international filing fee and the search fee, the receiving Office shall,
subject to paragraph (d), invite the applicant to pay to it the amount
required to cover those fees, together with, where applicable, the late
payment fee under Rule 16bis.2, within a time limit of one month from
the date of the invitation.</p>
</content>
</point>

</list>
</paragraph>
</rule>
</body>

source21

???

modelling

<body>
<rule eId="rule_75" status="removed">
<num>Rule 75</num>
<content>
<p>[Deleted]</p>
</content>
</rule>
<rule eId="rule_76">
<num>Rule 76</num>
<heading>Translation of Priority Document; Application of Certain Rules to Procedures before
Elected Offices </heading>
<paragraph eId="rule_76-1" status="removed" class="concatenated">
<num>76.1</num>
<content>
<p>
<omissis>,</omissis>
</p>
</content>
</paragraph>
<paragraph eId="rule_76-2" status="removed" class="concatenated">
<num>76.2</num>
<content>
<p>
<omissis>, and</omissis>
</p>
</content>
</paragraph>
<paragraph eId="rule_76-3" status="removed">
<num>76.3</num>
<content>
<p> [Deleted] </p>
</content>
</paragraph>
<paragraph eId="rule_76-4">
<num>76.4</num>
<heading>Time Limit for Translation of Priority Document </heading>
<content>
<p> The applicant shall not be required to furnish to any elected Office a
translation of the priority document before the expiration of the applicable
time limit under Article 39.</p>
</content>
</paragraph>
</rule>
</body>

notes

Here the @status attribute is used to indicate that the paragraphs 76.1, 76.2 and 76.3 have been deleted by setting its value to "removed".

There is an additional class attribute set with @class=’concatenated’ which is used for presentation purposes, to show the contents of the consecutively deleted paragraphs on the same line.

You will notice the <omissis> tag used in the content of the paragraph. This has been used to indicate that the content in the paragraph is not the original content of the paragraph, and should not be considered as such. The <omissis> tag is typically used for legal redactions from normative text.

A question may be asked here as to why we have used <paragraph> tags to indicate the deleted paragraphs. The reason is to ensure consistency and continuity in the mark-up (especially if you have to renumber), –at an earlier stage of the life of the document the paragraphs existed with content, and were later deleted – thus the empty paragraphs act as placeholders for the deletions.

Closing formula: <conclusion>

The closing formula includes all concluding material (e.g. closing formula(s), date(s) and signature(s)) and is placed at the end of the main document, typically before the Annexes.

Some or all the info parts below, not necessarily in the same order, may be found in this part:

date of execution

place/site

witnessing clause

parties

Modelling <conclusions>

For information about element specific usage, see section 1.6 <conclusions>.

Examples

source22

???

modelling

<conclusions>

<container>
<formula name="witnessingClause">
<p> IN WITNESS WHEREOF, the undersigned Plenipotentiaries, being duly authorized, have
signed this Agreement.</p>
</formula>
<p> DONE in <location refersTo="#rome">Rome </location>on this <date refersTo="#dateEvent"
 date="2009-11-22"> Twenty-second day of November, 2009.</date>
</p>

</container>

</conclusions>

source23

???

modelling

<conclusions>

<container>
<formula name="witnessingClause">
<p>IN WITNESS WHEREOF the duly authorized representatives of the States whose names appear
hereunder have signed this Final Act.</p>
</formula>
<p>
<signature>For <formula name="parties"><organization refersTo="#memberAlbania"
 >Albania</organization>: <person refersTo="#rolandKristo"
 as="#representativeAlbania">Roland Kristo </person></formula>
</signature>
</p>

</container>

</conclusions>

source24

???

modelling

<conclusions>

<container>
<formula name="witnessingClause">
<p>IN WITNESS WHEREOF the undersigned Plenipotentiaries, having been duly authorized, have
signed this Protocol.</p>
</formula>
<p>DONE at Beijing on the tenth day of September of the year Two Thousand and Ten in the
English, Arabic, Chinese, French, Russian and Spanish languages, all texts being equally
authentic, such authenticity to take effect upon verification by the Secretariat of the
Conference under the authority of the President of the Conference within ninety days hereof
as to the conformity of the texts with one another.</p>
<p>This Protocol shall remain deposited in the archives of the International Civil Aviation
Organization and certified copies thereof shall be transmitted by the Depositary to all
Contracting States to this Protocol.</p>

</container>

</conclusions>

Annexes/Attachments: <attachments>

The annexes block includes all additional material in normative documents. They are generally autonomous documents that the normative document adopts or endorses, e.g. international agreements, treaties etc. They all retain their independent structure and formats. When such a document appears after the closing formula, it is structurally considered an annex.

The "additional material" typically appears after the main text of the normative document and may be titled with the word Annex, Attachment, Schedule, Tables, etc. and, usually, a descriptive heading.

Annexes in the strict sense are used as a means of presenting provisions or parts of provisions separately from the body of the enacting terms, in particular because of their technical nature: e.g. rules to be applied by specific actors, lists of products, tables of figures, plans and drawings and so on.

All these documents are "annexed" and by their very nature an integral part of the normative document. While pre-existing legal documents that are endorsed or referenced by normative documents (e.g. rules of subordinate bodies or international agreements) are generally "attached".

Modelling <attachments>

For information about element specific usage, see section 1.7 <attachments>.

Examples

source25

???

(omissis)

???

modelling

(Annex 1)

<attachments>
<attachment>
<doc name="annex">
<meta> <meta/>
<preface>
<p>
<docType>ANNEX</docType>
<docNumber>I</docNumber>
<docTitle>HIGHLY MIGRATORY SPECIES</docTitle>
</p>
</preface>
<mainBody>
<list eId="list_1">
<point eId="list_1__point_1">
<num>1.</num>
<content>
<p>
<term refersTo="albacoreTuna">Albacore tuna</term>: <term
 refersTo="thunnusAlalunga">Thunnus alalunga.</term>
</p>
</content>
</point>
<point eId="list_1__point_2">
<num>2.</num>
<content>
<p>
<term refersTo="bluefinTuna">Bluefin tuna</term>: <term
 refersTo="thunnusthynnus">Thunnus thynnus. </term>
</p>
</content>
</point>
<point eId="list_1__point_3">
<num>3.</num>
<content>
<p>
<term refersTo="bigeyeTuna">Bigeye tuna</term>: <term
 refersTo="thunnusObesus">Thunnus obesus. </term>
</p>
</content>
</point>
<point eId="list_1__point_4">
<num>5.</num>
<content>
<p>
<term refersTo="skipjackTuna">Skipjack tuna</term>: <term
 refersTo="thunnusKatsuwonusPelamis">Katsuwonus pelamis.</term>
</p>
</content>
</point>
</list>
</mainBody>
</doc>
</attachment>

modelling
(Annex 2)

<attachments>

<attachment>
<doc name="annex">
…………<meta> … </meta>
<preface>
<p>
<docType>ANNEX</docType>
<docNumber>II</docNumber>. <docTitle>COMMISSION ON THE LIMITS OF THE CONTINENTAL
SHELF</docTitle>
</p>
</preface>
<mainBody>
<article eId="art_1q">
<num>Article 1</num>
<content>
<p>In accordance with the provisions of article 76, a Commission on the
Limits of the Continental Shelf beyond 200 nautical miles shall be
established in conformity with the following articles.</p>
</content>
</article>
<article eId="art_2">
<num>Article 2</num>
<paragraph eId="art_2_para_1">
<num>1.</num>
<content>
<p>The Commission shall consist of 21 members who shall be experts in
the field of geology, geophysics or hydrography, elected by States
Parties to this Convention from among their nationals, having due
regard to the need to ensure equitable geographical representation,
who shall serve in their personal capacities. 2</p>
</content>
</paragraph>
</article>
</mainBody>
</doc>
</attachment>
</attachments>

source26

???

modelling

<attachments>
<attachment>
<doc name="appendix">

…………<meta> … </meta>

<preface>
<p>
<docType>APPENDIX</docType>
<docNumber> 1</docNumber>. <docTitle>Form of Certificate for Ships operating in
Polar Waters </docTitle>
</p>
</preface>
<mainBody>
<tblock>
<heading>POLAR SHIP CERTIFICATE </heading>
<subheading>This Certificate shall be supplemented by a Record of Equipment for
the Polar Ship Certificate</subheading>
<block name="field"> (Official seal)</block>
<block name="field"> (State)</block>
<block name="text"> Issued under the provisions of the</block>
</tblock>
</mainBody>
</doc>
</attachment>
</attachments>

1 The author of the XML markup, the person/organization who take the responsibility for information provided.

2 http://www.fao.org/3/a-i5469t.pdf

3 http://library.arcticportal.org/1696/1/SOLAS_consolidated_edition2004.pdf

4 http://www.fao.org/fao-who-codexalimentarius/sh-proxy/es/?lnk=1&url=https%253A%252F%252Fworkspace.fao.org%252Fsites%252Fcodex%252FStandards%252FCAC%2BGL%2B2-1985%252FCXG_002e.pdf

5 http://unesdoc.unesco.org/images/0022/002269/226924e.pdf#page=6

6 http://www.fao.org/fileadmin/user_upload/legal/docs/017t-e.pdf

7 http://www.ilo.org/dyn/normlex/en/f?p=NORMLEXPUB:12100:0::NO::P12100_INSTRUMENT_ID:312335

8 http://www.un.org/ga/search/view_doc.asp?symbol=A/RES/66/106 , page 2

9 http://apps.who.int/iris/bitstream/10665/80873/1/9789241505246_eng.pdf?ua=1&ua=1 , page 3

10 http://ilo.org/dyn/normlex/en/f?p=NORMLEXPUB:12100:0::NO::P12100_ILO_CODE:R014

11 In the cases where the hierarchical levels are either not named or their naming is unclear the more generic <level> element may be used.

12 http://apps.who.int/iris/bitstream/10665/80873/1/9789241505246_eng.pdf?ua=1&ua=1 , page 6

13 http://www.ilo.org/dyn/normlex/en/f?p=NORMLEXPUB:12100:0::NO:12100:P12100_INSTRUMENT_ID:312333:NO

14 http://apps.who.int/iris/bitstream/10665/80873/1/9789241505246_eng.pdf?ua=1&ua=1 page 19

15 ftp://ftp.fao.org/docrep/fao/005/y4544e/y4544e00.pdf, page 21

16 https://www.dropbox.com/s/4d8qvgai15u2qmn/SOLAS%202014-E.pdf?dl=0 , page 7

17 https://www.dropbox.com/s/ir7r7x9j05a0g2h/BASIC%20DOCUMENTS%20I.pdf?dl=0%22https://www.dropbox.com/s/ir7r7x9j05a0g2h/BASIC%20DOCUMENTS%20I.pdf?dl= , page 29

18 https://www.dropbox.com/s/n958pgkt6749gnm/Polar%20Code.pdf?dl=0, page 15

19 http://www.un.org/ga/search/view_doc.asp?symbol=A/520/rev.17&Lang=E

20 http://www.wipo.int/export/sites/www/pct/en/texts/pdf/pct_regs.pdf

21 http://www.wipo.int/export/sites/www/pct/en/texts/pdf/pct_regs.pdf, page 149

22 http://www.fao.org/3/a-i1644t.pdf , page 24

23 http://www.fao.org/fileadmin/user_upload/legal/docs/030t-e.pdf , page 1

24 https://www.unodc.org/tldb/en/2010_protocol_convention_unlawful_seizure_aircraft.html

25 http://www.un.org/depts/los/convention_agreements/texts/unclos/unclos_e.pdf Annex 1,2 : page 143

26 http://www.imo.org/en/MediaCentre/HotTopics/polar/Documents/POLAR%20CODE%20TEXT%20AS%20ADOPTED.pdf , page 44