Catching ideas

…and how else than in XProc:

<p:declare-step xmlns:p="http://www.w3.org/ns/xproc">

  <p:output port="result" sequence="true"/>

  <p:try name="announcement">
    <p:group>
      <p:identity>
        <p:input port="source">
          <p:inline>
            <p xmlns="http://www.w3.org/1999/xhtml">I am happy to
              announce the availability of version 1.0.8 of EMC
              XProc Engine, EMC's XProc processor implementation.
              The processor is free for developer use and can be
              downloaded - together with other XML tools - from
              the EMC XML Developer Community website.</p>
          </p:inline>
        </p:input>
      </p:identity>
    </p:group>
    <p:catch>
      <p:identity>
        <p:input port="source">
          <p:inline>
            <p xmlns="http://www.w3.org/1999/xhtml">This is the
              first public release of the processor. Note that
              while version 1.0.8 supports most of the required
              features of XProc, the implementation is not yet
              complete.</p>
          </p:inline>
        </p:input>
      </p:identity>
    </p:catch>
  </p:try>

  <p:identity name="feedback">
    <p:input port="source">
      <p:inline>
        <p xmlns="http://www.w3.org/1999/xhtml">We are looking
          forward to your feedback - please use the
          EMC XML Developer Community forum (or the xproc-dev
          mailing list) for any comments, suggestions, feature
          requests, or bug reports.</p>
      </p:inline>
    </p:input>
  </p:identity>

  <p:http-request name="download">
    <p:input port="source">
      <p:inline>
        <c:request xmlns:c="http://www.w3.org/ns/xproc-step"
          method="GET"
          href="https://community.emc.com/community/edn/xmltech"/>
      </p:inline>
    </p:input>
  </p:http-request>

  <p:wrap-sequence name="features" wrapper="features">
    <p:input port="source" xmlns="http://www.w3.org/1999/xhtml">
      <p:inline>
        <para>XProc Engine implements most of the required
          features of the XProc specification. For an overview
          of the supported features, and the progress of the
          implementation, see the XProc Test Suite website.</para>
      </p:inline>
      <p:inline>
        <para>Plug-ins can extend the processor and customize
          the default behavior or provide new functionality, such
          as extension XProc steps.</para>
        <para>The XProc Engine distribution comes with a number
          of plug-ins that can be used with the processor.
          Software developers can use the XProc Engine API to
          create custom plug-ins.</para>
      </p:inline>
      <p:inline>
        <para>Its Java application programming interface makes
          it easy to embed the XProc Engine in other Java
          applications.</para>
      </p:inline>
      <p:inline>
        <para>Its Java application programming interface makes
          it easy to embed the XProc Engine in other Java
          applications.</para>
      </p:inline>
      <p:inline>
        <para>XProc Engine provides an interface for running
          XProc pipelines from the command-line.</para>
      </p:inline>
      <p:inline>
        <para>XProc Engine can be integrated with the EMC
          Documentum xDB XML database (via a plug-in). The
          plug-in provides a number of xDB-specific XProc
          steps, and allows developers to combine the benefits
          of a state-of-the-art native XML database and XProc.
        </para>
      </p:inline>
    </p:input>
  </p:wrap-sequence>

  <p:compare>
    <p:input port="source">
      <p:document
        href="http://tests.xproc.org/results/calumet/report.xml"/>
    </p:input>
    <p:input port="alternate">
      <p:document
        href="http://tests.xproc.org/results/calabash/report.xml"/>
    </p:input>
    <p:documentation>
      <p xmlns="http://www.w3.org/1999/xhtml">How does it compare
        to the other XProc processor? :)</p>
    </p:documentation>
  </p:compare>

  <p:identity>
    <p:input port="source">
      <p:pipe step="announcement" port="result"/>
      <p:pipe step="feedback" port="result"/>
      <p:pipe step="download" port="result"/>
      <p:pipe step="features" port="result"/>
    </p:input>
  </p:identity>

</p:declare-step>