What's Different that Makes Open Data an Infrastructure?

Article by Christopher Thomas: “It wasn’t too long ago that governments remained pretty guarded with their data. It really did not matter who the data steward was, as each discipline had its “reasons” for keeping data out of the hands of others…
The mapping and GIS industry was no stranger to the resistance to open data.  However the concerns were slightly different than the governments’ concerns.  Perhaps this was due to the time, effort, and money required to develop the data by staff.  Mapping and GIS fought a valiant battle that this data was not information subject to the Freedom of Information Act, but rather an asset subject to different rules of funding and cost recovery.
Recently, attitudes have been changing as mapping and GIS data are being looked at as more of an infrastructure, because governments now see the importance of including it as part of their daily operation. …
So what’s different today? Well, governments can avoid data dumps that leave important members of your team wondering how the data is being used.  Or better yet, wondering how many times your old data has been exchanged and used without new or updated data being considered. You later learn that someone has used your old data on a project that has come back to haunt you.  The major difference today is that there is an ability to extend this infrastructure as a web service.  If you publish current data on websites or portals, data can now be downloaded for use in various products or connected to apps. As Mark Head, chief data officer for the city of Philadelphia puts it, “web services are the ‘secret sauce’ to open data.” Governments can simply extend map and GIS data for adoption by business startups and civic hackers, for example, with the confidence that current data is being used.”