[
Lists Home |
Date Index |
Thread Index
]
Title: Message
++1. As the musicians say, "when in doubt, lay
out."
Perhaps it would be good to put the various Spy Vs Spy subtopics
aside
and ask simply, what will XHTML 2.0 have that its predecessor
doesn't?
1. UIVMs need a core language. For web browsers, that is
(x)HTML.
UIVMs
are an important part of the web framework. Continued development
of
these capabilities with full recognition of the limits of applying them
to any
conceivable application is wise.
2. Non-UIVM web clients have a future, but they are individual and
largely circumscribed by each project. The majority of these
don't
use
(x)HTML as their core language. So this issue doesn't affect
the
question at hand. (Yes, some of us make very good money
on fat
clients in 2002 and will continue to. So what?)
This
question simply comes down to looking at the charter and
the
proposed new features for XHTML and deciding if we need them
now,
in the projected timeframe for release, or ever. This will not
stop
the development of XHTML 2.0. It enables individual developers
to
choose among alternatives. That is all.
I
apologize that I don't have time to go read what is available
and
sort that out for myself. Still, there are some serious web
developers
here
and maybe a quick sanity check of the proposed features and
charter would be helpful if we can stay out of the politics of
implementation
centers. If those who have this information don't have the time to
present it in this forum, that is also understood.
len
I
was just suggesting that sometimes, doing nothing not only gives you the
chance to relax and enjoy yourself, it also leaves the world a tidier
place.
| 