diff --git a/step-run/src/main/xml/conformance.xml b/step-run/src/main/xml/conformance.xml
index 01035c8..13720e8 100644
--- a/step-run/src/main/xml/conformance.xml
+++ b/step-run/src/main/xml/conformance.xml
@@ -32,11 +32,4 @@ how implementation-defined features are
-
-Implementation-dependent features
-
-The following features are implementation-dependent:
-
-
-
diff --git a/step-run/src/main/xml/specification.xml b/step-run/src/main/xml/specification.xml
index d056e5f..aa7e729 100644
--- a/step-run/src/main/xml/specification.xml
+++ b/step-run/src/main/xml/specification.xml
@@ -11,8 +11,8 @@
XProc 3.0: dynamic pipeline execution
-201820192020
-the Contributors to the XProc 3.0 Standard Step Library
+2018201920202024
+the Contributors to the XProc 3.x Standard Step Library
specifications
@@ -157,60 +157,68 @@ invocation will fail, for example). Options that are provided by p:run-opti
if the dynamically executed pipeline implicitly or explicitly declares a primary output port with
a different name than implicitly or explicitly specified in the p:run invocation.
-
- Example
-
- Dynamic Execution of a Transformation/Validation Pipeline
- <p:declare-step xmlns:p="http://www.w3.org/ns/xproc"
- xmlns:c="http://www.w3.org/ns/xproc-step"
- xmlns:xs="http://www.w3.org/2001/XMLSchema" version="3.0"
- name="sample-run-invocation">
- <p:variable name="xsl-params" select="map{'foo': 'bar'}"
- as="map(xs:QName, item()*)"/>
- <p:variable name="assert-valid" select="false()" as="xs:boolean"/>
- <p:variable name="mode" as="xs:QName?" select="()"/>
- <p:variable name="template" as="xs:QName?" select="()"/>
- <p:run name="runme">
- <p:with-input href="transform-n-validate.xpl"/>
- <p:run-option name="mode" select="$mode"/>
- <p:run-option name="template" select="$template"/>
- <p:run-option name="xslt-parameters" select="$xsl-params"/>
- <p:run-option name="assert-valid" select="$assert-valid"/>
- <p:run-input port="source" href="my.xml" primary="true"/>
- <p:run-input port="stylesheet" href="my.xsl"/>
- <p:run-input port="xsd" href="my.xsd"/>
- <p:output port="result" primary="true"/>
- <p:output port="report"/>
- </p:run>
-</p:declare-step>
- with this pipeline in transform-n-validate.xpl:
- <p:declare-step xmlns:p="http://www.w3.org/ns/xproc"
- xmlns:c="http://www.w3.org/ns/xproc-step"
- xmlns:xs="http://www.w3.org/2001/XMLSchema" version="3.0"
- name="transform-n-validate">
- <p:input port="source" primary="true" sequence="true"/>
- <p:input port="stylesheet"/>
- <p:input port="xsd"/>
- <p:option name="assert-valid" as="xs:boolean" select="false()"/>
- <p:option name="xslt-parameters" as="map(xs:QName, item()*)?"/>
- <p:option name="mode" as="xs:QName?"/>
- <p:option name="template" as="xs:QName?"/>
- <p:output port="result" primary="true"/>
- <p:output port="report" pipe="report@xsdval"/>
- <p:xslt>
- <p:with-option name="initial-mode" select="$mode"/>
- <p:with-option name="template-name" select="$template"/>
- <p:with-option name="parameters" select="$xslt-parameters"/>
- <p:with-input port="stylesheet" pipe="stylesheet"/>
- </p:xslt>
- <p:validate-with-xml-schema name="xsdval">
- <p:with-option name="assert-valid" select="$assert-valid"/>
- <p:with-input port="schema" pipe="xsd@transform-n-validate"/>
- </p:validate-with-xml-schema>
-</p:declare-step>
-
-
-
+
+Example
+
+The following pipeline shows how p:run might be used.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+]]>
+
+With this pipeline in transform-n-validate.xpl, the preceding
+step has the effect of running the pipeline with the dynamically constructed options.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+]]>
+
+In practice, p:run might be more often used with dynamically constructed
+pipelines.
+