W3C home > Mailing lists > Public > public-html@w3.org > January to March 2007

Re: Brainstorming: Best of all Worlds

From: Laurens Holst <lholst@students.cs.uu.nl>
Date: Wed, 28 Mar 2007 13:43:00 +0900
Message-ID: <4609F254.5070207@students.cs.uu.nl>
To: Sebastian Schnitzenbaumer <sebastian@dreamlab.net>
CC: public-html@w3.org
Fwiw, +1 for offering a declarative approach, as opposed to script-only.

Although I have yet to see why "field1 + field2" is more difficult to 
authors than "$field1 + $field2". Especially when you’re starting to 
create a subset of Javascript, I start to wonder whether it wouldn’t 
just be better to use XPath. But I didn’t really think hard about all 
the turing complete and static analysis bits, so maybe XPath has the 
same issues as JS has there :).

Finally, is there a solution yet for the names conflicting with 
Javascript keywords problem I indicated?


Sebastian Schnitzenbaumer schreef:
> Hello HTML WG,
> I would like to kick start discussion on whether or not it is 
> beneficial to think in terms of Best of all Worlds, including HTML5, 
> Web Forms 2.0, XHTML 1.0, Modularization of XHTML and XHTML 2.
> The way I see it is that what happened here at W3C recently is like a 
> merger between two competing companies with two competing products. 
> While both companies tried to define themselves as being "anti" the 
> other, shortly after the merger this mindset still exists, but slowly 
> fades aways in favour of a synergy strategy enabling a better product 
> for the customer.
> For us, I think a lot has been defined "as opposed to" the other 
> technology. We're all W3C now. The XML story of the W3C is coming 
> along in the market. For example, yesterday Kurt Cagle wrote on XML.com:
> "I find it increasingly difficult not to work with XForms, to be 
> honest, even given some of the complexities involved in different 
> implementations. With XForms, you can build the data model XML on the 
> client side, send it up to an XQuery that will validate and process 
> it, and then this object can in turn be passed off to a transformation 
> to generate another XForms instance, an XHTML report, or an SVG chart 
> of some sort. XSLT2 works well in building such input templates, again 
> giving you fine-grain conditional control and the establishment of 
> interface capabilities. I think the "X" model - XQuery + XSLT2 + XHTML 
> + XForms - will likely prove a potent one in the future."
> http://www.xml.com/pub/a/2007/03/21/the-future-of-xslt-20.html?page=2
> - Sebastian

Ushiko-san! Kimi wa doushite, Ushiko-san nan da!!
Laurens Holst, student, university of Utrecht, the Netherlands.
Website: www.grauw.nl. Backbase employee; www.backbase.com.

Received on Wednesday, 28 March 2007 04:43:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 28 March 2007 04:43:55 GMT