These steps can raise dynamic errors.
[Definition: A dynamic error is one which occurs while a pipeline is being evaluated.] Examples of dynamic errors include references to URIs that cannot be resolved, steps which fail, and pipelines that exhaust the capacity of an implementation (such as memory or disk space). For a more complete discussion of dynamic errors, see Dynamic Errors in XProc 3.0: An XML Pipeline Language.
If a step fails due to a dynamic error, failure propagates
upwards until either a p:try is encountered or the entire
pipeline fails. In other words, outside of a p:try, step
failure causes the entire pipeline to fail.
The following specific errors can be raised by these steps:
err:XC0012It 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.
See: p:directory-list
err:XC0017It is a dynamic error if the absolute path does not identify a directory.
See: p:directory-list
err:XC0050It is a dynamic error the file or directory cannot be copied to the specified location.
See: p:file-copy, p:file-move
err:XC0090It is a dynamic error if an implementation does not support directory listing for a specified scheme.
See: p:directory-list
err:XC0113It is a dynamic error if an attempt is made to delete a non-empty directory and the recursive option was set to false.
See: p:file-delete
err:XC0114It is a dynamic error if the directory referenced by the href option cannot be created.
See: p:file-mkdir
err:XC0115It is a dynamic error if the resource referenced by the target option is an existing file or other file system object.
See: p:file-move
err:XC0116It is a dynamic error if the temporary file could not be created.
err:XC0134It is a dynamic error if an implementation does not support p:file-info for a specified scheme.
See: p:file-info
err:XC0135It is a dynamic error if p:file-info is not available to the step due to access restrictions in the environment in which the pipeline is run.
See: p:file-info
err:XC0136It is a dynamic error if an implementation does not support p:file-touch for a specified scheme.
See: p:file-touch
err:XC0137It is a dynamic error if p:file-touch cannot be completed due to access restrictions in the environment in which the pipeline is run.
See: p:file-touch
err:XC0138It is a dynamic error if an implementation does not support p:file-create-tempfile for a specified scheme.
err:XC0139It is a dynamic error if p:file-create-tempfile cannot be completed due to access restrictions in the environment in which the pipeline is run.
err:XC0140It is a dynamic error if an implementation does not support p:file-mkdir for a specified scheme.
See: p:file-mkdir
err:XC0141It is a dynamic error if p:file-mkdir not available to the step due to access restrictions in the environment in which the pipeline is run.
See: p:file-mkdir
err:XC0142It is a dynamic error if an implementation does not support p:file-delete for a specified scheme.
See: p:file-delete
err:XC0143It is a dynamic error if p:file-delete is not available to the step due to access restrictions in the environment in which the pipeline is run.
See: p:file-delete
err:XC0144It is a dynamic error if an implementation does not support p:file-copy for a specified scheme.
See: p:file-copy
err:XC0145It is a dynamic error if p:file-copy is not available to the step due to access restrictions in the environment in which the pipeline is run.
See: p:file-copy
err:XC0147It is a dynamic error if a specified value is not a valid XPath regular expression.
See: p:directory-list
err:XC0148It is a dynamic error if an implementation does not support p:file-move for a specified scheme.
See: p:file-move
err:XC0149It is a dynamic error if p:file-move is not available to the step due to access restrictions in the environment in which the pipeline is run.
See: p:file-move