Language Selection

English French German Italian Portuguese Spanish

The open source business process

Filed under
OSS

Open source is more than Linux, more than software.

It is at heart a business process. You let people see what you’re doing. You use open APIs. You link to as many other business models as possible.

This was seen in full last week, as Macromind founder Marc Canter (right, by our own Dan Farber) announced the GoingOn Network at Tony Perkins’ AlwaysOn conference.

Canter calls GoingOn a Digital Lifestyle Aggregator (DLA). It supports subscriptions, all types of digital publishing and templates, but more important it’s based entirely on open standards.

“Our APIs and schemas will be completely open and anyone can use them to interconnect social networks together. Not just to our network. Any network to any network,” he writes. (Marc also pointed out numerous mistakes in my first blog entry about this, so you you might call this story a result of open source journalism.)

The open source business process is a two-way street, Canter adds. He's also supporting a number of other APIs, especially concerning identity, as seen in this chart.

This open source business process is catching on at companies both large and small. Google’s Map API is an example of an open source business process. Yahoo’s MyWeb 2.0 is another example.
SixApart VP Anil Dash says his company’s LiveJournal pioneered this approach five years ago. Key components of Movable Type and Typepad, including implementations of Atom, FOAF and SOAP, have all been released as open source, “and we eat our own dog food by building on top of them in the applications and platforms we ship.”

I think it's the two-way open source business proces, not open source software per se, which companies like Microsoft and Oracle are finding the greatest trouble with. It’s the first great business invention of the 21st century. It’s changing the world in Internet Time.

Source.

More in Tux Machines

Uselessd: A Stripped Down Version Of Systemd

The boycotting of systemd has led to the creation of uselessd, a new init daemon based off systemd that tries to strip out the "unnecessary" features. Uselessd in its early stages of development is systemd reduced to being a basic init daemon process with "the superfluous stuff cut out". Among the items removed are removing of journald, libudev, udevd, and superfluous unit types. Read more

Android One: Let us fill you in on Google’s big game

India is now the world’s third largest Internet market and “on a bullet train to become the second”. But even when we become the second with around 300 million Internet users, India would still have over 75 per cent of the population that has no access to this so-called information superhighway. It is this chunk of population that will form the “next billion” which companies like Nokia, and now Google, has been talking about. And it is this next billion that Google thinks will line up to buy and good smartphone that is also affordable. Read more

Mesa Gets Closer To Having OpenGL 4.0 Tessellation Support

A significant patch-set was published on Saturday night that implements the driver-independent bits of OpenGL 4's ARB_tessellation_shader extension inside Mesa. The tessellation support has been one of the big pieces missing from Mesa's OpenGL 4 implementation and fortunately it's getting close to mainline. Chris Forbes of Intel published fifty-six patches this weekend that implement the driver-independent portions of the extension inside Mesa. Of course, the driver portions still need to follow for it to be useful. Read more

Small Console Menu Utilities

One of the great strengths of Linux is the whole raft of weird and wonderful open source utilities. That strength does not simply derive from the functionality they offer, but from the synergy generated by using them together, sometimes in conjunction with applications. The Unix philosophy spawned a "software tools" movement which focused on developing concise, basic, clear, modular and extensible code that can be used for other projects. This philosophy remains an important element for many Linux projects. Good open source developers writing utilities seek to make sure the utility does its job as well as possible, and work well with other utilities. The goal is that users have a handful of tools, each of which seeks to excel at one thing. Some utilities work well on their own. This article looks at four tiny utilities that offer menu facilities. They get virtually zero coverage in the Linux press, so you may not have heard of them before, but they are well crafted and might just fit the bill. Read more