The format war between Microsoft’s Open Office XML (OOXML) and the open source OpenDocument Format (ODF) has flared up again, right before the looming second OOXML ISO vote in March.
Group items tagged
7More
ODF and OOXML - The Final Act - 0 views
-
-
“ISO has a policy that, wherever possible, there should only be one standard to maximise interoperability and functionality. We have an international standard for digital documentation, ODF,” IBM’s local government programs executive Kaaren Koomen told AustralianIT.
-
ODF has garnered some criticism for being a touch limited in scope, however, one of its strengths is that it has already been accepted as a worldwide ISO standard. Microsoft’s format on the other hand, has been criticised for being partially proprietary, and even a sly attempt by the software giant to hedge its bets and get in on open standards while keeping as many customers locked into its solutions as possible.
-
A "touch limited in scope"? Youv'e got to be kidding. ODF was not defined to be compatible with the billions of MSOffice binary (BIN) documents. Nor was it designed to further interoperability with MSOffice.
Given that there are over 550 million MSOffice desktops, representing upwards of 95% of all desktop productivity environments, this discrepancy of design would seem to be a bit more than a touch limited in scope!
Many would claim that this limitation was due to to factors: first that Microsoft refused to join the OASIS ODF TC, which would have resulted in an expanded ODF designed to meet the interoperability needs of the great herd of 550 million users; and second, that Microsoft refused to release the secret binary blueprints.
Since it turns out that both IBM and Sun have had access to the secret binary blueprints since early 2006, and in the two years since have done nothing to imptove ODF interop and conversion fidelity, this second claim doesn't seem to hold much water.
The first claim that Microsoft didn't participate in the OASIS ODF process is a bit more interesting. If you go back to the first OASIS ODF Technical Committee meeting, December 16th, 2002, you'll find that there was a proposal to ammend the proposed charter to include the statemnt that ODF (then known as Open Office XML) be compatible with existing file formats, including those of MSOffice. The "MSOffice" reference was of course not included because ODF sought to be application, platform and vendor independent. But make no mistake, the discussion that day in 2002 was about compatibility and the conversion of the legacy BIN's into ODF.
The proposal to ammend the charter was tabled. Sun objected, claiming that people would interpret the statement as a direct reference to the BIN's, clouding the charter's purpose of application, platform and vendor independence. They proposed that the charter ammendment b -
Will harmonization work? I don't think so. The problem is that the DIN group is trying to harmonize two application specific formats. OpenOffice has one way of implementing basic document structures, and MSOffice another. These differences are directly reflected in the related formats, ODF and OOXML. Any attempts to harmonize ODF and OOXML will require that the applications, OpenOffice and MSOffice, be harmonized! There is no other way of doing this unless the harmonized spec has two different methods for implementing basic structures like lists, tables, fields, sections and page dynamics. Not to mention the problems of feature disparities. If the harmonized spec has two different implementation models for basic structures, interoeprability will suffer enormously. And interoperability is after all the prupose of the standardization effort. That brings us to a difficult compromise. Should OpenOffice compromise it's "innovative" features and methods in favor of greater interoperability with MSOffice and billions of binary documents? Let me see, 100 million OpenOffice installs vs. 550 MSOffice installs bound to workgroup-workflow business processes - many of which are critical to day to day business operations? Sun and IBM have provided the anser to this question. They are not about to compromise on OpenOffice innovation! They believe that since their applications are free, the cost of ODF mandated "rip out and replace" is adequately offset. Events in Massachusetts prove otherwise! On July 2nd, 2007, Sun delivered to Massachusetts the final version of their ODF plug-in for MSOffice. That night, after reviewing and testing the 135 critical documents, Massachusetts made a major change to their ETRM web site. They ammended the ETRM to fully recognize OOXML as an acceptable format standard going forward. The Massachusetts decision to overturn th
-
- ...1 more annotation...
-
-
The Burton Group did not recommend that ISO recognize OOXML as a standard! They pointed out that the marketplace is going to implement OOXML by default simply because it's impossible to implement ODF in situations where MSOffice dominates. ISO should not go down the slippery slope of recognizing application-platform-vendor specific standards. They already made that mistake with ODF, and recognizing OOXML is hardly the fix. What ISO should be doign is demanding that ODF fully conform with ISO Interoeprability Requirements, as identified in the May 2006 directive! Forget OOXML. Clean up ODF first.
-
-
Correcto mundo! There should be only one standard to maximise interoeprability and functionality. But ODF is application specific to the way OpenOffice works. It was not designed from a clean slate. Nor was the original 2002 OpenOffice XML spec designed as an open source effort! Check the OOo source code if you doubt this claim. The ONLY contributors to Open Office XML were Sun employees! What the world needs is in fact a format standard designed to maximise interoperability and functionality. This requires a total application-platofrm-vendor independence that neither ODF or OOXML can claim. The only format that meets these requirements is the W3C's family of HTML-XML formats. These include advancing Compound Docuemnt Framework format components such as (X)HTML-5, CSS-3, XForms, SVG and SMiL.. The W3C's CDF does in fact meet the markeplace needs of a universal format that is open, unencumbered and totally application, platform and vendor independent. The only trick left for CDF is proving that legacy desktop applications can actually implement conversions from existing in-memory-binary-representations to CDF without loss of information.
8More
XML.com: Standard Data Vocabularies Unquestionably Harmful - 0 views
-
At the onset of XML four long years ago, I commenced a jeremiad against Standard Data Vocabularies (SDVs), to little effect. Almost immediately after the light bulb moment -- you mean, I can get all the cool benefits of web in HTML and create my own tags? I can call the price of my crullers <PricePerCruller>, right beside beside <PricePerDonutHole> in my menu? -- new users realized the problem: a browser knows how to display a heading marked as <h1> bigger and more prominently than a lowlier <h3>. Yet there are no standard display expectations or semantics for the XML tags which users themselves create. That there is no specific display for <Cruller> and, especially, not as distinct from <DonutHole> has been readily understood to demonstrate the separation of data structure expressed in XML from its display, which requires the application of styling to accomodate the fixed expectations of the browser. What has not been so readily accepted is that there should not be a standard expectation for how a data element, as identified by its markup, should be processed by programs doing something other than simple display.
-
-
ODF and OOXML are contending to become the Standard Data Vocabulary for desktop office suite XML markup. Sun and Microsoft are proposing the standardization of OpenOffice and MSOffice custom defined XML tags for which there are no standard display expectations. The display expectations must therefore be very carefully described: i.e. the semantics of display fully provided.
In this article Walter Perry is pointing out the dangers of SDV's being standardized for specific purposes without also having well thought out and fully specified display semantics. In ODF - OOXML speak, we would call display presentation, or layout, or "styles".
The separation of content and presentation layer of each is woefully underspecified!
Given that the presnetation layers of both ODF and OOXML is directly related to how OpenOffice and MSOffice layout engines work, the semantics of display become even more important. For MSOffice to implement an "interoperable" version of OpenOffice ODF, MSOffice must be able to mimic the OpenOffice layout engine methods. Methods which are of course quite differeent from the internal layout model of MSOffice. This differential results in a break down of conversion fidelity, And therein lies the core of the ODF interoeprability dilemma!
-
-
There have also emerged a few "horizontal" data vocabularies, intended for expressing business communication in more general terms. One of these is the eXtensible Business Reporting Language (XBRL), about which more below. Most recently, governments and governmental organizations have begun to suggest and eventually mandate particular SDVs for required filings, a development which expands what troubles me about these vocabularies by an order of magnitude.
- ...5 more annotations...
-
-
Exactly! When governments mandate a specific SDV, they also are mandating inherent concepts and methods unique to the provider of the SDV. In the case of ODF and OOXML, where the presentation layers are application specific and woefully underspecified, interoperability becomes an insurmountable challenge. Interop remains stubbornly application bound.
Furthermore, there is no way to "harmonize" or "map" from one format to another without somehow resolving the application specific presentation differences.
-
-
-
"in the nature of the SDV's themselves is the problem of misstatement, of misdirection of naive interpretation, and potential for fraud.
Semantics matter! The presentation apsects of a document are just as important as the content.
-
-
-
Walter: "I have argued for years that, on the basis of their mechanism for elaborating semantics, SDVs are inherently unreliable for the transmission or repository of information. They become geometrically less reliable when the types or roles of either the sources or consumers of that information increase, ending at a nightmarish worst case of a third-order diminution of the reliability of information. And what is the means by which SDVs convey meaning? By simple assertion against the expected semantic interpretations hard-coded into a process consuming the data in question.
At this point in the article i'm hopign Walter has a solution. How do we demand, insist and then verify that SDV's have fully specifed the semantics, and not jus tpassed along the syntax?
With ODF and OOXML, this is the core of the interoperability problem. Yet, there really is no way to separate the presentation layers from the uniquely different OpenOffice and MSOffice layout engine models.
-
-
-
Interesting concept here: "the bulk of expertise is in understanding the detail of connections between data and the processes which produced it or must consume it ........ it is these expert connections which SDV's are intended to sever.
Not quite sure what to make of that statement? When an SDV is standardized by ISO, the expectation is that the connections between data and processes would be fully understood, and implementations consistent across the board.
Sadly, ODF is ISO approved, but doesn't come close to meeting these expectations. ODF interop might as well be ZERO. And the only way to fix it is to go into the presentation layer of ODF, strip out all the application specific bindings, and fully specifiy the ssemantics of layout.
-
-
In short, the bulk of expertise is in understanding the detail of connections between data and the processes which produced it or must consume it. It is precisely these expert connections which standard data vocabularies are intended to sever.
2More
What's So Bad About Microsoft? - 0 views
-
Backward Incompatibility Also contributing to Microsoft's goal of putting everybody on a perpetual upgrade cycle is the backward incompatibility in Microsoft's products. Once a small number of users adopt a new version of a Microsoft product all other users are pressured to upgrade lest they are unable to interact with files produced by the newer program. Dan Martinez summed up the situation created with the incompatibility in subsequent versions of Word when he said "while we're on the subject of file formats, let's pause for a moment in frank admiration of the way in which Microsoft brazenly built backward-incompatibility into its product. By initially making it virtually impossible to maintain a heterogenous environment of Word 95 and Word 97 systems, Microsoft offered its customers that most eloquent of arguments for upgrading: the delicate sound of a revolver being cocked somewhere just out of sight." (cited from the quote file) For a more detailed lament of how Microsoft likes to pressure its customers to keep buying the same product over and over by using backward incompatibility, see Zeid Nasser's page on 'Forced upgrading,' in the World of Word.
-
The "Backwards Compatibility" issue is all the rage at ISO, with the September vote on MS OOXML just a month away.
Microsoft and Sun (We've Been Had!) are arguing that ISO should approve MS OOXML (Microsoft OfficeOpenXML) because OOXML offers a backwards compatibility with the legacy of existing billions of binary documents.
This oft sighted history of Microsoft's reprehensible business practices is worth citing once again before the nations of the world go down that treacherous path towards ratifying Microsoft's proprietary systems and products as international standards.
1More
The Meaning of Open Standards - 0 views
-
The marbux comment:
See particularly section 6.8 and its discussion of "etiquettes," which sounds like CDF profiles to me.
This 1998 academic paper on open standards could give us a solid foundation to build our arguments for Universal Interop from. I may have forwarded this link before, roughly a year ago. Here is the abstract of the paper:
This paper develops the argument that many Information Technology standardization processes are in transition from being controlled by standards creators to being controlled by standards implementers. The users of standardized implementations also have rights that they wish addressed. Ten basic rights of standards creators, implementers and users are identified and quantified. Each of these ten rights represents an aspect of Open Standards. Only when all ten rights are supported will standards be open to all.
It builds upon a previous work by Bruce Perens. Well worth the read.
1More
Microsoft's Quest for Interoperability and Open Standards - 0 views
-
Interesting article discussing the many ways Microsoft is using to improve the public perception that they are serious about interoperability and open formats, protocols and interfaces. Rocketman attended the recent ISO SC34 meeting in Prague and agrees that Microsoft has indeed put on a new public face filled with cooperation, compliance and unheard of sincerity.
He also says, "Don't be fooled!!!"
There is a big difference between participation in vendor consortia and government sponsored public standards efforts, and, actual implementation at the product level. Looking at how Microsoft products implement open standards, my take is that they have decided on a policy of end user choice. Their applications offer on the one hand the choice of aging, near irrelevant and often crippled open standards. And on the other, the option of very rich and feature filled but proprietary formats, protocols and interfaces that integrate across the entire Microsoft platform of desktop, devices and servers. For instance; IE8 supports 1998 HTML-CSS, but not the advanced ACiD-3 "HTML+" used by WebKit, Firefox, Opera and near every device or smartphone operating at the edge of the Web. (HTML+ = HTML5, CSS4, SVG/Canvas, JS, JS Libs).
But they do offer advanced .NET-WPF proprietary alternative to Open Web HTML+. These include XAML, Silverlight, XPS, LINQ, Smart Tags, and OOXML. Very nice.
"When an open source advocate, open standards advocate, or, well, pretty much anyone that competes with Microsoft (news, site) sees an extended hand from the software giant toward better interoperability, they tend to look and see if the other hand's holding a spiked club.
Even so, the Redmond, WA company continues to push the message that it has seen the light regarding open standards and interoperability...."
1More
shared by Gary Edwards on 23 May 11
- No Cached
A New Patent Application from Apple Introduces us to a Breakthrough Platform Independen... - 0 views
www.patentlyapple.com/...ndependent-word-processor.html
apple-patent browser-wordprocessor layout-engine
shared by Gary Edwards on 23 May 11
- No Cached
-
excerpt: This could be Apple's new internet strategy that thrusts more of us into the next phase of what is now known as the Post-PC era. In my view, this breakthrough could be a game changer. The Problem to Solve The recent proliferation of web browsers and computer networks has made it easy to display the same document on different computing platforms. However, inconsistencies in the way fonts are rendered across different computing platforms could cause the same document to be rendered differently for users of different computing platforms. More specifically, for a given font, the way in which metrics for various font features are interpreted, such as character height, width, leading and white space, can differ between computing platforms. These differences in interpretation could cause individual characters in a document to be rendered at different locations, which could ultimately cause the words in a document to be positioned differently between lines and pages on different computing platforms. This inconsistent rendering could be a problem for people who are collaborating on a document. For example, if one collaborator points out an error on a specific line of a specific page, another collaborator viewing the same document on a different computing platform may have to first locate the error on a different line of a different page. Hence, what is needed is a technique for providing consistent rendering for documents across different computer systems and computing platforms. Apple's patent application describe a system that typesets and renders a document in a platform-independent manner. During operation, the system first obtains the document, wherein the document includes text content and associated style information including one or more fonts. The system also generates platform-independent font metrics for the one or more fonts, wherein the platform-independent font metrics include information that could be used to determine the positions of i
2More
shared by Gary Edwards on 04 Jun 11
- No Cached
The big winner from Apache OpenOffice.org | ITworld - Brian Proffitt - 1 views
www.itworld.com/...ig-winner-apache-openofficeorg
OOo OpenOffice Apache-OpenOffice marbux Brian-Proffitt
shared by Gary Edwards on 04 Jun 11
- No Cached
-
Brian is once again writing about OpenOffice and ODF, this time in the aftermath of Oracle's decision to cut OOo loose and turn it over to Apache instead of The Document Foundation. Good discussion - features a lengthy comment from the mighty Marbux where he vigorusly corrects the river of spin coming out of IBM. Worth a careful read! excerpt: IBM seems to maneuver itself to any open source project that suits its needs, and for whatever reason they have decided to hitch their wagon to Oracle's star (or vice versa). With this historical context, there is really little surprise in Oracle's decision to go with the Apache Software Foundation, because IBM was probably influencing the decision. My second question doesn't have a definitive answer--yet. But it needs to be answered. It is simply this: how will OpenOffice.org remain relevant to end users?
-
I should have added to that comment a stronger warning for the Apache Foundation Board and developers considering joining the IBM-backed Apache OpenOffice.org incubator project in regard to the danger posed by IBM and Oracle's control of the OpenDocument Formats Technical Committee at OASIS, aptly characterized by IBM's Rob Weir: "Those who control the exchange format, can control interoperability and turn it on or off like a water faucet to meet their business objectives." Rob Weir, Those Who Forget Santayana, An Antic Disposition (20 December 2007), http://www.robweir.com/blog/2007/12/those-who-forget-santayana.html What IBM, Oracle, and others can do by manipulating the ODF specification that Apache OOo depends upon is something entirely outside the control of the Apache Foundation. And as history has taught us so well, IBM and Sun exercised that control mercilessly via their co-chairmanship of the ODF TC to block all real interoperability initiatives. That is the very reason that only ODF implementations that share the same code base can interoperate. And if one were tempted to think that IBM and Sun/Oracle would not even consider manipulating the ODF specification to their own commercial advantage, consider the fact that in writing the quoted statement above, Rob Weir was speaking from deep personal experience in in such activities. So beware, both Apache Foundation and LibreOffice developers.
1More
WebODF - 1 views
-
WebODF is a JavaScript library that makes it easy to add Open Document Format (ODF) support to your website and to your mobile or desktop application. It uses HTML and CSS to display ODF documents. WebODF is a Free Software project. All code is available under the AGPL. This means that you can use the code free of charge, investigate how it works, and share it with others. Description of WebODF From LWN: ODF on the web An especially interesting project that was presented is WebODF, which wants to bring ODF to the web. Jos van den Oever started from the observation that a lot of office suites are moving into the "cloud". Examples are Microsoft Live Office, Google Docs, and Zoho. But where are the free software alternatives for the cloud? For OpenOffice.org, KOffice, AbiWord, and Gnumeric, there are none that have a cloud version with ODF support. That was the motivation for Jos to start a project to fill in this gap and let users view and edit ODF documents on the web without losing control of the document into some company's servers. The strategy Jos followed was to use just HTML and JavaScript for the web application. The application then loads the XML stream of the ODF document as is into the HTML document and puts it into the DOM tree. Styling is done by applying CSS rules that are directly derived from the and elements in the ODF document. That is how WebODF was born; it is a project with the initial goal of creating a simple ODF viewer and editor for offline and online use, implemented in HTML5. The small code base consists of one HTML5 file and eight JavaScript files, each of which is a few hundred lines of code. The most interesting part is that it doesn't need server-side code execution: the JavaScript code is executed in the user's browser and saving the document to the web server is done using WebDAV. It supports both the Gecko and WebKit HTML engines. There is also an implementation on top of QtWebKit, which is
1More
shared by Gary Edwards on 16 May 11
- No Cached
Roambi Flow turns your business information into gorgeous iPad reports | VentureBeat - 0 views
venturebeat.com/...roambi-flow-launch
Roambi-Flow visually-immersive HTML+ iOS Web-Compound-Documents
shared by Gary Edwards on 16 May 11
- No Cached
-
Now that's what i'm talking about! Business documents published in an advanced Web Productivity RIA format. Roambi Flow targets the iPAD with business reports based on SalesForce.com and other business productivity platforms hosting basic business intelligence and information. Roambi packages the reports in the increasingly popular visually immersive webzine style similar to FlipBoard, Zite, TreeSaver, OnSwipe, Push Pop, Instapaper, Readability, Pulse, PressJack, TweetMag, Sports Illustrated and the NYTimes iOS editions. Beautifully done. My guess is that the underlying format is the visually rich and interactive HTML+ (HTML5-CSS3-JSON-JavaScript-Canvas/SVG). excerpt: After revolutionizing the way companies can interact with their business data on the go with its Roambi app, San Diego-based startup Mellmo is now aiming to let you use that data to create gorgeous interactive reports and presentations with its new iPad app and publishing platform Roambi Flow. The move is the next step in Mellmo's plan to make business intelligence (BI) more accessible, and dare I say it, sexy. Mellmo's initial Roambi app integrates with existing BI systems, including Salesforce and SAP, letting business owners and executives easily make sense of their data with interactive charts, graphs and more. Now with Roambi Flow, that data can be used to create magazine-quality reports and presentations that can be shared more easily with any iPad user.
1More
shared by Gary Edwards on 23 Aug 11
- No Cached
UseOffice. Net - A Modern Component to Accurately Convert Popular Office Formats - 1 views
www.sbwire.com/...sbwire-104408.htm
cloud-productivity desktop-productivity Document-Management-System
shared by Gary Edwards on 23 Aug 11
- No Cached
-
Cloud based Productivity Platforms and Document Management Systems just got a huge "integration with legacy desktop productivity environments" boot from UseOffice. Net - a powerful component for integration of converting functions to Web-server ASP.NET and desktop applications Windows Forms applications for the platform of Windows, including the following versions: 2000, XP, Vista, 2008 Server, Seven. Applications built on the basis of this component, allow the user to quickly, and most importantly - accurately convert the formats DOC, DOCX, RTF, PPT, PDF, HTML, XHTML various documents - reports, forms, invoices, articles, forms, presentations, web pages etc. The converted documents are fully preserve the visual characteristics of the original, including elements of the structure and format, such as tables, font styles, colors, page margins, etc. UseOffice. Net Supports the following areas of transformation: - DOC to: html, xml, rtf, txt, pdf, docx - DOCX to: html, xml, rtf, txt, pdf, doc - HTML to: doc, rtf, txt, pdf - XLS to: html, xml, txt, csv, rtf, pdf - RTF to: html, xml, txt, doc, pdf - PPT to: html, xml, rtf, pdf, jpg, bmp, gif - XLSX to: html, xml, txt, csv, rtf, pdf Integrate the components into an application quickly and easily - just add a couple lines of code. The component is written in C # and requires the set. NET Framework and Microsoft Office (any version from 2000, XP, 2003, 2007, 2010). The following development environments: C #, VB.Net, J #, C + +. NET, Delphi.NET, ColdFusion 8, ASP.NET, and many others ... Combining ease of use and quality conversion UseOffice. Net allows you to set page numbers in the final document, orientation and page size settings for images and more necessary in the conversion.
3More
Groklaw - Digging for Truth - 6 views
-
You harmed us and our families. You harmed the public, and you will have to live with that judgment from us.
-
Legendary comment ... :o) "You harmed our families. You harmed the public and you will have to live with that judgement from us"
-
-
What an amazing conversation. It's true that ODF was NOT designed to be compatible with MSOffice and the legacy binary format. That's not to say there were not considerable efforts within the OASIS Open Office XML TC (ODF) pushing for compatibility. But Sun successfully held off these efforts, insisting that ODF was not designed to be compatible with MSOffice or the MSOffice binaries. Many asked the obvious question, "How are end users supposed to convert their information (billions of legacy "in-process" binary documents) to ODF if ODF is not designed for that conversion?" Stellent, represented by Phil Boutros, and Corel, represented by Paul Langille and Tom Magliery, were particularly obsessed with this problem. Without "compatibility", how were end users supposed to convert their documents? Needless to say, Sun prevailed. ODF is 100% perfectly compatible with OpenOffice/StarOffice, by design. It is not compatible with the billions of "in-process" compound business documents essential to world trade, commerce and information exchange. What a shame, ~ge~
1More
"A Strategy For Openness" : Report to the NYS Governor and Legislature (CIO/OFT) - 0 views
-
This is the report John Cody worked on. I spent four months answering his questions but was unable to adequately explain to him the difference between an "Office Suite" and a workgroup-workflow centric "Productivity Environment". John insists that it's entirely possible to rip-out-and-replace the MSOffice editors with the free OpenOffice Suite without disrupting important workflows and business processes. I explained to him what happened in Massachussetts, including the 300 page pilot study report Sam wrote. What he needs to do i think is pay close attention to the Burton Group coverage of what is now known as the SharePoint Foundation platform; SharePoint 2010 having totally swallowed the MSOffice 2010, leaving the venerable desktop productivity office suite as an important end user interface into information rich business systems centered on the SharePoint "Unified Productivity" platform.
7More
Microsoft attacks UK government decision to adopt ODF for document formats - 0 views
-
the panel reached consensus that one standard is important to ensure interoperability and to allow users to collaborate effectively on the same document,” said the minutes
-
A subsequent meeting of the same panel also considered a detailed comparison of ODF and OOXML, citing concerns raised by one member. “We need to make sure there is sound reasoning to back up the decision as this may incur significant costs to some government departments. The comparison may be slightly skewed by concentrating solely on implementation of strict OOXML, which is an emerging standard similar to ODF 1.3, whilst considering implementations of all ODF versions. It ignores transitional OOXML which does have very wide support, arguably wider than ODF,” said the meeting minutes.
-
“LH described the issues identified in the [comparison] document and added that there has since been some confusion about support for OOXML strict in LibreOffice. It appears that LibreOffice supports the standardised transitional OOXML, as well as a different Microsoft version of transitional OOXML,” the minutes stated.
- ...3 more annotations...
-
Despite its obvious disappointment at the government’s decision, Microsoft was also keen to point out that its software does fully support ODF.
-
“The good news for Office users is that Office 365 and Office 2013 both have excellent support for the ODF file format, so their current and future investments in Office are safe. In fact, Office 365 remains the only business productivity suite on the UK government’s G-Cloud that is accredited to the government’s own security classification of 'Official' and which also supports ODF,” said the Microsoft spokesman.
-
Government Digital Service director Mike Bracken
-
"Microsoft has attacked the UK government's decision to adopt ODF as its standard document format, saying it is "unclear" how UK citizens will benefit. The Cabinet Office announced its new policy yesterday, whereby Open Document Format (ODF) is immediately established as the standard for sharing documents across the public sector, with PDF and HTML also acceptable when viewing documents. SERGIGN - FOTOLIA The decision was a rejection of Microsoft's preference for Open XML (OOXML), the standard used by its Word software, which remains the dominant wordprocessor in government. "Microsoft notes the government's decision to restrict its support of the file formats it uses for sharing and collaboration to just ODF and HTML," said a spokesman for the software giant in a statement to Computer Weekly. "Microsoft believes it is unproven and unclear how UK citizens will benefit from the government's decision. We actively support a broad range of open standards, which is why, like Adobe has with the PDF file format, we now collaborate with many contributors to maintain the Open XML file format through independent and international standards bodies," it added"
5More
shared by Gary Edwards on 11 Aug 14
- No Cached
We Can No Longer Unbundle Microsoft Office - 0 views
techcrunch.com/...cannot-unbundle-office-anymore
wordsdk Office-365 office-formats Office-Productivity
shared by Gary Edwards on 11 Aug 14
- No Cached
-
In 2007, productivity reached the cloud when the EU forced Microsoft to open the file formats to OpenXML and add an x at the end of our familiar file extensions .pptx, .xlsx and .docx. Google Docs also quickly floated cloud versions of each Office document format. However, in the same year, Apple launched iPhone without a view to file storage on the device. Since then a lot of startup innovation came from Dropbox and Box unbundling file storage from the OS, but software that enables the creation and editing of files on touchscreen devices has been less of a concern.
-
2007 was also the year that Apple released the first iPhone. ISO standardised PDF with a unique very valuable attribute; "tags". Tagged PDF raced into the mobility breach enabling all kinds of data binding and digital signature advances critical to mobile document centric workflows. In 2008 we saw a global financial collapse that put more pressure than ever on productivity. To survive, companies had to do more with less. Less people, less resources and less money. Cloud computing and mobility rose to the occasion, but the timing of the cloud tsunami connects the incredible synchronicity of XML compound document formats (business documents), Tagged PDF, the iPhone, and the financial collapse of 2008. The rise of sync-share-store services like DropBox is a natural replacement of the local, workgroup bound, client/server hard drive problem. Most importantly though, the iPhone is the first device to integrate and combine communications with computation. The data had to move to the Cloud before it could become useful to mobile apps combining for the first time, communications, content and computation is hand held devices. Anyone who ever worked in the Microsoft client/server productivity ecosystem will tell you that the desktop PC was totally lacking in "communications"; let alone the kind of integrated communications that the iPhone offers. It is the integration of communications, content and collaborative computation that will make the productivity of Cloud Computing something extraordinary.
-
-
Three years ago, CloudOn CEO Milind Gadekar started using OpenXML formats to bring Microsoft Office to iPad. Since then, the company opened its interface to file authoring tools from Office and Google Drive, and storage providers like Dropbox, Box and Hightail, Google Drive, and OneDrive, and will soon be hard at work adding Apple’s CloudDrive. CloudOn feels that if it focuses on providing the best compatibility and exportability across devices, then they can be the place where users can “preserve, render and manipulate” documents on mobile. Once CloudOn can maintain its goal of giving consumers a familiar look and feel and lossless publishing for all the most popular document creation and storage providers, they plan to optimize for touchscreens. CloudOn sees only single-digit-minute session times in files, so their next step is to enable gestures to edit charts and annotate text with your fingers to help make better use of that time.
-
Feature-bundled workflows to get things done on the device you’re looking at are necessities, not nice pairings like chocolate and peanut butter.
- ...1 more annotation...
-
Pellucid Analytics takes a different strategy to rebuilding PowerPoint. Instead of looking at PowerPoint as a design tool, Pellucid fixes the design and enables archive search for thousands of financial accounting slide templates that an analyst would need to fill a pitch book such as ROE, EBITDA and other fun acronyms. Since the formatting is already set, analysts can just enter company names and based on the data sources that the bank they work for has licensed, Pellucid can fill in any of that data automatically and keep it up to date. However, the concept of live data in presentations is a shock to most bankers, so Adrian Crockett of Pellucid admits that it’s one of the first things he has to explain to new users. Of course, Pellucid offers the ability to snapshot data for use in later presentations. But Adrian stressed that in addition to Pellucid’s approach to removing grunt work for analysts, it is giving senior bankers access to live data right in the presentation that would normally require VPN access, logins, app switching and all other sorts of headaches to be able to access, especially on tablets.
1More
Guest Post Online - 0 views
-
Article Writing & Guestpost You Can Join this Site for Your Article & guest post, Just Easy way to join this site & total free Article site. This site article post to totally free Way. Guest Post & Article Post live to Life time only for Current & this time new User. http://guestpostonline.com
2More
shared by Gary Edwards on 12 Dec 07
- Cached
Mass. Set to Mix Office With ODF - 0 views
www.computerworld.com/...article.do
california davinci interop iso massachusetts oasis odef odf ooxml opendocument politics xml
shared by Gary Edwards on 12 Dec 07
- Cached
-
Massachusetts last week officially confirmed that its executive agencies for now will continue using Microsoft Office instead of switching to alternative desktop applications. But by Jan. 1, in keeping with a controversial policy announced last year, the state plans to start adding plug-in software that will let its Office users create and save files in the industry-standard OpenDocument format.
-
The August 28th, 2006 article about Massachusetts decision to use addon plugins. ComputerWorld - Caarol Sliwa
3More
shared by Gary Edwards on 12 Dec 07
- Cached
Odf - Converters & the ODF Zero Interop problem - 0 views
odf-converter.sourceforge.net/features.html
microsoft mooxml oasis odf officeopenxml opendocument openxml sun
shared by Gary Edwards on 12 Dec 07
- Cached
-
The ODF-Converter translates OpenXML documents (.DOCX) to Open Document Format (.Open Document Format) (and conversely) for Open XML processing applications. You will find below the list of unsupported features which may be due to standard compatibility issues, or to the translator itself (see rendering issues as discussed in the blog)...
-
Explosive compatibility - interoperability study concerning ODF and MOOXL! This has Florian's signature written all over it, and it goes right to the heart of the matter.
David A. Wheeler submitted a comment to the OASIS ODF TC outlining his concerns with this publication. He suggests that a few minor changes to ODF could greatly improve compatibility - interop issues. He also figures out that OpenOffice - ODF has more features than MSOffice - MOOXML. Wha the doesn't ge is that it is these new and innovative features that continue to increase the difficulties of implementing ODF in real world business process workgroups!
David also ignores the fact that the TC jus tvoted down the Novell "LIt Enhancement Proposal" which was specifically designed to address the compatibility - interop issues outlined in this odf-converter blog! Given a choice, the ODF TC members chose the new and innovative features of the interop breaking Sun-KOffice "List Enhancement Proposal".
The List Enhancement Proposal discussion was so contentious and focused on personal destruction as to represent a total break down of the ODF concensus process. There is no way that either the Foundation or Novell will ever contribute another compatibility - interop enhancement proposal given the personal assault and determined oppostion of Sun to compatibility - interoperability initiatives.
The hard lesson the Foundation learned is that if you oppose Sun, you'll get booted out of OASIS!
The lesson Novell learned is that they are better off working through Ecma 376 to resolve these issues that the public demands be addressed.
Notice the last line in David's comment, "In any case, the MUCH, MUCH longer list of problems with Microsoft XML format isn't our problem."
During the contentious List Enhancement Proposal and the compatibility - interop related Metadata RDF/XML discussions, ODF members freque -
These are the same guys who just voted against the Novell List Enhancement Proposal that did exactly what the odf-converter blog claims needs to be done if the compatibility-interop problems are to be resolved!
2More
shared by Gary Edwards on 12 Dec 07
- Cached
Evermore Integrated Office - 0 views
www.evermoresw.com/...index.jsp
california davinci interop iso massachusetts oasis odef odf ooxml opendocument politics xml
shared by Gary Edwards on 12 Dec 07
- Cached
-
EIOffice includes the features found in Microsoft Office, plus a number of productivity features found nowhere else.
-
Homepage for EIOffice, a complete JAVA clone of MSOffice. This stuff is excellent! Easily surpasses OpenOffice in terms of file format conversion and compatibilitiy. EIOffice is fully capable of "round tripping" documents with MSOffice users without compromising fideltiy. Supports UOF but not ODF or MOOXML
3More
shared by Gary Edwards on 12 Dec 07
- Cached
What will it be for ODF? Continuation of limited interop? Or a transition to Universa... - 0 views
lists.oasis-open.org/...msg00072.html
cdf conformance-clause interoperability marbux metadata odf odf-tc ooxml
shared by Gary Edwards on 12 Dec 07
- Cached
-
-
Preserving metadata! Preserving application specific information. Preserving "unknown" information inside of a document
-
-
Unless we add conformance requirements for the preservation of metadata and processing instructions, the less featureful apps will never be able to round-trip documents with the more featureful apps. Our language should require that. Personally, I believe that the software-as-an-end-point client-side office suites are dinosaurs at the end of their era. They are being finished off by a thousand cuts as users spend less and less time using them and more and more time using other apps, such as web apps. ODF either develops methods for interoperability among all apps or it will die along with the office suites. E.g., Microsoft knows this and is busily migrating its Office development budget across the Sharepoint/Exchange server hubs to the network. Meanwhile, this TC fiddles with preserving the 1995 software-as-an-endpoint vision.
-
Marbux is clearly at the top of his game here as he hammers the interoperability issue.