=====================================================================
Akoma Ntoso main schema
		
Release 30/03/2017 - Akoma Ntoso 3.0 WD17 with errata (6th output)
Complete version.
		
		
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 the licence
specified in the file licence.txt that can also be found at the URL xxxx
		
=====================================================================

=====================================================================
		
Main element groups
		
=====================================================================

=====================================================================
		
Attribute groups
		
=====================================================================

=====================================================================
		
Attribute groups: attribute "type"
		
=====================================================================

=====================================================================
		
Simple types (data values)
		
=====================================================================

=====================================================================
		
Complex types (markup structures)
		
=====================================================================

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

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

=====================================================================
		
Elements for hierarchical documents
		
=====================================================================

=====================================================================
		
Elements for debates documents
		
=====================================================================

=====================================================================
		
AN block elements
Comment: the only AN-specific block are the table of content (TOC),
a structure containing toc items related to the various subparts of the
main document, the list item and the titled block
		
=====================================================================

=====================================================================
		
AN marker elements
Comment: AN-specific marker elements are connected to the
identification of locations within the legal structure, anywhere where
there is text.
		
=====================================================================

=====================================================================
		
AN subFlow elements
Comment: AN-specific subFlow elements are connected to the
identification of structural elements that contain full structures
within a text content, but are not of textual nature.
		
=====================================================================

=====================================================================
		
Generic elements
Comment: All elements in this schema fall under one of five
content models: hierarchical container, container, block, inline
and mark. Besides named elements, the schema also provides for a
generic element for each of them, that can be used for markup that
fits the content models but can be specified by a precise name that
is not used in this schema. The 'name' attribute must be used for
naming the element.
It is also a characteristic of this schema that all named elements
are equivalent, and can be substituted to, the corresponding generic
element with their name as the value of the name attribute. Thus, by
definition, <p>  = <block name="p"> , <part>  = <hcontainer name="part"> ,
<act>  = <container name="act"> , etc.
Pattern: Generic Document + Role Attribute
Reference: http://www.xmlpatterns.com/GenericDocumentMain.shtml +
http://www.xmlpatterns.com/RoleAttributeMain.shtml
		
=====================================================================