W3C home > Mailing lists > Public > xproc-dev@w3.org > December 2011

Validation, error reports, and printing to stderr

From: Norman Walsh <ndw@nwalsh.com>
Date: Sat, 31 Dec 2011 16:03:13 -0500
To: XProc Dev <xproc-dev@w3.org>
Message-ID: <m2k45clai6.fsf@nwalsh.com>
After some investigation, I've got a couple of pipelines that treat
XSD and RNG validation like Schematron validation: if there's an error
you get a non-empty error report, but the step succeeds (if you want
it to). If there's no error, you get an empty error report.

That's all well and good, but following David Cramer's recent
messages, I think there's still something missing: how do the errors
get reported?

I'm not sure what the right answer is. I could add an option that
makes validation errors print to STDERR (but what about other errors)?
I could add a step that prints to STDERR and use that in the pipeline.

The errors used to go to STDERR, I think, but in environments like
oXygen, that's the wrong thing, calling the error listener is the
right thing.

I dunno what to do.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
Lead Engineer
MarkLogic Corporation
Phone: +1 413 624 6676
www.marklogic.com

Received on Saturday, 31 December 2011 21:03:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 31 December 2011 21:03:45 GMT