My personal inclination is to output only the message that was asked for. The API may want to tell us more than that -- perhaps to help folks who are writing XSLT debuggers? -- and I've no objection to folks plugging in an error reporter which includes that info. I don't even have a very strong opinion on whether that or the bare message should be the default as shipped, as long as the bare version is available as default by setting the appropriate properties file and/or command-line option.
However: Given the problem of not always having a meaningful stylesheet URI, and not always having line breaks and the question of byte offsets versus character offsets, there's a real question about how to report the message's location. My own preference, when dealing with location in an XML file, is always to provide an XPath to the location since that avoids the latter issues at least... ______________________________________ "... Three things see no end: A loop with exit code done wrong, A semaphore untested, And the change that comes along. ..." -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (http://www.ovff.org/pegasus/songs/threes-rev-11.html)
