Skip to main content

Home/ Document Wars/ Group items matching ""Office Open XML"" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
Graham Perrin

Doug Mahugh : 1 + 2 = 1? - 0 views

  • five prioritized guiding principles for Office’s ODF implementation
  • When Will Office Support OpenFormula?
  • nobody knows yet when ODF 1.2 will be published as an OASIS or ISO standard
  • ...4 more annotations...
  • risk that the results might not be the same
  • Open XML / ODF Translator Add-Ins for Office can be used with Office 2007 SP2
  • Sun ODF Plugin
  • apparently works with SP2
Gary Edwards

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.
    • Gary Edwards
       
      Hey, nice comments!
  •  
    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~
Graham Perrin

FR: Advocacy group protests government's approving of OOXML - - 0 views

  • FR: Advocacy group protests government's approving of OOXML
  • Nov 20, 2009
  • Gijs Hillenius
  • ...6 more annotations...
  • April, a French free and open source software advocacy group, is protesting the French government's approval of Microsoft's OOXML as a government document standard, alongside the open document format ODF.
  • General interoperability framework for public administrations and local governments, RGI
  • Référentiel Général d'Interopératibilité
  • We have just missed a historical opportunity to support openness and innovation in the software market
  • calling on members of the French parliament to clarify the RGI
  • The RGI does not resolve the controversy between software publishers and supporters of free software. Both standards office are placed 'under observation', and their use remains at the discretion of each administrative authority.
Gary Edwards

PlexNex: Achieving Openness - 0 views

  • "ECMA 376" is a set of file formats subject to ECMA and now to ISO. "Office 2007" is a set of file formats which extend "ECMA 376" file formats. Office 2007 file formats are undocumented per se. ECMA 376 are. ECMA 376 file formats are documented but only at a syntactic level. To realize the true meaning of every single attribute is to realize that the documentation is more like 600,000 pages, not 6,000. Of particular difficulty is to keep some kind of control over the virtually infinite combinations of such attributes. Quick analysis of the underlying schemas reveals that simple concepts such as text formatting is expressed in no less than 6 different and incompatible ways. This leads to thinking that the file formats were only designed to comply with existing legacy formats that themselves are the result of 15 years of inside/outside library aggregation (some of the libraries were bought from non-Microsoft vendors). In fact, the truth is, ask any reverse engineer third-party who worked with legacy formats, they'll tell you Microsoft essentially added angle brackets around the binary serialization in legacy formats. This makes for a very cool XML-based file format, not an international standard.
  •  
    Whoa, Stepen Rodriguez knocks this one out of the park.  What an impressive dissembling of MS OfficeOpenXML and it's poor sister subset, Ecma 376.  Incredible. 
Gary Edwards

Opportunity Knocks - 0 views

  • With the news that another state–California–is considering adopting open standard XML-based file formats for office documents (which could be interpreted to mandate ODF), and the continued march of governments around the world to ODF (ISO/IEC 26300:2006), their poorly-done translator is not likely to meet the standard. For one thing, it “bolts” ODF capability on, rather than building it in as a fully-native peer format. It also uses XSLT to attempt the translation when OOXML’s design is not fully usable with XSLT. I cannot see how they could have created a more error-prone method to do the conversions. This could potentially cause Microsoft’s office applications suite to be expelled from government agencies and their employees and contractors.
  •  
    Count on Walt Hucks to nail it every time.  Once again he comes through with another gem, commenting on the Mary Jo Foley interview with the slippery Tom Robertson, General Manager of laugh out loud "Interoperabiltiy and Standards" for Microsoft.  I kid you not. 

    Microsoft describes their highly proprietary and self serving implementation of interoperbiltiy as, "Interoperability by design".  Which means, only those applications, systems and services designed by Microsoft will have the needed interoperability consumers must have to make sense of the many volumes of information and information processes that drive critical day to day workflows.

    Now with Ecma 376, we have a clear example of Microsoft "Standards by Design".  Very sad, but it's our lot in life.

    Thanks Walt, once again a great commentary,
    ~ge~

Gary Edwards

Open XML trumps ODF in document format fight, consulting firm says - 0 views

  • The OpenDocument Format (ODF) remains "more of an anti-Microsoft political statement than an objective technology selection" by users, according to a report released Monday by analysts at Burton Group, who recommend that companies adopt Microsoft Corp.'s Office Open XML document format whether or not it is approved as an ISO standard next month.
Gary Edwards

California may join rush of states toward ODF - 0 views

  • Like the other two measures, the bill in the California Assembly doesn't list any specific document formats that could be used. But as in Minnesota and Texas, the introduction of such a bill appears to be another potential win for backers of the Open Document Format (ODF) for Office Applications.
  •  
    Good article about the opening salvo in what promises to be a long, hard fought war with Microsoft.  Unlike what has happened in the EU and Massachusetts, this time our friends in Redmond are politically facing off on the home turf of their powerful enemies in Silicon Valley, which stretches from the south of market area (SOMA) all the way down the San Francisco peninsula to San Jose, arching around the entire Bay area.

    If you thought it was raining dollars from Redmond in Massachusetts as the great monopolist moved to successfully shut down the entire Information Technology budget, including HomeLand Security projects, the battle of California promises to be the el nino of perfect storms.  I'm confident though that California CIO Clark Kelso and five star brigadiere general Bill Welty will stand tall against the storm.  I can hardly wait for the forces to move into place and the action begin.  What a show this is going to be.

    Meanwhile, what's at stake here is all the marbles of our digital future.  Forcing Microsoft to accept and fully implement the OpenDcoument XML file format is something the great monopolist has shown they will fight to the bitter end.  Brace yourselves!

Gary Edwards

Open Stack: Game Time for OpenDocument - 0 views

  • IMHO, it all comes down to one question: > *... Is ODF able to handle everything EOOXML was designed for? Is there something you can do in EOOXML that can't be done with ODF? > Microsoft insists that the reason they developed EOOXML is that ODF is inadequate and unable to handle the advanced features of MSOffice, and, most importantly, the billions of binary legacy documents produced by the many versions of MSOffice still in production. > The answer to this question is that ODF can handle everything MSOffice can throw at it. > There are two ways of proving this. >
  •  
    The primary difference between ODF and MOOXML is that ODF was designed to be a universal file format.  MOOXML was designed to be an XML file format for MSOffice, the Win32 API, and the Vista Information Processing Chain API (.NET 3.0). 

    ODF is application and platform independent.  MOOXML is application and platform specific.  It's bound to the Windows - Vista platform. 

    Microsoft's Brian Jones recently got caugh tup in a argument with the heavily armed WMD ODF expert and combatant Sam Hiser (WMD=Words of Massive Destruction).  In their exchange, Brian got confused over this very important distinction between ODF and MOOXML.  ODF allows specific applications to place their configurations and requirements in a settings file that is separate from the content, presentation and metadata containers.  MOOXML on the other hand makes no distinction whatsoever between application specific (MSOffice only) configuration, settings, processsing instructions and systemm dependencies and the rest of the file format contents.  Application settings are bound to content, presentation, and schema containers.  So bound that Brian is seemingly unaware of what ODF has achieved.  Sam caught him by surprise, as did many others posting comments:

    Brian Jones on MOOXML support for older versions of MSOffice:  Coments by Sam the WMD Man are below.


Gary Edwards

In Office SP2, Microsoft manages to reduce interoperability | TalkBack on ZDNet - 0 views

  •  
    ODF is important. So What Went Wrong? Response to Jeremy Allison: Having participated in a number of government pilot studies, I must say that you are right; government officials do care about ODF. They really want it to work. But they also had expectations that ODF simply wasn't designed for. What they expected ODF to be was an open technology based on highly-structured XML markup that was application, platform, and vendor-independent, backward compatible, universally interoperable, and importantly, Web ready. That is not ODF nor is it OOXML. In fact, the closest thing we have for meeting these expectations is an ajax-webkit style HTML+ (HTML5, CSS4, SVG/Canvas, JS jQuery, etc.). ODF is highly structured, but it is not application-independent. .....
Paul Merrell

Microsoft Finds Fault With Google Upgrade -- Redmondmag.com - 2 views

  • Google's announcement this week that it had improved its Google Docs Web apps drew ridicule from a Microsoft official on Wednesday.
  • Kisslo also accused Google of not following the OpenDocument Format (ODF) spec with fidelity in Google Docs applications. The Google spokesperson called that claim "ironic" for Microsoft. (Microsoft has had its own issues staying true to the ISO/IEC-standardized version of its Office Open XML document format spec. However, the company did previously announce support for ODF in Office 2007.) This seemingly minor spat between the two companies has deep implications. At stake may be much of Microsoft's empire, based on its two cash cows: Microsoft Office and Windows.
Gary Edwards

ODF1.2 Interoperability Proposal - 0 views

  • Subject: Suggested ODF1.2 items From: "Florian Reuter" &lt;freuter@novell.com&gt; To: &lt;office@lists.oasis-open.org&gt; Date: Mon, 20 Nov 2006 17:03:24 +0100 Suggested enhancement for OpenDocument V1.2
    • Gary Edwards
       
      This message was submitted to the ODF-OOo/SO OASIS TC the day Florian joined Novell. His Novell contract allowed him to continue his work as the OpenDcoument Foundation's CTO. Take note of the response from Sun's Michael Brauer. It's a classic. The link is at the bottom of the page. ~ge~
  •  
    Part of the sad but enduring "History of Failed ODF Interoperability Attempts".  This particular message is dated November 20th, 2006. 

    The OpenDocument Foundation was notified a week earlier that the "benefactor" ODF Community group Louis Gutierrez had asked IBM and Oracle to put together in Massachusetts had failed.  This was the group Louis formed around the da Vinci plugin and our InfoSet APi. 

    Florian has been hired by Novell, and his first day on the job he finds out about the IBM - Novell deal with Microsoft.  Now he has write the MOOXML plugin for OpenOffice using the MS-CleverAge Translator Project work.  So he writes this message to the ODF TC [office] list. 

    The interoperability enhancements Florian suggests are based on the <interoperability eXtensions> submitted in August to the ODF Metadata SC for consideration.

    The first element in this list tha tFlorian chose to tackle related to "Lists".  He called it the "LIst Override Proposal".  This became the now infamous "List Enhancement Proposal War" that resulted in Sun having OASIS boot out the Foundation.

    Such is life in big vendor ODF'dom

    ~ge~

Gary Edwards

Redmond Developer News | The Coming OOXML Showdown - 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.
Gary Edwards

IBM's Director of Strategy comes clean on OpenXML - IBM *WILL* support OpenXML in its Lotus and Portal products - Notes2Self.net - 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"
Gary Edwards

Home - Berkman Center for Internet & Society - 0 views

  • There were 5 successive Roundtables.  Each roundtable was led by 5 short presentations before the topic was opened to the floor for general discussion.  The first roundtable focused on "What is ODF, and why are open document standards important". There were many questions regarding how open standards affect competition and innovation, whether ODF is in fact the best standard, issues of archiving and interoperability with ODF as well as how ODF addresses/will address concerns of accessibility for disabled persons. The second Roundtable discussed how various software developers were responding to ODF and the third roundtable focused on whether governments or non-governmental and consumer organizations should systematically use procurement policy to promote ODF.  The following roundtable was a lively discussion on whether national or global "agreements" can play a role in promoting ODF and how.  During that roundtable as well as the last one on "Reflections and next steps", there were discussions of future work and strategies on ODF in a new international forum, the Internet Governance Forum (IGF) to be held in Athens, Greece, October 30 - November 3, 2006.
    • Gary Edwards
       
      The Berkman Center for Internet & Society at the Harvard Law School held an Open Document Conference, October 23rd, 2006. Just a few weeks after the October 4th, 2006 resignation of Massachusetts CIO Louis Gutierrez. This is the summary report of organizer Manon Ress. Sam Hiser represented the OpenDocument Foundation. The ZERO Interop problems that plague ODF implementation were not discussed. Strangely :) Another point not discussed is the fact that ODF is not an Internet file format. It's a desktop office suite only format. This constraint is written into the ODF charter. Interestingly, one of the problems of making ODF Web ready is that of highjacked W3C standards. Highjacking occurs when a specification or application takes existing W3C standards and changes the namespace reference to it's own. This is what ODF does. The reason for doing this is to constrain and limit the W3C standard to just those aspects implemented by the ODF reference application, OpenOffice. XForms, SVG, SMiL, XHTML, RDF/XML and RDFa are problematic examples of W3C namespaces that have been highjacked by ODF to meet the specific implementation constraints of OpenOffice. This impacts developers who rely on standard libraires to do conversions and processing. The libraries are built to the proper W3C namespace, and unfortunately assume that ODF complies. It doesn't, So developers have to investigate how OpenOffic eimplements XForms and SVG, and build special ODF libraries before they can use ODF on the Web. It can be done, i think. But it's a train wreck of a mess guaranteed to destroy the high level of web interoperability users and developers expect.
Gary Edwards

The Age of OOXML Computing - thanks a pant load Sun! - 0 views

  • Why does Microsoft want another standard, what's the rationale? There are at least 4 good reasons why: *ODF started out and was completed as an XML format, specifically supporting OpenOffice with a tight scope around that product. *It wasn't until 2005 that the spec was offered up as a general XML office document format and consequently renamed to ODF. *No opportunity existed for Microsoft to actually participate in this full process - given the original scope, the 6 months between the re-naming of the spec to ODF, and its subsequent approval by OASIS as a standard. *The scope of the ODF spec never included even the basic requirements that Microsoft required to support a fully open format, and nor did the OASIS technical committee want to include these requirements.
  •  
    Erwin's StarOffice Tango has an exhaustive response to this Microsoft Q&A. Correcting false statements by Microsoft
Gary Edwards

Plan B: The NO ViSTA Mandates, and the failure of ISO/IEC - 0 views

  • Plan B: The "NO ViSTA" Mandates:&nbsp; the failure of Anti Trust Laws and International Trade Agreements to Stop The Great Monopolist, Microsoft A series of surprising government mandate announcements rolled out in the immediate aftermath of the ISO/IEC decision to fast track Ecma 376 otherwise known as Microsoft Office Open XML (MOOX).&nbsp; The three articles commented on here are all from Information Week, who has done yeoman work concerning the OpenDocument - MOOX controversy that has so upset Microsoft.&nbsp; Now the mighty monopolist can taste victory, with fast track approval of MOOX certain, and ISO/IEC in the bag.&nbsp; Incredibly the company that escaped a Court ordered death sentence by purchasing what amounts to a presidential pardon.&nbsp; They even avoided the stink of their own lobbyist and henchman Jack Abramoff, and his motley crew of Ralph Reed and Grover Nyquist operatives.&nbsp; Now they are well on their way towards purchasing an International Standard.&nbsp; So much for Plan A.&nbsp; Time for Plan B, the "NO ViSTA" mandate.
  •  
    Okay.  I've combined my three comments into a single page.  Sadly Diigo does not offer spell checking.  My apologies to all.  Hoepfully this will be a better read.
Gary Edwards

Collaboration and Content Strategies Blog: Free Report on ODF/OOXML Available - 0 views

  • The overall document summary: Industry debate about the relative merits of OpenDocument Format (ODF) and Ecma 376 Office Open XML (OOXML) highlights the significance of the productivity application market shift from binary and proprietary file formats to vendor- and product-independent Extensible Markup Language (XML) models. The competitive stakes are huge, and the related political posturing is sometimes perplexing. In this overview, Research Directors Guy Creese and Peter O’Kelly introduce ODF, OOXML, and related World Wide Web Consortium (W3C) standards, and project their implications for future productivity applications.
Paul Merrell

PC Pro: News: Google Docs accommodates Office 2007 file formats - 0 views

  • Google has added support for the DOCX and XLSX file formats to the Google Docs office suite.
  • Google has now rectified this situation following the ratification of the Open XML standard last year, but anybody looking to import the PPTX files used by PowerPoint 2007 will need to wait. The files can be converted into a Google Docs-friendly format, but you'll lose formatting, themes and transition effects.
Gary Edwards

OASIS Open Document Format for Office Applications (OpenDocument) TC - 0 views

  •  
    ODF FAQ written by Michael Brauer with editing by David Faure. Excellent discussion of differences between ODF and MSXML and, the OASIS ODF TC process and the ECMA MSXML process
  •  
    ODF FAQ written by Michael Brauer with editing by David Faure. Excellent discussion of differences between ODF and MSXML and, the OASIS ODF TC process and the ECMA MSXML process
  •  
    ODF FAQ written by Michael Brauer with editing by David Faure. Excellent discussion of differences between ODF and MSXML and, the OASIS ODF TC process and the ECMA MSXML process
Gary Edwards

GullFOSS: It's our way or the highway. So what if new cool features = Zero Interop? Download OOo and get over it already! - 0 views

  • When such new features that enhance the interoperability require enhancements to the Open Document file format we will propose the necessary changes to the OASIS Open Document TC. This way not only OpenOffice.org but also Open Document benefits from our efforts. Florian Reuter, who now works for Novell, lists some of the changes we have in mind in his blog . So there are a lot of common ideas how we can improve the interoperability between OpenOffice.org and Microsoft Word documents and I hope we can work together with Florian here.
  •  
    The chuckleheads at Sun's StarOffice/OpenOffice Hamburg office respond to Florian's comprehensive lis tof suggestions to greatly improve ODF interoperability. 
  •  
    Make no mistake about it. Microsoft is absolutely right about three things: .... Compatibility with existing file formats is not an ODF concern. .... Sun controls the OASIS ODF TC. .... Sun makes certain that ODF is bound tightly to the OpenOffice feature set. Sun's view of interoperability is that of a one way street. Documents can be converted into ODF-OOo/SO, but they are guaranteed to break during any kind of document routing or round tripping. This is also the reason why the Sun "external" plugin for MSOffice fails. One way conversion simply isn't enough to crack the hold MSOffice has on critical day to day business processes. The only way to that is with a conversion process able to maintain high level fidelity while round tripping. As the EU IDABC has figured out, the ODF-OOo/SO specification is loaded with interoperability break points. That's why they are turning to ODEF, which can be seen as a version of ODF that is truly application independent and optimized for interoperability. ~ge~
« First ‹ Previous 61 - 80 of 96 Next ›
Showing 20 items per page