p:validate-with-xml-schema — The standard p:validate-with-xml-schema step.
The p:validate-with-xml-schema
step applies
W3C XML Schema: Part 1
validity assessment to the source input.
Input port | Primary | Sequence | Content types |
---|
source | ✔ | | xml html |
schema | | ✔ | xml |
Output port | Primary | Sequence | Content types |
---|
result | ✔ | | xml html |
report | | ✔ | xml json |
Option name | Type | Values | Default value |
---|
assert-valid | xs:boolean | | true() |
mode | xs:string | ('strict','lax') | 'strict' |
parameters | map(xs:QName,item()*)? | | () |
report-format | xs:string | | 'xvrl' |
try-namespaces | xs:boolean | | false() |
use-location-hints | xs:boolean | | false() |
version | xs:string? | | () |
Declaration
1 |<p:declare-step xmlns:p="http://www.w3.org/ns/xproc">
| <p:input port="source" primary="true" content-types="xml html"/>
| <p:input port="schema" sequence="true" content-types="xml"/>
| <p:output port="result" primary="true" content-types="xml html"/>
5 | <p:output port="report" sequence="true" content-types="xml json"/>
| <p:option name="use-location-hints" select="false()" as="xs:boolean"/>
| <p:option name="try-namespaces" select="false()" as="xs:boolean"/>
| <p:option name="assert-valid" select="true()" as="xs:boolean"/>
| <p:option name="parameters" as="map(xs:QName,item()*)?"/>
10 | <p:option name="mode" select="'strict'" values="('strict','lax')"/>
| <p:option name="version" as="xs:string?"/>
| <p:option name="report-format" select="'xvrl'" as="xs:string"/>
|</p:declare-step>
Errors
Code | Description |
---|
err:XC0011 | It is a
dynamic error (err:XC0011 ) if the specified schema version
is not available. |
err:XC0055 | It is a dynamic error (err:XC0055 )
if the implementation does not support the specified mode. |
err:XC0152 | It is a dynamic error (err:XC0152 )
if the document supplied on schema port is not a valid XML schema
document. |
err:XC0156 | It is a dynamic error (err:XC0156 )
if the assert-valid option on p:validate-with-xml-schema
is true
and the input document is not valid. |
Implementation defined features
- It is
implementation-defined if the documents supplied
on the schemas port are considered when resolving
xs:include
elements in the schema documents provided.