Name
p:file-touch — The standard p:file-touch step.
Synopsis
The p:file-touch step updates the modification
timestamp of a file.
| Output port | Primary | Sequence | Content types | 
|---|---|---|---|
| result | ✔ | application/xml | 
| Option name | Type | Default value | Required | 
|---|---|---|---|
| href | xs:anyURI | ✔ | |
| fail-on-error | xs:boolean | true() | |
| timestamp | xs:dateTime? | () | 
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="timestamp" as="xs:dateTime?"/>
5 |   <p:option name="fail-on-error" as="xs:boolean" select="true()"/>
  |</p:declare-step>Errors
| Code | Description | 
|---|---|
| err:XC0136 | It is a dynamic error ( err:XC0136) if an
      implementation does not supportp:file-touchfor a specified scheme. | 
| err:XC0137 | It is a
          dynamic error ( err:XC0137) ifp:file-touchcannot be completed 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 thehrefoption does not exist and cannot be created
or exists and cannot be accessed. | 
| 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 filefor thehrefoption ofp:file-touch. It is implementation-defined what other schemes are supported byp:file-touch, and what the interpretation of ‘directory’, ‘file’ and ‘contents’ is for those schemes.
Description
The p:file-touch step is a
  standard XProc 3.1 step.
  It is also described on XProcRef.org.