Your SlideShare is downloading. ×
Maximising theBenefits of OpenDataStuart Harrison @pezholioWeb Developer, ODIstuart.harrison@theodi.org
Maximising Benefits =Maximising Reuse• Legal ●     What can I (legally) do with this data?• Practical ●     How reliable i...
Legal• what can I do with the data?• clear, simple, unrestricted licences  ●    Open Government Licence• no contaminating ...
Practical• timeliness  ●    frequency of changes / releases  ●    lag in releases• quality control  ●    accuracy of the d...
Technical• machine-readable  ●    not images of tables• suitable to data type  ●    appropriate format & vocabulary• open ...
Social• documentation• gather feedback to improve  ●    every dataset contains mistakes  ●    email, form or API for corre...
Conclusions• 5 star scheme only covers format• also need to help re-users  ●    work out what they can do  ●    work out w...
What do you think?comment on alpha ODI Open DataCertificatehttp://theodi.github.com/open-data-certificate/questions?@pezho...
Upcoming SlideShare
Loading in...5
×

Data Driven Public Services - Stuart Harrison

827

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
827
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Data Driven Public Services - Stuart Harrison"

  1. 1. Maximising theBenefits of OpenDataStuart Harrison @pezholioWeb Developer, ODIstuart.harrison@theodi.org
  2. 2. Maximising Benefits =Maximising Reuse• Legal ● What can I (legally) do with this data?• Practical ● How reliable is the data? Frequency of updates?• Technical ● What format is the data in?• Social ● Where can I go to with problems?
  3. 3. Legal• what can I do with the data?• clear, simple, unrestricted licences ● Open Government Licence• no contaminating closed data ● extract out derived & copied data• no data protection concerns ● consent for re-use
  4. 4. Practical• timeliness ● frequency of changes / releases ● lag in releases• quality control ● accuracy of the data• guarantees ● availability (particularly of APIs) ● on-going publication
  5. 5. Technical• machine-readable ● not images of tables• suitable to data type ● appropriate format & vocabulary• open standard ● with open source implementations• using URIs as identifiers ● helps with linking up disparate datasets
  6. 6. Social• documentation• gather feedback to improve ● every dataset contains mistakes ● email, form or API for corrections• build community ● forum / group to share experience• provide tools ● libraries for operating with the data
  7. 7. Conclusions• 5 star scheme only covers format• also need to help re-users ● work out what they can do ● work out what they can rely on ● work with the data easily ● engage with you & others
  8. 8. What do you think?comment on alpha ODI Open DataCertificatehttp://theodi.github.com/open-data-certificate/questions?@pezholiostuart.harrison@theodi.org

×