Table of Contents

Search

  1. Preface
  2. Introduction to Data Transformation
  3. Data Processor Transformation
  4. Wizard Input and Output Formats
  5. Relational Input and Output
  6. Using the IntelliScript Editor
  7. XMap
  8. Libraries
  9. Schema Object
  10. Command Line Interface
  11. Scripts
  12. Parsers
  13. Script Ports
  14. Document Processors
  15. Formats
  16. Data Holders
  17. Anchors
  18. Transformers
  19. Actions
  20. Serializers
  21. Mappers
  22. Locators, Keys, and Indexing
  23. Streamers
  24. Validators, Notifications, and Failure Handling
  25. Validation Rules
  26. Custom Script Components

Role of Schemas in Serialization and Mapping

Role of Schemas in Serialization and Mapping

A serializer or mapper checks that its input is valid according to the XML schema. There are two validation modes:
  • Partial validation. Some deviations are allowed between the XML source document and the schema. Default.
  • Strict validation. The XML source document must conform strictly to its schema.
To define the validation level, assign the
validate_source_document
property of the
Serializer
or
Mapper
component.
If you use the strict mode, a validation error causes the serializer or mapper to fail. The
Events
view displays the errors.
If you use the partial mode, the transformation might proceed despite certain validation errors. For example, if there are more occurrences of an element than the schema permits, a serializer typically ignores the excess elements and processes the valid ones, and it writes a warning in the event log. Similarly, it might ignore an element containing an invalid data type.
The Script uses the Xerces C XML Parser, version 3.1, to perform validation.


Updated February 12, 2020