Lists Home |
Date Index |
Derek Denny-Brown wrote:
> -----Original Message-----
> From: Jonathan Borden [mailto:firstname.lastname@example.org]
> Sent: Monday, January 14, 2002 2:59 PM
> To: Mike Champion; email@example.com
> Subject: [xml-dev] XML is easy, was: Re: SV: [xml-dev] XML=WAP? And
> XML is easy. It is the problems people are trying to address with XML
> are hard.
Given the amount of time I spend explaining 'simple' Namespace, XPath,
XSD, DTD, etc.. issues to people, I would fall heavily on the 'not easy'
side of the issue. It is 'easy' if you take the time to sit down and
study it and think about it.
I cannot speak for everyone, but from personal experience, I found that
using XML and related technologies simplified projects I was working on.
I think it is much like the speed of Microsoft Word. I would guess that from
day 1, the speed of Word has remained roughly constant, despite the dramatic
increase in processor Mhz, memory and disc capacity. This is because,
obviously, the faster the computer we have, the more we ask of it (and the
less efficient we need to be).
Granted if XML is simple, when you add Namespaces, XPath, XSD and DTDs it
gets complex. A big reason is that (apparently) there has been a conscious
decision not to make DTDs compatible with Namespaces. So you get either
technical tour de forces, or monstrosities, depending on one's viewpoint,
such as XHTML Modularization.
Well in any case we are asking more and more. If we don't need
XPath/XSLT/XLink/XHTML/XSD etc etc., then why not simply use XML 1.0?
Because it is not enough, itself.
Part of my job ends up being to convince people that XML really is
complex enough to mandate using existing tools, rather than
:-))) right, and hence your bias, but thanks for admiting it. My bias is
that we should get people using only what is needed, rather than the
fanciest latest greatest and most complex way of solving the problem.
Again, perhaps this is just my own experience, but having spent a few years
debugging the nitty gritty details of binary distributed RPCs protocols, and
needing a fancy system debugger that can trace an execution path all the way
into the the Win32 kernel and back out, or trying to figure out the details
of why a distributed MTS transaction was hanging, XML is a breath of fresh