import of XSD documents into UML

[don work]

LAst night I tried to import an XSD file into EA, to study the structure described there-in. (The actual file was the XSDprofile.xml which defines XSD schema to EA - a bit recursive, but not relevant.)

The surprising result was that the various classes in the profile nested under each other. I didn't even know that was possible. Is it even valid UML?

I was expecing the nesting relationships of XSD to be represented by composition relationships, in a nice clear diagram.
I note that the palette for the XSD profile doesn't even include aggregation or composition. Despite this, in the past, I have used these relationships to successfully generate XSD files from UML models.

Any comments from sprx about the philosophy behind this?
I would prefer a fully UML diagrammatic way of showing nesting relationships, rather than "classes within classes" in the browser.

Don

[Geert Bellekens]

Don,

Although the "nested classes" principle may be arguable, it is in fact valid UML.
I think they do it this way to ensure the "Tree like" graph when importing an XSD. When using compositions they could end up having either name conflicts, or elements having different "parents".

Geert