RE: [XFORM][CALL FOR] XForms Tutorial/Introduction

>XForms should integrate easily with existing markups but provide a
>more model-driven approach

that's my point as well. The advantage of XForms is to take a schema + model
and render or question data accordingly. The UI should be generally
optional.

When the content is schematized and separated from layout, XForms might
potentially change the whole way the web works. 
Today the users can't technically distinguish the real content from the
(mostly unwanted) advertising, navigation and non-sense frame. That's why
searching the web is rather fuzzy and inaccurate, and constructing a
personalized web-portal which is independent of a specific .com is even
impossible. 

But the vast part of web-business is built upon this restriction.
Contentproviders won't give away their information as XML without merging it
with cookies, banners and "Click here"s. In fact, that's where micropayment
would have to come into play.

So my biggest concern is that XForms will still require hand-coding the UI,
rather than render the data according to the model and take only additional
hints from the UI (which is also desirable from a application-development
point of view).

Received on Monday, 2 April 2001 10:47:57 UTC