Re: [xml-dev] What's wrong w/ nested elements?

<RJ>
I noticed the problem is specifically w/ complex elements (such as <b>)
that have their own children. Such elements map to their own relational
tables. However, simple elements (such as <c>) are merely members of
other relational tables and probably that's why the tool doesn't mind
their reuse under different parents.
</RJ>

Yeah, actually, that's probably it. Elements with child nodes are translated
into "tables" and the other elements and attributes are "fields". Basically,
the tool treats every complex type (with complex content) as a "global"
element, no other elements can have the same name.

Bryce K. Nielsen
SysOnyx, Inc. (www.sysonyx.com)
Makers of xmlLinguist, the EDI-to-XML Translator
http://www.sysonyx.com/products/xmllinguist