[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Namespaces,W3C XML Schema (was Re: ANN: SAX FiltersforNamespaceProce
> > complexity than this). Using local types made schema design and > > maintenance much simpler than if every element name in the schema had to > > be uniquely typed. But it it also makes it harder for me to comprehend > > correctly even the relatively small (1-2Kb) messages that we typcially > > deal with. > > Maybe you do not use attributes, but if you do, do you have problems > comprehending them because typically they are not in a namespace? Why are > local element types different? > I do use attributes - the difference is simply complexity. An attribute's type is determined by its context, which is always its parent. Local elements can be layered all the way up to a single global root element. If you have n layers of local elements above an element whose type you are tying to determine, you have n possible determining contexts, of which n-1 are themselves of indeterminate type. In other words attributes are self-evident, but local elements require either schema-aware tools, schema coding standards or possibly both. Francis.
|
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
|