This thread started out to be about evolving XML to be a language for application development.Â
Not particularly surprising though, much of what has been discussed here deals with problems with browser support and why that is largely the problem with standards adoption.  Also there is discussion of serious issues related to efficient data formats for processing, communication and exchange, particularly with mobile devices.Â
What I am advocating is fundamental changes to the language foundations for XML, which would incidentally ameliorate both of these issues.
With regard to data formats, the fundamentals of a specification language need to deal directly with issues of effective data types and formats - in addition to UTF variants in a markup language.
While not directed at browser issues, this approach would have the following consequences:
· By simplifying specifications for XML standards, browser support for them becomes considerably easier.
· Support for various browser extensions can avoid the need for new base function in the browser.
For instance, a new standard involves new elements and attributes, and often complex constraints on their use.
Schema allow new elements to be defined. Properties and behavior for these elements can also be defined so that infosets essentially become objects. Implementation as objects then requires only the ability to add appropriately fenced execution libraries that can be accessed by the browser through standard interfaces â create, get, put, compare, run, etc.Â
End user output can be routed to a rendering engine, possibly implemented as a plug-in.
New standards also imply both syntax and semantic constraints. These can be addressed, in many cases with fundamental flexibility in the base language, and in other cases with ârulesâ statements.
Thus a new standard can be born with no change to the browser.
· What is suggested here is primarily directed to application development.
The intent is to have a fundamental influence on how computer applications are developed. This is driected more to developers, rather than to end users.  Hence the adoption path is different âimplementation by a single browser is sufficient for application support. Then, for other browsers - âif you build it they will comeâ â maybe ?
Platforms do compete based on their âappâ libraries.
This discussion highlights but two of the issues that an extended XML specification language can address.Â
But then, the questions remain:
·  Is a simpler and fundamentally more powerful language for models based application development a reasonable goal for the future of XML standards development ?
· Is there energy in the community to address such a fundamental change?