How the CICS assistants comply with the XML schema specification.
The CICS® assistants conditionally comply with the XML Schema and support the Schema with certain restrictions.
Note that the CICS assistants
perform limited runtime validation on your XML. To enable full validation,
see:
Supported features
| XML language feature | Support from the CICS assistants |
|---|---|
| Complex type definition | The CICS assistants support complex type definitions. |
| Elements | The CICS assistants support XML elements. |
| Attribute declarations | The CICS assistants support attribute declarations. For more information, see: |
| Simple types | The CICS assistants support simple types. For information on how simple types are mapped from XML to a high-level language, or vice versa, see: |
| Facets | The CICS assistants
support most facets for simple data types. The pattern facet
is ignored, and the enumeration facet is used during CICS processing but is not validated
at runtime.
|
| Content models | The CICS assistants support most content models with certain limitations. For more information, see: |
| Attribute groups | The CICS assistants support attribute groups. |
| Nil values | The CICS assistants support nil values. For more information, see |
| Target namespaces and unqualified locals | The CICS assistants support namespaces. However; for performance reasons, CICS does not always check the namespaces when parsing XML. The CICS assistants support both qualified and unqualified local elements and anonymous types. |
| Global and local declarations | The CICS assistants support both global and local declarations. |
| Combining schemas | The CICS assistants
support the use of the <xsd:import> and <xsd:include> elements
to combine schemas. Any referenced documents must specify the correct encoding, such as EBCIDIC-CP-US, in the prolog of the XML document. Use <xsd:include> for schemas in the same namespace. Use <xsd:import> for schemas in different namespaces. |
| Deriving complex and simple types | The CICS assistants support derivation of data-types by extension and restriction. |
| Using derived types in instance documents | The CICS assistants support run time derivation only if the data type is abstract. |
| Redefining types and groups | The CICS assistants support redefining types and groups. |
| Substitution groups | The CICS assistants support substitution groups. For more information, see: |
| Abstract elements and types | The CICS assistants support abstract elements and abstract data types. For more information, see: |
| Any element | The CICS assistants
support <xsd:any> and xsd:anyType with some limitations.
For more information, see:
|
Tolerated features
| XML language feature | Support from the CICS assistants |
|---|---|
| Annotations | CICS ignores annotations except those that have been added by the CICS assistants to preserve consistency when using reverse mappings. |
| Undeclared target namespaces | The CICS assistants tolerate undeclared target namespaces. However, you are recommended to provide a target namespace in your XML schemas. |
| Any attribute | The CICS assistants tolerate the use of <xsd:anyAttribute>, ignoring it during processing of XML. |
Unsupported features
| XML language feature | Support from the CICS assistants |
|---|---|
| Recursion | The CICS assistants
do not support recursion. Defining an element or type in terms of itself will result in an error message; typically DFHPI9024E. |