<?xml version="1.0" encoding="UTF-8" standalone="yes"?><oembed><version><![CDATA[1.0]]></version><provider_name><![CDATA[Scobleizer]]></provider_name><provider_url><![CDATA[http://scobleizer.blog]]></provider_url><author_name><![CDATA[Robert Scoble]]></author_name><author_url><![CDATA[https://scobleizer.blog/author/scobleizer/]]></author_url><title><![CDATA[Tim Bray wants Microsoft to make Office support&nbsp;ODF]]></title><type><![CDATA[link]]></type><html><![CDATA[<p><a href="http://tbray.org/ongoing/When/200x/2005/11/27/Office-XML">Tim Bray just told me (and my fellow Microsofties) to do more work</a>. He wants us to convert Office to support the open document format from OASIS.</p>
<p>Tim, I think you are GREATLY overstating the point when you say <em>&#8221; Almost all office documents are just paragraphs of text, with some bold and some italics and some lists and some tables and some pictures. Almost all spreadsheets are numbers and labels, with some sums and averages and pivots and simple algebra. Almost all presentations are lists of bullet points with occasional pictures. The capabilities of ODF and O12X are essentially identical for all this basic stuff.&#8221;</em></p>
<p>If they are so similar it&#8217;ll be a breeze to write a converter to take one XML file format and convert it into another, right Tim? Hey, Tim, wanna come work for the Office team? I think we have an office open for a co-inventor of XML. Maybe Sun Microsystems can give you a leave of absence. Or, heck, take a vacation and work on it on your three weeks off a year. If it&#8217;s so easy someone with your skills should be able to finish the job in a few weeks, no?</p>
<p>But, back to reality, thanks for telling me to do more work. I&#8217;m passing the request along.</p>
]]></html></oembed>