Cart
[Home] [By Thread] [By Date] [Recent Entries]
> From: "Mike Champion" <mc@x...> > > > I'm under the impression that managing schema evolution > > is a Hard Problem; lots of the complexity > > of WXS is there to make the problem more manageable by employing > > notions of partial re-use that come from the OO world, but it's > > not clear to me that best practices have emerged for using it. > > Hard Problems are often merely inadequately analysed problems. > For example, why should we expect that "Schema evolution" can be > be solved by a single mechanism? > > There are many ways that a schema may evolve, and different mechanisms > may be suitable for each way. For example, change over time, > change between locales, change between processes in pipelines, > change depending on what the user is interested in, minor changes/major > changes. <AOL>Very well said</AOL> I'm surprised to come across the idea of schema evolution as a monolithic problem. I am doubly surprised to see RSS held up as an example of the difficulty of schema evolution. RSS is but example of politics and carelessness. All social science, and not a drop of computer science to spare. -- Uche Ogbuji Fourthought, Inc. http://uche.ogbuji.net http://4Suite.org http://fourthought.com Python&XML column: 2. Introducing PyXML - http://www.xml.com/pub/a/2002/09/25/p y.html The Past, Present and Future of Web Services 1 - http://www.webservices.org/ind ex.php/article/articleview/663/1/24/ The Past, Present and Future of Web Services 2 - 'http://www.webservices.org/in dex.php/article/articleview/679/1/24/ Serenity through markup - http://adtmag.com/article.asp?id=6807 Tip: Using generators for XML processing - http://www-106.ibm.com/developerwork s/xml/library/x-tipgenr.html
|
