Skip to main content

Home/ OpenDocument/ Group items tagged ibm

Rss Feed Group items tagged

Gary Edwards

Microsoft trounces pro-ODF forces in state battles over open document formats - 0 views

  • Microsoft trounces pro-ODF forces in state battles over open document formats Eric Lai and Gregg Keizer   document.write(''); if (navigator.userAgent.indexOf("Gecko")==-1) { document.write(''); } document.write(''); if (document.getElementById('dclk999')) { document.getElementById('dclk999').src = 'http://ad.doubleclick.net/adi/idg.us.cpw.desktopapplications/index;pos=imu;tile=3;sz=336x280;ord=' + ord + '?'; } document.write(''); if ((!document.images && navigator.userAgent.indexOf('Mozilla/2.') >= 0)|| navigator.userAgent.indexOf("WebTV") >= 0) {document.write('');} June 03, 2007 (Computerworld)
  • Keeping it private The other problem, Mathers said, was the jargon-laden disinformation that committee members felt they were being fed by lobbyists for both IBM and Microsoft. Although lobbyists would tell the committee one thing in private, they got cold feet when asked to verify the information publicly, under oath. "Suddenly, nobody wanted to sign witness affirmation forms and testify," he said. That undermined the credibility of each side, but it particularly damaged the position of ODF proponents. After Wyne testified publicly that in Massachusetts, only a handful of computers had thus far been converted over to using ODF, IBM declined to dispute her claims, Mathers said -- despite having earlier given "gleaming" reports on the progress of ODF in Massachusetts. "That's when I really started to question the whole bill," he said.
  •  
    Uh Oh.  They got IBM dead to rights in Massachusetts.  I guess the truth about Massachusetts will be told!  Finally.  ODF failed in Massachusetts because there isn't a reasonable  means of implementing ODF.  Same in California.
  •  
    A must read.  And yes, the ODF Vendors are the reason ODF lost.  They didn't provide useful solutions.  In fact, the applicaitons they proposed were seen by government CIO's as cstly and disruptive "rip out and replace" non starters.  In California, CIO's asked if it was even possible to implement ODF!!!
Gary Edwards

What IBM VP Bob Sutor does not want you to read | Universal Interoperability Council - 0 views

  • What IBM VP Bob Sutor does not want you to read Submitted by marbux on Thu, 01/31/2008 - 23:36. This site is now live, although there's a ton of customization and configuration work to be done. But we might as well kick off by reprinting a comment I unsuccessfully attempted to post on IBM vice president Bob Sutor's blog today. I'm flattered that my post was the apparent triggering event for Sutor's announcement later in the day that he will now only allow comments from people who use their "real names."
    • Gary Edwards
       
      A must read post from the legendary marbux!
Gary Edwards

Harmonizing ODF and OOXML: The DIN - ISO "Harmonization" Project - 0 views

  •  
    Contact: Gerd Schürmann Fraunhofer Institute FOKUS Tel +49 (0)30 3463 7213 gerd.schuermann@fokus.fraunhofer.de Berlin
  •  
    At a recent meeting in Berlin, The DIN Fraunhoffer Institute pushed forward with the EU project to harmonize ODF and OOXML. Microsoft and Novell attended the harmonization effort. Sun and IBM did not. This in spite of invitations and pleas to cooperate coming into Sun and IBM from government officials across the European continent. We've long insisted that inside the OASIS ODF Technical Committee walls there have been years of discussions concerning ODF compatibility with the billions of MS binary documents, and ODF interoperability with MSOffice. Sun in particular has been very clear that they will not compromise OpenOffice application innovations to improve interoperability with MSOffice and MSOffice documents. The infamous List Enhancement Proposal donnybrook that dominated OASIS ODF discussions from November 20th, 2006, to the final vote in April of 2007, actually begins with a statement from Sun arguing that application innovation is far more important than market demands for interoperability. The discussions starts here: Suggested ODF1.2 items The first of many responses declaring Sun's position that innovation trumps interop, and that if anyone needs to change their application it should be Microsoft: see here DIN will submit a "harmonization" report with recommendations to ISO JTC1. I wonder if IBM and Sun will continue to insist on government mandated "rip out and replace" solutions based on their ODF applications when ISO and the EU have set a course for "harmonization"?
Gary Edwards

A gadfly's take on IBM's 'support' for Open XML | Computerworld Blogs - 0 views

  • On the revelation that some of IBM's products would support a document format that it officially, adamantly opposes, Hiser is not surprised one bit. IBM and Sun have both had "the magic blueprints" to Microsoft's document formats, including Open XML, for the past several years, Hiser said. With that key technical interoperability information, "how could you not expect IBM to start coding around OOXML?" he asked.
Gary Edwards

Microsoft Closer on \'Office Open\' Blessing - 0 views

  • Opponents to OOXML, which include IBM (Quote) and the Open Document Foundation, have argued that Microsoft's specifications are unwieldy and that the standard application is redundant with the Open Document Format (ODF), which already exists. Microsoft has countered that the OOXML format is valuable because it is closer to Office 2007 and is backwards-compatible with older versions of Office. "Although both ODF and Open XML are document formats, they are designed to address different needs in the marketplace," the company wrote in an open letter published earlier this month.
  •  
    Internet News is reporting that Ecma has submitted to the ISO/IEC JTC1 their repsonsess to the 20 "fast track" for Ecma 376 (OOXML) objections.  Nothing but blue skies and steady breeze at their back for our friends at Redmond, according to Ecma's rubber stamper in chief, Jan van den Beld.

    Once again there is that ever present drum beat from Microsoft that ODF can't handle MSOffice and legacy MSOffice features - including but not mentioned the conversion to XML of those infamous billions of binary documents:
    "Microsoft has countered that the OOXML format is valuable because it is closer to Office 2007 and is backwards-compatible with older versions of Office. "Although both ODF and Open XML are document formats, they are designed to address diffe
Gary Edwards

Open Document Foundation Gives Up | Linux Magazine - 0 views

  • The reasons for the move to CDF was improved compatibility with Microsoft’s OOXML format the foundation claimed at the time. Cris Lilley from W3C contradicted. CDF is not an office format, and thus not an alternative to the Open Document Format. This turn-down is likely the reason for the abrupt ditching of the foundation.
  •  
    I've got to give this one extra points for creativity!  All anyone has to do is visit the W3C web sites for CDF WICD Full 1.0 to realize that there is in fact a CDf profile for desktops.  CDF WICD Mobile is the profile for devices.

    My guess is that Chris Lilley is threading the needle here.  IBM, Groklaw, and the lawyer for OASIS have portrayed the Foundation's support for CDF WICD Full as a replacement for ODF - as in native file format for OpenOffice kind of replacement.  Mr. Lilley insists that CDF WiCD Full was not designed for that purpose.  It's for export only!  As in a conversion of native desktop file formats.

    Which is exactly what the da Vinci group was doing with MSOffice.  The Foundation's immediate interest in CDF WICD was based on the assumption that a similar conversion would be possible between OpenOffice ODF and CDF WICD.

    The Foundation's thinking was that if the da Vinci group could convert MSOffice documents and processes to CDF WICD Full, and, a similar conversion of OpenOffice ODF documents and processes to CDF WICD could be done, then near ALL desktop documents could be converted into a highly interoperable web platform ready format.

    Web platform ready documents from OpenOffice?  What's not to like?  And because the conversion between ODF and CDF WICD Full is so comparatively clean, OpenOffice would in effect, (don't go native file format now) become ahighly integrated rich client end user interface to advancing web platforms.

    The Foundation further reasoned that this conversion of OpenOffice ODF to CDF WICD Full would solve many of the extremely problematic interoperability problems that plague ODF.  Once the documents are in CDF WICD Full, they are cloud ready and portable at a level certain to diminish the effects of desktop applications specific feature sets and implementation models.

    In Massachusetts, the Foundation took
Gary Edwards

An Antic Disposition: Cracks in the Foundation - IBM takes over ODF - 0 views

  • You must admire their tenacity. Gary Edwards and the pseudonymous "Marbux". The mythology of Silicon Valley is filled with stories of two guys and a garage founding great enterprises. And here we have two guys, and through blogs, interviews, and constant attendance at conferences, they have become some of the most-heard voices on ODF. Maybe it is partly due to the power of the name? The "OpenDocument Foundation" sounds so official. Although it has no official role in the ODF standard, this name opens doors. The ODF Alliance , the ODF Fellowship, the OASIS ODF TC, ODF Adoption TC (and many other groups without "ODF" in their name) have done far more to promote and improve ODF, yet the OpenDocument Foundation, Inc. seems to score the panel invites. Not bad for two guys without a garage.
  •  
    An eMail went out today, October 24th, 2007, nominating IBM's Rob "Show me your garage!" Weir to be the new Co Chairman of OASIS ODF TC.  So it's looks like it's true; IBM is moving to take over ODF and OpenOffice.

    Not that that's bad.  In the long run this is perhaps the best thing that ever happened to ODF and OpenOffice.  There is no way IBM's Lotus Notes business plan for ODF-OOo could be any worse than Sun's plan has turned out to be. 

    ~ge~

  •  
    So, South Africa was watching closely the failed effort in Massachusetts to implement ODF?  And now they are determined to make it work? Good thing they left themselves a "pragmatic" out; "there are standards which we are obliged to adopt for pragmatic reasons which do not necessarily fully conform to being open in all respects."

    Massachusetts spent a full year on an ODF implementation Pilot Study only to come to the inescapable conclusion that they couldn't implement ODF without a high fidelity "round trip" capable ODF plug-in for MSOffice.  In May of 2006, Pilot Study in hand, Massachusetts issued their now infamous RFi, "the Request for Information" concerning the feasibility of an ODF plug-in clone of the MS-OOXML Compatibility Pack plug-in for MSOffice applications. At the time there was much gnashing of teeth and grinding of knuckles in the ODf Community, but the facts were clear. The lead dog hauling the ODf legislative mandate sleigh could not make it without ODf interoperability with MSOffice. Meaning, the rip out and replace of MSOffice was no longer an option. For Massachusetts to successfully implement ODf, there had to be a high level of ODf compatibility with existing MS documents, and ODf application interoperability with existing MS applications. Although ODf was not designed to meet these requirements, the challenge could not have been any more clear. Changes in ODf would have to be made. So what happened?

    Over a year later,
Gary Edwards

Can IBM save OpenOffice.org from itself? - 0 views

  • In e-mailed comments, Heintzman said his criticisms about the situation have been made openly. "We think that Open Office has quite a bit of potential and would love to see it move to the independent foundation that was promised in the press release back when Sun originally announced OpenOffice," he said. "We think that there are plenty of existing models of communities, [such as] Apache and Eclipse, that we can look to as models of open governance, copyright aggregation and licensing regimes that would make the code much more relevant to a much larger set of potential contributors and implementers of the technology.... "Obviously, by joining we do believe that the organization is important and has potential," he wrote. "I think that new voices at the table, including IBM's, will help the organization become more efficient and relevant to a greater audience.... Our primary reason for joining was to contribute to the community and leverage the work that the community produces.... I think it is true there are many areas worthy of improvement and I sincerely hope we can work on those.... I hope the story coming out of Barcelona isn't a dysfunctional community story, but rather a [story about a] potentially significant and meaningful community with considerable potential that has lots of room for improvement...."
    • Gary Edwards
       
      What Heintzman is refering to here is the incredibly disastrous "ODF Interoperability WorkShop" held at the OpenOffice Confernece in Barcelona, Spain. The Interop WorkShop was organized by IBM's Rob Weir. Incredilby he still has his job. RW put on display for all to see that special brand of ZERO interop unique to ODF. What's really surprising is that in the aftermath of this tragic display of interop illiteracy, RW initiated a new interoperabilitysub committee at the OASIS ODF Adoption TC! Interop is a technical problem, as was embarassingly demonstrated in Barcelona. Yet here they are setting up the interop solution at a marketing group! Which is a strong indication that rather than taking on the politically difficutl and vendor adverse task of binding an interoperability framework to the ODF specification, they've decided to shout down anyone who might point out that the emperor indeed has no clothes. What a sad day for ODF.
  •  
    Heintzman must be referring to the Rob Weir -OASIS ODF Adoption (cough marketing-lobbying) TC event called the "ODF Interoperability Workshop". This was a day long event demonstrating for all the world to see that there is no such thing as ODF interoperability. The exchange of documents between OpenOffice 2.0, KOffice and Lotus Symphony is pathetic. The results of the day long event were so discouraging that Rob Weir took to threatening developers who attended in his efforts to keep a lid on it. I think this is called damage control :). From what i hear, it was a very long day for Rob. but that's no excuse for his threatening anyone who might publicly talk about these horrific interop problems. The public expects these problems to be fixed. But how can they be fixed if the issues can't be discussed publicly?
  •  
    Lotus Symphony is based on the OpenOffice 1.1.4 code base that IBM ripped off back when OpenOffice was under dual license - SSSL and LGPL.
Jesper Lund Stocholm

Alex Brown on the ODF Zero Interop problem: The discussion to limit the use of Foreign ... - 0 views

  • So I think users need to understand, very clearly, that an ODF document/app of *either* conformance class has an EXTREMELY WEAK CLAIM TO INTEROPERABILITY. The "pure ODF conformance" sticker would be at best valueless and at worst positively misleading. So what I'd like to see is some real effort from the TC going into resolving this problem ...
    • Jesper Lund Stocholm
       
      The sad thing is that with the agreement between JTC1 and OASIS regarding ODF, it seems that SC34 has been completely cut out of the loop in terms of "fixing ODF", as you put it. I cannot see how SC34 will be able to play any part in this - besides rubber-stamping ODF 1.2 when it comes our way.
  •  
    So I think users need to understand, very clearly, that an ODF document/app of *either* conformance class has an EXTREMELY WEAK CLAIM TO INTEROPERABILITY. The "pure ODF conformance" sticker would be at best valueless and at worst positively misleading. So what I'd like to see is some real effort from the TC going into resolving this problem ... Alex Brown What Alex fails to mention is that the "foreign elements and alien attributes" components in the ODF Section 1.5 "Compliance and Conformance" clause was originally put there in early 2003 to provide a compatibility layer for MSOffice binary documents. Without this clause, it would be impossible to convert the billions of legacy MSOffice binary documents to ODF without breaking the fidelity. Now th OASIS ODF TC wants to limit the use of the compatiblity clause. An action that would seriously cripple Microsoft's efforts to implement ODF in MSOffice 14. No surprises here. It was only a matter of time until IBM and Sun ganged up on the newest TC member, Microsoft.
  •  
    So I think users need to understand, very clearly, that an ODF document/app of *either* conformance class has an EXTREMELY WEAK CLAIM TO INTEROPERABILITY. The "pure ODF conformance" sticker would be at best valueless and at worst positively misleading. So what I'd like to see is some real effort from the TC going into resolving this problem ... Alex Brown What Alex fails to mention is that the "foreign elements and alien attributes" components in the ODF Section 1.5 "Compliance and Conformance" clause was originally put there in early 2003 to provide a compatibility layer for MSOffice binary documents. Without this clause, it would be impossible to convert the billions of legacy MSOffice binary documents to ODF without breaking the fidelity. Now th OASIS ODF TC wants to limit the use of the compatiblity clause. An action that would seriously cripple Microsoft's efforts to implement ODF in MSOffice 14. No surprises here. It was only a matter of time until IBM and Sun ganged up on the newest TC member, Microsoft.
Paul Merrell

OpenOffice.org business manager John McCresh on ODF support in MS Office - 0 views

  • There was a certain inevitability that Microsoft would be forced to bow to market pressures and announce its acceptance of ODF. However, Microsoft’s traditional approach to standards has been characterised as Embrace, Extend, Extinguish - i.e. attempt to claim ownership and take control of a standard through abuse of its near monopoly position. Proponents of ODF need to defend against this by setting up independent testing for software conformance with the standard. The testing needs to be accessible not just to the Suns and IBMs of this world - but also the KOffices. While proponents of ODF are celebrating that a victory has been won, it is more likely that the real battle is only just beginning.
    • Paul Merrell
       
      One might reasonably wonder how one would go about building further tools to test for conformance with a standard that has almost no mandatory conformance requirements other than validation against the schema after all foreign elements and attributes (application-specific extensions) are removed. The validation tool specified pre-existed ODF. Methinks that the world verges on learning that ODF is a standard in name only and that ODF interoperability is a complete and utter myth no more accurate than the corresponding myth of OOXML interoperability that was thoroughly debunked long before OOXML became an international standard.
  •  
    There was a certain inevitability that Microsoft would be forced to bow to market pressures and announce its acceptance of ODF. However, Microsoft's traditional approach to standards has been characterised as Embrace, Extend, Extinguish - i.e. attempt to claim ownership and take control of a standard through abuse of its near monopoly position. Proponents of ODF need to defend against this by setting up independent testing for software conformance with the standard. The testing needs to be accessible not just to the Suns and IBMs of this world - but also the KOffices. While proponents of ODF are celebrating that a victory has been won, it is more likely that the real battle is only just beginning.
Gary Edwards

State's move to open document formats still not a mass migration - 0 views

  • June 08, 2007 (Computerworld) -- 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.
  •  
    Use of ODF remains minimal on government PCs in Massachusetts
    Eric Lai ....... June 8, 2007

    Bummer!  Do you think IBM is silent on this because they are busy cutting sweetheart deals with MS?  Are they going to hang Sun on this?  I'm sure that by next week IBM will have to respond to ODEF.   This just keeps getting better.  So in both Texas and California they wonder if it's even possible to implement ODF solutions.  No one wants to get into that hole with Massachusetts.

    ~ge~


Gary Edwards

Suggested ODF1.2 items - 0 views

  • Subject: Suggested ODF1.2 items From: "Florian Reuter" <freuter@novell.com> To: <office@lists.oasis-open.org> 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

Singing Kumbaya -- gary_edwards's comment on "Linux leaders plot counterattack on Micro... - 0 views

  • have you noticed that IBM is softening their position on "harmonization"? There are a number of events to consider that might have influenced this change in tone:
  •  
    More in that same "LiNUX Leaders plot counter attack on Microsoft" thread at ZDNet.  This time the issue is what has caused IBM to sing a differnet tune?  The tune known as "harmoniation".
Gary Edwards

ODF tied to OpenOffice? Say it isn't so! -- gary.edwards's comment on "IBM Symphony fal... - 0 views

  •  
    Good discussion on IBM's recent release of OpenOffice as Lotus Symphony. OpenOffice Community Marketing Lead, John McCreesh, steps into it though with an errant quote. Sadly, i have to take him to task.
Gary Edwards

Bluster keeps the ODF / OOXML debate afloat | BetaNews - 0 views

  • the Group went one step further, if only that far: It advised clients to steer clear of the whole format superiority debate, in order to avoid getting dragged down into what could be called "Office politics.""ODF is insufficient for complex real-world enterprise requirements, and it is indirectly controlled by Sun Microsystems, despite also being an ISO standard," the Burton Group's Guy Creese and Peter O'Kelly wrote. "It's possible that IBM, Novell, and other vendors may be able to put ODF on a more customer-oriented trajectory in the future and more completely integrate it with the W3C content model, but for now ODF should be seen as more of an anti-Microsoft political statement than an objective technology selection."
Gary Edwards

Microsoft: IBM masterminded OOXML failure - ZDNet UK - 0 views

  • "IBM have asked governments to have an open-source, exclusive purchasing policy," Tsilas said. "Our competitors have targeted this one product — mandating one document format over others to harm Microsoft's profit stream." "It's a new way to compete," Tsilas said. "They are using government intervention as a way to compete. It's competing through regulation, because you couldn't compete technically."
Gary Edwards

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?]
    • Gary Edwards
       
      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?
Gary Edwards

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…
Gary Edwards

Microsoft Watch - Business Applications - Convergence=Integration - 0 views

  • Microsoft significantly increases cross-integration of features with the company's other software. Microsoft acquired most of the products making up its Dynamics product line, and what a motley crew. New products and versions bring the Dynamics line more into the Microsoft family, in part by convergence—or increased integration with the company's other software.
  •  
    Thanks for the insightful commentary Joe. I see things a bit differently. Maybe my tin foil hat is wearing a bit tight these days, but i see MSOffice XML (MOOXML and the MOOXML binary InfoSet) as a very important aspect of how Microsoft integrates and leverages their desktop office monopoly power into server side and device systems. It is the combination of MOOXML and .NET that creates the integration mesh between desktop, server systems, and devices. Imagine every application or service participating in either a loosely coupled or carefully crafted information processing chain, being fluent in MOOXML, and able to process internal data structures and processing instructions unique to .NET. Enterprise systems and services from ORACLE, IBM and SAP will not have this same integration fluency. The design of ISO MOOXML is such that it would be impossible for <b>non Microsoft server and device systems</b> to match the quality and depth of integration with the 500 million desktops running MSOffice bound business processes. Given that MOOXML will probably succeed at getting ISO/IEC approval, removing the last "legal" barrier for this MOOXML Stack, were looking at a massive migration of MSOffice bound workgroup - workflow business processes to a new lockin point; The Exchange/SharePoint Hub. With the real estate industry, this migration to to E/S hosted applications only took six months to completely replace years of desktop productivity shrinkware dominance. The leap in productivity was spectacular. The downside of this migration is that the real estate industry is now tied into Microsoft at the critically important business process level. A binding that will perhaps last through the next fifteen years.
Gary Edwards

ODF, PDF, The Antic Waste Land, and Monica's Blue Dress - Rob Weir - 0 views

  • An intriguing idea is whether we can have it both ways. Suppose you are in an ODF editor and you have a "Save for archiving..." option that would save your ODF document as normal, but also generate a PDF version of it and store it in the zip archive along with ODF's XML streams. Then digitally sign the archive along with a time stamp to make it tamper-proof. You would need to define some additional access conventions, but you could end up with a single document that could be loaded in an ODF editor (in read-only mode) to allow examination of the details of spreadsheet formulas, etc., as well as loaded in a PDF reader to show exactly how it was formated.
  •  
    Intriguing?  Rob Weir knows full well that the Foundation proposed this exact same feature set as part of the da Vinci Plug-in design for Massachusetts, July of 2006!!!!!!!!!

    The Complete Feature list of the da Vinci plug-in for MSOffice that was proposed and signed off on by CIO Louis Gutierrez in early August of 2006 was well known by IBM's representatives who were working hand in hand with us at the time: Rob Weir, Don Harbison and Doug Heintzman. 

    Louis Gutierrez had asked IBM and Oracle to create a "benefactors Group" to overcome the challenge that Massachusetts ITD did not have a budget.  IBM and Oracle selected Google, Sun, Novell, Intel, and Nokia as key benefactors.  The group was provided with the complete feature set and roadmap for da Vinci development. 

    The da Vinci roadmap was the schedule announced by Louis Gutierrez in his mid year report, August 17th, 2006.

    The da Vinci plug-in feature set, in order of priority, consisted of:
    ODF iX Approval at OASISPlug-in for MS WORDAccessibility Interface for all ODF documents in MS WordPDF - ODF iX Digital Signature containerPlug-in for MS ExcelInteroperability Wizard for OpenOfficePlug-in for PowerPointXForms InterfaceThe roadmap we provided Louis and the "benefactors" was sceduled out with deliverables, test periods, and cost per deliverable.  The buy-in per "benefactor" was set at $350,000, and i
‹ Previous 21 - 40 of 84 Next › Last »
Showing 20 items per page