XProc Error Namespace

It is a dynamic error if a select expression or match pattern returns a node type that is not allowed by the step.

It is a dynamic error if no subpipeline is selected by the p:choose and no default is provided.

It is a dynamic error if more than one document appears on the connection for this input port.

If sequence is not specified, or has the value false, then it is a dynamic error unless exactly one document appears on the declared port.

If sequence is not specified on p:output, or has the value false, then it is a dynamic error if the step does not produce exactly one document on the declared port.

It is a dynamic error if a document sequence appears where a document to be used as the context node is expected.

It is a dynamic error if the element attribute on p:namespaces is specified and it does not identify a single element node.

It is a dynamic error if the match expression on p:viewport does not match an element or document.

It is a dynamic error if the resource referenced by a p:document element does not exist, cannot be accessed, or has an XML content type and is not a well-formed XML document.

It is a dynamic error if any attempt is made to dereference a URI where the scheme of the URI reference is not supported.

It is a dynamic error if the specified namespace bindings are inconsistent; that is, if the same prefix is bound to two different namespace names.

It is a dynamic error for any unqualified attribute names other than “name”, “namespace”, or “value” to appear on a c:param element.

It is a dynamic error if the specified QName cannot be resolved with the in-scope namespace declarations.

It is a dynamic error if the select expression on a p:input returns atomic values or anything other than element or document nodes (or an empty sequence).

It is a dynamic error if the running pipeline attempts to invoke a step which the processor does not know how to perform.

It is a dynamic error if the c:parameter-set parameter list contains any elements other than c:param.

It is a dynamic error if any option value does not satisfy the type required for that option.

It is a dynamic error if the combination of serialization options specified or defaulted is not allowed.

It is a dynamic error for a pipeline to attempt to access a resource for which it has insufficient privileges or perform a step which is forbidden.

It is a dynamic error if a processor that does not support PSVI annotations attempts to invoke a step which asserts that they are required.

It is a dynamic error if the namespace attribute is specified on c:param, the name contains a colon, and the specified namespace is not the same as the in-scope namespace binding for the specified prefix.

It is a dynamic error if the select expression makes reference to the context node, size, or position when the context item is undefined.

It is a dynamic error if any attribute value does not satisfy the type required for that attribute.

It is a dynamic error if a step is unable or incapable of performing its function.

It is a dynamic error if the name specified is not the name of an in-scope option or variable.

On steps which allow independent specification of a namespace and a name, it is a dynamic error to specify a new namespace or prefix if the lexical value of the specified name contains a colon.

It is a dynamic error if the element (or document element) passed to p:make-map is not a c:param-set element.

It is a dynamic error if the computed value does not match the specified sequence type.

It is a dynamic error if any of the c:param elements are invalid.

If an input port provides a set of acceptable content types, it is a dynamic error if an input document that arrives on the port has a content type that does not match any content type in that set.

It is a dynamic error if the select is used and any input document is not an XML document.

It is a dynamic error if the body is not correctly encoded per the value of the encoding attribute.

It is a static error if there are any loops in the connections between steps: no step can be connected to itself nor can there be any sequence of connections through other steps that leads back to itself.

All steps in the same scope must have unique names: it is a static error if two steps with the same name appear in the same scope.

It is a static error if any declared input is not connected.

It is a static error if an option or variable declaration duplicates the name of any other option or variable in the same environment.

It is a static error if the primary output port of any step is not connected.

It is a static error if the primary output port has no explicit connection and the last step in the subpipeline does not have a primary output port.

It is a static error if two subpipelines in a p:choose declare different outputs.

It is a static error if any element in the XProc namespace has attributes not defined by this specification unless they are extension attributes.

It is a static error if the p:group and p:catch subpipelines declare different outputs.

It is a static error if a pipeline contains a step whose specified inputs, outputs, and options do not match the signature for steps of that type.

It is a static error to identify two ports with the same name on the same step.

It is a static error to identify more than one output port as primary.

It is a static error if a compound step has no contained steps.

It is a static error to specify that an option is both requiredand has a default value.

If an option is required, it is a static error to invoke the step without specifying a value for that option.

it is a static error for a variable's document connection to refer to the output port of any step in the surrounding container's contained steps

It is a static error if the binding attribute on p:namespaces is specified and its value is not the name of an in-scope binding.

In all cases except the p:output of a compound step, it is a static error if the port identified by a p:pipe is not in the readable ports of the step that contains the p:pipe.

It is a static error if the content of the p:inline element does not consist of exactly one element, optionally preceded and/or followed by any number of processing instructions, comments or whitespace characters.

It is a static error if the expanded-QName value of the type attribute is in no namespace or in the XProc namespace.

It is a static error if the port specified on the p:log is not the name of an output port on the step in which it appears or if more than one p:log element is applied to the same port.

It is a static error if an option is specified with both the shortcut form and the long form.

It is a static error to declare an option or variable in the XProc namespace.

It is a static error to specify a connection for a p:output inside a p:declare-step for an atomic step.

It is a static error to specify that more than one input port is the primary.

It is a static error to use an option on an atomic step that is not declared on steps of that type.

It is a static error if no connection is provided and the default readable port is undefined.

All the step types in a pipeline or library must have unique names: it is a static error if any step type name is built-in and/or declared or defined more than once in the same scope.

It is a static error if any step directly contains text nodes that do not consist entirely of whitespace.

It is a static error if any required attribute is not provided.

It is a static error if the port specified on the p:serialization is not the name of an output port on the pipeline in which it appears or if more than one p:serialization element is applied to the same port.

It is a static error to specify both binding and element on the same p:namespaces element.

It is a static error to attempt to provide a connection for an input port on the declaration of an atomic step.

It is a static error if any element in the XProc namespace or any step has element children other than those specified for it by this specification. In particular, the presence of atomic steps for which there is no visible declaration may raise this error.

It is a static error to use a declared step as a compound step.

It is a static error if the except-prefixes attribute on p:namespaces does not contain a list of tokens or if any of those tokens is not a prefix bound to a namespace in the in-scope namespaces of the p:namespaces element.

It is a static error if the URI of a p:import cannot be retrieved or if, once retrieved, it does not point to a p:library, p:declare-step, or p:pipeline.

It is a static error to import a single pipeline if that pipeline does not have a type.

It is a static error if the exclude-inline-prefixes attribute does not contain a list of tokens or if any of those tokens (except #all or #default) is not a prefix bound to a namespace in the in-scope namespaces of the element on which it occurs.

It is a static error if the value #default is used within the exclude-inline-prefixes attribute and there is no default namespace in scope.

It is a static error if the pipeline element is not p:pipeline, p:declare-step, or p:library.

It is a static error if the processor encounters an explicit request for a previous version of the language and it is unable to process the pipeline using those semantics.

It is a static error if a use-when expression refers to the context or attempts to refer to any documents or collections.

It is a static error if a required version attribute is not present.

It is a static error if the value of the version attribute is not a xs:decimal.

It is a static error if the code attribute is missing from any but the last p:catch, if the last p:catch has a code, or if any error code is repeated.

It is a static error if there is no primary input port.

It is a static error if an expression does not have a closing right curly bracket or if an unescaped right curly bracket occurs outside of an expression.

It is a static error if the step attribute is not specified, and there is no default readable port. It is a static error if the port attribute is not specified, and the step identified has no primary output port.

It is a static error if the port attribute is not specified, and the step identified has no primary output port.

It is a static error if the encoding specified is not supported by the implementation.

It is a static error if an encoding is specified and the content type is an XML media type.

It is a static error if the content type value specifies a character set and the encoding attribute is absent.

It is a static error if an encoding is specified and the content of the p:inline contains any XML markup.

It is a dynamic error if the value starts with the string “--”.

It is a dynamic error if a username or password is specified without specifying an auth-method, if the requested auth-method isn't supported, or the authentication challenge contains an authentication method that isn't supported.

It is a dynamic error if the status-only attribute has the value true and the detailed attribute does not have the value true.

It is a dynamic error if the request contains a c:body or c:multipart but the method does not allow for an entity body being sent with the request.

It is a dynamic error if the method is not specified on a c:request.

It is a dynamic error if an encoding of base64 is specified and the character set is not specified or if the specified character set is not supported by the implementation.

It is a dynamic error if the contents of the directory path are not available to the step due to access restrictions in the environment in which the pipeline is run.

It is a dynamic error if the pattern matches a processing instruction and the new name has a non-null namespace.

It is a dynamic error if the XML namespace (http://www.w3.org/XML/1998/namespace) or the XMLNS namespace (http://www.w3.org/2000/xmlns/) is the value of either the from option or the to option.

It is a dynamic error if the absolute path does not identify a directory.

It is a dynamic error if the documents are not equal, and the value of the fail-if-not-equal option is true.

It is a dynamic error if the the user specifies a value or values that are inconsistent with each other or with the requirements of the step or protocol.

it is a dynamic error if the content of the c:body element does not consist of exactly one element, optionally preceded and/or followed by any number of processing instructions, comments or whitespace characters

It is a dynamic error if the match pattern does not match an element.

It is a dynamic error if the match pattern matches anything other than an element node and the value of the position option is “first-child” or “last-child”.

It is a dynamic error if any XPath expression makes reference to the context node, size, or position when the context item is undefined.

it is a dynamic error if the content of the c:body element does not consist entirely of characters

It is a dynamic error if an XInclude error occurs during processing.

It is a dynamic error if the override-content-type value cannot be used (e.g. text/plain to override image/png).

It is a dynamic error if the command cannot be run.

It is a dynamic error if the current working directory cannot be changed to the value of the cwd option.

It is a dynamic error to specify both result-is-xml and wrap-result-lines.

It is a dynamic error if the requested hash algorithm is not one that the processor understands or if the value or parameters are not appropriate for that algorithm.

It is a dynamic error if the value provided is not a properly x-www-form-urlencoded value.

It is a dynamic error if the specified version is not available.

It is a dynamic error if a sequence of documents (including an empty sequence) is provided to an XSLT 1.0 step.

It is a dynamic error if the document element of the document that arrives on the source port is not c:request.

It is a dynamic error if the URI scheme is not supported or the step cannot store to the specified location.

It is a dynamic error if the content-type specified is not supported by the implementation.

It is a dynamic error if the encoding specified is not supported by the implementation.

It is a dynamic error if the assert-valid option is true and the input document is not valid.

It is a dynamic error if the assert-valid option is true and any Schematron assertions fail.

It is a dynamic error if the implementation does not support the specified mode.

It is a dynamic error if the specified initial mode or named template cannot be applied to the specified stylesheet.

It is a dynamic error if the sequence that results from evaluating the XQuery contains items other than documents and elements.

It is a dynamic error if the all and relative options are bothtrue.

It is a dynamic error if the QName value in the attribute-name option uses the prefix “xmlns” or any other prefix that resolves to the namespace name http://www.w3.org/2000/xmlns/.

It is a dynamic error if the processor does not support the specified version of the UUID algorithm.

It is a dynamic error if the name of any encoded parameter name is not a valid xs:NCName.

It is a dynamic error if the match option matches a namespace node.

It is a dynamic error if the path-separator option is specified and is not exactly one character long.

It is a dynamic error if the exit code from the command is greater than the specified failure-threshold value.

It is a dynamic error if the arg-separator option is specified and is not exactly one character long.

It is a dynamic error to encounter a single closing curly brace “}” that is not immediately followed by another closing curly brace.

It is a dynamic error if more than one document appears on the source port.

It is a dynamic error if the properties map contains a key equal to the string “content-type”.

It is a dynamic error if the supplied content-type is not a valid media type of the form “type/subtype+ext”.

It is a dynamic error if the p:cast-content-type step cannot perform the requested cast.

It is a dynamic error if the c:data contains content is not a valid base64 string.

It is a dynamic error if the c:data element does not have a content-type attribute.

It is a dynamic error if the content-type is supplied and is not the same as the content-type specified on the c:data element.

In all cases except when the input document is a c:data element, it is a dynamic error if the content-type is not supplied.

It is a dynamic error if more than one document appears on the source port of the p:exec step.

It is a dynamic error for any unqualified attribute names other than “name”, “namespace”, or “value” to appear on a c:param element.

It is a dynamic error if the parameter list contains any elements other than c:param.

It is a dynamic error if the namespace attribute is specified, the name contains a colon, and the specified namespace is not the same as the in-scope namespace binding for the specified prefix.

It is a dynamic error to specify a new namespace or prefix if the lexical value of the specified name contains a colon.