A Data Divide? Data “Haves” and “Have Nots” and Open (Government) Data

Posted on July 11, 2011

14


  • The notion and substance of a “Digital Divide” has been very extensively discussed and researched.  The definition, at its most basic, is that the “Digital Divide” is the “divide” between those who have access to Information and Communications Technologies (ICTs) and particularly the Internet and those who don’t have such access.

(I’ve covered a lot of this below in earlier blog posts and elsewhere but my intention in presenting this here in this form at this time is to raise and focus the discussion of a “Data Divide”particularly for Open Government Data now, when things are still somewhat in flux, and there is the real possibility of those most directly involved–data designers and government folks–paying some attention and intervening in a positive way.)

Researchers have extensively explored the range of social, economic, geographical and other barriers which underlie and to a considerable degree “explain” (cause) the Digital Divide.  My own contribution has been to argue that “access is not enough”, it is whether opportunities and pre-conditions are in place for the “effective use” of the technology particularly for those at the grassroots.

The idea of a possible parallel “Data Divide” between those who have access and the opportunity to make effective use of data and particularly “open data” and those who do not, began to occur to me.  I was attending several planning/recruitment events for the Open Data “movement” here in Vancouver and the socio-demographics and some of the underlying political assumptions seemed to be somewhat at odds with the expressed advocacy position of “data for all”.

Thus the “open data” which was being argued for would not likely be accessible and usable to the groups and individuals with which Community Informatics has largely been concerned – the grassroots, the poor and marginalized, indigenous people, rural people and slum dwellers in Less Developed countries. It was/is hard to see, given the explanations, provided to date how these folks could use this data in any effective way to help them in responding to the opportunities for advance and social betterment which open data advocates have been indicating as the outcome of their efforts.

As I presented this uneasiness in public fora and through my blog it became additionally clear that many involved in “open data” saw their interests and activities being confined to making data ‘legally” and “technically” accessible — what happened to it after that was somebody else’s responsibility. And with this I partially agree. Ensuring the broadest opportunity for the use of (for example) Open (Government) Data (OGD) is a broad public responsibility which of course, is shared between public authorities and technical developers; with however, the technical developers having the responsibility (IMHO) to ensure that from their – technical – side no barriers are introduced (and technical barriers are removed) to allowing for the broadest possible public use of the data where they are undertaking their activities.

As I thought more actively on these issues I realized that while there were striking parallels between the Digital Divide and what I was rapidly coming to see as an associated “Data Divide” there were also very substantial and significant differences –notably while the Digital Divide deals with, for the most part “infrastructure” issues, the Data Divide is concerned with “content” issues.

As well, where a Digital Divide might exist for example, as a result of geographical or policy considerations and thus have uniform effects on all those on the wrong side of the “divide” whatever their socio-demographic situation; a Data Divide and particularly one of the most significant current components of the Open Data movement i.e. OGD, would have particularly damaging negative effects and result in particularly significant lost opportunities for the most vulnerable groups and individuals in society and globally. (I’ve discussed some examples here at length in a previous blogpost.)

The Data Divide thus would be the gap between those who have access to and are able to use Open (Government) Data and those who are not so enabled.

I have suggested elsewhere that there are seven layers/components through which a “Data Divide” (building on my similar analysis of the Digital Divide”) might be understood:

1. infrastructure—being on the wrong side of the “Digital Divide” and thus not having access to the basic infrastructure supporting the availability of OGD.

2. devices—OGD that is not universally accessible and device independent (that only runs on I-Phones for example)

3. software—“accessible” OGD that requires specialized technical software/training to become “usable”

4. content—OGD not designed for use by those with handicaps, non-English speakers, those with low levels of functional literacy for example

5.  interpretation/sense-making—OGD that is only accessible for use through a technical intermediary and/or is useful only if “interpreted” by a professional intermediary

6. advocacy—whether the OGD is in a form and context that is supportive for use in advocacy (or other purposes) on behalf of marginalized and other groups and individuals

7. governance—whether the OGD process includes representation from the broad public in its overall policy development and governance (not just lawyers, techies and public servants).

Intervening at this relatively early stage – whether by Open Data designers or through government (or other) policy and programmes (or most desirably both) –can help to avoid a Data Divide and preclude many of the negative effects (and relatively costly make up efforts) and lost opportunities associated with the Digital Divide.

My strong suggestion/hope would be that a minimum of 10% of expenditures on OGD would go to ensuring that structures of “data haves” and “data have nots’ was not being created as an outcome of OGD projects. Contributions to training for data use, for digital literacy, for disability oriented user interface design, to support advocacy based on OGD, for ensuring that OGD is not device dependent, to assist in participation in OGD governance and others would go some way in ensuring this outcome.

Advertisements