UH? When is this going to happen? How is it that OpenOffice, Google Docs and Zoho enter an existing MSOffice business workgroup? Where are the conversions of scripts, macros, OLE, security settings, data and media bindings? That's right. They are no where to be found. Which means that these application interlopers have no means of entering an existing MSOffice anchored workgroup, workflow or business process.
This link has been bookmarked by 2 people . It was first bookmarked on 29 May 2008, by Gary Edwards.
-
21 Dec 08
Marc LijourGood numbers
ooxml microsoft office openoffice news finance staroffice mt8213 office_suite
-
29 May 08
Gary EdwardsMore confusion about the MS announcement of native support for ODF, with delayed support for whatever ISO finally determines to be ISO 29500; "OOXML". Damn but these guys are all twisted up about this. The truth is, ISO National Bodies traded their vote in favor of OOXML for MSOffice support for ODF and Microsoft's joining the OASIS ODF TC. It's not complicated. MS wants ISO approval of OOXML because it established MSOffice as a "standards" editor. The rest of this kurfufull is all about anti trust concerns and Microsoft's need to put htose concerns to bed before the world figures out that they are leveraging the MS desktop monopoly into an MS Web monopoly. ISO approval of OOXML is the final piece of very complex puzzle.
The harmonization of OOXML-ODF is impossible. MS knows this. So why not join OASIS ODF TC if it means putting aside the anti trust claims from ISO NB's and getting that all important standardization of OOXML? Both ODF and OOXML are both XML encodings of entirely application specific binary formats. There is no possible to way to reconcile the file formats without also reconciling the applications! Incuding feature sets and layout engines!!!! Impossible!!
The real game is the transition from client/server to the emerging client/Web-Stack/server model. MS is the "client" in client/server. No way were they about to give that up without a plan to control the transition of MSOffice documents to the emerging client/Web-Stack/server model. They sought to fully control the formats, protocols and API's of this new model. ISO handed it to them.
The thing to watch is the MSOffice SDK where one can find a very cool OOXML <> XAML converter. XAML is totally proprietary, but "web ready". Meaning, MSOffice is a "web ready" application. It's just that the web readiness is 100% MS .NET-Silverlight.
The great transition to client/Web-Stack/server is now on. Thanks to ISO. All this ODF stuff is just background noise designed to quiet the anti trust crowd. Despicable, but well done.
~ge~-
On the same day that the state of New York published a report supporting open formats for electronic documents, mighty Microsoft (Nasdaq: MSFT) said that it would support the open-source ODF format in Office 2007. Redmond's own Open Office XML specification may be heading for the great Recycle Bin in the sky, never to come back.
-
Add Sticky Note
-
-
Add Sticky NoteThe company's biggest revenue generator may be a shadow of its former self in a few years. I just hope that Microsoft has some alternative business prospects on tap
-
Of course they have an alternative: the MS Web-Stack centered by Exchange/SharePoint/MS SQL Server. The whole idea is to migrate existing MSOffice anchored business processes to this new Web-Stack before interloper can figure out what happened. ISO approval of OOXML is the final piece to understanding this complex puzzle. Let the transition begin!
-
-
Public Stiky Notes
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.