Cause: Normal exit

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

Cause: The operating system has run out of memory.

Cause: An internal error has occurred (a key was requested to be placed in a hash table but was already there).

Cause: An internal error has occurred.

Cause: A name, quoted string, URL, or other document component was too long.

Cause: An attempt was made to add an invalid node-type to a parent node.

Cause: The documented ended unexpectedly, perhaps due to truncation.

Cause: The memory callback structure passed to xmlinit was missing the allocate or free functions (or both).

Cause: Error message prefixes, not errors themselves. These are the possible banner messages which appear before an XML error to describe the position (line#) and source (buffer or URI) in which the error occurred, as well as the entity's name (if the source is an entity). Parameter entity banner must be at +1 to non-entity banner, general entity at +2 (see lpxerr.c).

Cause: An input Unicode (UCS2) datum was not aligned properly.

Cause: The wrong node type was given as argument to a DOM call.

Cause: An operation was performed on a context that has already been used (so is not "clean").

Cause: More error message boilerplate.

Cause: An internal error has occurred.

Cause: An unexpected error has occured in a subsystem used by XML. Subcode is the error code returned by that failing subsystem.

Cause: The specified Qname prefix exceeded the maximum length of 255.

Cause: A language ID was specified without the matching global area.

Cause: The NLS (National Language Support) package initialization failed.

Cause: The LEH (Library Exception Handling) package initialization failed.

Cause: The LML (Low-Level Memory manager) package initialization failed.

Cause: The LPU (URL Parser/Loader) package initialization failed.

Cause: Validity Constraint 2.8 failed: "The Name in the document type declaration must match the element type of the root element." *Example: <?xml version="1.0"?> <!DOCTYPE greeting [ <!ELEMENT greeting (#PCDATA)> ]> salutationHello!/salutation *Explanation: The document's root element, salutation, does not match the root element declared in the DTD (greeting).

Cause: Validity Constraint 2.8 failed: "Parameter-entity replacement text must be properly nested with markup declarations." *Example: <?xml version="1.0"?> <!DOCTYPE greeting [ <!ENTITY % e "<!ELEMENT "> %e; greeting (#PCDATA)> ]> greetingHello!/greeting *Explanation: The parameter entity 'e' contains markup which may not be split up; the entire ELEMENT (or ATTLIST or ENTITY) definition must be present in one piece.

Cause: Validity Constraint 2.9 failed: "Standalone document declaration must have the value 'no' if any external markup declarations contain declarations of: * attributes with default values - or - * entities - or - * attributes with values subject to normalization - or - * element types with element content"

Cause: Validity Constraint 3 failed: "An element is valid if there is a declaration matching elementdecl where the Name matches the element type, and one of the following holds: * The declaration matches EMPTY and the element has no content * 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 each pair of child elements. * The declaration matches Mixed and the content consists of character data and child elements whose types match names in the content model. * The declaration matches ANY, and the types of any child elements have been declared."

Cause: Validity Constraint 3 failed: The named element has no matching elementdecl in the DTD

Cause: Validity Constraint 3 failed: The named element is declared as EMPTY in the DTD but contains sub-elements in the document.

Cause: Validity Constraint 3.1 failed:

Cause: Validity Constraint 3.2 failed: "No element type may be declared more than once."

Cause: Validity Constraint 3.2.1 failed: "Parameter-entity replacement text must be properly nested with parenthesized groups. For interoperability, if a parameter-entity reference appears in a choice, seq, or Mixed construct, its replacement text should not be empty, and neither the first nor last non-blank character of the replacement text should be a connector (| or ,). *Example: <?xml version="1.0"?> <!DOCTYPE foo [ <!ELEMENT greeting (#PCDATA)> <!ENTITY % e "(#PCDATA|"> <!ELEMENT foo %e; greeting)> ]> greetingHello!/greeting *Explanation: The parenthetical content of the 'e' entity may not be split up into sections: both open and close parentheses must be in the same declaration.

Cause: Validity Constraint 3.2.2 failed: "The same name must not appear more than once in a single mixed-content declaration." *Example: <!ELEMENT p (#PCDATA|a|b|c|d|a)> *Explanation: 'a' occurs more than once in the mixed-content declaration.

Cause: Validity Constraint 3.3.1 failed: Given thing is not a Name

Cause: Validity Constraint 3.3.1 failed: Given thing is not a Nmtoken

Cause: Validity Constraint 3.3.1 failed: "No element type may have more than one ID attribute specified."

Cause: Validity Constraint 3.3.1 failed: "An ID attribute must have a declared default of #IMPLIED or #REQUIRED."

Cause: Validity Constraint 3.3.1 failed: "Values of this type must match one of the Nmtoken tokens in the declaration."

Cause: Validity Constraint 3.3.2 failed: "If the default declaration is the keyword #REQUIRED, then the attribute must be specified for all elements of the type in the attribute-list declaration."

Cause: Validity Constraint 3.3.2 failed: "If an attribute has a default value declared with the #FIXED keyword, instances of that attribute must match the default value."

Cause: Validity Constraint 4.1 failed: "In a document with an external subset or external parameter entities with "standalone='no'", the Name given in the entity reference must match that in an entity declaration."

Cause: The attribute value must be an unparsed entity.

Cause: Entity's NDATA (notation) is undefined

Cause: Notation is not known.

Cause: Validity Constraint 3.3.1 failed: "A name must not appear more than once in an XML document as a value of this type; i.e., ID values must uniquely identify the elements which bear them."

Cause: An ID was used twice, they must be unique.

Cause: An attribute with tokenized type (IDREFS, ENTITIES, NMTOKENS) did not contain any tokens.

Cause: Warning returned by XmlDomGetDecl when original document did not contain an XMLDecl

Cause: The conversion cannot be made between the specified encodings.

Cause: The specified encoding was not known. It should be an IANA or Oracle encoding name.

Cause: The named input (file, URL, etc) does not exist.

Cause: Data could not be read from the named input.

Cause: A syntax error was found.

Cause: Bad syntax detected when processing a comment.

Cause: Bad syntax detected when processing CDATA. Proper format is '<![CDATA[' data ']]>'.

Cause: Bad syntax detected when processing a conditional section.

Cause: An unknown keyword was found in the DTD.

Cause: Processing instruction starting with XML was found.

Cause: A syntax error was detected.

Cause: Attribute default was invalid.

Cause: A syntax error was detected in the comment.

Cause: A syntax error was detected in the comment.

Cause: A syntax error was detected in the CDATA section.

Cause: A syntax error was detected in the PI section.

Cause: An invalid multibyte character was found.

Cause: An invalid Unicode character was found.

Cause: An invalid native (ASCII/EBCDIC) character was found.

Cause: An invalid digit was found in a character reference.

Cause: Found ']]>' in character data.

Cause: Found '<' in an attribute value.

Cause: An error was received from the SAX callback function.

Cause: An external entity reference was found in an attribute value.

Cause: An attribute occurred multiple times in the same start-tag or empty-element tag.

Cause: An element tag was not ended properly.

Cause: An entity is not declared.

Cause: An entity reference contained the name of an unparsed entity.

Cause: An entity reference contains a recursive reference to itself.

Cause: An XML input file has no contents.

Cause: An invalid character was found in a NAME or NMTOKEN.

Cause: An invalid character was found in a NAME or NMTOKEN.

Cause: A parameter entity reference was found in an improper location in the internal DTD subset.

Cause: Namespace prefix starting with XML was found.

Cause: Namespace prefix is not declared.

Cause: An invalid XML version was specified. Only version 1.0 of the XML specification is supported. Version 1.1 may be specified but will be treated as version 1.0.

Cause: An invalid character was found in a public identifier.

Cause: A conditional section <![ keyword [ markup ]]> had invalid keyword, must be either "IGNORE" or "INCLUDE"

Cause: A conditional section was not properly terminated with ]]>.

Cause: The attribute type is not valid. Options are CDATA, ID, IDREF, IDREFS, ENTITY, ENTITIES, NMTOKEN, or NMTOKENS.

Cause: A start-element tag was improperly formed.

Cause: An entity reference (general or parameter) was not formed properly.

Cause: The ampersand character is used only to start entity or character references.

Cause: An attribute defined in an element's start-tag must be enclosed in single ('') or double ("") quotes.

Cause: The less-than character ('<') is not permitted as data.

Cause: After the close of the top-level element, more data was found.

Cause: In an external ID declaration, the public ID literal was not followed by the system ID literal as required.

Cause: Problems were encountered in the DTD declaration.

Cause: Problems were encountered parsing an entity declaration.

Cause: Problems were encountered parsing an external ID declaration.

Cause: Problems were encountered parsing an attribute declaration.

Cause: A condition section is not permitted in internal DTDs.

Cause: Markup included from an entity must nest/group properly. That is, open/close markup must occur within the same entity. For example, <!DOCTYPE doc [ <!ENTITY e "/foofoo"> ]> docfoo&e;/foo/doc Is invalid since foo's start-tag occurs in the top-level document, but the close-tag is provided by the "e" entity. Both start and end must be provided by the same source.

Cause: An XML declaration was missing the required version#.

Cause: Problems were encountered parsing an XML declaration.

Cause: The "standalone" parameter in the XML declaration had an invalid value.

Cause: Problems were encountered parsing an element declaration.

Cause: The 'children' specification in an element declaration was invalid.

Cause: The 'Mixed' specification in an element declaration was invalid.

Cause: Problems were encountered parsing a notation declaration.

Cause: The xml:space attribute must be declared as an enumeration with choices "default" and "preserve". For example, <!ATTLIST foo xml:space (default|preserve) 'preserve').

Cause: The specified URL was invalid and could not be parsed.

Cause: An URL was encountered which requested a protocol not supported by the XML parser. Only HTTP and file are currently allowed.

Cause: A TCP connection couldn't be opened to the named host.

Cause: An error occurred trying to send data over a TCP connection.

Cause: An error occurred trying to read data from a TCP connection.

Cause: The given language specification was invalid.

Cause: The named relative URL couldn't be resolved against its parent.

Cause: The provided access code was not in the valid range.

Cause: An attempt was made to set the access method callbacks, but all three functions were not provided.

Cause: An error was returned from the FTP server while trying to retrieve a file. See the specific message for details.

Cause: The username/password combination was invalid for FTP login.

Cause: The FTP server is unavailable for use.

Cause: The TCP/IP package could not be initialized.

Cause: Some node types (DOCUMENT_NODE & DOCUMENT_TYPE_NODE) cannot be imported with importNode().

Cause: Output/data encoding must be set after initialization but BEFORE any parsing has taken place.

Cause: An HTTP reply contained an invalid Mime header.

Cause: A quoted string was started but not finished.

Cause: The proxy specification for the given protocol was invalid.

Cause: The no_proxy specification was invalid.

Cause: An HTTP protocol error occurred.

Cause: The specified encoding is known but not supported by the parser.

Cause: A parser context which had a shared DTD set was used to parse a document which also contained a DTD. You cannot use both a shared DTD and and internal/external one.

Cause: The input document was detected to be ASCII (or EBCDIC) based, but no encoding was specified in the XMLDecl and the default input coding was not ASCII (or EBCDIC) based, so could not be applied.

Cause: An element's namespace prefix declarations was for a NULL URI, e.g. <foo xmlns:bar=""/> This is illegal presently in XML 1.0, but will be legal in XML 1.1

Cause: A Unicode document contained an invalid surrogate. If the first (high) surrogate is in the correct range 0xD800 to 0xDBFF, then the second (low) surrogate must be in the range 0xDC00 to 0xDFFF.

Cause: The depth of embedded elements in the document exceeded the limit of 2000.

Cause: Max limit exceeded

Cause: Element content contained CDATA-section-close delimiter.

Cause: The XML namespace Uniform Resource Identifier 'http://www.w3.org/2000/xmlns/' must not be assigned a prefix.

Cause: The prefix 'xmlns' was reserved and could not be used as a prefix.

Cause: The style sheet had too many template match patterns, or the total length of all template match patterns in the style sheet was too long.

Cause: The name attribute was not found in the attribute-set element.

Cause: The XPATH evaluation returns an error.

Cause: The child node is of invalid type or has invalid name for this particular location in stylesheet, rendering the stylesheet as invalid XSLT.

Cause: Attribute is found but its value is not the expected value.

Cause: An input parameter passed into this function is null when it is not supposed to.

Cause: An expected token is not found.

Cause: A closing '}' is expected.

Cause: Namespace prefix is used but not declared.

Cause: The expected attribute for this node is not found.

Cause: XPATH context could not be initialized.

Cause: The expected element is not found.

Cause: This feature is not supported.

Cause: The content of XML PI node might be invalid.

Cause: The content of XML comment node might be invalid.

Cause: An internal error occurred in the code.

Cause: This extension function is not supported.

Cause: The value for the specified attribute is invalid.

Cause: The named decimal-format is undefined (the name "#default" means the default format).

Cause: The named decimal-format was declared more than once.

Cause: The node specified is not of expected type.

Cause: The element to which an attribute was being added is non empty and hence can not add anymore attributes to it.

Cause: User is trying to process an XML file with out selecting any mechanism for output.

Cause: Either an import,include or document() function tried to open a document and failed.

Cause: apply-imports was used even when there was no current template possibly with in for-each.

Cause: An invalid language name was specified for sorting.

Cause: A named parameter supplied to a style sheet did not match any parameters defined for the style sheet.

Cause: A style sheet parameter was previously set and already had a value; the value cannot be changed.

Cause: An internal error has occurred in XPATH.

Cause: An invalid QName was passed to the XPATH parser.

Cause: An invalid axis name was passed to the XPATH parser.

Cause: An unmatched quote was found in the XSL file.

Cause: The namespace URI may not be valid.

Cause: May be out of memory.

Cause: An object of incorrect type was passed to the XPATH/XSL function.

Cause: Right square bracket missing in the XSL file.

Cause: Right parenthesis missing in the XSL file.

Cause: An unexpected token encountered while parsing the expression/ pattern.

Cause: Variable reference may not be valid.

Cause: The function is not supported at this time or the name is invalid.

Cause: The numerical constant in the XPath expression is too big.

Cause: Invalid token in XPath expression.

Cause: Invalid child element in this stylesheet context.

Cause: Invalid attribute value in this stylesheet context.

Cause: Invalid attribute value for this attribute.

Cause: Invalid attribute for this element.

Cause: Missing attribute for this element.

Cause: Invalid variable or parameter or template reference.

Cause: Only one declaration is allowed at this level.

Cause: Invalid number of arguments.

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

Cause: The nested series of template calls is too deep.

Cause: The XML data is too large.

Cause: SAX callback returns an error.

Cause: Attribute is generated in a wrong context.

Cause: Attribute generated in the wrong context.

Cause: Invalid comment node.

Cause: VM terminates.

Cause: Invalid PI node.

Cause: Invalid object type in XPath evaluation.

Cause: Write operation failed.

Cause: The generated document is not well-formed.

Cause: Failed to load a document.

Cause: Invalid encoding specified.

Cause: The string data is too large.

Cause: Too many XML nodes.

Cause: Invalid or missing argument.

Cause: The SOAP context passed to an XmlSoap function was invalid.

Cause: An invalid SOAP role was specified.

Cause: An invalid SOAP connection binding was specified.

Cause: A SOAP message sent with an HTTP binding failed.

Cause: Header block does not have a mustUnderstand attribute.

Cause: Header block does not have a role attribute.

Cause: Message body has no Fault child.

Cause: Fault element does not have a reason with given language.

Cause: SOAP failed to make an HTTP connection to the given URL.

Cause: The reply to a SOAP call was not a valid XML document.

Cause: The version string specified at SOAP creation time was invalid.

Cause: Connection does not exists, or header is badly formed, or maximum number of headers is exceeded.

Cause: Message body has multiple Fault children.

Cause: Message body has additional children besides Fault.

Cause: Fault element does not have one of mandatory children or has children, which are not allowed.

Cause: Mandatory text child is missing from the requested message subelemt.

Cause: Mandatory Value child of the Code child of the Fault badly formed or absent.

Cause: The message has no envelope element child.

Cause: The maximum size of encoded namespace attribute name is 1022.

Cause: The message envelope does not have header.

Cause: The message envelope does not have body.

Cause: Header block does not have a relay attribute.

Cause: The element with requested namespace name and local part does not exists.

Cause: Input arguments passed into this function are null when it is not supposed to.

Cause: Input arguments passed into this function are exclusive. Specify only one of them.

Cause: Invalid value was specified for attribute.

Cause: The proxy specification for the given protocol was invalid.

Cause: The no_proxy specification was invalid.

Cause: A required argument was missing.

Cause: The list of condition factors need to be either all tagged with absoluteURI's or all untagged with absoluteURI's.

Cause: The input XML document's size exceeded the limit set by "max_xml_size" attribute set in XmlDavCreate().

Cause: Null was returned from user-provided callback function.

Cause: The TCP/IP package could not be initialized.

Cause: A TCP connection couldn't be opened to the named host.

Cause: An error occurred trying to send data over a TCP connection.

Cause: An error occurred trying to read data from a TCP connection.

Cause: The maximum allowable number of TCP connections were exceeded. This happens only if too many pending HTTP responses have not been properly ended or destroyed.

Cause: Either the server terminated the TCP connection or the TCP connection is in a bad state.

Cause: An HTTP protocol error occurred.

Cause: Only "chunked" and "identity" transfer-coding values are supported.

Cause: A text media type was expected. But other media types were found.

Cause: No entity body was found when it was read.

Cause: An XML media type was expected. But other media types were found.

Cause: A LOCK request to refresh a lock had no lock token header specified.

Cause: An UNLOCK request to remove a lock had no lock token header specified.

Cause: The wrong object type was given as argument to a WebDAV call.

Cause: The entity body sent by the server in Chunked Transfer Encoding violated protocol.

Cause: Invalid XQuery query.

Cause: Invalid XQuery query.

Cause: Invalid XQuery query.

Cause: Invalid XQuery query.

Cause: Invalid program.

Cause: Invalid program.

Cause: The program was invalid.

Cause: The program was invalid.

Cause: An internal error has occurred.

Cause: The replacement string was invalid.

Cause: XSLT Stylesheet can't be compiled to XQuery query.

Cause: XSLT Stylesheet can't be compiled to XQuery query.

Cause: XSLT Stylesheet can't be compiled to XQuery query.

Cause: Invalid value supplied to flags parameter for XmlDiff or XmlPatch functions.

Cause: Data could not be read from inputs to XmlDiff or XmlPatch functions.

Cause: The root nodes in input documents do not match.

Cause: The diff document either did not specify the XML Processing Instruction "oracle-xmldiff" or did not specify all data required by XmlPatch. The PI should be the first child of the top-level xdiff element. This error is also thrown when the output-model is 'snapshot' and operations-in-docorder is 'false'.

Cause: XmlPatch encountered an invalid XPATH in the diff document.

Cause: The JavaScript Object Notation (JSON) path engine encountered a fatal condition.

Cause: 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.

Cause: 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.

Cause: It is a static error if an expression is not a valid instance of the grammar defined in A.1 EBNF

Cause: 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.

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

Cause: Not currently used.

Cause: Not currently used.

Cause: 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.

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

Cause: An implementation must raise a static error if it encounters a reference to an axis that it does not support.

Cause: 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 [XMLSchema] Part 1 i.e., each definition must be valid, complete, and unique

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

Cause: An expression contained too many levels of nested parentheses.

Cause: Not currently used.

Cause: An implementation that does not support the Module Feature raises a static error if it encounters a module declaration or a module import.

Cause: 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.

Cause: It is a type error if the result of the last step in a path expression contains both nodes and atomic values.

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

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

Cause: Not currently used.

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

Cause: Not currently used.

Cause: 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.

Cause: 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.

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

Cause: 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: valid if validation mode is strict, or either valid or notKnown if validation mode is lax.

Cause: Not currently used

Cause: Not currently used

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

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

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

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

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

Cause: 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.

Cause: It is a static error to import a module if the importing module's in-scope schema types do not include definitions for the schema type names that appear in the declarations of variables and functions (whether in an argument type or return type) that are present in the imported module and are referenced in the importing module.

Cause: Not currently used

Cause: 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.

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

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

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

Cause: Not currently used.

Cause: Not currently used.

Cause: It is a dynamic error if the node-name property of the node constructed by a computed attribute constructor is in the namespace http://www.w3.org/2000/xmlns/ (corresponding to namespace prefix xmlns), or is in no namespace and has local name xmlns.

Cause: 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.

Cause: 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 xs:anyURI.

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

Cause: 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.

Cause: 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.)

Cause: 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 treat as document-node().

Cause: 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.

Cause: Not currently used.

Cause: Not currently used.

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

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

Cause: Not currently used.

Cause: 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.

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

Cause: 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.

Cause: 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).

Cause: 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.

Cause: Not currently used.

Cause: Not currently used.

Cause: 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).

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

Cause: 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.

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

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

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

Cause: A static error is raised if a namespace URI is bound to the predefined prefix xmlns, or if a namespace URI other than http://www.w3.org/XML/1998/namespace is bound to the prefix xml, or if the prefix xml is bound to a namespace URI other than http://www.w3.org/XML/1998/namespace.

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

Cause: 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.

Cause: It is a static error if the graph of module imports contains a cycle (that is, if there exists a sequence of modules M1 ... Mn such that each Mi imports Mi+1 and Mn imports M1), unless all the modules in the cycle share a common namespace.

Cause: 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.)

Cause: An implementation that does not support the Validation Feature must raise a static error if it encounters a validate expression.

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

Cause: Not currently used.

Cause: Not currently used.

Cause: 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.

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

Cause: 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.

Cause: Not currently used.

Cause: Not currently used.

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

Cause: 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].

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

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

Cause: 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.

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

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

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

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

Cause: 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.)

Cause: It is a dynamic error if fn:zero-or-one is called with a sequence containing more than one item

Cause: It is a dynamic error if fn:one-or-more is called with a sequence containing no items

Cause: It is a dynamic error if fn:exactly-one is called with a sequence containing zero or more than one item

Cause: It is a dynamic error if an XQuery F&O is called with wrong argument type.

Cause: It is a dynamic error if an XQuery F&O is called with wrong argument value.

Cause: It is a dynamic error if the Input value too large for decimal

Cause: It is a dynamic error if the Input value too large for integer

Cause: An error occurred during the processing of the XQuery expression.

Cause: It is an error to pass arguments to fn:dateTime having a specified timezone

Cause: It is an error to divide by zero

Cause: Numeric operations causes overflow/underflow

Cause: Wrong argument to fn:resolve-uri() function

Cause: Error resolving relative URI in fn:resolve-uri() function

Cause: NaN supplied as float/double value

Cause: String to be cast to decimal has too many digits of precision

Cause: Unsupported collation

Cause: Unsupported normalization form

Cause: Collation does not support collation units

Cause: No context document

Cause: Error retrieving resource

Cause: Function stability not defined

Cause: Invalid argument to fn:collection

Cause: Invalid argument to fn:doc or fn:doc-available

Cause: Overflow/underflow in date/time operation

Cause: Overflow/underflow in duration operation

Cause: Invalid timezone value

Cause: Base-uri not defined in the static context

Cause: Invalid value for cast/constructor

Cause: Invalid regular expression flags

Cause: Invalid regular expression

Cause: Regular expression matches zero-length string

Cause: Invalid replacement string

Cause: Argument node does not have a typed value

Cause: It is a static error if an updating expression is used in any position other than one of the following: 1. The topmost expression in the body of a query. 2. The modify clause of a transform expression. 3. The return clause of a FLWOR expression. 4. The return clauses of a typeswitch expression in which every return clause contains an updating expression, an empty expression ( ), or a call to the fn:error function. 5. The then and else clauses of a conditional statement in which both the then and else clauses contain either an updating expression, an empty expression ( ), or a call to the fn:error function. 6. An operand of a comma expression in which each operand is either an updating expression, an empty expression ( ), or a call to the fn:error function. 7. The content of a parenthesized expression. 8. The body of a function declaration in which the keyword updating is specified.

Cause: It is a static error if an non-updating expression other than an empty expression ( ) or a call to the fn:error function is used in one of the following positions: 1. The modify clause of a transform expression. 2. The top-level expression in the body of a function declaration in which the keyword updating is specified.

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

Cause: 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.

Cause: 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.

Cause: In an insert expression where before or 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.

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

Cause: 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.

Cause: 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.

Cause: 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.

Cause: 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.

Cause: 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.

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

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

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

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

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

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

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

Cause: An implementation may (but is not required to) raise a dynamic error if a node is deleted that had no parent before execution of the query began.

Cause: 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/XPath Data Model (XDM)]. In this case, none of the updates in the query are made effective.

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

Cause: 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.

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

Cause: It is a dynamic error if the target of a rename expression is a processing instruction node, and the new name expression returns a QName with a non-empty namespace prefix.

Cause: It is a static error if a revalidation declaration in a Prolog specifies a revalidation mode that is not supported by the current implementation.

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

Cause: It is a static error if a function declaration specifies both updating and a return type.

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

Cause: 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.

Cause: It is a dynamic error if the first operand of fn:put is not a node of a supported kind.

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