[veosotano]

The plan is to make the rendering engine an auto-updateable library, that's independent of the browser's release schedule. Thus, users would stay current faster.

On the other hand, there will be a versioning system, so that authors can specify what version of the technology they are targeting. So if the spec changes, compatibility modules can be created akin to how Adobe apps open documents differently if they are CS3 or CS5 documents, interpreting them according to what version they are.

Usually, layers can be built with new features, where only the very basic aspects of your design require a certain feature set, while others can be optional. In some scenarios, the user will have an outdated system and the author has REQUIRED a higher version than what is installed. Then a built-in prompt to update could be displayed, maybe with an option to view anyways, with the knowledge that it may render incorrectly.

Long story short, there are many things that can be done, and we certainly will learn a lot along the way, but I think we should definitely try.

[chc]

This sounds like something we already have. I don't want this to sound confrontational, since I know the F-word is viewed as kind of "dirty" around here, but how is what you're proposing substantially different from Flash?

[veosotano]

Well for starters its open source instead of proprietary. I think that already deserves some respect on its own.

Then, this is based on doing websites in the web standards spirit of using plain-text files, where multiple components are linked together, and having the semantic content (XML) separated from the presentation (HSS).

I mean, we like the concept of HTML+CSS, but we would like to see many of its flaws and shortcomings corrected.