Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Service Development Help | Properties | Schema Component Properties | Any Element Declaration
 
Any Element Declaration
An any element declaration in XML Schema is a wildcard declaration used as a placeholder for one or more undeclared elements in an instance document. The element that corresponds to the wildcard declaration in the instance document is called the matching element. In a DTD, an element declared to be of type ANY can contain any well-formed XML. This symbol corresponds to an <any> element declaration in an XML Schema and an element declared to be of type ANY in a DTD.
Because an <any> element declaration does not have a name, the schema uses 'Any' as the name of the element.
This field...
Specifies...
Min Occurs
The minimum number of occurrences for the matching element in the instance document.
Max Occurs
The maximum number of occurrences for the matching element in the instance document.
Process Contents
The validation constraints placed on the matching element in the instance document. The value of Process Contents equals the value of the processContents attribute in the <any> declaration. This field can have one of the following values:
*strict specifies that Integration Server must validate the matching element against a global declaration in a schema belonging to one of the allowed namespaces. If Integration Server cannot find one of the XML components, it generates a validation error. The Process Contents value is strict when the processContents attribute is absent or is set to "strict" in the <any> declaration. This is the default value.
*skip specifies that the matching element must be well-formed XML. Integration Server does not need to make sure the matching element is schema-valid. The Process Contents value equals skip when processContents="skip" in the <any> declaration.
*lax specifies that when Integration Server encounters the matching element in the instance document, it should (if possible) validate the matching element against the corresponding global declaration in a schema from an allowed namespace. However, if Integration Server cannot find the schema in the namespace, no error occurs. The Process Contents value equals lax when processContents="lax" in the <any> declaration.
Qualifier
Whether the matching element can or cannot be from one of the namespaces listed in the URIs field.
The namespace attribute value in the <any> declaration determines the value of Qualifier. See the following.
Namespace value
Qualifier value
Description
##any
any
Specifies that the matching element can be from any namespace.
##local
specific
Specifies that the matching element must belong to a namespace.
##other
not
Specifies that the matching element must be from a namespace other than the namespaces listed in the URIs field.
##targetNamespace
specific
Specifies that the matching element must be from the namespace listed in the URIs field
"URI1 URI2"
specific
Specifies that the matching element must be from one of the namespaces listed in the URIs field.
URIs
The namespaces to which the matching element can or cannot belong. The namespace attribute value in the <any> declaration determines the value of URIs. See the following.
Namespace value
URIs
any
blank. If the namespace attribute does not appear in the <any> declaration, ##any is used.
##local
"unqualified"
##other
target namespace and "unqualified"
##targetNamespace
target namespace
"URI1 URI2"
Specified by the namespace attribute in the <any> declaration.