In software , an XML pipeline is formed when XML (Extensible Markup Language) processes, especially XML transformations and XML validations , are connected.
9-464: For instance, given two transformations T 1 and T 2 , the two can be connected so that an input XML document is transformed by T 1 and then the output of T 1 is fed as input document to T 2 . Simple pipelines like the one described above are called linear ; a single input document always goes through the same sequence of transformations to produce a single output document. Linear operations can be divided in at least two parts They operate at
18-478: A W3C Recommendation as of May 2010, widespread adoption can be expected. XProc XProc is an XML transformation language for processing documents in pipelines: chaining conversions and other steps together to achieve the desired results. It can handle documents in XML , HTML , JSON , text and binary . The current (stable) version is 3.0. While XProc 1.0 is a W3C Recommendation, XProc 3.0
27-574: Is a standard developed by the W3C XProc Next Community Group. Its main characteristics are: The following is a (very) simple XProc pipeline: So if you supply the following XML document to this pipeline: It comes out as: The exact date and time recorded in the timestamp attribute is of course dependent on the date and time the pipeline is executed. The learning page of the XProc website contains links to all
36-462: Is implemented by software known as an XML pipeline engine, which creates processes, connects them together and finally executes the pipeline. Existing XML pipeline languages include: Different XML Pipeline implementations support different granularity of flow. Until May 2010, there was no widely used standard for XML pipeline languages. However, with the introduction of the W3C XProc standard as
45-507: The inner document level They take the input document as a whole They are mainly introduced in XProc and help to handle the sequence of document as a whole Non-linear operations on pipelines may include: Some standards also categorize transformation as macro (changes impacting an entire file) or micro (impacting only an element or attribute) XML pipeline languages are used to define pipelines. A program written with an XML pipeline language
54-576: The learning and reference materials the XProc community group is aware of. There is a special 101 section with introductory learning materials. 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
63-407: The recommendation for XProc 1.0 dated May 11, 2010. There were various attempts to create working XProc 1.0 processors. The only two currently available as open source products that implement the full 1.0 standard are XML Calabash 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
72-493: 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 was founded and started working on a new version, now completely XML based. Because this was a completely different approach than the 2.0 initiative, the version number was increased to 3.0. A stable version
81-422: Was released on 12 September 2022. In 2024 the working group started work on a minor update to 3.1. The following processors support the XProc 3.0 standard: The following processors support the XProc 1.0 standard. There were several other XProc 1.0 implementations, but these were either incomplete or are not maintained. This is the logo of XProc. It was created by Bethan Tovey-Walsh. The fish
#624375