Default chunking demo input/output document

You are seeing a modest XML document from MT's own site, which started out as plain XHTML.

The pipeline you ran this through to get here (showcase/chunk) is a pipeline which splits its input into chunks, validates them, and uses the schema type information to highlight certain values. It is intended as a model for a class of applications where schema-based information is needed, but schema validation of the whole document is impractical because of size.

This pipeline exploits the power of Markup's pipeline engine, which connects operations with a high-efficiency infoset bus, and caches schemas, stylesheets and other static resources. You can see the pipeline description which was compiled to produce this pipeline for the server to run.

Of particular note in this case is the use of MT Pipeline's powerful viewport facility, which allows selected sub-parts of a document to be processed efficiently within a sub-pipeline, as if they were the entire document.

Some of the links from this page are displayed in colour as the result of the schema-type-dependent processing in the stylesheet applied by the pipeline. A real application would of course do something more interesting.

Use this pipeline on your own data

It's probably easier to use the form for this pipeline, but if you want to construct a URL to use your own schema document (and you must specify one -- the schema caching mechanism does not look ahead to find xsi:schemaLocation hints) or stylesheet on your own data, replace http://www.markup.co.uk:8888/yourChunks.html in the URL you're fetching with a full URL (http: or https:) for the XML page you want to process and replace http://www.markup.co.uk:8888/xhtml1-strict.xsd in the URL you're fetching with a full URL (http: or https:) for a schema document corresponding to the schema you want to validate with, likewise replace http://www.markup.co.uk:8888/yourChunk.xsl, and try again.

Please note that this is not a schema development tool -- if your schema document is invalid, or doesn't correspond to a valid schema, you won't get much in the way of error messages - use XSV online to debug your schemas.