I keep hoping this will get some commentary while it’s gradually bubbling up the ranking. So, Fore is based on XForms, a W3C spec (with some widely used extens

I keep hoping this will get some commentary while it’s gradually bubbling up the ranking. So, Fore is based on XForms, a W3C spec (with some widely used extensions, in the ODK XForms spec; disclaimer: I work with ODK) to declaratively define form-based MVC applications. XForms is largely based in the XML family of technologies (forms are XML documents, bindings and computations are XPath expressions), but it’s been adapted to form definitions in Excel (which AFIAK is the most common usage), and with Fore it’s been adapted to authoring and interop with arbitrary web tech (with a BYO-anything attitude that I find refreshing). I maintain the (AFAIK only) other major web-based XForms implementation, and I was quite surprised that despite regular research I had overlooked Fore until just over a week ago. From what I can tell, it’s a younger but impressively mature and flexible implementation that does great service to the intent of XForms specifically as a web technology. (And if anyone on the team happens to notice this post, I’ll be in touch soon!)