[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Alternative algorithm to restrict use of data/string in patterns.
Kohsuke KAWAGUCHI wrote: > > This proposal is a rewrite of > http://lists.oasis-open.org/archives/trex/200104/msg00031.html Thanks. Thistime, I understand. <notAllowed/> is not mentioned, but this can be removed by simple preprocessing. Kohsuke KAWAGUCHI wrote: > case: p == <interleave> p1 p2 </interleave> > check( p1, fpds ) > check( p2, fpds ) > if( p1 contains <data/> or <string/>, > && p2 contains <anyString/> or <element />, or viceversa) > this pattern is illegal! Is this correct? The following patterns should be illegal, but your algorithm does not say so. <interleave><string>abc</string><string>asdf</string></interleave> <interleave><data type="xsd:integer"/><string>13</string></interleave> Cheers, Makoto
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC