- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Tue, 27 Jun 2006 20:22:36 +0100
- CC: www-forms <www-forms@w3.org>
> Personally I think that giving an error when there is no bound node > at all is and submitting with no parameters when there are no child > nodes of the bound node is the cleanest solution. I dispute the "cleanliness" of this. Just imagine yourself trying to explain newcomers how to do something as simple as an HTTP GET without parameters to retrieve text resources, and look at their face when they realize that just to do this, you have to create a dummy instance that really serves no purpose but takes three lines of code and has to be assigned an id. Simple things should be simple to write. Performing a simple GET is a simple thing, ergo... let's find a better solution if we can. > It requires no special cases, and follows naturally from the rest of > the rules in the binding and serialization sections. I believe that > in terms of weighing who has to do the work, giving an error when > the bound node doesn't exist is more beneficial to authors debugging > forms than easing the load of the occasional author who needs to do > something special. Part of my point was that doing a submission with GET and no parameters is going to be quite a frequent case as more and more interfaces move to REST and expose nice URLs, many of which do not use query parameters. -Erik -- Orbeon - XForms Everywhere: http://www.orbeon.com/blog/
Received on Tuesday, 27 June 2006 19:22:52 UTC