[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: ambiguous content model
Eike Jordan writes: > which means that a table should consist of *one* title and *one-or-more* table-groups. > each table-group should consist of *one* title and *one-or-more* of > *integer-or-void*, *real-or-void* or *text-or-void* > with my approach i'm caught in a trap of an 'ambigous content model': > > <!ENTITY % real.mix "(real | void)"> > <!ENTITY % integer.mix "(integer | void)"> > <!ENTITY % text.mix "(text | void)"> > <!ENTITY % tableContent.mix " > ((%integer.mix;)+) | > ((%real.mix;)+) | > ((%text.mix;)+) > "> How about: <!ENTITY % tableContent.mix "(void*,( (real,(real|void)*) | (integer,(integer|void)*) | (text,(text|void)*) )?)"> which allows any mix of real-or-void OR any mix of integer-or-void OR any mix of text-or-void OR all-void (omit the question mark if all-void is not permitted) HTH, Anthony -- Anthony Williams Senior Software Engineer, Beran Instruments Ltd.
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|