it is back to help and samples for me. I am very new at this whole XML thing. We
added support for xml files in our software so I read up on XML and how the
files are formatted. We needed to split down the files so I read up and learnt
XSLT. I will look up sax filtering and see what I can do.
> It seems that my theory
of using XSLT to split down these large documents with XSLT is going to have
to be replaced by hand writing something that handles the data as text instead
Very often that job
can be tackled quite easily using a SAX
name Saxon is in fact derived from SAX. Saxon started life as a Java library
that sat on top of SAX, scanning the document seqentially, and firing off
element handlers that matched particular patterns in the input. Later there
were options to process either serially or in memory, and the "in-memory"
option was extended to support XSLT. Then it became too difficult to support
two modes of operation in the same product. For a while I offered "preview"
mode, which was the ability to fire off templates while the document was being
loaded; but that too eventually became unsupportable because it really didn't
fit the functional programming model.