Comments on: News Wire: Reinventing HTML http://www.sitepoint.com/blogs/2006/10/31/news-wire-reinventing-html/ News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com. Sat, 20 Mar 2010 19:42:52 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: malikyte http://www.sitepoint.com/blogs/2006/10/31/news-wire-reinventing-html/comment-page-1/#comment-85241 malikyte Wed, 08 Nov 2006 01:01:16 +0000 http://www.sitepoint.com/blogs/2006/10/31/news-wire-reinventing-html/#comment-85241 Resizable form fields for v2.x is a bit misleading; it's also available for v1.5.x since I've been using it. It's also been updated for that browser version as well. :) Resizable form fields for v2.x is a bit misleading; it’s also available for v1.5.x since I’ve been using it. It’s also been updated for that browser version as well. :)

]]> By: Fenrir2 http://www.sitepoint.com/blogs/2006/10/31/news-wire-reinventing-html/comment-page-1/#comment-76600 Fenrir2 Mon, 30 Oct 2006 16:23:00 +0000 http://www.sitepoint.com/blogs/2006/10/31/news-wire-reinventing-html/#comment-76600 What if all websites were in XML. Just XML without special-meaning tags. To make the XML meaningful to users there should be a *turing-complete* language for describing how the XML is displayed and interacts on the screen. This language should handle style, like: text in h1 tags is big, and behavior: users can type in an input box. W3C should the publish standards in the form of libraries. These libraries will be in this language. You can include them (import w3c.org/...) in your website to get standard styles and to give standard meanings to tags. What we have now is an accumulation of standards that will probably never be implemented in certain browsers. If you use libraries you can always use new technology in every browser that supports these two basic elements (XML + style/behavior language). Maybe it's even better to define only a virtual machine for this language so we can program in our own language and compile that to bytecode for this virtual machine. What if all websites were in XML. Just XML without special-meaning tags. To make the XML meaningful to users there should be a *turing-complete* language for describing how the XML is displayed and interacts on the screen. This language should handle style, like: text in h1 tags is big, and behavior: users can type in an input box.

W3C should the publish standards in the form of libraries. These libraries will be in this language. You can include them (import w3c.org/…) in your website to get standard styles and to give standard meanings to tags.

What we have now is an accumulation of standards that will probably never be implemented in certain browsers. If you use libraries you can always use new technology in every browser that supports these two basic elements (XML + style/behavior language).

Maybe it’s even better to define only a virtual machine for this language so we can program in our own language and compile that to bytecode for this virtual machine.

]]>