Not to be a polyanna, but...
I get both sides. The Xforms/W3c crowd want to define a spec that can take web application development and data collection into the future. The html spec is old and really not flexible enough to do some of the "fancy stuff" that pushes the envelope.
OTOH The Webforms 2.0 crowd wants to ensure that the browser you have continues to work, which also makes sense.
But... doesn't it make sense that the "old" (ie webforms 2.0) could be refreshed/updated as part of the standard in a transition mode, and that at the same time Xforms would be supported as the "more robust/enterprise" standard going forward?
Adopting both standards in this way just does not seem to be awkward or odd to me at all.
This way, developers can choose which of the standards they want to adopt. If they find a compelling reason to do xforms now, then they realize that this choice will compell browser upgrades. Fine. They know that ahead.
Similarly, the browser folks can keep doing what they are doing, and simply aim to put xforms support in the dev tree for some future version.... while still being sure that the existing code will work with many sites that use the updated "old code" of webforms 2.0
Everyone wins, right?
Slashdot Mirror
This should have been a poll
Not to be a polyanna, but ...
I get both sides. The Xforms/W3c crowd want to define a spec that can take web application development and data collection into the future. The html spec is old and really not flexible enough to do some of the "fancy stuff" that pushes the envelope.
OTOH The Webforms 2.0 crowd wants to ensure that the browser you have continues to work, which also makes sense.
But ... doesn't it make sense that the "old" (ie webforms 2.0) could be refreshed/updated as part of the standard in a transition mode, and that at the same time Xforms would be supported as the "more robust/enterprise" standard going forward?
Adopting both standards in this way just does not seem to be awkward or odd to me at all.
This way, developers can choose which of the standards they want to adopt. If they find a compelling reason to do xforms now, then they realize that this choice will compell browser upgrades. Fine. They know that ahead.
Similarly, the browser folks can keep doing what they are doing, and simply aim to put xforms support in the dev tree for some future version .... while still being sure that the existing code will work with many sites that use the updated "old code" of webforms 2.0
Everyone wins, right?