Skip to main content

Home/ Document Wars/ Group items tagged open

Rss Feed Group items tagged

Paul Merrell

EUROPA - Press Releases - Antitrust: Commission opens proceedings against MathWorks - 1 views

  • Brussels, 1 March 2012 - The European Commission has opened a formal investigation to assess whether The MathWorks Inc., a U.S.-based software company, has distorted competition in the market for the design of commercial control systems by preventing competitors from achieving interoperability with its products. The Commission will investigate whether by allegedly refusing to provide a competitor with end-user licences and interoperability information, the company has breached EU antitrust rules that prohibit the abuse of a dominant position. The opening of proceedings means that the Commission will examine the case as a matter of priority. It does not prejudge the outcome of the investigation. The investigation follows a complaint alleging that MathWorks had refused to provide a competitor with end-user software licences and accompanying interoperability information for its flagship products "Simulink" and "MATLAB", thereby preventing it from lawfully reverse-engineering in order to achieve interoperability with these two products.
  • As in the Microsoft case (see IP/04/382 and MEMO/04/70 and MEMO/07/359), the issue of software interoperability is central to this investigation. The Commission's investigation will focus on whether MathWorks' behaviour has prevented competitors from achieving interoperability with its widely used products and thereby hindered competition in breach of Article 102 TFEU. In this context, it is recalled that the European Directive 2009/24/EC on the legal protection of computer programmes also aims to foster interoperability by allowing for reverse-engineering for interoperability purposes provided that the software at issue was lawfully acquired.
  • Background MathWorks' "Simulink" and "MATLAB" software products are widely used for designing and simulating control systems. Control systems are deployed in many innovative industries such as in cruise control or anti-lock braking systems (ABS) for cars. Article 102 TFEU prohibits the abuse of a dominant position which may affect trade and prevent or restrict competition. The implementation of this provision is defined in the Antitrust Regulation (Council Regulation No 1/2003) which can be applied by the Commission and by the national competition authorities of EU Member States. The Commission has informed MathWorks and the Member States' competition authorities that it has formally opened proceedings in this case.
  •  
    Commission v. MIcrosoft Redux.
Gary Edwards

Government - Focus for an OS Desktop - 0 views

  •  
    Government, to include Federal, State and Local, should be the prime focus for increasing open source desktop market share by vendors such as Novell, Redhat and Ubuntu. Why, because government is required to procure all product and services through an open, transparent and competitive process. As of today, few if any government organizations have complied with this requirement when it comes to purchases of desktop operating systems or productivity tools. In fact, until just recently there have not been competitive alternatives, but now there are.
  •  
    Government, to include Federal, State and Local, should be the prime focus for increasing open source desktop market share by vendors such as Novell, Redhat and Ubuntu. Why, because government is required to procure all product and services through an open, transparent and competitive process. As of today, few if any government organizations have complied with this requirement when it comes to purchases of desktop operating systems or productivity tools. In fact, until just recently there have not been competitive alternatives, but now there are.
Gary Edwards

Odf - Converters & the ODF Zero Interop problem - 0 views

  • The ODF-Converter translates OpenXML documents (.DOCX) to Open Document Format (.Open Document Format) (and conversely) for Open XML processing applications. You will find below the list of unsupported features which may be due to standard compatibility issues, or to the translator itself (see rendering issues as discussed in the blog)...
  •  
    Explosive compatibility - interoperability study concerning ODF and MOOXL!  This has Florian's signature written all over it, and it goes right to the heart of the matter.

    David A. Wheeler submitted a comment to the OASIS ODF TC outlining his concerns with this publication.  He suggests that a few minor changes to ODF could greatly improve compatibility - interop issues.  He also figures out that OpenOffice - ODF has more features than MSOffice - MOOXML.  Wha the doesn't ge is that it is these new and innovative features that continue to increase the difficulties of implementing ODF in real world business process workgroups!

    David also ignores the fact that the TC jus tvoted down the Novell "LIt Enhancement Proposal" which was specifically designed to address the compatibility - interop issues outlined in this odf-converter blog!  Given a choice, the ODF TC members chose the new and innovative features of the interop breaking Sun-KOffice "List Enhancement Proposal".   

    The List Enhancement Proposal discussion was so contentious and focused on personal destruction as to represent a total break down of the ODF concensus process.  There is no way that either the Foundation or Novell will ever contribute another compatibility - interop enhancement proposal given the personal assault and determined oppostion of Sun to compatibility - interoperability initiatives.

    The hard lesson the Foundation learned is that if you oppose Sun, you'll get booted out of OASIS!

    The lesson Novell learned is that they are better off working through Ecma 376 to resolve these issues that the public demands be addressed.

    Notice the last line in David's comment, "In any case, the MUCH, MUCH longer list of problems with Microsoft XML format isn't our problem." 

    During the contentious List Enhancement Proposal and the compatibility - interop related Metadata RDF/XML discussions, ODF members freque
  •  
    These are the same guys who just voted against the Novell List Enhancement Proposal that did exactly what the odf-converter blog claims needs to be done if the compatibility-interop problems are to be resolved!
Gary Edwards

O(blog N) » California's Open-Document Bill: AB 1668 - 0 views

  • I have an email apparently originating from Microsoft asking people to support their opposition to California A.B. 1668 - Open Document Format, Open Source. by writing to the California Assemblymen involved in this bill. This email has contact information for the Assemblymen involved, and a lot of information about their position regarding ODF.
  •  
    +1 ODF in California.  A good summary of the issues.
Gary Edwards

Microsoft playing three card monte with XML conversion, with Sun as the "outside man" w... - 0 views

  • In a highly informative post to his Open Stack blog Wednesday, Edwards explains how three key features are necessary for organizations to convert to open formats. These are: Conversion Fidelity - the billions of binaries problem Round Trip Fidelity - the MSOffice bound business processes, line of business integrated apps, and assistive technology type add-ons Application Interop - the cross platform, inter application, cross information domain problem
  •  
    Dana Blankenhorn posted this article back in March of 2007.  It was right at the time when the OASIS ODF TC and Metadata XML/RDF SC (Sub Committee) were going at it hammer and tong concerning three very important file format characteristics needed to fulfill a real world interoperability expectation:

    .... Compatibility - file format level interop -
    :::  backwards compatibility / compatibility with existing file formats, including the legacy of billions of binary Microsoft documents

    ....... Interoperability - application level interop-
    ::::::  application interoperability including interop with all Microsoft applications

Gary Edwards

Can't We All Just Get Along? - 0 views

  •  
    Another call for the "convergence" of ODF and MS-OOXML, this time from the government technology magazine, GCN.com.

    IMHO, there is a very steep technical barrier to both the harmonization and/or convergence of ODF and OOXML. The problem is that these file formats are application specific and bound respectively to OpenOffice and MSOffice feature sets and implementation models. The only way to perfect a harmonization or convergence file format effort is to dramatically change the reference applications.

    With over 500 million MSOffice workgroup bound desktops in the world, changing that suite of applications is likely to break business processes with a global disruption factor that is simply unacceptable. OpenOffice on the other hand could better sustain such the needed layout engine changes, but estimates it will take 3-5 years to accomplish this.

    Sun has often stated at the OASIS ODF TC (technical committee) that OpenOffice will not be bound and limited by having to mirror MSOffice features and implementation models. These arguments are often called application innovation rights.

    In the past year alone, there have been no less than five ODF iX "interoperability enhancement" proposals submitted to the OASIS ODF TC members for discussion. The iX proposals are designed to solve the problem of high fidelity "round trip" conversion of MSOffice binary and xml documents with OpenOffice ODF documents.

    Sadly, Sun and the other ODF application vendors fought and thoroughly defeated every aspect of these proposals even though the first three iX proposals were signed off on by Massachusetts ITD, and considered vital to the successful implementation of ODF there. ODF of course proved impossible to implement in Massachusetts. And without the iX interoperability enhancements, it is impossible for ODF plug-ins for MSOffice to perfect the high fidelity "round trip" conversion of existing doc
Gary Edwards

Choose Your Future :: You're in good hands with Microsoft - 0 views

  • With ISO/IEC having standardized Open Document Format (ODF) 1.0 and considering standardizing Ecma Office Open XML (Open XML), there is a lot of public discussion about document formats and whether the world should begin to focus on only one format or continue to see multiple formats developed and used over time. Microsoft believes that users should be able to choose among formats and pick the one that best meets their needs. We also believe in encouraging the continued evolution of computing and data formats. And we support the ratification of Open XML in ISO/IEC. There are several reasons for these views:
  •  
    This the infamous Microsoft letter that many have misconstrued as an announcement of support for OpenDocument.  Only in a Microsoft universe can the statement, "We're not going to attack ODF" be taken as Micrsoft support for ODF.
Gary Edwards

IBM In Denial Over Lotus Notes - Forbes.com - 0 views

  • The marketing folks in IBM's Lotus division are starting to sound like the Black Knight in Monty Python and the Holy Grail, who insists he's winning a fight even as he loses both arms and legs: "'Tis but a scratch," the Black Knight declares after one arm is lopped off. "Just a flesh wound," he says after losing the other. "I'm invincible!" The same goes for IBM's (nyse: IBM - news - people ) Lotus, which keeps declaring victory even as Microsoft (nasdaq: MSFT - news - people ) carves it up.
  •  
    Want to know the real reason why IBM and Microsoft are going at it hammer and tong over document formats?  Here it is.  Lotus Notes is getting clobbered by the Exchange/SharePoint juggernaut. 

    The article is old, but the point is well taken.  Today the Exchange/SharePoint juggernaut i sover 65% marketshare.  IBM is struggling to protect the Lotus Stack against an impossible foe.

    The thing is, Microsoft E/S will ALWAYS have better integration with the MSOffice - Outlook desktop monopoly base (550 M and counting).  Most of this "integration" is due to the high fidelity exchange of documents in Microsoft's proprietary XML mode known as MS-OOXML.   Forget the charade that MS-OOXML is an open standard called Ecma 376.  MSOffice and infamous XML Compatibility Pack Plug-in do not implement Ecma 376.  The Pack implements MS-OOXML.

    One key differnece between MS-OOXML and Ecma 376 us that MS-OOXML is infused with the Smart Tags components.  These are for metadata, data binding, data extraction, workflow, intelligent routing and on demand re purposing of docuemnt components.  In effect, MS-OOXML :: Smart Tags combines with proprietary .NET Libraries, XAML and soon enough Silverlight to replace the entire span of W3C Open Internet Technologies. 

    Can you say "HTML"?

    Okay, so why does this matter to IBM and the future of Lotus Notes?

    The end game of the document format wars is that of a stack model that converges desktop, server, devices and web information systems.  The MS Stack uses MS-OOXML as the primary transport of accelerated content/data/multi media streams running across the MS Stack of desktop, server, device and web application systems.  It's the one point of extreme interoperability.

    It's also a barrier that no non MS applicatio or service can penetrate or interoperate with except on terms Microsoft dictates. 
Gary Edwards

Government Open Source Conference to Feature Open Document Debate - Government Technolo... - 0 views

  • The Executive Panel on Open Document Formats, moderated by Andy Stein, director of information technology at the city of Newport News, Va., will focus on how the user community can get involved in this issue, have influence over its outcome and knowledge for implementations. Panelists are expected to address the practical differences between competing standards OOXML, ODF and CDF to determine which one(s) truly provide a single file format that is open, universally interoperable and application- and platform-independent. About half of the session will be set aside for audience questions, providing an opportunity for GOSCON attendees to gain direct access to the debate.
  •  
    The press coverage on GOSCON is outstanding.  Kudos to Debra Bryant and Andy Stein for stoking the fire here. 
Gary Edwards

Ballmer threatens Linux and open source with patents again - Flock - 0 views

  • To handle IP conflicts between open source and proprietary software organizations, Ballmer wants to see what he calls "an intellectual property interoperability framework between the two worlds." He did not give any specifics on what such a framework would look like.
  •  
    You've got to be kidding me!  Balmer wants to establish "an intellectual property interoperability framework" that open source communities would honor?  I think that's called "open standards" implemented according to the ISO, W3C and International Trade Agreement Interoperability conformance requirements.

    Why doesn't Microsoft start with an honest effort to comply with where the rest of the world has long been?

    ~ge~

Gary Edwards

Home - Berkman Center for Internet & Society - 0 views

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

ODF 1.2? You're dreaming! Microsoft starts rolling out more OOXML translators | Mary... - 0 views

  • Over the next three months, Microsoft will be releasing new and updated translators designed to aid  customers who want interoperability between Microsoft’s Office Open XML (OOXML) and other document formats, including Open Document Format (ODF). On December 4, Microsoft began rolling out three new translators that it plans to make available this month: A 1.1 update of its translator for Word; an Open XML spreadsheet translator and a presentation translator. Additionally, in February 2008, Microsoft will deliver the final version of its translator designed to provide interoperability between the Chinese-government backed Uniform Office Format (UOF) file format and OOXML. Microsoft announced the creation of the SourceForge-hosted Open Translation Project in July 2006. At that time, the Softies said the translator-focused initiatve was started “in response to government requests for interoperability with ODF because they work with constituent groups that use that format.” Vijay Rajagopalan, a Microsoft Principal Architect, provided the update on the OOXML-ODF translation work during the XML 2007 conference on Decmeber 4. During the XML 2007 interoperability panel — sponsored by Microsoft and of which Rajagopalan was a part — the ongoing battles that have raged for the past couple of years between Microsoft and the backers of ODF were a mere sidenote.
Gary Edwards

Whoops?! IBM products support Microsoft's Open XML doc format! Lotushpere - 0 views

  • Nobody has invested more to defeat Microsoft Corp.'s Open XML document format than IBM Corp. So why is IBM supporting Open XML in a handful of its products? According to technical documentation on IBM's own Web sites, Big Blue already supports Open XML, the native file format of Microsoft Office 2007, in at least four of its software. However, Microsoft Office users interested in testing or switching to Lotus Symphony, IBM's upcoming challenger to Office, may be disheartened by signs that IBM won't budge from its stance that it will only support documents created in Office 2003 and prior versions.
Gary Edwards

The Case for Harmonization (that IBM will vote against anyway) « A Frantic Op... - 0 views

  • The Case for Harmonization (that IBM will vote against anyway) In my recent post, I discussed the case for harmonization, mainly due to trying to portray a more kindly, conciliatory face in the “standards krieg” that I was enjoying so much. I have been forced to take a different tack, in light of being hung out to dry by my more business-focused IBM comrades and the work that the enemy has done in sprucing up the spec. However, as my closest friends know, for me, there are no half-victories, so you can rest assured that I will not settle for this weak “harmonization” compromise. I set out my (and IBM’s) stall some time ago on this, and as those on the Open Document Foundation know, any attempt at harmonization shall be met with swift and final retribution.  They were ejected from the odf-coven just days after their impudence. I have baited my trap, inviting this “harmonization” in my lair (the OASIS ODF TC) where I can bog them down in a morass of incompetence, bickering and politicking, so no new standard is ever ratified.  I have already been practicing for this, as you can see, by the ODF 1.1 and 1.2 specs.
Gary Edwards

Brian Jones: Open XML Formats : OASIS ODF committee considering joining DIN to help wit... - 0 views

  • OASIS ODF committee considering joining DIN to help with translation and interop This is very cool. It looks like the OASIS committee is looking at coming on board to help out with the work going on in DIN to help understand the translation between Open XML and ODF: http://www.oasis-open.org/archives/office/200801/msg0004
Gary Edwards

Microsoft Hit By U.S. DOT Ban On Windows Vista, Explorer 7, and Office 2007 - Technolog... - 0 views

  • »  E-Mail »  Print »  Discuss »  Write To Editor late last year -- can be resolved. "We have more confidence in Microsoft than we would have 10 years ago," says Schmidt. "But it always makes sense to look at the security implications, the value back to the customer, and those kind of issues." The DOT's ban on Vista, Internet Explorer 7, and Office 2007 applies to 15,000 computer users at DOT proper who are currently running the Windows XP Professional operating system. The memo indicates that a similar ban is in effect at the Federal Aviation Administration, which has 45,000 desktop users. Compatibility with existing applications appears to be the Transportation Department's major concern. According to a separate memo, a number of key software applications and utilities in use in various branches of the department aren't Vista compatible. Among them are Aspen 2.8.1, ISS 2.11, ProVu 3.1.1, and Capri 6.5, according to a memo issued by staffers at the DOT's Federal Motor Carrier Safety Administration. Any prolonged ban on new Microsoft technologies by the federal government could have a significant impact on the software maker's bottom line, as Microsoft sells millions of dollars in software to the feds annually. http://as.cmpnet.com/event.ng/Type=count&ClientType=2&AdID=125682&FlightID=75634&TargetID=2625&SiteID=222&AffiliateID=283&EntityDefResetFlag=0&Segments=1411,3108,3448,11291,12119&Targets=2625,2878,7904,8579&Values=34,46,51,63,77,87,91,102,140,222,227,283,442,646,656,1184,1255,1311,1405,1431,1716,1767,1785,1798,1925,1945,1970,2217,2299,2310,2326,2352,2678,2727,2767,2862,2942,3140,3347,3632,3636,3638,3890,3904,4080,448
    • Gary Edwards
       
      DOT chief technology officer Tim Schmidt DOT's CIO Daniel Mintz Federal Department of Transportation
  •  
    Whoa, those government desktops add up quickly.  This Vista ban will immediately effect over 50,000 desktops, with tens of thousands more possibly impacted by the IE 7.0 ban.  The MS Exchange/SharePoint Hub juggernaut is based on IE 7.0, which is not available for Windows 2000 - MSOffice 2000 desktops.

    Lack of Vista Stack compatibility with non Microsoft application is given as the reason for the ban.  But notice the "alternatives" to Vista mentioned; Novel SuSE and Apple Mac.  What kind of interop - compatibility do they offer?  My guess is ZERO!

    The reality is that the DOT is trapped.  My advice would be stay exactly where they are, keeping the current MSOffice desktop installs running.  Then, install the Foundation's daVinci ODF plugin for MSOffice. 

    This will insure that Windows OS and  MSOffice bound business processes can continue to function without disruption.  Win32 APi based applications like those mentioned in the article can continue.  Critical day to day business processes, workgroup and workflow related activities can continue without disruption or costly re engineering demanded by a cross platform port.

    What daVinci doe sdo is move the iron triangle that binds Windows-MSOffice applications to business processes and documents, to an ODF footing.  Once on a ODF footing, the government can push forward with the same kind of workgroup - workflow - intelligent docuemnt - collaborative computing advnaces that the Vista Stack was designed to deliver.  Only this push will involve the highly competitive "the customer is sovereign" environment of ODF ready desktop, server, device and Web 2.0 systems.  End of Redmond lock-in.  End of the costly iron triangle and the force march upgrade treadmill that so enriches Microsoft.

    So what's not to like?  We can do this.
    ~ge~

    http://docs.google.com/View?docID=dghfk5w9_20d2x6rf&revi
Gary Edwards

Three Stages of XML Migration: The OpenDocument Challenge - 0 views

  • "Open document formats: I get it! But how do I get there? Discuss."
  •  
    Eventually i suspect the truth will come out concerning ODF and the events in Massachusetts.  Migration is difficult and our friends in Redmond are not about to lend a hand.  The problem is the starting point, the MSOffice desktop productivity environment.  A starting point owned and controlled entirely by Microsoft.  The challenge is to get from the overwhelming dominance of proprietary Microsoft binary documents and into an open XML universal file format that any application, running on any platform can interactively read, render and write to.

    Microsoft has decided to keep secret the blueprint to these billions of binary documents, reserving exclusively for themselves the right to convert then to XML.  Of course, the only version of XML Microsoft will convert them to is the wholly owned and controlled OOXML file format. 

    Microsoft refuses to cooperate in any way with the conversion of these legacy binary documents to the only truly open XML universal file format, OASIS OpenDocument.  Which leaves the world with a near insolvable problem; how to get from where we are today, with the boot of a ruthless monopolist on the neck of our information and information processes, to where we really desire to be -  with our digital civilization in the hands of open standards, and out of the control of proprietary applications and platform vendors.

    This document describes what the OpenDocument Foundation learned in Massachusetts about the challenge of migrating to ODF. 

Gary Edwards

Joint letter to the Open Source Community From Novell and Microsoft - 0 views

  •  
    This makes me sick. The indemnification nazis are driving a patent wedge right through the heart and soul of open source.
  •  
    This makes me sick. The indemnification nazis are driving a patent wedge right through the heart and soul of open source.
  •  
    This makes me sick. The indemnification nazis are driving a patent wedge right through the heart and soul of open source.
Gary Edwards

The Meaning of Open Standards - 0 views

  •  
    The marbux comment:

    See particularly section 6.8 and its discussion of "etiquettes," which sounds like CDF profiles to me.

    This 1998 academic paper on open standards could give us a solid foundation to build our arguments for Universal Interop from. I may have forwarded this link before, roughly a year ago. Here is the abstract of the paper:

    This paper develops the argument that many Information Technology standardization processes are in transition from being controlled by standards creators to being controlled by standards implementers. The users of standardized implementations also have rights that they wish addressed. Ten basic rights of standards creators, implementers and users are identified and quantified. Each of these ten rights represents an aspect of Open Standards. Only when all ten rights are supported will standards be open to all.

    It builds upon a previous work by Bruce Perens. Well worth the read.

Paul Merrell

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

  • 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.
  •  
    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 270 Next › Last »
Showing 20 items per page