Skip to main content

Mashing in the UK?

In the last two weeks, several people have suggested to me that the UK could take more advantage of data collected here. Public agencies such as the Met. Office, Ordnance Survey, Transport for London, the British Crime Survey, the Land Registry and others hold data on various aspects of our lives. Private companies such as Experian and major retailers collect much more. If these were available as web services (in the broadest sense), inventive developers could mix and match them in new ways, displaying the results in meaningful ways (such as in map form).

Such activities are already popular in the USA, where more similar data sets are available. A widely-quoted example is Chicago Crime and there are many more. The question is, how can the UK catch up?

A few example projects are already underway. The DEWS project is combining Met Office data with health information and (separately) the coastguard. The Ordnance Survey is holding a Mashups day. Paul Longley's team at UCL caught the public eye with their Surname Profiler and eSociety Profiler. The Department for Transport has funded similar work - e.g. travel time maps and a data mashing workshop.

Despite these examples, "mashing" has yet to really take off in the UK. A major block is that some of the data is only available commercially - for example, there is an ongoing debate about access to Ordnance Survey data. I'm not against people making money - far from it - but the UK could benefit from providing would-be entrepeneurs with better access to data sets for experimental use. Licences could then be charged on commercial ventures that arise as a result, benefitting both the entrepeneurs and the data curators.

We also need to increase the provision of data sets in the first place, preferably using a small set of standard access mechanisms. Web services seem a good candidate, especially where secure access may be an issue. Alternatively, plain Web 2.0 interfaces may be good enough to experiment with.

The whole area could benefit from some joined-up thinking and collaboration across a range of agencies. Provided, of course, that this hurries things along rather than holding it up while people argue.


Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.

This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…

A brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…