XProc 3.1: Standard Step Library

It is a dynamic error if the value of option override-content-type is not a text media type.

See: p:text-join

It is a dynamic error if a “username” or a “password” key is present without specifying a value for the “auth-method” key, if the requested auth-method isn't supported, or the authentication challenge contains an authentication method that isn't supported.

See: p:http-request

It is a dynamic error if any key in parameters is associated to a value which is not an instance of the XQuery 1.0 and XPath 2.0 Data Model, e.g. with a map, an array, or a function.

See: Invoking an XSLT 2.0 stylesheet

It is a dynamic error if the stylesheet does not support a given mode.

See: Invoking an XSLT 3.0 stylesheet, Invoking an XSLT 2.0 stylesheet

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

See: p:xquery

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

See: p:rename

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.

See: p:namespace-rename

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

See: p:compare

It is a dynamic error if the selection pattern matches a node which is not an element.

See: p:add-attribute, p:delete, p:insert, p:label-elements, p:make-absolute-uris, p:rename, p:replace, p:set-attributes, p:unwrap, p:wrap

It is a dynamic error if the selection pattern matches a document node and the value of the position is “before” or “after”.

See: p:insert

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

See: p:insert

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

See: p:xinclude

It is a dynamic error if the response body cannot be interpreted as requested (e.g. application/json to override application/xml content).

See: p:http-request

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.

See: p:hash

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

See: p:www-form-urldecode

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

See: p:xslt

It is a dynamic error if the source port does not contain exactly one XML document or one HTML document if XSLT 1.0 is used.

See: Invoking an XSLT 1.0 stylesheet

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

See: p:store

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

See: Casting from an XML media type, p:encode

It is a dynamic error if the stylesheet does not provide a given template.

See: Invoking an XSLT 3.0 stylesheet, Invoking an XSLT 2.0 stylesheet

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

See: p:add-xml-base

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

See: p:add-attribute, p:pack, p:set-attributes, p:wrap, p:wrap-sequence

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

See: p:uuid

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

See: p:delete

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

See: p:set-properties

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

See: p:cast-content-type

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

See: Casting from an XML media type

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

See: Casting from an XML media type

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.

See: Casting from an XML media type

It is a dynamic error if the comparison method specified in p:compare is not supported by the implementation.

See: p:compare

It is a dynamic error if the media types of the documents supplied are incompatible with the comparison method.

See: p:compare

It is a dynamic error if the value associated with the “fail-on-timeout” is associated with true() and a HTTP status code 408 is encountered.

See: p:http-request

It is a dynamic error if the map parameters contains an entry whose key is defined by the implementation and whose value is not valid for that key.

See: p:archive, p:archive-manifest, p:cast-content-type, p:compress, p:unarchive, p:uncompress

It is a dynamic error if the number of documents on the archive does not match the expected number of archive input documents for the given format and command.

See: Handling of ZIP archives

It is a dynamic error if the format of the archive does not match the format as specified in the format option.

See: p:archive, p:archive-manifest

It is a dynamic error if two or more documents appear on the p:archive step's source port that have the same base URI or if any document that appears on the source port has no base URI.

See: p:archive

It is a dynamic error if the format of the archive cannot be understood, determined and/or processed.

See: p:archive, p:archive-manifest, p:unarchive

It is a dynamic error if as a consequence of changing or removing the namespace of an attribute the attribute's name is not unique on the respective element.

See: p:namespace-rename

It is a dynamic error if a static error occurs during the static analysis of the XSLT stylesheet.

See: p:xslt

It is a dynamic error if any document supplied on the source port is not an XML document, an HTML documents, or a Text document if XSLT 2.0 is used.

See: Invoking an XSLT 2.0 stylesheet

It is a dynamic error if an error occurred during the transformation.

See: p:xslt

It is a dynamic error if the transformation is terminated by XSLT message termination.

See: p:xslt

It is a dynamic error if a dynamic XPath error occurred while applying sort-key to a line.

See: p:text-sort

It is a dynamic error if the result of applying sort-key to a given line results in a sequence with more than one item.

See: p:text-sort

It is a dynamic error if the document on port manifest does not conform to the given schema.

See: p:archive, The archive manifest

It is a dynamic error if a document appearing on port source cannot be represented in the XDM version associated with the chosen XQuery version, e.g. when a JSON document contains a map and XDM 3.0 is used.

See: p:xquery

It is a dynamic error if any key in option parameters is associated to a value that cannot be represented in the XDM version associated with the chosen XQuery version, e.g. with a map, an array, or a function when XDM 3.0 is used.

See: p:xquery

It is a dynamic error if any error occurs during XQuery’s static analysis phase.

See: p:xquery

It is a dynamic error if any error occurs during XQuery’s dynamic evaluation phase.

See: p:xquery

It is a dynamic error if an XSLT 1.0 stylesheet is invoked and option parameters contains a value that is not an atomic value or a node.

See: Invoking an XSLT 1.0 stylesheet

It is a dynamic error if duplicate keys are encountered and option duplicates has value “reject”.

See: p:json-merge

It is a dynamic error if a document of a not supported document type appears on port source of p:json-merge.

See: p:json-merge

It is a dynamic error if any prefix is not in-scope at the point where the p:namespace-delete occurs.

See: p:namespace-delete

It is a dynamic error if a namespace is to be removed from an attribute and the element already has an attribute with the resulting name.

See: p:namespace-delete

It is a dynamic error if the evaluation of the XPath expression in option key for a given item returns either a sequence, an array, a map, or a function.

See: p:json-merge

It is a dynamic error if a document of an unsupported document type appears on port source of p:json-join.

See: p:json-join

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

See: p:archive

It is a dynamic error if flatten is neither “unbounded”, nor a string that may be cast to a non-negative integer.

See: p:json-join

It is a dynamic error if the relative-to option is not present and the document on the source port does not have a base URI.

See: p:archive-manifest, p:unarchive

It is a dynamic error if a document appearing on the secondary port has a base URI that is not both absolute and valid according to .

See: Invoking an XSLT 3.0 stylesheet, Invoking an XSLT 2.0 stylesheet

It is a dynamic error if the given method is not supported.

See: p:http-request

It is a dynamic error if any key in the “auth” map is associated with a value that is not an instance of the required type.

See: p:http-request

It is a dynamic error if any key in the “parameters” map is associated with a value that is not an instance of the required type.

See: p:http-request

It is a dynamic error if the key “accept-multipart” as the value false() and a multipart response is detected.

See: p:http-request

It is a dynamic error if the XPath expression in assert evaluates to false.

See: p:http-request

It is a dynamic error if the headers map contains two keys that are the same when compared in a case-insensitive manner.

See: p:http-request

It is a dynamic error if the URI’s scheme is unknown or not supported.

See: p:http-request

It is a dynamic error if the processor cannot support the requested encoding.

See: p:http-request

It is a dynamic error if the override content encoding cannot be supported.

See: p:http-request

It is a dynamic error if more than one document appears on the source port and a content-type header is present and the content type specified is not a multipart content type.

See: Construction of a multipart request

It is a dynamic error if the specified value for the override-content-types option is not an array of arrays, where the inner arrays have exactly two members of type xs:string.

See: Overriding content types

It is a dynamic error if the specified value is not a valid XPath regular expression.

See: Overriding content types, p:text-replace, p:unarchive

It is a dynamic error if evaluating the XPath expression in option test on a context document results in an error.

See: p:split-sequence

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

See: p:uncompress

It is a dynamic error if the compression format cannot be understood, determined and/or processed.

See: p:compress, p:uncompress

It is a dynamic error if the specified boundary is not valid (for example, if it begins with two hyphens “--”).

See: Construction of a multipart request