Cart
[Home] [By Thread] [By Date] [Recent Entries]
Delimit the application and the environment. Your example is one of an environment (shipping and mail systems) that have local differentiators (eg, language, geo-locator naming, etc) but have a low rate of change. The application may be changing more rapidly or have a higher degree of differentiation. By example, both the city architecture and the city location are related by geo-systems. However, while interdependent, the rate of change of the river, tectonic plate, forestry, etc. are much lower than the rate of change of buildings created and demolished. The schema is a means to define an environment and a means to validate/process/shape exchanges within that environment. Because of the rates and the local variations, a good designer will decouple the schemas and schedule their application based on recognition of events within a system of event types. Len Bullard Intergraph Public Safety clbullar@i... http://fly.hiwaay.net/~cbullard/lensongs.ram Ekam sat.h, Vipraah bahudhaa vadanti. Daamyata. Datta. Dayadhvam.h -----Original Message----- From: KenNorth [mailto:KenNorth@e...] Walter, << the salient rules are those most exactly specific, perhaps unique, to the particular occasion and environment << That, precisely, is why the schema actually implemented in a processing instance is, as I described it, effectively a schema of the relationships of the input data, Not every application view of data is unique, nor are schemas simply for processing inputs. *************************************************************************** This is xml-dev, the mailing list for XML developers. To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev List archives are available at http://xml.org/archives/xml-dev/ ***************************************************************************
|
