[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: XML Schemas: Best Practices
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@i... http://www.mp3.com/LenBullard Ekam sat.h, Vipraah bahudhaa vadanti. Daamyata. Datta. Dayadhvam.h -----Original Message----- From: Roger L. Costello [mailto:costello@m...] 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.
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|