7 Document Class: Meeting Reports

Document Class: Meeting Reports

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	Meeting Reports
subclass	Meeting Minute Description: third-person accounts of meetings. Meeting Report \| Conference Report \| Council Report Description: summaries of discussions held during meetings. They may also contain full text of resolutions or decisions, either proposed or adopted; recommended actions to be taken by other organs, etc., in the body of the document or as annexes.
AKN4UN document class	AKN	AKN4UN	UN Document	AKN4UN
	documentType mandatory	subtype mandatory	sub-class	@name subclass mandatory
		value is prescribed		value is suggested
meeting reports	<debateReport>	minutes	meeting minute	meetingMinute
		report	meeting report	meetingReport
				conferenceReport
				councilReport
function	A third-person summary account of meetings. Summary records recap the substantive points made during meetings. Function documents containing summarized accounts of meetings. Structure structures vary widely across organizations and traditions.
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 "Meeting Reports Document Class" (logical meeting report) that is not specific to the meeting report of any organization in particular. It does list all the possible characteristics that meeting reports 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 meeting report may be published is presented in the "Publication Document Class".

The Meeting Reports 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 meeting reports.

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 minutes may have the following elements:

Identification part Title, identification, date, etc.	Always present.
Main content The main part reflects the sequence of agenda items to be considered and alternation of questions and answers.	Always present.
Closing formula e.g. dates, time, etc.	Not always present.
Annexes e.g. list of participants, etc.	Not always present.

Modelling

document type

metadata

<meta>

</meta>

identification part

(...)

</preface>

main content

closing formula

(...)

(…)

. <debateSection>

</ mainBody>

attachments

(...)

</attachments>

</debateReport>

</akomaNtoso>