My assessment is the Australian Government National Action Plan is based on solid principles and goals, but implementation recommendations are still relatively immature. It is as if experiences so far have been based on small pilot projects and small groups and is yet to hit the challenges associated with scalability, reliability, maintainability and interoperability.
Lets expand on this statement, under National Action Plan Themes:
Freedom of Information:
Australia has an open by default policy for government data. A great first step, but of minimal value until the data is readily usable. Yes, a bus timetable is useful when a paper copy of it is distributed to commuters every 6 months. But it is super useful when bus timetables are integrated with real-time bus and traffic data travel plans can be adjusted accordingly. This is facilitated by the concept of "mashable government" where government data is made available in machine readable form via standards based Application Programmer Interfaces (APIs).Cross agency integration of datasets can open up significant value, but usually requires addressing of technical, financial, legal and social challenges. Agencies need to agree upon common formats for common datasets (typically through use open standards). Who benefits from aggregated datasets is usually different to those who collects and maintains the data. As such, solving integration issues often requires creative, cross-agency, business cases to be crafted.
The National Action Plan should discuss: Mashable Government, APIs, use/extend/create open standards (in that order), writing business cases to identify high value datasets, and cross-agency funding of data management strategies.
Public Participation:
There has been good progress in bi-directional communication between citizens and government. There are now excellent tools to run YES/NO polls past many people to gauge community sentiment.A challenge worth tackling is how to enable public debate and evidence based decisions on complex topics - such as Climate Change. Complex systems require significant time to understand, which makes them susceptible to misdirected influence from vested interest groups. Questions to consider:
- Who will fund "trusted experts" to research and advise on complex issues so they can make informed decisions?
- How can a community vote on complex subjects?
- How do you address the signal-to-noise ratio within community discussions?
Fiscal Transparency:
Despite open government policies highlighting benefits of open source software and open standards, government uptake of open source is surprisingly low. Why? Because government purchasing practices inadvertently favour proprietary software and vendor lock-in tactics over collaborative business practices used by open communities. There are multiple aspects to this, which should be understood, leading to updated guidelines to government purchasing practices. Some considerations include:- How to compare long term value of open source and proprietary business models.
- How to assess the health of an open source community and associated rate of innovation in order to properly assess the value of open source.
- How to assess a product's claims of standards compliance. Some companies dissuade standards use by pricing extra for standards use, or limiting standards based functionality.
- How to assess the quality and applicability of a standard, and whether to invest in influencing the development of the standard.
- Typically government officials have mandate to solve department-wide problems, however open source and open standards based solutions will often be best justified at a Whole-Of-Government, or Whole-Of-World level. One particular argument is "If I invest in an open standard, or open source, I will see minimal immediate benefit, but long term will see international adoption which will lead to advancement of my local goals."
- Government's asymmetric spending of discretionary budgets at year-end disadvantages fee-for-service business models typically employed by open source businesses.
