It is a static error if analysis of an expression relies on some component of the static context that has not been assigned a value.

It is a static error if an expression is not a valid instance of the grammar.

During the analysis phase, it is a static error if the static type assigned to an expression other than the expression \c () or \c data(()) is \c empty-sequence().

It is a static error if an expression refers to an element name, attribute name, schema type name, namespace prefix, or variable name that is not defined in the static context, except for an ElementName in an ElementTest or an AttributeName in an AttributeTest.

It is a static error if the expanded QName and number of arguments in a function call do not match the name and arity of a function signature in the static context.

It is a static error if a QName that is used as an AtomicType in a SequenceType is not defined in the in-scope schema types as an atomic type.

It is a static error if the target type of a \c cast or \c castable expression is \c xs:NOTATION or \c xs:anyAtomicType.

It is a static error if a QName used in a query contains a namespace prefix that cannot be expanded into a namespace URI by using the statically known namespaces.

It is a static error if the target type of a \c cast expression or constructor function is \c xs:QName or a type derived from \c xs:QName or \c xs:NOTATION, and the argument of the cast expression or constructor function is not a string literal.

It is a type error if, during the static analysis phase, an expression is found to have a static type that is not appropriate for the context in which the expression occurs, or during the dynamic evaluation phase, the dynamic type of a value does not match a required type as specified by the matching rules in 2.5.4 SequenceType Matching.

It is a type error if the result of the last step in a path expression contains both nodes and non-nodes.

It is a type error if the result of a step (other than the last step) in a path expression contains an atomic value.

It is a type error if, in an axis step, the context item is not a node.

Attempt to cast to a namespace-sensitive type failed because the namespace bindings for the result can not be determined.

It is a type error if the content sequence in an element constructor contains an attribute node following a node that is not an attribute node.

It is a type error if the argument of a validate expression does not evaluate to exactly one document or element node.

It is a type error if the typed value of a copied element or attribute node is namespace-sensitive when construction mode is \c preserve and copy-namespaces mode is \c no-preserve.

It is a type error if the content sequence in an element constructor contains a function item.

An implementation that does not support the Schema Import Feature must raise a static error if a Prolog contains a schema import.

It is a static error if the set of definitions contained in all schemas imported by a Prolog do not satisfy the conditions for schema validity specified in Sections 3 and 5 of [XML Schema] Part 1--i.e., each definition must be valid, complete, and unique.

It is a static error if an implementation recognizes a pragma but determines that its content is invalid.

It is a static error if the value of a namespace declaration attribute is not a URILiteral.

It is a static error if the version number specified in a version declaration is not supported by the implementation.

A static error is raised if a Prolog contains more than one base URI declaration.

It is a static error if a module contains multiple bindings for the same namespace prefix.

It is a static error if multiple functions declared or imported by a module have the same number of arguments and their expanded QNames are equal (as defined by the eq operator).

It is a static error to import two schema components that both define the same name in the same symbol space and in the same scope.

It is a static error to import a module if the in-scope schema definitions of the importing module do not include all of the following: -# An in-scope schema type for each type-name that appears: - in the type of a variable that is declared in the imported module and referenced in the importing module, OR - in a parameter-type or result-type of a function that is declared in the imported module and referenced in the importing module. -# An in-scope element declaration for each element-name \c EN such that: - \c schema-element(EN) appears in the declared type of a variable in the imported module, and that variable is referenced in the importing module, OR - \c schema-element(EN) appears in a parameter-type or result-type of a function declared in the imported module, and that function is referenced in the importing module. -# An in-scope attribute declaration for each attribute-name \c AN such that: - \c schema-attribute(AN) appears in the declared type of a variable in the imported module, and that variable is referenced in the importing module, OR - \c schema-attribute(AN) appears in a parameter-type or result-type of a function declared in the imported module, and that function is referenced in the importing module.

It is a static error if a Prolog contains more than one default collation declaration, or the value specified by a default collation declaration is not present in statically known collations.

It is a static error for a function declaration to have more than one parameter with the same name.

It is a static error if the attributes specified by a direct element constructor do not have distinct expanded QNames.

It is a static error if the function name in a function declaration is in one of the following namespaces: http://www.w3.org/XML/1998/namespace, http://www.w3.org/2001/XMLSchema, http://www.w3.org/2001/XMLSchema-instance, http://www.w3.org/2005/xpath-functions.

An implementation MAY raise a static error if the value of a URILiteral is of nonzero length and is not in the lexical space of \c xs:anyURI.

It is a static error if multiple module imports in the same Prolog specify the same target namespace.

It is a static error if a function or variable declared in a library module is not in the target namespace of the library module.

It is a static error if two or more variables declared or imported by a module have equal expanded QNames (as defined by the eq operator.)

The type must be the name of a type defined in the in-scope schema types, and the {variety} of the type must be simple.

It is a static error if a variable depends on itself.

It is a static error if a Prolog contains more than one copy-namespaces declaration.

It is a static error if a schema import binds a namespace prefix but does not specify a target namespace other than a zero-length string.

It is a static error if multiple schema imports specify the same target namespace.

It is a static error if an implementation is unable to process a schema or module import by finding a schema or module with the specified target namespace.

It is a static error if the name of a function in a function declaration is not in a namespace (expanded QName has a null namespace URI).

A static error is raised if a Prolog contains more than one ordering mode declaration.

A static error is raised if a Prolog contains more than one default element/type namespace declaration, or more than one default function namespace declaration.

A static error is raised if a Prolog contains more than one construction declaration.

A static error is raised if a Prolog contains more than one boundary-space declaration.

A static error is raised if a Prolog contains more than one empty order declaration.

A static error is raised if one of the predefined prefixes \c xml or \c xmlns appears in a namespace declaration, or if any of the following conditions is statically detected in any expression or declaration: - The prefix \c xml is bound to some namespace URI other than http://www.w3.org/XML/1998/namespace. - A prefix other than \c xml is bound to the namespace URI http://www.w3.org/XML/1998/namespace. - The prefix \c xmlns is bound to any namespace URI. - A prefix other than \c xmlns is bound to the namespace URI http://www.w3.org/2000/xmlns/.

A static error is raised if the namespace declaration attributes of a direct element constructor do not have distinct names.

It is a static error if a \c collation subclause in an order by clause of a FLWOR expression does not identify a collation that is present in statically known collations.

It is a static error if an extension expression contains neither a pragma that is recognized by the implementation nor an expression enclosed in curly braces.

It is a static error if the namespace URI in a namespace declaration attribute is a zero-length string, and the implementation does not support [XML Names 1.1].

It is a static error if the encoding specified in a Version Declaration does not conform to the definition of \c EncName specified in [XML 1.0]

It is a static error if the literal that specifies the target namespace in a module import or a module declaration is of zero length.

It is a static error if a variable bound in a \c for or \c window clause of a FLWOR expression, and its associated positional variable, do not have distinct names (expanded QNames).

It is a static error if a character reference does not identify a valid character in the version of XML that is in use.

It is a static error to import a module M1 if there exists a sequence of modules M1 ... Mi ... M1 such that each module directly depends on the next module in the sequence (informally, if M1 depends on itself through some chain of module dependencies.)

In the group by clause of a FLWOR expression, it is a static error if the name of a grouping variable is not equal (by the eq operator on expanded QNames) to the name of a variable that is bound by a for or let clause that precedes the group by clause.

It is a static error for a decimal-format to specify a value that is not valid for a given property.

It is a static error if, for any named or unnamed decimal format, the properties representing characters used in a picture string do not each have distinct values. These properties are decimal-separator-sign, grouping-separator, percent-sign, per-mille-sign, zero-digit, digit-sign, and pattern-separator-sign.

If a module contains more than one context item declaration, a static error is raised [err:XQST0099].

All variables in a window clause must have distinct names.

It is a static error if a function's annotations contain more than one annotation named \c private or \c public. It is a static error if a function's annotations contain more than one annotation named \c deterministic or \c nondeterministic.

It is a static error for a query prolog to contain two decimal formats with the same name, or to contain two default decimal formats.

Specifying a VarValue or VarDefaultValue for a context item declaration in a library module is a static error.

It is a static error for a decimal format declaration to define the same property more than once.

It is a static error if a variable declaration contains both a %private and a %public annotation, more than one %private annotation, or more than one %public annotation.

It is a static error if a feature required by require-feature is not supported by the implementation.

It is a static error if the name of a feature in require-feature or prohibit-feature is not in the lexical space of QName.

It is a static error if the name of a feature in require-feature is not recognized by the implementation.

It is a static error if all-extensions appears in a require-feature option declaration.

It is a static error if a given feature is both required and prohibited, directly or indirectly, in a module.

It is a static error if a feature name that an implementation supports appears in a prohibit-feature option declaration, and the implementation is unable to disable the feature.

It is a dynamic error if evaluation of an expression relies on some part of the dynamic context that has not been assigned a value.

It is a dynamic error if the dynamic type of the operand of a treat expression does not match the sequence type specified by the treat expression. This error might also be raised by a path expression beginning with "/" or "//" if the context node is not in a tree that is rooted at a document node. This is because a leading "/" or "//" in a path expression is an abbreviation for an initial step that includes the clause \c treat as \c document-node().

It is a dynamic error if any attribute of a constructed element does not have a name that is distinct from the names of all other attributes of the constructed element.

It is a dynamic error if the result of the content expression of a computed processing instruction constructor contains the string "?>".

In a validate expression, it is a dynamic error if the root element information item in the PSVI resulting from validation does not have the expected validity property: \c valid if validation mode is \c strict, or either \c valid or \c notKnown if validation mode is \c lax.

It is a dynamic error if the value of the name expression in a computed processing instruction constructor cannot be cast to the type \c xs:NCName.

It is a static error the node-name of a node constructed by a computed attribute constructor has any of the following properties: - Its namespace prefix is \c xmlns. - It has no namespace prefix and its local name is \c xmlns. - Its namespace URI is http://www.w3.org/2000/xmlns/. - Its namespace prefix is \c xml and its namespace URI is not http://www.w3.org/XML/1998/namespace. - Its namespace prefix is other than \c xml and its namespace URI is http://www.w3.org/XML/1998/namespace.

It is a dynamic error if a cycle is encountered in the definition of a module's dynamic context components, for example because of a cycle in variable declarations.

It is a dynamic error if the operand of a validate expression is a document node whose children do not consist of exactly one element node and zero or more comment and processing instruction nodes, in any order.

It is a dynamic error if the value of the name expression in a computed processing instruction constructor is equal to "XML" (in any combination of upper and lower case).

It is a dynamic error if the result of the content expression of a computed comment constructor contains two adjacent hyphens or ends with a hyphen.

It is a dynamic error if the value of the name expression in a computed element or attribute constructor cannot be converted to an expanded QName (for example, because it contains a namespace prefix not found in statically known namespaces).

It is a dynamic error if the element validated by a \c validate statement does not have a top-level element declaration in the in-scope element declarations, if validation mode is \c strict.

An implementation MAY raise a dynamic error if an \c xml:id error, as defined in [XML ID], is encountered during construction of an attribute named \c xml:id.

An implementation MAY raise a dynamic error if a constructed attribute named \c xml:space has a value other than \c preserve or \c default.

It is a dynamic error the node-name of a node constructed by a computed element constructor has any of the following properties: - Its namespace prefix is \c xmlns. - Its namespace URI is http://www.w3.org/2000/xmlns/. - Its namespace prefix is \c xml and its namespace URI is not http://www.w3.org/XML/1998/namespace. - Its namespace prefix is other than \c xml and its namespace URI is http://www.w3.org/XML/1998/namespace.

Invalid prefix and/or uri in computed namespace constructor

In an element constructor, if two or more namespace bindings in the in-scope bindings would have the same prefix, then an error is raised if they have different URIs; if they would have the same prefix and URI, duplicate bindings are ignored.

It is a non-recoverable dynamic error if the picture string does not satisfy the format-number function rules.

It is a non-recoverable dynamic error if the $picture, $language, $calendar, or $place argument for fn:format-date, fn:format-time, or fn:format-dateTime is invalid.

It is a non-recoverable dynamic error if a component specifier within the picture refers to components that are not available in the given type of $value.

It is a static error if, during the static analysis phase, the query is found to contain a stop word option that refers to a stop word list that is not found in the statically known stop word lists.

It may be a static error if, during the static analysis phase, the query is found to contain a language identifier in a language option that the implementation does not support. The implementation may choose not to raise this error and instead provide some other implementation-defined behavior.

It is a dynamic error if a weight value is not within the required range of values; it is also a dynamic error if an implementation that does not support negative weights encounters a negative weight value.

It is a dynamic error if an implementation encounters a mild not selection, one of whose operands evaluates to an AllMatches that contains a StringExclude.

It is a static error if, during the static analysis phase, the query is found to contain a thesaurus option that refers to a thesaurus that is not found in the statically known thesauri.

It is a static error if, within a single FTMatchOptions, there is more than one match option of any given match option group.

It is a dynamic error if, when "wildcards" is in effect, a query string violates wildcard syntax.

Unidentified error.

Division by zero.

Numeric operation overflow/underflow.

Input value too large for decimal.

Invalid lexical value.

Input value too large for integer.

NaN supplied as float/double value.

Raised when casting a string to xs:decimal if the string has more digits of precision than the implementation can represent (the implementation also has the option of rounding).

Code point not valid.

Unsupported collation.

Unsupported normalization form.

Collation does not support collation units.

No context document.

Error retrieving resource.

Raised by fn:doc, fn:collection to indicate that it is not possible to return a result that is guaranteed deterministic.

Invalid argument to \c fn:collection().

Invalid argument to \c fn:doc() or \c fn:doc-available().

Invalid content passed to \c fn:parse().

Base URI passed to \c fn:parse() is not a valid absolute URI.

Invalid decimal format name supplied to \c fn:format-number().

Invalid decimal/integer format picture string.

Overflow/underflow in date/time operation.

Overflow/underflow in duration operation.

Invalid timezone value.

No namespace found for prefix.

Base-URI not defined in static context.

Invalid value for cast/constructor.

Invalid argument to \c fn:resolve-uri().

\c fn:zero-or-one() called with a sequence containing more than one item.

\c fn:one-or-more() called with a sequence containing no items.

\c fn:exactly-one() called with a sequence containing zero or more than one item.

Invalid argument type.

The two arguments to fn:dateTime() have inconsistent timezones.

Error in resolving a relative URI against a base URI in \c fn:resolve-uri().

Invalid regular expression flags.

Invalid regular expression.

Regular expression matches zero-length string.

Invalid replacement string.

Argument node does not have a typed value.

An argument to \c fn:data() contains a node that does not have a typed value.

The argument to \c fn:string() is a function item.

An argument to \c fn:deep-equal() contains a function item.

Identifier cannot be used to retrive a resource containing text

Retrieved resource contains octets that cannot be decoded into Unicode using the specified encoding, the resulting characters are not permitted XML characters or requested encoding not supported

This error is raised if the fn:function-lookup returns a context-dependent function and the context-dependent function is then called.

Invalid content passed to \c x:canonicalize().

It is a static error if an updating expression is used in any position other than one of the following: - The topmost expression in the body of a query. - The \c modify clause of a transform expression. - The \c return clause of a FLWOR expression. - The \c return clauses of a typeswitch expression in which every \c return clause contains an updating expression or a vacuous expression. - The \c then and \c else clauses of a conditional statement in which both the \c then and \c else clauses contain either an updating expression or a vacuous expression. - An operand of a comma expression in which each operand is either an updating expression or a vacuous expression. - The content of a parenthesized expression. - The body of a function declaration in which the keyword \c updating is specified.

It is a static error if a simple expression that is not a vacuous expression is used in one of the following positions: - The \c modify clause of a transform expression. - The top-level expression in the body of a function declaration in which the keyword \c updating is specified.

It is a static error if a Prolog contains more than one revalidation declaration.

It is a type error if the insertion sequence of an insert expression contains an attribute node following a node that is not an attribute node.

In an insert expression where into, as first into, or as last into is specified, it is a type error if the target expression returns a non-empty result that does not consist of a single element or document node.

In an insert expression where \c before or \c after is specified, it is a type error if the target expression returns a non-empty result that does not consist of a single element, text, comment, or processing instruction node.

It is a type error if the target expression of a delete expression does not return a sequence of zero or more nodes.

In a replace expression, it is a type error if the target expression returns a non-empty result that does not consist of a single element, attribute, text, comment, or processing instruction node.

In a replace expression where value of is not specified, it is a dynamic error if the node returned by the target expression does not have a parent.

In a replace expression where value of is not specified and the target is an element, text, comment, or processing instruction node, it is a type error if the replacement sequence does not consist of zero or more element, text, comment, or processing instruction nodes.

In a replace expression where value of is not specified and the target is an attribute node, it is a type error if the replacement sequence does not consist of zero or more attribute nodes.

In a rename expression, it is a type error if the target expression returns a non-empty result that does not consist of a single element, attribute, or processing instruction node.

In a transform expression, it is a type error if a source expression in the \c copy clause does not return a single node.

In a transform expression, it is a dynamic error if the \c modify clause modifies any node that was not created by the \c copy clause.

It is a dynamic error if any node is the target of more than one \c rename expression within the same query.

It is a dynamic error if any node is the target of more than one \c replace expression (without value of being specified) within the same query.

It is a dynamic error if any node is the target of more than one replace value of expression within the same query.

It is a dynamic error if a function that was declared to be \c external but not \c updating returns a non-empty pending update list.

It is a dynamic error if a function that was declared to be both \c external and \c updating returns a non-empty data model instance.

It is a dynamic error if the XDM instance that would result from applying all the updates in a query violates any constraint specified in [XQuery 1.0 and XPath 2.0 Data Model]. In this case, none of the updates in the query are made effective.

It is a type error if an insert expression specifies the insertion of an attribute node into a document node.

It is a dynamic error if an insert, replace, or rename expression affects an element node by introducing a new namespace binding that conflicts with one of its existing namespace bindings.

It is a dynamic error if the effect of a set of updating expressions is to introduce conflicting namespace bindings into an element node.

It is a dynamic error if the target expression of an insert, replace, or rename expression evaluates to an empty sequence.

It is a static error if a function declaration specifies both \c updating and a return type.

In an insert expression where \c before or \c after is specified, it is a dynamic error if the node returned by the target expression does not have a parent.

It is a dynamic error if an insert expression specifies the insertion of an attribute node before or after a child of a document node.

It is a dynamic error if multiple calls to \c fn:put() in the same snapshot specify the same URI (after resolution of relative URIs).

It is a dynamic error if the first operand of \c fn:put() is not a node of a supported kind.

It is a dynamic error if the second operand of \c fn:put() is not a valid lexical representation of the \c xs:anyURI type.

It is an error if an item in S6 in sequence normalization is an attribute node or a namespace node.

It is an error if the serializer is unable to satisfy the rules for either a well-formed XML document entity or a well-formed XML external general parsed entity, or both, except for content modified by the character expansion phase of serialization.

It is an error to specify the doctype-system parameter, or to specify the standalone parameter with a value other than omit, if the instance of the data model contains text nodes or multiple element nodes as children of the root node.

It is an error if the serialized result would contain an NCName Names that contains a character that is not permitted by the version of Namespaces in XML specified by the version parameter.

It is an error if the serialized result would contain a character that is not permitted by the version of XML specified by the version parameter.

It is an error if an output encoding other than UTF-8 or UTF-16 is requested and the serializer does not support that encoding.

It is an error if a character that cannot be represented in the encoding that the serializer is using for output appears in a context where character references are not allowed (for example if the character occurs in the name of an element).

It is an error if the omit-xml-declaration parameter has the value yes, and the standalone attribute has a value other than omit; or the version parameter has a value other than 1.0 and the doctype-system parameter is specified.

It is an error if the output method is xml, the value of the undeclare-prefixes parameter is yes, and the value of the version parameter is 1.0.

It is an error if the value of the normalization-form parameter specifies a normalization form that is not supported by the serializer.

It is an error if the value of the normalization-form parameter is fully-normalized and any relevant construct of the result begins with a combining character.

It is an error if the serializer does not support the version of XML or HTML specified by the version parameter.

It is an error to use the HTML output method when characters which are legal in XML but not in HTML, specifically the control characters #x7F-#x9F, appear in the instance of the data model.

It is an error to use the HTML output method when \c > appears within a processing instruction in the data model instance being serialized.

It is a an error if a parameter value is invalid for the defined domain.