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:]
> 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.
