W3C home > Mailing lists > Public > www-forms@w3.org > November 2001

RE: Non-browser compliance

From: David E. Cleary <davec@progress.com>
Date: Thu, 8 Nov 2001 09:22:52 -0500
To: "Jim Wissner" <jim@jbrix.org>, <www-forms@w3.org>
Message-ID: <NDBBIOBPAGDGFJAHFCGGCEJLCIAA.davec@progress.com>
> So you can see how two applications (Xybrix and a web browser) could
> potentially both be 100% xforms compliant, and yet be unable to read and
> render the same documents.

XForms can easily be split into two parts, the form purpose and the form
presentation. The presentation side of the equation isn't tied to any
particular vocabulary. You can bind a form to XForms widgets, XHTML widgets,
WAP widgets, or a proprietary vocabulary. Obviously, the presentation
vocabulary you choose is dependent on the client being able to render it.
However, the pupose of the form does not change at all.

If Xybrix doesn't support (X)HTML, then, people shouldn't expect it to
render it. Same goes in the other direction. But this is be design.

David Cleary
Received on Thursday, 8 November 2001 09:22:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:21:50 GMT