Personal tools

Skip to content. | Skip to navigation

 
You are here: Home → Release Notes → AKOMA NTOSO 1.0 Schema → Element Synopsis
 
We are in the process of updating this content to reflect changes to the latest release of AKOMA NTOSO!!!
Document Actions
Next: 8. Attribute Synopsis Previous: 6. Document URIs  

7. Element Synopsis


AKOMA NTOSO 1.0 Schema

1 Schema for AKOMA NTOSO 1.0

introduces and explains the schema for AKOMA NTOSO
2 Namespaces

AKOMA NTOSO 1.0 documents are completely qualified
3 Schema overview

All AKOMA NTOSO documents share ...
4 Patterns

abstraction and distillation of past experiences ...
5 Elements

supports the idea of using semantically rich terms
6 Document URIs

all resources are identified by a unique name
7 Element Synopsis

Elements of AKOMA NTOSO
8 Attribute Synopsis

Synopsis table
9 Stylesheets

example stylesheet for generating XHTML files
10 Release History

differences between releases
Elements of AKOMA NTOSO

Root element

Akomantoso
Content Model: DocumentTypes (a list of either act, bill, doc, report, or debaterecord)
Description: This is the root element, which contains all other elements. It is always present and required.
Use in: all document types
Example:  
 

Document Types

act
Content Model: HierarchicalStructure
Description: This is the element to use within AKOMA NTOSO for describing an act
Use in: acts only
Example:  

 

bill
Content Model: HierarchicalStructure
Description: This is the element to use within AKOMA NTOSO for describing a bill
Use in: bills only
Example:  

 

doc
Content Model: OpenStructure
Description: This is the element to use within AKOMA NTOSO for describing all kinds of documents for which there is no specific document type.
Use in: all document types except acts, bills, reports, and debaterecord.
Example:  

 

report
Content Model: OpenStructure
Description: This is the element to use within AKOMA NTOSO for describing a parliamentary report
Use in: reports only
Example:  

 

debaterecord
Content Model: DebateStructure
Description: This is the element to use within AKOMA NTOSO for describing the debate records of a parliamentary session (also known as Hansards)
Use in: debate records only
Example:  

 

judgement
Content Model: JudgementStructure
Description: This is the element to use within AKOMA NTOSO for describing the debate records of a parliamentary session (also known as Hansards)
Use in: judgement
Please note that the specific elements of this document type have not been defined yet.
Example:  

 

Common container elements

preface
Content Model: blocks (such as paragraphs and lists, plus TOCs)
Description: The preface contains all information that happen before the preamble, and constitute the heading of the document presented to the public. This may include the title, the number, the date, the emanating body, and every other piece of information that precedes the preamble. The content is organized in blocks within which semantically loaded terms can be specified (in particular, ActType, ActTitle, ActNumber, ActProponent, ActDate and ActPurpose).
Use in: all document types
Example:

<preface>
    <p>REPUBLIC OF SOUTH AFRICA</p>
    <p>
        <ActTitle>TRADITIONAL LEADERSHIP AND GOVERNANCE FRAMEWORK BILL</ActTitle>
    </p>
    <p>(As introduced in the National Assembly as a section 76 Bill; explanatory summary of
        Bill published in Government Gazette No. 25437 of 4 September 2003)</p>
    <p>(The English text is the off?cial text of the Bill)</p>
    <p>(<ActProponent>MINISTER FOR PROVINCIAL AND LOCAL GOVERNMENT</ActProponent>)</p>
    <p>
        <ActType>BILL</ActType>
    </p>
    <p>To <ActPurpose>provide for the recognition of traditional communities; to provide for
            the establishment and recognition of traditional councils; to provide for the
            functions and roles of traditional leaders; to provide a statutory framework for
            leadership positions within the institution of traditional leadership, the
            recognition of traditional leaders and the removal from office of traditional
            leaders; to provide for houses of traditional leaders; to provide for dispute
            resolution and the establishment of the Commission on Traditional Leadership
            Disputes and Claims; and to provide for matters connected
        therewith.</ActPurpose>
    </p>
</preface>

 

preamble
Content Model: blocks (such as paragraphs and lists, plus TOCs)
Description: The preamble element contains everything between the preface and the enacting terms of the act (included), such as the citations, the recitals and the solemn forms which precede and follow them.
Use in: all document types that have preambles
Example:  

 

conclusions
Content Model: blocks (such as paragraphs and lists, plus TOCs)
Description: The conclusions element contains all parts of the document that conclude it, such as final forms, signatures, dates, and all other information follow the actual content of the document
Use in: all document types
Example:  

 

attachments
Content Model: a list of attachment elements
Description: The attachments element introduces a number of attachments associated to the document. It is a simple container, and all relevant information is contained in as many attachment elements as there are attachments.
Use in: all document types
Example:

<attachments>
    <attachment xhref=”urn:AKOMA NTOSO:sa:act:117:1998:att1”/>
    <attachment xhref=”urn:AKOMA NTOSO:sa:act:117:1998:att2”/>
    <attachment xhref=”urn:AKOMA NTOSO:sa:act:117:1998:att3”/>
</attachments>

 

body
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc.
Description: The body element is the containing element for clauses in acts and bills and all other documents that rely on a hierarchical structure.
Use in: acts and bills
Example:

<body>
  <chapter id="chap1">
    <num>CHAPTER 1</num>
    <heading>INTERPRETATION AND APPLICATION</heading>
    <section id="sec1">
      <num>1.</num>
      <heading>Definitions and application</heading>
      <clause id="sec1-cla1">
        <num>(1)</num>
        <content>
          <p>...</p>
        </content>
      </clause>
      <clause id="sec1-cla2">
        <num>(2)</num>
        <content>
          <p>...</p>
        </content>
      </clause>
    </section>
  </chapter>

   …
</body>

 

debate
Content Model: a list of subdivision elements
Description: The debate element contains all speeches, questions and discussion items that are present in reports and debaterecord.
Use in: debate document types
Example:

<debate>
    <subdivision id="prayers">
        <heading>PRAYERS</heading>
    </subdivision>
    <subdivision id="papers">
        <heading>PAPERS LAID</heading>
        <other id="other1">
            <p> The following Papers were laid on the Table:-</p>
            <ul>
                <li><ref xhref=”...”>Annual Report and Accounts of Jomo Kenyatta University College of
                Agriculture and Technology for the year ended 30th June, 1990</a> and the
                <ref xhref=”...”>Certificate thereon by the Auditor-General (Corporations</ref>)</li>
            </ul>
        </other>
    </subdivision>
    <Questions id="qa">
        <heading>ORAL ANSWERS TO QUESTIONS</heading>
        <subdivision id="que803a">
            <heading>BANDITRY MENACE IN GALOLE</heading>
            <question by="Kofa" to="MS">
                <p>Mr. Kofa asked the Minister of State, Office of the President</p>
                <ul>
                  <li>whether he is aware that Councillor Abdi Sole of Asako Location was
                  seriously injured and two homeguards were shot dead and their guns
                  stolen while pursuing bandits on 20th May, 1995;</li>
                </ul>
            </question>
            <speech by="Smith" as="S">
                <p> Anybody from the Office of the President?</p>
            </speech>
            <answer by="Manga" as="AMS">
                <p> Mr. Speaker, Sir, the answer is being prepared. The Minister is coming
                    to give the answer.</p>
            </answer>
        </subdivision>
   </Questions>

 

maincontent
Content Model: blocks (such as paragraphs and lists, plus TOCs)
Description: The maincontent element contains all parts of the document that are between the preamble and the conclusions of the document. Note that maincontent is to be used with the doc and report element, and as such only for the MISC class of documents.
Use in: Document doc only
Example:  
 

Elements for hierarchical documents

Elements for hierarchical documents

section
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc., preceded by, if needed, number and heading.
Description: a hierarchical element called section. Use it whenever appropriate within a body element.
Use in: all hierarchical document types
Example:

see element body

 

part
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc., preceded by, if needed, number and heading.
Description: a hierarchical element called part. Use it whenever appropriate within a body element. 
Use in: all hierarchical document types
Example:

see element body

 

paragraph
Content Model: hierarchy of containment elements such as section, part, paragraph, chapter, article, etc., preceded by, if needed, number and title.
Description: a hierarchical element called paragraph. Use it whenever appropriate within a body element.
Use in: all hierarchical document types
Example: see element body

 

chapter
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc., preceded by, if needed, number and heading.
Description: a hierarchical element called section. Use it whenever appropriate within a body element. 
Use in: all hierarchical document types
Example: see element body

 

title
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc. , preceded by, if needed, number and heading.
Description: a hierarchical element called section. Use it whenever appropriate within a body element.
Use in: all hierarchical document types
Example: see element body

 

book
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc. , preceded by, if needed, number and heading.
Description: a hierarchical element called section. Use it whenever appropriate within a body element.
Use in: all hierarchical document types
Example: see element body

 

tome
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc. , preceded by, if needed, number and heading.
Description: a hierarchical element called section. Use it whenever appropriate within a body element.
Use in: all hierarchical document types
Example: see element body

 

article
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc. , preceded by, if needed, number and heading.
Description: a hierarchical element called section. Use it whenever appropriate within a body element.
Use in: all hierarchical document types
Example: see element body

 

clause
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc. , preceded by, if needed, number and heading.
Description: a hierarchical element called section. Use it whenever appropriate within a body element.
Use in: all hierarchical document types
Example: see element body

 

subsection
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc. , preceded by, if needed, number and heading.
Description: a hierarchical element called section. Use it whenever appropriate within a body element.
Use in: all hierarchical document types
Example: see element body

 

subpart
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc. , preceded by, if needed, number and heading.
Description: a hierarchical element called section. Use it whenever appropriate within a body element.
Use in: all hierarchical document types
Example: see element body

 

subparagraph
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc. , preceded by, if needed, number and heading.
Description: a hierarchical element called section. Use it whenever appropriate within a body element. 
Use in: all hierarchical document types
Example: see element body

 

subchapter
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc. , preceded by, if needed, number and heading.
Description: a hierarchical element called section. Use it whenever appropriate within a body element. 
Use in: all hierarchical document types
Example: see element body

 

subtitle
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc. , preceded by, if needed, number and heading.
Description: a hierarchical element called section. Use it whenever appropriate within a body element. 
Use in: all hierarchical document types
Example: see element body

 

subclause
Content Model: a hierarchy of containment elements such as section, part, paragraph, chapter, article, etc. , preceded by, if needed, number and heading.
Description: a hierarchical element called section. Use it whenever appropriate within a body element. 
Use in: all hierarchical document types
Example: see element body

 

content
Content Model: A list of blocks
Description: The content contains the actual text of the acts and bills, organized in blocks. 
Use in: all hierarchical document types
Example: see element body

 

heading
Content Model: text and inline elements such as b, i, span 
Description:  
Use in: all hierarchical document types
Example: see element body

 

subheading
Content Model: text and inline elements such as b, i, span 
Description: Added to deal with hierarchical elements that have both a heading and a subheading.
Use in: all hierarchical document types

 

sidenote
Content Model: text and inline elements such as b, i, span 
Description: Hierarchical elements that have a sidenote near the heading.
Use in: all hierarchical document types

 

from
Content Model: text and inline elements such as b, i, span 
Description: In all debate elements (speech, question, answer) specifies the person making the speech.
Use in: all debate document types

 

Elements for debate documents

AdministrationOfOath
Content Model: An alternative hierarchy of subdivisions, or a list of speech or question elements
Description: The subdivision is a hierarchical organization of elements composing a debate. They can be either speeches, or questions to the assembly or to the government. They can be further organized hierarchically (for instance, to agree with the sections of an agenda).
Use in: debate document types
Example: see element debate

 

Communication
Content Model: An alternative hierarchy of subdivisions, or a list of speech or question elements
Description: The subdivision is a hierarchical organization of elements composing a debate. They can be either speeches, or questions to the assembly or to the government. They can be further organized hierarchically (for instance, to agree with the sections of an agenda).
Use in: debate document types
Example: see element debate

 

Petitions
Content Model: An alternative hierarchy of subdivisions, or a list of speech or question elements
Description: The subdivision is a hierarchical organization of elements composing a debate. They can be either speeches, or questions to the assembly or to the government. They can be further organized hierarchically (for instance, to agree with the sections of an agenda).
Use in: debate document types
Example: see element debate

 

Papers
Content Model: An alternative hierarchy of subdivisions, or a list of speech or question elements
Description: The subdivision is a hierarchical organization of elements composing a debate. They can be either speeches, or questions to the assembly or to the government. They can be further organized hierarchically (for instance, to agree with the sections of an agenda).
Use in: debate document types
Example: see element debate

 

NoticesOfMotion
Content Model: An alternative hierarchy of subdivisions, or a list of speech or question elements
Description: The subdivision is a hierarchical organization of elements composing a debate. They can be either speeches, or questions to the assembly or to the government. They can be further organized hierarchically (for instance, to agree with the sections of an agenda).
Use in: debate document types
Example: see element debate

 

Questions
Content Model: An alternative hierarchy of subdivisions, or a list of speech or question elements
Description: The subdivision is a hierarchical organization of elements composing a debate. They can be either speeches, or questions to the assembly or to the government. They can be further organized hierarchically (for instance, to agree with the sections of an agenda).
Use in: debate document types
Example: see element debate

 

Address
Content Model: An alternative hierarchy of subdivisions, or a list of speech or question elements
Description: The subdivision is a hierarchical organization of elements composing a debate. They can be either speeches, or questions to the assembly or to the government. They can be further organized hierarchically (for instance, to agree with the sections of an agenda).
Use in: debate document types
Example: see element debate

 

ProceduralMotions
Content Model: An alternative hierarchy of subdivisions, or a list of speech or question elements
Description: The subdivision is a hierarchical organization of elements composing a debate. They can be either speeches, or questions to the assembly or to the government. They can be further organized hierarchically (for instance, to agree with the sections of an agenda).
Use in: debate document types
Example: see element debate

 

PointOfOrder
Content Model: An alternative hierarchy of subdivisions, or a list of speech or question elements
Description: The subdivision is a hierarchical organization of elements composing a debate. They can be either speeches, or questions to the assembly or to the government. They can be further organized hierarchically (for instance, to agree with the sections of an agenda).
Use in: debate document types
Example: see element debate

 

subdivision
Content Model: An alternative hierarchy of subdivisions, or a list of speech or question elements
Description: The subdivision is a hierarchical organization of elements composing a debate. They can be either speeches, or questions to the assembly or to the government. They can be further organized hierarchically (for instance, to agree with the sections of an agenda).
Use in: debate document types
Example: see element debate

 

speech
Content Model: blocks (such as paragraphs and lists, plus TOCs)
Description: A remark by a member of the assembly. The author of the remark is identified through the by attribute, which points to a listed person (see element persons).
Use in: debate document types
Example: see element debate

 

question
Content Model: blocks (such as paragraphs and lists, plus TOCs)
Description: A question posed to the assembly or the government by an individual. The author of the question is identified through the by attribute, which points to a listed person (see element persons). Analogously, the attribute as indicates the role according to which the utterance has been provided, and the attribute to indicates the addressee of the question.
Use in: debate document types
Example: see element debate

 

answer
Content Model: blocks (such as paragraphs and lists, plus TOCs)
Description: An answer offered to the assembly or the government by an individual. The author of the question is identified through the by attribute, which points to a listed person (see element persons). Analogously, the attribute as indicates the role according to which the utterance has been provided.
Use in: debate document types
Example: see element debate

 

other
Content Model: blocks (such as paragraphs and lists, plus TOCs)
Description: Any other information provided within a debate that is not an utterance by an individual.
Use in: debate document types
Example:  

 

comment
Content Model: text and inline elements such as b, i, span
Description: Any comment that has been recorded describing the events of a debate (such as noises, applauses, etc.)
Use in: debate document types
Example:  

 

list
Content Model: a list of items
Description: Any comment that has been recorded describing the events of a debate (such as noises, applauses, etc.)
Use in: All document types
Example:  

 

item
Content Model: optional num, title and subtitle, followed by blocks (such as paragraphs and lists, or TOCs)
Description: Any comment that has been recorded describing the events of a debate (such as noises, applauses, etc.)
Use in: All document types
Example:  
 

Akoma Ntoso Block elements

toc
Content Model: a list of tocitem elements
Description: A table of content (TOC), typically provided in the preamble or the preface of a document. It contains a list of TOC items.
Use in: all document types
Example:

<toc>
  <tocitem xhref=“#chap1">CHAPTER 1 INTERPRETATION AND APPLICATION</item>
  <tocitem xhref=“#art1">1. Definitions and application</item>
  <tocitem xhref=“#chap2">CHAPTER 2 TRADITIONAL COMMUNITIES AND TRADITIONAL COUNCILS</item>
  <tocitem xhref=“#art2">2. Recognition of traditional communities</item>
</toc>

 

tocitem
Content Model: text and inline elements such as b, i, span
Description: Each individual element of a table of content. The href attribute points to the id value of the corresponding part in the actual document content.
Use in: all document types
Example: see element toc
 

Akoma Ntoso inline elements

Preface-only elements

ActType
Content Model: text and inline elements such as b, i, span
Description: An inline element wrapping the type of the act. Use it typically in the preface.
Use in: all document types
Example: see element preface

 

ActTitle
Content Model: text and inline elements such as b, i, span
Description: An inline element wrapping the type of the act. Use it typically in the preface.
Use in: all document types
Example: see element preface

 

ActNumber
Content Model: text and inline elements such as b, i, span
Description: An inline element wrapping the type of the act. Use it typically in the preface.
Use in: all document types
Example: see element preface

 

ActProponent
Content Model: text and inline elements such as b, i, span
Description: An inline element wrapping the type of the act. Use it typically in the preface.
Use in: all document types
Example: see element preface

 

ActDate
Content Model: text and inline elements such as b, i, span 
Description: An inline element wrapping the title of the act. Use it typically in the preface.
Use in: all document types
Example: see element preface

 

ActPurpose
Content Model: text and inline elements such as b, i, span 
Description: An inline element wrapping the purpose of the act. Use it typically in the preface.
Use in: all document types
Example: see element preface

Reference-type inline elements

 

ref
Content Model text and inline elements such as b, i, span
Description: A legislative reference (i.e., to another AKOMA NTOSO-maintained document). Use ref for legislative references, and use a for references to World Wide Web documents.
Use in: all document types
Example: <li><def>district municipality</def> means a district municipality as defined in <ref xhref="urn:AKOMA NTOSO:sa:act:117:1998">section 1 of the Local Government: Municipal Structures Act, 1998 (Act No. 117 of 1998);</ref></li>

 

mref
Content Model text and inline elements such as b, i, span
Description: Multiple legislative references
Use in: all document types
Example: TBD

 

rref
Content Model text and inline elements such as b, i, span
Description: A range of consecutive legislative references.
Use in: all document types
Example: TBD

 

mod
Content Model text, inline elements such as b, i, span, plus two special elements for quotations: quotedText and quotedStructure. 
Description: The mod element contains the part of an act that provides explicit instruction for an amendment to another act.
Use in: all document types
Example:  

 

mmod
Content Model text and inline elements such as b, i, span, plus two special elements for quotations: quotedText and quotedStructure
Description: Multiple modifications
Use in: all document types
Example: TBD

 

rmod
Content Model text and inline elements such as b, i, span, plus two special elements for quotations: quotedText and quotedStructure
Description: A range of consecutive legislative modifications.
Use in: all document types
Example: TBD

 

quotedText
Content Model text and inline elements such as b, i, span
Description: a fragment of text being either the substituted text or the substitution text of an amendment. Only subparts of a whole structure (e.g., one or a few words) are placed in a quotedText element. Use quotedStructure for whole structures.
Use in: all document types
Example:  

 

quotedStructure
Content Model all types of structures: hierarchical elements such as whole parts, articles, clauses, etc. plus any kind of blocks or containers.
Description: a substructure of the act that is the part being substituted or the substitution itself of an amendment. Only whole structure (e.g., an article, a clause, a block) are placed in a quotedStructure element. Use quotedText for individual words.
Use in: all document types
Example:  

 

Other inline elements

def 
Content Model: Text and inline elements such as b, i, span
Description: the defined term in a definition. This is usually presented in bold, and it could be useful to differentiate for searches and cataloguing operations. 
Use in: all document types
Example:  see element ref

 

ins
Content Model: Text and inline elements such as b, i, span
Description: Inserted text
Use in: all document types
Example: TBD

 

del
Content Model: Text and inline elements such as b, i, span
Description: Deleted text
Use in: all document types
Example: TBD

 

omissis
Content Model: Text and inline elements such as b, i, span
Description: Omitted text
Use in: all document types
Example: TBD

 

noteref
Content Model: empty with an href attribute
Description: a reference to an endnote or a footnote. The content of the note is actually in the notes subsection of the meta section. The num attribute contains the note marker that is shown in the main text. The href attribute provides a pointer to it.
Use in: all document types
Example: see element notes

 

recordedTime
Content Model: empty with a time attribute
Description: the specification of the time in which a remark, discussion item or question was proposed. The time attribute contains the time itself in format hh:mm.
Use in: all document types
Example:

<p><recordedTime time="14:04"/> The Chief Whip of the Majority Party moved: That the House resolves that—</p>

 

eol
Content Model: empty with a breakat attribute
Description: The end of a line if recording end of lines is necessary according to local rules.
Use in: all document type
Example:  

 

 

eop
Content Model: empty with a breakat attribute
Description: The end of a page if recording end of page is necessary according to local rules. 
Use in: all document type
Example:  

Generic elements

container
Content Model: blocks (such as paragraphs and lists, plus TOCs) 
Description: A generic element to be used as a placeholder of any container element wherever containers are allowed.
Use in: all document types
Example: see discussion in sect 6 of this document

 

block
Content Model: text and inline elements such as b, i, span 
Description: A generic element to be used as a placeholder of any block element wherever blocks are allowed.
Use in: all document types
Example: see discussion in sect 6 of this document

 

inline
Content Model: text and inline elements such as b, i, span 
Description: A generic element to be used as a placeholder of any inline element wherever inlines are allowed.
Use in: all document types
Example: see discussion in sect 6 of this document

 

marker
Content Model: markerreq 
Description: A generic element to be used as a placeholder of any marker element wherever markers are allowed.
Use in: all document types
Example: see discussion in sect 6 of this document

 

foreign
Content Model: any content of a different namespace than Akoma Ntoso.
Description: A generic container for XML not belonging to Akoma Ntoso. Use it for instance for XML rendering of mathematical formulae with MathML, or graphic objects sith SVG, etc.
Use in: all document types
Example: TBD

HTML elements

div
Content Model: blocks (such as paragraphs and lists, plus TOCs)
Description: A generic element to be used as a placeholder of any container element wherever containers are allowed. Note: use as a container, not as a block (as HTML would recommend).
Use in: all document types
Example: see discussion in sect 7 of this document

 

p
Content Model: text and inline elements such as b, i, span
Description: as in HTML
Use in: all document types
Example:  

 

li
Content Model: text and inline elements such as b, i, span
Description: as in HTML
Use in: all document types
Example:  

 

span
Content Model: text and inline elements such as b, i, span
Description: as in HTML
Use in: all document types
Example:  

 

b
Content Model: text and inline elements such as b, i, span
Description: as in HTML
Use in: all document types
Example:  

 

i
Content Model: text and inline elements such as b, i, span
Description: as in HTML
Use in: all document types
Example:  

 

a
Content Model: text and inline elements such as b, i, span
Description: as in HTML
Use in: all document types
Example:  

 

img
Content Model: empty plus the src and alt attributes.
Description: as in HTML
Use in: all document types
Example:  

 

ul
Content Model: a list of li elements
Description: as in HTML
Use in: all document types
Example:  

 

ol
Content Model: a list of li elements
Description: as in HTML
Use in: all document types
Example:  

 

table
Content Model: a list of tr elements
Description: as in HTML
Use in: all document types
Example:  

 

tr
Content Model: a list of either th or td elements
Description: as in HTML
Use in: all document types
Example:  

 

th
Content Model: text and inline elements such as b, i, span
Description: as in HTML
Use in: all document types
Example:  

 

td
Content Model: text and inline elements such as b, i, span
Description: as in HTML
Use in: all document types
Example:  
 

Metadata elements

meta
Content Model: an identification element, a publication element, zero or more classification elements, zero or more lifecycle elements, zero or more references elements, zero or more notes sections, zero or more proprietary sections.
Description: The meta element contains the whole set of metadata defined for each AKOMA NTOSO document. All metadata are organized in subsections according to purpose and use.
Use in: all document types
Example:  

 

Identification elements

Identification
Content Model: Work, Expression, Manifestation, Item (optional)
Description: The identification container collects all metadata about the abstract document (Work), the concrete version (Expression), the conversion in XML (Manifestation) and optionally the actual file location (Item) of the document.
Use in: all document type
Example:

<identification source="#editor-office">
 <FRBRWork>
  <uri value="/ke/act/2003-12-10/8" />
  <date date="2003-12-10" name="Generation" />
  <author xhref=“#parliament” as="#author" />
  <components>
    <component name="main" id="wmain" xhref=“#emain”/>
    <component name="schedule1" id="wschedule1" xhref=“#eschedule1”>
      <component name="tableA" id="wtableA" xhref=“#etableA”/>
    </component>
  </components>
 </FRBRWork>
 <FRBRExpression>
  <uri value="/ke/act/2003-12-10/8/eng@" />
  <date date="2007-07-27" name="Generation" />
  <author xhref=“#editor-office” as="#jurist" />
  <components>
    <component name="main" id="emain" xhref=“#mmain”/>
    <component name="schedule1" id="eschedule1" xhref=“#mschedule1”>
      <component name="tableA" id="etableA" xhref=“#mtableA”/>
    </component>
  </components>
 </FRBRExpression>
 <FRBRManifestation>
  <uri value="/ke/act/2003-12-10/8/eng.akn" />
  <date date="2007-07-27" name="Generation" />
  <author xhref=“#editor-office” as="#editor" />
  <author xhref=“#fv” as="#editor" />
  <components>
    <component name="main" id="mmain" xhref=“main.xml”/>
    <component name="schedule1" id="mschedule1" xhref=“schedule1.xml”/>
    <component name="tableA" id="mtableA" xhref=“tableA.xml”/>
    <component name="fig1" id="mfig1" xhref=“fig1.tiff” howAs="fig. 1"/>
  </components>
 </FRBRManifestation>
</identification>

 

FRBRWork
Content Model: a collection of uri, alias, date, author, components, preservation elements.
Description: Details about the abstract document that remain unaffected after any variation (such as new versions or new rendering). At least one URI must be specified, but many more can be added. Zero or more aliases are meant for known names of the document, the date contains the date of creation of the work (e.g., the initial promulgation), the author is the individual or the composite that generated the work (e.g., the Parliament), the components element lists the hierarchy of document components contained in the document and in preservation all elements connected to the preservation of the Work are stored (e.g., bibliographic metadata and digital signatures).
Use in: all document types
Example: see element identification

 

FRBRExpression
Content Model: a collection of uri, alias, date, author, components preservation elements.
Description: Details about the document that changes after any variation (such as new versions). At least one URI must be specified, but many more can be added. Zero or more aliases are meant for known names of the document, the date contains the date of creation of the expression (e.g., the entering in force of the variant), the author is the individual or the composite that generated the expression (e.g., the editorial staff that actually consolidated the content), the components element lists the hierarchy of document components contained in the document and in preservation all elements connected to the preservation of the expression are stored (e.g., bibliographic metadata and digital signatures).
Use in: all document types
Example: see element identification

 

FRBRManifestation
Content Model: a collection of uri, alias, date, author, components preservation elements.
Description: Details about the document that is generated concretely in electronic forma in a specific data format. At least one URI must be specified, but many more can be added. Zero or more aliases are meant for known names of the document, the date contains the date of creation of the manifestation (e.g., the generation of the XML file), the author is the individual or the composite that generated the manifestation (e.g., the editorial staff that actually created the XML file), the components element lists the document components contained in the package and in preservation all elements connected to the preservation of the manifestation are stored (e.g., bibliographic metadata and digital signatures).
Use in: all document types
Example: see element identification

 

FRBRItem
Content Model: a collection of uri, alias, date, author, components preservation elements. 
Description: Details about the specific instance of manifestation that is the current document. At least one URI must be specified, but many more can be added. Zero or more aliases are meant for known names of the document, the date contains the date of creation of the item (e.g., the moment in which the instance was put on the actual server), the author is the individual or the composite that generated the item (e.g., the owner of the server), the components element lists the document components contained in the actual physical package  and in preservation all elements connected to the preservation of the item are stored (e.g., bibliographic metadata and digital signatures).
Use in: all document types
Example: see element identification

 

uri
Content Model: empty with value attribute
Description: The uri of the corresponding instance of one of the 4 levels.
Use in: all document types
Example: see element identification

 

alias
Content Model: empty with value attribute
Description: The known name of the corresponding instance of  one of the 4 levels
Use in: all document types
Example: see element identification

 

date
Content Model: empty with name, date attributes
Description: The date associated to an instance of one of the four levels. The attribute name is used to specify which date. 
Use in: all document types
Example: see element identification

 

author
Content Model: empty with href and as attribute
Description: A reference to the element in references that is the organization or individual author of the instance of one of  the four levels.  The as attribute specifies the role in which the author contributed.
Use in: all document types
Example: see element identification

 

components
Content Model: a list of component elements
Description:  
Use in: all document types
Example: see element identification

 

component
Content Model: a list of component elements with href and showAs attributes
Description: The URI and the display name of each component of the instance at that level within the four levels. Within each component the hierarchically dependent components are listed.
Use in: all document types
Example: see element identification

 

preservation
Content Model: Any element of a different namespace than Akoma Ntoso
Description: An open set of information items relevant to the correct preservation in time of the instance.
Use in: all document types
Example: TBD

 

Publication elements

publication
Content Model: mpty with name, date and showAs attributes
Description: Details about the official publication where the act or document first appeared. It is assumed that there is one authoritative publication, and optionally a few more additional publication venues. The type of publication, number (if the publication has issues) and date are required attributes.
Use in: all document types
Example:  

 

Classification elements

classification
Content Model: (keyword+)
Description: A list of keyword elements. The dictionary attribute controls the source dictionary of keywords that is being used.
Use in: all document types
Example:  

 

keyword
Content Model: empty with value attribute.
Description: Each individual keyword according to the dictionary specified.
Use in: all document types
Example:  

 

Lifecycle elements

lifecycle
Content Model: one or more event elements
Description: The <lifecycle> element contains two main structure to determine the life cycle of the document: the list of events that the current document has undergone, and the list of references that have generated these events.
Use in: all document types
Example:

<lifecycle>
    <event id="evn1" source="org1" date="2005-08-29" type="Generation"/>
    <event id="evn2" source="pas1" date="2005-12-31" type="Repeal"/>
</lifecycle>

 

event
Content Model: empty with required source, date and type attributes.
Description: Each event that affects the history and lifecycle of the document. Each event is caused by one document, which is listed in the references list and is referred to by the source attribute. The date attribute specifies the date from which the event takes place, and the type attribute specifies the type of event.
Use in: all document types
Example: see element lifecycle

 

Analysis elements

analysis
Content Model: Currently, just amendments
Description: All analytical description of provisions contained within the document. At the moment, only amendment provisions are analyzed.
Use in: all document types
Example:  

 

ActiveModifications
Content Model: a list of repeatable Textual, Meaning, Scope, Force, Efficacy, LegalSystem elements.  
Description: A list of references to Amendment items identifying active modifications (i.e., the document contains references to other documents that need to be amended.
Use in: all document types
Example:  

 

ActiveModifications
Content Model: a list of repeatable Textual, Meaning, Scope, Force, Efficacy, LegalSystem elements.
Description: A list of references to Amendment items identifying active modifications (i.e., the document contains references to other documents that need to be amended. 
Use in: all document types 
Example:  

 

Textual
Content Model: TBD
Description: TBD
Use in: all document types
Example:  

 

Meaning
Content Model: TBD
Description: TBD
Use in: all document types
Example:  

 

Scope
Content Model: TBD
Description: TBD
Use in: all document types
Example:  

 

Force
Content Model: TBD
Description: TBD
Use in: all document types
Example:  

 

Efficacy
Content Model: TBD
Description: TBD
Use in: all document types
Example:  

 

LegalSystem
Content Model: TBD
Description: TBD
Use in: all document t