Lists Home |
Date Index |
Tim Bray [mailto:email@example.com] wrote:
> Rich Salz wrote:
> > Sure, if your business application has ben (re)written to understand
> > and isn't, instead, legacy code fronted by an XML wrapper.
> Good point. Any wrapper that includes XSD validation is going to be
> awfully thick "wrapper" though. And a *lot* of people are writing
> that read in XML right now today; I wonder how many of them are
> including an XSD valudation step? -Tim
But even when it's written from the ground up to understand XML, it
places a greater burden on the developer to get the XML reading code
right. For example, if the developer is using DOM+XPath and uses a "//"
somewhere where they should've used a "/", they might get an incorrect
value somewhere that still makes sense to your back-end.
Aaron Skonnard <http://skonnard.com>, DevelopMentor <http://develop.com>
Essential XML Quick Reference available online in PDF format...
Before you criticize someone, you should walk a mile in their shoes.
That way, when you criticize them, you're a mile away and you have their