- From: Norman Walsh <ndw@nwalsh.com>
- Date: Tue, 03 Jan 2012 10:02:43 -0500
- To: XProc Dev <xproc-dev@w3.org>
- Message-ID: <m2sjjwrfqk.fsf@nwalsh.com>
David Cramer <david@thingbag.net> writes: > On 01/02/2012 09:29 AM, Norman Walsh wrote: > ... > >> 1. Abort on validation error 2. Silently ignore validation error 3. >> Ignore validation errors, but make sure that the errors are >> reported to the user >> > > ... > >> Does this cover all of the use cases? (I'm not asking if you think >> this is a *good* solution, I'm just trying to see if we've >> technically covered all the bases or if there's still more that I'm >> not getting.) > > Just to be clear, there's also #4, "Report errors to the user AND > abort", correct? If you just leave the validation step outside of a p:try, that's the intended behavior. > I need #4 with the ability to pass in a parameter at build time to do > #3 instead (I'm not wild about the idea, but the users say they want it). That should be possible with an appropriate p:choose. > The only other thing I recall being mention in the previous thread on > this subject was the ability to transform the XML version of the list > of errors, but I think that was already covered with p:error. I think so too. Be seeing you, norm -- Norman Walsh Lead Engineer MarkLogic Corporation Phone: +1 413 624 6676 www.marklogic.com
Received on Tuesday, 3 January 2012 15:05:51 UTC