Updates from April, 2007 Toggle Comment Threads | Keyboard Shortcuts

  • Roberto Galoppini 8:39 am on April 24, 2007 Permalink | Reply  

    Software Patent: the truth unveiled, Simon Phipps’s and Florian Mueller’s opinions 

    Talking about open source having a need for lobbyists I mentioned the David vs Patent Goliath fight, a ground where previously unknown lobbyists – people coming from the Economic Majority of European SMEs against software patents or no profit organizations like FFII – made their name.

    TruthTruth or Consequences by kxlly

    Simon Phipps joined the conversation, saying:

    Something this overlooks – and that was present in the CII Directive debate – is that as more and more companies depend on open source as the bedrock of their business, they will direct their lobbyists to act on behalf of the open source communities.

    I spent a great deal of time in support of lobbyists (as did my colleague Mark Webbink from Red Hat) patiently explaining to politicians and their staffs the problems with software patents as envisaged by Microsoft and the other pro-lobby members. In fact, I might even want to claim that our little informal alliance – Sun, Red Hat, Oracle, IBM and one other that prefers to remain anonymous – actually swung the interoperability argument that killed the Directive.

    This is not to say we don’t need lobbyists acting on behalf of FOSS projects directly. But don’t forget that corporations that grok FOSS lend can their weight to the cause.

    I took the chance to privately ask Florian Mueller – “No lobbyists as such” author and founder of the NoSoftwarePatents.com campaign – his opinion, that I fully quote.

    Anyway, interoperability was a secondary theater of war for us. The simplest way to explain it is that if you have no software patents, you don’t need an interoperability privilege. There was an email exchange in the week before the final vote between a lawyer working for some or all of the companies Simon refers to, the FFII’s then-president Hartmut Pilch, and myself. Both Hartmut and I pointed out that we looked at interoperability as a minor bargaining chip, far from a priority subject.

    It is true, however, that some interoperability proposals that were proposed back then as amendments caused a certain degree of discord within the pro-swpat camp, especially between IBM and Microsoft.

    I have previously explained and documented in my blog certain facts about Red Hat’s role.

    In a situation of political instability (back in those days, the Parliament was a “zoo” with dozens of lobbyists from both camps running around, numerous citizens emailing, faxing and phoning MEPs, etc.), anything can contribute to people’s nervousness, including some discord over a secondary issue like interoperability. But the important thing was to have that zoo, that overall instability, a large part of which was due to the political situation that had arisen from the FFII’s and my fight against the Council’s common position, including the restart initiative in the EP.
    The important second-reading amendments were the 21 amendments filed by various political groups and lists of MEPs at the FFII’s initiative, and certainly not the one proposed by the companies Simon refers to and which proposal was in fact not liked by the FFII and myself at all. Claiming that a small-scale interoperability initiative made all the difference for getting the proposed directive killed is like eating a peanut after a five-course meal and believing that it was that peanut which took your hunger away because after eating the peanut you no longer felt hungry.

    I never claimed all of the credit for myself and shared it with the FFII in a variety of public declarations. However, I would prefer for companies with an obvious, vested interest in currying favor with the community to take reasonable positions as well.

    I guess my most recent success in a policy area unrelated to patents (i.e., football broadcasting rights) gives me more credibility than I could gain from further debates on who made what contribution to the rejection of the swpat directive.

    Technorati Tags: software patent, simon phipps, FFII, florian mueller

     
    • Simon Phipps 12:53 pm on April 24, 2007 Permalink

      It’s exactly the fact that Florian thought interoperability irrelevant that made it important for others to champion it! His was an all-or-nothing strategy, and in the end it was that “peanut” that saved the day according to my independent sources. I know Florian disagreed and it seems we still differ. Oh well. At least CIID was defeated (or postponed)

      I’m afraid I find his response disappointing though, there was more than him and FFII in the fight. And my point (that corporations truly working with FOSS can be expected to defend it) stands, even if Florian want’s to try to dismiss it.

    • Roberto Galoppini 3:29 pm on April 24, 2007 Permalink

      Dear Simon,

      I might not refer to interoperability as irrelevant, neither I think Florian does, as results from his own words:

      It is true, however, that some interoperability proposals that were proposed back then as amendments caused a certain degree of discord within the pro-swpat camp, especially between IBM and Microsoft.

      Being an involved activist from the very beginning I can’t share your idea that, in your own words

      the interoperability argument killed the directive.

      By the way, considering that IBM, Sun, Oracle and other important players are still working on interoperability and open standards issues, I would be glad you all to take into consideration the hidden traps in Open Document (or any other open standard).

  • Roberto Galoppini 7:56 pm on April 21, 2007 Permalink | Reply  

    Open Source Government Policies: the French case 

    APRIL, the French advocacy group whose acronym stands for Association for Promotion and Research in Libre Computing, on the 2th of February launched a survey containing 14 questions to the presidential candidates, asking them for their positions on issues related to the future of the free software (patentability, royalty, data processing of control, interoperability, etc).

    Eiffel towerEiffel tower by Grufnik

    Eight out of 12 candidates have responded, as reported by the article of Bruce Byfield.

    Among respondees the major candidates, Ségolène Royal of the Socialist Party and François Bayrou of the Union for French Democracy, along with Nicolas Sarkozy of the Union for a Popular Movement, who also responded but not fully addressing APRIL’s questions.

    Kudos to APRIL for its great work, read here some excerpts of the original article, orif you can manage French have a look at the APRIL’s press release in French.

    (More …)

     
  • Roberto Galoppini 2:08 pm on April 21, 2007 Permalink | Reply  

    Open Source Hackers: Brian Behlendorf’s speech at the Digital Freedom expo 

    Brian Behlendorf, Apache founder and now CTO at Collabnet, on Thursday at the Digital Freedom Expo gave a speech entitled “Ten things you may not know about open source“.

    open standard campaignOpen Standard campaign by 4_eveR_Young

    Some excerpts out of his list:

    2. Apache kept the Web flat and free

    Apache was launched in 1995, at the time Netscape was the dominant Web browser and there was a fear that if the same company could own the browser market and the server market they would have too much control and could charge companies a tax of sorts for web hosting. Apache’s launch was done with a dual purpose. There was the pragmatic aspect of combining efforts for better development and there was the idealistic aspect of keeping HTTP (Hypertext transfer protocol) as an open standard.

    That is really interesting. Enforcing an Open Standards through an open source reference implementation. Someonelse is also suggesting the need for a reference implementation to augment – if not, perhaps, replace – the formal specification of the standard.

    4. Open Source helped free the human genome

    Before the mapping of the human genome had been completed, a commercial consortium, Celera, was sequencing the genome with the intention of patenting it. This preposterous idea of patenting a discovery rather than an invention began to get many geneticists concerned. In about 2002 a doctoral student, Jim Kent, wrote 10 000 lines of Perl code to make a program that could perform the number crunching of raw data that was necessary in sequencing the genome. This program [Human Genome Project] was then run over 100 Linux servers and the entire genome was successfully sequenced a few months before Celera finished.

    While more related to Open Knowledge this story is really interesting, in 2002 Tim O’Reilly described Kent’s work as “the most significant work of open source development in the past year”.

    5. Microsoft loves open source

    As odd as it sounds, Behlendorf explained that Microsoft has benefitted from open source development and also included software, which although not labeled “open source”, had the source code openly provided. The first use of TCP/IP in Windows was a port of Berkley’s code. He sited the work that Microsoft was doing with open source programs such as MySQL, SugarCRM and JBoss. Codeshare, Channel 9 and other websites were also cited as positive signs that the proprietary giant is openeing further, as Behlendorf put it, “dragged kicking and screaming into the future”.

    So I am alone thinking things like that. Ten days ago I happened to see a meeting of developers belonging to a Microsoft’s community and I was quite impressed.

    6. Altruism is not the only reason why people contribute to open source software

    Many contributors use the software professionally and find that doing things such as fixing bugs and adding features is much easier when collaborating within a group. According to a survey done in 2006, the existing base of FLOSS represents 131 000 real person years of developmental effort. The costs of sharing code are low while the benefits are high.

    Many thanks Brian, I am really tired to listen to professors talking about gifts and fun, I am happy that people hacking for real can tell them the truth.

    9. Open source can still change the world

    Behlendorf strongly believes in the power of open source to make the world a better place, citing many examples. Within government, he believes that open source software can help immensely in counting election votes in a trustworthy way and also with transparency of government’s actions and policy. For countries such as China where there is restricted acces on the internet, open source has already been successful on helping people within these countries get greater access by overcoming the censorship exerted on them. Third world development can benefite greatly through initiatives such as the One Laptop Per Child project which runs on entirely open source software for the dual purpose of making it cheaper to produce and so that it can be modified to suite each country’s specific needs. Fighting digital rights management was another example given.

    Technorati Tags: Open Source, open standard, hacker, behlendorf

     
  • Roberto Galoppini 9:31 am on April 20, 2007 Permalink | Reply  

    OpenOffice.org Users: Michael Dell enjoys OpenOffice.org 2.2! 

    Michael Dell, Chief Executive Officer of Dell, at home uses the last release of Ubuntu 7.04 (7.04, aka Feisty Fawn) on a Precision M90 laptop loaded with Openoffice.org 2.2 (download), as results from his biography.

    dell&dr evilDell and Dr.Evil by edans

    While Dell actually didn’t address the demand for Linux pre-installed PCs, the company opened a linux community forum and later a survey to assess users’ linux demand.

    Shuttleworth during a conference call with the press said that Michael Dell’s use of Ubuntu it is not an indication that Canonical is or not in discussions with Dell. He also added:

    The only time I ever met Michael Dell was at a Microsoft Summit at their headquarters and I didn’t think it appropriate to bring up Linux there.

    Technorati Tags: OpenOffice, Dell, Ubuntu, Shuttleworth

     
  • Roberto Galoppini 8:42 am on April 17, 2007 Permalink | Reply  

    Open Source Advocacy: Wheeler revised his paper “Why Open Source Software / Free Software (OSS/FS, FLOSS, or FOSS)? Look at the Numbers!” 

    David Wheeler, who I always mention talking about Commercial open source, just released a revised version of his most famous paper, Why Open Source Software / Free Software (OSS/FS, FLOSS, or FOSS)? Look at the Numbers!“. The study contains quantitative data showing that considering FLOSS makes a lot of sense.

    Linux plate/dev/porsche by Xenedis

    This paper provides quantitative data that, in many cases, using open source software / free software (abbreviated as OSS/FS, FLOSS, or FOSS) is a reasonable or even superior approach to using their proprietary competition according to various measures. This paper’s goal is to show that you should consider using OSS/FS when acquiring software. This paper examines market share, reliability, performance, scalability, security, and total cost of ownership. It also has sections on non-quantitative issues, unnecessary fears, OSS/FS on the desktop, usage reports, governments and OSS/FS, other sites providing related information, and ends with some conclusions. An appendix gives more background information about OSS/FS. You can view this paper at http://www.dwheeler.com/oss_fs_why.html.

    Technorati Tags: Open Source Advocacy, Wheeler

     
    • Andrea Trasatti 4:19 pm on April 30, 2007 Permalink

      It took me a couple of weeks to find the time to read this article… Not yours, Roberto, but the original by Wheeler. It is interesting in the beginning, but honestly it just becomes boring after you realize that it’s about 70 pages of raw numbers.

      Anyway, I am sure it’s been a LONG work to collect these.

      I think the update should have also removed totally outdated resources, such the statistic that said that linux handhelds have about the same installbase as microsoft windows-based. Unfortunately, this is not true by far, today.

    • Roberto Galoppini 8:45 pm on May 6, 2007 Permalink

      Andrea I suggest you to write David, he is always open to others’ suggestions.

  • Roberto Galoppini 10:36 pm on April 10, 2007 Permalink | Reply  

    Community-based production: do they need a roadmap? The Debian case 

    The Debian Project yesterday announced the release of “etch”, the last version of Debian.
    The press release reported that it took 21 months of development to create this release. Whether you consider contributing to Debian a work or a joy, it would be interesting to know how much would have cost to develop “etch” from scratch.

    roadmapRoadmap by Pinocure

    Being based exclusively on volunteer contributions, Debian can’t grant the availability of all packages included in the previous version, as results from “Evolution of Volunteer Participation in Libre Software Projects: Evidence from Debian“. Packages maintained by volunteers who left the project become unmaintained (“orphaned”) and the probability that an orphaned package gets adopted by other maintainers is not 1.

    [..] maintainers who left Debian between July 1996 and December 2004 were responsible for 33.5% of the packages in 2.0, 67.5% of these packages can still be found in 3.0.

    The Constitution itself can’t help much when a volunteer decide to exit and no one is willing to take care of his or her tasks. It is worth to notice that within an hybrid production model paid employees are often responsible for less attractive tasks, as results from “GNOME, a case of open source global software development“:

    Paid employees are usually responsible for the following tasks: project de- sign and coordination, testing, documentation, and bug fix- ing. These tasks are usually less attractive to volunteers. By taking care of them, the paid employees make sure that the development of GNOME continues at a steady pace.

    Corporate production has to be on Time on Budget. The firm solves the problem of finding the efficient management of human resources through time not allowing the free entry and exit, and delegating production control to a manager.

    Community-based production on the contrary allows volunteers to enter and choose their tasks. Volunteers choosing what to do apply for tasks they like, and that they are likely to accomplish effectively. They can also freely exit from a project though, or not to end their tasks on time.

    How open source firms will approach the hybrid production model? Whatever is your guess, read the following (old) excerpt from the Debian Weekly News – December 2nd, 2003:

    Debian Roadmap? The project was asked if there was a roadmap for the Debian distribution, so that certification can be organised accordingly. Ben Collins pointed out that Debian hardly has release goals and Jonathan Dowland added that a smaller group of loose-knit volunteers has managed to agree on a roadmap.

    Technorati Tags: Debian, Coordination costs, Hierarchy, hybrid production model

     
    • Martin Michlmayr 2:42 pm on May 10, 2007 Permalink

      I believe roadmaps are gaining importance in free software development too. IMHO this is related to increased complexity found in many successful projects (both in terms of the size of the development community and the code base itself), which requires a higher degree of planning than in the past. For example, shortly after Debian 4.0 was released, the release managers contacted the maintainers of every large software package in Debian (e.g. the Linux kernel, KDE and GNOME) to obtain more information about the release plans of these projects. This information will be used to create a release plan for Debian. Furthermore, during the development cycle of Debian 4.0, release goals were defined in a much better way than this was done in the past. There was also a split into release blockers and release goals to make it clearer which work is absolutely needed before a release can be made.

      In summary, I don’t believe the absence of plans is something inherent with free software development. I believe there will be more planning as more projects gain considerable complexity and size, and to some extent we can see that already.

    • Roberto Galoppini 5:06 pm on May 13, 2007 Permalink

      Martin thank you to join the conversation. I agree with you, the absence of plans is not inherent with free software development.

      You mentioned GNOME and other projects where paid developers are on duty for unsexy tasks. Do you believe that the hybrid production model might be the third way?

      This way we might get the best of both world, but harmonizing contributions is not straightforward, though.

    • Martin Michlmayr 12:47 pm on May 30, 2007 Permalink

      There’s certainly a trend towards hybrid models, even though they are (or may be) associated with certain problems too. There’s a fairly good paper about the issue of control in the Netbeans community. The question there is who is actually in charge of the project – community or a company (Sun in this case).

      Reference:

      Jensen, Chris and Scacchi, Walt: Collaboration, Leadership, Control, and Conflict Negotiation in the Netbeans.org Community

    • Roberto Galoppini 3:07 pm on June 2, 2007 Permalink

      Thank you Martin, I didn’t read that paper before.

      The way a corporate actor open the development process to others can deeply affect results. Looking at Eclipse vs Netbeans popularity I wonder at which extent it is to be related to the way IBM and Sun backed their respective projects.

  • Carlo Daffara 2:03 pm on April 6, 2007 Permalink | Reply  

    Open Source Business Models: a Taxonomy of Open Source Firms’ business models 

    Within the context of the FLOSSMETRICS project we are performing a study on the business models adopted by companies that are leveraging FLOSS source code, and how the model changes with respect of licenses and commercialization approaches.In this post I present a draft of the result of 80 FLOSS-based companies and business models, conducted using only publicly available data. Feedbacks and suggestions are welcome!

    taxonomyPractical taxonomy by ellen’s attic

    Methodology

    An initial list of 120 companies was prepared during the first two month of 2007 using some popular open source news websites as source like FreshMeat, Slashdot.org, OSNews, LinuxToday, NewsForge and some blog sites devoted to FLOSS business models like those of Matt Asay, Fabrizio Capobianco, Roberto Galoppini. Additional information was retrieved from Google searches. this list was further refined by eliminating companies that were not really adopting FLOSS, even using a very relaxed definition. In the specific, any company that allowed source code access only to non-commercial users, or that did not allowed for redistribution was dropped from the list; also, companies for which no information was available, or for which no clear product or service was identifiable was equally eliminated. One of the companies included (Sourceforge, from the OSTG group) is not open source in itself, but represents an example of an “ancillary” model, as the site itself hosts more than 100000 open source projects and provides supporting services like mailing lists, source code versioning systems and file distribution. Also, companies that have a significant OSS contribution, but for which FLOSS is not the core business model were not included (this for example includes IBM, HP and Sun; all of which are important FLOSS contributors, but for which open source software is just one of the overall revenue streams).

    Results

    The final result is summarized in a table (pdf), the 6 main clusters identified are:

    Twin licensing: the same software code distributed under the GPL and a commercial license. This model is mainly used by producers of developer-oriented tools and software, and works thanks to the strong coupling clause of the GPL, that requires derivative works or software directly linked to be covered under the same license. Companies not willing to release their own software under the GPL can buy a commercial license that is in a sense an exception to the binding clause; by those that value the “free as in speech” idea of free/libre software this is seen as a good compromise between helping those that abide to the GPL and receive the software for free (and make their software available as FLOSS) and benefiting through the commercial license for those that want to maintain the code proprietary. The downside of twin licensing is that external contributors must accept the same licensing regime, and this has been shown to reduce the volume of external contributions (that becomes mainly limited to bug fixes and small additions).

    Split OSS/commercial products: this model distinguish between a basic FLOSS software and a commercial version, based on the libre one but with the addition of proprietary plugins. Most companies adopt as license the Mozilla Public License, as it allows explicitly this form of intermixing, and allows for much greater participation from external contributions, as no acceptance of double licensing is required. The model has the intrinsic downside that the FLOSS product must be valuable to be attractive for the users, but must also be not complete enough to prevent competition with the commercial one. This balance is difficult to achieve and maintain over time; also, if the software is of large interest, developers may try to complete the missing functionality in a purely open source way, thus reducing the attractiveness of the commercial version.

    Badgeware: a recent reinvention/extension of a previous license constraint, that is usually based on the Mozilla Public License with the addition of a “visibility constraint”, the non-removability of visible trademarks or elements from a user interface. This allows the company to leverage trademark protection, and allows the original developers to receive recognition even if the software is resold through independent resellers.

    Product specialists: companies that created, or maintain a specific software project, and use a pure FLOSS license to distribute it. The main revenues are provided from services like training and consulting (the “ITSC” class) and follow the original “best code here” and “best knowledge here” of the original EUWG classification. It leverages the assumption, commonly held, that the most knowledgeable experts on a software are those that have developed it, and this way can provide services with a limited marketing effort, by leveraging the free redistribution of the code. The downside of the model is that there is a limited barrier of entry for potential competitors, as the only investment that is needed is in the acquisition of specific skills and expertise on the software itself.

    Platform providers: companies that provide selection, support, integration and services on a set of projects, collectively forming a tested and verified platform. In this sense, even linux distributions were classified as platforms; the interesting observation is that those distributions are licensed for a significant part under pure FLOSS licenses to maximize external contributions, and leverage copyright protection to prevent outright copying but not “cloning” (the removal of copyrighted material like logos and trademark to create a new product). The main value proposition comes in the form of guaranteed quality, stability and reliability, and the certainty of support for business critical applications.

    Selection/consulting companies: companies in this class are not strictly developers, but provide consulting and selection/evaluation services on a wide range of project, in a way that is close to the analyst role. These companies tend to have very limited impact on the FLOSS communities, as the evaluation results and the evaluation process are usually a proprietary asset.

    The remaining companies are in too limited number to allow for any extrapolation, but do show that non-trivial business model may be found on ancillary markets. For example, the Mozilla foundation obtains a non trivial amount of money from a search engine partnership with Google (an estimated 72M$ in 2006), while SourceForge/OSTG receives the majority of revenues from ecommerce sales of the affiliate ThinkGeek site.

    Technorati Tags: , ,

     
    • Seth Grimes 6:53 pm on May 18, 2007 Permalink

      Roberto,

      Looking at http://www.robertogaloppini.net/documents/businessmodels.pdf

      – I believe that EnterpriseDB does not provide ANY OSS. They sell only closed-source extensions to PostgreSQL.

      – Given that you have SugarCRM, why not also list CentricCRM, which provides a good contrast?

      – And given Pentaho & JasperSoft, how about SpagoBI or all of Spago?

      – If your going to list Red Hat, then you should list Novell rather than SuSE Linux.

      – I’d suggest that “dual licensing” is a better term than “twin licensing.”

      Ciao,

      Seth

    • Carlo Daffara 2:15 pm on May 21, 2007 Permalink

      Seth: many thanks for your comments. On EnterpriseDB, the reason for inclusion is related to how we evaluate “open source” companies; that is, if the company sponsors in a direct or indirect way an open source project that is the basis of his work, then we consider the company to be a “marginal” open source one. The inclusion of EnterpriseDB is related to the direct funding of most of postgresql developers, through employing. In this sense, while not directly “selling” an open source version of postgresql, they are creating a market model that is similar to the split oss/commercial ones.
      On Novell/Suse you are right; the longer title was “novell Suse linux” to distinguish from the other novell activities, and simply got cropped.
      CentricCRM is simply not open source at all; the license explicitly states that “You may not redistribute the code, and you may not sublicense copies or
      derivatives of the code, either as software or as a service.” and as such it clearly is not meeting the definition of open source software.
      As for SpagoBI, Engineering seems at the moment mainly touching the waters with his OSS offer; I will wait a little bit to see if I can obtain balance sheet data on how much is obtained through OSS offers.

    • James Dixon 4:21 am on May 22, 2007 Permalink

      That is a lot of research.

      If you are interested I have developed a model to describe the open source model used by companies that write the majority of the code (JBoss, MySQL, Alfresco, Pentaho, SugarCRM etc).

      http://www.pentaho.com/beekeeper

      James Dixon
      Chief Geek / CTO Pentaho

    • Martin 6:19 pm on May 31, 2007 Permalink

      James… I love the beekeeper analogy. The paper has helped to crystalise my own thoughts on successful software projects.

    • Roberto Galoppini 6:53 pm on May 31, 2007 Permalink

      Hi Martin,

      I also enjoyed the metaphor, really amusing.
      Quoting your comment about your attention:

      But one observation really got my attention. In POSS projects (or even FLOSS projects), the end user (/customer) is engaged at a much earlier stage in the process, thereby ensuring that design defects and unexpected use cases are brought to surface before it is too late.

      I don’t believe that is typical of FLOSS listening to users, Microsoft and many other proprietary vendors do listen too, sometimes even more than some OS firms (just have a look at many OS products’ forums, you’ll sort it out by yourself!).

      OS applications’ ecosystems? May be, but they can be effective only under certain circumstances, definitely not an easy game to play, though.

  • mfioretti 8:58 am on April 1, 2007 Permalink | Reply  

    File Format: Hidden traps in OpenDocument (or any other open standard) and how to avoid them 

    (Note: this post is an excerpt and a follow-up of an article published in December 2006 in the monographic issue on the OpenDocument Format by Upgrade, the online version of the Spanish magazine Novatica. The whole monography can be read online)

    It is almost sure that, eventually, all major producers of both proprietary and Free software in the office files space will support OpenDocument. In and by itself, however, that standard is open to several ways to keep monopolies possible, or to nullify its usefulness for long term archiving.

    Technically speaking, OpenDocument is very powerful and useful because it can be extended. The standard doesn’t mandate, however, nor it should, that all extensions are licensed in the same way as the standard itself. Even ignoring future extensions, the standard as it is today has plenty of backdoors for proprietary traps. Some examples are (see the full Novatica article for details):

    • digital signatures
    • macros
    • embedded images, audio or any other multimedia object embedded in texts spreadsheets and presentations
    • in-file databases

    Objects of this kind can be placed inside an OpenDocument file even if their format is accessible only through patent-covered or otherwise proprietary software. Nothing in the OpenDocument specification prevents this (and, again, it shouldn’t!).

    The practical consequence is that it is possible to have a perfectly Free as in Freedom XML container which is full of patent-ridden components. A container, in other words, which is culturally, economically and politically useless to guarantee long term preservation of information, public ownership of public documents or a really free market in the software industry.

    If anything, the fact that an office file standard is not owned and controlled by one vendor may make it even easier, not harder, than proprietary extensions appear to keep end users locked in, at least in some scenarios.

    Does this mean that OpenDocument is useless?

    Not at all. Personally, I am still convinced that OpenDocument is by far the best possible solution for a very serious problem. To the best of my knowledge, OpenXML is still much worse than OpenDocument both in terms of feasible support in third party applications and in terms of space left to reinventing the wheel and unnecessary proprietary extensions . For these reasons, I remain convinced that it is necessary, at least for creation of new public documents, to just say no to OpenXml (available to unregistered users by the end of April).

    At the same time, I am convinced that it is necessary to stop, at least in the public sector, to just “switch to OpenDocument” and feel happy about it without looking behind the corner. I believe that further steps need to be taken, steps which, by the way, are not specific to OpenDocument.

    What is the right solution?

    OK, so “100% OpenDocument (or OpenXML) Compliance” isn’t enough to guarantee that an OpenDocument report or law proposal stored today will be completely readable and usable 20 or more years from now. The real solution, however, is not a technical one. Technical ways to apply it once it exists are available, and they are mentioned in my Novatica article.

    This said, this is not a format specification issue. When present, technical extensibility of a standard is (and must remain) neutral with respect to intentions. It would be very inefficient, if not plain wrong, to place specifications of a legal nature inside what must remain purely technical documents.

    What I believe to be necessary is to establish and enforce:

    • in the first place, some official “OpenFile” trademark or equivalent label which can be legally applied only to files in which no component has restrictive licenses or uncomplete documentation
    • immediately after that, laws requiring that OpenDocument files can be stored by, or exchanged with public Administrations, libraries and so only if they carry this “OpenFile” seal. Exceptions to this rule should be temporarily granted only in really exceptional cases, when there really is no alternative

    What do you think? Are these conditions enough? Who should define the “label”? Governments or standard bodies? Who should enforce its usage? Which exceptions could or should be tolerated? Please let me know: I am very interested to hear your opinion and to participate in any future discussions on these issues!

    (Thanks to Roberto for suggesting that I write this post and for hosting it!)

     
    • Llorenç Pagés 9:59 pm on April 18, 2007 Permalink

      I think that your arguments are very interesting and the dilemma you are posing very challenging.

      I have translated your message into Spanish and posted it onto the ATI debate forum devoted to Open Document Standards

      I am planning to summarize and post that summary here, if exist, the most interesting opinions we collect on the ATI forum.

      Thank you very much Marco for giving me permission to make that translation.

      Llorenç Pagés
      Chief Editor of Novatica and Upgrade

    • Hikari 4:59 pm on February 19, 2012 Permalink

      Well, the features you listed are needed, and some of them can’t be open.

      Digital Certificate code can be open, I believe its hash data can also be, does ODF formats support it? But, AFAIK, there’s no open software to handle DC, and editor must access its proprietary DLL to sign the document. In the same way, to validate the sining we must access its AC. Would we wanna give up on signed documents and DC?

      Macro is editor-related in the way that it automates editor features, it can’t be standardized because it’d limit how editors work. Well, we need macros to automate our work, and when we decide to use it we know it will be bound to current editor and we’ll have trouble porting it to other editor, even the same model in different version. The solution would be ODF formats support multiple macros in them, related to specific editors, in a way that one editor can’t change or delete other editor’s macros. OR, macros be completely banned and each editor create external files to store its macros.

      Embedded multimedia data is also trouble. HTML 5 supporters are having hard time for years to define which formats will be standardized. Of course, any user worried with long time storage will use properly formats for their multimedia data as they do with their text, be we also can’t stop users from storing proprietary formats, because they’d get angry and go to Micro$oft ones.

      In general, I think ODF formats don’t need to force “openess”, they just need to support and allow it, and each user uses it in the way it’s better for them. Let’s not forget GIF, whose support is gone for years but is still largely used and supported by readers and editors.

      What we can’t allow, at any cost, is that editors add proprietary data inside ODF files without user explicit knowledge and acceptance, because if that’s done the user will only find out years later when it’s too late.

  • Roberto Galoppini 7:22 pm on March 30, 2007 Permalink | Reply  

    European Open Source Observatory news – 30 March 2007 

    IDABC‘s Monthly Open Source News Service has been just released. The Open Source Observatory ‘s monthly new service keeps us updated on news related to the use of FLOSS in the European Public Sector.

    Some interesting spots:

    IT: Umbria to promote Open Source in schools
    Open Source News – 27 March 2007 – Italy – Policies and Announcements

    The regional government of Umbria is investing 100.000 euro to promote the use of Open Source in local schools. The Italian region will soon train students, teachers and education management in the use of this type of software.

    DK: Open standards made mandatory
    Open Source news – 19 March 2007 – Denmark – Policies and announcements

    Denmark is making the use of open standards mandatory in state, region and municipal governments starting next year. This was announced on February 23rd by Helge Sander, minister of Sciences, Technology and Innovation. His plan comes eight months after a resolution in the Danish parliament.
    FR: OpenMairie, competitive Open Source services for medium-sized cities
    Open Source News – 15 March 2007 – France – Deployments and Migrations

    OpenMarie, a French Open Source project aiming to develop governmental applications for medium sized French cities, is increasing the competition in the market for applications for public administrations.

    Technorati Tags: Open Source, IDABC, Italy, Denmark, France

     
  • italovignoli 9:40 am on March 28, 2007 Permalink | Reply  

    OpenOffice.org Security: OpenOffice.org Italian Association comments Secunia’s report 

    Secunia, the Danish company that collects, evaluates, verifies and analyzes all the information about software vulnerabilities, has just published the 2006 Report. The document summarizes the facts of the past year, and offers some statistics on the software that have been hit more severely by security problems.

    In 2006, OpenOffice.Org has been affected only by 5 vulnerabilities for the total of the three versions still available in the market (which have all been solved), while its largest competitor – a proprietary application – has been affected by 67 vulnerabilities (several of these problems have not yet been solved, even if they have been identified quite a long time ago). This makes this software a leader of a very unconfortable category.

    The last problem identified by Secunia last week, about three vulnerabilities – of which only the first, related to documents in WordPerfect native format, has been solved by a patch  while the others are still under scrutiny – is going to be solved by OpenOffice.Org 2.2, which is going to be released very soon.

    The full report in PDF format is available for download.

    PLIO, the OpenOffice.org Italian Native-Lang Project, is the Italian community of volunteers who develop, support and promote the open-source office productivity suite, OpenOffice.org. OpenOffice.org supports the Open Document Format for Office applications (standard ISO/IEC 26300) and is available on major computing platforms in over 90 languages, available to 90% of the world-wide population in their own mother tongue.
    OpenOffice.org is provided under the GNU Lesser General Public Licence (LGPL), can be legally used in any context. 

    PLIO, Progetto Linguistico Italiano OpenOffice.org:
    http://it.openoffice.org
    “Vola e fai volare con i gabbiani di OpenOffice.org: usalo, copialo e regalalo, è legale!”
    For further information: Italo Vignoli (+39.348.5653829), stampa@openoffice.org

    Technorati Tags: OpenOffice.org, OpenOffice, PLIO, Security, Secunia

     
c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel