advising on IT-business alignment
IT-business alignment about us blog our services articles & reports resources your profile exposure
blog
blog
Friday, June 10, 2005

On 100% openness - and consensual constraints

I was perusing Bob Sutor's excellent blog today and picked up this thread (also mused on by RedMonk among others) regarding the nature of openness. It's a big question - the idea (and the potential value) of "perfect openness" is a really interesting one - and it certainly got me thinking.

So below is a "first stab" at what might constitute a definition of "100% openness". I don't flatter myself that it is 100% complete or "correct" (whatever that might mean). But maybe (in a spirit of openness) it might fuel some others' thoughts.

I have a feeling that the only way to think about this at a sufficiently abstract level, is to focus on "inventions" - rather than source code, compiled software, APIs or whatever. So here goes.

1) 100% open means comprehensible without constraint. Understanding and utilisation of the invention must be simple. The invention must be exhaustively documented in a format which is readable by anyone, regardless of the technology they use to read documents.

2) 100% open means accessible without constraint. The documentation and any "first generation" (ie by the original inventor) encoding of the invention (for example in source code) must be made accessible to absolutely anyone, regardless of location or technology, without charge.

3) 100% open means contribution, debate and evolution without constraint. The invention, its documentation, and all encodings cannot be "owned" by anyone - no single person or entity with any vested commercial interests in the evolution of the assets can exert control over them.

4) 100% open means distributable without constraint. Anyone can make any changes at all to the invention as documented, its documentation, or any encoding of the invention without any ownership claims being made - consistent with the above, and with no charges being levied. Anyone can copy the originals, or changed originals, as much as they like.

5) 100% open means usable and modifiable without constraint. Anyone who either modifies the assets associated with the invention, or embeds them or links them to another invention, has no obligations at all to do anything in particular - no obligations to contribute any further invention in an open way, no obligation to be "open" at all.

(As an aside, it's interesting that "inventions" are what gets patented - one way of thinking about an encoding of the ideas above would be to create "anti-patents"...)

I've tried to create a list which is about the removal of constraints over invention. Sounds like a good plan. So - does this look like a desirable list of attributes, or even a workable one? I don't think so. Why? Because it's about the idea of openness, not the reailty of openness. This list would make a really crappy foundation for community invention, for example - and although the concept of "no ownership" is an interesting one, it's just not practical if taken to extremes. If there is no attribution of invention to individuals, where would you go to ask questions?

My suspicion is that even the things which are considered as "really open" and which have real utility in today's world - things like IP, XML, JPEG/MPEG, SQL etc - aren't 100% open inventions. Shouldn't we be actually aiming for 80% (or thereabouts) openness, with some "consensual constraints" to grease the wheels of community collaboration and commercial involvement? After all, Linus constrains the Linux kernel; Tim Berners-Lee and the W3C constrain XML; and so on.

Therein, I think, lies the rub with openness. One person's (or community's) comfortable constraints, can be anathema to another. That's why we will continue to have such healthy debate ;-)


Burn this feed
Burn this feed!

Creative Commons License
This work is licensed under a Creative Commons License.

Blog home

Previous posts

Oracle acquires TimesTen: a rational move but not ...
Don’t judge industry collaboration by source code ...
The complex nature of business processes...
Oracle's (con)Fusion Middleware?
Microsoft and Sun mark one year of collaboration
IBM's acqusition of Gluecode: it's about more than...
A note re: the IBM-Lawson Software tie-up: just re...
Gupta gets it – now can CA deliver?
OASIS SOA Reference Model - a positive start but l...
Note to Microsoft: join up sales & marketing!

Blog archive

March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
July 2008
August 2008
September 2008
October 2008
November 2008
December 2008
January 2009
February 2009
March 2009
April 2009
May 2009
June 2009
July 2009

Blogroll

Andrew McAfee
Andy Updegrove
Bob Sutor
Dare Obasanjo
Dave Orchard
Digital Identity
Don Box
Fred Chong's WebBlog
Inside Architecture
Irving Wladawsky-Berger
James Governor
Jon Udell
Kim Cameron
Nicholas Carr
Planet Identity
Radovan Janecek
Sandy Kemsley
Service Architecture - SOA
Todd Biske: Outside the Box

Powered by Blogger

Weblog Commenting and Trackback by HaloScan.com

Enter your email address to subscribe to updates:

Delivered by FeedBurner