[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Issue: references to an external grammar
Is the issue here simply whether we want a shorthand for <grammar> <include href="..."> <start> <ref name="..."/> </start> </include> </grammar> ? ----- Original Message ----- From: "Murata Makoto" <mura034@attglobal.net> To: <relax-ng@lists.oasis-open.org> Sent: Thursday, July 05, 2001 3:38 PM Subject: Issue: references to an external grammar > Kawaguchi-san raised this question long time ago. <externalRef> > references to start elements only and cannot reference to other named > patterns. Meanwhile, <include> expands all definitions in the > referenced grammar, and may cause conflicting <define>s. > > Cheers, > > Makoto > > James wrote: > >Kawaguchi-san wrote: > >> The only workaround I found is > >> > >> <element name="topLevel"> > >> <grammar> > >> <include href="relaxCore.trex" /> > >> <start combine="replace"> > >> <ref name="ref.label" /> > >> </start> > >> </grammar> > >> </element> > > > >That is the intended solution to the problem. > > > >> Which is quite a lot of typing (at least for me). > > > >I suppose it wouldn't be hard to add a shortcut: > > > ><element name="topLevel"> > > <include href="relaxCore.trex" start="ref.label"/> > ></element> > > > >> I believe this also > >> slows down grammar parsing because validator has to read relaxCore.trex > >> every time I use <include> pattern. > > > >It is easy for a parser to avoid rereading for an include at the pattern > >level. It's a bit harder for a grammar level include. > > > >> Is this worth raising as an issue? > > > >I guess so. > > > ------------------------------------------------------------------ > 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