Lists Home |
Date Index |
forget attributes. The advice that one reads recommending using
elements only proves to
dead wrong. Also, in practice, building up complex systems requires
markup is too tightly coupled to the application language system. It
is only with the
application of namespaces that I've seen true composable markup.
Even then, one has to
past markup to the application framework. What I do find attractive
is that once one
designed a worthy markup application for the app framework to consume, the
literally endless and never have to touch intermediaries such as XSLT (not a
against XSLT; just saying it isn't required).
consuming complex markup, one does find out that all-in-one browsers have their
headaches. For example, reliable widgets even as simple as popups
aren't as readily
available as one assumes, and behaviors aren't as reliable as one would
I think that
XML is a lot like Legos.
with simple building blocks that have clearly defined assembling mechanisms
(i.e., ways of snapping the blocks together) you can create a
virtually endless variety and complexity of structures.
Consider XML: in
XML there are just two building blocks: (1) tags, and (2) data.
The assembling mechanisms of XML building blocks are very simple: (1) a
tag can embed tag(s), and (2) a tag can embed data. With
these building blocks, and these assembly mechanisms virtually any information
structure can be created.
blocks ... simple assembly mechanisms ... endless