Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Standards and Open Source Cities

Philip Ashlock
September 19, 2012

Standards and Open Source Cities

Standards and Open Source Cities: Collaboration driven by shared platforms

A talk I gave at Open Knowledge Festival Helsinki in 2012
http://okfestival.org

Philip Ashlock

September 19, 2012
Tweet

More Decks by Philip Ashlock

Other Decks in Technology

Transcript

  1. Philip Ashlock | CivicAgency.org | OKfest September 2012
    Standards and Open Source Cities:
    Collaboration driven by shared platforms

    View Slide

  2. View Slide

  3. OpenPlans builds open source civic infrastructure.
    We collaborate with the public sector to create technology
    for a more efficient, responsive, and inclusive government.
    OpenPlans.org

    View Slide

  4. NYC Real-Time Bus Information

    View Slide

  5. View Slide

  6. View Slide

  7. View Slide

  8. View Slide

  9. View Slide

  10. View Slide

  11. View Slide

  12. Facilitates collaboration to improve government by
    sharing technology, building open platforms, and
    spreading knowledge.

    View Slide

  13. View Slide

  14. View Slide

  15. Find opportunities for collaboration,
    match needs and tools
    Research & communicate best practices.
    Support & foster standards.
    Apply the extra effort to spark &
    sustain collaboration
    Build the legal and policy framework
    to institutionalize collaboration

    View Slide

  16. Cities
    Support
    Organizations
    Technologies Information
    Resources

    View Slide

  17. Cities
    Support
    Organizations
    Technologies Information
    Resources
    Communities & Ecosystems

    View Slide

  18. Cities
    Support
    Organizations
    Technologies Information
    Resources
    Sustainable!

    View Slide

  19. Sharing Technology

    View Slide

  20. Disrupt procurement with an open marketplace
    Needs
    Tools Support

    View Slide

  21. Precedents

    View Slide

  22. hp://commons.codeforamerica.org
    COMMONS

    View Slide

  23. View Slide

  24. View Slide

  25. View Slide

  26. View Slide

  27. View Slide

  28. Motivation to release
    vs
    Motivation to re-use

    View Slide

  29. ?

    View Slide

  30. View Slide

  31. View Slide

  32. View Slide

  33. An open communication standard for
    public services & local government
    Open311

    View Slide

  34. View Slide

  35. View Slide

  36. View Slide

  37. View Slide

  38. View Slide

  39. View Slide

  40. View Slide

  41. View Slide

  42. View Slide

  43. View Slide

  44. View Slide

  45. View Slide

  46. View Slide

  47. View Slide

  48. • Governments can’t easily manage or control all these
    different apps and communication channels.
    • People don’t always have clear expectations set for
    whether government can respond or act.
    • Many apps aren’t actually connected to the official
    government CRMs.
    • Most apps aren’t compatible with one another and
    everyone has a different app.
    Problems with proliferation

    View Slide

  49. API
    PC / Web
    SaaS
    Cloud Integration
    CRM
    SMS
    Tablet
    Mobile
    Web
    Smart Phone
    Voice
    IVR

    View Slide

  50. • Governments can control which apps connect and how
    they are used.
    • Governments can provide automated responses and show
    SLA’s where appropriate.
    • Many different apps and communication channels can
    simultaneously connect to the official CRM.
    • With many apps and services working interoperably using
    the same API, people and government have more choice.
    Benefits of a web API

    View Slide

  51. Boston NYC Portland Pisburgh
    Reinventing the Wheel
    Should everyone have a custom app? Or just different branding?

    View Slide

  52. Distributed innovation
    API
    API
    API

    View Slide

  53. Interoperability
    Consistency
    Ubiquity
    Efficiency
    Shareability
    Benefits of an open standard

    View Slide

  54. How Open311 was born

    View Slide

  55. View Slide

  56. View Slide

  57. DevCamp
    New York City October 24, 2009

    View Slide

  58. View Slide

  59. View Slide

  60. Open311
    GeoReport v2
    Established March 2011

    View Slide

  61. Edmonton
    Vancouver
    Portland
    San Francisco New York City
    Washington D.C.
    Toronto
    Chicago
    Boston
    Baltimore
    Miami
    Philadelphia
    Seattle
    Bloomington
    New Orleans
    Tuscon
    New Haven
    Grand Rapids
    See http://wiki.open311.org/GeoReport_v2/Servers
    St Louis
    Houston

    View Slide

  62. Barnet
    Southampton
    Cebu
    Helsinki
    See Map of
    North America
    Open311 Worldwide
    Dominican
    Republic
    Darwin

    View Slide

  63. ~ 35 city endpoints
    ~ 10 vendor supported products
    ~ 5 open source servers
    ~ 7 open source clients
    ~ 6 client libraries
    For details see:
    http://wiki.open311.org/GeoReport_v2/Servers
    http://wiki.open311.org/GeoReport_v2/Support
    http://wiki.open311.org/GeoReport_v2/Resources
    Open311 GeoReport v2 Stats

    View Slide

  64. View Slide

  65. View Slide

  66. View Slide

  67. Open311 Dashboard

    View Slide

  68. Open311 on Joget

    View Slide

  69. Open311 on Mark a Spot

    View Slide

  70. Open311 on FixMyStreet

    View Slide

  71. Open311 Server from Miami-Dade County

    View Slide

  72. View Slide

  73. View Slide

  74. View Slide

  75. View Slide

  76. View Slide

  77. Distributed innovation
    API
    API
    API
    Standards establish
    platforms of collaboration

    View Slide

  78. GeoReport v2 Service Requests
    Inquiry v0.1 FAQ Knowledgebase
    Open311 Specifications


    ✓ Ideation: Answers/suggestions

    View Slide

  79. Issue Report: Request / Report
    Inquiry: Ask / Search
    wiki.civiccommons.org/Collaboration_Platforms
    Patterns of Interaction


    ✓ Ideation: Answer / Suggest

    View Slide

  80. View Slide

  81. View Slide

  82. Not just informal questions, but also
    formal requests for information:
    “Open FOI”

    View Slide

  83. View Slide

  84. View Slide

  85. What if anyone could answer?

    View Slide

  86. View Slide

  87. Suggest Ideas

    View Slide

  88. View Slide

  89. View Slide

  90. Integration with
    Urban Planning
    &
    Participatory Budgeting

    View Slide

  91. View Slide

  92. View Slide

  93. View Slide

  94. View Slide

  95. Unify these interactions?

    View Slide

  96. View Slide

  97. View Slide

  98. ?

    View Slide

  99. Civic Engagement
    - as -
    Citizens of
    Open Source Communities

    View Slide

  100. “Crowdsourced Government”
    “Open Source Data”
    Mixed Metaphors
    “Participatory Democracy”

    View Slide

  101. t
    Web Republic
    Public
    Parsable Free Citizen
    Open Data
    Process
    Platform Democracy
    Open Interface
    Decentralized
    Distributed Open Standards Constitution
    Open
    The Architecture of Participation
    http://bit.ly/openocracy

    View Slide

  102. Web Republic
    Public
    Parsable Free Citizen
    Open Data
    Process
    Platform Democracy
    Open Interface
    Decentralized
    Distributed Open Standards Constitution
    Open
    Open Code
    Open Development
    Open Licenses
    Apps
    &

    View Slide

  103. View Slide

  104. View Slide

  105. View Slide

  106. View Slide

  107. GeoWeb DNS / LoST
    http://api.democracymap.org

    View Slide

  108. www.citysdk.eu
    pdxcitysync.org

    View Slide

  109. View Slide

  110. View Slide

  111. View Slide

  112. View Slide

  113. View Slide

  114. View Slide

  115. @projectmygov bit.ly/mygovblog

    View Slide

  116. Questions

    View Slide

  117. Civic Agency
    [email protected] / @civicagency
    Philip Ashlock / @philipashlock

    View Slide