The neatest solution for handling forms I've seen was XForms (http://www.w3.org/TR/xforms11/ http://www.w3.org/TR/xforms11/), originally part of the XHTML2 prop

The neatest solution for handling forms I've seen was XForms (http://www.w3.org/TR/xforms11/ http://www.w3.org/TR/xforms11/), originally part of the XHTML2 proposal. You had multiple, potentially schema-validated models per page, the ability to neatly segue in RESTful behaviour and custom controls for dates, ranges, tabs, composite controls etc. However, the standard relied on robust browser support instead of being added on as a library (here's a current attempt at this: http://code.google.com/p/ubiquity-xforms/ http://code.google.com/p/ubiquity-xforms/). There was also an almost slavish adherence to XPath which was too clunky for certain uses, and finally it ended up as an unfortunate victim of the XHTML2 debacle.