• To: jordan@f...
• Subject: Re: ambiguous content model
• From: Anthony Williams <anthony.williams@h...>
• Date: Wed, 11 Jun 2003 13:09:49 +0100
• Cc: xml-dev@l...
• In-reply-to: <aca4476479a558e8e715613191dd97c23ee71403@f...>
• References: <aca4476479a558e8e715613191dd97c23ee71403@f...>

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.

• Follow-Ups:
  • Re: ambiguous content model
    • From: Eike Jordan <jordan@f...>

• References:
  • ambiguous content model
    • From: Eike Jordan <jordan@f...>

• Prev by Date: ambiguous content model
• Next by Date: Re: JSR 225 - XQJ: JDBC for XQuery
• Previous by thread: ambiguous content model
• Next by thread: Re: ambiguous content model
• Index(es):
  • Date
  • Thread