XML-20003 to XML-30017

Cause: An expected token was not found in the input data.

Cause: An expected keyword was not found in the input data.

Cause: An expected keyword was not found in the input data.

Cause: Additional text was found after the end-tag of the root element.

Cause: The element declaration was missing the required content model spec. See Production [45] in XML 1.0 2nd Edition.

Cause: The content model in the element declaration was invalid because the content particle requires an element name. See Production [48] in XML 1.0 2nd Edition.

Cause: The target names "XML", "xml", and so on are reserved for standardization in future versions of XML specification. See Production [17] in XML 1.0 2nd Edition.

Cause: The notation name used in the unparsed entity declaration did not match the name in a declared notation [VC: Notation Declared]. See Production [76] in XML 1.0 2nd Edition.

Cause: The attribute type was missing the attribute-list declaration. One of the following types must be added: CDATA, ID, IDREF, IDREFS, ENTITY, ENTITIES, NMTOKEN, or NMTOKENS. See Production [52], [53] in XML 1.0 2nd Edition.

Cause: The required white space was missing.

Cause: An invalid character was used in the entity value. The ampersand, percent, and quote characters (&, %, ", ’) (based on the value delimiters) are invalid. See Production [9] in XML 1.0 2nd Edition.

Cause: A syntax error in comment due to the use of "--". See Production [15] in XML 1.0 2nd Edition.

Cause: "]]>" is not allowed in text. It is used only as an end marker for a CDATA section. See Production [14] in XML 1.0 2nd Edition.

Cause: White space is not allowed in the contentspec before the occurrence indicator. For example, <!ELEMENT x (a,b) *> is not valid. See Production [47], [48] in XML 1.0 2nd Edition.

Cause: Occurrence is not allowed in mixed content declaration. For example, <!ELEMENT x (#PCDATA)?> is not valid. See Production [51] in XML 1.0 2nd Edition.

Cause: Content list is not allowed in mixed-content declaration. For example, <!ELEMENT x (#PCDATA | (a,b))> is not valid. See Production [51] in XML 1.0 2nd Edition.

Cause: Duplicate element name was found in mixed-content declaration [VC: No Duplicate Types, Section 3.2.2]. For example, <!ELEMENT x (#PCDATA | a | a)> is not valid. See Production [51] in XML 1.0 2nd Edition.

Cause: [VC: Root Element Type, Section 2.8] failed because the Name in the document type declaration must match the element type of the root element. For example:

<?xml version="1.0"?> <!DOCTYPE greeting [ <!ELEMENT greeting (#PCDATA)> ]> <salutation>Hello!</salutation> 

The document’s root element, <salutation>, does not match the root element declared in the DTD, i.e., <greeting>.

Cause: Element was declared twice in the DTD [VC: Unique Element Type Declaration. Section 3.2].

Cause: [VC: One ID per Element Type, Section 3.3.1] failed because no element type may have more than one ID attribute specified.

Cause: [VC: ID Attribute Default, Section 3.3.1] failed because an ID attribute must have a declared default of #IMPLIED or #REQUIRED.

Cause: [VC: Required Attribute, Section 3.3.2] failed because if the default declaration has the keyword #REQUIRED, then the attribute must be specified for all elements of the type in the attribute-list declaration.

Cause: [VC: ID, Section 3.3.1] failed because values of type ID must match the Name production. A name must not appear more than once in an XML document as a value of this type; that is, ID values must uniquely identify the elements which bear them.

Cause: [VC: IDREF, Section 3.3.1] failed because values of type IDREF must match the value of some ID attribute.

Cause: [VC: Enumeration, Section 3.3.1] failed because values of this type must match one of the Nmtoken tokens in the declaration.

Cause: [VC: Fixed Attribute Default, Section 3.3.2] failed because if an attribute has a default value declared with the #FIXED keyword, then instances of this attribute must match the default value.

Cause: [VC: Attribute Default Legal, Section 3.3.2] failed because the declared default value must meet the lexical constraints of the declared attribute type.

Cause: [VC: Element Valid, Section 3, bullet #2] failed because the element does not allow text in content. An element is valid if there is a declaration matching elementdecl where the Name matches the element type and the following holds: the declaration matches children and the sequence of child elements belongs to the language generated by the regular expression in the content model, with optional white space (characters matching the nonterminal S) between the start-tag and the first child element, between child elements, or between the last child element and the end-tag. Note that a CDATA section containing only white space does not match the nonterminal S and hence cannot appear in these positions.

Cause: VC: Element Valid, Section 3, bullet #2] failed because the element has invalid content. An element is valid if there is a declaration matching elementdecl where the Name matches the element type, and one of the following applies:

1. The declaration matches children and the sequence of child elements belongs to the language generated by the regular expression in the content model, with optional white space (characters matching the nonterminal S) between the start-tag and the first child element, between child elements, or between the last child element and the end-tag. Note that a CDATA section containing only white space does not match the nonterminal S, and hence cannot appear in these positions.

2. The declaration matches Mixed and the content consists of character data and child elements whose types match names in the content model.

Cause: [VC: Element Valid, Section 3, bullet #2] failed because the element has invalid content. An element is valid if there is a declaration matching elementdecl where the Name matches the element type, and one of the following holds:

1. The declaration matches children and the sequence of child elements belongs to the language generated by the regular expression in the content model, with optional white space (characters matching the nonterminal S) between the start-tag and the first child element, between child elements, or between the last child element and the end-tag. Note that a CDATA section containing only white space does not match the nonterminal S, and hence cannot appear in these positions.

2. The declaration matches Mixed and the content consists of character data and child elements whose types match names in the content model.

Cause: [VC: Proper Declaration/PE Nesting, Section 2.8] failed because parameter-entity replacement text must be properly nested with markup declarations. If either the first character or the last character of a markup declaration (markupdecl above) is contained in the replacement text for a parameter-entity reference, then both must be contained in the same replacement text.

Cause: [WFC: Element Type Match, Section 3] failed because the Name in an element’s end-tag must match the element type in the start-tag.

Cause: [WFC: Unique Att Spec, Section 3.1] failed because no attribute name may appear more than once in the same start-tag or empty-element tag.

Cause: An invalid character was used in the attribute value. The ampersand, less-than character, and quote sign (&, <, ", ’) are invalid. See Production [10] in XML 1.0 2nd Edition.

Cause: [WFC: No External Entity References, Section 3.1] failed because attribute values cannot contain direct or indirect entity references to external entities.

Cause: [WFC: Parsed Entity, Section 4.1] failed because an entity reference must not contain the name of an unparsed entity. Unparsed entities may be referred to only in attribute values declared to be of type ENTITY or ENTITIES.

Cause: [VC: Attribute Value Type, Section 3.2] failed because an invalid attribute type was used in the attribute-list declaration. One of the following types must be added: CDATA, ID, IDREF, IDREFS, ENTITY, ENTITIES, NMTOKEN, or NMTOKENS. See Production [52], [53] in XML 1.0 2nd Edition.

Cause: [WFC: Legal Character, Section 4.1] failed because characters referred to using character references must match the production for Char.

Cause: [WFC: No Recursion, Section 4.1] failed because a parsed entity must not contain a recursive reference to itself, either directly or indirectly.

Cause: [VC: Enumeration, Section 3.3] failed because values of this type must match one of the Nmtoken tokens in the declaration, and must be a valid Nmtoken.

Cause: An invalid character was used in a public identifier. See Production [12], [13] in XML 1.0 2nd Edition.

Cause: The prefix was not defined in any namespace declaration in scope.

Cause: [VC: Entity Name, Section 3.3.1] failed because values of type ENTITY must match the Name production, values of type ENTITIES must match Names; each Name must match the name of an unparsed entity declared in the DTD.

Cause: [VC: Notation Attributes, Section 3.3.1] failed because values of this type must match one of the notation names included in the declaration; all notation names in the declaration must be declared.

Cause: The element declaration referred to by an attribute declaration was not found in the DTD.

Cause: Warning regarding duplicate entity declaration.

Cause: NDATA declaration was found in parameter entity declaration. It is allowed only in general unparsed entity declaration. See Production [72], [74] in XML 1.0 2nd Edition.

Cause: Warning regarding duplicate attribute declaration.

Cause: [VC: Unique Notation Name. Section 4.7] failed because only one notation declaration can declare a given Name.

Cause: The attribute declaration was not found in the DTD.

Cause: The element declaration was not found in the DTD.

Cause: The entity declaration was not found in the DTD.

Cause: The document returned by the createDocument function of NodeFactory was invalid, either it was null or instance of an unsupported class.

Cause: The SAX feature supplied was not a valid feature name.

Cause: The value supplied for the SAX feature was not valid.

Cause: The SAX property supplied was not a valid property name.

Cause: The value supplied for the SAX property was not valid.

Cause: An error occurred while opening the supplied URL.

Cause: The input data contained bytes that are not valid with regard to the UTF-8 encoding scheme.

Cause: The XML Parser does not support the 5-byte UTF-8 encoding scheme. It is also possible that invalid UTF-8 characters were misinterpreted as 5-byte UTF-8 encoding.

Cause: The XML Parser does not support 6-byte UTF-8 encoding scheme. It is also possible that invalid UTF-8 characters were misinterpreted as 6-byte UTF-8 encoding.

Cause: Invalid XML character was found in the input data.

Cause: The encoding of the data, either by auto-detection or by user action, did not match the encoding specified in the XML declaration.

Cause: The XML Parser does not support the specified encoding.

Cause: An invalid instance of InputSource was returned by the EntityResolver. An InputSource can be invalid if the none of Reader, InputStream, and SystemId were initialized or if the SystemId was invalid.

Cause: An invalid size or count was passed to a DOM function.

Cause: An invalid index was passed to a DOM function.

Cause: The DOM operation was trying to a add an ancestor node as a child, which is not permitted because it can lead to inconsistencies in the tree.

Cause: The DOM specification does not allow the parent-child combination used in the DOM operation.

Cause: The XML well-formedness requires that the document node have only one element node as its child. The application tried adding a second element node.

Cause: The attribute list (instance of NamedNodeMap) can contain only attribute nodes.

Cause: The node being added was created by a different document. The DOM specification does not allow use of nodes across documents.

Cause: The qualified or local name passed was invalid.

Cause: The node of the specified type cannot have a value.

Cause: The descendants of entity or entity reference nodes are read-only nodes. Modification is not allowed.

Cause: DTD and all its content is read-only and cannot be modified.

Cause: An attempt was made to remove an attribute that does not belong the current element.

Cause: An attempt was made to remove a node that does not belong to the current node as a child.

Cause: The DOM parameter was not recognized.

Cause: The DOM parameter was not recognized.

Cause: An attempt was made to add an attribute that belonged to another element.

Cause: The namespace for xml and xmlns prefixes is fixed. Usage must match this standard.

Cause: The qualified name passed to a DOM function was invalid.

Cause: The DOM tree has conflicting namespace declarations for the same prefix and so cannot be serialized.

Cause: The object was detached, but no operations are supported on a detached object. The object can be a Range or iterator object.

Cause: The boundary specified in the range was invalid. The selection can be partial only for text nodes.

Cause: The range operation is not supported on the node type specified.

Cause: The event type passed was invalid.

Cause: The application tried to set prefix on a node on which a prefix is not allowed.

Cause: The application tried to import a node of type DOCUMENT or DOCUMENT FRAGMENT.

Cause: The application tried to import a node of type other than ELEMENT or ATTRIBUTE.

Cause: An unexpected error occurred during processing.

Cause: [cvc-assess-attr.1] The attribute was not expected for the owner element.

Cause: [cvc-assess-elt.1.1.1.1] The element declaration required by the processor for validation was absent.

Cause: [cvc-assess-elt.1.1.1.2] The element declaration required by the context was missing in the schema.

Cause: [cvc-assess-elt.1.1.1.3] The context-determined declaration was not skipped. The declaration that matches the element could not be found in the schema.

Cause: [cvc-assess-elt.2]

Cause: [cvc-assess-elt.2]

Cause: [cvc-attribute.1] Attribute declaration was absent from the element declaration.

Cause: [cvc-attribute.2] Missing type definition for the attribute declaration.

Cause: [cvc-attribute.3] Invalid attribute value with respect to its type.

Cause: [cvc-au] Attribute’s normalized value was not the same as the fixed value declared.

Cause: [cvc-complex-type.1] The type of this element was specified as abstract.

Cause: [cvc-complex-type.2.1] The content type was specified empty while the actual content was not.

Cause: [cvc-complex-type.2.2] The element was declared with simple content, but the instance had element children.

Cause: [cvc-complex-type.2.3] Characters appeared in the content of the element with element-only content.

Cause: [cvc-complex-type.2.5] More than one attribute with type ID or its derivation matched the attribute wildcard.

Cause: [cvc-datatype-valid.1.2.2] Characters were not valid with respect to the string type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not valid with respect to the boolean type.

Cause: [cvc-datatype-valid.1.2.2] Characters could not be parsed into a decimal value.

Cause: [cvc-datatype-valid.1.2.2] Characters could not be parsed into a float value.

Cause: [cvc-datatype-valid.1.2.2] Characters were not in a valid double format as specified in IEEE 754-1985.

Cause: [cvc-datatype-valid.1.2.2] Characters were not in a correct extended date time format defined in ISO 8601.

Cause: [cvc-datatype-valid.1.2.2] Characters were not in a valid calendar date format specified in ISO 8601.

Cause: [cvc-datatype-valid.1.2.2] Characters were not in a valid combined data time format as specified in ISO 8601.

Cause: [cvc-datatype-valid.1.2.2] Characters were not in a valid time format as specified in ISO 8601.

Cause: [cvc-datatype-valid.1.2.2] Characters were not in a valid right-truncated date format as specified in ISO 8601.

Cause: [cvc-datatype-valid.1.2.2] Characters were not in a valid right-truncated date format as specified in ISO 8601.

Cause: [cvc-datatype-valid.1.2.2] Characters were not in a valid left-truncated date format as specified in ISO 8601.

Cause: [cvc-datatype-valid.1.2.2] Characters were not in a valid left-truncated date format as specified in ISO 8601.

Cause: [cvc-datatype-valid.1.2.2] Characters were not in a valid left-and-right-truncated date format as specified in ISO 8601.

Cause: [cvc-datatype-valid.1.2.2] Characters were not valid hex encoded binary.

Cause: [cvc-datatype-valid.1.2.2] Characters were not valid with respect to base64 encoding.

Cause: [cvc-datatype-valid.1.2.2] Characters were not in a valid format as specified in RFC 2396 and RFC 2732.

Cause: [cvc-datatype-valid.1.2.2] Characters were not in a valid QName format.

Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for NOTATION type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid normalizedString value.

Cause: [cvc-datatype-valid.1.2.2] Characters were not valid a value for the token type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for the language type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for NMTOKEN type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid list of NMTOKEN type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not valid a value for Name type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for the NCName type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for the ID type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for the IDREF type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for the ENTITY type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid list of ENTITY value.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for the integer type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for the nonPositiveInteger type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for the negativeInteger type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for long type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for int type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for the short type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for the byte type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for the nonNegativeInteger type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for unsignedlong type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value of the unsignedInt type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for the unsignedShort type.

Cause: [cvc-datatype-valid.1.2.2] Characters were not a valid value for the unsignedByte type.

Cause: [cvc-datatype-valid.1.2.3] Characters were invalid with respect to any member type of union.

Cause: [cvc-elt.1]

Cause: [cvc-elt.2] Element declared abstract was used in an instance document.

Cause: [cvc-elt.3.1] There was an attribute xsi:nil, which was not allowed because the element declaration was not nillable.

Cause: [cvc-elt.3.2.1] Element was specified nill but had character or element children.

Cause: [cvc-elt.3.2.2] Element had a fixed value while the content in the instance was empty.

Cause: [cvc-elt.4.1] The value of xsi:type attribute was not a QName.

Cause: [cvc-elt.4.2] The referenced type specified by xsi:type was absent.

Cause: [cvc-elt.4.3] The type referenced by xsi:type was not derived from the original type.

Cause: [cvc-enumeration-valid] The value was not in the enumeration constraint.

Cause: [cvc-facet-valid] The given data value violates the constraining facet.

Cause: [cvc-fractionDigits-valid] The given number violated the fractionDigits constraining facet.

Cause: [cvc-id.1] There is no ID binding in the ID/IDREF table for the validation root.

Cause: [cvc-id.2] The same ID was defined more than once.

Cause: [cvc-identity-constraint] The document contained a duplicate key sequence that violated a uniqueness constraint.

Cause: [cvc-identity-constraint.4.2.1] There were empty key sequences in the key constraint.

Cause: [cvc-identity-constraint.4.2.3] The element selected as a member in a key sequence was nillable, which is not allowed.

Cause: [cvc-identity-constraint.4.3] A keyref referenced an empty key sequence.

Cause: [cvc-length-valid] The length of the value was not the same as specified in the length facet.

Cause: [cvc-maxExclusive-valid] The data value was out of the boundary specified in the maxExclusive facet.

Cause: [cvc-maxInclusive-valid] The data value was out of boundary specified in the maxInclusive facet.

Cause: [cvc-maxLength-valid] The length of the data value was greater than maxLength.

Cause: [cvc-minExclusive-valid] The data value was out of the lower boundary of the value range.

Cause: [cvc-minInclusive-valid] The data value was too small.

Cause: [cvc-minLength-valid] The length of the value was smaller than that specified in minLength.

Cause: [cvc-particle.1.1] The wildcard particle’s minOccurs had not been met.

Cause: [cvc-particle.1.2] The element particle’s minOccurs had not been met.

Cause: [cvc-particle.1.3] The model group particle’s minOccurs had not been met.

Cause: [cvc-pattern-valid] The literal did not match the pattern constraining facet.

Cause: [cvc-resolve-instance.1] Could not resolve the type reference to a type definition.

Cause: [cvc-resolve-instance.2] Could not resolve attribute reference to an attribute declaration.

Cause: [cvc-resolve-instance.3] Could not resolve the element reference to an element declaration.

Cause: [cvc-resolve-instance.4] Could not resolve the attribute group reference to an attribute group definition.

Cause: [cvc-resolve-instance.5] Could not resolve the model group reference to a model group definition.

Cause: [cvc-resolve-instance.6] Could not resolve the notation reference to a notation declaration.

Cause: [cvc-totalDigits-valid] The number of digits in the numeric value was greater than the value of the totalDigits facet.

Cause: An element in the XML Schema document did not have a Schema namespace.

Cause: [schema_reference.2] The processor could not find the schema from the given schema location.

Cause: [schema_reference.3] The processor was unable to retrieve the schema based on the given namespace.

Cause: [src-annotation]

Cause: [src-annotation] More than one annotation element appeared in the component.

Cause: [src-annotation] Annotation was not the first element in the component.

Cause: The attribute wildcard appeared before the attribute declarations.

Cause: [src-attribute.1] More than one anyAttributes were declared.

Cause: [src-attribute.1] Both default and fixed attributes were present in the attribute declaration.

Cause: [src-attribute.2] Both default and use were present, but the value for use is not optional.

Cause: [src-attribute.3.1] Neither name nor ref attribute was present in declaration.

Cause: [src-attribute.3.1] Name and ref attribute were both present in attribute declaration.

Cause: [src-attribute.3.2] The attribute was a reference. A form, type, or simpleType child were specified.

Cause: [src-attribute.4] Both type attribute and simpleType child were present.

Cause: [src-attribute_group.2] Attribute wildcards defined were not expressible with a wildcard.

Cause: [src-attribute_group.3] Attribute groups were circularly referenced outside redefine.

Cause: Groups were circularly referenced outside redefine.

Cause: [src-ct.1] Derived a complexType with complex content from a simple type.

Cause: [src-ct.2] A complexType with simpleContent was derived from a complexType with complex content.

Cause: [src-element.2.2] Element reference also had one or more of the following attributes: complexType, simpleType, key, keyref unique children or nillable, form, default, block, or type.

Cause: [src-element.3] Element declaration had both complexType and simpleType children.

Cause: [src-import.1.1] The imported namespace was the same as the target namespace of the importing schema.

Cause: [src-import.1.2] Imported namespace was specified but absent from the imported schema.

Cause: [src-import.3.1] Specified namespace was different from the actual targetNamespace imported.

Cause: [src-import.3.2] Specified a no-namespace schema, but the actual schema had targetNamespace.

Cause: [src-include.1] The processor was unable to include a schema from the given location.

Cause: [src-include.2.1] Tried to include a schema with a different targetNamespace.

Cause: [src-include.2.2] A schema without targetNamespace tried to include a schema with targetNamespace.

Cause: [src-list-itemType-or-simpleType] Both the itemType attribute and simpleType child were present in list simple type declaration.

Cause: [src-qname] Prefix of a qname was present, but did not map to any in-scope namespace.

Cause: [src-redefine.3.1] Redefined schema’s targetNamespace was not the same as the targetNamespace of the redefining schema.

Cause: [src-redefine.3.2] A no-namespace schema tried to redefine a schema with a namespace.

Cause: [src-redefine.5] A simpleType or complexType was present in redefine, but its base type was not itself.

Cause: [src-redefine.5] A simpleType or complexType was present in redefine, but its base type was not itself.

Cause: [src-redefine.6.1.1] A group was present in redefine and it had more than one reference to itself in its content.

Cause: [src-redefine.6.1.2] A minOccurs or maxOccurs with value other than 1 was specified in a group self-reference in redefine.

Cause: [src-redefine.6.2.2] A group was presented in redefine without self-reference but was not a valid restriction of its original group.

Cause: [src-redefine.7.2.2] An attributeGroup was present in redefine without self-reference but was not a valid restriction of its original.

Cause: [src-restriction-base-or-simpleType]

Cause: [src-simple-type.2] Both base and simpleType were absent in simple type restriction.

Cause: [src-simple-type.3] Missing itemType attribute or simpleType child in list definition.

Cause: [src-simple-type.3] Both itemType attribute and simpleType child were present in list definition.

Cause: [src-simple-type.4] Some member types in union type made references to the union type.

Cause: [src-single-facet-value] The same facet other than enumeration and pattern had been specified more than once, which is not allowed.

Cause: [src-union-memberTypes-or-simpleTypes] Both memberTypes and simpleType were absent for a union type.

Cause: [st-restrict-facets] Derivation was not restricted while facet children were present.

Cause: [ag-props-correct.1] There were more than one attribute declarations with the same namespace and name in an attribute group definition.

Cause: [ag-props-correct.2] There were more than one attribute declarations with type ID.

Cause: [a-props-correct.2] The fixed value or default value did not satisfy the attribute’s type.

Cause: [a-props-correct.3] Attribute with ID type had either fixed or default value constraint.

Cause: [au-props-correct.2] Attribute reference specified a fixed value which is not the same as that in referenced declaration.

Cause: [au-props-correct.2] Attribute reference specified a default value, while the referenced declaration had a fixed value.

Cause: [c-fields-xpaths.1] The value of xpath was not valid xpath expression as specified in XPath 1.0.

Cause: [c-fields-xpaths.2] The value of xpath did not satisfied field’s restricted xpath syntax.

Cause: [cos-all-limited] Some elements in a All group had maxOccurs greater than one.

Cause: All group was contained in another model group.

Cause: [cos-applicable-facets] All group was contained in another model group

Cause: [cos-applicable-facets] A facet not applicable to the simple type was used.

Cause: [cos-aw-intersect] Two wildcards in an attribute group had different negative namespaces.

Cause: [cos-ct-derived-ok.1] Base type’s final prevented the derivation.

Cause: [cos-ct-derived-ok.2] There was no derivation chain from base type to derived type.

Cause: [cos-ct-extends.1.4.2.1] The content type of an extension of a complex type was empty.

Cause: [cos-ct-extends.1.4.2.2.2] Base type’s content type was not empty and was not the same as the content type specified.

Cause: More than one element in the content had the same name and namespace, but did not refer to the same type.

Cause: [cos-equiv-derived-ok-rec]

Cause: [cos-list-of-atomic] The itemType of a list type was itself a list.

Cause: [cos-no-circular-union] Union’s name and namespace matched one of its memberType.

Cause: [cos-nanambig] particles in a content type violated UPA (Unique Particle Attrition) constraint.

Cause: [cos-particle-extend]

Cause: [cos-particle-restrict]

Cause: [cos-st-derived-ok] Derivation was restriction but restriction was in base type’s final.

Cause: [cos-st-derived-ok] The derivation violated the "type derivation OK (simple)" constraint.

Cause: [cos-st-restricts.1.1] The base type is list.

Cause: [cos-st-restricts.1.1] Tried to directly restrict anySimpleType.

Cause: [cos-st-restricts.2.3]

Cause: [cos-st-restricts.3.3]

Cause: [cos-valide-default] Element had default constraint but its mixed content type was not emptiable.

Cause: [cos-valide-default] Element had default value constraint but its content type was element only or empty.

Cause: [cos-valide-default] Element’s default value constraint was invalid to its type.

Cause: [c-props-correct] Number of fields were different between keyref and referenced key.

Cause: [ct-props-correct] Complex type was derived from simple type, but derivation was not extension.

Cause: [ct-props-correct] Type was in its own derivation chain.

Cause: [ct-props-correct] Type was in its own derivation chain.

Cause: [derivation-ok-restriction.1] Complex type was restricted from a simple type.

Cause: [derivation-ok-restriction.2] The attribute in restriction was not allowed for base type.

Cause: [derivation-ok-restriction.3] Restriction’s attribute uses was not a subset of base type’s attribute uses.

Cause: [derivation-ok-restriction.4] Restriction had an attribute wildcard that did not correspond to any attribute wildcard in base type.

Cause: [derivation-ok-restriction.5.1] Content type was simple, but the base type has complex content that is not mixed or not emptiable.

Cause: [derivation-ok-restriction.5.2] Content type was empty, but the base type had simple content or non-emptiable complex content.

Cause: [enumeration-required-notation] NOTATION type was used without enumeration facet.

Cause: [enumeration-valid-restriction] Some value in enumeration was not valid in respect to the type.

Cause: [e-props-correct.2] Default value was invalid in respect to the type of the element.

Cause: [e-props-correc.3] The type of the element was not a valid derivation from the type of element’s substitutionGroup.

Cause: [e-props-correct.4] Type was ID or its derivation while there was a value constraint.

Cause: [fractionDigits-totalDigits] The value for fractionDigits was greater than totalDigits.

Cause: [length-minLength-maxLength] Both length and either minLength or maxLength were specified.

Cause: [length-valid-restriction] Specified a length that was not the same as the length in base type.

Cause: [maxExclusive-valid-restriction] Restricted maxExclusive was greater than its original in base type.

Cause: [maxInclusive-maxExclusive] Specified a minInclusive that was greater or equal to maxExclusive.

Cause: [maxLength-valid-restriction] Specified a maxLength greater than original in base type.

Cause: [mg-props-correct] Circular model group references.

Cause: [minExclusive-less-than-equals-to-maxExclusive] minExclusive was bigger than maxExclusive.

Cause: [minExclusive-less-than-maxInclusive] inExclusive specified was greater than or equal to maxInclusive.

Cause: [minExclusive-valid-restriction] Restriction’s minExclusive was less than base type’s minExclusive.

Cause: [minExclusive-valid-restriction] Restriction’s minExclusive was less than the base type’s minInclusive.

Cause: [minExclusive-valid-restriction] Restriction’s minExclusive was greater than the base type’s maxInclusive.

Cause: [minExclusive-valid-restriction] Restriction’s minExclusive was greater than or equal to base type’s maxExclusive.

Cause: [minInclusive-less-than-equal-to-maxInclusive] Specified a minInclusive that was greater than maxInclusive.

Cause: [minInclusive-minExclusive]] Restriction specified for both minInclusive and minExclusive.

Cause: [minInclusive-valid-restriction] Restriction’s minInclusive was less than or equal to minInclusive in base type.

Cause: [minInclusive-valid-restriction] Restriction’s minInclusive was less than minExclusive in base type.

Cause: [minInclusive-valid-restriction] Restriction’s minInclusive was greater than maxInclusive in base type.

Cause: Restriction’s minInclusive was greater than or equal to maxEnclusive in base type.

Cause: [minLength-less-than-equal-to-maxLength] minLength in restriction is greater than base type’s maxLength.

Cause: [minLength-valid-restriction] Value of minLength is smaller than that of base type in restriction.

Cause: [no-xmlns] Declared an attribute with name xmlns.

Cause: [n-props-correct] The minOccurs of the particle was greater than the maxOccurs.

Cause: [n-props-correct] The minOccurs of the particle was greater than the maxOccurs.

Cause: [p-props-correct] The maxOccurs of the particle was less than 1.

Cause: [n-props-correct] The Notation declaration had incorrect properties.

Cause: [range-ok] Range of restriction was not within the range of parent particle.

Cause: Restriction did not satisfy the constraint: Particle Derivation OK (Sequence:Choice -- MapAndSum).

Cause: [rcase-NameAndTypeOK] Restriction did not satisfy the constraint: Particle Restriction OK.

Cause: [rcase-NSCompat] Restriction did not satisfy the constraint: Particle Restriction OK.

Cause: [rcase-NSRecurseCheckCardinality] Restriction did not satisfy the constraint: Particle Restriction OK.

Cause: [rcase-NSSubset] Restriction did not satisfy the constraint: Particle Restriction OK (Any:Any -- NSSubset).

Cause: [rcase-Recurse] Restriction did not satisfy the constraint: Particle Restriction OK (All:All, Seqiemce"Sequence:-- Recurse).

Cause: [rcase-RecurseLax] The wildcard was not validly restricted from another wildcard.

Cause: Restriction violated the constraint: Particle Derivation OK (Sequence:All--RecurseUnordered).

Cause: [sch-props-correct] There were two schema components with same name and namespace.

Cause: [st-props-correct]

Cause: [w-props-correct] The namespace constraint was not a restriction of its super.

Cause: [totalDigits-valid-restriction] Restriction specified a totalDigits with a value greater than that in base type.

Cause: [whiteSpace-valid-restriction] Restriction’s whiteSpace was replace or preserve, and base had whiteSpace collapse, or restriction had replace while base had preserve.

Cause: Substitution group was circular.

Cause: Error occurred while processes execution is ignored.

Cause: Component being wrapped by pipeline process is causing an error.

Cause: Output url might be invalid.

Cause: Base url is invalid.

Cause: Input url might be invalid.

Cause: Param with name target is missing or invalid.

Cause: Element procdef is missing.

Cause: The dependent process did not provide a valid ContentHandler.

Cause: Component output and input don’t match in terms of document/docfrag.

Cause: A process whose output label matched target label is not available.

Cause: A dependent process output label has not been named correctly, or a dependent process is missing.

Cause: A process could not be created because there is an error in the process definition element associated with it.

Cause: Either the target does not exist, or the pipeline inputs are more recent than the target.