3. What has happened
●
We won the PICNIC hackathon with
Parkshark
●
We won the Apps voor Nederland with
Vistory
●
We entered 2 Hacks in Hack Day Paris and
got some honourable mentions
5. ●
Invited to talk at a DIVV internal meeting
●
Invited to participate at open Data Cafe
●
Invitation to input to
Smart City SDK
●
Commercial work
for CITION
6. ●
Invited to present to policy committee in
den Hague about app making
●
Invited by the UK embassy to an event for
UK/NL creative entrepreneurs
●
Building relationships
with cultural institutes
●
Exploring commercial
opportunities
9. ●
Open Data is not necessarily useful data
– Manage expectations
– Pursue a tipping point
Developers
Data
Open Data
10.
11. ●
About the data
– Make sure it is complete useable
– Write background information
– Actively ask the community for feedback
– Be prepared to improve the data
– Provide a contact person
– Real time is best, otherwise update regularly
12.
13. ●
Use the language of the developer
– Provide some specific challenges
– If possible use english as well as dutch
– Provide json
– Provide rest
– GEO : google maps not KML
– Understand who you are dealing with
14. ●
Especially consider the indie developer
– Make sure a creative mind can understand
the data
– Provide calculations and business rules
– Provide a way to contact you
– Don't force the developer to create a server
infrastructure
30. ●
What do we really need?
●
To Use the data
●
To innovate
●
How can we help and inform
●
Data owners
●
Policy makers
●
Can we give a list of our priorities?