Document Class: Deliberative Documents
For the Deliberative Documents Class, "resolution" and "decision" were modelled individually because of their relevance in the context of the UN normative documents and also because their structure may also be quite different.
Subclass: Resolution
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 | Deliberative documents |
subclass | Resolution Description: formal expressions of the will of a principal or subsidiary organ or other empowered bodies. |
AKN4UN | AKN | AKN4UN | UN Document | AKN4UN |
documentType | subtype | sub-class | @name subclass mandatory | |
value is prescribed | value is suggested | |||
<statement> | deliberation | resolution | resolutionDraft | |
resolution |
function | Function formal expressions of the opinion or will of a principal or subsidiary organ or other empowered bodies intended to express the opinions and will of the Members, provide policy recommendations and assign mandates and adopt codes, guidelines, procedures, recommendations, amendments to codes, conventions, etc. Structure open structure documents, sometimes articulated in hierarchical structures in which the text is subdivided into higher and lower subdivisions, generally including a preamble and operative paragraphs. |
authors | UN principal and subsidiary organs, funds, programs, specialized agencies and other entities’ deliberative bodies. |
editors | Secretariats of the assemblies, councils, conferences, boards, or other entities. |
Caveat. What follows is the modelling and description of the "Resolution Document Class" which is the logical component of the resolution publication in which a "resolution" may appear during its lifecycle.
The Resolution Document Class is not specific to the resolution of any organization in particular. It will list all the possible characteristics that a resolution 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 resolution may be published is presented in the "Publication Document Class".
The Resolution Document 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 any specific typology of resolutions.
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
Description
The structure of a resolution may have the following elements:
Identification part Title, proponent authority, identification numbers, date of approval, etc. | always present |
Preamble One or more paragraphs stating purpose, aims, and justification of a resolution. | not always present. |
Operative paragraphs One or more paragraphs detailing the resolution. | always present. |
Closing formula e.g. dates, signatures, formulas, etc. | not always present. |
Annexes Annexes / Attachments that supplement the content of the document. | not always present. |
Modelling
This section presents the most important Akoma Ntoso elements and attributes necessary to model the general structure of a resolution.
document type | <akomaNtoso> |
metadata | <meta> |
identification part | <preface> (...) </preface> |
preamble | <preamble> (...) </preamble> |
operative block | <mainBody> (...) </mainBody> |
closing block | <conclusions> (...) </conclusions> |
annexes | <attachments> (...) </attachments> |
</statement>
|
Examples
Below are some practical examples of the Akoma Ntoso mark-up of the main blocks of the resolution.
document type | <akomaNtoso> | |
identification part27 | <preface> (...) </preface> | |
preamble | <preamble> (...) </preamble> | |
operative block | <mainBody> (...) </mainBody> | |
closing block | <conclusions> (...) </conclusions> | |
</statement> |
Example 2 with annex
document type | <akomaNtoso> | |
identification part28 | <preface> (...) </preface> | |
preamble | <preamble> (...) </preamble> | |
operative block | <mainBody> (...) </mainBody> | |
closing block | <conclusions> (...) </conclusions> | |
annexes | <attachments> (...) </attachments> | |
</statement> |
Identification part: <preface>
The identification part <preface> </preface> is meant to include 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, and the like. Typically resolutions start with some or all the information listed below, not necessarily in the same order:
document type
document authority
identifier
title, usually preceded or followed by the resolution’s identifier
Modelling <preface>
For information about element specific usage, see 1.2 <preface>.
Examples
text | |
modelling | <preface> |
text | |
modelling | <preface> |
text29 | |
modelling | <preface> |
modelling | <preface> </docDate> (<ref href="/akn/un/{documentIRIparts}" (<ref href="/akn/un/{documentIRIparts}" |
note | The @name attribute on the <container> element, simply gives a name to the generic <container> element. We do not prescribe a name for this in the rules, as the choice of naming them may be different across organizations, and even the way the content is grouped and structured may vary across documents and across organizations. In the above example the @name attribute has been used to identify some blocks of text as authorial, and others as editorial. |
| |
modelling | <preface> |
notes | |
Introductory block: <preamble>
One or more paragraphs stating purpose, aims, and justification of a resolution. They may refer to the legal basis, other resolutions and statements, recognise efforts of other bodies or statements on the topic, its significance and its impact.
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. Preambular 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.
Irregular structures
Please note the following irregular cases:
No preambular paragraph. There are resolutions, e.g. resolutions adopting a declaration, that do not have any preambular paragraphs.
More than one preambular parts. There are resolutions that have more than one "preambular parts" with related operative clauses.
Modelling <preamble>
For information about element specific usage, see section 1.4 <preamble>.
No preambular paragraph
The case of "no preambular paragraph" will be modelled including only the enacting formula in the <preamble>, like this:
<preamble>
<formula name="enactingFormula">
<p>The General Assembly,</p>
</formula>
</preamble>
More than one preambular parts
The case of "more than one preambular parts" with related operative clauses happens when text similar in language and semantic to the preamble appears in the body / content of the document.
Even if they are actually in the "body" part of the document, we deal with them here because of their being actually semantically "preambular". The preambular parts in the body may be identified by the language they use, usually the English sentence usaully starts with a verb in the present-participle form ("Having", "Affirming", "Endorsing"…).
To handle these cases of preambular parts in the body of a document the <crossHeading> element must be used, even if the <block> element is very similar to <crossHeading> because these preambular parts happen to be within AKN hierarchical sections in the body of a resolusion, and in this context only other hierarchical elements are allowed by Akoma Ntoso.
The <crossHeading> element needs to be qualified with the @refersTo="#preamble", to explicitly indicate that it is preambular. <crossHeading> is typically used to mark preambular paragraphs.
<crossHeading eId="sec_1__crossHeading_1" refersTo="#preamble">
Having considered the report of
the Secretary-General on the request for a subvention to the
Extraordinary Chambers in the Courts of Cambodia and the related
report of the Advisory Committee on Administrative and Budgetary Questions
</crossheading
The ontological concept definition of preamble may look like this:
<meta>
<references>
<TLCConcept eId="preamble" href="/akn/ontology/concept/un/preamble" showAs="preamble"/>
</references>
</meta>
Examples
example32 | |
modelling | <preamble>
<container name=""> <block name="preamble" eId="block_1"> Recalling its Resolution 8/81 (21st Session, November 1981) which adopted the first version of the World Soil Charter;</block> <block name="preamble" eId="block_2">Noting with appreciation the timely initiative of the organs of the recently established Global Soil Partnership (GSP), namely its Plenary Assembly and Intergovernmental Technical Panel on Soils, to assess the continued validity of the Charter and to develop a revised text more attuned to present and challenging soil issues and contexts; </block> </container> </preamble> |
example | |
modelling | <preamble>
<container name=""> <block name="preamble" eId="block_1">Having considered the report on contributing to social and <container> </preamble> |
example33 | |
modelling | <preamble>
<container name=""> <block name="preamble" eId="block_1">RECALLING Article 15(j) of the Convention on the <container> </preamble> |
Irregular structures
No preambular paragraph
example | |
modelling | <preamble> <formula name="enactingAuthority"> </mainBody> |
note | In this example, the body of the document has only a paragraph of text. The text needs to be wrapped in a structural tag, so we use <paragraph> and place the text content inside it. The <p> in AKN is a generic inline tag, and should always appear inside a container element. In this case we use the <paragraph> to express the structural semantic. |
More than one preambular parts
Multiple preambular parts34 First part | |
Second part |
text | (omissis) |
modelling | <mainBody> </section> (omissis) <section eId="sec_II"> <num>II </num> |
<mainBody> <section eId="sec_III"> </mainBody> | |
Main Content: <mainBody>
The operative block <mainBody> </mainBody> is meant to include any matter found after the <preamble> up to where the <conclusion> or <attachments> or the end of the document. It contains one or more paragraphs stating the opinion of the organ or the action to be taken.
The main content is organized in "operative paragraphs":
Each operative paragraph begins with an operative verb (or phrase).
Operative paragraphs are numbered with Arabic numerals, but a single operative paragraph is not numbered.
Each paragraph may have sub-paragraphs.
Headings and sub-headings may be added. There are several variations in structure with no fixed hierarchy even within an organization.
Subdivision: some operative sections may be subdivided in parts, sections, etc.
There are resolutions that have subdivisions only in the "operative paragraphs".
There are resolutions that have subdivisions in the preamble that may continue in operative paragraphs.
<mainBody>
The <mainBody> element may contain all types of AKN groups of elements. In the conctext of Document Class Deliberative Documents only hierarchical and block containers elements are allowed. See the table below:
AKN4UN | AKN | body element | Supported elements |
Deliberative Documents | <statement> | <mainBody> | Element group: hierElements 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, transitional |
Element group: blockElements block, blockContainer, blockList, foreign, ol, p, table, tblock, toc, ul |
For the content model used by hierarchical and block containers please see the relevant sections.
Examples
text | |
modelling | <paragraph eId="para_7"> |
text | |
modelling | <section eId="sec_I"> |
Text | |
modelling | <division eId="part_A__sec_I__division_1"> (omiss) (omiss) |
note | The <division> element groups different paragraphs with a heading. |
text | |
modelling | <list eId="part_A__sec_I__division_1__para_67__list_1"> |
text | |
modelling | <paragraph eId="para_8"> <paragraph eId="para_8"> <num>8. </num> <list eId="para_8__list_1"> <intro eId="para_8__list_1__intro"> <p> The qualifications are as follows: </p> </intro> <point eId="para_8__list_1__point_a"> <num>(a)</num> <heading>Education. </heading> <content> <p>Advanced university degree (master’s degree or equivalent) in business management, economics, finance, banking and portfolio investment management or related fields; </p> </content> </point> <point eId="para_8__list_1__point_b"> <num>(b)</num> <heading> Work experience. </heading> <list> <intro> <p class="concatenated">Over 20 years of proven progressively responsible experience in the management of economic, social security and/or financial policies and activities for governmental or intergovernmental organizations or for substantial private concerns, including a proven track record of extensive relevant experience in the management of the investment of complex portfolios of assets of various classes, such as pension funds, including their risk management, and in financial markets.</p> <p class="concatenated">Demonstrated direct knowledge of and experience in managing financial, economic and investment policies, including:</p> </intro> <point> <num>(i) </num> <content> <p>Defining and overseeing investment policy for substantial and diversified investment portfolios having long-term return objectives, including policies for investment objectives, risk appetite and tolerance, the risk framework, the investment milieu, restrictions on investments and social responsibility considerations;</p> </content> </point> </list> </point> </list> </paragraph> |
text | |
modelling | <part eId="part_I"> |
Irregular structures
Resolutions issued under the same number
Some resolutions issued under the same number and identified with a capital letter may be issued separately (e.g.: A/RES/68/24735 and A/RES/68/247 B36).
Those issued in the same document (see A/RES/69/96 A-B37) will have to be modelled as in the following example.
text38 | (omissis) |
modelling | In this document, the <documentRef> element allows referencing individual logical components. In this particular resolution, the logical components are the two Resolutions A and B, which are components of the main resolution. So <documentRef> provides a reference to each of the individual Resolutions, which are described in the <components> section of the document (as they are logical components of the main Resolution). There are two <component> definitions in <components> each corresponding to a Resolution. We use <documentRef> to provide a reference to each individual resolution which is part of the main Resolution, however <documentRef> is not merely a reference, and it implies that the contents of the referenced document are included from that point onwards in the document body. For visual/print purposes, this will not be evident to the reader / end-user, since to them it will appear like a continuous document in the body of the main resolution. <akomaNtoso> <component> </component>
</documentCollection>
|
Resolution A | <akomaNtoso> Taking note of the comprehensive and important report of the </block> </preamble> |
Resolution B | <?xml version="1.0" encoding="UTF-8"?> |
notes | Note that the two resolutions, A and B, inside the main resolution 69/96, have their own numbering of paragraphs and sections independent of each other. |
Endorsed/adopted document ebedded in the body of the resolution
In some resolutions, documents that a resolution may adopt or endorse (e.g. declarations, policy document, etc.) may appear at the end of an operative clause (or in the middle of an operative clause) but before the closing formula. These documents all retain their independent structures and formats.
In these cases, we use <embeddedStructure> and <documentRef> for referencing the whole structure of the embedded document, and continue the contents of the document after this. In the table below we provide an example of this scenario.
If the document that is endorsed/adopted is instead after the closing formula, it is structurally considered an annex. Please see the section Annex/attachments ahead.
text39 | (omissis) |
modelling | The publication contains resolution 70/1. The Resolution 70/1 contains the Annex of Resolution no: 69/31540, page 1 embedded in the content, not as an annex because it falls in between the operative clause "Adopt …." And the closing fornula. |
Preface of the resolution 70/1 | <preface> |
Preamble | <preamble> |
(omissis) | |
Body41 | <mainBody> <embeddedStructure> <documentRef eId="docref_1" showAs="Transforming our world: the 2030 Agenda for Sustainable Development" ref="/akn/un/collection/publication/ga/2015-09-15/A-RES-69-315/!annex "/>"" </embeddedStructure> (omissis) </p> <componentRef src="#addendum" showAs="Addendum"/> </mainBody> |
We use <embeddedStructure> because the Annex of resolution A/RES/69/315 is referenced and imported into the content of this resolution (70/1). The inclusion happens mid content (i.e. in the middle of a paragraph), and <embeddedStructure> allows embedding document structures anywhere inside content paragraphs. The additional implication is that the styling and header and footer of the main holding resolution (70/1) applies on even the document referenced by <embeddedStructure>. | |
text 42 | |
modelling | <component eId="addendum"> |
note | This is a block of text with a heading found at the end of the document. It is like an end-note, but is placed in the content of the body. So this has been modelled as a generic document which may be included in the body via <componentRef> |
Closing formula: <conclusions>
The closing formula <conclusions> </conclusions> is meant to include all concluding material (e.g. closing formula(s), date(s) and signature(s). It is placed at the end of the main document, typically before the Annexes, if any. The closing formula may contain the following information:
place where the meeting took place
date of the meeting
date of adoption
session of the meeting
adopting body
type of adoption
Modelling <conclusions>
For information about element specific usage, see section 1.6 <conclusions>.
Examples
text43 | |
modelling | <conclusions> <container name=""> </vote> </container> |
note | The votes for and against a resolution are identified using the <quantity> element, and the nature of the vote whether it was for or against is described in a <TLCConcept> and referred to from the appropriate <quantity> element using the @refersTo attribute. |
text | |
modelling | <conclusions> <container name=""> </container> |
text | (Resolution adopted by the General Assembly on 9 December 2011) |
modelling | <conclusions> <container name=""> </container> |
note | The <location> tag is optional. It allows additional qualification of the event, by specifying where the event took place e.g. if it took place in the plenary hall or a committee room. |
Annexes/Attachments: <attachments>
The annexes block <attachments> </attachments> is meant to include all annexes/attachments to a resolution are generally autonomous documents that the resolution adopts or endorses, e.g. treaties, conventions, tables etc. They all retain their independent structure and formats.
NOTE: Annexes typically appear after the main text of the resolution and are headed with the word Annex (or Attachment) and usually, a title. If there are two or more annexes, they may be identified by Roman numerals.
Modelling <attachments>
For information about element specific usage, see section 1.7 <attachments>.
Examples
This section presents the most important Akoma Ntoso elements and attributes necessary to model the annexes in detail. All elements will have to be contained within the <attachments> element. Annexes imply making a copy of the document being attached. This would suggest a duplication of the content of the document which is the attachment / annex, however this is the nature of attachments, they are snapshots of a document as they were at a point in time. The attachment metadata will allow referencing the original source document that the attachment is from.
| |
modelling | <attachments> |
notes | <act name="codeOfConduct"> (…) </act> follows the mark-up of the relevant document type. The FRBRWork of this annex is that of the document containing the annex, with just the part name, i.e. the specification of the component differing at the end of the URI /akn/un/debateReport/debate/date/number/!main/annex_2. To maintain a link with the original source document of the attachment, you will need to add a reference to the original document using the <original> tag in the <references> block of the attachment document. For naming and identifying attachments, see the AKN4UN Naming Convention Section for more information. |
Subclass: Decisions
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 | Deliberative documents | |||
subclass | Decision Description: formal action regarding administrative and procedural matters of principal or subsidiary organ or other empowered bodies. They are sometimes also used to record the adoption of a text representing the consensus of the members of a given organ. | |||
AKN4UN | AKN | AKN4UN | UN Document | AKN4UN |
documentType | subtype | sub-class | @name subclass mandatory | |
value is prescribed | value is suggested | |||
<statement> | deliberation | decision | decisionDraft | |
decision | ||||
function | Formal action regarding administrative and procedural matters of principal or subsidiary organ or other empowered bodies. They are sometimes also used to record the adoption of a text representing the consensus of the members of a given organ. Function formal expressions of the opinion or will of a principal or subsidiary organ or other empowered bodies. Structure open structure documents, sometimes articulated in hierarchical structures in which the text is subdivided into higher and lower subdivisions, generally including a preamble and operative paragraphs. | |||
authors | UN principal and subsidiary organs, funds, programs, specialized agencies and other entity deliberative bodies. | |||
editors | Secretariats of the assemblies, councils, conferences, boards, or other entities. |
Caveat. What follows is the modelling and description of the "Decision Document Class" (logical decision) in which a "decision" may appear during its lifecycle.
The Decision Document Class is not specific to the decision of any organization in particular. It does list all the possible characteristics that a decision 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 decision may be published is presented in the "Publication Document Class".
The Decision Document 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 decisions.
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
Description
The structure of a decision may have the following elements:
Identification part title, identifier, etc. | Always present |
Preamble One or more paragraphs stating purpose, aims, and justification of a decision. | Not always present |
Decision body One or more paragraphs detailing the decision. | Always present |
Closing formula e.g. dates, signatures, formulas, etc. | Not always present. |
Modelling
document type | <akomaNtoso> <statement contains="originalVersion" name="{AKN4UN:subclass}"> |
metadata | <meta> <identification source="#{manifestationAuthor45}"> </identification> </meta> |
identification part | <preface> (...) </preface> |
preamble | <preamble> (...) </preamble> |
operative block | <mainBody> (...) </mainBody> |
closing block | <conclusions> (...) </conclusions> |
</statement> </akomaNtoso> |
Examples
Decision without preambular clauses:
document type | <akomaNtoso> <statement contains="originalVersion" name="decision"> | |
identification part | <preface> ……… </preface> | |
preamble | <preamble> ……… </preamble> | |
decision body | <mainBody> ……… </mainBody> | |
closing block | <conclusions> ….. </conclusions> | |
</statement> </akomaNtoso> |
Decision with preambular clauses46:
document type | <akomaNtoso> <statement contains="originalVersion" name="decision"> | ||
identification part | <preface> ……… </preface> | ||
preamble | <preamble> ……… </preamble> | ||
decision body | <mainBody> ……… </mainBody> | ||
closing block | <conclusions> ….. </conclusions> | ||
</statement> </akomaNtoso> |
Identification part: <preface>
The identification part <preface> </preface> is meant to include any matter found from the very beginning of a document up to where the <preamble> begins. It may contain information related to the title, adoption body, date of approval, and the like. All decisions start with some or all the info below, not necessarily in the same order:
identifier
title
Modelling <preface>
For information about element specific usage, see 1.2 <preface>.
Examples
source47 | |
modelling | <preface> |
source48 | |
modelling | <preface> |
source49 | |
modelling | <preface> REPORT BY THE WIPO INDEPENDENT ADVISORY OVERSIGHT COMMITTEE (IAOC) </docTitle> document <docNumber refersTo="#symbol" >WO/PBC/25/2 </docNumber> |
notes | This decision appears within a publication of decisions, and links to the original Agenda Item |
source50 | |
modelling | <preface> <p> <docNumber> 28/101. </docNumber> <docTitle> Outcome of the universal periodic review: Italy </docTitle> </p> </preface> |
source51 | |
modelling | <preface> </docTitle> Prepared by the <docProponent refersTo="#bureau"> </docProponent> |
source52 | |
modelling | <preface> |
notes | Security Council decisions may be published, grouped under the same heading with no individual specific identification. These decisions also do not have a published "identifier" and they may be referred using the agenda item title, in this case "The situation in the Middle East" and the meeting number, in this case 7025 meeting as e.g.: "The situation in the Middle East: Decision, 7025th meeting " |
<preamble>
The justificatory text <preamble> </preamble> is meant to include any matter found after the <preface> up to where the <mainBody> begins. It may contain one or more paragraphs stating purpose, aims, and justification of a decision.
Some decisions are structured like "resolutions" with a preamble with unnumbered paragraphs.
Modelling <preamble>
For information about element specific usage, see section 1.4 <preamble>.
Examples
source53 | |
modelling | <preamble> <formula name="enactingauthority"> <container name=""> </container> </preamble> |
source54 | (omissis) |
<preamble> <container name=""> <blockContainer eId="blockContainer_10" refersTo="#summary"> </p> (omissis) </blockContainer> <formula name="enactingAuthority" refersTo="#meetingParties"> <blockContainer eId="blockContainer_1"> </container> </preamble> | |
notes | The summary has been modelled as part of the preamble. |
modelling | <preamble> <container name=""> <blockContainer> <container> </preamble> (omissis) <components> </components> |
notes | We may also model the summary to be a separate document which is referenced and embedded within the preamble using the <componentRef> tag which allow us to clearly separate the "Summary" part from the decision and remove the it when it may not be necessary e.g. after approval. We use the <blockContainer> element that may contain <componentRef> or <documentRef> to refer to the summary component. |
source55 | |
modelling | <preamble> Recalling decision 1/CP.17 on the establishment of the Ad Hoc Working Group on the Durban Platform for Enhanced Action, </block> (ommissis) |
note | |
Main Content: <mainBody>
The main content <mainBody> </mainBody> is meant to include any matter found after the <preamble> up to where the <conclusion> or <attachments> or the end of the document. It contains one or more paragraphs detailing the decision of the organ or the action to be taken.
Decisions may be presented in the form of:
un/numbered paragraphs
that may also have ordered lists and sub-lists
the text may be subdivided by headings and sub-headings
some decisions are structured like resolutions with "preambular" and "operative" paragraphs
<mainBody>
The <mainBody> element may contain all types of AKN groups of elements. In the context of Document Class Deliberative Documents, only hierarchical and block containers elements are allowed. See the table below:
AKN4UN | AKN | body element | Supported elements |
Deliberative Documents | <statement> | <mainBody> | Element group: hierElements 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, transitional |
Element group: blockElements block, blockContainer, blockList, foreign, ol, p, table, tblock, toc, ul |
For the content model used by hierarchical and block containers, please see AKN4UN Guidelines relevant sections.
Examples
source56 | |
modelling | <paragraph eId="para_1"> At its 81st plenary meeting, on 5March 2015, the General Assembly, on the proposal of its President,29 recalling its resolutions 66/199 of 22December 2011, 67/209 of 21December 2012, 68/211 of 20December 2013 and 69/219 of 19December 2014, decided that the conference on disaster risk reduction, to be held in Sendai, Japan, from 14 to 18March 2015, should henceforth be known as the Third United Nations World Conference on Disaster Risk Reduction. </p> |
notes | |
source57 | |
modelling | <paragraph eId="para_1"> <list eId="para_2__list_1"> <p> The PBC also, taking note of the discussions during the 25th session of the PBC </intro> |
notes | |
source58 | |
modelling | <paragraph refersTo="#operative" eId="para_1"> |
notes | We use @refersTo to associate specific paragraphs to the operative part. |
source59 | |
modelling | <section eId="sec_B"> <paragraph eId="sec_B__para_2"> |
notes | |
source60 | |
modelling | <paragraph eId="para_140"> |
notes | We use the <table> tag here as the content is clearly in tabular form and layout. There are additional qualifiers for person, role and organization which refer to their respective TLC tags. |
source61 | |
modelling | <paragraph eId="para_121"> Item 148<br /> <listIntroduction>Closed peacekeeping missions </listIntroduction> Related report of the Advisory Committee on </p> In the metadata: <TLCReference eId="referenceToReport" name="reportRef" href="/akn/un/{documentIRIparts}" showAs=""/> |
notes | We use <embeddedStructure> here because the text in question is from a different document62, different from the main document. To explicitly depict this in the mark-up, we use the <embeddedStructure> tag and import the fragment of text from the referenced document being quoted. The text is imported with its own structure, so to distinguish that from the main document we need to place it in <embeddedStructure>. |
source63 | |
modelling | <paragraph eId="para_91"> <embeddedStructure inlineQuote=""" endQuote="""> |
notes | We use <embeddedStructure> here as the text is quoted, and is a kind of sub-structure within the main text of the document. The @innerQuote parameter of the <embeddedStructure> element puts a starting quotation mark for every item in the structure – it corresponds to the quotation mark highlighted in yellow in the image below. The inner text has an additional ending quotation marks for the sentence, and that is expressed in the mark-up using the <embeddedStructureag that takes the @endQuote parameter. |
Use cases
Decisions body may include:
Text of letter sent or received by the body taking the decision.
Whole text of "agenda" or "programme of work" that it may have approved.
Amending instructions.
References to agenda items.
Reference to documents.
source64 (includes letter) | ||||||
modelling | Option 1 – we may use <embeddedStructure> and place the paragraphs of the letter directly inside using <p> tags: <paragraph eId="para_101"> <embeddedStructure> Option 2 – you may treat the letter as logical component, and place it in <components> and use <componentRef> to refer to the letter logical component: <paragraph eId="para_101"> On 11 October 2013, the President of the Security Council addressed the following letter to the Secretary-General: <embeddedStructure> …. <components> </component> | |||||
notes | ||||||
source65 (include agenda) | ||||||
modelling | Option 1 – we may use <embeddedStructure> and refer to the agenda document via its IRI, using <documentRef> to an external XML physical file: <paragraph> <embeddedStructure> Option 2 – we may use <embeddedStructure> and embed the agenda document as a logical component of the document in <components> and refer to it using <documentRef> <paragraph> <embeddedStructure> <documentRef showAs="" src="#comp_1"/> </embeddedStructure> <components> <doc name="agenda"> <meta></meta> <preface> <p> PROVISIONAL AGENDA AND DOCUMENTATION FOR THE FIFTY-THIRD SECTION OF THE COMMISSION FOR SOCIAL DEVELOPMENT </p> </preface> <mainBody> <point eId="point_1"> <num>1.</num> <content> <p>Election of officers. </p> </content> </point> <point eId="point_2"> <num>2.</num> <content> <p>Adoption of the agenda and other organizational matters.</p> </content> </point> </component> | |||||
source66 (amend) | ||||||
modelling | <paragraph eId="para_1"> <content> <p> <mod> At its <ref href="/akn/un/{documentIRIparts}">46th plenary meeting</ref>, on 16 July 2014, the Economic and Social Council decided to approve the amendment to the rules of procedure of the United Nations Group of Experts on Geographical Names proposed by the Group of Experts, whereby section XII, rule 37, is replaced with the following text: "<quotedStructure> <chapter eId="chp_XII"> <num>XII.</num> <heading>Public meetings</heading> <rule eId="rule_37"> <num>Rule 37</num> <content> <p> The meetings of the Group of Experts and meetings of its working groups shall be in public, unless it decides otherwise. </p> </content> </rule> </chapter> </quotedStructure>" </mod> </p> </content> </paragraph> | |||||
note | We use <quotedStructure> here instead of <embeddedStructure> even if they are similar in structure because quoted Structure is explicitly meant to be used for quoting text and structures with respect to modificaitons. | |||||
source67 | ||||||
modelling | <blockList> <listIntroduction> <p> At its 51st plenary meeting, on 17 November 2014, the Economic and Social </p> </listIntroduction>
| |||||
Structure with headings
source68 | ||
modelling | <section eId="sec_A"> At its 12th plenary meeting, on 23 April 2014, the Economic and Social Council took the following action with regard to vacancies in the subsidiary and related bodies: </p> The Council elected the following six Member States to the Commission on Population and Development for a four-year term beginning at the first meeting of the forty-ninth session of the Commission, in 2015, and expiring at the close of its fifty-second session, in 2019: BELARUS, BOLIVIA (PLURINATIONAL STATE OF), BURUNDI, IRAN (ISLAMIC REPUBLIC OF), PHILIPPINES and SIERRA LEONE. </p> </content> The Council postponed the election of one member from Latin American and Caribbean States and one member from Western European and other States for a four-year term beginning at the first meeting of the forty-ninth session of the Commission and expiring at the close of its fifty-second session. </p> </content> | |
note | ||
29 http://www.fao.org/docrep/meeting/017/MO153E/MO153E01.htm#Resolution4
30 http://www.imo.org/en/OurWork/Environment/ShipRecycling/Documents/980.pdf
32 http://www.fao.org/docrep/meeting/017/MO153E/MO153E01.htm#Resolution5
33 http://www.basel.int/Portals/4/Basel%20Convention/docs/ships/IMO-Resolution-A.981(24).English.pdf
34 http://www.un.org/en/ga/search/view_doc.asp?symbol=A/RES/68/247
See page 13/35, http://undocs.org/A/RES/70/1
42 Page 35 makes reference to a heading on Page 13 http://undocs.org/A/RES/70/1
45 The author of the XML mark-up, the person/organization who take the responsibility for information provided.
46 http://ap.ohchr.org/documents/dpage_e.aspx?si=A/HRC/DEC/28/101 , http://daccess-ods.un.org/access.nsf/Get?Open&DS=A/HRC/DEC/28/101&Lang=E
51 https://www.unece.org/fileadmin/DAM/env/pp/wgp/WGP-21/Documents/AEC/ece.mp.pp.wg.1.2017.L.2_aec.pdf