It is desired to have improved interoperability between ODF and OOXML. However, OOXML lacks the following features:
Group items tagged
2. WordprocessingML Reference Material - OOXML-Wiki - 0 views
-
-
It is desired to have improved interoperability between ODF and OOXML. However, OOXML lacks the following feature: image can be positioned absolutely within a frame Proposed change: Include support for this feature from ISO ODF in order to improve interoperability between the two formats.
-
Include support for this feature in ISO ODF is another way of saying to hell with Ecma, OASIS and the big vendors driving the ODF-OOXML bus, Micrsoft and Sun. This is delicious beyond belief. It's also the only way the world is going to get the interoperability they are demanding. The big vendors must be neutralized. The file formats must be completely independent of applications, platforms and the control of big vendors who routinely make exclussionary interoperabilty deals with each other whenever and wherever profitable.
-
-
I promise that within a few minutes of reading this OOXML Wiki you will be wondering if this is in fact an ODF Wiki! This is incredible.
Fast forward to the section called, "Interoperability between ODF and OOXML", and enjoy. They cite the problem and make an interop recommendation for each entry. And what a recommendation it is. Speaks volumes.
There is definately something going on in Europe. The EU IDABC has rejected ODF, OOXML, OASIS, Ecma and ISO! And are now trying to write their own highly interoperable XML file format, ODEF. an effort we will fully support with our da Vinci plugin for MSOffice.
Well, not only will we support ODEF, we'll write it for them if they really want to cut to the chase and get the kind of vendor independent interoperability the world hungers for.
The British Standards Institute (BSi) is responsible for the massive research that went into this OOXML Wiki. They have hunted down and defined the interoperability problem areas between ODF and OOXML. Surprise surprise. They be many.
The interesting part is that the BSi researchers have found massive, indeed overwhelming fault with OOXML! Yet, instead of recommending that Ecma make the needed changes to OOXML, they instead recommend that ISO ODF make the changes!
Not OASIS ODF! Not Ecma OOXML.
ISO ODf!
The difference is all the difference in the world. Sun does not control ISO ODF the way they control OASIS ODF. And at ISO, all the binding of ODF to OpenOffice/StarOffice that accounts for the zero interoperability of ODF applications can be broken as needed.
This is
Microsoft Partners with Atlassian & NewsGator - SharePoint Goes Web 2.0 - Flock - 0 views
-
4) Linking; Within Confluence, users can access SharePoint document facilities. By including SharePoint lists and content within Confluence, users can (in a single click) edit Microsoft Office documents.
-
Pay close attention here boys and girls because here it is. Wonder why Microsoft is wealing, dealing and ready to shell out billions for Web 20 collaboration software? It's to tie them into the MS Stack of MSOffice, IE, Exchange/SharePoint, MS LIve, MS Dynamics, MS SQL Server, etc.
Grand convergence is the convergence of desktop, server, device and web systems. It increasing looks like were going to have to live with the MS Stack and the Open Stack of grand convergence interoperability. One will be able to have perfect interop within it's walls, with all applications able to handle the same compound XML document. The other will be totally unable to implement an inteoperable version of MS-OOXML.
Members of the MS Stack will be able to access everything in the Open Stacks, but outside systems will have limited (crippled) access into the MS Stack. Embrace, Extend, Extinguish. Here we go again.
~ge~
Slashdot | Pro-ODF Legislation Loses In Six States - 0 views
-
If this is the case then it greatly increases the scope of the bill from being a simple switch from MS Office to OpenOffice to a massive effort involving the definition of many new XML schemata, developing, testing and debugging software to handle the new schemata, creation of documentation, deployment of and training for the new software, etc., etc.
-
Another document format is not needed. This was already obvious before blogs took off, but to be promoting now is unforgivably stupid and irresponsible. Try and explain to an average person why all the typing they just did cannot even be viewed in a Web browser, they will not get it. Saving the user's typing as DOC or ODF is a con. The storage of text, styled text, graphics, photos, even movies (MPEG-4 H.264-AAC) has been solved. Your document format is ready it is HTML 4.01 Strict, CSS 2.1, and JS 1.5, there is nothing in the 1980's technology of MS Word that cannot be stored this way.
BetaNews | ECMA to Begin Drafting XPS as Alternative Standard to PDF - 0 views
-
"Be that as it may," Updegrove continues, "perpetuating one monopolistic market position after another seems wholly incompatible with the role of a global standards body, tasked with protecting the interests of all stakeholders. If OOXML, and now Microsoft XML Paper Specification, each sail through ECMA and are then adopted by ISO/IEC JTC1, then it may be time to wonder whether the time has come to declare 'game over' for open standards."
-
More on Andy UpDegrove's "Game Over for open standards" comment.
Is Open Source Dying? - 0 views
-
But behind the scenes, things are not quite as rosy. The Commonwealth of Massachusetts, which lived up to its left-leaning credentials (didn't Microsoft CEO Steve Ballmer famously upbraid open-source proponents for being Communists?) broke important ground by mandating that state agencies switch to open-source platforms. There's just one problem: They can't seem to manage the transition. Sources close to the situation tell me that former state CIO Peter Quinn's resignation happened at least in part because of delaying tactics by vendors who publicly support open source but do their best to scuttle it behind the scenes.
-
Interesting topic which i've covered more fully with the OpenStack Blog : Connecting the Dots
Billions of Legacy Binary Documents -- gary_edwards's comment on "Linux leaders pl... - 0 views
-
The point is that ODF has to be flexible enough so that the demand side of the equation can successfully convert their MSOffice documents to ODF. More important than simple one-way conversion is the need for high fidelity round trip conversion.
-
This is a follow up comment to a question cocerning my previous post, "commercialization of interoperability". The question from "mosborne" is as follows:
A different viewI'm not on the ODF TC, but I have followed its evolution through the information publicly available at Oasis.
My outside view of some of the various interoperability discussions you mention is different than yours. I saw a resistance to adoption of features if the sole reason was because OOXML did it that way. The dissenting members wanted a more substantial reason, not simply to add OOXML "features" to ODF.
If the goal is to simply make ODF like OOXML, then what is the point? You would have conceded all control to Microsoft since they have effective control of OOXML.It's an interesting question, but not well informed. The threads at OASIS ODF having to do with interoperability are focused on efforts to have our cake and eat it too.
The List Enhancement Proposal thread played out over a six month period. And yes, it is true that Sun fought the Novell proposal because they felt new and innovative features for OpenOffice/StarOffice were more important than the interoperability CIO's and IT departments are demanding. But that misses the more important point that Novell was able to craft their interoperability proposal exactly so that the precious advanced feature sets of applications that command les sthan 1% marketshare would be accommodated.
What Sun and most others on the ODF TC don't get is that the markets have no use for these new and innovative feature sets unless and until they can transition their documents and business processes out of MSOffice. If workgroup bound end users can't do that first, it won't matter how
State's move to open document formats still not a mass migration - 0 views
-
Only a tiny fraction of the PCs at Massachusetts government agencies are able to use the Open Document Format (ODF) for Office Applications, despite an initial deadline of this month for making sure that all state agencies could handle the file format.
-
Eric Lai keesp pokign at that Massachusetts hornets nest. One of these days he's going to crack it open, and it will be back to square one for the ODF Community. Still missing from his research is the infoamous 300 page pilot study and accompanying web site where comments and professional observations document a year long study concernign the difficulties of implementing ODF solutions and making the migration. <br><br>
The study was focused on OpenOffice, StarOffice, Novell Office, and a IBM WorkPlace prototype.<br><br>
The results of the year long pilot have never seen the public light of day. But ComputerWorld is one of the media orgs that successfully filed a court action to invoke the freedom of information act in Massachusetts. How come they can't find the Pilot Study?<br><br>
At the end of the pilot study period, Massachusetts issued their infamous RFi; the request for information regarding the possiblity of a ODF plugin for MSOffice! Meaning, the Pilot Study did not go well for the heroes of ODF - OpenOffice, StarOffice, Novell Office and WorkPlace. Instead, Massachusetts sought an ODF plugin that would no doubt extend the life of MSOffice for years to come. No rip out and replace here folks!<br><br>
~ge~
INTERVIEW: Craig Mundie -- Microsoft's technology chief, taking over from Bill Gates - 0 views
-
In this exclusive interview with APC, Mundie says the notion of all software delivered entirely through the web browser is now widely recognised as being 'popular mythology'. He also stakes the claim that Google's existence and success was contingent on Microsoft creating Windows. He talks about what's coming down the pipeline for future versions of Windows, and his belief that Windows can get still more market share than it has today. He also discusses the issues around the recent controversy over the Office Open XML file format.
-
So Vista is in its diffusion cycle and until there is enough of it out there, you won't really see the developer community come across.
-
Uh, the diffusion we really should be focused on involves the OOXML plug-in for MSOffice, IE 7.0, MSOffice 2007, and the Exchange/SharePoint Hub.
The Exchange/SahrePoint juggernaught is now at 65% marketshare, with Apache servers in noticeable decline.
So it seems the improtant "diffusion" is going forward nicely. The exploitation of the E/S Hub has also started, and here the Microsoft deelopers have an uncahllenged advantage. Most of the business processes being migrated to the E/S Hub are coming off the MSOffice bound desktop. Outsiders to the MS Stack do not have the requisite access to the internals that drive these MSOffice bound business processes, so they have little hope of getting into the "exploitation" cycle.
This aspect was on full display at the recent Office 2.0 Conference in San Francisco. The only way a O2 provider can position their service as a collaborative addon to existing business processes is to have some higher level of interop-integration into those processes beyond basic conversion to HTML.
Most O2 operatives struggle to convince the market that an existing business process can be enhanced by stepping outside the process and putting the collaboration value elsewhere. While this approach is disruptive and unfriendly, it tends to work until a more integrated, more interoperable coolaboration value becomes available.
And that's the problem with O2. Everyone is excited over the new collaboration possibilities, but the money is with the integration of collaborative computing into existing business processes. This is a near impossible barrier for non Microsoft shops and would be competitors. If you're Microsoft though, and you control existing formats, applications and processes, the collaboration stuff is simple value added on. It's all low hanging fruit that Microsoft can get paid to deliver while O2 players struggle to f
-
-
So far, we have delivered about 60 million copies. That would represent about six per cent of the global Windows install base. So it has probably got to get up another few percentage points before you will start to see a big migration of the developer community.
-
What is he talking about? Does a developer write to Vista? Or do they write to MS Stack ready .NET - OOXML-Smart Documents, XAML, Silverlight stuff?
-
- ...2 more annotations...
-
Great inteview, i'll comment as i make my way down the page. Hopefully others will do the same.
OOXML-ODF: The Harmonization Hope Chest | Orcmid's Lair - 0 views
-
4. The Reality in the Punchbowl Meanwhile, Sam Hiser offers a different impression of the DIN effort [4]: "The ODF-to-OOXML harmonization effort being hosted by the German standards group, DIN, is Europe's best effort to resolve our Mexican Standoff between Microsoft, Sun and IBM. Even though harmonization is laughably complex and will not work unless the applications are harmonized too, the best and brightest of Germany are left to hope for success." [emphasis mine: dh] Although the mission of the German effort is translation (Übersetzung), not harmonization, I find there is a very important point that is not made often enough: People write, read, and edit office documents with little, if any, understanding of the particular format that makes them persistent in digital form. The XML-based open formats do not change that. People adapt to the software/device they are using by trial and error. We train ourselves to obtain the visible results that we want. Different people obtain superficially similar results by quite different means. Even when someone has gone to the trouble to create style sheets, forms, macros, templates and other format-impacting aids, it is very loosey-goosey in practice. And it still does not require paying attention to the file format.
CDI WICD 2.0 - 0 views
-
This document defines a generic language-independent processing model for combining arbitrary document formats. The Compound Document Framework is language-independent. While it is clearly meant to serve as the basis for integrating W3C's family of XML formats within its Interaction Domain (e.g., MathML, SMIL, SVG, VoiceXML, XForms, XHTML, XSL) with each other, together with CSS and the DOM; it can also be used to integrate non-W3C formats with W3C formats or integrate non-W3C formats with other non-W3C formats. 1.1. Conformance Everying in this specification is normative except for diagrams, examples, notes and sections marked non-normative. The key words must, must not, required, shall, shall not, should, should not, recommended, may and optional in this document are to be interpreted as described in RFC 2119 [RFC2119]. This specification defines the following classes of products: conforming implementation A user agent that implements all interfaces described in this specification and follows all must-, required- and shall-level of critera in this specification. conforming document A document that follows all must-, required- and shall-level of critera in this specification that apply to document authors. conforming authoring tool One that produces conforming documents.
Open Stack: ISO Does The Unthinkable. How ISO approval of MSOffice-OOXML will break th... - 0 views
-
In August of 2007 we dropped ODF as the da Vinci target conversion format, and moved to the W3C's Compound Document Format (CDF) with an ePUB wrapper.The reason for this move is that we could not establish a reasonable degree of interoperability with OpenOffice ODF unless Sun supported the five generic eXtensions to ODF needed to hit the high fidelity conversion the da Vinci process is capable of.Since da Vinci is a clone of the MSOffice OOXML compatibility Kit, we use the same internal conversion process where imbr (in-memory-binary-representation) is converted to another format: imbr <> OOXML or, imbr <> RTF.While it's entirely compliant to eXtend ODF, without Sun's changes to OpenOffice ODF the application-platform-vendor independent interoperability end users expect would be meaningless.The problem as we see it is this; it is impossible to do a high fidelity conversion between two application specific XML formats. It is however quite possible to do a conversion between an application specific format and a generic (application-platform-vendor independent) format.
-
A summary of my views on ISO approval of MSOffice-OOXML and the impact it will have on the futrue of the open web.
-
In response to a recent question posted to a rather old OpenStack blog, i posted this summary of my views on ISO approval of MSOffice-OOXML and the impact it will have on the futrue of the open web.
The Coming OOXML Showdown | Redmond Developer News | Desmond - 0 views
-
Forget about the Super Tuesday presidential primaries. The biggest election in February could be the long-awaited vote to approve Microsoft Office Open XML (OOXML) as an industry standard under the International Organization for Standardization (ISO). You want to get a rise out of a group of developers? Tell them you see no difference between Open Document Format (ODF) and OOXML, since both simply map the features and functions of their respective, underlying Office application suites, OpenOffice and Microsoft Office. Yeah, I can feel the hate mail already.
IT set to 'take their heads out of the sand' and embrace Web 2.0 - 0 views
-
IT managers and CIOs in large companies who have actively resisted embracing Web 2.0 technologies like wikis, RSS, blogs and social networks will likely begin adding them to their priority lists in 2008, according to a report released Friday by Forrester Research Inc.
Wizard of ODF: OASIS invited to join Microsoft in the DIN technical report - harmoniz... - 0 views
-
the WG is busy working on a first draft. This'll include mainly work in Wordprocessing. Spreadsheet and Presentation is still in the very early work. So help from the ODF TC would be great --- and a liaison would make sense IMHO. To give you an idea why help from the ÓDF TC would be needed I'll briefly outline some questions which arose: * Need for more use-cases, i.e. feasable interop scenarios * Discussions of unspecified behaviour (e.g numbering in 1.0, spreadsheet formulas, compatibilty options, etc.) and their impact on interop scenarios * Questions regaring generic settings like e.eg. form:control-implementation="ooo:com.sun.star.form.component.Form", or tweaking a la http://www.openoffice.org/issues/show_bug.cgi?id=51726. * Possible interop problems not handled by the specs (e.g. graphics, WMF, EMF, SVM, etc.) or e.g. font metrics and font embedding. As you see there are a lot of overlapping areas with eg. the "ODF interop" we dealt with in the workshop in Barcelona. [This issue is hosted in the Adoption TC, right? Maybe this TC is also suited as a liaison partner?]
-
Uh Oh. Microsoft and Novell joined the EU's call to harmonize ODF and OOXML, but Sun and IBM refused the invite. Now we have the invite in front of the OASIS ODF TC!. Is there any rock big enough for them to hide under if they also refuse?
And if the OASIS ODF does join the EU-DIN-ISO effort, where doe stha tleave IBM, Sun and their inistance on a politically mandated "rip out and replace" as the only acceptable solution?
-
IBM's Director of Strategy comes clean on OpenXML - IBM *WILL* support OpenXML in its L... - 0 views
-
Well, if that's IBM's plan they're going to need more than ODF, that's for sure - and that brings us to the announcement I've been wondering about: IBM favors ODF as a file format because it is "truly open" and technically elegant, Heintzman said. But IBM will support Open XML, which is the current document format in Office 2007, in its Lotus collaboration and portal products. IBM already supports older versions of Office. I feel a Pamela Jones moment coming on .... there it is, as plain as day for the world to see, Doug Heintzman breaks through all IBM's doublespeak and hypocrisy and admits it. I don't know about "Beyond Office" as a plan, I think the real game here is "Beyond ODF"
IBM's Stance Against OpenXML Is Increasingly Confusing : Oliver Bell's weblog - 0 views
-
Events have played out in the media and in the blogosphere over the last couple of weeks that represent a breakdown of some of those anti-OpenXML arguments that have been played back so frequently over the last year. Arguments that there is a lack of demand for Open XML, the specification is too complex to implement, the specification can’t be deployed cross platform and the long running but baseless claim that the Ecma-376 specification might be encumbered by IPR and patent threats all appear to have been cast aside as big blue steps up to meet the demands of their own customers and the market in general. Here is a blow by blow review of the relevant activity over the last two weeks…
Issue 51726: OpenOffice ODF Graphics Nightmare - 0 views
-
Currently, the above given specification is a draft and has to be adjusted. Beside the change of the context menu and the navigator it's is needed to adjust the import of the XML file formats (OpenDocument and OpenOffice.org) and the export to the OpenOffice.org file format. The import needs adjustment, because the existence of name is used to distinguish Writer graphics/text boxes and Draw graphics/text boxes. The new criterium is now, that Draw graphics/text boxes of Writer documents doesn't have a parent style. The export to the OpenOffice.org file format needs adjustment, because a Writer document in the OpenOffice.org file format doesn't contain names for shapes.
-
The EU DIN effort to harmonize or merge ODF and OOXML has uncovered some incredible inconsistencies in OpenOffice ODF tht will break interop every time, guaranteed. This particular issue has to do with problems naming graphics, and the hack solution now in use. It's hacks like this that make it impossible to convert MSOffice binaries to ODF.
-
« First
‹ Previous
101 - 120 of 147
Next ›
Last »
Showing 20▼ items per page
It was at the height of our List Enhancement battle with Sun that OASIS stepped in their threat to boot the OpenDocument Foundation. OASIS carried out that threat in May. The lesson we learned is clear and unequivocal. Opposition to Sun, in either the marketplace (da Vinci) or in the OASIS ODF TC, can be quite hazzardous to your health.
Not that this comes as any surprise. Nearly five years ago in 2002, when i first joined OASIS to work on OpenDocument, it was clear that OASIS was a big vendor consortia. While OASIS does have an affordable "Lawn Jockey" program, Sun is clearly calling all the shots on the OASIS ODF TC. This is why ODF is bound so tightly to the OpenOffice feature set.
Still, we thought the "Lawn Jockey" loophole could be used to balance out the interests and control of the OASIS big vendors. We were wrong. And it took near five years for the obvious to finally sink. Well, "sink in" thanks to the OASIS hammer and boot.
~ge~