This is a bit of a follow-up to some commercialisation thoughts, prompted by the following four points:
I sympathise with the idea of hosting your own data. Of course, for a lot of companies it'll be much handier to have some website do it for them - for a small fee. The internet makes this technically feasible, now it's up to a bit of structuring and a bit of organisation. So that's three things: own your data, structuring and organisation. * Own your data. Take a manufacturer in the construction industry as an example. You've got your own marketing materials and your own catalog, perhaps even a website. But "everybody uses" the local specification system, so you pay to be included. In their closed database in their format. And "everybody uses" that big publishing outfit's "construction documentation". So you pay them to include you. And you pay for inclusion in a few portals. All in their format and in their closed database. That is a steaming pile of money, burning a hole right through your quarterly figures.
I can't really help to make the comparison with scientific journals. Scientists write the articles (which costs money), scientists referee the articles (which costs money), scientists buy the journals with articles (which costs money). The publishers of the journals do a useful job, but what they pay (approximately zero) is way out of proportion with what they do (the scientist themselves do most of the work) and what they get payed (I don't want to know).
Back to the construction industry: paying money for advertisements and a bit of promotion and a bit of professional binding etc. of catalogs: that's OK. But the amount of effort and money needed to get your data that you own into somebody else's closed database...
Let's start with getting the individual acts together. Make the info in the drawing system available over the Internet in some documented format. Likewise for the specification system. Likewise for the accounting system. Likewise... Put behind passwords what should be kept within the project.
Figure out your own simple data format if you have to, document it and notify your partners, customers, whatever. Probably it'll be handier to have somebody else do the hard work and use his webserver to put your data online. But make sure you really own the data and that you can get it back :-) (A system like del.icio.us allows you to download a full dump of your data, which is the most trustworthy of promises that you own your own data).
The alternative? Local initiatives, small initiatives, cooperation, some research results, etc. Wikipedia works surprisingly well, so...
To finish up, some thoughts from my side with a potential startup in the back of my mind... The fact that I like the "own your data" idea almost makes it impossible for me to want to hoard other people's information. I'm not an grumpy dragon sitting on a hoard of information, ready to test the fire resistance and, if inadequate, the tastiness of everybody that ventures to close.
This is not something that's bad news, though. Hoarding information means that I (would I start that startup) would have to compete on the same terms as existing information providers. On their ground. OUCH. Better do something on a terrain where they can't follow: making as much as possible of the information free.
Not that I'm planning to start an 40-man company. The smaller the better, if I'm going through with it. Which means the company has to travel light, without 30 metric ton of data chained to the leg.
Still can't really understand why I'm seriously thinking about a startup. I was scared stiff of it a year ago. No way I was going to do that. But it is good for polishing my research-thinkwork. And I'm slowly coming into the mood. There's serious money in this. I believe I've mentioned one or two business models halfway this article... Hm.
And I kinda like it to post these thought out here in the open. The market is big enough when it is open. It is only when you want to make a quick land-grab when you really have to be secret. And that's not something in my planning.
My name is Reinout van Rees and I work a lot with Python (programming language) and Django (website framework). I live in The Netherlands and I'm happily married to Annie van Rees-Kooiman.
Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):