Lists Home |
Date Index |
That was the conclusion of the X3D team as well.
VRML syntax is superior for the job, but the
benefits of syntax integration are there for XML.
The real arguments start at the API, eg, is the DOM a
good real time rendering interface. One argument
has been, "Well, it works for SVG", but I am
not yet convinced. There remain cases where
values that can be touched by a vanilla DOM
based on InfoSet like definitions would be
deadly. So, syntax, yes. API, maybe and
maybe only parts. This is something the
generalized XMLer has to consider; knowing
the XML DOM is not enough. Some operations
that work against some apps will return
errors in others. Duh, but something we
have to make clear from time to time.
From: Gavin Thomas Nicol [mailto:firstname.lastname@example.org]
I agree that XML has practical benefits... but I think the cause is
more from "standardization" (minimal level of interoperability as
Marton says), "network effects", "application", and "tribal knowledge"
than from inherent benefits of the syntax.
FWIW. I also believe in "the right syntax for the job".