Title: RE: [ubl-lcsc] Newest version of the OO-design position paper. Hello Arofan, XML is not a hype anymore. One of that reason is the complexity of the business documents. The most of the business documents have too much hierarchies. More than EDIFACT or ANSI ASC X.12 ever have. These many hierarchies makes the business documents very heavy or not at all processable. I know some projects, which had some big problems with the many hierarchies. - It was not possible to put this documents or part of these documents into the databases - It was a big effort to realize any application interface for processing these documents - Additionally, the effort to define a XSLT rule was much more higher as for defining any mapping rules for EDIFACT and Inhouse formats. I guess that the instances itself do not need any containers, because it is easier to define any interfaces for business objects. My suggestion is that we have partial object classes instead of unstructured containers. This partial object classes makes the building of structure much more controllable and the partial object classes are reausable, too. Otherwise, if we use containers , than we need some simple rules for the definition and processing in a automatic manner. One another import thing is, that the names containers impacts the dictionary entry name. If you use a container with the name header , than the dictionary entry name will be order.header.id instead of order.id . This representation is not ebXML CCTS compliant. Kind regards, Gunther