OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: [xml-dev] ambiguous content model

[ Lists Home | Date Index | Thread Index ]

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.





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS