Skip to main content

Home/ OpenDocument/ Group items tagged open standards

Rss Feed Group items tagged

Gary Edwards

Microsoft's OOXML limps through ISO meeting - ZDNet UK - 0 views

  • Gary Edwards, former president of the Open Document Foundation, an industry group that promoted ODF but then rejected both approaches and closed itself down in November 2007, said: "Ecma and Oasis are vendor consortia where the rules governing standards specification work favour vendor innovation over the open and transparent interoperability consumers, governments and FLOSS efforts demand... Shutting that door on Ecma OOXML is proving very difficult exactly because the primary and fundamental rule of ISO interoperability requirements has been breached."
Gary Edwards

XML 2007 Conference - Boston MA, Dec 3-5 - 0 views

  • XML 2007 Conference XML 2007 is the world’s largest and longest-running conference devoted to XML and other open data and document technologies. Our theme for 2007 is XML in Practice, focusing on the lessons learned from implementing XML in production-grade systems. When? Monday 3 December–Wednesday 5 December 2007 Where? Marriott Copley Place, Boston, MA  
  •  
    Check out the schedule.  There are some really interesting topics to be covered.  Microsof tand Sun are also going to have a session on application level interoperability and why multiple standards are better than one.
Graham Perrin

Orcmid's Lair: Microsoft ODF Interoperability Workshop - 0 views

  • 2008-08
  • Microsoft's first built-in support
  • approach to adding Open Document Format support directly into Office 2007
  • ...20 more annotations...
  • the balancing act that Office-ODF interoperability requires
  • absence of non-disclosure agreements
  • I saw no down side
  • all ODF TC members who desired to come had a place
  • interaction with the ODF community
  • balancing of different interests: standards groups, corporations, institutions, government agencies, regulatory bodies, and general users
  • five guiding principles that govern ODF support in Word, Excel, and PowerPoint
  • priorities that apply in making trade-offs
  • a serious, open conversation is beginning
  • Balancing of competing considerations is not trivial
  • current OpenOffice.org implementations fail to check whether a formula conforms to its own extension
  • the central feature of typical document processing software is the internal, in-memory representation of the software's document model
  • features may be lost on output
  • features may be lost on input
  • rely on features that succeed with the internal representation
  • degraded or lost entirely in the chosen external representation
  • losing some of them when saving
  • Florian Reuter argued an interesting gracefully-failing extension technique that, on reflection, I believe could avoid breaking changes against earlier ODF specifications of namespaces, their elements and their attributes too
    • Graham Perrin
       
      I'd like to learn more about this.
  • an application being quite friendly with its own ODF but not with that of other significant implementations
  • discussions did not arrive at conclusions
  •  
    I read this more than a year after the event but still, it's interesting.
Gary Edwards

OOXML in Norway: The haywire process | Geir Isene : Straight talk on IT - 0 views

  • I had read the essay by Jon Bosak (SUN Microsystems) on why SUN voted as it did in the US. He lays out a very different strategy. His view is that the battle is lost to completely reject OOXML as an ISO standard. ISO can only reject it with comments, and that is equivalent to giving Microsoft a todo-list on how to fix the draft so as to get it approved. Microsoft has sufficient manpower to easily tackle that. Most of us had missed what Mr. Bosak saw: OOXML promises interoperability with earlier closed binary formats (the Word Doc, older Excel file formats etc.). But it doesn’t deliver. How on earth could someone be able to convert old binary files to the new format without having the specification of the old formats and a mapping to OOXML. If you are to translate some text from Chinese to English, it doesn’t much help to only know English.
    • Gary Edwards
       
      A "Yes with comments" is a yes for the ISO approval of MS-OOMXL. If ISO approves MS-OOXML, it won't matter what Bosak's "comments" strategy is. Microsoft and the Vista Stack will be off to the races. The full disclosure of the MS binary document secret blueprint won't matter much at that point.
  • “Ah c’mon Bosak, you are chickening out, we must stop this dead in the track”
    • Gary Edwards
       
      There you go Geir!

      Sun and Bosak have held the door open for MS-OOXML since 2002, when Sun blocked an effort to write the ODF Charter to include as a priority, "compatibility with existing file formats". This of course would include the billions of legacy MS binary documents.

      The thing is that those who work in the conversion-translation field will tell you that it is currently impossible to pipe converted legacy binary documents and OOXMl docs for that matter into ODF. Just as Microsoft claims, ODF in it's current state is insufficient and unable to handle the rich feature set of the MSOffice developers platform.

      The problem could of course be easily fixed by the inclusion in ODF of five structural generics. In the past year, there have been no less than five iX "interoperability enhancement" proposals submitted to the OASIS ODF TC for discussion and consideration. As uber universal interop expert Florian Reuter points out in his blog, these iX proposals did not fare so well.

      What Florian doesn't point out is that it was Sun who opposed any and all efforts to improve compatibility with existing Microsoft binary and OOXML documents. Just as they have done for nearly five years now.

      Sort of puts the Sun-Bosak support for ISO approval of MS-OOXML in a different light. ~ge~
  •  
    see the sticky notes on this one
Gary Edwards

IBM undeterred by setbacks to ODF adoption | InfoWorld | News | 2007-06-08 | By China M... - 0 views

  • You might think the steady defeat of bills in several U.S. states to mandate the use of free interoperable file formats might dampen the spirits of IBM, one of the prime supporters of ODF (OpenDocument Format). Far from it, said IBM's Bob Sutor, who sees the recent news as par for the course in the evolution of any open standard.
  •  
    Thus spoke the little Dutch Boy, his finger in the dike, his confidence large.  Meanwhile, people with half a brain were heading for the high ground.  California, Texas, Massachusetts and the EU IDABC come to mind.  Hello bob!  Can you say ODEF?
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

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

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

What's Up Doc? Report on ODF / OOXML / W3C Document Wars |Collaboration and Content St... - 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.
Gary Edwards

IT set to 'take their heads out of the sand' and embrace Web 2.0 - 0 views

  • IT managers and CIOs in large companies who have actively resisted embracing Web 2.0 technologies like wikis, RSS, blogs and social networks will likely begin adding them to their priority lists in 2008, according to a report released Friday by Forrester Research Inc.
Gary Edwards

OOXML and ISO: The Process Challenge - A Predictable Path | Matusow's Blog - 0 views

  • Where can we expect challenges?
  •  
    Scott B responds to Matusow blathering with a list of ISO changes that should be made given the OOXML fiasco, but won't.
Gary Edwards

The Stockholm Syndrom at ISO | ODF Editor Says ODF Loses If OOXML Does | Slashdot - 0 views

  • ISO is bound to the business of "interoperability", and has very strict guidelines for interoperability requirements, that are themselves tied to international trade agreements and legal conventions. In this context, it is beyond surprising that ISO allows the "OASIS PAS" and "Ecma Fast Track" channels to remain open, with specification work remaining under the controlling influence of the vendors.IMHO, the change in Patrick's position is entirely due to the realization that it is impossible to map between OOXML and ODF. I don't know this for sure, but when i read the German Standards Group (DIN) report on harmonization, authorized by the EU-IDABC and provided to ISO, i couldn't help but wonder how Patrick would react. The report definitively ends his OOXML ODF mapping dream.
  •  
    Response to Yoon Kit's comments that Patrick Durusau is caught between a rock and hard place. His ISO JTC-1 group is now overwhelmed with MS OOXML supporters!
Gary Edwards

Open Malaysia: Geneva, Day Five - 0 views

  • We eventually found out that if any changes affected current implementations it would certainly be rejected. This seriously compromised any elegant solutions, and it forced us to be mindful of the "existing corpus of documents" in the wild. I personally don't believe that that should be our problem, but there was a large and vocal voting bloc which would oppose any changes to the spec which would 'break' Ecma 376. This was why appeasing Ecma had to happen. Even though they rushed their Ecma International Standard, and Microsoft took the risk in shipping Microsoft Office 2007 last year, we now have to bear the burden of having to support its limitations. This also means that future maintenance changes would get harder and harder.
Gary Edwards

International Digital Publishing Forum (formerly Open eBook Forum) - Flock - 0 views

  • The International Digital Publishing Forum (IDPF) is the trade and standards association for the digital publishing industry.
Gary Edwards

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

  • Plan B: The "NO ViSTA" Mandates:  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).  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.  Now the mighty monopolist can taste victory, with fast track approval of MOOX certain, and ISO/IEC in the bag.  Incredibly the company that escaped a Court ordered death sentence by purchasing what amounts to a presidential pardon.  They even avoided the stink of their own lobbyist and henchman Jack Abramoff, and his motley crew of Ralph Reed and Grover Nyquist operatives.  Now they are well on their way towards purchasing an International Standard.  So much for Plan A.  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

FAA May Ditch Microsoft's Windows Vista And Office For Google And Linux Combo - Technol... - 0 views

  • Bowen's compatibility concerns, combined with the potential cost of upgrading the FAA's 45,000 workers to Microsoft's next-generation desktop environment, could make the moratorium permanent. "We're considering the cost to deploy [Windows Vista] in our organization. But when you consider the incompatibilities, and the fact that we haven't seen much in the way of documented business value, we felt that we needed to do a lot more study," said Bowen. Because of Google Apps' sudden entry into the desktop productivity market
  •  
    The FAA issues their "NO ViSTA" mandate, hinting that it might be permanent if they can come up with MSOffice alternatives.  They are looking at Google Apps!

    Okay, so plan B does have legs.  The recent failure of ISO/IEC to stand up to the recidivist reprobate from Redmond is having repercussions.  Who would have ever thought ISO would fold so quickly without ceremony?  One day there are 20 out of 30 JTCS1 national bodies (NB's) objecting to Micrsoft's proprietary XML proposal, the MOOX Ecma 376 specfication, and the next ISO is approving without comment the placing of MOOX into the ISO fast track where approval is near certain.  With fast track, the technical objections and contradictions are assumed to be the provence of Ecma, and not the JTCS1 experts group.

    Apparently the USA Federal Government divisions had a plan B contingency for just such a case.  And why not?  Microsoft was able to purchase a presidential pardon for their illegal anti trust violations.  If they can do that, what's to stop them from purchasing an International Standard?  Piece of cake!

    But Google Apps?  And i say that as one who uses Google Docs every day.

    The problem of migrating away from MSOffice and MOOX to ODF or some other "open" XML portable file format is that there are two barriers one must cross.

    The first barrier is that of converting the billions of MS binary docuemnts into ODF XML. 

    The second is that of replacing the MSOffice bound business processes that drive critical day to day business operabions. 

    Google Apps is fine for documents that benefit from collaborative computing activities.  But there is no way one can migrate MSOffice bound business processes - the workgroup-worflow documents to Google Apps.  For one thing Google Apps is unable to facillitate important issues like XForms.  Nor can they round trip an ODF document with the needed fidelity a
Gary Edwards

Any objections? For Open XML standard, yes (still) - 0 views

  •  
    This brief summary of the ODF <>OOXML controversy covers the recent response by Ecma to the ISO/IEC JTC 1 National Body members who filed objections to placing Ecma 376 on an ISO fast track approval process.    This article has the actual ECMA Response PDF!  A document that is well worth reading and studying.

    Essentially Ecma has told ISO to take a hike! 

    In responding to the different objections, Ecma chose to explain their position without once offering to fix or remedy he many problems and issues that so concern the 20 different NB's filing objections.  Not once!  No compromise whatsoever, only the preachy attitude that the objecting NB's simply don't understand the wonders of Ecma 376 or what a ISO "contraditction" means.

    Take a Hike!  Up Yours!  Screw you and the horse you rode in on too! 

    Pick your metaphor, it's all the same. 

Gary Edwards

Getting the (Share)Point About Document Formats [LWN.net] - Gly Moody - 0 views

shared by Gary Edwards on 27 Nov 07 - Cached
  • The OpenDocument Foundation was formed in 2005, with the mission "to provide a conduit for funding and support for individual contributors to participate in ODF development" at the standards body OASIS. So, at a time when backing for the ODF format seems to be gaining in strength around the world, eyebrows were naturally raised when Sam Hiser, the Foundation's Vice President and Director of Business Affairs, wrote on October 16 that it was no longer supporting ODF:
Gary Edwards

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

  •  
    This quote from Chalres Schultz is ridiculous. Because Novell is not allowed to commit code to OpenOffice, they must maintain a separate code base of extensions and improvements. With each build of OpenOffice, Novell must reintegrate their changes into the code base, making for a managerial nightmare. When Novell does have improvements that Sun wants though, there is no end to the hoops of fire the Sun developers will jump through to get it. The Field Enhancement routine written by Novell's Florian Router is one of those improvements that Sun had to have. Sun even went so far as to arguing for changes in the way ODF implements fields to accomodate the Novell improvements! It's important to note however that Sun did not support the ODF Field Enhancements UNTIL Novell agreed to donate Florian's code to OpenOffice!!!!!! Proving conclusively what i have been arguing for years: Sun does not allow for any changes to ODF unless and until those changes can be implemented by OpenOffice. The ODF Field Enhancements needed by Florian's fix to OpenOffice were originally proposed on July 12th, 2006, when Florian was the CTO of the OpenDocument Foundation. These changes to the way ODF implements fields were needed by the da Vinci plug-in as part of our efforts to save ODF in Massachusetts. so here we have a rather direct example of Sun refusing improvements to ODF when needed by another application (da Vinci), but supporting those exact same changes when it is OpenOffice that can be improved!!! The arguments that the OpenOffice.org Community isn't open also apply to the OASIS ODF TC work!!!!!!
  •  
    Good catch by Eric!
    This link is to the infamous Sun statement of support for MS OOXML issued by Jon Bosak when ISO DIS 2900 was voted on by the US delegation to ISO.
    The statement is important because it directly references the core issue: MS OOXML was written for MSOffice and the billions of binary docuemnts bound to that application suite. ODF on the other hand was written to OpenOffice.
    Because ODF was not designed for the conversion of those billions of MSOffice documents, conversion is next to impossible. The implementation of ODF in MSOffice is next to impossible. The loss of information, especially the presentation-layout information, is so severe as to be intolerable in the real world.
    This leaves the real world, where MSOffice dominates over 550 million desktops, unable to implement ODF. In light of this real world problem, Sun's Bosak urges support for MS OOXML as an ISO standard!!!
    So we have this situation at OASIS ODF where Sun is in control of both ODF and OpenOffice, refusing in all cases to compromise the linkage or accomodate the much needed interoperability enhancemnts seeking to improve the conversion of billions of documents to ODF. And publicly supporting MS OOXML as the only pragmatic alternative to the situation Sun is responsible for!
Gary Edwards

ODF Split Shakes Up Document Battle | Redmond Developer News Michael Desmond - 0 views

  • The ongoing file format battle between proponents of the OpenDocument Format (ODF) and Microsoft's Office Open XML (OOXML) took a surprising turn lthis week, when a key ODF proponent announced that it intended to abandon the ISO-approved specification. The move by the OpenDocument Foundation comes less than two months after Microsoft lost a key ISO vote to approve OOXML as a standard.
  •  
    Thi sis Michael Desmons's second article on the file format wars.
Gary Edwards

ODF calls time on da Vinci coding | The Register Lucy Sherriff - 0 views

  • The Open Document Foundation (ODF) has quietly ended all work on its da Vinci project after failing to secure approval from the Organisation for the Advancement of Structured Information Standards (OASIS). The da Vinci project was to develop a class of plug-ins that would allow users "to create and edit CDF (compound document format) files in their existing Microsoft Office installations". That is to say, a user could save a .odt file within Word as easily as if it were a .doc format. document.write('\x3Cscript src="http://ad.uk.doubleclick.net/adj/reg.software.4159/applications;'+RegExCats+GetVCs()+'pid='+RegId+';'+RegKW+'maid='+maid+';test='+test+';pf='+RegPF+';dcove=d;sz=336x280;tile=3;ord=' + rand + '?" type="text/javascript">\x3C\/script>'); However, the organisation now says all work has ceased because OASIS has not granted approval of its generic extensions. Without this approval, ODF says: "We can not effectively convert existing Microsoft documents, applications and processes to ODF. The loss of fidelity and feature - business process specific information is too great."
« First ‹ Previous 101 - 120 of 124 Next ›
Showing 20 items per page