Want more apps to be built on your open data? Discover ways to make data more developer friendly. We will look at the history of the Internet and current trends to build an understanding of standards and interfaces to make your data future friendly. At the same time it will make it more useful to developers, citizens and your own organization.

1. Developer Friendly
Open Data
Albert O’Connor @amjoconn
Colin Bell @collectdevCA

2. { lessons from the Internet }
{ APIs }
{ platform for productivity }

3. { lessons from the Internet }

5. “The Internet is becoming the town
square for the global village of
tomorrow.”
Bill Gates

6. The Web

7. The Web
The Internet
SSH
FTP
Skype Email
IRC BitTorrent
DNS
Online
Gaming

8. Gopher
Bulletin Board Systems

9. How did the Web come to
dominate?

10. Clay Shirky observed that
the Web won because it is
evolutionary
Source: http://www.shirky.com/writings/evolve.html [2013]

11. Not because it was perfectly
designed or technically
superior

12. Weakly Defined
Solutions that produce partial results
when partially implemented can
succeed.

13. Constantly Changing
What is, is wrong, no evolving system is
ever perfectly in sync with the
challenges it faces.

14. Evolution is cleverer than you
The ability to understand what is missing
at any given moment does not mean
that one person or a small central group
can design a better system in the long
haul.

15. HTML5

16. Open Data

17. { application programmer
interfaces — APIs }

18. What application?

19. UI or GUI
Graphical User Interface

20. Data User Interface
or
Developer User Interface

21. DUI

22. DUI
err
API

23. File Based Open Data
http://www.regionofwaterloo.ca/opendatadownloads/DoorsOpendataset.xls
 Save file on disk
Parse the file
Store as Intermediate format
Load entire dataset into app
Index
Query
 Present Result
App
Data
loader

24. API Open Data
http://api.uwaterloo.ca/public/v1/?key=FFF&service=Weather&output=json
{} Json
Convert some data types
 Present Result
App
Language
Specific
Library

25. When and how often do I
load the data?
Do I always have to
resubmit my App?

26. Why API?
1 - Monitoring
2 - Metrics

27. Why API?
1 - Monitoring / Audit ➡ Who, What, When?
2 - Metrics / Analytics ➡ How?

28. { platform for productivity }

29. Effectiveness + Efficiency
Efficient (adj.) - performing or functioning in
the best possible manner with the least waste
of time and effort.
Source: http://dictionary.reference.com [2013]
Effective (adj.) - adequate to accomplish a
purpose; producing the intended or expected
result.

30. Effectiveness + Efficiency
{} JSON
Convert some data types
 Present Result
App
Language
Specific
Library
API Open Data
 Save file on disk
Parse the file
Store as Intermediate format
Load entire dataset into app
Index
Query
 Present Result
App
Data
loader
File Based Open Data

31. {} JSON
Convert some data types
 Present Result
App
Language
Specific
Library
API Open Data
 Save file on disk
Parse the file
Store as Intermediate format
Load entire dataset into app
Index
Query
 Present Result
App
Data
loader
File Based Open Data
Data Access
File Based
both
effective
Data Access
API
Effectiveness + Efficiency

32. { file based works }

33. {} JSON
Convert some data types
 Present Result
App
Language
Specific
Library
API Open Data
 Save file on disk
Parse the file
Store as Intermediate format
Load entire dataset into app
Index
Query
 Present Result
App
Data
loader
File Based Open Data
7 steps
File Based
<
less
efficient
3 steps
API
Effectiveness + Efficiency

34. {} JSON
Convert some data types
 Present Result
App
Language
Specific
Library
API Open Data
 Save file on disk
Parse the file
Store as Intermediate format
Load entire dataset into app
Index
Query
 Present Result
App
Data
loader
File Based Open Data
7 steps
File Based
<
less
efficient
3 steps
API
Effectiveness + Efficiency
- duplication
- silos
- complexity
- blind to use
- on-demand
- direct
- benign
- visible

35. Effectiveness + Efficiency =
Productivity
Productivity is the effective use of innovation
and resources to increase the value-added
content of products and services. It is the
true source of competitive advantage that
creates long term economic viability and a
better standard of living for all.
Source: http://hkpc.org => http://bit.ly/ZoivM7 [2013]

36. Effectiveness + Efficiency =
Productivity
Innovation + Resources
combine to make
Products + Services

37. Effectiveness + Efficiency =
Productivity
Innovation + Resources
combine to make
Products + Services
Adding value makes us more efficient!

38. Effectiveness + Efficiency =
Productivity
Innovation + Resources
combine to make
Products + Services
Adding value makes us more efficient!
Effectiveness and Efficiency make us Productive.

39. { make all the things! }

40. { make all the things! }
... but you can’t ...

41. { make all the things! }
... but you can? ...

42. { make all the things! }
... but you can! ...
we

43. Rewind... Evolutionary
partial results when partially
implemented can succeed
no evolving system is ever perfect
no single entity can meet all user
needs and account for all niches

44. Embrace the reality,
empower the toolmakers
We can all innovate to add value together!
Define data entities (nouns) ... see EA[1]
Make data accessible so Developers are Efficient
Developers inside and outside your organization
can design + build services with the same data
[1]: http://en.wikipedia.org/wiki/Enterprise_architecture [2013]

45. Empower Developers within
your Organization across
Organizational Boundaries
Improve your Organization’s Productivity

46. Steadily evolve your APIs
and begin using them
yourself.
Improve your Productivity

47. Design for ‘maker’* Users
https://www.gov.uk/designprinciples
* Toolmakers... aka. Developers

48. Design for Access
Access by Design (AbD)
http://www.ipc.on.ca/images/Resources/accessbydesign_7fundamentalprinciples.pdf
Proactive, not Reactive
Access Embedded into Design
Openness and Transparency = Accountability
Fosters Collaboration
Enhances Efficiency
Makes Access Truly Accessible
Increases Quality of Information

49. { provide friendly access }
Empower the ‘maker’ users to help you.
Make friends with developers!

50. { provide open access }
Do your part to help improve productivity!
Empower yourself and others to provide better (more
valuable) service.

51. { further reading }
https://www.gov.uk/service-manual/making-software/apis.html
http://www.w3.org/Provider/Style/URI.html
http://www.shirky.com/writings/evolve.html
http://en.wikipedia.org/wiki/Enterprise_architecture

52. Developer Friendly
Open Data
Albert O’Connor @amjoconn
Colin Bell @collectdevCA