Skip to main content

Home/ Document Wars/ Group items tagged archives

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

Brian Jones: Open XML Formats : Mapping documents in the binary format (.doc; .xls; .pp... - 0 views

blogs.msdn.com/...pt-to-the-open-xml-format.aspx

burtongroup cdf css ibm iso microsoft odf okelly ooxml opendocument openxml sun w3c xhtml

shared by Gary Edwards on 20 Jan 08 - Cached
  • The second issue we had feedback on was an interest in the mapping from the binary formats into the Open XML formats. The thought here was that the most effective way to help people with this was to create an open source translation project to allow binary documents (.doc; .xls; .ppt) to be translated into Open XML. So we proposed the creation of a new open source project that would map a document written using the legacy binary formats to the Open XML formats. TC45 liked this suggestion, and here was the TC45 response to the national body comments: We believe that Interoperability between applications conforming to DIS 29500 is established at the Office Open XML-to- Office Open XML file construct level only.
    • Gary Edwards
      Gary Edwards on 20 Jan 08
       
      And here i was betting that the blueprints to the secret binaries would be released the weekend before the September 2nd, 2007 ISO vote on OOXML! Looks like Microsoft saved the move for when they really had to use it; jus tweeks before the February ISO Ballot Resolution Meetings set to resolve the Sept 2nd issues. The truth is that years of reverse engineering have depleted the value of keeping the binary blueprints secret. It's true that interoperability with MSOffice in the past was near entirely dependent on understanding the secret binaries. Today however, with the rapid emergence of the Exchange/SharePoint juggernaught, interop with MSOffice is no longer the core issue. Now we have to compete with E/S, and it is the E/S interfaces, protocols and document API's and dependencies tha tmust be reverse engineered. The E/S juggernaught is now surging to 70% or more of the market. These near monopoly levels of market penetration is game changing. One must reverse engineer or license the .NET libraries to crack the interop problem. And this time it's not just MSOffice. Today one must crack into the MS Stack whose core is tha tof MSOffice <> E/S. So why not release the secret binary blueprints? If that's the cost of getting the application, platform and vendor specific OOXML through ISO, then it's a small price to pay for your own international standard.
  • Gary Edwards on 20 Jan 08
     
    Well well well. We knew that IBM had access to the secret binary blueprints back in 2006. Now we know that Sun ALSO had access!
    And why is this important? In June of 2006, Massachusetts CIO Louis Gutierrez asked the OpenDocument Foundation's da Vinci Group to work with IBM on developing the da Vinci ODF plug-in clone of Microsoft's OOXML Compatibility Pack plug-in. When we met with IBM they were insistent that the only way OASIS ODF could establish sufficient compatibility with MSOffice and the billions of binary documents would be to have the secret blueprints open.
    Even after we explained to IBM that da Vinci uses the same internal conversion process that the OOXML plug-in used to convert binaries, IBM continued to insist that opening up the secret binaries was a primary objective of the OASIS ODF community.
    For sure this was important to IBM and Sun, but the secret binaries were of no use to us. da Vinci didn't need them. What da Vinci needed instead was a subset of ODF designed for the conversion of those billions of binary documents! A need opposed by Sun.
    Sun of course would spend the next year developing their own ODF plug-in for MSOffice. But here's the thing: it turns out that Sun had complete access to the secret binary blueprints dating back to 2006!!!!!!
    So even though IBM and Sun have had access to the blueprints since 2006, they have been unable to provide effective conversions to ODF!
    This validates a point the da Vinci group has been trying to make since June of 2006: the problem of perfecting a high fidelity conversion between the billions of binaries and ODF has nothing to do with access to the secret binary blueprints. The real issue is that ODF was NOT designed for the conversion of those binary documents.
    It is true that one could eXtend ODF to achieve the needed compatibility. But one has to be very careful before taking this ro
Gary Edwards

Microsoft's OOXML: The No vote | Computerworld - 0 views

www.computerworld.com.au/...d;1414093266;fp;4194304;fpid;1

cdf ecma iso odf ooxml

shared by Gary Edwards on 20 Jan 08 - Cached
  • The Cyberspace Law and Policy Centre at the University of New South Wales recently hosted a symposium to discuss issues surrounding the proposed Microsoft OOXML document format standard. In attendance at a technical session were representatives from Microsoft, IBM, Google, the Open Source Industry Australia, Standards Australia, the National Archives of Australia, and the International Organisation for Standardisation.
Gary Edwards

Interoperability Enhancement Proposal: Suggested ODF1.2 items - 0 views

lists.oasis-open.org/...msg00048.html

foundation interop ix odf odfix opendocument subset

shared by Gary Edwards on 20 Jan 08 - Cached
  • 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
  • Gary Edwards on 20 Jan 08
     
    This is the fifth of the six major iX - interoperability enhancement proposals submitted to the OASIS ODF TC - SC between July 2006 and February of 2007. This particular iX proposal lead to the "List Enhancement Proposal" donnybrook that consumed the OASIS ODF TC for the next six months, ending with the OpenDocument Foundation being booted out of OASIS in May of 2007. The six iX proposals were all different approaches to the same basic problem: ODF was not desinged to be interoperable with MSOffice documents, applications or bound processes. The proposals come out of the OpenDocument' Foundation's efforts to save ODF in Massachusetts. ODF iX repressents a subset of ODF designed to grealty improve compatibility with MS binary and XML formats. With the ODF iX subset, the da Vinci plug-in would be able to convert the billions of MSOffice binary and xml documents with a very high level of fidelity, and do so within the bounds of "round trip" business processes. The most basic iX approach was to add five generic elements to the existing ODF specification. The five generic elements would cover lists, tables, fields, sections, and page dynamics (breaks). It is a well known fact that these five areas of incompatibility between OpenOffice ODF and MSOffice binaries represent 95% of all conversion fidelity problems. MSOffice has one way of implementing lists, and, OpenOffice has another. These application specific implementation models are irreconcilably different. It's also true that the applicaiton specific implementation models are directly reflected in each file format. So applications implementing ODF must also implement the OpenOffice model for lists, fields, tables, sections and page dynamics-page positioning if they are to have any meaningful measure of exchange fidelity. Perhaps the best of the iX approaches was that based on the innovative use of metadata to describe presentation-layout attributes.
Gary Edwards

OOXML/ODF: Just One Battlefield in a Much Bigger War | Linux Today - 2 views

www.linuxtoday.com/news_story.php3

cloud-computing grid-computing odf ooxml openxml

shared by Gary Edwards on 07 Mar 08 - Cached
  • If the OOXML format in its current form cannot get made into a true ISO standard, it could lock Microsoft out of any future plays in what could be the biggest IT revolution to date. Here are the pieces of the puzzle that fit together for me:
  • "Amazon SimpleDB is a web service for running queries on structured data in real time."
  • "Structured data." And what's a good way to contain such data? In well-built structured data file format of course. Like, for instance, the Open Document Format (ODF). And who has a vested interest in ODF? IBM certainly does. And so does Sun. And these two companies, along with Google, Microsoft, and I'm sure many others, realize that if cloud computing does indeed take off, then it will be the file format that makes the whole thing work. Which is why Microsoft feels it must get their format standardized. Even with tactics that ironically have started to attract the attention of the EU again. How else can they get a piece of the cloud pie?
    • Gary Edwards
      Gary Edwards on 07 Mar 08
       
      Partly right. The MS plan is actually much bigger than Brian Profitt suggests. The MSOffice 2007 SDK is fille dwith new API's, the most interesting of which are the ones connecting MSOffice to XAML and the Windows Presentation Foundation layer. The killer component though is the OOXML <> fixed/flow translator component with related API's. fixed/flow is a new web format that is 100% proprietary. It's at the heart of the Microsoft cloud, enabling developers to easily transition between OOXML and IE browsers able to serve fixed/flow pages to devices, desktops and just about any kind re purposing publication - content management system imaginable. If ISO approves OOXML, then they've standardized MSOffice as a legitamate Web editor - enterprise publication, content management, archive management front end. Instead of producing W3C compliant (X)HTML - CSS web pages though, the MSOffice Web editor will produce the proprietary fixed/flow format via the OOXML translation component we can now see in the SDK. What we don't see in the MSOffice SDK is the use of W3C technologies such as (X)HTML, CSS, SVG, XForms, SMiL, XSL, XSL-FO. Instead of Mozilla XUL or Adobe Flex, we find XAML and Silverlight. IMHO, Microsoft is making their run for the Web. Key to this run is ISO approval of OOXML. Once that happens, there will be no need for MS product compliance with W3C standards. The break will be complete. The We forever split into the Windows Web, and the Firefox - Apache Tomcat Web. And never the twain shall meet.
Gary Edwards

Wizard of ODF: Interoperability barriers and the List Proposal Vote Deadline on Wednesday - 0 views

www.oasis-open.org/...msg00039.html

harmonization interop interoperability odf ooxml opendocment openxml

shared by Gary Edwards on 07 Mar 08 - Cached
  • this TC does not have the final word on what goes into the ODF 1.2 spec. There is still the OASIS vote, the JTC-1 vote, and the ISO final ballot, with a few other stops along the way. There is also the market's response to what this TC does. Given that no one on this TC has objected to my considerable efforts to raise public concerns with Microsoft's ISO submission and some on this TC have lambasted Microsoft for creating interoperability barriers, why should this TC's members consider themselves exempt from warnings that they have just fallen into precisely the kind of behavior we routinely criticize when it's Microsoft that creates the interoperability barriers. Especially when it's the end users who will pay the price of the non-interoperability?
Gary Edwards

Whither OpenDocument Format? Say Hello To a Truly Universal File Format - CDF! - 0 views

www.technewsworld.com/...60938.html

cdf corel odf ooxml opendocument w3c xhtml

shared by Gary Edwards on 28 Dec 07 - Cached
  • Filtering vs. Standards Corel's policy is to focus on what its customers want rather than get overly involved in any one document format, Larock explained. WordPerfect uses Corel's proprietary document format but makes that code available. "We have filters built in to translate into more than 65 different file formats, including OOXML and ODF," he said. "That list included some legacy WordPerfect, AMIPro, PDF, multiple MS Word earlier formats and numerous graphic file formats." Maintaining filters for legacy document formats is important. People have lots of older files in archive that they still want to access, said Larock. Up for Grabs The evolution of text on the Internet along with the use of Web 2.0 applications is starting to have an impact. It is becoming a contest between a desktop presence and a Web-based format, according to Larock. He compared the situation to the transition from analog to digital formats in the telephone industry.
    • Gary Edwards
      Gary Edwards on 28 Dec 07
       
      Another big endorsement for the W3C's CDF as the universal file format!
Gary Edwards

Wizard of ODF: Proposal to amend TC charter, re interoperability with non-conformant ap - 0 views

www.oasis-open.org/...msg00022.html

harmonization interop interoperability oasis odf ooxml opendocument

shared by Gary Edwards on 07 Mar 08 - Cached
  • 7. it must provide all feasible functionality required to suppport full fidelity conversions from and to existing office document binary file formats.
Gary Edwards

Wizard of ODF: The Foundation on Interop and the List Proposal Vote Deadline - 0 views

www.oasis-open.org/...msg00040.html

anti-trust ecis foundation odf ooxml opendocument openxml

shared by Gary Edwards on 09 Feb 08 - Cached
  • Oh, my. Both IBM and Sun voted for the proposal that broke the Foundation's plugin that was going to add full-fidelity native ODF file support to Microsoft Office. So it's sounding to me like at least two of the TC members who voted for the Sun/KOffice proposal didn't check in with the ECIS lawyer before they broke interoperability with Microsoft Office. Do you think Microsoft won't use this evidence in the DG Competition antitrust proceeding, Michael? Let's see, you guys are prosecuting Microsoft for not supporting ODF in Microsoft Office while you block Microsoft Office from supporting ODF. Yeah, I think DG Competition is going to hear about this one from Microsoft. They'll probably hear about what you said about compatibility being a trade off too. Oh, yeah. Microsoft's lawyers are going to love this. Look at the ECIS public statement about interoperability's importance.
Gary Edwards

OOXML-ODF: The Harmonization Hope Chest | Orcmid's Lair - 0 views

orcmid.com/...f-harmonization-hope-chest.asp

shared by Gary Edwards on 09 Feb 08 - Cached
  • 4. The Reality in the Punchbowl Meanwhile, Sam Hiser offers a different impression of the DIN effort [4]: "The ODF-to-OOXML harmonization effort being hosted by the German standards group, DIN, is Europe's best effort to resolve our Mexican Standoff between Microsoft, Sun and IBM. Even though harmonization is laughably complex and will not work unless the applications are harmonized too, the best and brightest of Germany are left to hope for success."&nbsp; [emphasis mine: dh] Although the mission of the German effort is translation (Übersetzung), not harmonization, I find there is a very important point that is not made often enough:&nbsp; People write, read, and edit office documents with little, if any, understanding of the particular format that makes them persistent in digital form.&nbsp; The XML-based open formats do not change that.&nbsp;&nbsp; People adapt to the software/device they are using by trial and error.&nbsp; We train ourselves to obtain the visible results that we want.&nbsp; Different people obtain superficially similar results by quite different means.&nbsp;&nbsp; Even when someone has gone to the trouble to create style sheets, forms, macros, templates and other format-impacting aids, it is very loosey-goosey in practice.&nbsp; And it still does not require paying attention to the file format.&nbsp;&nbsp;
Gary Edwards

Wizard of ODF: OASIS invited to join Microsoft in the DIN technical report - harmoniz... - 0 views

www.oasis-open.org/...msg00040.html

din eu harmonization iso oasis odf ooxml xml

shared by Gary Edwards on 29 Jan 08 - Cached
  • 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
      Gary Edwards on 29 Jan 08
       
      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 Director of Strategy comes clean on OpenXML - IBM *WILL* support OpenXML in its L... - 0 views

notes2self.net/...lotus-and-portal-products.aspx

cdf heintzman ibm odf ooxml openxml

shared by Gary Edwards on 25 Jan 08 - Cached
  • 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

[office] The infamous list-override list enhancement proposal - 0 views

www.oasis-open.org/...msg00056.html

application-specific florian-reuter foundation list-enhancement michael-brauer oasis-odf odf opendocument openoffice

shared by Gary Edwards on 25 Jan 08 - Cached
  • Well, I think the problem we face is that there are different interpretations of the 1.1 specification regarding the numbering of numbered paragraphs that have different list styles assigned. We therefore cannot say that the one or the other proposal is backward-compatible to the ODF 1.1 specification regarding the number or the style. We can only say whether it is backward-compatible to a certain _interpretation_ of the ODF 1.1 specification regarding the number or the style.
Gary Edwards

office by thread - 0 views

lists.oasis-open.org/...threads.html

shared by Gary Edwards on 23 Jan 08 - Cached
  • [Fwd: clarification: OpenDocument and SVG] From Lars Oppermann &lt;Lars.Oppermann@Sun.COM&gt; on 2 Feb 2005 10:31:44 -0000 Re: [office] [Fwd: clarification: OpenDocument and SVG] From Michael Brauer &lt;Michael.Brauer@Sun.COM&gt; on 2 Feb 2005 12:16:44 -0000 Message not available. Message not available. Message not available. Re: [office] [Fwd: clarification: OpenDocument and SVG] From Michael Brauer &lt;Michael.Brauer@Sun.COM&gt; on 3 Feb 2005 10:14:18 -0000 Message not available. Re: [office] [Fwd: clarification: OpenDocument and SVG] From Michael Brauer &lt;Michael.Brauer@Sun.COM&gt; on 3 Feb 2005 14:01:24 -0000 Propsal regarding the use of the SVG namespace in OpenDocument From Michael Brauer &lt;Michael.Brauer@Sun.COM&gt; on 3 Feb 2005 13:49:10 -0000 Use of SVG namespace From Patrick Durusau &lt;Patrick.Durusau@sbl-site.org&gt; on 7 Feb 2005 13:34:56 -0000
    • Gary Edwards
      Gary Edwards on 23 Jan 08
       
      Hello Jesper .... this is what you are looking for. The very contentious exchange of messages between the W3C SVG Workgroup, and the OASIS ODF TC. The issue at stake is the W3C namespace highjacking by the OASIS ODF TC.
Gary Edwards

Re: [office-comment] Public Comment - 0 views

lists.oasis-open.org/...msg00016.html

shared by Gary Edwards on 23 Jan 08 - Cached
  • Regarding section 1.5 itself: The Open Office TC decided to use the term MAY rather than MUST (or will) at the mentioned location, because it wanted to ensure that the OpenDocument specification can be used by as many implementations as possible. This means that the format should also be usable by applications that only support a very small subset of the specification, as long as the information that these applications store can be represented using the OpenDocument format. A requirement that all foreign elements and attributes must be preserved actually would mean that some applications may not use the format, although the format itself would be suitable. Therefor, we leave it up to the implementations, which elements and attributes of the specification they support, and whether they preserve foreign element and attributes. Some more information about this can be found in appendix D of the specification.
    • Gary Edwards
      Gary Edwards on 23 Jan 08
       
      This OASIS ODF discussion is about the Compliance - conformance clause of the ODF specification: Section 1.5. A developer has complained that use of MAY instead of MUST in the wording of the clause would enable conforming applications to destroy foreign elements and alien attribute markup at will. This of course would result in ZERO Interoeprability!!!!! The foreign elments and alien attributes were included for the purposes of improved ODF compatibility with the billions of MSOffice binary documents that would need to be converted to ODF. Sadly, the section 1.5 loop hole falls short of the compatibility goal, but that only begins to scratch the surface of the ODF problems. OpenOffice only supports foreign elements and alien attributes for text spans, and paragraphs!!!!!! All other such markup is unrecognized and therefore "destroyed" by OpenOffice. ZERO interop. No roundtripping with MSOffice desktops. Lossy conversion with jagged fidelity. Guaranteed.
Gary Edwards

What's So Bad About Microsoft? - 0 views

www.kmfms.com/whatsbad.html

backwards-compatibility iso microsoft odf ooxml xml

shared by Gary Edwards on 12 Dec 07 - Cached
  • 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.
  • Gary Edwards on 12 Dec 07
     
    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.



Gary Edwards

Open Stack: Game Time for OpenDocument - 0 views

openstack.blogspot.com/...ame-time-for-opendocument.html

ecma eooxml iso microsoft mooxml oasis odf

shared by Gary Edwards on 12 Dec 07 - Cached
  • 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. >
  • Gary Edwards on 12 Dec 07
     
    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

Brian Jones: Open XML Formats : Open XML support in older versions of Office - 0 views

blogs.msdn.com/...-older-versions-of-office.aspx

iso microsoft msoffice oasis odf ooxml opendocument openxml xml

shared by Gary Edwards on 12 Dec 07 - Cached
  • The big thing I'm waiting for is other applications like OpenOffice to support custom defined schemas. This would mean that rather than simply sharing wordprocessing or spreadsheet information, we can share actual customer information. For example you could take health care data, or invoice data, or RFP data from one of the applications and move it over to the other without losing that semantic meaning. It would be like that demo many of you have seen me do where I take data from a table in Excel and move it over to Word where it's formatted more like a catalog.
  • Gary Edwards on 12 Dec 07
     
    The big thing I'm waiting for is other applications like OpenOffice to support custom defined schemas. This would mean that rather than simply sharing wordprocessing or spreadsheet information, we can share actual customer information. For example you c
  • Gary Edwards on 12 Dec 07
     
    The big thing I'm waiting for is other applications like OpenOffice to support custom defined schemas. This would mean that rather than simply sharing wordprocessing or spreadsheet information, we can share actual customer information. For example you c
  • Gary Edwards on 12 Dec 07
     
    The big thing I'm waiting for is other applications like OpenOffice to support custom defined schemas. This would mean that rather than simply sharing wordprocessing or spreadsheet information, we can share actual customer information. For example you c
Gary Edwards

Matusow's Blog : Open XML Translator - 0 views

blogs.msdn.com/...658184.aspx

imported:del.icio.us interop interoperability msxml odf

shared by Gary Edwards on 12 Dec 07 - Cached
  • Gary Edwards on 12 Dec 07
     
    Microsoft's ODf Translator Project and interoperability position
  • Gary Edwards on 12 Dec 07
     
    Microsoft's ODf Translator Project and interoperability position
  • Gary Edwards on 12 Dec 07
     
    Microsoft's ODf Translator Project and interoperability position
Gary Edwards

Open Sources | InfoWorld | The Future of Lock-in | May 17, 2006 08:56 AM | By Matt Asay - 0 views

weblog.infoworld.com/...the_future_of_l.html

eooxml exchange imported:del.icio.us notes odf sharepoint

shared by Gary Edwards on 12 Dec 07 - Cached
  • Gary Edwards on 12 Dec 07
     
    Whoa, Matt Asay knocks one out of the ballpark! Finally a Web 2.0 provider who understands the importance of the Exchange/SharePoint Hub, and the long term lockin of critical day to day business processes that Microsoft has brewing. One thing he doesn't
  • Gary Edwards on 12 Dec 07
     
    Whoa, Matt Asay knocks one out of the ballpark! Finally a Web 2.0 provider who understands the importance of the Exchange/SharePoint Hub, and the long term lockin of critical day to day business processes that Microsoft has brewing. One thing he doesn't
  • Gary Edwards on 12 Dec 07
     
    Whoa, Matt Asay knocks one out of the ballpark! Finally a Web 2.0 provider who understands the importance of the Exchange/SharePoint Hub, and the long term lockin of critical day to day business processes that Microsoft has brewing. One thing he doesn't
Paul Merrell

Gray Matter : Compatibility Pack for Open XML passes 100 million downloads - 0 views

blogs.technet.com/...ses-100-million-downloads.aspx

office 2007 compatibility pack odf-ooxml stats

shared by Paul Merrell on 24 Jun 09 - Cached
  • The Compatibility Pack, software that allows you to open, edit and save Open XML format documents in Office XP and 2003 has now been downloaded over 100 million times.
  • Paul Merrell on 24 Jun 09
     
    Also includes stats in table form indicating that according to Google Search OOXML documents now outnumber ODF documents on the Web, for word processor documents, spreadsheet documents, and presentation documents.
« First ‹ Previous 41 - 60 of 76 Next ›
Showing 20▼ items per page