Schema Component Properties

In the schema editor, you can view the contents of an IS schema and details about each component in the schema. When you select a component in the Schema Browser (the left side of the schema editor), Designer displays detailed information in the Component Details (the right side of the schema editor). The information contained in Component Details varies with the selected component.

All Content Model

An all content model specifies that child elements can appear once, or not at all, and in any order in the instance document. This symbol corresponds to the <all> compositor in an XML Schema definition.

This field... Specifies...
Min Occurs The minimum number of occurrences of the content model for an element in the instance document. The value of Min Occurs is equal to the value of the minOccurs attribute in the <all> content model
Max Occurs The maximum number of occurrences of the content model for an element in the instance document. The value of Max Occurs is equal to the value of the maxOccurs attribute in the <all> content model.
Summary of Children The name and occurrence constraints for the child elements in the content model.
  • Name. The name of the child element.
  • Min, Max. The minimum and maximum occurrence constraints for the child element. The Min and Max values correspond to the minOccurs and maxOccurs attributes (respectively) in the local element declaration.

Any Attribute Declaration

An any attribute declaration is a wildcard declaration used as a placeholder for undeclared attributes in an instance document. This symbol corresponds to the <anyAttribute> declaration in an XML Schema. The attribute that corresponds to the wildcard declaration in the instance document is called the matching attribute.

Because an <anyAttribute> declaration does not specify an attribute name, the schema uses 'Any' as the name of the attribute.

This field... Specifies...
Process Contents The validation constraints placed on the matching attribute in the instance document. The value of Process Contents equals the value of the processContents attribute in the <anyAttribute> declaration. This field can have one of the following values:
  • strict specifies that Integration Server must validate the matching attribute 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 <anyAttribute> declaration. This is the default value.
  • skip specifies that the matching attribute must be well-formed XML. Integration Server does not need to make sure the matching element or attribute is schema-valid. The Process Contents value is skip when processContents="skip" in the <anyAttribute> declaration.
  • lax specifies that when Integration Server encounters the matching attribute in the instance document, it should (if possible) validate the matching attribute 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 is lax when processContents="lax" in the <anyAttribute> declaration.
Qualifier Whether the matching attribute can or cannot be from one of the namespaces listed in the URIs field.

The namespace attribute value in the <anyAttribute> declaration determines the value of Qualifier. See the following.

  Namespace value Qualifier value Description
  ##any

any

Specifies that the matching attribute can be from any namespace.
 

##local

specific

Specifies that the matching attribute must belong to a namespace

 

##targetNamespace

specific

Specifies that the matching attribute must be from the namespace listed in the URIs field.

 

##other

not

Specifies that the matching attribute must be from a namespace other than the namespaces listed in the URIs field.

 

"URI1 URI2"

specific

Specifies that the matching attribute must be from one of the namespaces listed in the URIs field.

URIs The namespaces to which the matching attribute can or cannot belong. The namespace attribute value in the <anyAttribute> declaration determines the value of URIs. See the following.
  Namespace value URIs
  any blank. If the namespace attribute does not appear in the attribute declaration, ##any is used.
  ##local "unqualified"
  ##other target namespace and "unqualified"
  ##targetNamespace target namespace
  "URI1 URI2" Specified by the namespace attribute in the <anyAttribute> 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.

Attribute Declaration

An attribute declaration associates an attribute name with a simple type definition. This symbol corresponds to the XML Schema <attribute> declaration or the attribute in a DTD ATTLIST declaration.

An attribute declaration can specify a default value, a fixed value, and whether the appearance of the attribute in the instance document is required. Like element declarations, attribute declarations can be global or local.

This field... Specifies...
Name The local name and target namespace of the attribute declaration. The Name value is equal to the expanded value (prefix plus local name) of the name attribute in the attribute declaration.
Default The default value for the attribute in an instance document. The Default value is equal to the value of the default attribute in the attribute declaration. During data validation, Integration Server supplies the instance document with an attribute whose value equals that of Default if:
  • The element to which the attribute is assigned appears in the instance document, and
  • The attribute itself does not appear.

If the element to which the attribute declaration is assigned does not appear in the instance document, Integration Server does not augment the instance document.

Note: During data validation, Integration Server applies the Default value for an attribute declaration differently than the Default value for an element declaration. For attributes, Integration Server supplies the instance document with an attribute with the Default value when the attribute does not appear in the instance document. For elements, Integration Server supplies the instance document with an element equal to the Default value only if the element appears in the instance document, but has no content.
Fixed Value The fixed value for the attribute. The Fixed Value is equal to the value of the fixed attribute in the attribute declaration. If this attribute appears in an instance document, the attribute value must equal the Fixed Value. During data validation, Integration Server supplies the instance document with an attribute whose value equals Fixed Value if:
  • The element to which the attribute is assigned appears in the instance document, and
  • The attribute itself does not appear in the instance document.
Is Required Whether or not the attribute must appear in an instance document. Is Required is determined by the value of the use attribute in the attribute declaration. This field only appears when you select a local attribute declaration or an attribute reference. The Is Required field can have one of the following values:
  • True specifies that the attribute is required and must appear in the instance document. When the value of Is Required is True, the attribute declaration contains use="required".
  • False specifies that the appearance of the attribute in the instance document is optional; that is, the attribute is not required. When the value of Is Required is False, the attribute declaration or use=“optional” or the use attribute is absent from the declaration.

If an attribute declaration in an XML Schema contains use=”prohibited”, the attribute declaration does not appear in the schema browser. Integration Server does not retain attribute declarations whose use is prohibited.

Simple Type The name and namespace of the simple type definition associated with the attribute. See Simple Type Definition.

Attribute Reference

An attribute reference is a reference from a complex type definition to a globally declared attribute. This symbol corresponds to the ref=”globalAttributeName” attribute in an attribute declaration. DTDs do not have attribute references. Consequently, attribute references do not appear in schemas generated from DTDs.

This field... Specifies...
Name The local name and target namespace of the attribute declaration for this attribute reference. The Name value is equal to the expanded value (prefix plus local name) of the name attribute in the attribute declaration.
Default The default value for the referenced attribute in an instance document. The Default value is equal to the value of the default attribute in the attribute declaration. During data validation, Integration Server supplies the instance document with an attribute whose value equals that of Default if:
  • The element to which the attribute is assigned appears in the instance document, and
  • The attribute itself does not appear.

If the element to which the attribute declaration is assigned does not appear in the instance document, Integration Server does not augment the instance document.

Note: During data validation, Integration Server applies the Default value for an attribute declaration differently than the Default value for an element declaration. For attributes, Integration Server supplies the instance document with an attribute with the Default value when the attribute does not appear in the instance document. For elements, Integration Server supplies the instance document with an element equal to the Default value only if the element appears in the instance document, but has no content.
Fixed Value The fixed value for the referenced attribute. The Fixed Value is equal to the value of the fixed attribute in the attribute declaration. If this attribute appears in an instance document, the attribute value must equal the Fixed Value. During data validation, Integration Server supplies the instance document with an attribute whose value equals Fixed Value if:
  • The element to which the attribute is assigned appears in the instance document, and
  • The attribute itself does not appear in the instance document.
Is Required Whether or not the referenced attribute must appear in an instance document. Is Required is determined by the value of the use attribute in the attribute declaration. This field only appears when you select a local attribute declaration or an attribute reference. The Is Required field can have one of the following values:
  • True specifies that the attribute is required and must appear in the instance document. When the value of Is Required is True, the attribute declaration contains use="required".
  • False specifies that the appearance of the attribute in the instance document is optional; that is, the attribute is not required. When the value of Is Required is False, the attribute declaration or use=“optional” or the use attribute is absent from the declaration.

If an attribute declaration in an XML Schema contains use=”prohibited”, the attribute declaration does not appear in the schema browser. Integration Server does not retain attribute declarations whose use is prohibited.

Simple Type The name and namespace of the simple type definition associated with the referenced attribute. See Simple Type Definition.

Choice Content Model

A choice content model specifies that only one of the child elements in the content model can appear in the instance document. This symbol corresponds to the <choice> compositor in an XML Schema definition or a choice list in a DTD element type declaration.

If one of the child elements does not appear or more than one child element appears, the instance document is not schema-valid. (An exception to this is when the minOccurs attribute for the <choice> element is set to 0. If minOccurs=0, Integration Server does not generate a validation error if no child element appears.)

This field... Specifies...
Min Occurs The minimum number of occurrences of the content model for an element in the instance document. The value of Min Occurs is equal to the value of the minOccurs attribute in the <choice> content model
Max Occurs The maximum number of occurrences of the content model for an element in the instance document. The value of Max Occurs is equal to the value of the maxOccurs attribute in the <choice> content model.
Summary of Children The name and occurrence constraints for the child elements in the content model.
  • Name. The name of the child element.
  • Min, Max. The minimum and maximum occurrence constraints for the child element. The Min and Max values correspond to the minOccurs and maxOccurs attributes (respectively) in the local element declaration.

Complex Type Definition

A complex type definition defines the structure and content for elements of complex type. (Elements of complex type can contain child elements and carry attributes.) This symbol corresponds to the <complexType> element in an XML Schema definition.

If the complex type definition is unnamed (an anonymous type), the Schema Browser displays 'Anonymous' as the name of the complex type definition.

This field... Specifies...
Name The local name and target namespace of the complex type. The Name value is equal to the expanded value (prefix plus local name) of the name attribute in the type definition.

If the Schema Browser displays 'Anonymous' as the name of the simple type, the complex type is an anonymous (unnamed) type defined in an element declaration.

Is Abstract Whether the complex type definition is abstract. The value of Is Abstract corresponds to the abstract attribute in the complex type definition. The Is Abstract field can have one of the following values:
  • True indicates the complex type is abstract. When an element corresponds to an abstract complex type definition, the element in the instance document must contain xsi:type to refer to a complex type derived from the abstract type. When the value of Is Abstract is True, the complex type definition contains abstract="true".
  • False indicates the complex type definition is not abstract. When the value of Is Abstract is False, the abstract attribute is absent from the complex type definition or abstract="false".
Note: If the complex type was created from a simple type, then the Schema Browser also displays the fields for the simple type. For details, see Simple Type Definition.

Element Declaration

An element declaration associates an element name with a type definition. This symbol corresponds to the <element> declaration in an XML Schema and the ELEMENT declaration in a DTD.

An element declaration can contain attributes to specify a default value, a fixed value, and whether the element is abstract or nillable. If an element declaration is part of a content specification, the element declaration can contain attributes to specify occurrence constraints.

This field... Specifies...
Name The local name of the element followed by the namespace to which the element belongs. The Name value is equal to the expanded value (prefix plus local name) of the name attribute in the element declaration.
Default The default value for the element. The Default value is equal to the value of the default attribute in the element declaration.

During data validation, if the element appears in an instance document but contains no content, Integration Server supplies the element with the Default value. If the element does not appear in the instance document, Integration Server does not augment the instance document.

Fixed Value The fixed value for the element. The Fixed Value is equal to the value of the fixed attribute in the element declaration. When Integration Server validates an instance document against the schema, if the element appears, its value must be equal to the Fixed Value.

During data validation, if the element appears in an instance document but contains no content, Integration Server supplies the element with the Fixed Value. If the element does not appear in the instance document, Integration Server does not augment the instance document.

Is Nillable Whether the element can have no content in the instance document. The Is Nillable value is equal to the value of the nillable attribute in the element declaration. The Is Nillable field can have the following values:
  • True indicates that the nil attribute for this element in the instance document can be set to true. (When nil="true", the element has a null value.) When the value of Is Nillable is True, the element declaration in the XML Schema contains nillable="true".
  • False indicates that the nil attribute for the element in an instance document cannot be set to true; that is, the element must contain content. When the value of Is Nillable is False, the element declaration contains nillable="false" or the nillable attribute is absent. This is the default value.
Is Abstract Whether the element is abstract. The Is Abstract value is equal to the value of the abstract attribute in the element declaration. The Is Abstract field can have the following values:
  • True indicates the element is abstract. Abstract element declarations cannot appear in instance documents. Instead, an element in the abstract element’s substitution group must appear in the instance document. When Is Abstract is True, the element declaration contains abstract="true".
  • False indicates the element is not abstract. When the value of Is Abstract is False, the element declaration contains abstract="false" or the abstract attribute is absent. This is the default value.
Complex Type The name and namespace of the complex type assigned to the element. This field appears only if the element is defined to be of complex type. If the element is defined to be of anonymous complex type, this field displays 'Anonymous' as the name of the complex type.

In the Schema Browser, the complex type definition assigned to an element appears as an immediate child of the element.

Simple Type The name and namespace of the simple type assigned to the element. This field appears only if the element is defined to be of simple type. If the element is defined to be of anonymous simple type, this field displays 'Anonymous' as the name of the simple type.

In the Schema Browser, the simple type definition assigned to an element appears as an immediate child of the element.

Min Occurs The minimum number of times this element must appear. The Min Occurs value is equal to the value of the minOccurs attribute in the local element declaration. If the local element declaration does not specify minOccurs, Designer uses a default value of 1.

This field appears only when you select a local element declaration; that is, an element declaration in a complex type definition.

Max Occurs The maximum number of times this element may appear. The Max Occurs value is equal to the value of the maxOccurs attribute in the local element declaration. If the local element declaration does not specify maxOccurs, Designer uses a default value of 1.

This field appears only when you select a local element declaration; that is, an element declaration in a complex type definition.

Element Reference

An element reference is a reference from an element declaration in a content specification to a globally declared element. In a schema generated from an XML Schema, this symbol corresponds to the ref=”globalElementName” attribute in an <element> declaration. In a schema generated from a DTD, this symbol appears next to an element that is a child of another element; that is, the parent element has only element content

This field... Specifies...
Name The local name of the referenced element followed by the namespace to which the referenced element belongs. The Name value is equal to the expanded value (prefix plus local name) of the name attribute in the element declaration.
Default The default value for the referenced element. The Default value is equal to the value of the default attribute in the referenced element declaration.

During data validation, if the element appears in an instance document but contains no content, Integration Server supplies the element with the Default value. If the element does not appear in the instance document, Integration Server does not augment the instance document.

Fixed Value The fixed value for the referenced element. The Fixed Value is equal to the value of the fixed attribute in the element declaration. When Integration Server validates an instance document against the schema, if the element appears, its value must be equal to the Fixed Value.

During data validation, if the element appears in an instance document but contains no content, Integration Server supplies the element with the Fixed Value. If the element does not appear in the instance document, Integration Server does not augment the instance document.

Is Nillable Whether the referenced element can have no content in the instance document. The Is Nillable value is equal to the value of the nillable attribute in the element declaration. The Is Nillable field can have the following values:
  • True indicates that the nil attribute for this element in the instance document can be set to true. (When nil="true", the element has a null value.) When the value of Is Nillable is True, the element declaration in the XML Schema contains nillable="true".
  • False indicates that the nil attribute for the element in an instance document cannot be set to true; that is, the element must contain content. When the value of Is Nillable is False, the element declaration contains nillable="false" or the nillable attribute is absent. This is the default value.
Is Abstract Whether the referenced element is abstract. The Is Abstract value is equal to the value of the abstract attribute in the element declaration. The Is Abstract field can have the following values:
  • True indicates the referenced element is abstract. Abstract element declarations cannot appear in instance documents. Instead, an element in the abstract element’s substitution group must appear in the instance document. When Is Abstract is True, the element declaration contains abstract="true".
  • False indicates the referenced element is not abstract. When the value of Is Abstract is False, the element declaration contains abstract="false" or the abstract attribute is absent. This is the default value.
Complex Type The name and namespace of the complex type assigned to the referenced element. This field appears only if the element is defined to be of complex type. If the element is defined to be of anonymous complex type, this field displays 'Anonymous' as the name of the complex type.

In the Schema Browser, the complex type definition assigned to an element appears as an immediate child of the element.

Simple Type The name and namespace of the simple type assigned to the referenced element. This field appears only if the element is defined to be of simple type. If the element is defined to be of anonymous simple type, this field displays 'Anonymous' as the name of the simple type.

In the Schema Browser, the simple type definition assigned to an element appears as an immediate child of the element.

Min Occurs The minimum number of times this element must appear. The Min Occurs value is equal to the value of the minOccurs attribute in the local element declaration. If the local element declaration does not specify minOccurs, Designer uses a default value of 1.

This field appears only when you select a local element declaration; that is, an element declaration in a complex type definition.

Max Occurs The maximum number of times this element may appear. The Max Occurs value is equal to the value of the maxOccurs attribute in the local element declaration. If the local element declaration does not specify maxOccurs, Designer uses a default value of 1.

This field appears only when you select a local element declaration; that is, an element declaration in a complex type definition.

Empty Content

Empty content occurs in XML Schema definition when an element's associated complex type definition does not contain any element declarations. An element with empty content may still carry attributes. In a DTD, an element has empty content when it is declared to be of type EMPTY.

Mixed Content Model

A mixed content model allows character data to be interspersed with child elements. This symbol corresponds to the mixed=”true” attribute in a complex type definition in an XML Schema definition or a DTD element list in which the first item is #PCDATA.

Sequence Content Model

A sequence content model specifies that the child elements in the instance document must appear in the same order in which they are declared in the content model. This symbol corresponds to the <sequence> compositor in an XML Schema definition or a sequence list in an element type declaration in a DTD.

This field... Specifies...
Min Occurs The minimum number of occurrences of the content model for an element in the instance document. The value of Min Occurs is equal to the value of the minOccurs attribute in the <sequence> content model
Max Occurs The maximum number of occurrences of the content model for an element in the instance document. The value of Max Occurs is equal to the value of the maxOccurs attribute in the <sequence> content model.
Summary of Children The name and occurrence constraints for the child elements in the content model.
  • Name. The name of the child element.
  • Min, Max. The minimum and maximum occurrence constraints for the child element. The Min and Max values correspond to the minOccurs and maxOccurs attributes (respectively) in the local element declaration.

Simple Type Definition

A simple type definition specifies the data type for an element that contains only character data or for an attribute. Unlike complex type definitions, simple type definitions cannot carry attributes. This symbol corresponds to the <simpleType> element in an XML Schema definition.

If the simple type definition is unnamed (an anonymous type), the Schema Browser displays 'Anonymous' as the name of the complex type definition.

This field... Specifies...
Base Constraints The constraining facet values set in the type definitions from which a simple type was derived. Base constraints are the constraining facet values from the primitive type to the immediate parent type. These constraint values represent the cumulative facet values for the simple type.
Simple Type: Name The local name and target namespace of the simple type. The Name value is equal to the expanded value (prefix plus local name) of the name attribute in the type definition. If the Schema Browser displays 'Anonymous' as the name of the simple type, the simple type is an anonymous (unnamed) type defined in an element or attribute declaration.
Primitive Type The primitive datatype from which the simple type is derived.
constraining facet fields The constraining facets applied to a simple type definition. This includes fields for values such as enumeration, length, minlength, maxlength, whitespace, and pattern. Which constraining facets are displayed depends on the primitive type of the simple type definition. A constraining facet field contains a value only if the simple type definition specified a value for the facet. The constraining facets fields do not display facet values set in the type definition from which the simple type was derived.

For more information about constraining facets, see the W3C specification XML Schema Part 2: Datatypes.