Posts Tagged 'brm'

IP Issues with OOXML (DIS 29500)

Who’s Afraid of the GPL?

Out of all the free and open source licences which are available, there are two which are disproportionately chosen by FOSS developers when licensing their software. Those two are the GPL and the LGPL. Of these, the GPL is disproportionately favoured over the LGPL.* If there are issues with GPL implementations then there are IP issues with OOXML. Any assurance that excludes implementation under these licences is just cause for the FOSS community to voice concern.

The FAQ on the OSP has this to say about the GPL:

Q: Is this Promise consistent with open source licensing, namely the GPL? And can anyone implement the specification(s) without any concerns about Microsoft patents?

A: The Open Specification Promise is a simple and clear way to assure that the broadest audience of developers and customers working with commercial or open source software can implement the covered specification(s). We leave it to those implementing these technologies to understand the legal environments in which they operate. This includes people operating in a GPL environment. Because the General Public License (GPL) is not universally interpreted the same way by everyone, we can’t give anyone a legal opinion about how our language relates to the GPL or other OSS licenses, but based on feedback from the open source community we believe that a broad audience of developers can implement the specification(s).**

Imagine if you were standing next to someone’s land and there was a sign with the details of an open access promise (OAP), setting out when you are allowed to enter the land. It just so happens that the owner of the land is standing right beside you. You turn and say to them “So, this OAP, I’m here you can check me out, can I enter or not?”. They reply, “Well, I can’t really help you on that, you’ll have to read the OAP. It’s expressed in a simple and clear way – oh, and talk to your lawyer”.

If one thing is certain from that conversation it is that there are issues with you entering the land.

Similarly it is clear that there are issues with GPL implementations of DIS 29500. If there weren’t the answer would be phrased “A: Yes”. In fact, they still can. Microsoft can change the OSP right now by adding “and by the way any GPL implementation is permitted”. But they haven’t and I suspect they won’t.

If there are issues with GPL implementations then there are IP issues with OOXML. Microsoft implicitly concedes there are issues with GPL implementations.

Notes
* These figures are based on data from Sourceforge and relate to the numbers of projects licensed, without being weighted by popularity or maturity of the project.
** This FAQ indicates that those writing the FAQ believe that the OSP clearly permits implementation by some developers but not others based on the licence chosen by the developer. This raises the question of whether or not the OSP is really “non discriminatory” in effect.

DIS29500: BRM Process Unfair for SMEs?

The Issue

The fact that ECMA dispositions on National Body comments are only being made available through a password protected website has been widely reported (one example of many). The BRM convenor notes that this is due to the confidential nature of National Body comments (scroll down to the heading ECMA secrecy). While I had been aware of this before it has only occurred to me this week (while preparing for an informal working group meeting on DIS29500 arranged by Standards Australia – I am an OSIA representative) how difficult this makes it for small organisations to participate sensibly.

The reason is that, during the first phase leading up to the vote, it was easy to leverage off those parts of the specification that other people had commented on publicly. This, in effect, meant that everyone could take the benefit of everyone else’s work. Small organisations could therefore identify relevant issues from those identified by others. Not only did it allow taking the benefit of others’ work it also permitted the incremental improvement of it.

BRM Process Makes Review Much Harder

The BRM process radically changes that dynamic. Now the documents are confidential and, if they are confidential it is hard to comment on them publicly. As such each organisation which is pariticipating in a National Body consultation process is on its own.  With each prevented from interacting with others – collaboration is, in effect, banned. Each is left to trawl through the large number of dispositions to try to make what sense it can out of them. Without seeing other people’s views on the various dispositions it is very difficult to know which are significant and why (and which are insignificant and why not) – or even which dispositions relate to important issues identified in the lead up to the initial vote. The comparatively short time between the availability of the dispositions and the BRM (about 6 weeks or so) compounds this difficulty.

Of course, this gets back to the size of the document. A document one tenth of the size would probably be manageable under this process – even by a small organisation although it wouldn’t necessarily be pleasant. DIS29500 simply inspires despair. Presumably National Bodies will also be in a similar situation. Unless they have a substantial team that they can devote to the process how can they hope to adequately parse the dispositions – and any regressions that they create?

Is this Process Unfair to SMEs?

This creates the additional complication of whether a National Body, if it is required to take into account the interests of small and medium businesses and/or consumers, can reasonably fulfill that obligation under this process (for example, in Australia, the Productivity Commission’s November 2006 Research Report on Standard Setting and Laboratory Accreditation recommended that Standards Australia should “improve the balance of interests represented on technical committees by… increasing the participation of small business,…and other community interests“). If SMEs cannot parse the disposition in the time available, they cannot adequately understand its consequences and cannot therefore adequately represent their own interests to their National Body.


Blog Stats

  • 279,048 hits

OSWALD Newsletter

If you would like to receive OSWALD, a weekly open source news digest please send an email to oswald (with the subject "subscribe") at opensourcelaw.biz