Microsoft reboots Office

See correction below

Free IT resource TechNet: More ways to know it, share it, and keep it running. Sponsored by Microsoft Free IT resource Attend the SOA Executive Forum: Breaking SOA Bottlenecks SOAExecForum.com/may2007 Sponsored by InfoWorld DOWNLOAD PDF Click here to download InfoWorld's special report: Office 2003 XML

It’s been a long time since office suites in general, and Microsoft’s in particular, generated much heat. The features that most users depend on most often were hammered out before these programs were even ported to Windows. Word’s document-handling prowess and Excel’s analytical power have matured over the years, and they are formidable assets, but the truth is the average information worker has little need of them. Résumés, memos, and e-mails are written in Word by habit, not by necessity. Excel is typically used just to format, convey, and visualize tabular data. The way to reinvigorate Office was not to pile on more elite functionality, but rather to expand the scope of routine tasks. Office 2003 does so in ways that make it, arguably, the most compelling upgrade ever.

The information flowing through Office applications and stored in Office documents represents much of the intellectual capital of the modern enterprise. After years of milking its proprietary file formats, Microsoft opted to embrace an open and universal standard: XML. As a result, Office 2003, at least in its Professional and Professional Enterprise editions, promises to help us redesign our information ecosystems so that people, desktop applications, and network services can interact in new and strategically valuable ways. It’s a bold vision. Will it change your enterprise for the better? Let’s look at what new benefits are now possible, and what it will take to achieve them.

For Jason De Lorme, CTO of Monster, the job posting and recruitment Web site, strategic data assets come in the form of résumés -- lots of them, 95 percent of which are produced in Microsoft Word. Although using Word may be an appropriate way for job seekers to create impressive

8-1/2-by-11-inch pages, it’s a lousy way to feed a database. So, most Monster users rely on the cut-and-paste method to transfer résumé content from Word documents into its database. Soon, De Lorme says, Monster will try an alternative method. Job seekers who have Word 2003 will be able to download Word templates that solve two problems at once. First, they will allow users to create, edit, and print résumés in the normal way. Second, their data will be mapped to XML elements and validated against HR-XML, the dominant XML schema in the human resources realm, allowing the information to be parsed by machines. If the experiment succeeds, job seekers will save time and everyone will benefit from high-fidelity data that can be easily exchanged and effectively searched.

Adapting Word 2003 to this kind of use takes serious effort by XML developers. Word wasn’t built for structured data entry. Its XML capability was bolted on, not built in. And even the best special-purpose XML editors present usability challenges. To smooth out the user experience, Monster’s templates protect tags that might be damaged by editing and use SmartDocs extensions to deliver context-sensitive guidance and lists of choices in Word’s task pane.

“We’re not betting the bank on this technology,” De Lorme freely admits. What is certain is that your résumé, however you provide it, eventually becomes valid HR-XML. Word’s ability to meet this requirement, and users’ comfort with the resulting experience, will need to evolve over time. But the goal is clearly in view, and the software is moving in the right direction.

All Roads Lead to XML

Three different Office 2003 applications -- Word, Excel, and InfoPath -- have the power to read and write XML data that is not merely well-formed, but also valid with respect to customer-defined schema. This creates a wealth of new opportunities for enterprise information architects, but also a certain amount of confusion.

Consider the venerable expense report, a classic Excel application. It’s now possible to bind an XML schema to a spreadsheet template and map elements of the schema to spreadsheet cells. Expense data gathered this way is guaranteed to be easily accessible by any application, service, or script running on any platform, just because it is XML. The fidelity of that data is likewise portable because any XML application can verify that it conforms to the schema.

Given all this, it might seem like a no-brainer to upgrade your expense reports to Excel 2003. But there’s a wild card in the deck: Office’s new XML-based forms application, InfoPath. As Excel and Word do, InfoPath can gather XML data, validate it against a schema, and augment declarative validation with programmed logic. Because it was built from the ground up for gathering structured data, however, InfoPath’s interactive XML features are more flexible than Excel’s or Word’s. An InfoPath document is a container of nested, expandable data structures, and its user interface is tuned accordingly. InfoPath also makes it easy for less technical developers to build forms that make data entry flow smoothly. What it can’t do is mimic the form that you would have printed and sent to accounting.

If you want to capture XML data and inject it into a business process, you may not care to simulate the piece of paper that is used to represent that process. In that case, InfoPath is a logical first choice. To meet the need of the many business processes that remain paper-bound, other options exist.