• To: <xml-dev@l...>
• Subject: Re: What's wrong w/ nested elements?
• From: "Bryce K. Nielsen" <bryce@s...>
• Date: Mon, 7 Jun 2004 18:47:20 -0600
• References: <656BE56E7D48F6419054CC1C81114927014CD367@e...>

<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

• References:
  • RE: What's wrong w/ nested elements?
    • From: "Jain, Rajnish" <rjain@x...>

• Prev by Date: Re: The triples datamodel -- was Re: SemanticWeb permathread, iteration n+1
• Next by Date: Re: Bruce Perens and yet more patents
• Previous by thread: RE: What's wrong w/ nested elements?
• Next by thread: Conformance Testing and Schemas (WAS RE: The triples datamodel -- was Re: Sema ntic Web permathread, iteration n+1)
• Index(es):
  • Date
  • Thread