OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



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

[ Lists Home | Date Index | Thread Index ]
  • To: "Elliotte Rusty Harold" <elharo@metalab.unc.edu>
  • Subject: RE: [xml-dev] What's wrong w/ nested elements?
  • From: "Jain, Rajnish" <rjain@xl.com>
  • Date: Mon, 7 Jun 2004 11:01:16 -0400
  • Cc: <xml-dev@lists.xml.org>
  • Thread-index: AcRMlu3OCfuM9xu7Rc6NRx4mYGz4mQABZwdA
  • Thread-topic: [xml-dev] What's wrong w/ nested elements?


Thanks for your response. I can understand that this limitation (i.e.
can't nest a complex element under more than one parent) is probably in
the Microsoft tool. My example is right in front of us (thus there is no
broader issue in my application context):


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. 


Is their a way I can get the tool to behave correctly (I'm surely
missing something given how basic this is)? Or should I be using some
other editor?


-----Original Message-----
From: Elliotte Rusty Harold [mailto:elharo@metalab.unc.edu] 
Sent: Monday, June 07, 2004 9:44 AM
To: Jain, Rajnish
Cc: xml-dev@lists.xml.org
Subject: Re: [xml-dev] What's wrong w/ nested elements?

At 8:36 AM -0400 6/7/04, Jain, Rajnish wrote:

When I try to create an XSD for this XML using Microsoft Development
Environment 7.1, I get the following error:

Failed to Create a schema for this data file because:
Although this XML document is well formed, it contains structure that
Data View cannot display.
The same table (b) cannot be the child table in two nested relations.

Wondering why the containment relationship shown above is not valid for
an XSD? And what can I do to workaround this problem (I can't afford to
name mangle (b) everywhere it appears).

There's nothing here the W3C XML Schema Language can't handle. The
problem is with the Microsoft tool, not with XML. Try hand authoring a
schema and see if it accepts that, though given the error message I
suspect the problem may not be quite what you think it is. It sounds
like there might be broader issues in your application context that
prohibit this normally allowed structure.


   Elliotte Rusty Harold
   Effective XML (Addison-Wesley, 2003)

The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://www.oasis-open.org/mlmanage/index.php>


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS