[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Improving 7.1
Unfortunately I discovered this approach doesn't work, because it disallows <group> <attribute name="foo"> <data type="token"/> </attribute> <attribute name="bar"> <data type="token"/> </attribute> </group> Using exclusions cannot distinguish the fact that the <data> elements are inside <attribute>. Thus I think inference rules are the most straightforward way to describe this restriction. --On Friday, July 27, 2001 12:33 PM -0700 Kohsuke KAWAGUCHI <kohsuke.kawaguchi@eng.sun.com> wrote: > >> foo - bar >> >> to indicate something that matches foo but doesn't contain any bar >> descendants. Then I think this restriction can be described by saying >> that the content of a group or interleave element not inside a list >> element must match >> >> (pattern - data - value) (pattern - data - value) >> | pattern (pattern - text - data - value) >> | (pattern - text - data - value) pattern > > The following might be better > > (pattern - {data,value}) (pattern - {data,value}) > | pattern (pattern - {data,value,text}) > | (pattern - {data,value,text}) pattern > > At first I was confused because A-B is whether left-associative or > right-associative. > > > 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