atom feed23 messages in org.oasis-open.lists.ublRe: [ubl] Global vs. Local -- Gunther...
FromSent OnAttachments
Jim WilsonFeb 25, 2003 10:26 am.zip
Dave CarlsonFeb 25, 2003 4:41 pm 
Stuhec, GuntherFeb 25, 2003 9:58 pm 
Eve L. MalerMar 12, 2003 7:40 am.doc
Eve L. MalerMar 12, 2003 7:54 am.doc
Stuhec, GuntherMar 14, 2003 4:37 pm 
Eve L. MalerMar 14, 2003 5:33 pm 
CRAWFORD, MarkMar 14, 2003 5:55 pm 
Dan VintMar 14, 2003 9:44 pm 
Eve L. MalerMar 15, 2003 4:46 am 
Stig KorsgaardMar 17, 2003 6:09 am 
Eve L. MalerMar 17, 2003 6:29 am 
Dave CarlsonMar 17, 2003 7:09 am 
Stig KorsgaardMar 17, 2003 8:11 am 
Stig KorsgaardMar 17, 2003 8:24 am 
CRAWFORD, MarkMar 17, 2003 8:28 am 
Dave CarlsonMar 17, 2003 8:55 am 
robe...@gerbercoburn.comMar 17, 2003 9:01 am 
CRAWFORD, MarkMar 17, 2003 9:06 am 
Dave CarlsonMar 17, 2003 9:13 am 
Eve L. MalerMar 19, 2003 6:16 am 
Dave CarlsonMar 19, 2003 7:07 am 
Dave CarlsonMar 19, 2003 7:18 am 
Subject:Re: [ubl] Global vs. Local -- Gunther's Recommendation
From:Eve L. Maler (eve.@sun.com)
Date:Mar 14, 2003 5:33:15 pm
List:org.oasis-open.lists.ubl

I don't doubt that local elements are more OO-like in that they scope elements to a type (class). But...I don't understand the reasons you've given for saying that local elements are therefore preferred. (My lack of understanding may be entirely due to my not being an OO developer, so please forgive any clueless questions below.)

What is a pseudo-class, and why must one be created for every global element? Multiple global elements could be bound to a single type/class, just as multiple local elements with the same name could be bound to a single type: no explosion of types. Are you saying that with OO processing you can't distinguish between multiple elements that are bound to the same type because you only ever look at type information? In that case, isn't the problem the same whether you have local or global elements?

And what is the packaging/maintenance barrier to OO class-based processing of complex types when global elements are used?

Eve

Stuhec, Gunther wrote:

Hello all,

I have spoken about the topic "Global versus Global" with Garret Minakawa (Oracle), Frank Vandamme (SWIFT) and Dave Carlson. All three colleagues said to me that for implementation reasons will be the "Venetian Blind" design much more better as the "Garden of Eden" design. Because the "Venetian Blind" design aligns to the OO (UML) model and "Garden of Eden" does not.

That means, every type in "Venetian Blind" represents an object class and this can be used in UML class diagrams as well as in object oriented-programming language in the same manner. In object-oriented programming places a great deal of emphasis on packaging classes according to their services. The types in the venetian blind design represents the package structure and this organizes the code and facilitates modularity and maintenance. Therefore, the components of venetian blind are highly cohesive and have a high coupling. We do see how this is very OO-like, and how an OO (UML) model might map directly to this design. This kind of principle will be used many XML-APIs, like JAXB.

In "Garden of Eden" must be created a pseudo-class for every global declared element. And this means an additional maintenance and redundant modularity of the UML models as well as OO-programming. And this might be not directly the OO modelling effort. Although is some additional work necessary by developing with APIs.

Kind regards,

Gunther