XProc 2.0: An XML Pipeline Language XProc 2.0: An XML Pipeline Language
W3C Editor's Draft
- This Version:
- https://xquery.github.io/xproc-vnext-spec/langspec
- Latest Version:
- http://www.w3.org/TR/xproc20/
- Editors:
- Norman Walsh, MarkLogic Corporation
<norman.walsh@marklogic.com> - Alex Milowski, Invited expert
<alex@milowski.org> - Henry S. Thompson, University of Edinburgh
<ht@inf.ed.ac.uk> - Repository:
- This specification on GitHub
- Report an issue
- Changes:
- Diff against current “status quo” draft
- Commits for this specification
This document is also available in these non-normative formats: XML, automatic change markup from the previous draft courtesy of DeltaXML.
Copyright © 2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.
Abstract
This specification describes the syntax and semantics of XProc 2.0: An XML Pipeline Language, a language for describing operations to be performed on documents.
An XML Pipeline specifies a sequence of operations to be performed on documents. Pipelines generally accept documents as input and produce documents as output. Pipelines are made up of simple steps which perform atomic operations on documents
XProc 2.0: Standard Step Library XProc 2.0: Standard Step Library
W3C Editor's Draft
- This Version:
- https://xquery.github.io/xproc-vnext-spec/langspec
- Latest Version:
- http://www.w3.org/TR/xproc20-steps/
- Editors:
- Norman Walsh, MarkLogic Corporation
<norman.walsh@marklogic.com> - Alex Milowski, Invited expert
<alex@milowski.org> - Henry S. Thompson, University of Edinburgh
<ht@inf.ed.ac.uk> - Repository:
- This specification on GitHub
- Report an issue
- Changes:
- Diff against current “status quo” draft
- Commits for this specification
This document is also available in these non-normative formats: XML, automatic change markup from the previous draft courtesy of DeltaXML.
Copyright © 2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.
Abstract
This specification describes the standard step vocabulary of XProc 2.0: An XML Pipeline Language.
Status of this Document
This document is an editor's draft that has no official standing.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list
XProc Namespace XProc Namespace
1 Introduction
This document describes the names that are defined in the
http://www.w3.org/ns/xprocnamespace at the time of publication. The W3C reserves the right to define additional names in this namespace in the future. Only the XML Processing Model Working Group or its successors may amend this namespace.2 Names in the XProc Namespace
The following names are defined in the XProc: An XML Pipeline Language specification (May, 2010 version). For updated information, please refer to the latest version of the specification.
2.1 XProc 2.0 Names
- p:choose
- p:declare-step
- p:document
- p:document-properties
- p:documentation
- p:empty
- p:for-each
- p:group
- p:import
- p:inline
- p:input
- p:iteration-position
- p:iteration-size
- p:library
- p:log
-
XProc Step Namespace XProc Step Namespace
1 Introduction
This document describes the names that are defined in the
http://www.w3.org/ns/xproc-stepby the XProc: An XML Pipeline Language specification (May, 2010 version). For updated information, please refer to the latest version of the specification.This document describes the names that are defined in this namespace at the time of publication. The W3C reserves the right to define additional names in this namespace in the future. Language implementors and pipeline authors may amend this namespace.
2 Names in the XProc Step Namespace
- c:error
- c:errors
- c:param
- c:param-set
- c:body
- c:data
- c:directory
- c:error
- c:errors
- c:file
- c:header
- c:line
- c:multipart
- c:other
- c:param
- c:param-set
- c:query
-
XProc Error Namespace XProc Error Namespace
1 Introduction
This document describes the names that are defined in the
http://www.w3.org/ns/xproc-errornamespace at the time of publication. The W3C reserves the right to define additional names in this namespace in the future. Only the XML Processing Model Working Group or its successors may amend this namespace.2 Names in the XProc Error Namespace
The following names are defined in the XProc: An XML Pipeline Language specification (May, 2010 version). For updated information, please refer to the latest version of the specification.
2.1 XProc 2.0 Errors
err:XC0023It is a dynamic error if a select expression or match pattern returns a node type that is not allowed by the step.
err:XD0004It is a dynamic error if no subpipeline is selected by the p:choose and no default is provided.
err:XD0005It is a dynamic error if more than one document appears on the connection for this input port.
err:XD0006If sequence is not specified, or has the value false, then it is a dynamic error unless exactly one document appears on the declared port.
err:XD0007If sequence is not specified on p:output, or has the value false, then it is a dynamic error if the step does not produce exactly one document on the declared port.
err:XD0008It is a dynamic error if a document sequence appears where a document to be used as the context node is expected.
err:XD0009It is a dynamic error if the element attribute on p:namespaces is specified and it does not identify a single element node.
err:XD0010It is a dynamic error if the match expression on p:viewport does not match an element or document.
err:XD0011It is a dynamic error if the resource referenced by a p:document element does not exist, cannot be accessed, or has an XML content type and is not a well-formed XML document.
err:XD0012It is a dynamic error if any attempt is made to dereference a URI where the scheme of the URI reference is not supported.
err:XD0013It is a dynamic error if the specified namespace bindings are inconsistent; that is, if the same prefix is boun
Remember: these documents are editor's drafts with no normative standing.
If you have a question or comment about these documents, please raise it as an issue on the specification repository.