OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] Schema Evolution

[ Lists Home | Date Index | Thread Index ]

One of the answers that crops up to our problem (albeit internally within 
the project) of limiting the cost of change is to cut back on the rich 
structure we capture in our XML. In short instead of mapping our logical UML 
model into a very similar rich xml structure make the xml more like a 
Metamodel, and capture content rules outside of this Metamodel. The theory 
is that the underlying code of all applications would not change frequently, 
and that applications interpret the content as oppose to the structure.

My gut feeling is this is a smoke and mirrors answer, but wondered what 
others thought?




Want to block unwanted pop-ups? Download the free MSN Toolbar now!  


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS