Elliotte Rusty Harold wrote:
> There are some use cases where XML is just not appropriate.
Indeed. That's the point where finding another format but trying to
build strong bridges between it and XML could well make sense.
> However, for what it does work for, it works very well; and
> trying to make it work better for some of the current use cases, or for
> new use cases, at the expense of existing use cases and interoperability
> does not seem wise.
Determining whether such optimisations are "at the expense of existing
use cases and interoperability" or not, and if expenses there are
whether they are higher or lower than not doing it, is an important part
of the WG's work.
--
Robin Berjon
