XML pipeline: Difference between revisions

Revision as of 11:38, 30 November 2011

Revision as of 05:40, 29 December 2011

Line 1:

In [[software]], an '''XML Pipeline''' is formed when [[XML]] (Extensible Markup Language) processes, especially [[XML transformation language|XML transformations]] and [[XML validation]]s, are connected together.

For instance, given two transformations T₁ and T₂, the two can be connected together so that an input XML document is transformed by T₁ and then the output of T₁ is fed as input document to T₂. 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 ==

Line 49:

=== Product-specific ===

* '''W3C XML Pipeline Definition Language''' is specified in a W3C Note.<ref>{{cite web|title=W3C XML Pipeline Definition Language|url=http://www.w3.org/TR/xml-pipeline/}}</ref>.

* '''W3C XML Pipeline Language (XPL) Version 1.0 (Draft) [http://www.w3.org/Submission/xpl/] [http://www.w3.org/TR/xml-pipeline/]''' is specified in a W3C Submission and a component of Orbeon Presentation Server OPS (now called Orbeon Forms). This specification provides an implementation of an earlier version of the language. XPL allows the declaration of complex pipelines with conditionals, loops, tees, aggregations, and sub-pipelines.

* '''[[Apache Cocoon|Cocoon]] sitemaps''' allow, among other functionality, the declaration of XML pipelines. Cocoon sitemaps are one of the earliest implementations of the concept of XML pipeline.

Line 65:

== Standardization ==

Until mayMay 2010, there was no widely used standard for XML pipeline languages. However, with the introduction of the [[W3C]] XProc standard as a [[W3C recommendation#Recommendation (REC)|W3C Recommendation]] as of May 2010 [http://www.w3.org/TR/xproc/], widespread adoption can be expected.

==XML Pipeline History==