[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: What's wrong w/ nested elements?

• To: "'Bryce K. Nielsen'" <bryce@s...>, xml-dev@l...
• Subject: RE: What's wrong w/ nested elements?
• From: "Bullard, Claude L (Len)" <len.bullard@i...>
• Date: Mon, 7 Jun 2004 14:50:36 -0500

Some hit the same wall here.  Hence, the local copies of a competitor's 
product.

I understand Dare's explanation as to how, but not why.  It seems 
shortsighted.

len


From: Bryce K. Nielsen [mailto:bryce@s...]

> The tool is okay w/ element (c) being contained under more than one
> parent. And even (b) can be present more than once under either (a1) or
> (a2) but not under both (a1) and (a2)simultaneously.
>

Actually, it wouldn't accept that either, it's just the parser errored out
on the <b> element before it could find a <c> element. There is no way to do
this within VisualStudio, it's a limitation within the tool. They are trying
to make the schema fit into a relational model, which means imposing
limitations on the schema language.

• Prev by Date: Re: What's wrong w/ nested elements?
• Next by Date: RE: What's wrong w/ nested elements?
• Previous by thread: RE: What's wrong w/ nested elements?
• Next by thread: RE: What's wrong w/ nested elements?
• Index(es):
  • Date
  • Thread