Q&A: Calif. CIO Steers Clear of Ideology on File Formats - 0 views
www.computerworld.com/...article.do
california iso microsoft mooxml msoffice odf ooxml opendocument openxml xml
![](/images/link.gif)
-
We’re trying to view it as a straight business decision. What are the costs associated with one approach over another? Does it serve all of our business needs? If it doesn’t serve a business need, how do we satisfy that business need? We’re trying to view this just as a plain-vanilla, nonpartisan, nonideological issue.
-
A mus tread. Carol Sliwa of ComputerWorld intervies Clark Kelso, California CIO. ODF is the main issue, with clark casting all his answers in the context of business decisions. Carol o fcourse is asking the best questions of any journalist alive.
Keep in mind that ComputerWorld and the Boston globe filed for the Freedom of Information Act to be invoked in Massachusetts. They got access to all the eMail, documnetation, and conferencing notes concerning ODF and Microsoft. Carol's interview with Louis Gutierrez last week was filled with the same hard questions Clark Kelso fielded so deftly.
The "committee" Clark Kelso has set up to look at these issues is headed by Bill Welty, the CIO of the California Air Resources Board. Bill is a long time opensource - Linux guy, but will be the firs tto admit that Microsoft is the only vendor providing a means of getting everything inot XML. And that's the heart of any SOA strategy, "First, get everything into XML".
With a 500 million MSOffice desktop bound business process headstart, Microsoft has the extreme advantage in this much needed migration to XML.
They now have their own proprietary application and platform bound version of XML; MOOXML (Microsoft OfficeOpenXML) heading for international standardization at ISO.
They now have their XML Hub in place; the Exchange4/SharePoint Hub. This is also an essential part of any SOA strategy. You've got to have an XML Hub where the XML information streams and service connection to legacy black box systems can be piped into, managed and resolved. The XML must also provide an end user interface to these information flows. One that converges and integrates information, documents, data, and workflows into an easy to manage and participate in interface. The E/S Hub excells at this because it covers the fundamentals of eMail, messaging, portal, calendar, scheduling, c