Project

Profile

Help

Support #5584 ยป 11-akn-subschema.xsd

schema used - Geert Bormans, 2022-06-28 21:11

 
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns="http://docs.oasis-open.org/legaldocml/ns/akn/3.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://docs.oasis-open.org/legaldocml/ns/akn/3.0"
xmlns:akn="http://docs.oasis-open.org/legaldocml/ns/akn/3.0"
elementFormDefault="qualified" version="1.1" xpathDefaultNamespace="##targetNamespace">


<xsd:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="./xml.xsd"/>

<xsd:annotation>
<xsd:documentation>
=====================================================================
Akoma Ntoso main schema


Release 30/03/2017 - Akoma Ntoso 3.0 - Published 06/06/2017

Automatically generated modular subversion from the full schema.
Current subversion contains the following modules:

hcontainers optHierarchy smallHierarchy additionalHierarchy transitionalSection debateDocs debateReport debate judgmentDocs amendmentDocs collectionDocs amendmentList officialGazette legislativeDocs modifications act bill statementDocs core semantic advancedMetadata toc html table specials components prefaceSubstructures tblock legislativePreface advancedPreface advancedRefs publishing delimiters embedded authorialNote additionalGeneric generic analysis 11_hcm-chapter-section-article-nocontent

Please consult http://www.akomantoso.org/subversions for more information.



technical supervision Fabio Vitali - University of Bologna
legal domain supervision Monica Palmirani - University of Bologna

The present schema uses systematically XML design patterns as
described in http://www.xmlpatterns.com/
A few of them are explicitly mentioned, when their use or approach
was not felt clear or natural enough. Others are just used without
mentions.

TERMS AND CONDITIONS

This schema is provided by OASIS, the Copyright Holder, under licence
cc-by 4.0, that can also be found at the URL
https://creativecommons.org/licenses/by/4.0/legalcode

=====================================================================
</xsd:documentation>
</xsd:annotation>

<xsd:annotation>
<xsd:documentation>
=====================================================================

Main element groups

=====================================================================
</xsd:documentation>
</xsd:annotation>

<xsd:group name="ANhier">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>ANhier</name>
<comment>
The group ANhier lists the elements that belong to the Akoma Ntoso legislative hierarchy.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="section"/>
<xsd:element ref="part"/>
<xsd:element ref="paragraph"/>
<xsd:element ref="chapter"/>
<xsd:element ref="title"/>
<xsd:element ref="article"/>
<xsd:element ref="book"/>
<xsd:element ref="tome"/>
<xsd:element ref="division"/>
<xsd:element ref="list"/>
<xsd:element ref="clause"/>
<xsd:element ref="point"/>
<xsd:element ref="indent"/>
<xsd:element ref="alinea"/>
<xsd:element ref="rule"/>
<xsd:element ref="subrule"/>
<xsd:element ref="proviso"/>
<xsd:element ref="subsection"/>
<xsd:element ref="subpart"/>
<xsd:element ref="subparagraph"/>
<xsd:element ref="subchapter"/>
<xsd:element ref="subtitle"/>
<xsd:element ref="subdivision"/>
<xsd:element ref="subclause"/>
<xsd:element ref="sublist"/>
<xsd:element ref="level"/>
<xsd:element ref="transitional"/>
</xsd:choice>
</xsd:group>

<xsd:group name="ANcontainers">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>ANcontainers</name>
<comment>
The group ANcontainers lists the elements that are containers and are specific to the Akoma Ntoso debate vocabulary.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="speechGroup"/>
<xsd:element ref="speech"/>
<xsd:element ref="question"/>
<xsd:element ref="answer"/>
<xsd:element ref="other"/>
<xsd:element ref="scene"/>
<xsd:element ref="narrative"/>
<xsd:element ref="summary"/>
</xsd:choice>
</xsd:group>

<xsd:group name="basicContainers">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>basicContainers</name>
<comment>
The group basicContainers lists the elements that are containers and are specific to vocabulary of preambles, prefaces, conclusions and coverPages.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="longTitle"/>
<xsd:element ref="formula"/>
<xsd:element ref="container"/>
</xsd:choice>
</xsd:group>

<xsd:group name="preambleContainers">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>preambleContainers</name>
<comment>
The group preambleContainers lists the elements that are containers and are specific to the Akoma Ntoso preamble vocabulary.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="recitals"/>
<xsd:element ref="citations"/>
<xsd:element ref="formula"/>
<xsd:element ref="container"/>
</xsd:choice>
</xsd:group>

<xsd:group name="prefaceContainers">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>prefaceContainers</name>
<comment>
The group prefaceContainers lists the elements that are containers and are specific to the Akoma Ntoso preface vocabulary.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="longTitle"/>
<xsd:element ref="formula"/>
<xsd:element ref="container"/>
</xsd:choice>
</xsd:group>

<xsd:group name="ANblock">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>ANblock</name>
<comment>
The group ANblock lists the elements that are blocks and are specific to the Akoma Ntoso vocabulary.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="blockList"/>
<xsd:element ref="blockContainer"/>
<xsd:element ref="tblock"/>
<xsd:element ref="toc"/>
</xsd:choice>
</xsd:group>

<xsd:group name="ANinline">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>ANinline</name>
<comment>
The group ANinline lists the elements that are inline and are specific to the Akoma Ntoso vocabulary.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="ref"/>
<xsd:element ref="mref"/>
<xsd:element ref="rref"/>
<xsd:element ref="mod"/>
<xsd:element ref="mmod"/>
<xsd:element ref="rmod"/>
<xsd:element ref="remark"/>
<xsd:element ref="recordedTime"/>
<xsd:element ref="vote"/>
<xsd:element ref="outcome"/>
<xsd:element ref="ins"/>
<xsd:element ref="del"/>
<xsd:element ref="omissis"/>
<xsd:element ref="embeddedText"/>
<xsd:element ref="embeddedStructure"/>
<xsd:element ref="opinion"/>
<xsd:element ref="placeholder"/>
<xsd:element ref="fillIn"/>
<xsd:element ref="decoration"/>
</xsd:choice>
</xsd:group>

<xsd:group name="ANtitleInline">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>ANtitleInline</name>
<comment>
The group ANtitleInline lists the elements that are inline, are specific to the Akoma Ntoso vocabulary, and should only be used within the initial elements (preface, preamble and coverpage).
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="docType"/>
<xsd:element ref="docTitle"/>
<xsd:element ref="docNumber"/>
<xsd:element ref="docProponent"/>
<xsd:element ref="docDate"/>
<xsd:element ref="legislature"/>
<xsd:element ref="session"/>
<xsd:element ref="shortTitle"/>
<xsd:element ref="docAuthority"/>
<xsd:element ref="docPurpose"/>
<xsd:element ref="docCommittee"/>
<xsd:element ref="docIntroducer"/>
<xsd:element ref="docStage"/>
<xsd:element ref="docStatus"/>
<xsd:element ref="docJurisdiction"/>
<xsd:element ref="docketNumber"/>
</xsd:choice>
</xsd:group>

<xsd:group name="ANheaderInline">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>ANheaderInline</name>
<comment>
The group ANheaderInline lists the elements that are inline, are specific to the Akoma Ntoso vocabulary, and should only be used within the header element.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="courtType"/>
<xsd:element ref="neutralCitation"/>
<xsd:element ref="party"/>
<xsd:element ref="judge"/>
<xsd:element ref="lawyer"/>
<xsd:element ref="signature"/>
<xsd:element ref="argument"/>
</xsd:choice>
</xsd:group>

<xsd:group name="ANsemanticInline">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>ANsemanticInline</name>
<comment>
The group ANsemanticInline lists additional elements that are inline, and are specific to the Akoma Ntoso vocabulary.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="date"/>
<xsd:element ref="time"/>
<xsd:element ref="person"/>
<xsd:element ref="organization"/>
<xsd:element ref="concept"/>
<xsd:element ref="object"/>
<xsd:element ref="event"/>
<xsd:element ref="location"/>
<xsd:element ref="process"/>
<xsd:element ref="role"/>
<xsd:element ref="term"/>
<xsd:element ref="quantity"/>
<xsd:element ref="def"/>
<xsd:element ref="entity"/>
</xsd:choice>
</xsd:group>

<xsd:group name="ANmarker">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>ANmarker</name>
<comment>
The group ANmarker lists the elements that are markers and are specific to the Akoma Ntoso vocabulary.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="noteRef"/>
<xsd:element ref="eol"/>
<xsd:element ref="eop"/>
</xsd:choice>
</xsd:group>

<xsd:group name="ANsubFlow">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>ANsubFlow</name>
<comment>
The group ANsubFlow lists the elements that are subFlows and are specific to the Akoma Ntoso vocabulary.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence>
<xsd:element ref="authorialNote"/>
</xsd:sequence>
</xsd:group>

<xsd:group name="HTMLcontainers">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>HTMLcontainers</name>
<comment>
The group HTMLcontainers lists the elements that are containers and were inherited from the HTML vocabulary.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence>
<xsd:element ref="div"/>
</xsd:sequence>
</xsd:group>

<xsd:group name="HTMLblock">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>HTMLblock</name>
<comment>
The group HTMLblock lists the elements that are blocks and were inherited from the HTML vocabulary.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="ul"/>
<xsd:element ref="ol"/>
<xsd:element ref="table"/>
<xsd:element ref="p"/>
</xsd:choice>
</xsd:group>

<xsd:group name="HTMLinline">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>HTMLinline</name>
<comment>
The group HTMLinline lists the elements that are inline and were inherited from the HTML vocabulary.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="b"/>
<xsd:element ref="i"/>
<xsd:element ref="a"/>
<xsd:element ref="u"/>
<xsd:element ref="sub"/>
<xsd:element ref="sup"/>
<xsd:element ref="abbr"/>
<xsd:element ref="span"/>
</xsd:choice>
</xsd:group>

<xsd:group name="HTMLmarker">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>HTMLmarker</name>
<comment>
The group HTMLmarker lists the elements that are marker and were inherited from the HTML vocabulary.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="img"/>
<xsd:element ref="br"/>
</xsd:choice>
</xsd:group>

<xsd:group name="judgmentBlock">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>judgmentBlock</name>
<comment>
The group judgmentBlock lists the structures that should be found in a judgment.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="introduction"/>
<xsd:element ref="background"/>
<xsd:element ref="arguments"/>
<xsd:element ref="remedies"/>
<xsd:element ref="motivation"/>
<xsd:element ref="decision"/>
</xsd:choice>
</xsd:group>

<xsd:group name="amendmentBlock">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>amendmentBlock</name>
<comment>
The group amendmentBlock lists the structures that should be found in an amendment.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="amendmentHeading"/>
<xsd:element ref="amendmentContent"/>
<xsd:element ref="amendmentReference"/>
<xsd:element ref="amendmentJustification"/>
</xsd:choice>
</xsd:group>

<xsd:group name="amendmentInline">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>amendmentInline</name>
<comment>
The group amendmentInline lists the inline elements that should be found in the preface of an amendment.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="affectedDocument"/>
<xsd:element ref="relatedDocument"/>
<xsd:element ref="change"/>
</xsd:choice>
</xsd:group>

<xsd:group name="speechSection">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>speechSection</name>
<comment>
The group speechSection lists the structures that should contain speeches.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="administrationOfOath"/>
<xsd:element ref="rollCall"/>
<xsd:element ref="prayers"/>
<xsd:element ref="oralStatements"/>
<xsd:element ref="writtenStatements"/>
<xsd:element ref="personalStatements"/>
<xsd:element ref="ministerialStatements"/>
<xsd:element ref="resolutions"/>
<xsd:element ref="nationalInterest"/>
<xsd:element ref="declarationOfVote"/>
<xsd:element ref="communication"/>
<xsd:element ref="petitions"/>
<xsd:element ref="papers"/>
<xsd:element ref="noticesOfMotion"/>
<xsd:element ref="questions"/>
<xsd:element ref="address"/>
<xsd:element ref="proceduralMotions"/>
<xsd:element ref="pointOfOrder"/>
<xsd:element ref="adjournment"/>
<xsd:element ref="debateSection"/>
</xsd:choice>
</xsd:group>

<xsd:group name="hierElements">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>hierElements</name>
<comment>
The group hierElements lists all the elements that are hierarchical.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:group ref="ANhier"/>
<xsd:element ref="hcontainer"/>
</xsd:choice>
</xsd:group>

<xsd:group name="containerElements">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>containerElements</name>
<comment>
The group containerElements lists all the elements that are containers.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:group ref="speechSection"/>
<xsd:group ref="HTMLcontainers"/>
<xsd:element ref="container"/>
</xsd:choice>
</xsd:group>

<xsd:group name="blockElements">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>blockElements</name>
<comment>
The group blockElements lists all the elements that are blocks.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:group ref="ANblock"/>
<xsd:group ref="HTMLblock"/>
<xsd:element ref="foreign"/>
<xsd:element ref="block"/>
</xsd:choice>
</xsd:group>

<xsd:group name="inlineElements">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>inlineElements</name>
<comment>
The group inlineElements lists all the elements that are inline.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:group ref="ANinline"/>
<xsd:group ref="HTMLinline"/>
<xsd:group ref="ANtitleInline"/>
<xsd:group ref="ANsemanticInline"/>
<xsd:group ref="ANheaderInline"/>
<xsd:group ref="amendmentInline"/>
<xsd:element ref="inline"/>
</xsd:choice>
</xsd:group>

<xsd:group name="subFlowElements">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>subFlowElements</name>
<comment>
The group subFlowElements lists all the elements that are subFlows.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:group ref="ANsubFlow"/>
<xsd:element ref="subFlow"/>
</xsd:choice>
</xsd:group>

<xsd:group name="markerElements">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>markerElements</name>
<comment>
The group markerElements lists all the elements that are markers.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:group ref="ANmarker"/>
<xsd:group ref="HTMLmarker"/>
<xsd:element ref="marker"/>
</xsd:choice>
</xsd:group>

<xsd:group name="inlineCM">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>inlineCM</name>
<comment>
The group inlineCM is the content model of blocks and inlines, and is composed of all the inlines and all the markers.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:group ref="inlineElements"/>
<xsd:group ref="markerElements"/>
<xsd:group ref="subFlowElements"/>
</xsd:choice>
</xsd:group>

<xsd:annotation>
<xsd:documentation>
=====================================================================

Attribute groups

=====================================================================
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup name="contains">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>contains</name>
<comment>
The attribute contains is used in the root of document types to indicate whether the document is original or modified wrt the orignal version.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="contains" type="versionType" default="originalVersion"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="alt">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>alt</name>
<comment>
The attribute alternativeTo is used to specify, when the element contains an alternative version of some content, the eId of the main element which this element is an alternative copy of.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="alternativeTo" type="eIdRef"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="name">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>name</name>
<comment>
The attribute name is used to give a name to all generic elements.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="name" type="xsd:string" use="required"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="number">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>number</name>
<comment>
The attribute number is used to specify a number in the publication of the document.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="number" type="xsd:string"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="source">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>source</name>
<comment>
The attribute source links to the agent (person, organization) providing the specific annotation or markup.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="source" type="agentRef" use="required"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="date">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>date</name>
<comment>
The attribute date is used to give a normalized value for a date according to the XSD syntax YYYY-MM-DD or a normalized value for a dateTime according to the XSD syntax YYYY-MM-DDThh:mm:ss(zzzz).
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="date" use="required">
<xsd:simpleType>
<xsd:union>
<xsd:simpleType>
<xsd:restriction base="xsd:date"/>
</xsd:simpleType>
<xsd:simpleType>
<xsd:restriction base="xsd:dateTime"/>
</xsd:simpleType>
</xsd:union>
</xsd:simpleType>
</xsd:attribute>
</xsd:attributeGroup>

<xsd:attributeGroup name="time">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>time</name>
<comment>
The attribute time is used to give a normalized value for a time according to the XSD syntax HH:MM:SS.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="time" use="required">
<xsd:simpleType>
<xsd:union>
<xsd:simpleType>
<xsd:restriction base="xsd:time"/>
</xsd:simpleType>
<xsd:simpleType>
<xsd:restriction base="xsd:dateTime"/>
</xsd:simpleType>
</xsd:union>
</xsd:simpleType>
</xsd:attribute>
</xsd:attributeGroup>

<xsd:attributeGroup name="link">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>link</name>
<comment>
The attribute href is used to specify an internal or external destination for a reference, a citation, an access to the ontology or a hypertext link. In elements using this attribute definition the href attribute is required.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="href" type="xsd:anyURI" use="required"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="linkopt">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>linkopt</name>
<comment>
The attribute href is used to specify an internal or external destination for a reference, a citation, an access to the ontology or a hypertext link. In elements using this attribute definition the href attribute is optional.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="href" type="xsd:anyURI"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="value">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>value</name>
<comment>
The attribute value is used to specify a value for metadata elements. In elements using this attribute definition the value attribute is required.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="value" type="xsd:string" use="required"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="optvalue">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>optvalue</name>
<comment>
The attribute value is used to specify a value for metadata elements. In elements using this attribute definition the value attribute is optional.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="value" type="xsd:string"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="booleanvalue">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>booleanvalue</name>
<comment>
The attribute value is used here to specify a boolean value for metadata elements. In elements using this attribute definition the value attribute is required.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="value" type="xsd:boolean" use="required"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="interval">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>interval</name>
<comment>
The start and end attributes are used to specify events that mark the beginning and the end of a time interval. Both are references to eventRef elements in the lifecycle element.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="start" type="eventRefRef"/>
<xsd:attribute name="end" type="eventRefRef"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="duration">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>duration</name>
<comment>
The duration attribute is used to specify a duration when either the start or the end event of a time interval is not known..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="duration" type="xsd:duration"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="speechAtts">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>speechAtts</name>
<comment>
The attributes in speechAtts are used in speeches to identify agents and roles of speeches. In particular, attribute 'by' identifies the speaker, optional attribute 'as' identifies the role under which the speaker is speaking, optional attribute startTime specifies the absolute date and time where the individual speech item started, optional attribute endTime specifies the absolute date and time where the individual speech item ended, and optional attribute to identifies the addressee of the speech. All of them are references to person or organization elements in the references section.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup ref="agent"/>
<xsd:attributeGroup ref="role"/>
<xsd:attribute name="startTime" type="xsd:dateTime"/>
<xsd:attribute name="endTime" type="xsd:dateTime"/>
<xsd:attribute name="to" type="agentRef"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="voteAtts">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>voteAtts</name>
<comment>
The attributes in voteAtts are used in votes to identify agents and choices in votes. In particular, attribute 'by' identifies the voter, optional attribute 'as' identifies the role under which the voter is acting, optional attribute 'choice' specifies the vote that was casted..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup ref="agent"/>
<xsd:attributeGroup ref="role"/>
<xsd:attribute name="choice" type="voteRef"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="frozen">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>frozen</name>
<comment>
The attribute frozen for the condition element specifies whether the condition is frozen or not in the time period of this expression..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="frozen" type="xsd:boolean"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="lawyerAtts">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>lawyerAtts</name>
<comment>
The attributes in lawyerAtts are used in the inline element lawyer to identify representation aspects of lawyers. In particular, attribute 'as' identifies his/her role, attribute 'for' identifies which party it represents, and attribute 'empoweredBy' identifies another lawyer, if any, this lawyer received the power delegation of power..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup ref="role"/>
<xsd:attribute name="for" type="agentRef"/>
<xsd:attribute name="empoweredBy" type="agentRef"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="normalizedAtt">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>normalizedAtt</name>
<comment>
The attribute normalized is used in the inline element quantity to provide a normalized value of the number, if appropriate..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="normalized" type="xsd:string"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="for">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>for</name>
<comment>
The attribute for is used in modification elements to specify the element this is a modification of..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="for" type="eIdRef"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="mappingAtts">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>mappingAtts</name>
<comment>
The mappingAtts attributes represent the reference to the permanent wId (attribute original) of a structure, and to the eId (attribute current) such structure had during the time interval included between an initial temporalGroup (attribute start) and a final temporalGroup (attribute end)..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="original" type="wIdRef"/>
<xsd:attribute name="current" type="eIdRef"/>
<xsd:attribute name="start" type="eventRefRef"/>
<xsd:attribute name="end" type="eventRefRef"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="originating">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>originating</name>
<comment>
The attribute originating is used to identify whether the event is the one originating this expression.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="originatingExpression" type="xsd:boolean"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="outcome">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>outcome</name>
<comment>
The attribute outcome is used to identify the outcome of a step in a workflow. It is a reference to a TLCConcept element in the references section.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="outcome" type="conceptRef"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="portionAtt">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>portionAtt</name>
<comment>
the attribute includedIn specifies the eId of the element of the references section identifying the document that this portion is a portion of..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="includedIn" type="referenceRef" use="required"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="level">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>level</name>
<comment>
the attribute level specifies the level of the toc element..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="level" type="xsd:integer" use="required"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="target">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>target</name>
<comment>
the attribute target specifies the target of the a element..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="target" type="xsd:string"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="imgAtts">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>imgAtts</name>
<comment>
these attributes specify the dimension of the image..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="width" type="xsd:integer"/>
<xsd:attribute name="height" type="xsd:integer"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="tableAtts">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>tableAtts</name>
<comment>
these attributes specify the characteristics of the table..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="width" type="xsd:integer"/>
<xsd:attribute name="border" type="xsd:integer"/>
<xsd:attribute name="cellspacing" type="xsd:integer"/>
<xsd:attribute name="cellpadding" type="xsd:integer"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="originalText">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>originalText</name>
<comment>
the attribute originalText contains the original text of a placeholder.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="originalText" type="xsd:string"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="fillInWidth">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>fillInWidth</name>
<comment>
the attribute width of the element fillIn specifies the width of the fillIn element..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="width" type="xsd:string"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="upTo">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>upTo</name>
<comment>
The attribute upTo is used in range-based elements to specify the eId of the ending element of the range..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="upTo" type="eIdRef" use="required"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="upToOpt">


<xsd:attribute name="upTo" type="eIdRef"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="range">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>range</name>
<comment>
These attributes are used in range-based elements to specify the eId of the beginning and ending element of the range..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="from" type="eIdRef" use="required"/>
<xsd:attributeGroup ref="upTo"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="rangeOpt">


<xsd:attribute name="from" type="eIdRef" use="required"/>
<xsd:attributeGroup ref="upToOpt"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="pos">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>pos</name>
<comment>
The attribute pos is used to identify the specific position of the reference (e.g., in source or destination)
with respect to the element being identified with the relative eId..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="pos" type="posType"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="language">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>language</name>
<comment>
This attribute specifies the human language in which the document the element refers to is expressed. Values are taken from the RFC 4646..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="language" type="language" use="required"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="fromLanguage">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>fromLanguage</name>
<comment>
This attribute specifies the human language of the expression this is a translation of. Values are taken from the RFC 4646..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="fromLanguage" type="language" use="required"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="pivot">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>pivot</name>
<comment>
This attribute specifies the human language used as a pivot in the translation. Values are taken from the RFC 4646..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="pivot" type="language"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="authoritative">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>authoritative</name>
<comment>
This attribute specifies whether the translation is authoritative or not.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="authoritative" type="xsd:boolean"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="dictionary">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>dictionary</name>
<comment>
This attribute specifies the eId of the element in the references section detailing the dictionary used for the keyword..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="dictionary" type="referenceRef" use="required"/>
</xsd:attributeGroup>

<xsd:annotation>
<xsd:documentation>
=====================================================================

Attribute groups: attribute "type"

=====================================================================
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup name="type">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>type</name>
<comment>
The type attribute is used in various element to identify a type without restrictions as to its values..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="type" type="xsd:string"/>
</xsd:attributeGroup>

<xsd:simpleType name="eventType">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>eventType</name>
<comment>
This is the list of allowed values for the type attribute of the eventRef element.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="generation"/>
<xsd:enumeration value="amendment"/>
<xsd:enumeration value="repeal"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:attributeGroup name="eventType">


<xsd:attribute name="type" type="eventType"/>
</xsd:attributeGroup>

<xsd:simpleType name="opinionType">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>opinionType</name>
<comment>
This is the list of allowed values for the type attribute of the opinion element.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="dissenting"/>
<xsd:enumeration value="agreeing"/>
<xsd:enumeration value="null"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:attributeGroup name="opinionType">


<xsd:attributeGroup ref="agent"/>
<xsd:attribute name="type" type="opinionType"/>
</xsd:attributeGroup>

<xsd:simpleType name="resultType">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>resultType</name>
<comment>
This is the list of allowed values for the type attribute of the result element.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="deny"/>
<xsd:enumeration value="dismiss"/>
<xsd:enumeration value="uphold"/>
<xsd:enumeration value="revert"/>
<xsd:enumeration value="replaceOrder"/>
<xsd:enumeration value="remit"/>
<xsd:enumeration value="decide"/>
<xsd:enumeration value="approve"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:attributeGroup name="resultType">


<xsd:attribute name="type" type="resultType" use="required"/>
</xsd:attributeGroup>

<xsd:simpleType name="remarkType">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>remarkType</name>
<comment>
This is the list of allowed values for the type attribute of the remark element for the specification of editorial remarks (e.g., applauses, laughters, etc.) especially within debate records.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="sceneDescription"/>
<xsd:enumeration value="phenomenon"/>
<xsd:enumeration value="caption"/>
<xsd:enumeration value="translation"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:attributeGroup name="remarkType">


<xsd:attribute name="type" type="remarkType"/>
</xsd:attributeGroup>

<xsd:simpleType name="timeType">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>timeType</name>
<comment>
This is the list of allowed values for the type attribute of the recordedTime element for the specification of an explicit mention of a time (e.g., in a debate).
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="startEvent"/>
<xsd:enumeration value="endEvent"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:attributeGroup name="recordedTimeType">


<xsd:attribute name="type" type="timeType"/>
</xsd:attributeGroup>

<xsd:simpleType name="TextualMods">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>TextualMods</name>
<comment>
The simple type TextualMods lists all the types of textual modifications as values for the type attribute of the textualMod element..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="repeal"/>
<xsd:enumeration value="substitution"/>
<xsd:enumeration value="insertion"/>
<xsd:enumeration value="replacement"/>
<xsd:enumeration value="renumbering"/>
<xsd:enumeration value="split"/>
<xsd:enumeration value="join"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:attributeGroup name="textualModType">


<xsd:attribute name="type" type="TextualMods" use="required"/>
</xsd:attributeGroup>

<xsd:simpleType name="MeaningMods">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>MeaningMods</name>
<comment>
The simple type MeaningMods lists all the types of modifications in meaning as values for the type attribute of the meaningMod element..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="variation"/>
<xsd:enumeration value="termModification"/>
<xsd:enumeration value="authenticInterpretation"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:attributeGroup name="meaningModType">


<xsd:attribute name="type" type="MeaningMods" use="required"/>
</xsd:attributeGroup>

<xsd:simpleType name="ScopeMods">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>ScopeMods</name>
<comment>
The simple type ScopeMods lists all the types of modifications in scope as values for the type attribute of the scopeMod element..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="exceptionOfScope"/>
<xsd:enumeration value="extensionOfScope"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:attributeGroup name="scopeModType">


<xsd:attribute name="type" type="ScopeMods" use="required"/>
</xsd:attributeGroup>

<xsd:simpleType name="ForceMods">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>ForceMods</name>
<comment>
The simple type ForceMods lists all the types of modifications in force as values for the type attribute of the forceMod element..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="entryIntoForce"/>
<xsd:enumeration value="endOfEnactment"/>
<xsd:enumeration value="postponementOfEntryIntoForce"/>
<xsd:enumeration value="prorogationOfForce"/>
<xsd:enumeration value="reEnactment"/>
<xsd:enumeration value="unconstitutionality"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:attributeGroup name="forceModType">


<xsd:attribute name="type" type="ForceMods" use="required"/>
</xsd:attributeGroup>

<xsd:simpleType name="EfficacyMods">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>EfficacyMods</name>
<comment>
The simple type EfficacyMods lists all the types of modifications in efficacy as values for the type attribute of the efficacyMod element..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="entryIntoEfficacy"/>
<xsd:enumeration value="endOfEfficacy"/>
<xsd:enumeration value="inapplication"/>
<xsd:enumeration value="retroactivity"/>
<xsd:enumeration value="extraefficacy"/>
<xsd:enumeration value="postponementOfEfficacy"/>
<xsd:enumeration value="prorogationOfEfficacy"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:attributeGroup name="efficacyModType">


<xsd:attribute name="type" type="EfficacyMods" use="required"/>
</xsd:attributeGroup>

<xsd:simpleType name="LegalSystemMods">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>LegalSystemMods</name>
<comment>
The simple type LegalSystemMods lists all the types of modifications in the legal system as values for the type attribute of the LegalSystemMod element..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="staticReference"/>
<xsd:enumeration value="implementation"/>
<xsd:enumeration value="ratification"/>
<xsd:enumeration value="application"/>
<xsd:enumeration value="legislativeDelegation"/>
<xsd:enumeration value="deregulation"/>
<xsd:enumeration value="conversion"/>
<xsd:enumeration value="expiration"/>
<xsd:enumeration value="reiteration"/>
<xsd:enumeration value="remaking"/>
<xsd:enumeration value="republication"/>
<xsd:enumeration value="coordination"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:attributeGroup name="legalSystemModType">


<xsd:attribute name="type" type="LegalSystemMods" use="required"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="show">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>show</name>
<comment>
These attributes are used in metadata to propose visible representations of the metadata itself. Both a full visualization (attribute showAs) and an abbreviated one (attribute shortForm) can be specified.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="showAs" type="xsd:string" use="required"/>
<xsd:attribute name="shortForm" type="xsd:string"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="showopt">


<xsd:attribute name="showAs" type="xsd:string"/>
<xsd:attribute name="shortForm" type="xsd:string"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="src">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>src</name>
<comment>
These attributes are used in manifestation-level references to specify external manifestation-level resources to be loaded in place. The src attribute holds the manifestation-level IRI of the resource, while the alt attribute holds the text to be displayed in case the loading of the external resource is not possible for any reason..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="src" type="manifestationURI" use="required"/>
<xsd:attribute name="alt" type="xsd:string"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="period">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>period</name>
<comment>
The period attribute is used in versioned content and metadata elements to indicate a time interval in which they were in force, in efficacy, or in any other type of interval as specified in the corresponding temporalGroup..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="period" type="temporalGroupRef"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="enactment">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>enactment</name>
<comment>
These attributes are those already defined in attribute list "period", plus the attribute status, that allows to specify the status of the piece of text it wraps..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup ref="period"/>
<xsd:attribute name="status" type="statusType"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="notes">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>notes</name>
<comment>
These attributes are used by notes, both authorial and editorial. The marker is the string to be used as a marker of the note, the placement is the position where the note should be placed, and placementBase is the eId of the element respect to which the note should be placed near..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="marker" type="xsd:string"/>
<xsd:attribute name="placement" type="placementType"/>
<xsd:attribute name="placementBase" type="eIdRef"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="modifiers">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>modifiers</name>
<comment>
These attributes are used in the analysis to allow manifestation editors to specify whether the analysis is complete and/or ignored in the text.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="exclusion" type="xsd:boolean"/>
<xsd:attribute name="incomplete" type="xsd:boolean"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="role">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>role</name>
<comment>
The attribute role is used to identify the role of an individual mentioned in the text. It is a reference to a TLCRole element in the references section.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="as" type="roleRef"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="agent">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>agent</name>
<comment>
The attribute by is used to identify the agent of an action. It is a reference to a TLCPerson or TLCOrganization element in the references section.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="by" type="agentRef" use="required"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="quote">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>quote</name>
<comment>
The attributes startQuote and endQuote are used in quotedText, quotedStructure, embeddedText and embeddedStructure to specify the start and quote character delimiting the quoted or embedded part. If the characters are the same, one can use only startQuote. Attribute inlineQuote is used for marking the character showing continuation of a quote e.g. at the beginning of each page or at the beginning of each line of the quote.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="startQuote" type="xsd:string"/>
<xsd:attribute name="endQuote" type="xsd:string"/>
<xsd:attribute name="inlineQuote" type="xsd:string"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="cellattrs">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>cellattrs</name>
<comment>
These attributes are used to specify that table cells span more than one row or one column, exactly as in HTML.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="rowspan" type="xsd:integer" default="1"/>
<xsd:attribute name="colspan" type="xsd:integer" default="1"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="HTMLattrs">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>HTMLattrs</name>
<comment>
These attributes are used to specify class, style and title of the element, exactly as in HTML.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="class" type="xsd:string"/>
<xsd:attribute name="style" type="xsd:string"/>
<xsd:attribute name="title" type="xsd:string"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="core">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>core</name>
<comment>
This attribute list are used to specify the fact that any attribute can be specified for this element if it belongs to a different namespace..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="idreq">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>idreq</name>
<comment>
These attributes identify the element in an absolute manner. In elements using this attribute definition the eId attribute is required whenever the Akoma Ntoso naming Convention is used. The wId is used to mark the identifier that the structure used to have in the original version, and is only needed when a renumbering occurred..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="eId" type="noWhiteSpace"/>
<xsd:attribute name="wId" type="noWhiteSpace"/>
<xsd:attribute name="GUID" type="noWhiteSpace"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="idopt">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>idopt</name>
<comment>
These attributes identify the element in an absolute manner. In elements using this attribute definition the eId attribute is optional. The wId is used to mark the identifier that the structure used to have in the original version, and is only needed when a renumbering occurred..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="eId" type="noWhiteSpace"/>
<xsd:attribute name="wId" type="noWhiteSpace"/>
<xsd:attribute name="GUID" type="noWhiteSpace"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="refersreq">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>refersreq</name>
<comment>
This attribute creates a connection between the element and an element of the Akoma Ntoso ontology to which it refers. In elements using this attribute definition the refersTo attribute is required.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="refersTo" use="required">
<xsd:simpleType>
<xsd:list>
<xsd:simpleType>
<xsd:restriction base="referenceRef"/>
</xsd:simpleType>
</xsd:list>
</xsd:simpleType>
</xsd:attribute>
</xsd:attributeGroup>

<xsd:attributeGroup name="refers">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>refers</name>
<comment>
This attribute creates a connection between the element and an element of the Akoma Ntoso ontology to which it refers. In elements using this attribute definition the refersTo attribute is optional.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute name="refersTo">
<xsd:simpleType>
<xsd:list>
<xsd:simpleType>
<xsd:restriction base="referenceRef"/>
</xsd:simpleType>
</xsd:list>
</xsd:simpleType>
</xsd:attribute>
</xsd:attributeGroup>

<xsd:attributeGroup name="xmllang">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>xmllang</name>
<comment>
These attribute specify the human language in which the content of the element is expressed as well as the rules for whitespace management in the element. Values for xml:lang are taken from the RFC 4646. Both xml:lang and xml:space are reserved attributes of the XML language, and cannot be used for any other purpose than these ones..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attribute ref="xml:lang"/>
<xsd:attribute ref="xml:space"/>
<xsd:attribute ref="xml:id"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="corereq">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>corereq</name>
<comment>
This is the list of the core attributes that all elements in the content part of the document must have. In elements using this attribute definition the refersTo attribute is optional but the eId attribute is required.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup ref="core"/>
<xsd:attributeGroup ref="HTMLattrs"/>
<xsd:attributeGroup ref="enactment"/>
<xsd:attributeGroup ref="idreq"/>
<xsd:attributeGroup ref="refers"/>
<xsd:attributeGroup ref="xmllang"/>
<xsd:attributeGroup ref="alt"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="corereqreq">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>corereqreq</name>
<comment>
This is the list of the core attributes that all elements in the content part of the document must have. In elements using this attribute definition both the refersTo attribute and the eId attribute are required.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup ref="core"/>
<xsd:attributeGroup ref="HTMLattrs"/>
<xsd:attributeGroup ref="enactment"/>
<xsd:attributeGroup ref="idreq"/>
<xsd:attributeGroup ref="refersreq"/>
<xsd:attributeGroup ref="xmllang"/>
<xsd:attributeGroup ref="alt"/>
</xsd:attributeGroup>

<xsd:attributeGroup name="coreopt">
<xsd:annotation>
<xsd:documentation>
<type>Attlist</type>
<name>coreopt</name>
<comment>
This is the list of the core attributes that all elements in the content part of the document must have. In elements using this attribute definition both the refersTo attribute and the eId attribute are optional.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup ref="core"/>
<xsd:attributeGroup ref="HTMLattrs"/>
<xsd:attributeGroup ref="enactment"/>
<xsd:attributeGroup ref="idopt"/>
<xsd:attributeGroup ref="refers"/>
<xsd:attributeGroup ref="xmllang"/>
<xsd:attributeGroup ref="alt"/>
</xsd:attributeGroup>

<xsd:annotation>
<xsd:documentation>
=====================================================================

Simple types (data values)

=====================================================================
</xsd:documentation>
</xsd:annotation>

<xsd:simpleType name="noWhiteSpace">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>noWhiteSpace</name>
<comment>
These values are those of ids such as eId, wId and GUID as a collection of any printable character except whitespaces..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:pattern value="[^\s]+"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:simpleType name="eIdRef">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>eIdRef</name>
<comment>
These values are references to existing eIds only, i.e., given an existing eId of the form XYZ, the value is necessarily #XYZ.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:anyURI"/>
</xsd:simpleType>

<xsd:simpleType name="wIdRef">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>wIdRef</name>
<comment>
These values are references to existing wIds only, i.e., given an existing wId of the form XYZ, the value is necessarily #XYZ.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:anyURI"/>
</xsd:simpleType>

<xsd:simpleType name="roleRef">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>roleRef</name>
<comment>
These values are references to existing roles (i.e., TLCRole) only, i.e., given an existing eId of a role of the form XYZ, the value is necessarily #XYZ.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:anyURI"/>
</xsd:simpleType>

<xsd:simpleType name="agentRef">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>agentRef</name>
<comment>
These values are references to existing agents (i.e., TLCPerson or TLCOrganization) only, i.e., given an existing eId of an agent of the form XYZ, the value is necessarily #XYZ.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:anyURI"/>
</xsd:simpleType>

<xsd:simpleType name="conceptRef">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>conceptRef</name>
<comment>
These values are references to existing concepts (i.e., TLCConcept) only, i.e., given an existing eId of a concept of the form XYZ, the value is necessarily #XYZ.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:anyURI"/>
</xsd:simpleType>

<xsd:simpleType name="referenceRef">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>referenceRef</name>
<comment>
These values are references to existing References elements only, i.e., given an existing eId of an element of the References section of the form XYZ, the value is necessarily #XYZ.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:anyURI"/>
</xsd:simpleType>

<xsd:simpleType name="voteRef">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>voteRef</name>
<comment>
These values are references to existing votes (i.e., quorum or count) only, i.e., given an existing eId of a vote element of the form XYZ, the value is necessarily #XYZ.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:anyURI"/>
</xsd:simpleType>

<xsd:simpleType name="eventRefRef">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>eventRefRef</name>
<comment>
These values are references to existing event references (i.e., eventRef) only, i.e., given an existing eId of an eventRef of the form XYZ, the value is necessarily #XYZ.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:anyURI"/>
</xsd:simpleType>

<xsd:simpleType name="temporalGroupRef">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>temporalGroupRef</name>
<comment>
These values are references to existing temporal groups only, i.e., given an existing eId of a temporal group of the form XYZ, the value is necessarily #XYZ.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:anyURI"/>
</xsd:simpleType>

<xsd:simpleType name="manifestationURI">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>manifestationURI</name>
<comment>
These values are references of a manifestation-Level document only.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:anyURI"/>
</xsd:simpleType>

<xsd:simpleType name="language">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>language</name>
<comment>
This type specifies the human language in which the document the element refers to is expressed. Values are taken from the RFC 4646..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string"/>
</xsd:simpleType>

<xsd:simpleType name="versionType">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>versionType</name>
<comment>
This is the list of allowed values for the contains attribute.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="originalVersion"/>
<xsd:enumeration value="singleVersion"/>
<xsd:enumeration value="multipleVersions"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:simpleType name="placementType">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>placementType</name>
<comment>
This is the list of allowed values for the placement attribute of notes.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="side"/>
<xsd:enumeration value="left"/>
<xsd:enumeration value="right"/>
<xsd:enumeration value="bottom"/>
<xsd:enumeration value="inline"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:simpleType name="statusType">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>statusType</name>
<comment>
This is the list of allowed values for the status attribute. This is the list of possible reasons for a dscrepancy between the manifestation as it should be (e.g., a faithful representation of the content of an expression), and the manifestation as it actually is. Values should be interpreted as follows:
- removed: the content of the element is present in the markup (manifestation) but is not present in the real content of the document (expression level) because it has been definitely removed (either ex tunc, as in annullments, or ex nunc, as in abrogations).
- temporarily removed: the content of the element is present in the markup (manifestation) but is not present in the real content of the document (expression level) because it has been temporarily removed (e.g., for a temporary suspension or limitation of efficacy).
- translated: the content of the element is present in the markup (manifestation) in a different form than in the real content of the document (expression level) because it has been translated into a different language (e.g., to match the rest of the document or because of other editorial decisions).
- editorial: the content of the element is present in the markup (manifestation) but is not present in the real content of the document (expression level) because it has been inserted as an editorial process when creating the XML markup.
- edited: the content of the element is different in the markup (manifestation) than in the real content of the document (expression level) because it has been amended (e.g., to remove scurrilous or offensive remarks).
- verbatim: the content of the element is present in the markup (manifestation) is EXACTLY as it was in the real content of the document (expression level) because usual silent fixes and edits were NOT performed (e.g. to punctuation, grammatical errors or other usually non-debatable problems).
- incomplete: the content of the element or the value of a required attribute is NOT present in the markup (manifestation), although it should, because the missing data is not known at the moment, but in the future it might become known. This is especially appropriate for documents in drafting phase (e.g., the publication date of the act while drafting the bill)
- unknown: the content of the element or the value of a required attribute is NOT present in the markup (manifestation), although it should, because the author of the manifestation does not know it.
- undefined: the content of the element or the value of a required attribute is NOT present in the markup (manifestation), because the information is not defined in the original document, or it doesn't exist in some legal tradition (e.g. an anonymous speech cannot specify the attribute by, or some publications do not record the numbering of the items, etc.)
- ignored: the content of the element or the value of a required attribute is NOT present in the markup (manifestation) because the information exists but the author of the manifestation is not interested in reporting it (e.g., omitted parts of the document due to editorial reasons, etc.).
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="removed"/>
<xsd:enumeration value="temporarilyRemoved"/>
<xsd:enumeration value="translated"/>
<xsd:enumeration value="editorial"/>
<xsd:enumeration value="edited"/>
<xsd:enumeration value="verbatim"/>
<xsd:enumeration value="incomplete"/>
<xsd:enumeration value="unknown"/>
<xsd:enumeration value="undefined"/>
<xsd:enumeration value="ignored"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:simpleType name="posType">
<xsd:annotation>
<xsd:documentation>
<type>Simple</type>
<name>posType</name>
<comment>
This is the list of possible positions of the text being analyzed by the element in the analysis section.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:restriction base="xsd:string">
<xsd:enumeration value="start"/>
<xsd:enumeration value="before"/>
<xsd:enumeration value="inside"/>
<xsd:enumeration value="after"/>
<xsd:enumeration value="end"/>
<xsd:enumeration value="unspecified"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:annotation>
<xsd:documentation>
=====================================================================

Complex types (markup structures)

=====================================================================
</xsd:documentation>
</xsd:annotation>

<xsd:complexType name="basehierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>basehierarchy</name>
<comment>
The complex type basehierarchy is not used by any element, but is derived by other types to contain the basic structure of hierarchical elements.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:element ref="num" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="heading" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="subheading" minOccurs="0" maxOccurs="1"/>
</xsd:choice>
</xsd:complexType>

<xsd:complexType name="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>hierarchy</name>
<comment>
The complex type hierarchy is used by most or all the hierarchical elements of act-like documents..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:complexContent>
<xsd:extension base="basehierarchy">
<xsd:choice>
<xsd:sequence>
<xsd:element ref="intro" minOccurs="0" maxOccurs="1"/>
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:element ref="componentRef"/>
<xsd:group ref="hierElements"/>
<xsd:element ref="crossHeading"/>
</xsd:choice>
<xsd:element ref="wrapUp" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:element ref="content"/>
</xsd:choice>
<xsd:attributeGroup ref="corereq"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

<xsd:complexType name="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>althierarchy</name>
<comment>
The complex type althierarchy is used by most or all the hierarchical elements of documents that are not act-like..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:complexContent>
<xsd:extension base="basehierarchy">
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:group ref="containerElements"/>
<xsd:element ref="componentRef"/>
<xsd:group ref="ANcontainers"/>
<xsd:group ref="blockElements"/>
</xsd:choice>
<xsd:attributeGroup ref="corereq"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

<xsd:complexType name="blocksreq">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>blocksreq</name>
<comment>
the complex type blocksreq defines the content model and attributes shared by all containers. Here the eId attribute is required.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence minOccurs="0" maxOccurs="unbounded">
<xsd:group ref="blockElements"/>
</xsd:sequence>
<xsd:attributeGroup ref="corereq"/>
</xsd:complexType>

<xsd:complexType name="blocksopt">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>blocksopt</name>
<comment>
the complex type blocksopt defines the content model and attributes shared by all containers. Here the eId attribute is optional.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence minOccurs="0" maxOccurs="unbounded">
<xsd:group ref="blockElements"/>
</xsd:sequence>
<xsd:attributeGroup ref="coreopt"/>
</xsd:complexType>

<xsd:complexType name="inline" mixed="true">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>inline</name>
<comment>
the complex type inline defines the content model and attributes shared by all blocks and inlines. Here the eId attribute is optional.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:group ref="inlineCM"/>
</xsd:choice>
<xsd:attributeGroup ref="coreopt"/>
</xsd:complexType>

<xsd:complexType name="inlinereq" mixed="true">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>inlinereq</name>
<comment>
the complex type inlinereq defines the content model and attributes shared by all blocks and inlines. Here the eId attribute is required.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:group ref="inlineCM"/>
</xsd:choice>
<xsd:attributeGroup ref="corereq"/>
</xsd:complexType>

<xsd:complexType name="inlinereqreq" mixed="true">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>inlinereqreq</name>
<comment>
the complex type inlinereq defines the content model and attributes shared by all blocks and inlines. Here the eId attribute is required and also the refersTo is required.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:group ref="inlineCM"/>
</xsd:choice>
<xsd:attributeGroup ref="corereqreq"/>
</xsd:complexType>

<xsd:complexType name="markerreq">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>markerreq</name>
<comment>
the complex type markerreq defines the content model and attributes shared by all marker elements. Here the eId attribute is required.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup ref="corereq"/>
</xsd:complexType>

<xsd:complexType name="markeropt">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>markeropt</name>
<comment>
the complex type markeropt defines the content model and attributes shared by all marker elements. Here the eId attribute is optional.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup ref="coreopt"/>
</xsd:complexType>

<xsd:complexType name="metareq">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>metareq</name>
<comment>
the complex type metareq defines the content model and attributes shared by all metadata elements. Here the eId attribute is required.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup ref="core"/>
<xsd:attributeGroup ref="idreq"/>
</xsd:complexType>

<xsd:complexType name="metaopt">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>metaopt</name>
<comment>
the complex type metaopt defines the content model and attributes shared by all metadata elements. Here the eId attribute is optional.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup ref="core"/>
<xsd:attributeGroup ref="idopt"/>
</xsd:complexType>

<xsd:complexType name="maincontent">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>maincontent</name>
<comment>
the complex type maincontent is used by container elements that can contain basically any other Akoma Ntoso structure.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice minOccurs="1" maxOccurs="unbounded">
<xsd:element ref="componentRef"/>
<xsd:group ref="hierElements"/>
<xsd:group ref="blockElements"/>
<xsd:group ref="containerElements"/>
</xsd:choice>
<xsd:attributeGroup ref="coreopt"/>
</xsd:complexType>

<xsd:complexType name="speechType">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>speechType</name>
<comment>
the complex type speechType defines the content model and attributes shared by all speech elements. Here the eId attribute is optional.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:complexContent>
<xsd:extension base="basehierarchy">
<xsd:sequence>
<xsd:element ref="from" minOccurs="0" maxOccurs="1"/>
<xsd:sequence minOccurs="1" maxOccurs="unbounded">
<xsd:group ref="blockElements"/>
</xsd:sequence>
</xsd:sequence>
<xsd:attributeGroup ref="coreopt"/>
<xsd:attributeGroup ref="speechAtts"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

<xsd:complexType name="itemType">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>itemType</name>
<comment>
The complex type itemType is similar to a hierarchical element, but is isolated and does not belong to a full hierarchy..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:complexContent>
<xsd:extension base="basehierarchy">
<xsd:sequence minOccurs="1" maxOccurs="unbounded">
<xsd:group ref="blockElements"/>
</xsd:sequence>
<xsd:attributeGroup ref="corereq"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

<xsd:complexType name="referenceType">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>referenceType</name>
<comment>
the complex type referenceType defines the empty content model and the list of attributes for metadata elements in the references section.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup ref="core"/>
<xsd:attributeGroup ref="idreq"/>
<xsd:attributeGroup ref="link"/>
<xsd:attributeGroup ref="show"/>
</xsd:complexType>

<xsd:complexType name="srcType">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>srcType</name>
<comment>
the complex type srcType defines the empty content model and the list of attributes for manifestation-level references to external resources.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup ref="core"/>
<xsd:attributeGroup ref="idopt"/>
<xsd:attributeGroup ref="src"/>
<xsd:attributeGroup ref="show"/>
</xsd:complexType>

<xsd:complexType name="linkType">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>linkType</name>
<comment>
the complex type linkType defines the empty content model and the list of attributes for Work- or Expression-level references to external resources.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:attributeGroup ref="core"/>
<xsd:attributeGroup ref="idreq"/>
<xsd:attributeGroup ref="link"/>
<xsd:attributeGroup ref="show"/>
</xsd:complexType>

<xsd:complexType name="anyOtherType">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>anyOtherType</name>
<comment>
the complex type anyOtherType defines an open content model for elements that may use elements from other namespaces..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xsd:choice>
<xsd:attributeGroup ref="core"/>
<xsd:attributeGroup ref="idopt"/>
<xsd:attributeGroup ref="linkopt"/>
</xsd:complexType>

<xsd:complexType name="docContainerType">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>docContainerType</name>
<comment>
the complex type docContainerType defines a shared content model for elements that contain whole documents, namely attachment, collectionItem, component..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:complexContent>
<xsd:extension base="basehierarchy">
<xsd:choice>
<xsd:group ref="documentType"/>
<xsd:element ref="interstitial"/>
<xsd:element ref="toc"/>
<xsd:element ref="documentRef"/>
</xsd:choice>
<xsd:attributeGroup ref="corereq"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

<xsd:annotation>
<xsd:documentation>
=====================================================================

Root element
Comment: One generic root element contains all document elements
Pattern: Universal Root
Reference: http://www.xmlpatterns.com/UniversalRootMain.shtml

=====================================================================
</xsd:documentation>
</xsd:annotation>

<xsd:group name="documentType">
<xsd:annotation>
<xsd:documentation>
<type>Group</type>
<name>documentType</name>
<comment>
the type documentType lists all the document types that are managed by Akoma Ntoso.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:element ref="amendmentList"/>
<xsd:element ref="officialGazette"/>
<xsd:element ref="documentCollection"/>
<xsd:element ref="act"/>
<xsd:element ref="bill"/>
<xsd:element ref="debateReport"/>
<xsd:element ref="debate"/>
<xsd:element ref="statement"/>
<xsd:element ref="amendment"/>
<xsd:element ref="judgment"/>
<xsd:element ref="portion"/>
<xsd:element ref="doc"/>
</xsd:choice>
</xsd:group>

<xsd:annotation>
<xsd:documentation>
=====================================================================

Document elements
Comment: All document elements share just two content models
Pattern: Consistent Element Set
Reference: http://www.xmlpatterns.com/ConsistentElementSetMain.shtml

=====================================================================
</xsd:documentation>
</xsd:annotation>

<xsd:complexType name="akomaNtosoType">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>akomaNtosoType</name>
<comment>
the complex type akomaNtosoType is the type for the root element in Akoma Ntoso..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence>
<xsd:sequence>
<xsd:group ref="documentType"/>
</xsd:sequence>
<xsd:element ref="components" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>

<xsd:element name="akomaNtoso" type="akomaNtosoType">
<xsd:annotation>
<xsd:documentation>
<type>Element (root)</type>
<name>akomaNtoso</name>
<comment>
NAME
akomaNtoso
the element akomaNtoso is the root element of all document types in Akoma Ntoso. It follows the pattern Universal Root (http://www.xmlpatterns.com/UniversalRootMain.shtml).
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:complexType name="openStructure">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>openStructure</name>
<comment>
the type openStructure specifies the overall content model of all the document types that do not have a specific and peculiar structure.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence>
<xsd:element ref="meta"/>
<xsd:element ref="coverPage" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="preface" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="preamble" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="mainBody"/>
<xsd:element ref="conclusions" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="attachments" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="components" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attributeGroup ref="contains"/>
</xsd:complexType>

<xsd:element name="doc" type="openStructure">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>doc</name>
<comment>
Element doc is used for describing the structure and content of any other document that is not included in the list of document explicitly managed by Akoma Ntoso.
</comment>
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="eId-doc">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@eId"/>
</xsd:unique>
<xsd:unique name="GUID-doc">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@GUID"/>
</xsd:unique>
</xsd:element>

<xsd:element name="mainBody" type="maincontent">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>mainBody</name>
<comment>
the element mainBody is the container of the main part of all other document types.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="statement" type="openStructure">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>statement</name>
<comment>
Element statement is used for describing the structure and content of an official document of a body that may or may not be normative in structure (e.g., statements, resolutions, etc.)..
</comment>
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="eId-statement">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@eId"/>
</xsd:unique>
<xsd:unique name="GUID-statement">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@GUID"/>
</xsd:unique>
</xsd:element>

<xsd:element name="components">
<xsd:complexType>
<xsd:sequence minOccurs="1" maxOccurs="unbounded">
<xsd:element ref="component"/>
</xsd:sequence>
<xsd:attributeGroup ref="idreq"/>
</xsd:complexType>
</xsd:element>

<xsd:element name="component" type="docContainerType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>component</name>
<comment>
The element component is a container of a subdocument specified in a composite document.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:complexType name="collectionStructure">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>collectionStructure</name>
<comment>
the type collectionStructure specifies the overall content model of the document types that are collections of other documents.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence>
<xsd:element ref="meta"/>
<xsd:element ref="coverPage" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="preface" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="preamble" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="collectionBody"/>
<xsd:element ref="conclusions" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="attachments" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="components" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attributeGroup ref="contains"/>
</xsd:complexType>

<xsd:element name="amendmentList" type="collectionStructure">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>amendmentList</name>
<comment>
Element amendmentList is used for describing the structure and content of a collection of amendments.
</comment>
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="eId-amendmentList">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@eId"/>
</xsd:unique>
<xsd:unique name="GUID-amendmentList">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@GUID"/>
</xsd:unique>
</xsd:element>

<xsd:element name="officialGazette" type="collectionStructure">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>officialGazette</name>
<comment>
Element officialGazette is used for describing the structure and content of an issue of an official gazette.
</comment>
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="eId-officialGazette">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@eId"/>
</xsd:unique>
<xsd:unique name="GUID-officialGazette">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@GUID"/>
</xsd:unique>
</xsd:element>

<xsd:element name="documentCollection" type="collectionStructure">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>documentCollection</name>
<comment>
Element documentCollection is used for describing the structure and content of a collection of other documents chosen and combined for any reason whatsoever.
</comment>
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="eId-documentCollection">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@eId"/>
</xsd:unique>
<xsd:unique name="GUID-documentCollection">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@GUID"/>
</xsd:unique>
</xsd:element>

<xsd:complexType name="collectionBodyType">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>collectionBodyType</name>
<comment>
the type collectionBodyType specifies a content model of a container of a list of other documents (e.g, acts, bills, amendments, etc.) possibly interspersed with interstitial elements with content that does not form an individual document.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence>
<xsd:element ref="component" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="coreopt"/>
</xsd:complexType>

<xsd:element name="collectionBody" type="collectionBodyType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>collectionBody</name>
<comment>
the element collectionBody is the container of a list of other documents (e.g, acts, bills, amendments, etc.) possibly interspersed with interstitial elements with content that does not form an individual document.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:complexType name="portionStructure">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>portionStructure</name>
<comment>
the type portionStructure specifies the overall content model of the document type that is a portion of another document.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence>
<xsd:element ref="meta"/>
<xsd:element ref="portionBody"/>
</xsd:sequence>
<xsd:attributeGroup ref="portionAtt"/>
</xsd:complexType>

<xsd:element name="portion" type="portionStructure">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>portion</name>
<comment>
Element portion is used for describing the structure and content of an independent portion of a document.
</comment>
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="eId-portion">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@eId"/>
</xsd:unique>
<xsd:unique name="GUID-portion">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@GUID"/>
</xsd:unique>
</xsd:element>

<xsd:complexType name="portionBodyType">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>portionBodyType</name>
<comment>
the type portionBodyType specifies a content model of a container of a portion of another document.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice>
<xsd:group ref="containerElements"/>
<xsd:group ref="hierElements"/>
<xsd:group ref="ANcontainers"/>
<xsd:element ref="recitals"/>
<xsd:element ref="recital"/>
<xsd:element ref="citations"/>
<xsd:element ref="citation"/>
<xsd:element ref="longTitle"/>
<xsd:element ref="formula"/>
<xsd:element ref="coverPage"/>
<xsd:element ref="preface"/>
<xsd:element ref="preamble"/>
</xsd:choice>
<xsd:attributeGroup ref="coreopt"/>
</xsd:complexType>

<xsd:element name="portionBody" type="portionBodyType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>portionBody</name>
<comment>
the element portionBody is the container of a portion of another document.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:complexType name="hierarchicalStructure">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>hierarchicalStructure</name>
<comment>
the type hierarchicalStructure specifies the overall content model of the document types that are hierarchical in nature, especially acts and bills.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence>
<xsd:element ref="meta"/>
<xsd:element ref="coverPage" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="preface" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="preamble" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="body"/>
<xsd:element ref="conclusions" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="attachments" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="components" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attributeGroup ref="contains"/>
</xsd:complexType>

<xsd:element name="act" type="hierarchicalStructure">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>act</name>
<comment>
Element act is used for describing the structure and content of an act.
</comment>
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="eId-act">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@eId"/>
</xsd:unique>
<xsd:unique name="GUID-act">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@GUID"/>
</xsd:unique>
</xsd:element>

<xsd:element name="bill" type="hierarchicalStructure">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>bill</name>
<comment>
Element bill is used for describing the structure and content of a bill.
</comment>
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="eId-bill">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@eId"/>
</xsd:unique>
<xsd:unique name="GUID-bill">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@GUID"/>
</xsd:unique>
</xsd:element>

<xsd:complexType name="bodyType">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>bodyType</name>
<comment>
the type bodyType specifies a content model of the main hierarchy of a hierarchical document (e.g, an act or a bill).
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice minOccurs="1" maxOccurs="unbounded">
<xsd:element ref="componentRef"/>
<xsd:group ref="hierElements"/>
</xsd:choice>
<xsd:attributeGroup ref="coreopt"/>
</xsd:complexType>

<xsd:element name="body" type="bodyType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>body</name>
<comment>
the element body is the container of the main hierarchy of a hierarchical document (e.g, an act or a bill).
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:complexType name="debateStructure">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>debateStructure</name>
<comment>
the type debateStructure specifies the overall content model of the document types that describe debates.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence>
<xsd:element ref="meta"/>
<xsd:element ref="coverPage" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="preface" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="debateBody"/>
<xsd:element ref="conclusions" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="attachments" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="components" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attributeGroup ref="contains"/>
</xsd:complexType>

<xsd:element name="debateReport" type="openStructure">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>debateReport</name>
<comment>
Element debateReport is used for describing the structure and content of a report.
</comment>
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="eId-debateReport">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@eId"/>
</xsd:unique>
<xsd:unique name="GUID-debateReport">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@GUID"/>
</xsd:unique>
</xsd:element>

<xsd:element name="debate" type="debateStructure">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>debate</name>
<comment>
Element debate is used for describing the structure and content of a debate record.
</comment>
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="eId-debate">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@eId"/>
</xsd:unique>
<xsd:unique name="GUID-debate">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@GUID"/>
</xsd:unique>
</xsd:element>

<xsd:complexType name="debateBodyType">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>debateBodyType</name>
<comment>
the type debateBodyType specifies a content model of the main hierarchy of a debate.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence minOccurs="1" maxOccurs="unbounded">
<xsd:group ref="speechSection"/>
</xsd:sequence>
<xsd:attributeGroup ref="coreopt"/>
</xsd:complexType>

<xsd:element name="debateBody" type="debateBodyType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>debateBody</name>
<comment>
the element debateBody is the container of the main hierarchy of a debate.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:complexType name="judgmentStructure">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>judgmentStructure</name>
<comment>
the type judgmentStructure specifies the overall content model of the document types that describe judgments.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence>
<xsd:element ref="meta"/>
<xsd:element ref="coverPage" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="header"/>
<xsd:element ref="judgmentBody"/>
<xsd:element ref="conclusions" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="attachments" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="components" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attributeGroup ref="contains"/>
</xsd:complexType>

<xsd:element name="judgment" type="judgmentStructure">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>judgment</name>
<comment>
Element judgment is used for describing the structure and content of a judgment.
</comment>
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="eId-judgment">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@eId"/>
</xsd:unique>
<xsd:unique name="GUID-judgment">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@GUID"/>
</xsd:unique>
</xsd:element>

<xsd:complexType name="judgmentBodyType">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>judgmentBodyType</name>
<comment>
the type judgmentBodyType specifies a content model of the main hierarchy of a judgment document.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence minOccurs="1" maxOccurs="unbounded">
<xsd:group ref="judgmentBlock"/>
</xsd:sequence>
<xsd:attributeGroup ref="coreopt"/>
</xsd:complexType>

<xsd:element name="judgmentBody" type="judgmentBodyType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>judgmentBody</name>
<comment>
the element judgmentBody is the container of the main hierarchy of a judgment document.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:complexType name="amendmentStructure">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>amendmentStructure</name>
<comment>
the type amendmentStructure specifies the overall content model of the document types that describe amendments.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence>
<xsd:element ref="meta"/>
<xsd:element ref="coverPage" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="preface" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="amendmentBody"/>
<xsd:element ref="conclusions" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="attachments" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="components" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attributeGroup ref="contains"/>
</xsd:complexType>

<xsd:element name="amendment" type="amendmentStructure">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>amendment</name>
<comment>
Element amendment is used for describing the structure and content of an amendment.
</comment>
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="eId-amendment">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@eId"/>
</xsd:unique>
<xsd:unique name="GUID-amendment">
<xsd:selector xpath=".//*"/>
<xsd:field xpath="@GUID"/>
</xsd:unique>
</xsd:element>

<xsd:complexType name="amendmentBodyType">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>amendmentBodyType</name>
<comment>
the type amendmentBodyType specifies a content model of the main hierarchy of a amendment document.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:sequence minOccurs="1" maxOccurs="unbounded">
<xsd:group ref="amendmentBlock"/>
</xsd:sequence>
<xsd:attributeGroup ref="coreopt"/>
</xsd:complexType>

<xsd:element name="amendmentBody" type="amendmentBodyType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>amendmentBody</name>
<comment>
the element amendmentBody is the container of the main hierarchy of a amendment document.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:complexType name="recitalHierarchy">


<xsd:complexContent>
<xsd:extension base="basehierarchy">
<xsd:sequence>
<xsd:element ref="intro" minOccurs="0" maxOccurs="1"/>
<xsd:choice minOccurs="1" maxOccurs="unbounded">
<xsd:element ref="componentRef"/>
<xsd:element ref="recital"/>
</xsd:choice>
<xsd:element ref="wrapUp" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attributeGroup ref="corereq"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

<xsd:element name="recitals" type="recitalHierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>recitals</name>
<comment>
the element recitals is the section of the preamble that contains recitals.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="recital" type="itemType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>recital</name>
<comment>
the element recital is the individual element of the preface that is called recital.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:complexType name="citationHierarchy">


<xsd:complexContent>
<xsd:extension base="basehierarchy">
<xsd:sequence>
<xsd:element ref="intro" minOccurs="0" maxOccurs="1"/>
<xsd:choice minOccurs="1" maxOccurs="unbounded">
<xsd:element ref="componentRef"/>
<xsd:element ref="citation"/>
</xsd:choice>
<xsd:element ref="wrapUp" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attributeGroup ref="corereq"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

<xsd:element name="citations" type="citationHierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>citations</name>
<comment>
the element citations is the section of the preamble that contains citations.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="citation" type="itemType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>citation</name>
<comment>
the element citation is the individual element of the preface that is called citation.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="longTitle" type="blocksreq">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>longTitle</name>
<comment>
the element longTitle is the section of the preface or coverPage that is called long title.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="formula">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>formula</name>
<comment>
the element formula is a section of the preface or preamble that contains a formulaic expression that is systematically or frequently present in a preface or a preamble and has e precise legal meaning (e.g. an enacting formula). Use the refersTo attribute for the specification of the actual type of formula..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="blocksreq">
<xsd:attributeGroup ref="name"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>

<xsd:complexType name="basicopt">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>basicopt</name>
<comment>
the complex type basicopt defines the content model and attributes used by basic containers such as coverPage and conclusions. Here the eId attribute is optional.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice minOccurs="1" maxOccurs="unbounded">
<xsd:group ref="blockElements"/>
<xsd:group ref="basicContainers"/>
</xsd:choice>
<xsd:attributeGroup ref="coreopt"/>
</xsd:complexType>

<xsd:element name="coverPage" type="basicopt">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>coverPage</name>
<comment>
the element coverPage is used as a container of the text that acts as a cover page.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:complexType name="preambleopt">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>preambleopt</name>
<comment>
the complex type preambleopt defines the content model and attributes used by preambles. Here the eId attribute is optional.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice minOccurs="1" maxOccurs="unbounded">
<xsd:group ref="blockElements"/>
<xsd:group ref="preambleContainers"/>
</xsd:choice>
<xsd:attributeGroup ref="coreopt"/>
</xsd:complexType>

<xsd:element name="preamble" type="preambleopt">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>preamble</name>
<comment>
the element preamble is used as a container of the text that opens the main body of the document as a preamble.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:complexType name="prefaceopt">
<xsd:annotation>
<xsd:documentation>
<type>Complex</type>
<name>prefaceopt</name>
<comment>
the complex type prefaceopt defines the content model and attributes used by preface. Here the eId attribute is optional.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:choice minOccurs="1" maxOccurs="unbounded">
<xsd:group ref="blockElements"/>
<xsd:group ref="prefaceContainers"/>
</xsd:choice>
<xsd:attributeGroup ref="coreopt"/>
</xsd:complexType>

<xsd:element name="preface" type="prefaceopt">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>preface</name>
<comment>
the element preface is used as a container of all prefacing material (e.g. headers, formulas, etc.).
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="conclusions" type="basicopt">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>conclusions</name>
<comment>
the element conclusion is used as a container of all concluding material (e.g. dates, signatures, formulas, etc.).
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="header" type="blocksopt">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>header</name>
<comment>
the element header is used as a container of all prefacing material of judgments (e.g. headers, formulas, etc.).
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="attachments">
<xsd:complexType>
<xsd:sequence minOccurs="1" maxOccurs="unbounded">
<xsd:element ref="attachment"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

<xsd:element name="attachment" type="docContainerType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>attachment</name>
<comment>
the element attachment is used as a container of individual attachment elements.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="interstitial" type="blocksreq">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>interstitial</name>
<comment>
the element interstitial is used as a container of text elements and blocks that are placed for any reason between individual documents in a collection of documents.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="componentRef" type="srcType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>componentRef</name>
<comment>
the element componentRef is a reference to a separate manifestation-level resource that holds the content of the component of the document not physically placed at the position specified. Actual resources can either be external (e.g. in the package or even in a different position) or internal (within the components element).
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="documentRef" type="linkType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>documentRef</name>
<comment>
the element documentRef is a reference to a separate work- or expression-level resource that should be placed in this position. Actual resources are external (e.g. in the package or even in a different position) and are (an expression or any expression of) a separate Work..
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:annotation>
<xsd:documentation>
=====================================================================

Elements for hierarchical documents

=====================================================================
</xsd:documentation>
</xsd:annotation>

<xsd:element name="section" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>section</name>
<comment>
this element is a hierarchical container called "section" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="part" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>part</name>
<comment>
this element is a hierarchical container called "part" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="paragraph" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>paragraph</name>
<comment>
this element is a hierarchical container called "paragraph" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="chapter">
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="hierarchy">
<xsd:assert test="every $x in (*) satisfies $x = (num | heading | section | article)"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>


<xsd:element name="title" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>title</name>
<comment>
this element is a hierarchical container called "title" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="book" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>book</name>
<comment>
this element is a hierarchical container called "book" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="tome" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>tome</name>
<comment>
this element is a hierarchical container called "tome" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="article" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>article</name>
<comment>
this element is a hierarchical container called "article" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="division" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>division</name>
<comment>
this element is a hierarchical container called "division" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="list" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>list</name>
<comment>
this element is a hierarchical container called "list" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="clause" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>clause</name>
<comment>
this element is a hierarchical container called "clause" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="point" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>point</name>
<comment>
this element is a hierarchical container called "point" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="indent" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>indent</name>
<comment>
this element is a hierarchical container called "indent" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="alinea" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>alinea</name>
<comment>
this element is a hierarchical container called "alinea" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="rule" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>rule</name>
<comment>
this element is a hierarchical container called "rule" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="subrule" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>subrule</name>
<comment>
this element is a hierarchical container called "subrule" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="proviso" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>proviso</name>
<comment>
this element is a hierarchical container called "proviso" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="subsection" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>subsection</name>
<comment>
this element is a hierarchical container called "subsection" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="subpart" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>subpart</name>
<comment>
this element is a hierarchical container called "subpart" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="subparagraph" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>subparagraph</name>
<comment>
this element is a hierarchical container called "subparagraph" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="subchapter" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>subchapter</name>
<comment>
this element is a hierarchical container called "subchapter" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="subtitle" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>subtitle</name>
<comment>
this element is a hierarchical container called "subtitle" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="subdivision" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>subdivision</name>
<comment>
this element is a hierarchical container called "subdivision" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="subclause" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>subclause</name>
<comment>
this element is a hierarchical container called "subclause" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="sublist" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>sublist</name>
<comment>
this element is a hierarchical container called "sublist" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="level" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>level</name>
<comment>
this element is a hierarchical container called "level" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="transitional" type="hierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>transitional</name>
<comment>
this element is a hierarchical container called "transitional" either explicitly or due to the local tradition.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="content" type="blocksreq">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>content</name>
<comment>
the element content is the final container in a hierarchy, and is where the blocks of text of the content of the structure are finally specified.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="num" type="inline">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>num</name>
<comment>
the element num is a heading element in a hierarchy that contains a number or any other ordered mechanism to identify the structure..
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="heading" type="inlinereq">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>heading</name>
<comment>
the element heading is a heading element in a hierarchy that contains a title or any other textual content to describe the structure..
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="subheading" type="inlinereq">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>subheading</name>
<comment>
the element subheading is a heading element in a hierarchy that contains a subtitle or any other textual content to further describe the structure..
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="crossHeading" type="inlinereq">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>crossHeading</name>
<comment>
the element crossHeading is a heading element that is placed side by side with hierarchical containers ..
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="intro" type="blocksreq">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>intro</name>
<comment>
the element intro is a heading element in a hierarchy that contains paragraphs introducing one or more lower hierarchical elements..
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="wrapUp" type="blocksreq">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>wrapUp</name>
<comment>
the element wrapUp is a concluding element in a hierarchy that contains paragraphs wrapping up the preceding lower hierarchical elements..
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:annotation>
<xsd:documentation>
=====================================================================

Elements for debates documents

=====================================================================
</xsd:documentation>
</xsd:annotation>

<xsd:element name="administrationOfOath" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>administrationOfOath</name>
<comment>
this element is a structural container for parts of a debates that contain the administration of an oath.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="rollCall" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>rollCall</name>
<comment>
this element is a structural container for parts of a debates that contain a roll call of individuals.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="prayers" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>prayers</name>
<comment>
this element is a structural container for parts of a debates that contain prayers.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="oralStatements" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>oralStatements</name>
<comment>
this element is a structural container for parts of a debates that contain oral statements by participants.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="writtenStatements" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>writtenStatements</name>
<comment>
this element is a structural container for parts of a debates that contain written statements by participants.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="personalStatements" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>personalStatements</name>
<comment>
this element is a structural container for parts of a debates that contain written statements by participants.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="ministerialStatements" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>ministerialStatements</name>
<comment>
this element is a structural container for parts of a debates that contain written statements by participants.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="resolutions" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>resolutions</name>
<comment>
this element is a structural container for parts of a debates that contain resolutions.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="nationalInterest" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>nationalInterest</name>
<comment>
this element is a structural container for parts of a debates that contain resolutions.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="declarationOfVote" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>declarationOfVote</name>
<comment>
this element is a structural container for parts of a debates that are relevant to the declaration of votes.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="communication" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>communication</name>
<comment>
this element is a structural container for parts of a debates that contain communications from the house.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="petitions" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>petitions</name>
<comment>
this element is a structural container for parts of a debates that are relevant to petitions.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="papers" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>papers</name>
<comment>
this element is a structural container for parts of a debates that are relevant to the display of papers.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="noticesOfMotion" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>noticesOfMotion</name>
<comment>
this element is a structural container for parts of a debates that are relevant to the notices of motions.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="questions" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>questions</name>
<comment>
this element is a structural container for parts of a debates that are relevant to questions.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="address" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>address</name>
<comment>
this element is a structural container for parts of a debates that are relevant to addresses.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="proceduralMotions" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>proceduralMotions</name>
<comment>
this element is a structural container for parts of a debates that are relevant to procedural motions.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="pointOfOrder" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>pointOfOrder</name>
<comment>
this element is a structural container for parts of a debates that are relevant to points of order.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="adjournment" type="althierarchy">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>adjournment</name>
<comment>
this element is a structural container for parts of a debates that contain adjournment notices.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="debateSection">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>debateSection</name>
<comment>
this element is a generic structural container for all other parts of a debates that are not explicitly supported with a named element.
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="althierarchy">
<xsd:attributeGroup ref="name"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>

<xsd:element name="speechGroup">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>speechGroup</name>
<comment>
the element speechGroup is a container of speech elements. This element is meant to pooint out, in a complex sequence of individual speech elements, the main contributor, i.e., the individual speech who was introducedand expected and that is causing the complex sequence that follows. Attributes by, as and to are those of the main speech..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="althierarchy">
<xsd:attributeGroup ref="speechAtts"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>

<xsd:element name="speech" type="speechType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>speech</name>
<comment>
the element speech is a container of a single speech utterance in a debate. Dialogs between speakers need a speech element each.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="question" type="speechType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>question</name>
<comment>
the element question is a container of a single official question as proposed by an MP to a person holding an official position.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="answer" type="speechType">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>answer</name>
<comment>
the element answer is a container of a single official answer to a question.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="other" type="blocksreq">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>other</name>
<comment>
the element other is a container of parts of a debate that are not speeches, nor scene comments (e.g., lists of papers, etc.).
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="scene" type="inline">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>scene</name>
<comment>
the element scene is a container of descriptions of the scene elements happening in a given moment during a debate (e.g., applauses).
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="narrative" type="inline">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>narrative</name>
<comment>
the element narrative is a block element in a debate to mark description in the third person of events taking place in the meeting, e.g. "Mr X. takes the Chair".
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="summary" type="inline">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>summary</name>
<comment>
the element summary is a block element in a debate to mark summaries of speeches that are individually not interesting (e.g.: "Question put and agreed to").
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="from" type="inline">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>from</name>
<comment>
the element from is a heading element in a debate that contains the name or role or a reference to the person doing the speech.
</comment>
</xsd:documentation>
</xsd:annotation>
</xsd:element>



<xsd:element name="vote">
<xsd:annotation>
<xsd:documentation>
<type>Element</type>
<name>vote</name>
<comment>
the element vote is an inline that wraps either the name of the voter (when organized by choice) or the vote (when organized by name) in a voting report..
</comment>
</xsd:documentation>
</xsd:annotation>

<xsd:complexType mixed="true">
<xsd:complexContent>
<xsd:extension base="inline">
<xsd:attributeGroup ref="voteAtts"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>