Problems in 2.0.1, Fixed in 2.1:

- Expanding parameter entities should always surround them with spaces, as per
  4.4.8 in the XML specifications
- Fixes various issues when validating documents
- EA03-006: Setting attribute for an element not added to the tree results in
  a Constraint_Error (Workaround: disable shared strings in dom-core.ads)
- Validating a not well-formed document results in an validation error instead
  of a well-formedness error. It is therefore harder to understand such error
  messages
- E908-010: importing the same schema twice generates an error
- E908-011: incorrect handling of elementFormDefault, when the child node
  belongs to a namespace different than the parent's namespace
- E908-011: incorrect handling of elementFormDefault when a schema included
  with <include> has a setup different than the including file
- Attributes normalization done even if the attribute's type is CDATA. However,
  according to 3.3.3 in the XML standard, space sequences should be left untouched
  in such a case

Problems in 2.0:

- E307-011: Invalid project file for xmlada_schema.gpr when installing static
  libraries

Problems fixed in 2.0

- DB25-005 Incorrect value returned by DOM.Attributes.Owner_Element
- D714-002 Attribute quotes are no longer present in a processing-instruction
  data, in SAX or DOM
- Constraint_Error raised when an external entity doesn't reference an
  existing file
- D213-012: Constraint_Error when using the same parser twice
- SAX: End_Document() is called even in case of a fatal error
- DOM: There is now initially a single Text node per block of text, as required
  by DOM specifications
- DOM: Missing function DOM.Core.Nodes.Node_Type added
- CC01-006: In some cases, the handling of entities like &amp; results in
  duplicates when getting the Node_Value through DOM
- CC01-002: Handling of big files (multi-mega bytes) was generating a
  Storage_Error in Direct_IO.