[open-government] [euopendata] [psi-workers] Rules + website for Open Data Challenge

[Chris Taggart]

I think we should make it clear whether we are encouraging the building of
general tools (e.g. Google Refine type things), which should be open source,
or opening up data and building services on them while keeping the data open
(which doesn't and IMHO should require the source code to be open). For what
it's worth I think the focus should be on open data rather than open data
software tools (although there is definitely a need for this).

Chris
-- 
-------------------------------------------------------
OpenCorporates :: The Open Database of the Corporate World
http://opencorporates.com
OpenlyLocal :: Making Local Government More Transparent
http://openlylocal.com
Blog: http://countculture.wordpress.com
Twitter: http://twitter.com/CountCulture

On 24 March 2011 21:11, Daniel Dietrich <daniel.dietrich at okfn.org> wrote:

> Dear all,
>
> Besides all arguments about using open source technology....
>
> On 24.03.2011, at 13:26, Federico Morando wrote:
> > What needs to the open are the public data (in input), not necessarily
> the code/data of the re-users ("derived data")...
>
> I agree that what we needs to be open is the data! But I have a strong
> opinion that this should NOT be limited to the "data input". As a reference
> please see the article from Jonathan
>
> "Keeping Open Government Data Open?"
> http://blog.okfn.org/2011/03/01/keeping-open-government-data-open/
>
> One very important issue on our way towards a flowering "Open Data
> Landscape" is that we keep Open Data 'open'. As a principle we should call
> for apps, to be:
>
> Open in, open out – If you pull open data into your website or system, then
> others should be able to pull it out as open data as well.
>
> Regards
> Daniel
>
> On 24.03.2011, at 13:26, Federico Morando wrote:
>
> > On 03/24/2011 01:08 PM, Jonathan Gray wrote:
> >> Some key ideas for rules:
> >>
> >> * Pan-European angle is strongly encouraged
> > I surely agree. We may even say that you should use data from at least 2
> member states and/or that your app shoul make sense in at least two member
> states (e.g. in London and Paris).
> >> * Entries for apps must come from team which contains groups/individuals
> from at least 2 EU member states
> > I don't think that this is necessary: let's put constraints on the
> apps/data (as you did above and below) and not on the
> institution/organization/group that proposes them... It's a call for apps,
> not a EU project ;-)
> >> * Repurposed apps are allowed (i.e. an app that exists for London can be
> expanded to work for Paris + Torino and entered)
> > OK, sure!
> >> * Apps must be open source
> >> * Core data must be freely reusable and derived data must be openly
> licensed
> > I'm not entirely sure: we may say that this is a plus in the evaluation,
> but is it a requirement? What needs to the open are the public data (in
> input), not necessarily the code/data of the re-users ("derived data")...
> [Personally, I'm sympathetic with this rule - in particular the part about
> open source code: it's just that I think it deserves an explicit and open
> discussion.]
> >
> > Thanks and best regards,
> >
> > Federico
> >
> >
> >
> > _______________________________________________
> > euopendata mailing list
> > euopendata at lists.okfn.org
> > http://lists.okfn.org/mailman/listinfo/euopendata
>
>
> _______________________________________________
> open-government mailing list
> open-government at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/open-government
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/open-government/attachments/20110324/47126f92/attachment-0001.html>