Note: The change in the XQuery for this extract was just the deletion of the ‘step’ operator, this change rendered the XQuery invalid because we’re left with an invalid QName ‘xq:docxq:module’; unsurprisingly, XMLSpectrum doesn’t do too well tokenizing XQuery that won’t compile – hence the unexpected output where the invalid QName is split into two.
span element in the HTML source represents an XQuery token, each span element has a class attribute that holds upto 2 space-separated values:
- Token Type – always present, the type of XQuery token, for example step is used to denote an XQuery
- Part Identifier – posible values: partA or partB, indicates the A or B origin of the token, only present when no match is found for the token in the other file.
Now we’ve previewed the output, its time to look at the pipeline configuration and filters used to help produce this:
The Pipeline Configuration
The Pipeline Configuration file, referenced in the Ant file using its ‘xquery’
id attribute, is used to declare the input and output filters for the comparison, in this case there is just one input filter and one output filter: