[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Issue(?): <list> in <list>
So the problem is, as in earlier discussions, the rule does not allow it in that it does not match the bad pattern; however, an implementation is not obligated to report this as an error? -Mike -----Original Message----- From: Kohsuke KAWAGUCHI [mailto:kohsuke.kawaguchi@eng.sun.com] Sent: Thursday, June 14, 2001 4:50 PM To: Michael Fitzgerald; RELAX NG ML Subject: Re: Issue(?): <list> in <list> By the way, the reply of yours didn't reach the list; it just reached me. > I think Kohsuke is right, of course. Chances are the "smart" inference rule > > E; ns |- { }; split( s ) =~ p => k; kr > --------------------------------------------- > E; ns |- { }; s =~ <list> p </list> => k; kr > > already forbids this. How? No. Firstly, the inference rules tell that certainly patterns like the following do not match anything: <list> <list> <data type="int"> <data type="int"> </list> </list> But it doesn't say whether the processor should report an error for such a grammar or not. Secondly, sometimes a nested <list> accepts something. For example, <list> <list> <data type="int"/> </list> </list> accepts "5". regards, -- Kohsuke KAWAGUCHI +1 650 786 0721 Sun Microsystems kohsuke.kawaguchi@sun.com ------------------------------------------------------------------ To unsubscribe from this elist send a message with the single word "unsubscribe" in the body to: relax-ng-request@lists.oasis-open.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC