Although each e-forms approach shares common goals for automating business processes using XML to exchange data, the strategies differ in key areas.
Microsoft's arguments in favour of InfoPath include a presentation format that mimics other applications in the Office System. Instead of looking and acting like a jazzed-up Web page, InfoPath forms will appear to users as a slight variation on the types of office documents they already work with, said Rajesh Jha, Microsoft's general manager for InfoPath.
"You get not only the flexibility of the document but all the power of a form; all the business rules are maintained," Jha said.
That means sharing of forms is limited, however. Any XML-capable application, such as a Web browser, can view data output from InfoPath, but users will need the full $199 (£119) InfoPath client to input data. Analysts say that means InfoPath adoption is likely to be restricted to internal processes, such as human resources tasks, rather than connecting with clients and general consumers.
"They really designed it for addressing workgroup, workflow problems, and I think Microsoft has a pretty compelling argument there," said Joshua Duhl, an analyst for research company IDC.
But is it too complex?
InfoPath has also drawn criticism for the complex interface users must master to create forms and link entries to back-end functions. That complexity is likely to prevent InfoPath from gaining the same widespread acceptance as other Office applications, analysts say.
"To construct a form (in InfoPath), depending on how sophisticated a form it is, that can be a fair amount of work -- a couple of days worth for a well-trained programmer," Duhl said. "There's some scripting you have to do, some Web services calls -- you have to have a knowledge of your infrastructure."
Although the more technical aspects of InfoPath development are likely to be done by information technology departments, Jha acknowledged, the less technically inclined can still be productive with the application after a little training. Beta tests showed that midlevel managers found it useful and practical to create forms to address department-level problems, he said.
