[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Partyin' like it's 1999
Let me get one of these first, so I have a place to preserve my insanity. http://www.kleinbottle.com/ I don't know of a way to measure the pain, and one can't just rely on the reactions of the developers because like camels, people react negatively to load in general. The refactoring of SGML was sellable for reasons that went beyond the technical. I'm not too sure that those reasons pertain to XML which was sold as anythingToAnything so everyone felt they could benefit. Once one starts 'removing features', one creates a subset. If anyone wants to add features, it's not. Actually, redesign for simpler syntax has been done. The VRMLers started that way. Neill Kipp designed a simpler SGML than XML. So really, this is a question of timing at the large scales, and at the inner scales, the influence of individuals and the relationship of a change like this to their company's strategies. This is about framework competition, not syntax. There is no money in the core. XML doesn't have an equilibrium. It's the needle. len From: Michael Champion [mailto:michaelc.champion@g...] That's one question that needs to be answered (or at least guessed at) before doing anything: how much short term pain would actually be caused? My own guess is that most end user application builders have avoided the crufty stuff, whether or not it is legal in the specs. The people complaining at the Sells' conference are the poor suckers trying to implement the specs because their customers want 'standards' in the abstract but are not clamoring for the nasty bits of the actual specs. The purpose of any refactoring would be to cut at the inflection points beyond which a given feature causes more complexity pain than empirical benefit in the real world. I grant that will be hard to determine! > Why > not toss out this whole 'pointy' thing and get > back to a clean one pass parse based on proper > data definitions, white space, end of lines, > and curlies (let's Do C!)? Sooner or later someone is going to do just that. The question is whether we want to do selective breeding to keep the specs in synch with changing realities or wait for punctuated equilibrium to toss it out and start over. > There comes a point where the business execs and > the data owners look back and say "good enough" > and push back because the costs of reinnovation > are restarts in too many places. OK, automobiles, television, most home appliances, homebuilding technology ... lots of things have been essentially "good enough" for decades. I'm trying to think of a computer-related technology that exhibits this (mainframes? COBOL?). In the technology industry, who's not busy bein' reborn is busy becomin' a low margin commodity. > > Are there > any non-XML geeks, Maybe not, but if "Developers Hate XML", who will stand up for it when its equilibrium gets punctuated?
|
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
|