an old hangover from The SGML Way. It was adapted as a
slogan for XML. Nothing in XML presupposes that
separation. It is a best practice issue. One does it so
each layer of the system handles only the properties
needs. Such layers include the organizations and humans
process the information most effectively in a form and
names most familiar in that domain. That is why we
XSLT etc. Node is nodes, properties is properties.
make the most difference to the mammals and they
fight to the death for them.
human readability is useful. It takes some practice,
even when an IDE is more productive, occasionally you
to open the file and poke and peek. Note that even
all of the Visual apps, you still need to edit code. True
Basic, Java etc and just as true for XML.
sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
Sorry if this is an old, dead horse on this list,
but does anyone see any substance in the supposed "separation of content
from presentation" feature of XML?
Since we had this years ago with
databases and server-side scripts, I'm thinking this (and certain
other misconceptions) are just attempts
to create visual, easily demonstrable features
for what is an inherently non-visual
technology. Since XML no doubt owes some
of its hype to its (distant) relation to HTML, which is visual, people wanted
to be shown features of XML that they could "see."
In the same vein, has anyone else noticed lots of
demonstrations of XML-using applications that make a point of exposing
the XML itself, as if its readability were an asset to the end user? Since XML
works in the background, it's hard to demonstrate its effects on the
application from the user's point of view.
I'm thinking that being able to explain the root
causes of these misconceptions will help me in explaining to people why they