[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [relax-ng] Re: RELAX NG + Schematron
> The issue isn't the syntax but the fact that the Schematron assertion > specifies an error message to be given to the user. With the > use-schematron-to-guide-RNG approach, it may be ambiguous which Schematron > constraint was not satisfied, so there's no way to determine which message > to the user. If you just have attribute (x:require) with no message, then > that doesn't matter. I'm not sure how it will become ambiguous. Any example? > Isn't checking this going to be exponential with something like > > (a? & b? & c? & ...)* > > ? Hmm, I think the algorithm can be further modified to exploit the disjointness of interleave. We don't need to compare different branches of interleaves, and this should prevent the explosion. regards, -- Kohsuke KAWAGUCHI +1 650 786 0721 Sun Microsystems kohsuke.kawaguchi@sun.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC