Title: RE: [ubl-lcsc] Newest version of the OO-design position paper. Hello Mark, human-readable is very efficient for defining and building of applications and interfaces. The objects in the oo-design-paper are human-readable enough for that. But the structure is simple an fits with our definitions. Because we said that all components must be reusable and the structure must be align on the instructions of ebXML CCTS. And I think that a Header or Summary is not a reusable and logical grouping of data. In addition, we defined that the complete path-name of the assembled objects will be identical to the dictionary entry name. If you have hierachy like a Order , Header for the collection of all header information, Parties for the collection of all parties, BuyerParty , Communications for the collection of all communication facilities and Telephone.Identfier than the dictionary entry name will become Header Parties BuyerParty Communications Telephone.Identification.Identifier . I guess, this will be completley against the definition of a dictionary entry name. In oo-design-paper way, the path-name will be the dictionary entry name Order BuyerParty Telephone.Identification.Identifier . I think, this is semantically clear. Or, I am wrong? Kind regards, Gunther