2 Feb 14:12
Open Data Openness and Licensing
I've been meaning to put something down on 'open data' for some time. The motivation for actually doing something now were recent discussions with John Wilbanks and then the post of Michael Nielsen and related thread on okfn-discuss. [nielsen-thread]. [nielsen-thread]:http://lists.okfn.org/pipermail/okfn-discuss/2009-January/001206.html I'd really appreciate any comments people have. For those who prefer reading websites rather than lists I've also posted the text up at: <http://blog.okfn.org/2009/02/02/open-data-openness-and-licensing/> Lastly there are two appendices for this essay which I've left out in the interests of length. One is on 'Facts and Databases' the other is 'Comments on the Science Commons Protocol'. I'd be happy to send them along if anyone wants to them. Regards, Rufus # Open Data Openness and Licensing # ## Why does this matter? Why bother about openness and licensing for data? After all they don't matter in themselves: what we really care about are things like the progress of human knowledge or the freedom to understand and share. However, open data is crucial to progress on these more fundamental(Continue reading)
In particular, I
would be interested to hear how well it works for variable scope
proposals. It appears to be designed for fixed scope work. It starts
with a list of missing features, and pays out at the end only when they
are successfully realised (apparently). It doesn't appear directly to
coalesce different actors working across identical domains. Therefore,
it appears to reflect a market based approach, where vendors make
offers, customers make bids, and payments are made when procured goods
are delivered.
The software club process we've arrived at seems to be slightly
differently constituted. There are two levels: domain and proposal.
Central to the software club process is connecting with a definite
domain of work. Actors working within the domain are invited to become
members of the club. Members simply consent to the proposal for the
club, which defines the scope of objectives and the general strategy of
the club. The strategy is normally to share analysis and software
development on an incremental and indefinite basis. Then within these
indefinite iterations, the club host relentlessly builds consensus
around variable scope proposals to build capacity within the domain.
RSS Feed