(I droped mentioning xhtml after reading Stan Rogers comment) .
Bob Balaban has mentioned on his blog that there might be some ideas to modernize the Domino HTTP engine for a later release.
I think this is getting more and more important for different reasons:
- we now have more modern html standards. Unfortunatedly more than the 1 right standard. Xhtml has its problems. A standard that honours well formed xml rules seems important to me.
- html markup from the 90ties becomes more and more a burden in hindsight of quick adoption towards current and maybe even more future customer expectations.
- webservices/soa will gain in importance and exchanging html that also is well formed xml really makes REST webservices easier.
- future aditions like simple to use post-processing facilities for the result of the Domino HTTP engine would be much easier with more modern html.
- its easier to make the web site accessible for those folks with physical issues like blindness.
- from what I hear currently there seems to be efforts in some of the smaller albeit relatively affluent EU countries like Denmark and Austria to pass some serious legislation to require accesibility standards on web sites by law. And those small countries may become forerunners for EU legislation. With more modern html it is becomming much easier to adhere to those standards.
The requirements for a systematic modernizing of the markup for web frontends are very well known (for example see this presentation: www.parleys.com/display/PARLEYS/Refactoring+HTML). Inside the Domino community there is a lot of awareness for those issues.
So I think an open process with lots of early informations and some discussions about requirements with the community would make a lot of sense.
I think this to be a systemic modernization with some key decisions and a lot of important results. So an early and transparent flow of information might help IBM and users of Domino technology.