Content deleted Content added
m HTTP to HTTPS for SourceForge |
|||
(44 intermediate revisions by 30 users not shown) | |||
Line 1:
{{Short description|Part of Extensible Markup Language}}
In [[software]], an '''XML For instance, given two transformations T<sub>1</sub> and T<sub>2</sub>, the two can be connected
== Linear
Linear operations can be divided in at least two parts
=== Micro-operations ===
They operate at the inner document level
* '''[[Identity transform]]''' - makes a verbatim copy of its input to the output▼
* '''Transform''' - execute a transform on the input file using a specified [[XSLT]] file. Version 1.0 or 2.0 should be specified.▼
* '''Rename''' - renames elements or attributes without modifying the content
* '''Replace''' - replaces elements or attributes
* '''Insert''' - adds a new data element to the output stream at a specified point
* '''Delete''' - removes an element or attribute (also known as pruning the input tree)
* '''Split''' - take a single XML document and split it into distinct documents▼
* '''Wrap''' - wraps elements with additional elements
* '''Reorder''' - changes the order of elements
=== Document operations ===
==Non-linear==▼
They take the input document as a whole
▲* '''[[Identity transform]]''' - makes a verbatim copy of its input to the output
* '''Compare''' - it takes two documents and compare them
▲* '''Transform''' - execute a transform on the input file using a specified [[XSLT]] file. Version 1.0 or 2.0 should be specified.
▲* '''Split''' - take a single XML document and split it into distinct documents
=== Sequence operations ===
They are mainly introduced in [[XProc]] and help to handle the sequence of document as a whole
* '''Count''' - it takes a sequence of documents and counts them
* '''[[Identity transform]]''' - makes a verbatim copy of its input sequence of documents to the output
* '''split-sequence''' - takes a sequence of documents as input and routes them to different outputs depending on matching rules
* '''wrap-sequence''' - takes a sequence of documents as input and wraps them into one or more documents
▲== Non-linear ==
Non-linear operations on pipelines may include:
Line 23 ⟶ 37:
* '''Loops''' — where a transformation is executed on each node of a node set selected from a document or a transformation is executed until a condition evaluates to false
* '''Tees''' — where a document is fed to multiple transformations potentially happening in parallel
* '''Aggregations''' — where multiple documents are aggregated into a single document
* '''Exception Handling''' — where failures in processing can result in an alternate pipeline being processed
Some standards also categorize transformation as macro (changes impacting an entire file) or micro (impacting only an element or attribute)
== XML
XML pipeline languages are used to define pipelines. A program written with an XML pipeline language 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:
=== Standards ===
* '''[[XProc|XProc: An XML Pipeline Language]]''' is a W3C Recommendation
=== Product-specific ===
* '''W3C XML Pipeline Definition Language''' is specified in a W3C Note.<ref>{{cite
* '''W3C XML Pipeline Language (XPL) Version 1.0 (Draft)
* '''[[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.
* '''smallx XML Pipelines''' are used by the smallx project.
* '''ServingXML''' defines a vocabulary for expressing flat-XML, XML-flat, flat-flat, and XML-XML transformations in pipelines.
* '''[http://www.polarlake.com/reference-data-distribution/xml-data-pipelining-platform PolarLake Circuit Markup Language] {{Webarchive|url=https://web.archive.org/web/20100830081429/http://www.polarlake.com/reference-data-distribution/xml-data-pipelining-platform |date=2010-08-30 }}''' used by PolarLake's runtime to define [http://www.polarlake.com/reference-data-distribution/xml-data-pipelining-platform XML pipelines] {{Webarchive|url=https://web.archive.org/web/20100830081429/http://www.polarlake.com/reference-data-distribution/xml-data-pipelining-platform |date=2010-08-30 }}. Circuits are collections of paths through which fragments of XML stream (usually as SAX or DOM events). Components are placed on paths to interact with the stream (and/or the outside world) in a low latency process.
* '''xmlsh''' is a scripting language based on the unix shells which natively supports xml and text pipelines [http://www.xmlsh.org]
* '''[[Stylus Studio]] XML Pipeline''' is a visual grammar which defines the following operations: Input, Output, [[XQuery]], XSLT, Validate, XSL-FO to PDF, Convert To XML, Convert From XML, Choose, Warning, Stop.
== Pipe
Different XML Pipeline implementations support different granularity of flow.
* Document: Whole documents flow through the pipe as atomic units. A document can only be in one place at a time. Though usually multiple documents may be in the pipe at once.
Line 50 ⟶ 67:
== Standardization ==
Until
==
* 1972 [[Douglas McIlroy]] of [[Bell Laboratories]] adds the pipe operator to the [[UNIX]] command shell. This allows the output from one shell program to go directly into input of another shell program without going to disk. This allowed programs such as the UNIX [[awk]] and [[sed]] to be specialized yet work together [http://www.cs.dartmouth.edu/~doug/].<ref>{{cite
* 1993 [http://seanmcgrath.blogspot.com Sean McGrath] developed a C++ toolkit for [[SGML]] processing.<ref>{{cite
* 1998 [[Stefano Mazzocchi]] releases the first version of [[Apache Cocoon]], one of the first software programs to use XML pipelines.
* 1998 [http://www.polarlake.com/ PolarLake] {{Webarchive|url=https://web.archive.org/web/20080418064200/http://www.polarlake.com/ |date=2008-04-18 }} build [http://www.polarlake.com/reference-data-distribution/xml-data-pipelining-platform XML Operating System]{{Dead link|date=July 2025 |bot=InternetArchiveBot |fix-attempted=yes }}, which includes [http://www.polarlake.com/reference-data-distribution/xml-data-pipelining-platform XML Pipelining]{{Dead link|date=July 2025 |bot=InternetArchiveBot |fix-attempted=yes }}.
* 2002 Notes submitted by Norman Walsh and [[Eve Maler]] from [[Sun Microsystems]], as well as a W3C Submission submitted in 2005 by [[Erik Bruchez]] and [[Alessandro Vernet]] from [[Orbeon]], were important steps toward spawning an actual standardization effort. While neither submission directly became a W3C recommendation, they were considered key sources of inspiration for the W3C XML Processing [[Working group|Working Group]].
* September 2005 W3C XML Processing [[Working group|Working Group]] started. The task of this working group was to create a specification for an XML pipelining language.
Line 69 ⟶ 86:
* [[W3C recommendation]]
* [[XSLT]]
== References ==
<references/>
== External links ==
=== Standards ===
==== Recommendations ====
* [http://www.w3.org/TR/xproc/ XProc: An XML Pipeline Language], W3C Recommendation 11 May 2010
==== Working drafts ====
* [http://www.w3.org/XML/Processing/ W3C XML Processing Model Working Group]▼
* [http://www.w3.org/TR/xml-pipeline/ W3C XML Pipeline Definition Language Note]
* [http://www.w3.org/Submission/xpl/ W3C XML Pipeline Language (XPL) Version 1.0 (Draft) Submission]
▲* [http://www.w3.org/XML/Processing/ W3C XML Processing Model Working Group]
=== Product specific ===
* [http://www.data2type.de/en/xml-xslt-xslfo/xproc/ XProc tutorial and reference]
* [http://www.oracle.com/technology/tech/xml/xdkhome.html Oracle's XML Pipeline Definition Language Controller Implementation] ''Part of XML Developer's kit, no individual download''
* [http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html Cocoon sitemap]
* [http://www.1060research-server-1.co.uk/docs/3.2.0/book/tutorial/doc_guide_xml_pipelines_main.html NetKernel XML Pipelines]
* [http://idealliance.org/proceedings/xtech05/papers/04-03-01/ Managing Complex Document Generation through Pipelining] {{Webarchive|url=https://web.archive.org/web/20051028015614/http://idealliance.org/proceedings/xtech05/papers/04-03-01/ |date=2005-10-28 }}
* [http://www.orbeon.com/ois/doc/reference-xpl-pipelines XML Pipeline Language (XPL) Documentation] {{Webarchive|url=https://web.archive.org/web/20041212090900/http://www.orbeon.com/ois/doc/reference-xpl-pipelines |date=2004-12-12 }}
* [http://norman.walsh.name/2004/06/20/sxpipe SXPipe]
* [http://www.polarlake.com/ PolarLake Reference data management] {{Webarchive|url=https://web.archive.org/web/20080418064200/http://www.polarlake.com/ |date=2008-04-18 }} PolarLake XML circuits and reference data management
* [https://smallx.dev.java.net/ smallx] {{Webarchive|url=https://web.archive.org/web/20070708133342/https://smallx.dev.java.net/ |date=2007-07-08 }}
* [
* [http://www.stylusstudio.com/xml/pipeline.html XML Pipeline Implementation from Stylus Studio] - This program allows XML transforms to be chained together along with other operations on XML files such as validation and [[HTML
* [http://xmlpipelineserver.com IVI XML Pipeline Server] XML Pipeline Server is an implementation for the Stylus Studio XML Pipeline language
* [http://xproc.org/ Norman Walsh's XProc web site] - Norman Walsh is the chair of the W3C XProc standards committee.
* [
* [https://web.archive.org/web/20070209060027/http://pipes.yahoo.com/ Yahoo! Pipes] let's users create multi-source data mashups in a web-based visual environment
* [http://www.xmlsh.org xmlsh] A shell for manipulating xml based on the unix shells. Supports in-process multithreaded xml and text processing pipelines.
* [http://www.gerixsoft.com/blog/xslt/xml-pipeline-xslt]{{Dead link|date=July 2025 |bot=InternetArchiveBot |fix-attempted=yes }} How to implement XML Pipeline in XSLT
* [http://xmlcalabash.com/ Calabash is an implementation of XProc]
* [https://community.emc.com/community/edn/xmltech/ Calumet] is an XProc implementation from EMC
* [http://code.google.com/p/quixproc QuiXProc] is an XProc implementation of Innovimax
{{DEFAULTSORT:Xml Pipeline}}
[[Category:XML-based standards]]
[[Category:Inter-process communication]]
|