64 LSX-00001 to LSX-00344

Cause: A NULL pointer was detected as an internal error condition.

Cause: The top-level element of an XML Schema must be <schema>.

Cause: The named Schema element had an invalid attribute.

Cause: Schema contains an XML node other than element, text (or CDATA),

Cause: An attempt was made to use a feature that is not yet implemented.

Cause: Data is missing for an element or attribute of a simple type.

Cause: Extra elements exist at the end of schema component declarations.

Cause: Implementation error.

Cause: Bogus element exists in the schema file. Its name is not from Schema of Schemas.

Cause: Instance document to be Schema validated was empty (no top-level element).

Cause: Failed to parse the schema document using the given URI.

Cause: Parsed schema components were in a simple-type character set while the parsed instance document data was not. A simple-type character set is single-byte, not shift sensitive, and has no linguistic specials in use.

Cause: An invalid schema context was provided to the processor. Multiple schema documents were loaded and assembled into the schema context. At least one of them is not fully valid with respect to a schema corresponding to the Schema for Schemas.

Cause: A specified type was unknown (not defined in any loaded Schemas).

Cause: Element is undefined in the specified namespace.

Cause: Prefix in a QName is undefined in the current scope.

Cause: Namespace URI is unknown to the schema processor.

Cause: The name of attribute group is unknown to the schema processor in the current scope.

Cause: The name of group is unknown to the schema processor in the current scope.

Cause: The name of attribute is unknown to the schema processor in the current scope.

Cause: The named validation property was unknown.

Cause: Element declaration is not unique within its scope.

Cause: Group declaration is not unique within its scope.

Cause: Type definition is not unique within its scope.

Cause: Attribute group declaration is not unique within its scope.

Cause: Attribute declaration is not unique within its scope.

Cause: A facet declaration did not have a value attribute.

Cause: A specified facet was invalid for a type. Each datatype has a different set of facets which may apply.

Cause: A facet (other than "enumeration") was specified more than once.

Cause: Facet value contained illegal characters or its value was out of range.

Cause: Facets are not defined in the XMLSchema namespace.

Cause: Mutual exclusiveness violations were found for facets. For example, both "length" and either "minLength" or "maxLength" are not allowed to be facets.

Cause: The value of "minLength" must be less than or equal to the value of "maxLength".

Cause: The value of a fixed facet in the base type definition should remain the same.

Cause: There was an error in that minLength was among the members of {facets} of {base type definition} and {value} was less than the {value} of the parent minLength.

Cause: There was an error in that maxLength was among the members of {facets} of {base type definition} and {value} was greater than the {value} of the parent maxLength.

Cause: There was an error in that length was among the members of {facets} of {base type definition} and {value} was not equal to the {value} of the parent length.

Cause: There was an error in that whiteSpace was among the members of {facets} of {base type definition} and at least one of the following conditions was true: 1 {value} is replace or preserve and {value} of the parent whiteSpace is collapse 2 {value} is preserve and the {value} of the parent whiteSpace is replace

Cause: Missing base type declaration in the type definition.

Cause: A "list" element either must have its "itemType" attribute set or have one of its children be a "simpleType" element, but both conditions cannot exist.

Cause: A "restriction" element either must have its "base" attribute set or have one of its children be a "simpleType" element, but both conditions cannot exist.

Cause: Facet value contained illegal characters or its value was out of range.

Cause: Attribute "processContents" in the "any" element or "anyAttribute" declaration has an invalid value.

Cause: A minOccurs or maxOccurs attribute had an invalid value (not a integer or less than zero).

Cause: A "use" attribute had an invalid value. Choices for "use" are "default", "fixed", "optional", "prohibited", or "required".

Cause: An attribute that specifies qualification (form, attributeFormDefault, elementFormDefault) was invalid; it must be one of "qualified" or "unqualified".

Cause: "minOccurs" has a value other than 0/1 or "maxOccurs" has a value other than 1.

Cause: The value of the "maxOccurs" specification is less than the value of the "minOccurs" specification.

Cause: For backward compatibility with DTD, ID type may only be used in attributes.

Cause: There was an invalid sub-element in the content of either the attribute or the element declaration. This was because the sub-element was either at the wrong position or out of context.

Cause: A Schema element was declared but was neither type or reference.

Cause: An attribute which specifies a derivation-restriction setting (block, content, final) had an invalid value. Choices are "#all", "extension", or "restriction".

Cause: A derivedBy attribute had an invalid value. Choices are "extension" or "restriction".

Cause: An element or attribute definition must have either its "type" attribute set or must have one of its children be a "simpleType" or "complexType" element but both conditions cannot exist.

Cause: An invalid schema component exists in the current declaration.

Cause: "annotation" element must be the first in the content.

Cause: An attempt was made to specify two distinct members of {attribute uses}with {attribute declaration}s, both of whose {type definition}s are from ID or are derived from ID.

Cause: A reference-to-attributeGroup element has children. It is suppose to be empty except for annotations.

Cause: If the item"s parent is not <schema>, then either the "ref" or the "name" attribute must be present, but not both. Top-level elements or attributes must have a name.

Cause: If the item"s parent is not <schema> and "ref" is present, then "complexType", "simpleType", "key", "keyref", "unique", "nillable", "default", "fixed", "form", "block", and "type" must be absent.

Cause: It is an error for a declaration to contain both fixed and default attributes.

Cause: If "default" and "use" are both present, use must have its value set to "optional".

Cause: If the item"s parent is not <schema> and the attribute "ref" is present, then the element "simpleType" and the attributes "form" and "type" must be absent.

Cause: Derivation from a type that is declared to be final occurred.

Cause: The element declaration or the type definition was abstract.

Cause: The derivation constraint was violated.

Cause: Two or more simple types were specified within the list content .

Cause: There was an error in that {substitution group exclusions} prevented substitution group affiliation by type restriction or type extension.

Cause: There was a substituted type whose deriving method falls in the union of the {disallowed substitutions} and the {type definition}"s {prohibited substitutions}.

Cause: If the {content type} is a simple type definition, then the string must be valid with regard to the simple type definition as defined by String Valid (3.14.4). If the {content type} is mixed, then the {content type}"s particle must be emptiable as defined by Particle Emptiable (3.9.6). However, one of these conditions was not met, resulting in this error.

Cause: There was a duplicate content specification in the children of complexType.

Cause: In a simpleContent specification, either "restriction" or "extension" was not specified as a child.

Cause: The content type of the type definition was not a simple type definition.

Cause: If the content types of the derived type and base type are not the same simple type definition and the content type of the base type is not empty, then both content types must be mixed or both must be element-only. This was not the case, resulting in this error.

Cause: The defining form did not occur at the top level of a schema.

Cause: The referring form did not occur within a complex type definition or an attribute group definition.

Cause: There was a circular group reference.

Cause: There was no member type definition for the union declaration.

Cause: The sub-element specified in the error message was required.

Cause: The schema component constraint, Derivation Valid (Restriction, Complex) or Particle Valid (Restriction), was violated.

Cause: The schema component constraint, Particle Restriction OK (Elt:Elt -- NameAndTypeOK), was violated.

Cause: The schema component constraint, Derivation Valid (Restriction, simple), (Restriction, complex) or (Extension), was violated.

Cause: A complex base within "simpleContent" was not restricted to contain only simple content.

Cause: An attempt was made to use a circular reference. This is not allowed. For example, it is not possible to return to an element declaration by repeatedly following the {substitution group affiliation} property. Or, within the {particles} of a group there must not be at any depth a particle whose {term} is the group itself.

Cause: Content of the element must be empty.

Cause: Node with type other than "element", "processing instruction", or "comment" exists in the content of the violating element.

Cause: Node with type other than "text", "processing instruction", or "comment" exists in the content of the violating element.

Cause: Extra nodes exist at the end of an element with a complex type definition.

Cause: The element had a value other than its fixed value.

Cause: An attempt was made to substitute an element that violated a constraint.

Cause: Value is out of range for the data with a specific type.

Cause: Too many fractional digits after the decimal point.

Cause: Too many digits in the decimal data.

Cause: Too few occurrences of particles in the node.

Cause: Too many occurrences of particles in the node.

Cause: There were too many digits in the decimal data.

Cause: Data of simple type has invalid length.

Cause: The length of the data is too short.

Cause: The length of the data is too long.

Cause: The specified item type must not itself be a list type, and must be one of the types identified in [XML Schemas: Datatypes] as a suitable item type for a list simple type.

Cause: Illegal characters exist in the "integer" or its derivative type declarations.

Cause: Illegal characters exist in the "unsignedLong", "unsignedInt", "unsignedShort", or "unsignedByte" declarations.

Cause: Illegal characters exist in the "unsignedLong" declaration.

Cause: Illegal characters exist in the "long" declaration.

Cause: Illegal characters exist in the "decimal" declaration.

Cause: Invalid URI specification for data of "anyURI" type.

Cause: Invalid XML name.

Cause: Invalid Nmtoken.

Cause: Invalid value for "float" type data.

Cause: Invalid value for "double" type data.

Cause: Boolean data must have a value from the following set: "1", "0", "true", or "false".

Cause: Invalid value for data of "date" type.

Cause: Invalid value for data of "NCName" type.

Cause: Data specified is not of "NCName" type.

Cause: Invalid value for data of "QName" type.

Cause: Invalid value for data of "language" type.

Cause: Invalid value for data of "duration" type.

Cause: Invalid value for data of "dateTime", "time", "gYearMonth", "gYear", "gMonthDay", "gDay", or "gMonth" type.

Cause: Invalid value for data of "normalizedString" type.

Cause: Invalid value for data of "token" type.

Cause: Data of simple type is not one of the union type.

Cause: The pattern specification "branch1 | branch2" has either "branch1" or "branch2" missing.

Cause: ")" found without a matching "(" in a pattern specification.

Cause: "[]" found when processing a character class expression.

Cause: A quantifier was found without an atom specification.

Cause: "x" in "\x" is not a valid escape character.

Cause: An unexpected character was found in the pattern.

Cause: Something is missing at the end of the pattern.

Cause: An error occurred when processing the character property. For example, "{" is missing after "\p" or "\P".

Cause: The type of the attribute is "complex".

Cause: Violating attribute is not defined in the current scope.

Cause: Global declarations cannot contain the attributes "ref", "minOccurs", or "maxOccurs", or the use of this attribute is explicitly declared as "prohibited" by the schema.

Cause: Attribute has a value other than its fixed value.

Cause: A required attribute is missing.

Cause: Data of "hexBinary" type has odd number of digits.

Cause: Data of "hexBinary" type has invalid characters.

Cause: Number of digits is not a multiple of four.

Cause: Data of "base64Binary" type has invalid characters.

Cause: Invalid padding characters at the end of data.

Cause: ID name is not unique within the schema scope.

Cause: Referenced ID name is not defined within the schema scope.

Cause: The name of the "notation" element is not unique within the schema scope.

Cause: Referenced notation name is not defined within the schema scope.

Cause: Each constraint declaration has a name which exists in a single symbol space for constraints.

Cause: Referenced key name is not defined within the schema scope.

Cause: The key value was not unique within its scope.

Cause: The key value was not unique within its scope.

Cause: The value of the data is not one of the enumeration choice.

Cause: Data has a value less than required minimum.

Cause: Data has a value greater than maximum.

Cause: The required fields were missing from the content of the element.

Cause: XPath expressions relative to each element selected by a {selector}are specified by {fields}. These XPath expressions must identify a single node (element or attribute) whose content or value was used in the constraint. This content or value must be of a simple type.

Cause: The field element evaluated to a node-set with a member that was not a simple type.

Cause: "ref" or "name" attributes are either both missing or have both been specified.

Cause: Element or attribute name is not namespace qualified.

Cause: Element or attribute name is namespace qualified.

Cause: Some required elements in "all" particle are missing.

Cause: Missing range start character in a character range specification.

Cause: A comma is missing in a range specification.

Cause: Quatifier has invalid characters.

Cause: Literal is not valid with respect to the pattern.

Cause: If the namespace attribute is present, then its actual value must not match the actual value of the enclosing schema"s targetNamespace attribute. If the namespace attribute is not present, then the enclosing schema must have a targetNamespace attribute.

Cause: For compatibility, ENTITY or ENTITIES should be used only on attributes.

Cause: If the "complexContent" alternative is chosen, then the type definition resolved to by the actual value of the attribute "base" must be a complex type definition.

Cause: Attribute nillable was set to be "false" in element"s declaration.

Cause: The targetNamespace specified in the schema document differed from either: a) the value of the enclosing schema"s namespace attribute, or b) the value of the namespace attribute identified in the import element information item.