[
Lists Home |
Date Index |
Thread Index
]
Hello Didier:
Good to see you here again.
Yes. The space is shaped by the dominant attractor language, HTML and
the dominant storage model, relational dbs. The HTML is convenient (it
fits nicely into the constraints of a human author's memory and even
extended, a programmer's coding skills). The relational model probably
has more persistence but between them, they are creating hysteresis for
other models. I believe real-time 3D can evaporate that lock but the
side effect is to recreate the computing priesthood: it takes a lot of
skill to build effective real-time 3D worlds today. That may change.
One problem on the table is the current standards are pretty inadequate
at exposing the network in an author-friendly way. One still has to
know too much about the mechanics of protocols which is where text-based
hypermedia was prior to URIs and xmlhttp. Real time systems are a
challenge to the current architectural assumptions.
One may inquire as to how satisfactory XML and xmlhttp are for real time
communications.
len
-----Original Message-----
From: Didier PH Martin [mailto:martind@netfolder.com]
Sent: Tuesday, July 18, 2006 9:44 AM
To: Bullard, Claude L (Len); 'Richard Salz'; 'Costello, Roger L.'
Cc: xml-dev@lists.xml.org
Subject: RE: [xml-dev] RE: Why is there little usage of XML on the
"visible Web"?
Hello Len,
Len said:
Through an "HTML web browser". That is an accident of history. The
Internet doesn't really care that you use HTML as the containing markup.
It is the page metaphor triumphing over other modes and means. That can
change but I don't expect it soon. I do expect it to be relatively
sudden when it happens.
Didier replies:
AJAX (I now it's simply rebranding the actual capabilities) is slowly
changing that. We now have two metaphors:
a) Not (or very little) interactive pages. Just a small improvement over
the printed media (with the exception of video)
b) Interactive applications such as mail, word processors, order entry,
etc...
The latter are not so much based on the page model than on the
application model with overlays. The latter trend can potentially be
re-enforced by XAML even if XAML is not a W3 recommendation or an
international or European standard.
We can observe that even if it is possible to be "model driven" with a
usage of data encoded into XML and rendered in HTML after going through
an XSLT transformation, this method is not used on the client side and
is sometime used on the server side. I attribute this lack of usage to
the fact that current technologies such as xml/sql or xquery allows us
to easily package data coming out of RDB in XML but do not easily allows
us to update the RDB as easily without add-ons to the query engines.
When round trips will be easily performed and if the data publisher has
vested interest to do so, we will probably see more XML usage and more
"model driven" applications.
Cheers
Didier PH Martin
|
