xml-dev - RE: XML Schemas: Best Practices

["Bullard, Claude L (Len)" <clbullar@ingr.com>]

Consider that aggregation usually takes place in 
context of a process and that the requirements of 
the process dictate the use of the components, not 
the arbitrariness of a global namespace.  A user 
will have the component or will fetch it.  The 
more problematic situation is namespace mapping 
to GUIDs and those who use that approach will 
not want to use chameleons.  A chameleon changes 
colors to a background in response to a stimulus 
event.  In the context of service routing, one 
assumes the right aggregate is created and the 
services needed are available apriori.  Global 
aggregation that does not consider the process 
space definition is not realistic for any case 
I can think of.

Len Bullard
Intergraph Public Safety
clbullar@ingr.com
http://www.mp3.com/LenBullard

Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h


-----Original Message-----
From: Roger L. Costello [mailto:costello@mitre.org]

Okay, so we have come up with two limitations on the Chameleon Namespace
design:

1. Name collisions.
2. Tools to process the no-namespace components.