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:CRAWFORD, Mark (MCRA@lmi.org)
Date:Mar 17, 2003 8:28:50 am
List:org.oasis-open.lists.ubl

Dave C. wrote -

The most difficult problem is with mapping (in UML) a global element to the namespace in which it is declared. The global element may be declared in a different schema module, and possibly a different XML namespace, than the complexType or simpleType on which it is based. Some XML Schemas (e.g. ACORD) use one very large schema file in one namespace; global elements are quite straightforward here. Other schemas (e.g. OAGIS 8.0 and 8.1) use a very large number of schema modules to support reuse and abstraction, which greatly complicates mapping global elements to schema modules and namespaces. UML has not yet settled on a rule for determining schema document modularity and their namespace assignment.

But if we are consistent across schema modules on a unique one-to-one association of an element to a type, then this does not appear to be a problem.

Dave C. wrote -

My interest in NDR recommendations is more general than UBL. I'm looking for a set of industry best practices. I am still testing alternative approaches to support global element mapping to UML and expect to find a workable solution, but use of local elements (or restricted use of global elements in some situations) simplifies the mapping and will reduce long-term maintenance of UML models used for system integration.

So I read this to mean that local makes it easier, but global works. Given the benefits of a single, semantically unambiguous universal business language, global still seems the way to go.