Cart
[Home] [By Thread] [By Date] [Recent Entries]
Title: Message Don't
forget attributes. The advice that one reads recommending using
elements only proves to
be
dead wrong. Also, in practice, building up complex systems requires
namespaces; otherwise,
the
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
look
past markup to the application framework. What I do find attractive
is that once one
has
designed a worthy markup application for the app framework to consume, the
producers
can be
literally endless and never have to touch intermediaries such as XSLT (not a
kick
against XSLT; just saying it isn't required).
As to
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
like.
len
|
