XProc

The following is a (very) simple XProc pipeline: • It declares two ports: • An input port called source. This is where the original document flows in. • An output port called result. This is where the resulting document flows out. • The document that comes in through the source port automatically flows into the first step of the pipeline. This p:add-attribute step adds an attribute called timestamp with the current date and time. • The result of this flows through the p:delete step that removes all attributes called data. • Since p:delete is the last step, the resulting document flows out through the output result port. So if you supply the following XML document to this pipeline: Some data... It comes out as: Some data... The exact date and time recorded in the timestamp attribute is of course dependent on the date and time the pipeline is executed. == Understanding and learning XProc ==

The learning page of the XProc website contains links to all the learning and reference materials the XProc community group is aware of. There is a special 101 section with introductory learning materials. == History ==

Ideas for something, some programming language, for processing were there right from the beginnings of XML, at the end of the twentieth century. But it was not until the end of 2005 that the W3C started a working group called the XML Processing Model Working Group. This resulted in the recommendation for XProc 1.0 dated May 11, 2010. and MorganaXProc. After the release of version 1.0, the XProc working group continued debating a next version. Ideas were raised for version 2.0. This was based on a non-XML syntax which didn’t raise a lot of support from the community. Engagement in the working grouped waned and in 2016 it ceased to exist. In June 2017 the XProc Next Community Group • Dynamic pipeline execution - for running pipelines constructed dynamically • File steps - for accessing and managing files on a filesystem • Operating system steps - for accessing information about the operating system and running external commands • Mail steps - for working with email • Paged media steps - for applying CSS or XSL-FO to an XML or HTML document • Text steps - optional text-related steps, eg. converting markdown to html. The standard step library already includes several required steps for working with text • Validation steps - for testing whether an input conforms to a set of rules expressed in a schema. The input may be XML, HTML or JSON • Invisible XML - for working with Invisible XML == Implementations ==

The following processors support XProc 3.0 and above: XProc 3.0 is backwards incompatible and therefore the above implementations are not expected to support XProc 1.0. Older versions The following processors support the XProc 1.0 standard: • XML Calabash, maintained by Norman Walsh. This processor is also integrated in the Oxygen XML Editor product. • Morgana Xproc 1.0, maintained by Achim Berndzen. There were several other XProc 1.0 implementations, but these were either incomplete or are not maintained. == Logo ==

The XProc logo and mascot is a fish, called Kanava, after the Finnish word for pipeline. The logo was created by Bethan Tovey-Walsh. ==References==