Use Case 5.29/5.30 Pipeline

In theory, a streaming pipeline engine would stream the source and the
match matter used would have to stream as well.  The
/xhtml:html/xhtml:body xpath is easily matched in a streaming
processor.

<?xml version="1.0" encoding="UTF-8"?>
<p:declare-step xmlns:p="http://www.w3.org/ns/xproc"
    xmlns:c="http://www.w3.org/ns/xproc-step" version="1.0"
    xmlns:xhtml="http://www.w3.org/1999/xhtml">
    <p:input port="source">
        <p:inline>
            <html xmlns="http://www.w3.org/1999/xhtml">
                <head><title>Test Document</title></head>
                <body>
                    <div class="main">
                        <p>I can be arbitrarily large.</p>
                    </div>
                </body>
            </html>
        </p:inline>
    </p:input>
    <p:output port="result"/>
    <p:insert position="first-child" match="/xhtml:html/xhtml:body">
        <p:input port="insertion" xmlns="http://www.w3.org/1999/xhtml">
            <p:inline>
                <ul class="navigation">
                    <li><a href="/about/">About</a></li>
                    <li><a href="/xml/">Fantastic XML Stuff</a></li>
                    <li><a href="/cats/">Pictures of Cats</a></li>
                </ul>
            </p:inline>
        </p:input>
    </p:insert>
</p:declare-step>

-- 
--Alex Milowski
"The excellence of grammar as a guide is proportional to the paucity of the
inflexions, i.e. to the degree of analysis effected by the language
considered."

Bertrand Russell in a footnote of Principles of Mathematics

Received on Wednesday, 23 May 2012 18:42:09 UTC