Steps are those parts of an XProc implementation which applies particular behavior to the xml content 'flowing' thru a pipeline.
Feature |
Description |
---|---|
<p:XSLT> |
The <XSLT> step should be implemented in accordance with the specification. The step receives the document, which is to treat via the input port and provides the transformation result at the output port. |
<p:XInclude> |
The <XInclude> step should be implemented in accordance with the specification. The step receives the document, which is to treat via the input port and provides the transformation result at the output port. |
<p:Load> |
The <Load> step should be implemented in accordance with the specification. The step loads an XML document from somewhere accessed via the URI expressed in the href attribute and provides this document at the result port. The URI might also reference to an database server or any other service, which is able to return XML documents. (yax will provide a (experimental?) data source interface in one of the next releases.) |
<p:Store> |
The <Store> step should be implemented in accordance with the specification. The step store the content of a context to somewhere accessed via the URI expressed in the href attribute. The URI might also reference to an database server or any other service, which is able to return XML documents. (yax will provide a (experimental?) data source interface in one of the next releases.) |
Constructs are those parts of an XProc implementation which controls the pipeline processing.
Feature |
Description |
---|---|
<p:pipeline> |
The <Pipeline> element should be implemented in accordance with the specification. The input port provides the documents to the contained components. The output port receives the result and provides it to the external realm. |
<p:choose>/<p:when>/<p:choose> |
The <p:choose>/<p:when>/<p:choose> element should be implemented in accordance with the specification. Beside the source and the result port <p:choose>/<p:when>/<p:choose> uses the reference port. You can define a reference port either for each <p:when> or a general reference port at the <p:choose> element (or a mix from both). The input port provides the documents to the contained components. <p:choose>/<p:when>/<p:choose> communicates only via the ports of the <p:choose> element with the external realm. |
<p:try>/<p:group>/<p:catch> |
The <p:try>/<p:group>/<p:catch> element should be implemented in accordance with the specification. The <p:try> element traps all exception which appears while processing the <p:group> elements content. If an exception appears the <p:catch> gets the control to continue the processing. <p:try>/<p:group>/<p:catch> communicates only via the ports of the <p:try> element with the external realm. |
Implementation of Steps |
|
<p:XSLT> |
The <XSLT> step should be implemented in accordance with the specification. The step receives the document, which is to treat via the input port and provides the transformation result at the output port. |
<p:XInclude> |
The <XInclude> step should be implemented in accordance with the specification. The step receives the document, which is to treat via the input port and provides the transformation result at the output port. |
<p:Load> |
The <Load> step should be implemented in accordance with the specification. The step loads an XML document from somewhere accessed via the URI expressed in the href attribute and provides this document at the result port. The URI might also reference to an database server or any other service, which is able to return XML documents. (yax will provide a (experimental?) data source interface in one of the next releases.) |
<p:Store> |
The <Store> step should be implemented in accordance with the specification. The step store the content of a context to somewhere accessed via the URI expressed in the href attribute. The URI might also reference to an database server or any other service, which is able to return XML documents. (yax will provide a (experimental?) data source interface in one of the next releases.) |