6 Akoma Ntoso document types (Non-Normative)
6.1 Document types
Akoma Ntoso manages seven main document types, grouped for function, organization, or role in the legal domain:
- Collection Structure
- Hierarchical Structure
- Debate Structure
- Amendment Structure
- Judgment Structure
- Open Structure
- Portion Structure
A particular attention is devoted to the table, attachments, components that could be included in any type of document.
6.2 Collection Structure
Composite documents are containers of other documents that have their own identity, lifecycle, workflow, and other metadata. An example is the Official Journal or Official Gazette volume where many bills, acts, minutes, reports are collected. Each document is autonomous with its FRBR identification package, metadata, modifications, and temporal information. Nevertheless, the volume of the Journal is an independent work that is composed of other works.
A collection structure is any folder (such as one that contains a bill) that is usually composed of several documents (cover, motivations, commission report, amendments, first draft of a bill, amended bill, etc.).
In this way, it is possible to represent a document composed of different autonomous parts (work or expressions). The following example shows a documentCollection, with the bill (proyecto de ley) and the explanatory part (motivos).
We have several documents that belongs to the collection structure. Certain types of documents, such as amendmentLists and officialGazettes, are usually made of several distinct and autonomous documents.
| Name | Definition | Structure |
|---|---|---|
| DOCUMENT COLLECTION | The type documentCollection is a generic document type for representing any kind of collection container. | Complex structure composed by different works or by different expressions (e.g. different versions of the same bill: one presented in the Chamber of Deputies and another presented in the Senate) A document collection can also be used, for example, to represent an EP committee's report on a bill, containing a Resolution (possibly with an amendments list annexed), a Explanatory Memorandum Opinions of other committees. |
| AMENDMENT LIST | An amendment list is a document listing a series of amendments. | Complex structure including amendments and parts of the text by which an amendment is introduced. |
| OFFICIAL GAZETTE | An Official Gazette or Official Bulletin | Official publishing source of law composed of an assortment of legal documents (laws, decrees, orders, legal notices, etc.). |
-
6.2.1 Composition of a collection structure The different documents included in the documentCollection can be represented in three different ways:
-
- The documents are embedded in the collectionBody of the documentCollection:
<?xml version="1.0" encoding="UTF-8"?> <akomaNtoso xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://docs.oasis-open.org/legaldocml/ns/akn/3.0 ../schemas/akomantoso30.xsd" xmlns="http://docs.oasis-open.org/legaldocml/ns/akn/3.0"> <documentCollection name="billPackage"> <meta> ... </meta> <coverPage> ... </coverPage> <collectionBody> <component eId="cmp_1"> <bill name="bill"> <meta>,,, </meta> <preface> <p><docTitle>THE KENYA INFORMATION AND COMMUNICATIONS BILL 2006</docTitle></p> <p><docNumber>No.8 of 2006</docNumber></p> <longTitle> <p>AN ACT of Parliament to promote and develop in an orderly manner the carriage and content of communications (including broadcasting, multimedia, telecommunications and postal), for the establishment of a commission to regulate all forms of communications, for the establishment of an appeals tribunal and for connected purposes. </p> </longTitle> </preface> <body> <section eId="sec_1"> <num>1.</num> <heading>Short title and commencement</heading> <content> <p>This Act may be cited as the <shortTitle>Kenya Information and Communications Act, 2006</shortTitle> and shall come into operation on such date as the Minister may, by notice in the Gazette, appoint and different dates may be appointed for different provisions.</p> </content> </section> </body> </bill> </component> <component eId="cmp_2"> <interstitial eId="cmp_2__interstitial"> <p>Any text is in the collection but belongs to no individual document</p> </interstitial> </component> <component eId="cmp_3"> <doc name="memorandum"> <meta> ...the metadata of the second document... </meta> <preface> ...the preface of the second document... </preface> <mainBody> ...the body of the second document... </mainBody> </doc> </component> </collectionBody> </documentCollection> </akomaNtoso> |
|---|
-
- The documents are modelled in the components part of the documentCollection:
<?xml version="1.0" encoding="UTF-8"?> <akomaNtoso xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://docs.oasis-open.org/legaldocml/ns/akn/3.0 ./akomantoso30.xsd" xmlns="http://docs.oasis-open.org/legaldocml/ns/akn/3.0"> <documentCollection name="billPackage"> <meta> .... </meta> <coverPage> </coverPage> <collectionBody> <component eId="cmp_1"> <documentRef eId="cmp_1__dref_1" href="#bill" showAs="BILL"/> </component> <component eId="cmp_2"> <interstitial eId="cmp_2__interstitial"> <p>Any text is in the collection but belongs to no indi-vidual document</p> </interstitial> </component> <component eId="cmp_3"> <documentRef eId="cmp_3__dref_1" href="#memorandum" showAs="MEMORANDUM"/> </component> </collectionBody> </documentCollection> <components> <component eId="cmpnts__cmp_1"> <bill name="bill"> <meta>,,, </meta> <preface> <longTitle eId="cmpnts__cmp_1__longTitle"> The title of the bill </longTitle> </preface> <body> ,,, </body> </bill> </component> <component eId="cmpnts__cmp_2"> <doc name="memorandum"> <meta> ...the metadata of the second document... </meta> <preface> ...the preface of the second document... </preface> <mainBody> ...the body of the second document... </mainBody> </doc> </component> </components> </akomaNtoso> |
|---|
-
- The documentCollection includes only the <documentRef> specification to external documents that are modelled and represented in separated XML files.
<?xml version="1.0" encoding="UTF-8"?> <akomaNtoso xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://docs.oasis-open.org/legaldocml/ns/akn/3.0 ./akomantoso30.xsd" xmlns="http://docs.oasis-open.org/legaldocml/ns/akn/3.0"> <documentCollection name="billPackage"> <meta> .... </meta> <coverPage> </coverPage> <collectionBody> <component eId="cmp_1"> <documentRef eId="cmp_1__dref_1" href=“/akn/uy/bill/2013-02-10/450!bill" showAs="BILL"/> </component> <component eId="cmp_2"> <interstitial eId="cmp_2__interstitial"> <p>Any text is in the collection but belongs to no individual document</p> </interstitial> </component> <component eId="cmp_3"> <documentRef eId="cmp_3__dref_1" href="/akn/doc/2013-02- 10/450!memorandum" showAs="MEMORANDUM"/> </component> </collectionBody> </documentCollection> </akomaNtoso> |
|---|
6.2.2 Recursive Components in DocumentCollection
It is also possible to have a component in the same position as the attachment, at the end of the main document. This permits recursive definition inside of the documentCollection.
The following case shows the usage of this construct.
<?xml version="1.0" encoding="UTF-8"?> <akomaNtoso xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://docs.oasis-open.org/legaldocml/ns/akn/3.0 ./akomantoso30.xsd " xmlns="http://docs.oasis-open.org/legaldocml/ns/akn/3.0" xmlns:uy="http://uruguay/propetary.xsd"> <documentCollection name="billPackage"> <meta> FRBR block information </meta> <preface> Preface of the documentCollection </preface> <preamble> Preamble of the documentCollection </preamble> <collectionBody> <component eId="cmp_1"> <documentRef eId="dref_1" href="#cmpnts_cmp_1" showAs="INFORME EN MAYORÍA Y PROYECTO DE LEY - FRENTE AMPLIO"/> </component> <component eId="cmp_2"> <documentRef eId="dref_2" href="#cmpnts__cmp_2" showAs="INFORME EN MINORÍA Y PROYECTO DE RESOLUCIÓN - PARTIDO NACIONAL"/> </component> </collectionBody> </documentCollection> <components> <component eId="cmpnts__cmp_1"> <documentCollection name="informeDeMayoria" contains="originalVersion"> <meta> .... </meta> <collectionBody> <component eId="cmpnts__cmp_1__cmp_1"> <documentRef eId="cmpnts_cmp1_dref_1" href="#cmpnts_cmp_1__cmpnts__cmp_1" showAs="Informe"/> </component> <component eId=" cmpnts__cmp_1__cmp_2"> <documentRef eId=" cmpnts_cmp1_dref_2" href="#cmpnts_cmp_1__cmpnts__cmp_2" showAs="Bill"/> </component> </collectionBody> <components> <component eId="cmpnts__cmp_1__cmpnts__cmp_1"> <doc name="reporteInformeEnMayoria"> ... </doc> </component> <component eId="cmpnts__cmp_1__cmpnts__cmp_2"> <bill name="bill"> ... </bill> </component> </components> </documentCollection> </component> <component eId="cmpnts__cmp_2"> <documentCollection name="informeMinoriaNacional" contains="originalVersion"> <meta> ... </meta> <collectionBody> <component eId=" cmpnts__cmp_2__cmp_1"> <documentRef eId=" cmpnts_cmp2_dref_1" href="#cmpnts_cmp_2__cmpnts__cmp_1" showAs="Informe"/> </component> <component eId=" cmpnts__cmp_2__cmp_2"> <documentRef eId="cmpnts_cmp2_dref_2" href="#cmpnts_cmp_2__cmpnts__cmp_2" showAs="Resolucion"/> </component> </collectionBody> <components> <component eId="cmpnts__cmp_2__cmpnts__cmp_1"> <doc name="reportInformeMinoriaNational"> ... </doc> </component> <component eId=" cmpnts__cmp_2__cmpnts__cmp_2"> <statement name="PROYECTO DE RESOLUCIÓN"> ... </statement> </component> </components> </documentCollection> </component> </components> </akomaNtoso> |
|---|
6.2.3 Components and <componentRef>
There are use-cases where an autonomous work, emitted by an authority with its FRBR block, incudes another document that is not autonomous (e.g., draft bill included in a verbatim, resolution included in a report). In these cases we can model the embedded document using <component> part for favouring the markup and we use <componentRef> for referring to this component.
A <componentRef> is a manifestation-level reference to an XML sub-structure that for practical purpose has been extracted from the main structure. The XML substructure does not have independent identity outside of the hosting document, and may be extracted because of length or size considerations, or to better organize the delivery of the requested structures. Being manifestation-level, such structures do not have autonomous legal identity or existence, and should be considered for all purposes as parts directly contained inside the host document. Of course, manifestations of whole documents may be referred to using <componentRef>, as long as this approach is fully equivalent in all purposes to simply inserting the whole document manifestation in place of the reference.
<componentRef> is admissible in the following position:
| Inside of the container like <preface><preamble><recital ><citation><conclusions> <header> etc. | <blockContainer> <componentRef showAs="" src=""/> </blockContainer> |
|---|---|
| Inside of any hcontainer | <hcontainer eId="hcontainer_1" name="hcontainerName"> <componentRef showAs="" src=""/> </hcontainer> <article eId="art_1"> <componentRef showAs="" src=""/> </article> |
| Inside of any subflow like <embeddedStructure><quoted Structure><authorialNote> etc. | <embeddedStructure> <componentRef showAs="" src=""/> </embeddedStructure> <quotedStructure> <componentRef showAs="" src=""/> </quotedStructure> |
6.3 Hierarchical Structure
Any document with a hierarchical structure belongs to this family of documents. For hierarchical structure we mean a structure organized with higher levels that group basic units, basic units (article, section, etc.) and lower levels inside of the basic unit. The Akoma Ntoso standard is neutral with respect to the legal drafting techniques of the different legal traditions, providing most of the hierarchical elements for modelling the body structure: book, tome, part, subpart, title, subtitle, chapter, subchapter, section, subsection, clause, subclause, paragraph, subparagraph, division, point, indent, alinea, list, sublist. For these reasons, the main requirements of structuring legal text are covered. The following table shows an example how to use of hierarchical elements:
| Anglophone tradition | French tradition | Portuguese tradition | Italian tradition | Spanish tradition | EU tradition (here,only English, French, Spanish) | AKOMA NOTOSO | |
|---|---|---|---|---|---|---|---|
| Higher Division | Tome | Tome | tome | ||||
| Part | Partie (codes) | Parte (codes) | Parte | Parte | Part/ Partie parte | part | |
| Livre (codes) | Livro (codes) | Libro | Libro | book | |||
| Title | Titre | Título | Titolo | Título | Title/ Titre/ Titulo | title | |
| Chapter | Chapitre | Capítulo | Capitolo | Capítulo | Chapter/ Chapitre Capitulo | chapter | |
| Subchapter Article (US) | Section (codes) | Secção | Sezione | Sección o Párrafo | Section/ section/ Sección | section | |
| Subsection (code) | SubSeçcão | Subsezione | Subsection/ SousSection/ Subsección | subsection | |||
| level | level | ||||||
| Basic Unit | Section Rule | Article | Artigo | Articolo | Artículo | Article (rule)/ article/ articulo/ | article/ section/ rule |
| Subdivision | Subsection Clause (in US Constitution) | Alinéa | Alineas | Comma | Inciso | unnumbered paragraph/ alinéa / Párrafo6 | subsection aliena clause |
| Paragraph | Paragraphe | Paragrafo | Paragrafo | paragraph paragraphe Apartado | paragraph | ||
| Proviso | proviso | ||||||
| Subparagraph | Subparagraph/ sous paragraphe/ Párrafo7 | subparagraph | |||||
| division | |||||||
| Lettera | letra | Point/ point/ Letra | point/item | ||||
| Numero | número | Point/ point/ punto | point/item | ||||
| Latin number | Point/ point Inciso | point/item | |||||
| Indent/ tiret guion | point/item |
The list of the hierarchical partitions included in Akoma Ntoso are the following, listed in alphabetic order:
- alinea
- article
- book
- chapter
- clause
- division
- indent
- level
- list
- paragraph
- part
- point
- proviso
- rule
- subrule
- section
- subchapter
- subclause
- subdivision
- sublist
- subparagraph
- subpart
- subrule
- subsection
- subtitle
- title
- tome
- transitional.
Each hierarchical element has some relevant optional children that characterize the hierarchy pattern:
- <num>: the element <num> marks up the number of the partition, including letters in case of points (e.g., the point (a) is <num>(a) </num>);
- <heading>: the element <heading> marks up the title of the partition;
- <subheading>: the element <subheading> marks up the subtitle of the partition;
- <crossheading>: the element <crossheading> marks up an intermediate block.
6.4 Debate Structure
The debate structure is dedicated to parliamentary documents such as report of committees, transcript record of the parliament or assembly, Hansard, debates, voting report, roll calling, etc. In particular, to these documents is the unstructured format and the fact that they describe a narrative, similar to a script or a screenplay. For these reasons the debateStructure includes particular structures that permits this modelling.
Debate record is similar to a screenplay and so it is mostly composed by sections according with the main topics or actions admitted in the rules of procedure in the assembly:
- administrationOfOath
- rollCall
- prayers
- oralStatements
- writtenStatements
- personalStatements
- ministerialStatements
- resolutions
- nationalInterest
- declarationOfVote
- communication
- petitions
- papers
- noticesOfMotion
- questions
- address
- proceduralMotions
- pointOfOrder
- adjournment
- debateSection.
Each of these containers can include the following elements:
- speechGroup: group of speeches in the dialogue;
- speech: speech dialogue;
- question: question dialogue;
- answer: answer dialogue;
- other: other dialogue;
- scene: description of some action performed inside of the assembly like applause, shouting, crying, etc.;
- narrative: narrative part of what happened in the assembly;
- summary: summary of an event like the result of a voting.
In case it is necessary we have also inline element <remark> for making up the type of annotation: “sceneDescription” (e.g. the minority party leaves the room shouting out), “phenomenon” (e.g. raining), “caption”, “translation” (e.g. [Bab’ uNkwinti, are you going to say it in Afrikaans?]).
An example of fragment of debate is blow presented.
| <debate name="record"> <meta>...</meta> <coverPage>...</coverPage> <preface>...</preface> <debateBody> <debateSection eId="dbsect_1" name="Preliminary"> <rollCall eId="dbsect_1__rollCall_1">...</rollCall> <prayers eId="dbsect_1__prayers_1">...</prayers> </debateSection> <debateSection eId="dbsect_2" name="Actas"> <speech eId="dbsect_2__speech_1" by="#Ascencio"> <from>El señor ASCENCIO (Presidente).- </from> <p> El señor Secretario dará lectura a los pareos. <remark type="sceneDescription">(Aplausos)</remark>.</p> ..... </speech> <narrative eId="dbsect_2__narrative_1" >-Con posterioridad, la Sala se pronunció sobre el proyecto en los siguientes términos:</narrative> <summary eId="dbsect_2__summary_1" > <outcome refersTo="#seAbstiene"> -Se abstuvieron los diputados señores: <vote by="#persona"> <person eId="p3517" refersTo="#GalileaVidaurreJoseAntonio">Galilea Vidaurre José Antonio;</person> </vote> </outcome> </summary> <scene eId="dbsect_2__scene_1" >-Aplausos.</scene> </debateSection> <debateBody> </debate> |
|---|
6.5 Amendment Structure
The amendment structure is dedicated to modelling particular official documents that provide instructions or proposals for modifications to a bill.
Example: amendment of the European Parliament on a proposal from the Commission can be marked as following.
| <amendment name="amendment"> <meta> <identification source=""> ... </identification> <analysis source="http://www.europarl.europa.eu/"> <activeModifications> <textualMod eId="textualMod_1" type="substitution"> <source href="#mod_1__qstr_2__rec_3"/> <destination href="uri:COM proposal/bill(Expression)]#rec_3"/> </textualMod> </activeModifications> </analysis> <references source="http://www.europarl.europa.eu/"> <TLCConcept eId="concept-content-current" href="/concept/content/current" showAs="original version of amended fragment"/> <TLCConcept eId="concept-content-proposed" href="/concept/content/proposed" showAs="proposed version of amended fragment"/> <TLCPerson eId="codict_person-id-96835" href="eu.europa.europarl.codict:person/id=96835" showAs="Traian Ungureanu"/> <TLCPerson eId="codict_person-id-96832" href="eu.europa.europarl.codict:person/id=96832" showAs="Pascale Gruny"/> </references> </meta> <preface> <container eId="preface__container_1" name="mainDoc"> <p xml:space="preserve"><docIntroducer><person eId="preface__container_1__person_1" refersTo="#codict_person-id-96835">Traian Ungureanu</person> and <person eId="preface__container_1__person_2" refersTo="#codict_person-id-96832">Pascale Gruny</person></docIntroducer></p> </container> </preface> <amendmentBody> <amendmentHeading> <block name="amendedAct" xml:space="preserve"><docType>Proposal for a decision</docType> - amending act</block> <block name="amendedAct" xml:space="preserve"><inline name="AMposition">Recital 3</inline></block> </amendmentHeading> <amendmentContent> <block name="versionTitle" refersTo="#concept-content-current">Text proposed by the Commission</block> <block name="versionTitle" refersTo="#concept-content-proposed">Amendment</block> <block name="changeBlock"> <mod eId="mod_1" refersTo="#textualMod_1"> <quotedStructure eId="mod_1__qstr_1" refersTo="#concept-content-current"> <recital eId="mod_1__qstr_1__rec_3"> <num>(3)</num> <p xml:space="preserve">In line with the Inter-institutional agreement of <date date="2006-05-17">17 May 2006</date> between the European Parliament, the Council and the Commission on budgetary discipline and sound financial management, <change>EUR 100 million needs to be reallocated from the existing budget to finance</change> the new European microfinance facility <change>for employment and social inclusion – Progress</change></p> </recital> </quotedStructure> <quotedStructure eId="mod_1__qstr_2" refersTo="#concept-content-proposed"> <recital eId="mod_1__qstr_2__rec_3"> <num>(3)</num> <p xml:space="preserve">In line with the Inter-institutional agreement of <date date="2006-05-17">17 May 2006</date> between the European Parliament, the Council and the Commission on budgetary discipline and sound financial management, <change>in the event that no additional appropriations are allocated, then</change> the new European microfinance facility <change>should be financed by reallocating resources from other budgetary sources.</change></p> </recital> </quotedStructure> </mod> </block> </amendmentContent> <amendmentJustification> <block name="justificationHeading">Justification</block> <p xml:space="preserve">Due to the present financial situation there is a clear need to find the best financil solution for the new instrument. From this poin of view, there should be furtherconsultations to find the optimal solution in order for the facility to deliver to its aims.</p> </amendmentJustification> </amendmentBody> </amendment> |
|---|
6.6 Judgment Structure
The Judgment structure is dedicated to case-law, precedents, and judiciary decisions. The structure of those documents varies greatly without a common template, especially the metadata are complex and with a great diversity in each legal tradition and judicial system. The main legal part of the judgment <judgmentBody> and it is divided in <background>, <introduction>, <motivation>, <decision> containers. We have also particular inline elements used in the judiciary system:
- <docJurisdiction></docJurisdiction> for marking up the jurisdiction of the case-law;
- <docketNumber></docketNumber> for marking up number of the trial;
- <neutralCitation> for marking up the number assigned by the number used for hamonized the citations in a given judiciaty system (e.g. [2008] ZASCA 134);
- <party refersTo=""></party> for marking up the party;
- <lawyer refersTo=""></lawyer> for marking up the lawyer;
- <judge refersTo=""></judge> for marking up the judge;
- <opinion> for marking up the opinion of each judge;
- <argument></argument> for marking up the argument sentences for supporting the judge’s legal argumentation and reasoning.
Some relevant metadata are included in the <judicial> metadata block for modelling citations to other legal sources and result of the judgment.
An example of fragment of judgment is blow presented.
| <judgment name="decision"> <meta> <identification source="#somebody"></identification> <publication date="2008-11-30" name="Law Report" showAs="Law Report Office Journal" number="555"/> <classification source="#somebody"></classification> <lifecycle source="#somebody"> <eventRef date="2008-11-26" eId="eref_1" source="#ro_1" type="generation"/> </lifecycle> <workflow source="#somebody"> <step date="2007-08-23" eId="step_1" outcome="#outcome_1" by="#chamber "/> <step date="2008-11-05" eId=" step_2" outcome="#outcome_1" by="# senate"/> </workflow> <analysis source="#somebody"> <judicial> <result type="deny"/> <applies eId="applies_1"> <source href="#ref_11"/> <destination href="/za/judgment/SA491/eng@!main.xml"/> </applies> <supports eId="supports_1"> <source href="#ref_12"/> <destination href="/za/judgment/SA490/eng@/!main.xml~par12"/> </supports> </judicial> </analysis> <references source="#somebody"></references> </meta> <header> <p> <party refersTo=""></party> <lawyer refersTo=""></lawyer> <judge refersTo=""></judge> </p> </header> <judgmentBody> <background></background> <introduction></introduction> <motivation></motivation> <decision></decision> </judgmentBody> <conclusions></conclusions> </judgment> </akomaNtoso> |
|---|
6.7 Open Structure
A document is text devoid of any specific structure. Examples include annexes, tables, schedules, informative material, letters, and memorandums.
| Name | Definition | Structure |
|---|---|---|
| DOCUMENT | A document is any valid text for which there is no specific structure or document type. | Texts having an open structure. The main body of the text is the main content. |
An example of usage of the general document is presented below. It is an annex that has no particular structure.
| Appendix 1 OFFICIALS FROM THE DEPARTMENT OF DEFENCE Mr. January (Secretary of Defence and Director General of the Department) Mr. February (Deputy Director General and Chief Director of Policy and Planning) Lieutenant General March (SANDF Chief: Corporate Staff) | <preface> <p class="heading"> <docType>APPENDIX 1</docType> <docTitle>OFFICIALS FROM THE DEPARTMENT OF DEFENCE </docTitle> </p> </preface> <mainBody> <container eId="container_1" name="members" class="memberslist"> <ol eId="container_1__ol_1"> <li eId="container_1__ol_1__li_1> Mr January (Secretary for Defence and Director General of the Department)</li> <li eId="container_1__ol_1__li_2>Mr Feruray (Deputy Director General and Chief Director Policy and Planning)</li> <li eId="container_1__ol_1__li_3>Lieutenant General March </span>(SANDF Chief: Corporate Staff)</li> </ol> </container> |
|---|---|
| 1. Introduction The Portfolio Committee on Defence considered the 2007/2008 Budget of the Department of Defence on 22–23 March 2007 as part of its oversight function over the Department of Defence. The report is based on both the budget hearings held on 22 March 2007 as well as the committee deliberations held on 23 March 2007. | <hcontainer eId="hcontainer_1" name="issue"> <num>1. </num> <heading>Introduction</heading> <paragraph eId="hcontainer_1__para_1"> <content> <p>The Portfolio Committee on Defence considered the 2007/2008 Budget of the Department of Defence on 22 -23 March 2007, as part of its oversight function over the Department of Defence. The report is based on both the budget hearings held on 22 March 2007 as well as the committee deliberations on 23 March 2007. </p> </content> </paragraph> </hcontainer> </mainBody> |
6.8 Portion Structure
The Portion Structure is a particular template which permits modelling a portion of the normative part of a document, at the level of the manifestation. It is a pure technical split. Once modelled, it is possible to refer to the portion inside of another Akoma Ntoso document using the <componentRef> element. This is useful for fragmenting a very long document and for facilitating legal drafting and document management. A typical example could be the US Code composed by different titles that are autonomous works. For the code, we could define this:
| <collectionBody> <component><documentRef href="uri/title1.xml" /></component> <component><documentRef href="uri/title2.xml" /></component> <component><documentRef href="uri/title3.xml" /></component> </collectionBody> |
|---|
Each title is composed by several long chapters. We can use <componentRef> combined with <portion> for better managing the length of the whole document.
| <act> ….<meta>…</meta> ….<body> ….….….<componentRef showAs="" src="/akn/us/usc/title_9/eng@2013-07-26/!main ~chp_1.xml"/> ….….….<componentRef showAs="" src="/akn/us/usc/ title_9/eng@2013-07-26/!main ~chp_2.xml"/> ….….….<componentRef showAs="" src="/akn/us/usc/title_9/eng@2013-07-26/!main ~chp_3.xml"/> omissis ….</body> </act> |
|---|
In this case, the chapter 3 content is outside the document containing the title 9. The chapter has its own meta data block (FRBRManifestation only inside of the FRBR block because the rest FRBRWork and FRBRExpression are the same of the title_9 document) but it is not necessary to have a preface, preamble, or annexes, only <portionBody>. Note that the name of the Manifestation is <FRBRuri value="/akn/us/usc/title_9/eng@2013-07-26/!main~chp_3.xml"/> and in the FRBRManifestation block it is possible to specify also the portion with <FRBRportion from="chp_3" />. In case of interval, (e.g. from chapter 3 to chapter 5) we also use the attribute upTo=”chp_5” to specify the end of the interval.
| <portion includedIn="/akn/us/act/title_9"> <meta> <identification source="#vergottini"> <FRBRWork> <FRBRthis value="/akn/us/usc/title_9/!main"/> <FRBRuri value="/akn/us/usc/title_9"/> <FRBRdate date="1947-07-30" name="Title 9"/> <FRBRauthor href="#olrc" as="#author"/> <FRBRcountry value="us"/> <FRBRsubtype value="title"/> <FRBRnumber value="title_9"/> <FRBRname value="title"/> <FRBRprescriptive value="false"/> <FRBRauthoritative value="true"/> </FRBRWork> <FRBRExpression> <FRBRthis value="/akn/us/usc/eng@2013-07-26/title_9/!main"/> <FRBRuri value="/akn/us/usc/eng@2013-07-26/title_9"/> <FRBRdate date="2013-07-26" name="Chapter 3 of Title 9 (July 26, 2013)"/> <FRBRauthor href="#olrc" as="#editor"/> <FRBRlanguage language="eng"/> </FRBRExpression> <FRBRManifestation> <FRBRthis value="/akn/us/usc/ title_9/eng@2013-07-26/!main |
|---|