Name
p:file-info — The standard p:file-info step.
Synopsis
The p:file-info
step returns information about a file, directory or other file system
object.
Output port | Primary | Sequence | Content types |
---|---|---|---|
result | ✔ | application/xml |
Option name | Type | Default value | Required |
---|---|---|---|
href | xs:anyURI | ✔ | |
fail-on-error | xs:boolean | true() | |
override-content-types | array(array(xs:string))? | () |
Declaration
1 |<p:declare-step xmlns:p="http://www.w3.org/ns/xproc">
| <p:output port="result" primary="true" content-types="application/xml"/>
| <p:option name="href" required="true" as="xs:anyURI"/>
| <p:option name="fail-on-error" as="xs:boolean" select="true()"/>
5 | <p:option name="override-content-types" as="array(array(xs:string))?"/>
|</p:declare-step>
Errors
Code | Description |
---|---|
err:XC0134 | It is a dynamic error (err:XC0134 ) if an
implementation does not support p:file-info for a specified scheme. |
err:XC0135 | It is a
dynamic error (err:XC0135 ) if p:file-info is not available to the step due to access restrictions
in the environment in which the pipeline is run. |
err:XD0011 | It is a dynamic error (err:XD0011 ) if the resource referenced by the
href option does not exist, cannot be accessed or is not a file, directory or other file
system object. |
err:XD0064 | It is a dynamic
error (err:XD0064 ) if the base URI is not both absolute and valid according to RFC 3986. |
Implementation defined features
- Conformant processors must support URIs whose
scheme is
file
for thehref
option ofp:file-info
. It is implementation-defined what other schemes are supported byp:file-info
, and what the interpretation of ‘directory’, ‘file’ and ‘contents’ is for those schemes.
Description
The p:file-info
step is defined in the
XProc 3.1:
Standard Step Library. It is also described on
XProcRef.org.