Skip to main content

Home/ Groups/ Document Wars
Gary Edwards

Vista Aiding Linux Desktop, Strategist Says - 0 views

  • Crawford said a corporate desktop needs to be focused on the business user, compliant with company standards, interoperable, secure, and able to be shipped with an enterprise kernel and managed remotely, and to have standard applications installed. "The Linux desktop can do all of that. It can be interoperable with earlier versions of the operating system, is generally interoperable with Windows, can ship with an enterprise kernel and can be remotely managed by existing management solutions," he said.
Gary Edwards

Between a rock and a hard place: ODF & CIO's - Where's the Love? - 0 views

  • So I'm disappointed. And not just on behalf of open documents, but on behalf of the CIOs of this country, who are now caught between a rock and a hard place, without a paddle to defend themselves with if they won't to do anything new, innovative and necessary, if a major vendor's ox might be gored in consequence. After the impressive lobbying assault mounted over the past six months against open document format legislation, I expect you won't be hearing of many state IT departments taking the baton back from their legislators.    And who can blame them? If they tried, it wouldn't be likely to be anything as harmless as an open document format that would bite them in the butt.
  •  
    Andy Updegrove weighs in on the wave of ODF legislative failures first decribed by Eric Lai and Gregg Keizer compiled the grim data in a story they posted at ComputerWorld last week titled  Microsoft trounces pro-ODF forces in state battles over open document formats.


    Andy believes that it is the failure of state legislators to do their job that accounts for these failures.  He provides three reasons for this being a a failure of legislative duty.  The most interesting of which is claim that legislators should be protecting CIO's from the ravages of aggressve vendors. 


    The sad truth is that state CIO's are not going to put their careers on the line for a file format after what happened in Massachusetts.


    Andy puts it this way, "
      

    And second, in a situation like this, it is a cop out for legislatures to claim that they should defer to their IT departments to make decisions on open formats.  You don't have to have that good a memory to recall why these bills were introduced in the first place: not because state IT departments aren't a good place to make such decisions, but because successive State CIOs in Massachusetts had been so roughly handled in trying to make these very decisions that no state CIO in his or her right mind was likely to volunteer to be the next sacrificial victim.
    As both Peter Quinn and Louis Gutierrez both found out, trying to make responsible standards-related decisions whe
Gary Edwards

Novell CEO confirms that Microsoft is a reality | The Register - 0 views

  • It was a performance that saw Hovsepian call Microsoft a reality the community must work with
  • Skimming over the details of Microsoft's support, Hovespian said such deals are critical if Linux is going to give customers running mixed environments what they need, by delivering interoperability in the data center and on the desktop.
    • Gary Edwards
       
      No Kidding! The marketplace knows this full well. It's the FOSS and ODF Communities that are clueless. Interoperability with Microsoft bound documents, applications and processes must be dealt with before Linux and ODF systems can begin to penetrate the growing Microsoft Stack. This is why the ODF iX proposals, five of which were submitted to the ODF TC for discussion in the past year alone, were critical to the success of ODF in California, Massachusetts, Denmark, Belgium and the EU-IDABC. Too bad the ODF TC doesn't understand this importance and the need to accomodate the marketplace.
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~
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

» Web inventor Tim Berners-Lee Unplugged: Semantic Web better than APIs for d... - 0 views

  • the general idea is for there to be a layer of data on the Internet that he calls the “data bus” and the way the data bus works is not too different from how we’ve heard Microsoft’s WinFS filesystem described where connectivity between related data items is organic rather than synthesized. For example, whereas today, a mashup developer may have to call upon two APIs to show where a specific Starbucks is on a map, the Semantic Web approach might involve little more than a simple query of that data bus using a query technology called SparQL.
  •  
    Great explanation of the Semantic Web, RDF, SparQL versus big vendor Web API's
Gary Edwards

Sun Sets Application Specific Limits on ODF Metadata - 0 views

  • Fine; I hope that you also will specify the citation metadata then. Using unspecified metadata for *relevant* parts of the document in OOo can be the starting signal to kill ODF. I'm not sure if citation data is a "relevant part of the document" but without further investigation I assume it to be that.
  •  
    The battle to break ODF away from being limited to only those features supported by Sun's OpenOffice/StarOffice continues.  This eMail thread sets the stage for the upcoming presentation of the metadata proposal to the ODF mainline TC.

    SEction 1.4.3 of the metadata proposal is a list of existign ODF elements that developers can apply RDF to.  And the reason given fo rwhy the list is so constrained?  Svante Schubert, co-editor and Sun employee has claimed on more than a few occassions that the reason for limiting the lis tis that Sun will only support RDF on those particular ODF elements in OpenOffice/StarOffice.  Therefore, everyone is similarly limited!

    I kid you not. 
    ~ge~

Gary Edwards

Real World Government Open Source - Bill Welty and Government OSS Technology - 0 views

  • Welty gave a rapid-fire look at the realities of open source in government. "The doors have been blown open in California," he said. "In 2004 when Governor Schwarzenegger signed the California Performance Review a section called State Operations #10 specifically authorized the use of open source." Operations #10 says: "Departments should take an inventory of software purchases and software renewals in the Fiscal Year 2004-2005 and implement open source alternatives where feasible."
  •  
    If there is an Open Source hero in government, it's Bill Welty.  This article pulished in Government Technology covers the GOSCON 2006 conference where Bill spoke to the realities of open source software in government.  Bill will also be speaking at the October 2007 GOSCON Conference in Portland Oregon.  He doesn't pull his punches :)  Even with Microsoft, IBM, Novell, and Sun sitting across the table.
Gary Edwards

What will it be for ODF? Continuation of limited interop? Or a transition to Universa... - 0 views

    • Gary Edwards
       
      Preserving metadata! Preserving application specific information. Preserving "unknown" information inside of a document
  • Unless we add conformance requirements for the preservation of metadata and processing instructions, the less featureful apps will never&nbsp; be able to round-trip documents with the more featureful apps. Our language should require that. Personally, I believe that the software-as-an-end-point client-side office suites are dinosaurs at the end of their era. They are being finished off by a thousand cuts as users spend less and less time using them and more and more time using other apps, such as web apps. ODF either develops methods for interoperability among all apps or it will die along with the office suites. E.g., Microsoft knows this and is busily migrating its Office development budget across the Sharepoint/Exchange server hubs to the network. Meanwhile, this TC fiddles with preserving the 1995 software-as-an-endpoint vision.
  •  
    Marbux is clearly at the top of his game here as he hammers the interoperability issue.
Gary Edwards

Sun Inner Circle: Sun and Microsoft: Interoperability Now - 0 views

  •  
    Sun waxes eloquent on the $2 Billion 2004 interoperability deal with Microsoft. Desktop and Server interop on steroids!
Gary Edwards

Sun Supports OOXML as an ISO Standard? - 0 views

  • Sun Microsystems Inc., largely considered an avowed opponent of Open XML because of its own development and support for the competing, ODF-based StarOffice suite, found itself in the unexpected position of stating its support for ratifying Open XML -- albeit after some changes in the proposal are made.
  •  
    Quote: Sun Microsystems Inc., largely considered an avowed opponent of Open XML because of its own development and support for the competing, ODF-based StarOffice suite, found itself in the unexpected position of stating its support for ratifying Open XML -- albeit after some changes in the proposal are made. "We wish to make it completely clear that we support DIS 29500 becoming an ISO Standard and are in complete agreement with its stated purposes of enabling interoperability among different implementations and providing interoperable access to the legacy of Microsoft Office documents," Jon Bosak, a Sun representative to V1, wrote in an e-mail to other committee members over the weekend. "Sun voted No on Approval because it is our expert finding, based on the analysis so far accomplished in V1, that DIS 29500 as presently written is technically incapable of achieving those goals, not because we disagree with the goals or are opposed to an ISO Standard that would enable them." Sun "found itself in the unexpected position of stating its support for ratifying OOXML"?  What???? This is the official position of Sun?

    For the near five years that i have been a member of the OASIS ODF TC, Sun has opposed
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

We've Been Had! - 0 views

  • There is nothing open about MOOXML, and it should have never made it to consideration as an international standard. But one has to ask, what is up with Sun? The John Bosak comment is just as much cause for concern as the fact that the nations of the world would dare consider OOXML as an international standard. All i can say is that we've been had. Sun and Microsoft have worked us royally, and only now, at the last moment, does the fog of confusion clear and we can see it all.
  •  
    Yeah.  I said this!  And i still think ODF has what it takes to become a universal file format.  But only if the "interoperability enhancment" proposals are made part of the specification.  You can't talk your way to universal interop.   It has to go into the spec!

    OBTW, for you idiots who think i support OOXML as a standard?  You're idiots.  I support the quest for a universal file format that is totally application, platform and vendor independent.  The requirements, demands and criticisms we make of OOXML should be applied to every file format up for universal file format consideration.  Including ODF.  Including XHTML+ (XHTML, CSS3, RDF).  Including the EU IDABC "ODEF".

    The one area where i differ from most universal interoperability seekers is that i fully believe the big vendors have left open a loop hole we can exploit.  The plugin architecture is fully able to convert a big vendors application to produce our beloved but elusive universal file format. 

    This is important because the big vendors control "interoperability" by contolling the big vendor standards consortia, and, the major applications.  It's a double edged sword.

    The ubiquitous plugin architecture enables universal interop seekers to exploit the applications any way we want.  What's missing is a truly open "universal" standards process that is outside the reach of big vendors. 

    Personally i like the recent GPL3 process as a model on which to base emerging universal standards work.  Somehow the big vendors must be neutralized.  Otherwise, we;ll never see the universal inteop the world so desires.

    idiots,
    ~ge~

Gary Edwards

The Document Foundation, LibreOffice and OOXML - The Document Foundation Wiki - 1 views

  • Why does LibreOffice offer to read, edit and save documents in OOXML? Just like OpenOffice.org, LibreOffice lets its users handle documents in the format used by Microsoft Office 2007 and 2010. It is important to understand that these formats, also called OOXML are in fact somewhat different from the ISO standard bearing the same name; in fact it is unclear whether anyone is able to implement the ISO standard. To avoid confusion, we will refer to the Microsoft formats produced by Microsoft Office as Microsoft Open XML (MOX) hereafter. To enable data interchange, LibreOffice and OpenOffice.org before it, has traditionally engaged with the reality of a world filled with data in many, less than ideal formats. Our users are used to exchanging data bi-directionally between many proprietary formats, and their Free Software equivalents. Indeed there are few choices for a non-dominant player to deliberately shun inter-operating, and remain relevant.
  • Don't you feel as if you are betraying Free and Open Source Software, as well as Open Standards such as ODF? No. And if we felt that way, we would take immediate action to remove the full stack. What we are offering our users is convenience; if we didn't offer these features we would not be serving users and we would get daily messages requesting the support of the new Microsoft Office formats. Besides, the same reasoning applies to the old Microsoft Office formats we support; and while it was thought for a while it was possible to prevent people from using these formats or even buying Microsoft Office, it turned out that it was not possible. We do believe, however, that by offering a full-featured and innovative office suite that exists among a rich and diverse ODF ecosystem, ODF shall prevail in the end.
Gary Edwards

GROKLAW - 0 views

Alex Brown

OOXML is defective by design: Microsoft's latest aggression on ODF, codenamed "cast lead" - 0 views

  • nazis
    • Alex Brown
       
      "Nazis", "genocide", "white phosphorous" -- and all about a file format implementation ...
« First ‹ Previous 381 - 400 Next › Last »
Showing 20 items per page