[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: QNames
I think Makoto's proxy idea is very appealing. Rather than introducing a new concept, though, couldn't we just use the prefix as the proxy name and then just overload the ns attribute? Consider: <grammar xmlns:e="http://www.example.com/e" proxy="yes"> <start> <element name="addressBook" ns="e"> <zeroOrMore> <element name="card" ns="e"> <element name="name" ns="e"> <text/> </element> <element name="email" ns="e" > <text/> </element> </element> </zeroOrMore> </element> </start> </grammmar> It's less verbose. It overloads (so to speak) the ns attribute so that it could contain a namespace URI or prefix as a proxy name. proxy is just a flag...perhaps unnecessary. Casting about as usual, Mike MURATA Makoto wrote: >3. The proxy attribute >1) Namespace declarations >A grammar element begins with namespace delclarations (for the lack of a better name). >A namespace declaration declares a namespace URI and attaches a proxy to it. >E.g., ><grammar> ><namespace name="http://www.example.com" nsproxy="e"/> ><start> ><element name="addressBook" nsproxy="e"> > <zeroOrMore> > <element name="card" nsproxy="e"> > <element name="name" nsproxy="e"> > <text/> > </element> > <element name="email" nsproxy="e" > > <text/> > </element> > </element> > </zeroOrMore> ></element> ></start> ></grammmar> > >Cheers, > >Makoto
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC