Ugo Cei wrote: > > 5) Lock In > > Since the only known open standard here is XForms and there are no > widespread implementations of it, the risk of lock-in is present no > matter which solution you choose.
Perhaps there is a level of risk of lock-in with XForms, but it seems like a much lower level. XForms is a W3C recommendation; there are several implementations of it (not all may be open source or complete, but they exist); and Mozilla and IBM have committed to supporting it. Thus it looks like there is good potential for having multiple options for some time to come. Whereas with CForms, it's not even stable yet, and no one outside of the Cocoon community is even proposing to support it, right? Probably the most attractive feature of Cocoon, for me, is its basis on XML/XSLT. These are wide-open standards, which lets me use my existing skills and tools to fully customize how my webapps work. I would like this same advantage to apply to forms. I guess I'm as puzzled as Julian about why Cocoon decided to drop support for XForms and roll their own. This may have been necessary while XForms was still not a recommendation (that happened 14 Oct 2003), but ... according to http://www.xml.com/pub/a/2003/09/10/xforms.html, "XForms was the most widely implemented W3C specification, ever" -- even when it was only a Proposed Rec! (Hard to believe it could be more widely implemented than XML, but still... Maybe they meant most widely implemented for that stage in its lifecycle?) Thomas wrote: > There's the Chiba project - http://chiba.sourceforge.net/ - which is > rapidly approaching full XForms compliance. There's also an > integration > project called Chicoon which is an integration between Chiba > (which, for > example, assumes its documents are on the filesystem) and Cocoon. > > There's also OXF, http://orbeon.sourceforge.net/ - which has a > server-side XForms processor. Not sure how one might > integrate OXF with > Cocoon, though, they seem to view Cocoon as a competitor - > http://www.orbeon.com/community/cocoon > > <opinion> > CForms are really excellent for webapp development, but for > some types > of XML processing XForms has advantages. Whether it comes > from Chicoon, > from an OXF/Cocoon integration or from a resuscitated JXForms, the > Cocoon+XForms combination hits some targets for which CForms is less > than ideal. > </opinion> > > Anyone else interested in XForms with Cocoon? > - Thomas. Yes, I am. I would be interested in some client-side validation (a la DENG, or Mozilla's implementation of XForms); but since XForms can be used for either client-side or server-side processing, I can go ahead and develop the webapp in either one, and leave open the possibility of switching later. Anyway, I for one would be interested in talking about combining XForms and Cocoon, sharing experiences and info. Lars --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
