<snip/> > For that, we could use a common way of locating errors. I'm afraid that > getting the physical locations from Schematron is too difficult a task and > the result might not quite match the physical locations by Xerces. On the > other hand, Schematron can reliably produce 'logical' locations, something > like 'canonical XPath' to the node where the violation occurred. E.g. > '/root/a[1]/b[23]' meaning the 23rd 'b' child of the first 'a' child of > 'root'. (Things are more difficult in the presence of namespaces, but still > tractable.) > > How difficult would it be to extend Xerces to: > (i) Produce 'logical' locations in terms of 'canonical' XPaths > as described above. > (ii) Pass these locations to XMLErrorReporter. > Then I could set up a filtering XMLErrorReporter that would let me > gradually move violation reports from XML Schema to Schematron.
God loves me - someone else wants exactly the same as I want :-)) ...almost... I was always wondering why the xpath isn't passed with errors!! But I'd like go even a little further... I like to have some kind of an error object/facet whatever which tells what failed not only as a human readable message... so one can process it programmatically.... -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
