Re: [ubl-ndrsc] RE: [ubl-lcsc] Newest version of the OO-designposition paper.

I've found it very helpful to use XSD group or attributeGroup to define reusable content in an OO model, and these do not create any additional containers in the XML instance.
If I use UML to define the schema model, I assign <<XSDgroup>> or <<XSDattributeGroup>> stereotypes to the UML classes, then my schema generator produces the corresponding constructs in the schema.
When I reverse engineer existing XSD into UML, any <group> or <attributeGroup> definitions become appropriately stereotyped classes in the UML model.
With this approach the UML model is much more readable as a conceptual model of the vocabulary, but the XML instance is still flat.
Similarly, when this more structured UML/OO model is used to generate relational database schema or Java processors, the groups create a more componentized Java application without requiring container elements in the XML instance.
Gunther, is this what you mean by "partial object classes"?
Regards, Dave Carlson